Group call processing method and communication apparatus

By acquiring and processing group call information through the client and sending instructions to the server to merge group calls, the problem of merging multiple group calls in emergency tasks is solved, achieving efficient merging and improved user experience.

WO2026237610A1PCT designated stage Publication Date: 2026-11-19HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/089665
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-12
Filing Date
2026-04-09
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

In emergency mission operations, how to effectively merge multiple group calls to improve user experience and efficiency, especially when multiple group calls exist, is a challenge that existing technologies struggle to achieve efficient merging.

Method used

The client obtains and processes group call information, sends instructions to the server to merge participants in two or more group calls, determines the merging method based on factors such as priority, number of participants, and establishment method, and updates the group call information on the server side to achieve the merging.

Benefits of technology

It enables efficient merging of group calls, improves user experience and merging efficiency, simplifies server-side operations, and reduces client-side processing burden.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026089665_19112026_PF_FP_ABST
    Figure CN2026089665_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure provides a group call processing method and a communication apparatus. In some embodiments, a client acquires information of a first group call and information of a second group call; and the client transmits first information to a server, wherein the first information is used for adding participants of the first group call and participants of the second group call to the same group call. In this way, in the embodiments of the present disclosure, the client can acquire the information of the first group call and the information of the second group call, and transmit the first information to the server, so as to add the participants of the first group call and the participants of the second group call to the same group call, thereby implementing merging of the two group calls.
Need to check novelty before this filing date? Find Prior Art

Description

Group call processing method and communication device

[0001] This application claims priority to Chinese Patent Application No. 202510608564.1, filed on May 12, 2025, entitled “Group Call Processing Method and Communication Device”, which is incorporated herein by reference in its entirety. Technical Field

[0002] The embodiments disclosed herein mainly relate to the field of communications, and more specifically, to a group call processing method and a communication device. Background Technology

[0003] Mission critical (MC) services can be used to support trunked communication in public safety scenarios. Examples include mission critical push-to-talk (MCPTT) systems for voice, data (MCData), and video (MCVideo). These systems allow group calls, where a single group call involves communication between multiple clients. In scenarios with more than one group call, how to merge two or more group calls is one of the issues that needs to be considered. Summary of the Invention

[0004] This disclosure provides a scheme for group call processing that can add participants from different group calls to the same group call.

[0005] In a first aspect of this disclosure, a group call processing method is provided, which can be executed by a client. The method includes: acquiring information about a first group call and information about a second group call; and, based on the information about the first group call and the second group call, sending first information to a server, the first information being used to add participants from the first group call and participants from the second group call to the same group call.

[0006] In this manner, embodiments of the present disclosure enable the client to obtain information about the first group call and the second group call, and to send first information to the sending server so as to add the participants of the first group call and the participants of the second group call to the same group call, thereby realizing the merging of the two group calls.

[0007] In some implementations, the first information includes group call update information, which indicates that the second group call should be updated by adding participants from the first group call to the second group call. In this way, by updating the second group call, participants from both the first and second group calls are included in the updated second group call, thus achieving group call merging.

[0008] In some implementations, the method further includes: determining, based on at least one of the following, to update the second group call by adding participants from the first group call to the second group call: the number of participants in the first group call and the number of participants in the second group call; the priority of the first group call and the priority of the second group call; the establishment method of the first group call and the establishment method of the second group call; user preference information corresponding to the client, or the client's local policy. For example, the merging method is to update the second group call by adding participants from the first group call to the second group call. In this way, the client can determine the merging method, giving the client more initiative in merging group calls and improving the user experience.

[0009] In some implementations, the decision to update the second call group by adding participants from the first call group to the second call group is based on at least one of the following: adding participants from the first call group to the second call group is determined if at least one of the following conditions is met: the number of participants in the first call group is less than the number of participants in the second call group; the priority of the first call group is lower than the priority of the second call group; the first call group is established based on a user list, and the second call group is established based on a criterion; or the first call group is established based on a first criterion, and the second call group is established based on a second criterion, and the region corresponding to the first criterion is smaller than the region corresponding to the second criterion. In this way, the merging method can be determined through predetermined judgment conditions, adding participants from the first call group to the second call group, simplifying the merging process and improving merging efficiency.

[0010] In some implementations, the group call update information includes at least one of the following information from the updated second group call: key index information, priority, security level, broadcast method, or hang time. In this way, the client can determine or specify partial information from the updated second group call, facilitating rapid group call merging on the server side.

[0011] In some implementations, the first information includes group call establishment information, which is used to establish a third group call. The participants in the third group call include those from the first and second group calls. In this way, by creating a new third group call, participants from the first and second group calls can be added to the third group call, thus achieving group call merging.

[0012] In some implementations, the group call setup information includes the identifier of the third group call. This allows the user on the client side to specify the identifier of the third group call to be established, reducing additional operations on the server side.

[0013] In some implementations, the group call setup information includes at least one of the following: key index information, priority, security level, broadcast method, or hang time. In this way, the client can determine or specify some information about the third group call, facilitating rapid group call setup on the server side.

[0014] In some implementations, the method further includes sending a second message to the control function of the second call group, the second message being used to release the second call group. Thus, after the third call group is established, the control function of the second call group can release the second call group.

[0015] In some implementations, the method further includes sending third information to the server of the first call group, the third information being used to release the first call group. Thus, after updating the second call group or establishing the third call group, the control functions of the first call group can release the first call group.

[0016] In some implementations, the first information includes at least one of the following: a list of users for the first group call, the criteria for establishing the first group call, a list of users for the second group call, or the criteria for establishing the second group call. In this way, the client can provide the server with information about the establishment methods of the first group call and / or the second group call, which facilitates the server's merging of participants in the first group call and / or the second group call.

[0017] In some implementations, the first information includes information used to trigger the merging of the first and second call groups. This allows the server to determine the specific merging method, reducing the processing burden on the client side.

[0018] In some implementations, the method further includes: obtaining information about multiple group calls, including a first group call and a second group call; and determining, based on the information about the multiple group calls, to merge the first group call and the second group call. In this way, the client can decide which group calls to merge.

[0019] In some implementations, the first information includes information about the first group of calls and / or the second group of calls. In this way, the information about the first and second group of calls can be provided to the server, allowing the server to determine the merging method.

[0020] In some implementations, the first information includes the identification information of the first group of calls and the identification information of the second group of calls. This makes it easier for the server to determine which group of calls to merge.

[0021] In some implementations, obtaining information about the first and second group calls includes: obtaining information about the first group call from the server of the first group call; and obtaining information about the first group call from the server of the second group call. In this way, the client can obtain information about both group calls from the servers of the first and second group calls respectively, which facilitates the merging of group calls.

[0022] In some implementations, the information of the first group call and / or the information of the second group call includes at least one of the following: the identification information of the group call, the method of establishing the group call, the priority of the group call, the list of participants in the group call, the criteria for establishing the group call, the number of participants in the group call, the information of the initiator of the group call, the security level of the group call, the broadcasting method of the group call, or the hang time of the group call.

[0023] In a second aspect of this disclosure, a group call processing method is provided, which can be implemented by a server or a control function. The method may include: receiving first information for adding participants of a first group call and participants of a second group call to the same group call; and adding participants of the first group call and participants of the second group call to the same group call based on the first information.

[0024] In some implementations, the first information includes group call update information, which is used to indicate that the second group call should be updated by adding participants from the first group call to the second group call.

[0025] In some implementations, the group call update information includes at least one of the following information from the updated second group call: key index information, priority, security level, broadcast method, or hang time.

[0026] In some implementations, the method further includes: updating the second group call and determining at least one of the following information for the updated second group call: key index information, priority, security level, broadcast method, or hang time.

[0027] In some implementations, the first information includes group call establishment information, which is used to establish a third group call, wherein the participants in the third group call include the participants in the first group call and the participants in the second group call.

[0028] In some implementations, the group call setup information includes the identification information of the third group call.

[0029] In some implementations, the group call setup information includes at least one of the following information for the third group call: key index information, priority, security level, broadcast method, or hang time.

[0030] In some implementations, the method further includes: establishing a third group call and determining at least one of the following information for the third group call: key index information, priority, security level, broadcast method, or hang time.

[0031] In some implementations, the first information includes at least one of the following: a list of users for the first group of calls, the criteria for establishing the first group of calls, a list of users for the second group of calls, or the criteria for establishing the second group of calls.

[0032] In some implementations, the first information includes information for triggering the merging of the first and second call groups.

[0033] In some implementations, the method further includes determining, based on at least one of the following, whether to update the second call group by adding participants from the first call group to the second call group: the number of participants in the first call group and the number of participants in the second call group; the priority of the first call group and the priority of the second call group; the establishment method of the first call group and the establishment method of the second call group; or a local policy of the server. This approach fully utilizes the server's processing power, allowing the server to determine the merging method, thus simplifying the processing complexity at the client end.

[0034] In some implementations, the decision to update the second call by adding participants from the first call group to the second call group is based on at least one of the following: adding participants from the first call group to the second call group is determined if at least one of the following conditions is met: the number of participants in the first call group is less than the number of participants in the second call group; the priority of the first call group is lower than the priority of the second call group; the first call group is established based on a user list and the second call group is established based on a criterion; or the first call group is established based on a first criterion and the second call group is established based on a second criterion, and the area corresponding to the first criterion is smaller than the area corresponding to the second criterion.

[0035] In some implementations, based on the first information, participants in the first group call and participants in the second group call are added to the same group call. This includes: sending addition information to the control function of the first group call based on the first information, whereby the addition information is used to add the participants of the first group call to the second group call; or establishing a third group call based on the first information, where the participants of the third group call include the participants of the first group call and the participants of the second group call. In this way, the server of the third group call can send information to the control function of the first / second group call to add the participants of the first group call and the participants of the second group call to the third group call, thereby achieving the merging of group calls.

[0036] In some implementations, the method further includes sending a second message to the control function of the second call group, the second message being used to release the second call group. Thus, after the third call group is established, the control function of the second call group can release the second call group.

[0037] In some implementations, the method further includes sending third information to the server of the first call group, the third information being used to release the first call group. Thus, after updating the second call group or establishing the third call group, the control functions of the first call group can release the first call group.

[0038] In some implementations, establishing a third group call based on the first information includes: sending a fourth information to the control function of the first group call, the fourth information being used to add the participants of the first group call to the third group call; and sending a fifth information to the control function of the second group call, the fifth information being used to add the participants of the second group call to the third group call.

[0039] In some implementations, the method further includes receiving information or right-to-speaker request information from the speaker of the second group call, which is used to request right-to-speaker status for the speaker of the second group call in the third group call. This facilitates control over right-to-speaker status in the third group call and avoids conflicts between speakers' right-to-speaker situations.

[0040] In some implementations, the method further includes: determining the speaker in the third group of calls, whereby the speaker in the third group of calls is either the speaker in the first group of calls or the speaker in the second group of calls. In this way, the server can determine the speaker in the third group of calls through speaker adjudication.

[0041] In some implementations, the method further includes: determining to reject the speaking request of the first speaker in the first group of calls and to approve the speaking request of the second speaker in the second group of calls. In some implementations, the method further includes: sending an approval message to the client of the second speaker via the control function of the second group of calls, and sending a rejection message to the client of the first speaker via the control function of the first group of calls.

[0042] In some implementations, the method further includes sending a sixth message to the control functions of the first and second call groups, the sixth message indicating that the speaker's right of speech is available in the third call group. In this way, the speaker's right of speech in the first and second call groups can be cleared, and the speaker's right of speech can be indicated as available.

[0043] In some implementations, the information of the first group call and / or the information of the second group call includes at least one of the following: the identification information of the group call, the method of establishing the group call, the priority of the group call, the list of participants in the group call, the criteria for establishing the group call, the number of participants in the group call, the information of the initiator of the group call, the security level of the group call, the broadcasting method of the group call, or the hang time of the group call.

[0044] In a third aspect of this disclosure, a group call processing method is provided, which can be implemented by a server of a first group call or a control function of the first group call. The method may include: receiving fourth information for adding participants of the first group call to a third group call; and sending response information indicating acceptance of joining the third group call. Exemplarily, the fourth information may originate from the control function of the third group call, and the response information may be sent to the control function of the third group call.

[0045] In some implementations, the method also includes updating local media plane forwarding rules. For example, uplink data from participants in the first group of calls can be forwarded to the control function of the third group of calls, and downlink data from the control function of the third group of calls can be forwarded to participants in the first group of calls (i.e., participants in the third group of calls).

[0046] In some implementations, the method may also include updating local discourse control rules, for example, sending the received speaker's discourse request information to the control function of a third group call.

[0047] In some implementations, the method may further include: sending information about the speaker of the first group call or a right-to-speak request to the control function of the third group call, wherein the right-to-speak request is used to request the right to speak for the speaker of the first group call in the third group call.

[0048] In some implementations, the method may also include receiving consent speech information from the control function of a third group of calls, such as speech authorization information.

[0049] In some implementations, the method may also include: receiving a rejection message from the control function of the third group call; and sending a revocation message to the client of the first speaker.

[0050] In some implementations, the method further includes: receiving control function sixth information from the third group call, the sixth information indicating that the third group call has idle speaking rights. In some implementations, the method further includes: sending speaking right revocation information to the client of the first speaker based on the idle speaking rights information.

[0051] In some implementations, the method further includes sending notification information to the participants of the first group call, which may include: key index information and / or identification information of the third group call.

[0052] In some implementations, the method further includes: receiving request information from a client; and sending information about the first group call to the client. Exemplarily, the information about the first group call includes at least one of the following: group call identification information, group call establishment method, group call priority, list of participants in the group call, criteria for group call establishment, number of participants in the group call, information about the group call initiator, security level of the group call, broadcast method of the group call, or hang time of the group call.

[0053] In a fourth aspect of this disclosure, a communication apparatus is provided. The apparatus includes an acquisition module and a transmission module. The acquisition module can be configured to acquire information from a first group call and information from a second group call. The transmission module can be configured to send first information to a server based on the information from the first and second group calls, the first information being used to add participants from the first and second group calls to the same group call. In some implementations, the communication apparatus can be implemented as a client as described in the first aspect, and the communication apparatus can implement the methods described in the first aspect or any of its implementations.

[0054] In a fifth aspect of this disclosure, a communication apparatus is provided. The apparatus includes a receiving module and a processing module. The receiving module can be configured to receive first information for adding participants of a first group call and participants of a second group call to the same group call. The processing module can be configured to add participants of the first group call and participants of the second group call to the same group call based on the first information. In some implementations, the communication apparatus can be implemented as a server or control function as described in the second aspect above, and the communication apparatus can implement the methods described in the second aspect above or any implementation thereof.

[0055] In a sixth aspect of this disclosure, a communication apparatus is provided. The apparatus includes a receiving module and a transmitting module. The receiving module can be configured to receive fourth information from a control function of a third group call, the fourth information being used to add participants from a first group call to the third group call. The transmitting module can be configured to send response information to the control function of the third group call, the response information being used to indicate acceptance of joining the third group call. In some implementations, the communication apparatus can be implemented as a server or control function of the first group call as described in the third aspect above, and the communication apparatus can implement the methods described in the third aspect above or any implementation thereof.

[0056] In some implementations, the receiving module can be implemented as a receiver or transceiver, the transmitting module can be implemented as a transmitter or transceiver, and the processing module can be implemented as a processor or control circuit.

[0057] In a seventh aspect of this disclosure, a communication apparatus is provided. The apparatus includes one or more processors configured, together with a transceiver, to cause the communication apparatus to perform the methods described in the first aspect or any implementation thereof. In some implementations, the communication apparatus may include one or more memories configured to store instructions or computer program instructions executable by one or more processors. In some implementations, when the instructions are executed by one or more processors, the communication apparatus causes to perform the methods described in the first aspect or any implementation thereof.

[0058] In an eighth aspect of this disclosure, a communication apparatus is provided. The apparatus includes one or more processors configured, together with a transceiver, to cause the communication apparatus to perform the methods described in the second aspect or any implementation thereof. In some implementations, the communication apparatus may include one or more memories configured to store instructions or computer program instructions executable by one or more processors. In some implementations, when the instructions are executed by one or more processors, the communication apparatus causes to perform the methods described in the second aspect or any implementation thereof.

[0059] In a ninth aspect of this disclosure, a communication apparatus is provided. The apparatus includes one or more processors configured, together with a transceiver, to cause the communication apparatus to perform the methods described in the third aspect or any implementation thereof. In some implementations, the communication apparatus may include one or more memories configured to store instructions or computer program instructions executable by one or more processors. In some implementations, when the instructions are executed by one or more processors, the communication apparatus causes to perform the methods described in the third aspect or any implementation thereof.

[0060] In a tenth aspect of this disclosure, a communication system is provided, including communication devices as described in the fourth (or seventh) aspect and communication devices as described in the fifth (or eighth) aspect. In some implementations, the communication system may further include communication devices as described in the sixth (or ninth) aspect.

[0061] In the eleventh aspect of this disclosure, a computer-readable storage medium is provided, which stores computer-executable instructions that, when executed, implement operations according to the method of the first aspect or any implementation thereof, or implement operations according to the method of the second aspect or any implementation thereof, or implement operations according to the method of the third aspect or any implementation thereof. In some implementations, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

[0062] In a twelfth aspect of this disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry configured to perform operations according to the method of the first aspect or any implementation thereof, or to implement operations according to the method of the second aspect or any implementation thereof, or to implement operations according to the method of the third aspect or any implementation thereof.

[0063] In a thirteenth aspect of this disclosure, a computer program or computer program product is provided. The computer program or computer program product is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, implement the operation of the method according to the first aspect or any implementation thereof, or implement the operation of the method according to the second aspect or any implementation thereof, or implement the operation of the method according to the third aspect or any implementation thereof.

[0064] It should be understood that the technical effects in the first aspect and its various implementations also apply to each of the second to thirteenth aspects, therefore the technical effects of the second to thirteenth aspects will not be described again in this paper.

[0065] It should be understood that the description in the Summary of the Invention is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0066] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0067] Figure 1A shows a schematic diagram of the functional model of the application surface of the MCPTT service;

[0068] Figure 1B illustrates a schematic diagram of group call creation based on a user list.

[0069] Figure 1C shows a schematic diagram of group call establishment based on criteria.

[0070] Figure 1D shows a schematic diagram of an example system in which embodiments of the present disclosure can be applied;

[0071] Figure 2 shows a flowchart of an example process for group call processing according to some embodiments of the present disclosure;

[0072] Figure 3A illustrates a schematic diagram of an example process for determining and updating the second group of calls according to some embodiments of the present disclosure;

[0073] Figure 3B illustrates a schematic diagram of an example process for determining and updating the second group of calls according to some embodiments of the present disclosure;

[0074] Figure 4 illustrates a schematic diagram of an example process for merging group calls according to some embodiments of the present disclosure;

[0075] Figure 5A illustrates a schematic diagram of an example process for determining the establishment of a group call according to some embodiments of the present disclosure;

[0076] Figure 5B illustrates a schematic diagram of an example process for merging group calls according to some embodiments of the present disclosure;

[0077] Figure 5C illustrates a schematic diagram of an example process for merging group calls according to some embodiments of the present disclosure;

[0078] Figure 5D illustrates a schematic diagram of an example process for handling discourse power according to some embodiments of this disclosure;

[0079] Figure 6 illustrates a schematic diagram of an example process for determining a user list / criteria according to some embodiments of the present disclosure;

[0080] Figure 7 shows an example block diagram of a communication device according to some embodiments of the present disclosure;

[0081] Figure 8 shows an example block diagram of a communication device according to some embodiments of the present disclosure; and

[0082] Figure 9 shows a schematic block diagram of an example device that can be used to implement embodiments of the present disclosure. Detailed Implementation

[0083] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0084] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc., may refer to different or the same objects. The term "and / or" indicates at least one of the two items associated therewith. For example, "A and / or B" means A, B, or A and B. Other explicit and implicit definitions may also be included below.

[0085] In embodiments of this disclosure, unless otherwise expressly stated, “a plurality of” means at least two, that is, two or more.

[0086] The embodiments of this disclosure involve the term "group call," which can be replaced by call, voice call, group call, group talk, group communication, etc., and this disclosure is not limited thereto. Optionally, the group call in the embodiments of this disclosure can be an ad hoc group call (AHGC). In the embodiments of this disclosure, the term "group call identifier" can be replaced by group call identification information, group call ID, group ID, call ID, etc., and this disclosure is not limited thereto. In the embodiments of this disclosure, the following terms are interchangeable: client, terminal, UE, user, member, participant, group member, etc.

[0087] The Third Generation Partner Project (3GPP) has defined the functional architecture, processes, and information flows required to support MCPTT services. Figure 1A shows a schematic diagram of the functional model 100A of the application surface of the MCPTT service. For example, the MCPTT service can support MC services based on Long Term Evolution (LTE). The MCPTT system shown in Figure 1A includes: an MCPTT server 151, an MCPTT UE 161, other MCPTT servers 171, an MCPTT user database 172, a network interconnection function to legacy systems 173, and an MC gateway server 174. This MCPTT system connects to other MCPTT systems, including MC gateway server 175, through the MC gateway server 174. As shown, the interface between the MCPTT server 151 and the network interconnection function to legacy systems 173 is an Interworking Function (IWF-1) interface. As shown, the MCPTT server 151 includes a media distribution function 152 and a talk control server 153. As shown in the figure, MCPTT UE 161 includes an MCPTT client 162, which includes a media mixer 163 and a floor participant 164.

[0088] Additionally, MCPTT-x (where x is an integer between 1 and 10) shown in Figure 1A represents the logical interface between different logical entities. For example, MCPTT-9 carries multicast speech control signaling between the speech control server 153 of MCPTT server 151 and the speech participant 164 of MCPTT UE 161. For example, MCPTT-4 carries unicast speech control signaling between the speech control server 153 of MCPTT server 151 and the speech participant 164 of MCPTT UE 161. For example, MCPTT-7 carries unicast media between the media distribution function 152 of MCPTT server 151 and the media mixer 162 of MCPTT UE 161. For example, MCPTT-8 carries multicast media from the media distribution function 152 of MCPTT server 151 to the media mixer 163 of MCPTT UE 161.

[0089] In some cases, the MCPTT system in Figure 1A can be adapted to MCPTT voice service using the evolved universal terrestrial radio access network (E-UTRAN) based on the evolved packet system (EPC) architecture.

[0090] The Mission Critical Service Server (MC Service Server / MC server) is a logical entity primarily responsible for call control, media control, service authorization, and user registration processing. For example, it could be the MCPTT server 151 shown in Figure 1A, or an MCVideo server or MCData server, etc. For instance, the MC server may include a group call control function (CF) for performing group call control, media control, and service authorization. Optionally, the MC server may include a participating function (PF) for signaling routing between the group call control function and the client (the MC server client described below), and addressing operations for the group call control function and / or the client.

[0091] The Mission Critical Service Client (MC Service Client / MC client) is an application-layer entity that corresponds to the Mission Critical Service Server. For example, the Mission Critical Service Client can be the MCPTT client 162 shown in Figure 1A. It can be implemented as a software program module on a terminal device (such as MCPTT UE 161), and can be used as a system application of the terminal operating system or as an aftermarket application. The Emergency Mission Service client is primarily responsible for processing application-layer transactions, including service registration, security authentication, authorization (achieved through interaction with the Emergency Mission Service server via the MCPTT-1 interface (also known as the reference point), call control (e.g., SIP message processing, achieving call creation, updating, and release through interaction with the Emergency Mission Service server via the MCPTT-1 interface), location management (achieved through interaction with the Emergency Mission Service server via the MCPTT-1 interface, such as receiving location reporting configurations from the server and reporting location information to the server), media processing (achieved through interaction with the Emergency Mission Service server via the MCPTT-7 / 8 interface, such as media reception / transmission, encoding / decoding, and receiving broadcast / multicast data on MCPTT-8), and broadcast / multicast control management of the mobile network (e.g., reporting broadcast / multicast reception quality and receiving broadcast / multicast announcement messages through interaction with the Emergency Mission Service server via the MCPTT-7 / 8 interface). It also includes the management of media transmission rights through interaction between its internal speakers and the speech control server.

[0092] A media control server is a media transmission control entity on the media plane and can reside within a service server (such as the MCPTT server 151 in Figure 1A). The media control server is primarily responsible for the transmission control of media uplink and / or downlink. For example, a media control server could be a talk control server 153 as shown in Figure 1A. Alternatively, a media control server could be a transmission control server in an MCVideo system. For ease of description, in the embodiments of this disclosure, the terms media control server, talk control server, and transmission control server can be used interchangeably, all referring to peer server entities that send or receive transmission control signaling to or from clients.

[0093] The speaking participant (speaking participant 164 in Figure 1A) can be used interchangeably with the transmission control participant. It is the peer entity of the media control server on the user side. It is also the media transmission control entity on the media plane and is mainly responsible for the transmission control of media uplink and / or downlink.

[0094] The media distribution function (media distribution function 152 in Figure 1A) is a logical entity located inside the business server (MCPTT server 151 in Figure 1A), which is mainly responsible for receiving uplink media data and sending downlink media data.

[0095] The media mixer (media mixer 163 in Figure 1A) is a peer entity located on the terminal side corresponding to the media distribution function, and is mainly responsible for processing media packets.

[0096] It should be noted that although the above mainly describes an EPS-based MCPTT system, the embodiments of this disclosure are not limited thereto. For example, the embodiments of this disclosure can be applied to MCData or MCVideo systems. For example, the embodiments of this disclosure can be applied to systems based on other mobile communication networks, such as MCPTT, MCData, or MCVideo systems based on 5G systems (5GS).

[0097] Instant group calls can be established using different methods. Figure 1B illustrates a group call establishment method based on a user list. The initiator 161-1 can provide a user list in the group call request, and then the server 151-1 can send a request to the client 161-2 in the user list to join the group call. Figure 1C illustrates a group call establishment method based on criteria. The initiator 161-1 can provide criteria (such as location information, like the geographical area range) in the group call request, and then the server 151-1 can select a client 161-3 that meets the criteria and send it a request to join the group call. In some cases, multiple group calls may exist, and how to merge at least two of these group calls is one of the problems that needs to be solved.

[0098] The embodiments of this disclosure provide a scheme for group call processing. In this scheme, participants from at least two group calls can be added to the same group call, thereby achieving the merging of at least two group calls. For ease of explanation, the merging of two group calls (the first group call and the second group call) is used as an example below; however, it is understood that the embodiments of this disclosure can be applied to the merging of more than two group calls. Based on the embodiments for merging two group calls described below, embodiments for merging more than two group calls obtained by those skilled in the art are still within the protection scope of this disclosure.

[0099] In the embodiments of this disclosure, different group calls can have different group call identification information, such as identifiers (IDs). A group call (e.g., group call x) with a specific group call identification information (e.g., IDx) can be modified, adjusted, or updated. For example, participants in group call x can be added or removed, the criteria for group call x can be modified or adjusted, the priority of group call x can be changed, the key of group call x can be replaced, and so on. However, during the process of modifying, adjusting, or updating group call x, its group call identification information (IDx) can remain unchanged. Optionally, the group call identification information can be a group call ID or a group ID, etc.

[0100] In the embodiments of this disclosure, merging two group calls can be equivalent to adding the participants of the two group calls to the same group call. The group call identification information of the same group call can be the same as the group call identification information of one of the two group calls being merged, or it can be different from the group call identification information of either of the two group calls being merged.

[0101] Figure 1D illustrates a schematic diagram of an example system 100D to which embodiments of the present disclosure can be applied. Servers 112, 110, and 114 are shown in Figure 1D, along with clients 120-11 to 120-1m, clients 120-21 to 120-2n, and client 130. For ease of description, it can be assumed that the participants in the first group call include clients 120-11 to 120-1m, and that the control function of the first group call is server 112; it can be assumed that the participants in the second group call include clients 120-21 to 120-2n, and that the control function of the second group call is server 114. Furthermore, in Figure 1D, server 110 is independent of servers 112 and 114, and client 130 is independent of clients 120-11 to 120-1m and clients 120-21 to 120-2n.

[0102] For example, servers 110, 112, and 114 can be the aforementioned emergency task service servers, such as the MCPTT server 151 shown in FIG1A. For example, servers 110, 112, and 114 can be understood as group call control functions (or simply control functions). Optionally, system 100D may further include participation functions (not shown in FIG1D). It should be noted that in some embodiments below, unless specifically indicated, the servers may include control functions and participation functions.

[0103] It should be noted that although the participants in the first group of calls (clients 120-21 to 120-2n) and the participants in the second group of calls (clients 120-21 to 120-2n) are different in Figure 1D, in some scenarios, a client may belong to both the first group of calls and the second group of calls. The embodiments of this disclosure are not limited to this.

[0104] It should be noted that although the control functions of the first group call (server 112) and the second group call (server 114) are shown to be different in Figure 1D, in some scenarios, the control functions of the first group call and the second group call can be the same, for example, server 112 and server 114 are implemented as the same server.

[0105] It should be noted that the embodiments of this disclosure do not limit the number of participants in the first group of calls (e.g., m) and the number of participants in the second group of calls (e.g., n). For example, m and n can be any positive integers, or any positive integers not less than 2.

[0106] It should be noted that the various entities (clients or servers) shown in Figure 1D can be logical entities, for example, implemented through software program code. It should also be noted that System 100D in Figure 1D is for convenience only in the following description; in real-world scenarios, it may include more or fewer servers / clients, and may include other entities not shown, etc.

[0107] Figure 2 illustrates a flowchart of an example process 200 for group call processing according to some embodiments of the present disclosure. Process 200 involves a server 201 and a client 202. Referring to Figure 1D, server 201 can be server 112, server 114, or server 110. Referring to Figure 1D, client 202 can be client 130, client 120-21 to 120-2n, or any of client 120-21 to 120-2n. Different embodiments will be described below. It should be noted that although some embodiments of the present disclosure are described in conjunction with system 100D of Figure 1D, the embodiments of the present disclosure are not limited thereto and can also be applied to other systems. Exemplarily, the various steps implemented by server 201 in process 200 can be implemented by a chip or the like associated with server 201, and the various steps implemented by client 202 in process 200 can be implemented by a chip or the like inside the terminal device where client 202 resides.

[0108] At position 210, client 202 obtains information about the first group of calls and the second group of calls.

[0109] At 220, client 202 sends first information to server 201 based on the information of the first group call and the information of the second group call. The first information is used to add the participants of the first group call and the participants of the second group call to the same group call.

[0110] Accordingly, at 220, server 201 can receive the first information from client 202.

[0111] At point 230, server 201, based on the first information, adds the participants of the first group call and the participants of the second group call to the same group call.

[0112] In embodiments of this disclosure, client 202 can be an authorized user. Exemplarily, client 202 can be granted processing permissions, including the ability to trigger the merging of at least two group calls. As an example, client 202 can be a participant in both the first and second group calls. For instance, client 202 can be one of the participants in both the first and second group calls.

[0113] In some embodiments, it can be assumed that a first group call is in progress, and the participants in the first group call include clients 120-11 to 120-1m. It can also be assumed that a second group call is in progress, and the participants in the second group call include clients 120-21 to 120-2n. In some embodiments, client 202 can obtain information about the first group call from the control function of the first group call (e.g., server 112) and information about the second group call from the control function of the second group call (e.g., server 114). For example, client 202 can obtain information about the first and second group calls through a subscription. For example, if client 202 has pre-subscribed, then server 112 / 114 can provide client 202 with information about the first / second group call based on the subscription information. For example, client 202 can send a subscription request to server 112 / 114, which may include identification information for the first / second group call, and then server 112 / 114 can provide client 202 with information about the first / second group call based on the subscription request. Optionally, if the information about the first (or second) group call...

[0114] For example, client 202 can request information about the first call group and the second call group.

[0115] Through embodiments of this disclosure, participants in a first group call and participants in a second group call can be added to the same group call; for example, the "same group call" can be referred to as the target group call. Exemplarily, participants in both the first and second group calls can be added to the target group call through a merging or combining operation. Optionally, the target group call can be an updated second (or first) group call; or it can be a third group call that is different from both the first and second group calls. Exemplarily, server 201 can be the control function (or control feature) of the target group call.

[0116] In some embodiments of this disclosure, the first information at 220 may include or be implemented as group call update information. In some examples, taking the update of a second group call as an example, FIG3A illustrates a schematic diagram of an example process 300A for determining an update of a second group call according to some embodiments of this disclosure. In process 300A, it can be assumed that servers 112 and 114 include control functions. Process 300A involves server 112, server 114, client 202, and participation function 301. It should be noted that although the control function and participation function are interpreted as separate entities in embodiments of this disclosure, in other scenarios, the control function and participation function may also be implemented as a single logical entity (e.g., an emergency task service server), and this disclosure is not limiting in this regard.

[0117] At point 310, client 202 sends a request message to server 112 to request information for the first group of calls, and client 202 sends a request message to server 114 to request information for the second group of calls.

[0118] Specifically, client 202 can send request information to server 112 and server 114 via participation function 301. In some implementations, this request information is used to request information for the first group of calls and the second group of calls, respectively. It should be understood that this request information can be implemented as a first request information for requesting information for the first group of calls and a second request information for requesting information for the second group of calls, and this disclosure is not limited thereto.

[0119] At position 320, server 112 can send the information of the first call to client 202.

[0120] At position 330, server 114 can send the information of the second call to client 202.

[0121] Specifically, server 112 can send the first set of call information to client via participation function 301; server 114 can send the second set of call information to client via participation function 301.

[0122] Optionally, in some examples, participation function 301 can obtain information about the first group of calls from server 112 and information about the second group of calls from server 114. It is understood that this operation can be implemented as an operation between service entities, and this operation may be invisible to client 202. Optionally, in some examples, participation function 301 can send response information to client 202. In some implementations, this response information may be referred to as response information, and the response information may include information about the first group of calls and information about the second group of calls. It should be understood that the response information may be implemented as first response information for providing information about the first group of calls and second response information for providing information about the second group of calls, and this disclosure is not limited thereto.

[0123] In embodiments of this disclosure, the information of a group call (such as a first group call or a second group call) may include one or more of the following: group call identification information, group call establishment method, group call priority, list of participants in the group call, criteria for group call establishment, number of participants in the group call, information of the group call initiator, security level of the group call, broadcasting method of the group call, hang time of the group call, or index of the key used by the group call, etc.

[0124] At 350, client 202 can determine to update the second call by adding participants from the first call to the second call.

[0125] For example, the merging method or strategy for the first group call and the second group call can be: adding the participants of the first group call to the second group call to update the second group call.

[0126] In some embodiments, client 202 may determine to add participants from the first group call to the second group call based on information from the first group call and information from the second group call. For example, client 202 may determine to add participants from the first group call to the second group call based on at least one of the following: (a1) the number of participants in the first group call and the number of participants in the second group call; (a2) the priority of the first group call and the priority of the second group call; (a3) ​​the establishment method of the first group call and the establishment method of the second group call; (a4) user preference information corresponding to client 202; or (a5) the local policy of client 202.

[0127] For example, if at least one of the following conditions is met, client 202 may determine to add participants from the first call group to the second call group: the number of participants in the first call group is less than the number of participants in the second call group; the priority of the first call group is lower than the priority of the second call group; the first call group is established based on a user list and the second call group is established based on a criterion; or the first call group is established based on a first criterion, the second call group is established based on a second criterion, and the area corresponding to the first criterion is smaller than the area corresponding to the second criterion.

[0128] For example, user preference information or local policies can instruct participants from a group call established earlier to be added to a group call established later. For instance, if the first group call was established earlier than the second group call, client 202 can determine to add participants from the first group call to the second group call.

[0129] For example, user preference information or local policies can instruct participants in a group call with a longer hang time to be added to a group call with a shorter hang time. For instance, if the hang time of the first group call is greater than the hang time of the second group call, client 202 can determine to add participants from the first group call to the second group call.

[0130] Additionally or optionally, client 202 may also determine one or more of the following information for the updated second call: key index information, priority, security level, broadcast method, or hang time.

[0131] For example, the updated key for the second group call can be different from both the key for the first group call and the key for the second group call before the update. For instance, the index of the key for the first group call and the index of the key for the second group call before the update can be different. Optionally, the key can be indexed by group IDs; for example, different group IDs can be mapped to different keys. Optionally, a one-to-one correspondence between multiple group IDs and multiple keys can be predefined or pre-configured. The client 202 can select one of the multiple keys as the key for the updated second group call and use the group ID corresponding to the selected key as the key index for the updated second group call.

[0132] For example, the updated priority of the second call group can be one of the priorities of the first call group and the previous priority of the second call group, such as the higher of the two. For example, the updated priority of the second call group can be different from both the priority of the first call group and the previous priority of the second call group. For example, client 202 can re-specify this priority.

[0133] For example, the updated security level of the second group call can be one of the security levels of the first group call and the previous security level of the second group call, such as the higher of the two. For example, the updated security level of the second group call can be different from both the security level of the first group call and the security level of the previous second group call. For example, client 202 can re-specify this security level.

[0134] For example, the broadcast method of the updated second group call can be one of the broadcast methods of the first group call and the original broadcast method of the second group call. For instance, if the broadcast method of the first group call or the original broadcast method of the second group call was non-broadcast, then the broadcast method of the updated second group call can also be non-broadcast. Conversely, if both the broadcast method of the first group call and the original broadcast method of the second group call were broadcast, then the broadcast method of the updated second group call can be broadcast.

[0135] For example, the hang time of the updated second group call can be one of the hang time of the first group call and the hang time of the second group call before the update, such as the longer of the two. For example, the hang time of the updated second group call can be different from both the hang time of the first group call and the hang time of the second group call before the update. For example, client 202 can re-specify this hang time, such as the average or weighted sum of the hang time of the first group call and the hang time of the second group call before the update. For example, the weights used to determine the weighted sum can be determined based on the number of participants in the group call.

[0136] At position 360, client 202 sends the first message to server 114.

[0137] In some implementations, the first information can be sent to the server 114 via participation function 301. The first information can be implemented as group call update information for updating the second group call. The first information may include identification information of the second group call. For example, specific fields of the group call update information can carry the identification information of the second group call to indicate that the group call update information is used to indicate that the second group call is being updated. In this way, sending the group call update information to the control function of the second group call (i.e., server 114) facilitates the server 114 in updating the second group call.

[0138] Optionally, the group call update information may also include indication information of the merging method. For example, the indication information indicates that the second group call is updated by adding participants from the first group call to the second group call. Exemplarily, the group call update information may indicate that the second group call is updated by adding participants from the first group call to the second group call. Optionally, the group call update information may also include at least one of the following: identification information of the first group call, a list of participants in the first group call, and a first criterion for the first group call. Optionally, the group call update information may also include information about the first group call, such as the method of establishing the first group call (based on a user list or based on criteria). Optionally, if the first group call is established based on a first user list, the group call update information may also include a list of participants in the first group call. Optionally, if the first group call is established based on a first criterion, the group call update information may also include the first criterion. For example, the group call update information may include the first criterion at the time of establishment of the first group call, as well as a list of participants added after establishment. For example, the group call update information may include identification information of the first group call, so that the server 114 can determine the list of participants and / or the first criterion of the first group call based on the identification information of the first group call.

[0139] Optionally, the group call update information may also include one or more of the following information from the updated second group call: key index information, priority, security level, broadcast method, or hang time.

[0140] In this way, client 202 can make a decision based on the information of the first group call and the information of the second group call, and determine to update the second group call by adding the participants of the first group call to the second group call.

[0141] In some embodiments of this disclosure, the first information at 220 may include or be implemented as group call update information. In some examples, taking the update of a second group call as an example, FIG3B illustrates a schematic diagram of an example process 300B for determining an update of a second group call according to some embodiments of this disclosure. In process 300B, it can be assumed that servers 112 and 114 include control functions. Process 300B involves server 112, server 114, client 202, and participation function 301.

[0142] At point 311, client 202 can obtain information about multiple group calls.

[0143] In some implementations, client 202 can obtain information about multiple group calls through subscription, where the multiple group calls include a first group call and a second group call. The group call information obtained through subscription may include the group call's identification information. Optionally, the group call information may also include the group call's establishment method.

[0144] At point 321, client 202 can determine to merge the first group call and the second group call based on information from multiple group calls.

[0145] In some implementations, client 202 can determine / select the first group call and the second group call from multiple group calls. For example, client 202 can select the first group call and the second group call based on the user's input information (e.g., based on human-computer interaction, selection actions from the user, etc.).

[0146] Additionally or optionally, client 202 may further obtain more detailed or additional information about the first group call and the second group call. Exemplarily, this information can be obtained through the process shown in 310 to 340 of Figure 3A. Optionally, the information about the group call (i.e., the first or second group call) may include one or more of the following: group call identification information, group call establishment method, group call priority, list of participants in the group call, criteria for group call establishment, number of participants in the group call, information about the group call initiator, security level of the group call, broadcast method of the group call, hang time of the group call, or index of the key used in the group call, etc.

[0147] For example, client 202 may determine that the first group of calls and the second group of calls should be merged, but does not determine the merging method or merging strategy, that is, it does not determine whether to add the participants of the first group of calls to the second group of calls or to add the participants of the second group of calls to the first group of calls.

[0148] Additionally or optionally, client 202 may also determine one or more of the following information for the updated group call: key index information, priority, security level, broadcast method, or hang time. Specifically, an embodiment in which client 202 determines this information can refer to the foregoing description in conjunction with FIG3A of determining the information for the updated second group call, the difference being that at 321 in FIG3B, it is not yet determined whether the updated group call is the updated first group call or the updated second group call.

[0149] At point 331, client 202 sends first information, which can be implemented as group call update information, and the first information includes the identification information of the first group call and the identification information of the second group call.

[0150] In some implementations, the initial information may be sent to server 114 via participation function 301. For example, a specific field of the group call update information may be configured to carry identification information of the updated group call; in this example, this specific field may be empty.

[0151] For example, the group call update information includes information for triggering the merging of the first group call and the second group call. For instance, the group call update information may include indication information (such as an indicator or tag) for triggering or requesting the merging of the first group call and the second group call.

[0152] Optionally, the group call update information may also include merging instructions. For example, the instructions may indicate: merge the first group call and the second group call. Or, the instructions may indicate: add a participant from one of the first and second group calls to the other group call.

[0153] Optionally, the group call update information may also include information about the first group call, such as one or more of the following: the identification information of the first group call, the establishment method of the first group call, the priority of the first group call, the list of participants in the first group call, the criteria for establishing the first group call, the number of participants in the first group call, the information of the initiator of the first group call, the security level of the first group call, the broadcast method of the first group call, the hang time of the first group call, or the index of the key used by the first group call, etc.

[0154] Optionally, the group call update information may also include information about the second group call, such as one or more of the following: the identification information of the second group call, the establishment method of the second group call, the priority of the second group call, the list of participants in the second group call, the criteria for establishing the second group call, the number of participants in the second group call, the information of the initiator of the second group call, the security level of the second group call, the broadcast method of the second group call, the hang time of the second group call, or the index of the key used by the second group call, etc.

[0155] Optionally, the group call update information may also include one or more of the following information of the updated group call: key index, priority, security level, broadcast method, or hang time.

[0156] At 341, server 114 determines to update the second call by adding participants from the first call to the second call.

[0157] In some implementations, server 114 can determine the merging method or merging strategy as follows: add participants from the first group of calls to the second group of calls to update the second group of calls.

[0158] In some embodiments, server 114 can determine whether to add participants from the first group call to the second group call based on information from the first group call and information from the second group call. Optionally, server 114, as the control function of the second group call, already knows the information of the second group call. Optionally, the first information includes information from the first group call, and server 114 can obtain the information from the first information. Optionally, server 114 can obtain the information from the control function of the first group call (i.e., server 112) based on the identification information of the first group call.

[0159] For example, server 114 may determine to add participants of the first call group to the second call group based on at least one of the following: (b1) the number of participants in the first call group and the number of participants in the second call group; (b2) the priority of the first call group and the priority of the second call group; (b3) the establishment method of the first call group and the establishment method of the second call group; or (b4) the local policy of server 114.

[0160] For example, server 114 may determine to add participants from the first call group to the second call group if at least one of the following conditions is met: the number of participants in the first call group is less than the number of participants in the second call group; the priority of the first call group is lower than the priority of the second call group; the first call group is established based on a user list and the second call group is established based on a criterion; or the first call group is established based on a first criterion, the second call group is established based on a second criterion, and the area corresponding to the first criterion is smaller than the area corresponding to the second criterion.

[0161] For example, a local policy could instruct participants from a group call established earlier to be added to a group call established later. For instance, if the establishment time of the first group call is earlier than that of the second group call, server 114 can determine to add participants from the first group call to the second group call. Similarly, a local policy could instruct participants from a group call with a longer hang time to be added to a group call with a shorter hang time. For instance, if the hang time of the first group call is greater than that of the second group call, server 114 can determine to add participants from the first group call to the second group call.

[0162] Optionally, in some implementations, after the participation function 301 receives the group call update information from the client 202, the participation function 301 can send the group call update information to both the control function of the first group call (server 112) and the control function of the second group call (server 114). Subsequently, servers 112 and 114 can use the same strategy to determine the merging method. As shown in the figure, at 351, the participation function 301 can send the group call update information to server 112. Optionally, server 112 can determine the merging method as adding the participants of the first group call to the second group call based on the information of the first and second group calls. Then, at 352, server 112 can ignore (or delete, discard) the group call update information from the participation function 301.

[0163] Optionally, in some implementations, after the participation function 301 receives the group call update information from the client 202, the participation function 301 can send the group call update information to the control function of the first group call (server 112). If the server 112 determines that the merging method is to add the participants of the first group call to the second group call, then the server 112 can send a rejection update message or a negative confirmation message, etc., to the participation function 301. Then the participation function 301 sends the group call update information to the server 114.

[0164] Optionally, in some implementations, after the participation function 301 receives the group call update information from the client 202, the participation function 301 can send the group call update information to the control function of the second group call (server 114). If the server 114 determines that the merging method is to add the participants of the first group call to the second group call, then the server 114 can send an update confirmation message or a positive confirmation message, etc., to the participation function 301. Then the participation function 301 may stop sending the group call update information to the server 112.

[0165] In this way, client 202 can send the merged instruction information to the server, which then makes a decision based on the information from the first and second call groups, determining to update the second call group by adding the participants from the first call group to the second call group. This reduces the operations at client 202 and fully utilizes the server's processing power.

[0166] It should be understood that although the merging methods shown in Figures 3A and 3B are both to update the second group of calls by adding the participants of the first group of calls to the second group of calls, the distinction between "first group of calls" and "second group of calls" in this disclosure is only illustrative. For example, "first" and "second" can be interchanged.

[0167] Furthermore, following the process shown in Figure 3A or Figure 3B, server 114 can merge the first and second group calls by updating the second group call. Figure 4 illustrates a schematic diagram of an example process 400 for merging group calls according to some embodiments of this disclosure. Process 400 involves server 112, server 114, client 202, and participants 401 of the first group call (group call 1) and participants 402 of the second group call (group call 2). Exemplarily, prior to 410, server 114 has obtained information about the first group call, including but not limited to the identification information of the first group call, the establishment method of the first group call, the user list of the first group call, and the first criteria of the first group call.

[0168] At 410, server 114 updates the user list or criteria for the second group of calls.

[0169] In some examples, if both the first and second call groups are based on user lists, the union of the user lists of the first and second call groups can be used as the updated user list for the second call group. In some examples, if the first call group is based on a first criterion and the second call group is based on a second criterion, the union of the first and second criterions can be used as the updated criterion for the second call group. In some examples, if the first call group is based on a user list and the second call group is based on a criterion, the updated criterion for the second call group can be the criterion for the second call group, and each participant in the user list of the first call group (e.g., participants who do not meet the criterion for the second call group) is labeled or marked, indicating that the corresponding participant is not bound by the criterion. In some examples, if the second call group is based on a user list and the first call group is based on a criterion, the updated criterion for the second call group can be the criterion for the first call group, and each participant in the user list of the second call group (e.g., participants who do not meet the criterion for the first call group) is labeled or marked, indicating that the corresponding participant is not bound by the criterion. In some examples, if the first group call is established based on a first criterion and includes participants added after its establishment via a user list, and the second group call is established based on a second criterion, then the union of the first and second criters can be used as the criterion for the updated second group call. Furthermore, participants added later to the first group call are tagged or marked, indicating that the corresponding participant is not bound by the criterion. It is understood that for combinations of the above examples, those skilled in the art can determine the user list and / or criterion for the updated second group call using the group calls from the above examples; these embodiments of this disclosure will not be listed exhaustively.

[0170] Additionally or optionally, server 114 may also determine one or more of the following information for the updated second group call: key index, priority, security level, broadcast method, or hang time. For example, the first information (group call update information) may include information for the updated second group call. For example, server 114 may determine one or more of the following information for the updated second group call based on information from the first and second group calls: key index, priority, security level, broadcast method, or hang time. Optionally, the method by which server 114 determines the information for the updated second group call is similar to the embodiment described above where client 202 determines the information for the updated second group call.

[0171] For example, the updated key for the second group call can be different from both the key for the first group call and the key for the second group call before the update. For instance, the key for the first group call and the key for the second group call before the update can be different. Optionally, the key index can be indexed using group IDs; for example, different group IDs can be mapped to different keys. Optionally, a one-to-one correspondence between multiple group IDs (key indices) and multiple keys can be predefined or pre-configured. Server 114 can select one of the multiple keys as the key for the updated second group call and use the group ID corresponding to the selected key as the index of the key for the updated second group call. For example, server 114 can also determine that the key for the second group call remains unchanged, that is, the index of the key for the updated second group call is the same as the index of the key for the second group call before the update.

[0172] For example, the priority of the updated second call group can be one of the priorities of the first call group and the previous second call group, or the higher of the two. For example, the priority of the updated second call group can be different from both the priority of the first call group and the previous second call group. For instance, server 114 can reassign this priority.

[0173] For example, the updated security level of the second group of calls can be one of the security levels of the first group of calls and the security level of the second group of calls before the update, such as the higher of the two. For example, the updated security level of the second group of calls can be different from both the security level of the first group of calls and the security level of the second group of calls before the update. For example, server 114 can re-specify this security level.

[0174] For example, the broadcast method of the updated second group call can be one of the broadcast methods of the first group call and the original broadcast method of the second group call. For instance, if the broadcast method of the first group call or the original broadcast method of the second group call was non-broadcast, then the broadcast method of the updated second group call can also be non-broadcast. Conversely, if both the broadcast method of the first group call and the original broadcast method of the second group call were broadcast, then the broadcast method of the updated second group call can be broadcast.

[0175] For example, the hang time of the updated second group call can be one of the hang time of the first group call and the hang time of the second group call before the update, such as the longer of the two. For example, the hang time of the updated second group call can be different from both the hang time of the first group call and the hang time of the second group call before the update. For example, server 114 can re-specify this hang time, such as the average or weighted sum of the hang time of the first group call and the hang time of the second group call before the update. For example, the weights used to determine the weighted sum can be determined based on the number of participants in the group call.

[0176] At 420, server 114 sends a group call request message to participant 401 of the first group call, which includes the identification information of the second group call.

[0177] In some examples, the group call request information is used to request participant 401 from the first group call to join the second group call. Optionally, the group call request information may include updated key information for the second group call. As previously mentioned, the updated key for the second group call is the same as the key for the previous group call, or the updated key for the second group call is different from the key for the previous group call.

[0178] In some embodiments, server 114 may send group call request information to participants who meet the user list / criteria but are not yet in the second group call, based on the user list / criteria updated at 410. For example, server 114 may obtain the client ID of group call participant 401 and send group call request information to group call participant 401 based on the client ID.

[0179] Optionally, participant 401 in group call 1 in Figure 4 can be one of the participants in the first group call but not in the second group call. Optionally, participant 401 in group call 1 can present a prompt message to its corresponding user. Optionally, participant 401 in group call 1 can send a response message to server 114, such as indicating whether to accept or reject the group call request.

[0180] As shown in the diagram, additionally or optionally, at point 430, server 114 may send group call key information to participant 402 of the second group call. For example, if the updated key for the second group call is different from the original key, then server 114 may send the updated key information to participant 402 of the second group call. For instance, if the updated key for the second group call is K2, then after point 430, participants in the updated second group call can use key K2 to communicate.

[0181] In this way, participants from the first call group are added to the second call group, merging the first and second call groups. As shown in the diagram, the first call group can also be released via 441, 442, or 443. In some implementations, server 114 can be the control function for the first call group; that is, server 112 and server 114 share the same control function, in which case the first call group can be released via 441. In some implementations, server 114 and server 112 are different entities, in which case the first call group can be released via 442 or 443.

[0182] In some embodiments, server 114 may send a second message at 441 to participant 401 of the first group call to release the first group call.

[0183] In some embodiments, at 442-1, server 114 may send a second message to server 112 to release the first group of calls. At 442-2, server 112 may send a release message to participant 401 of the first group of calls to release the first group of calls.

[0184] In some embodiments, at 443-1, server 114 may send release information to client 202 to release the first group call. At 443-2, client 202 sends second information to server 112 to release the first group call. At 443-3, server 112 may send release information to participant 401 of the first group call to release the first group call. Optionally, the second information at 443-2 may be sent to server 112 via a participation function.

[0185] For example, the second information and / or release information in 441, 442, or 443 may include identification information of the first group call. Optionally, the second information and / or release information may include a release reason, such as a release reason indicating group call merging.

[0186] It should be noted that process 300A in Figure 3A or process 300B in Figure 3B can be understood as a specific implementation of 210 and 220 in Figure 2, and process 400 in Figure 4 can be understood as a specific implementation of 230 in Figure 2. For example, server 201 in Figure 2 can be the control function of the second group call, and server 114. It should be noted that the embodiments described in conjunction with Figures 3A to 4 are for illustrative purposes only and are not intended to limit the scope of this disclosure. For example, some operations (or steps) shown in the figures may be omitted, removed, or combined. For example, one or more additional operations (or steps) may be further included in the figures. For example, the order of operations (or steps) shown in the figures may be rearranged or adjusted.

[0187] By combining the descriptions in Figures 3A to 4, participants in the first group call can be added to the second group call, the second group call updated, and the first group call released, thus achieving the merging of the first and second group calls. In some examples, the client can determine the merging method, giving the client more initiative in group call merging and improving user experience. In other examples, the server can determine the merging method, which reduces the processing burden and implementation complexity on the client side, reduces unnecessary transmission, dissemination, or exchange of group call information, and improves the security of group call information.

[0188] In some embodiments of this disclosure, the first information at 220 may include or be implemented as group call establishment information. Figure 5A illustrates a schematic diagram of an example process 500A for determining the establishment of a group call according to some embodiments of this disclosure. Process 500A involves server 112, server 1100, server 114, and client 202.

[0189] At point 511, client 202 obtains information about the first group of calls and the second group of calls.

[0190] For example, the information of the first group of calls and the information of the second group of calls can be obtained by request (see 310 to 340 in Figure 3A) or by subscription. Specific implementation details can be found in the foregoing embodiments, and will not be repeated here for the sake of brevity.

[0191] In some examples, the information of a group call (such as the first group call or the second group call) may include one or more of the following: group call identification information, how the group call is established, the priority of the group call, the list of participants in the group call, the criteria for establishing the group call, the security level of the group call, the broadcast method of the group call, the hang time of the group call, or the index of the key used by the group call, etc.

[0192] Optionally, at 512, client 202 may determine to add participants from the first call group and participants from the second call group to a new call group (hereinafter referred to as the third call group for ease of description) to merge the first and second calls group. In some implementations, client 202 may determine to establish the third call group based on a merging strategy and / or based on information from the first and second calls group.

[0193] Additionally or optionally, client 202 may also determine one or more of the following information for the third call: identification information, key index, priority, security level, broadcast method, hang time, or session description protocol (SDP) information.

[0194] For example, client 202 can set or specify identification information for the third call group, such as ID3. It is understood that the identification information for the third call group is different from the identification information for the first call group (such as ID1) and also different from the identification information for the second call group (such as ID2).

[0195] For example, the key for the third call group can be different from the key for the first call group and also different from the key for the second call group; for instance, the key for the first call group and the key for the second call group can be different. Optionally, the key index can be indexed using a group ID; for example, different group IDs can be mapped to different keys. Optionally, a one-to-one correspondence between multiple group IDs and multiple keys can be predefined or preconfigured. The client 202 can select one of the multiple keys as the key for the third call group and use the group ID corresponding to the selected key as the index of the key for the third call group.

[0196] For example, the priority of the third call group can be one of the priorities of the first and second calls, such as the higher of the two. For example, the priority of the third call group can be different from both the priority of the first and second calls. For example, the client can reassign this priority using a 202 redirect.

[0197] For example, the security level of the third call group can be one of the security levels of the first and second calls group, such as the higher of the two. For example, the security level of the third call group can be different from both the security levels of the first and second calls group. For example, client 202 can re-specify this security level.

[0198] For example, the broadcast method of the third group call can be one of the broadcast methods of the first group call and the second group call. For example, if the broadcast method of the first group call or the broadcast method of the second group call is non-broadcast, then the broadcast method of the third group call can be non-broadcast. For example, if the broadcast methods of the first group call and the broadcast methods of the second group call are both broadcast, then the broadcast method of the third group call can be broadcast.

[0199] For example, the hang time for the third call group can be one of the hang time for the first call group and the second call group, such as the longer of the two. For example, the hang time for the third call group can be different from both the hang time for the first and second call groups. For example, client 202 can re-specify this hang time, such as the average or weighted sum of the hang times for the first and second call groups. For example, the weights used to determine the weighted sum can be determined based on the number of participants in the call group.

[0200] For example, the SDP information for the third group call may include media description information for the third group call, such as codec information and media direction. For example, the media direction can be one of the following: receive only, send only, sendrecv, inactive, etc.

[0201] At point 513, client 202 sends first information to server 110, the first information including or being implemented as group call establishment information.

[0202] It is understood that the first information can be sent via the participation function. For example, the group call establishment information includes the identification information of the first group call and the identification information of the second group call. Optionally, the group call establishment information can also be replaced with group call combine information or group call merge information. Optionally, server 110 can resolve the corresponding control function, i.e., server 112, based on the identification information of the first group call in the group call establishment information. Optionally, server 110 can resolve the corresponding control function, i.e., server 114, based on the identification information of the second group call in the group call establishment information.

[0203] Optionally, the group call establishment information may include information about the first group call, such as the establishment method of the first group call, the user list of the first group call, and the first criteria of the first group call. Optionally, the group call establishment information may include information about the second group call, such as the establishment method of the second group call, the user list of the second group call, and the second criteria of the second group call.

[0204] In some examples, servers 110, 112, and 114 are the same server, so server 110 already knows the information for the first and second call groups. In some examples, servers 110 and 112 are the same server, but server 114 is different from server 110. In this case, server 110 already knows the information for the first call group, and can obtain the information for the second call group from the first information or from server 114 (as shown in 515 of Figure 5A). In some examples, servers 110 and 114 are the same server, but server 112 is different from server 110. In this case, server 110 already knows the information for the second call group, and can obtain the information for the first call group from the first information or from server 112 (as shown in 514 of Figure 5A). In some examples, server 110 is different from both server 112 and server 114. In this case, server 110 can obtain information about the first group of calls from the first information or from server 112 (as shown in 514 of Figure 5A), and can also obtain information about the second group of calls from the first information or from server 114 (as shown in 515 of Figure 5A). In some examples, server 112 and server 114 are the same server, and server 110 is different from servers 112 / 114. In this case, server 110 can obtain information about the first group of calls equal to or equal to the information about the second group of calls from the first information, or it can obtain information about the first group of calls and the second group of calls from servers 112 / 114.

[0205] Optionally, the group call setup information may also include one or more of the following information for the third group call: identification information, key index, priority, security level, broadcast method, or hang time.

[0206] For example, after the process shown in FIG5A, server 110 can establish a third group call and add the participants of the first group call and the participants of the second group call to the third group call. FIG5B shows a schematic diagram of an example process 500B of merging group calls according to some embodiments of the present disclosure. Process 500B involves server 201, client 202, and participants 401 of the first group call (group call 1) and participants 402 of the second group call (group call 2). For example, prior to 510, server 201 has obtained information about the first / second group call, including but not limited to the identification information of the first / second group call, the establishment method of the first / second group call, the user list of the first / second group call, the criteria of the first / second group call, etc. For example, server 201 can determine the identification information of the third group call for establishing the third group call. Optionally, the identification information of the third group call can be included in the first information (group call establishment information). Optionally, if the first information (group call setup information) does not include the identification information of the third group call, or if the server 201 can refuse to use the identification information included in the first information (group call setup information), then the server 201 can specify or assign the identification information of the third group call. For example, the identification information of the third group call is represented as ID3.

[0207] At 510, server 201 determines the list of users or criteria for the third group of calls.

[0208] Specifically, server 201 determines the user list / criteria for the third group of calls based on the information from the first group of calls and the information from the second group of calls.

[0209] In some examples, if the first call group is based on a user list and the second call group is also based on a user list, then the union of the user lists of the first and second calls can be used as the user list of the third call group.

[0210] In some examples, if the first set of calls is based on the first criterion and the second set of calls is based on the second criterion, then the union of the first and second criters can be used as the criterion for the third set of calls.

[0211] In some examples, if the first call group is based on a user list and the second call group is based on criteria, then the criteria for the third call group can be the criteria for the second call group, and each participant in the user list of the first call group (such as participants who do not meet the criteria of the second call group) is labeled or marked, indicating that the corresponding participant is not bound by the criteria.

[0212] In some examples, if the second call group is based on a user list and the first call group is based on criteria, then the criteria for the third call group can be the criteria for the first call group, and each participant in the user list of the second call group (such as participants who do not meet the criteria of the first call group) is labeled or marked, indicating that the corresponding participant is not bound by the criteria.

[0213] In some examples, if the first call group is established based on the first criterion and also includes participants added after its establishment via a user list (such as one or more participants added by the initiator of the first call group who do not meet the first criterion), and the second call group is established based on the second criterion, then the union of the first and second criters can be used as the criterion for the third call group, and participants who joined the first call group later are labeled or marked with a tag indicating that the corresponding participant is not bound by the criterion.

[0214] It is understood that, for some combinations of the above examples, those skilled in the art can determine the user list and / or criteria for the third group call through the group call in the above examples, and this disclosure will not list them one by one.

[0215] Additionally or optionally, server 201 may also determine one or more of the following information for the third group call: key index, priority, security level, broadcast method, or hang time. For example, the first information (group call establishment information) may include information about the third group call. For example, server 201 may determine one or more of the following information for the third group call based on the information of the first and second group calls: key index, priority, security level, broadcast method, or hang time. Optionally, the way server 201 determines the information of the third group call is similar to the embodiment described above where client 202 determines the information of the third group call, as described in conjunction with the portion of Figure 5A; for brevity, it will not be repeated here.

[0216] At point 520, server 201 sends a group call request to participant 401 of the first group call, which includes the identification information of the third group call.

[0217] At point 530, server 201 sends a group call request to participant 402 of the second group call, which includes the identification information of the third group call.

[0218] Optionally, the group call request information at 520 and 530 can be replaced with combined group call request information or merged group call request information, which is not limited in this disclosure. In some examples, the group call request information at 520 and 530 is used to request participant 401 of the first group call and participant 402 of the second group call to join the third group call. Exemplarily, the group call request information may also include key information for the third group call.

[0219] In some embodiments, server 201 may send group call request information to participants that meet the user list / criteria of the third group call determined at 510. For example, server 201 may obtain the client ID of group call participant 401 and the client ID of group call participant 402, and send group call request information to both group call participant 401 and group call participant 402 based on these client IDs.

[0220] Optionally, participant 401 of group call 1 may present a prompt message to their corresponding user. Optionally, participant 401 of group call 1 may send a response message to server 201, such as indicating whether to accept or reject the group call request. Optionally, participant 402 of group call 2 may present a prompt message to their corresponding user. Optionally, participant 402 of group call 2 may send a response message to server 201, such as indicating whether to accept or reject the group call request.

[0221] In this way, participants from the first and second call groups are added to the third call group, thus merging the first and second call groups. Optionally, the third call group can be understood as a new call group relative to the first and second call groups. Optionally, the first and second call groups can be understood as the original call groups, the call groups before the merger, or the old call groups, etc., relative to the third call group.

[0222] As shown in the figure, the first call group can be released at position 540, and the second call group can be released at position 550. In some embodiments, the first and second calls can be released after the third call group is successfully established, such as after the control session of the third call group is established or after the media plane of the third call group is established. Exemplarily, the method of releasing the first / second call group can refer to the embodiment of releasing the first call group in Figure 4 above.

[0223] In some examples, if server 201 is server 112, the first call group can be released using a procedure similar to 441. In some examples, if server 201 is different from server 112, the first call group can be released using a procedure similar to 442 or 443.

[0224] In some examples, if server 201 is server 114, then similar to 441, server 201 can send a third message to group call participant 402 to release the second group call. In some examples, if server 201 is different from server 114, then similar to 442, server 201 can send a third message to server 114 to release the second group call; for example, server 114 can send a release message to group call participant 402. In some examples, if server 201 is different from server 114, then similar to 443, server 201 can send a third message to client 202 to release the second group call; client 202 can send a third message to server 114 to release the second group call; for example, server 114 can send a release message to group call participant 402. Optionally, the third message and release message used to release the second group call may include the identification information of the second group call. Optionally, the third message / release message may also include a release reason, such as group call merging or a participant being added to a new group call.

[0225] It should be noted that process 500A in Figure 5A can be understood as a specific implementation of 210 and 220 in Figure 2, and process 500B in Figure 5B can be understood as a specific implementation of 230 in Figure 2. For example, server 201 in Figure 2 can be server 110.

[0226] Exemplarily, following the process shown in FIG5A, server 110 may establish a third group call and add participants from the first group call and the second group call to the third group call. FIG5C shows a schematic diagram of an example process 500C for merging group calls according to some embodiments of the present disclosure. Process 500C involves server 110, server 112, server 114, client 202, and participants 401 of the first group call (group call 1) and participants 402 of the second group call (group call 2). Exemplarily, server 110 may determine identification information for the third group call for establishing the third group call. Optionally, the identification information for the third group call may be included in the first information (group call establishment information). Optionally, the first information (group call establishment information) may not include the identification information for the third group call, or server 110 may refuse to use the identification information included in the first information (group call establishment information), in which case server 110 may specify or assign the identification information for the third group call. For example, the identification information for the third group call may be represented as ID3. Alternatively, the third group of calls may also be referred to as a temporary group of calls.

[0227] At point 551, server 110 sends a fourth message to server 112, which is used to add the participants of the first group of calls to the third group of calls.

[0228] For example, the fourth information may include the identification information of the first group call and the identification information of the third group call. For instance, the fourth information may include group call establishment request information. Optionally, the fourth information may also include the identification information of the second group call. Optionally, the fourth information may also include the key information of the third group call, the SDP information of the third group call, etc.

[0229] At point 552, optionally, server 112 sends a call merging notification to participant 401 of the first call group, the notification indicating that the first call group has been added to the third call group (or participant 401 of the first call group has been added to the third call group).

[0230] For example, the notification information may include identification information of the third group call. For instance, the notification information may include group call update information, such as any of the following: SIP INVITE, SIP re-INVITE, SIP INFO, SIP REFER, SIP MESSAGE, etc. Optionally, the notification information may also include index information of the third group call key, SDP information of the third group call, etc.

[0231] At point 553, optionally, participant 401 of the first group of calls sends a response to the call merging notification information to server 112.

[0232] For example, the response information can be an acknowledgment (ACK). Optionally, the response information from participant 401 of the first group call may include an SDP answer, media description information, etc., wherein the media description information may include encoding / decoding information and / or media direction information.

[0233] It should be noted that although 552 and 553 are described in Figure 5C using participant 401 of the first group of calls as an example, participants in the first group of calls may not all receive the join request information at the same time, nor may they all respond with join response information.

[0234] At 554, server 112 sends a response message corresponding to the fourth message to server 110. This response message (also known as an acknowledgment) indicates whether to accept joining the third group call.

[0235] For example, the response information may include a participant list indicating which participants have responded to the notification and joined the third group call, and which participants have not yet responded. Optionally, the response information may include SDP response information, such as server 112 sending an SDP response from participant 401 of the first group call to server 110.

[0236] Optionally, the response information may include floor request information.

[0237] At point 555, optionally, server 112 sends a message request to server 110.

[0238] For example, the speaking request information may include talker information or an implicit speaking request. For instance, the talker information may include an identifier of the client currently holding the speaking right in the first group call. For example, a participant (i.e., a speaker) is currently holding the speaking right to send media data in the first group call. Optionally, the speaking request information may also include identification information for the first group call. It is understood that this speaking request information is used to request the speaking right for the speaker. Optionally, the implicit or explicit speaking request may also include request priority information for use in determining the speaking right.

[0239] It should be noted that if the response information at 554 includes a message request, then 555 does not need to be executed.

[0240] At position 556, server 112 updates its local media forwarding rules.

[0241] For example, after receiving uplink media data, server 112 forwards it to server 110; after receiving downlink media data from server 110, it forwards it to participant 401.

[0242] For example, after the server 112 updates the local media plane forwarding rules, the first group of calls and the third group of calls can be interconnected.

[0243] Understandably, after steps 5545 / 555, server 112 no longer functions as a control function for participant 401 in group call 1, but rather as a non-control function. It should be noted that steps 551-555 shown in Figure 5C are for illustrative purposes only. In other examples, server 112 may send a response message to server 110 after determining that there is no speaker in the first group call, i.e., after all participants have been deprived of their speaking rights for a period of time. In this case, since there is no speaker with speaking rights, there is no need to send an additional speaking request message.

[0244] Figure 5C also shows steps 561 to 566, corresponding to the second group call. At 561, server 110 sends a fifth message to server 114, which is used to add the participants of the second group call to the third group call. At 562, server 114 sends a call merging notification message to participant 402 of the second group call, which is used to indicate to participant 402 that the second group call has been added to the third group call (or participant 402 of the second group call has been added to the third group call). At 563, participant 402 of the second group call sends a response message to server 114 to the call merging notification message, for example, the response message can be ACK. At 564, server 114 sends a response message to server 110 to the fifth message, which is used to indicate whether participant 402 of the second group call has responded to the notification message. Optionally, at 565, server 114 can send a speech request message to server 110. At 566, server 114 updates its local media plane forwarding rules. It is understood that the embodiments of 561 to 565 can be referred to the foregoing description in conjunction with parts 551 to 555, and for the sake of brevity, they will not be repeated here.

[0245] Additionally or optionally, server 110 may perform speaker adjudication at 570. Exemplarily, server 112 sends a floor request to server 110, which may include, for example, the identifier of the first speaker; and server 114 also sends a floor request to server 110, which may include, for example, the identifier of the second speaker. In some examples, if the third group call only allows one speaker at a time, one of the first and second speakers can be selected (or chosen) as the target speaker. In another scenario, if the first, second, and third group calls all allow multiple speakers, servers 112 and 114 may choose to send floor request information separately for each speaker. Alternatively, floor request information for all speakers can be sent in a single response message. For example, when the received speaking request information is for more than one speaker, and the number of speakers does not exceed the maximum number of speakers allowed in the third group call, server 110 can grant speaking rights to all of them. If the limit is exceeded, speaking rights are decided for multiple speakers in the first and second group calls. For example, based on the priority of the speaking request, one or more speakers can be rejected so that the total number of speakers granted speaking rights does not exceed the maximum number of speakers allowed in the third group call. For example, the number of rejected speakers can be the difference between the total number of speakers targeted by the speaking request information and the maximum number of speakers allowed in the third group call.

[0246] In some implementations, server 110 may select one of the first speaker and the second speaker. Exemplarily, the selection may be based on at least one of the following: the priority of the speaking request from server 112 and the speaking request from server 114, the priority of the first speaker and the second speaker, or the priority of the first group call and the second group call. Optionally, the speaker with higher priority may be selected.

[0247] In some implementations, server 110 can clear the speaker and send an idle message. For example, if server 110 receives response messages from servers 112 and 114 indicating agreement to join the third group call, it sends an idle message to all participants in the third group call.

[0248] Figure 5D illustrates a schematic diagram of an example process 500D for handling discourse rights according to some embodiments of the present disclosure. Process 500D involves servers 110, 112, and 114, as well as participants 401 of a first group call (group call 1) and participants 402 of a second group call (group call 2).

[0249] In some examples, assuming it's determined at 570 that the speaker in the second group call will speak, then 581 or 582 can be executed. At 581-1, server 110 sends an agreement to speak message to server 114, thereby granting the speaking right to the speaker in the second group call, or granting it to server 114, for example, server 114 can decide which participant 402 in group call 2 will be the speaker in the third group call (e.g., server 110 can re-determine the speaker). At 581-2, server 110 sends a refusal to speak message to server 112, thereby refusing or canceling a participant in the first group call from being the speaker in the third group call. Accordingly, at 581-3, server 112 can send a withdrawal of speech message to participant 401 in group call 1 (or the first speaker among them). At point 581-4, server 110 may send a floor taken message to server 112. This floor taken message may include information about the speaker of the third group call (e.g., one of the participants 401 in group call 2) to indicate that one of the participants 402 in group call 2 has taken the speaking role in the third group call. Optionally, server 110 may also send a floor taken message to server 114 (not shown in Figure 5D).

[0250] At point 582-1, server 110 can send a withdrawal message to server 112 to revoke the speaking right of participant 401 in group call 1. For example, this withdrawal message may include the identifier of the first speaker, such as the speaker information included at point 554 in Figure 5C, to revoke the first speaker's speaking right in the third group call. At point 582-2, server 110 can send a speaking message to server 112 to indicate that one of the participants 402 in group call 2 has acquired the speaking right in the third group call.

[0251] In some examples, assuming it is determined at 570 that a speaker needs to be removed, then 583 can be executed. Optionally, at 583-1, server 110 can send a withdraw speech message to server 114 to withdraw the speaking right of group call participant 402 in the third group call, for example, the second speaker (as included in speaker information 564 in Figure 5C) can be withdrawn from the third group call. Optionally, at 583-2, server 110 can send a withdraw speech message to server 112 to withdraw the speaking right of group call participant 401 in the third group call, for example, the first speaker (as included in speaker information 554 in Figure 5C) can be withdrawn from the third group call. At 583-3, server 110 sends a speech idle message to servers 112 and 114, indicating that the withdrawn speaker's speaking right in the third group call is idle.

[0252] Optionally, in some examples, server 110 may notify each participant in server 112, group call 1 participant 401, server 114, and group call 2 participant 402 to revoke their speaking rights. Optionally, server 110 may clear its local speaking rights state machine, for example, by placing the state machine into a speaking idle state.

[0253] It is understandable that at this point, the first and third call groups are linked (i.e., for participants in the first call group, the first and third call groups are identical), and the second and third call groups are linked (i.e., for participants in the second call group, the second and third call groups are identical). Therefore, granting the first speaker (or second speaker) the right to speak in the third call group, as mentioned above, can also be understood as authorizing (or maintaining) the first speaker's (or second speaker's) right to speak in the first (or second) call group; revoking the first speaker's (or second speaker's) right to speak in the third call group can also be understood as revoking (or refusing) the first speaker's (or second speaker's) right to speak in the first (or second) call group. The fact that the third call group has free speaking time can also be understood as free speaking time in the first and / or second call groups.

[0254] As shown in Figure 5D, subsequent media control can be performed at point 590, and media path processing can be performed at point 592. For example, for a speaking request from a participant, it can be processed as if there is a subgroup in the third group call. For example, the speaking request can be sent to the control server (i.e., server 110) for adjudication via a non-control server (such as server 112 or server 114).

[0255] For example, the media path can be processed according to the case where there are subgroups in the third group of calls. For example, for uplink media data from a participant, the uplink media data can be sent to the control server (i.e., server 110) via a non-control server (such as server 112 or server 114). For example, for downlink data from server 110 to a participant, it can be sent to the corresponding participant via the corresponding non-control server (such as server 112 or server 114).

[0256] It should be noted that the embodiments described in conjunction with Figures 5A to 5D are for illustrative purposes only and are not intended to limit the scope of this disclosure. For example, some operations (or steps) shown in the figures may be omitted, removed, or combined. For example, one or more additional operations (or steps) may be further included in the figures. For example, the order of operations (or steps) shown in the figures may be rearranged or adjusted.

[0257] By combining the descriptions in Figures 5A to 5D, participants from the first call group and the second call group can be added to the newly created third call group, and the first and second calls can be released, thus achieving the merging of the first and second calls.

[0258] The above-described process for group call processing has provided some exemplary embodiments in conjunction with Figures 3A to 5D. It should be understood that these exemplary embodiments and the accompanying drawings are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure. For example, those skilled in the art can recombine, omit / remove, merge, modify / adjust, or rearrange the order of some operations (or steps) in the accompanying drawings. Other embodiments obtained based on the foregoing embodiments also fall within the scope of protection of this disclosure. For example, at 410 in Figure 4, server 114 determines the updated user list / criteria for the second group call, and at 510 in Figure 5B, server 201 determines the user list / criteria for the third group call. However, in other examples, the client 202 may also perform this determination, as shown below in conjunction with Figure 6.

[0259] Figure 6 illustrates a schematic diagram of an example process 600 for determining a user list / criteria according to some embodiments of the present disclosure. Process 600 involves a server 201 and a client 202. As previously mentioned, server 201 can be server 112, server 114, or server 110, etc. It should be noted that process 600 can be understood as a specific implementation of 410 in Figure 4 or 510 in Figure 5B. For ease of description, the updated second and third group calls can be collectively referred to as target group calls.

[0260] At 610, client 202 determines the list / criteria of users for the target group call.

[0261] In some implementations, client 202 can determine the user list and / or criteria for the target group call based on information from the first group call and the second group call. For example, this determination operation is similar to the operations described in 410 or 510 above.

[0262] In some examples, if the first call group is based on a user list and the second call group is also based on a user list, then the union of the user lists of the first and second calls can be used as the user list of the target call group.

[0263] In some examples, if the first group of calls is established based on the first criterion and the second group of calls is established based on the second criterion, then the union of the first and second criters can be used as the criterion for the target group of calls.

[0264] In some examples, if the first call group is based on a user list and the second call group is based on criteria, then the criteria for the target call group can be the criteria for the second call group, and each participant in the user list of the first call group (such as participants who do not meet the criteria for the second call group) is tagged or marked, indicating that the corresponding participant is not bound by the criteria.

[0265] In some examples, if the second call group is based on a user list and the first call group is based on criteria, then the criteria for the target call group can be the criteria for the first call group, and each participant in the user list of the second call group (such as participants who do not meet the criteria of the first call group) is tagged or marked, indicating that the corresponding participant is not bound by the criteria.

[0266] In some examples, if the first call group is established based on the first criterion and also includes participants added after its establishment via a user list (such as one or more participants added by the initiator of the first call group who do not meet the first criterion), and the second call group is established based on the second criterion, then the union of the first and second criters can be used as the criterion for the target call group, and participants who joined the first call group later are labeled or marked with a tag indicating that the corresponding participant is not bound by the criterion.

[0267] It is understood that, for some combinations of the above examples, those skilled in the art can determine the user list and / or criteria for the target group call through the group call of the above examples, and this disclosure will not list them one by one.

[0268] At 620, client 202 sends the target group call user list / criteria to server 201.

[0269] In some implementations, the user list / criteria for the target group call sent at position 620 can be included in the first information discussed above. That is, the first information (such as group call update information or update establishment information) can include the user list / criteria for the target group call. In some implementations, the user list / criteria for the target group call sent at position 620 can be included in another piece of information independent of / different from the first information, such as update / modify criteria request information, update / modify user list request information, etc.

[0270] Additionally, it should be noted that although the above embodiments illustrate the merging of two group calls (first and second group calls), these embodiments can also be applied to merging more than two group calls. For example, participants from each of two or more group calls can be added to the same group call (which may be called the target group call). For instance, one of the two or more group calls can be updated to serve as the target group call, or a new group call can be created as the target group call. It is understood that embodiments merging more than two group calls are similar to the embodiments merging two group calls described above, and for the sake of brevity, they will not be repeated here.

[0271] It should be understood that in the embodiments of this disclosure, terms such as "first," "second," and "third" are merely used to indicate that multiple objects may be different, but do not exclude the possibility that two objects are the same. "First," "second," and "third," etc., should not be construed as any limitation on the embodiments of this disclosure.

[0272] It should also be understood that the manner, situation, category, and division of embodiments in the present disclosure are for the convenience of description only and should not constitute a special limitation. Various manners, categories, situations, and features in the embodiments can be combined with each other where logically consistent.

[0273] It should also be understood that the foregoing is merely to help those skilled in the art better understand the embodiments of this disclosure, and is not intended to limit the scope of the embodiments of this disclosure. Those skilled in the art can make various modifications, variations, or combinations based on the foregoing. Such modifications, variations, or combinations are also within the scope of the embodiments of this disclosure.

[0274] It should also be understood that the above description focuses on highlighting the differences between the various embodiments. Similarities or commonalities can be referenced or learned from each other, and for the sake of brevity, they will not be repeated here.

[0275] It should be noted that some exemplary embodiments have been described in conjunction with the accompanying drawings in this disclosure. However, these exemplary embodiments and the drawings are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure. For example, operations (or steps) in different drawings can be recombined. For example, some operations (or steps) shown in the drawings can be omitted, removed, or combined. For example, one or more additional operations (or steps) may be further included in the drawings. For example, the order of operations (or steps) shown in the drawings can be rearranged or adjusted. It should be understood that other embodiments obtained based on the foregoing embodiments also fall within the scope of protection of this disclosure.

[0276] Figure 7 shows a schematic block diagram of a communication apparatus 700 according to some embodiments of the present disclosure. The apparatus 700 includes an acquisition module 710 and a transmission module 720. The acquisition module 710 can be configured to acquire information about a first group call and information about a second group call. The transmission module 720 can be configured to send first information to a server based on the information about the first group call and the second group call, the first information being used to add participants from the first group call and participants from the second group call to the same group call.

[0277] In some implementations, the communication device 700 can be implemented as the aforementioned client (e.g., client 202), an internal device of the client, or an internal chip of the client. In some implementations, the acquisition module 710 can be implemented as a receiver or transceiver. In some implementations, the transmission module 720 can be implemented as a transmitter or transceiver. In some implementations, the communication device 700 may also include a processing module, such as a processor or control circuit.

[0278] In some implementations, the first information includes group call update information, which is used to indicate that the second group call should be updated by adding participants from the first group call to the second group call.

[0279] For example, the processing module may be configured to determine, based on at least one of the following, to update the second call by adding participants from the first call group to the second call group: the number of participants in the first call group and the number of participants in the second call group; the priority of the first call group and the priority of the second call group; the establishment method of the first call group and the establishment method of the second call group; user preference information corresponding to the client, or the client's local policy.

[0280] For example, the processing module can be configured to determine to add participants from the first call group to the second call group if at least one of the following conditions is met: the number of participants in the first call group is less than the number of participants in the second call group; the priority of the first call group is lower than the priority of the second call group; the first call group is established based on a user list and the second call group is established based on a criterion; or the first call group is established based on a first criterion and the second call group is established based on a second criterion, and the area corresponding to the first criterion is smaller than the area corresponding to the second criterion.

[0281] In some implementations, the first information includes group call establishment information, which is used to establish a third group call, wherein the participants in the third group call include the participants in the first group call and the participants in the second group call.

[0282] For example, the sending module 720 can be configured to send second information to the server of the second group call, the second information being used to release the second group call.

[0283] In some embodiments, the sending module 720 may also be configured to send third information to the server of the first group of calls, the third information being used to release the first group of calls.

[0284] In some embodiments, the first information includes at least one of the following: a list of users for the first group call, criteria for establishing the first group call, a list of users for the second group call, or criteria for establishing the second group call.

[0285] In some implementations, the first information includes information for triggering the merging of the first and second call groups.

[0286] For example, the acquisition module 710 can be configured to acquire information about multiple group calls, including a first group call and a second group call. For example, the processing module can be configured to determine, based on the information about the multiple group calls, to merge the first group call and the second group call.

[0287] For example, the first information includes information from the first group of calls and / or information from the second group of calls.

[0288] In some embodiments, the first information includes identification information of the first group of calls and identification information of the second group of calls.

[0289] In some embodiments, the acquisition module 710 may be specifically configured to acquire information about the first group of calls from the server of the first group of calls; and to acquire information about the first group of calls from the server of the second group of calls.

[0290] In some embodiments, the information of the first group call and / or the information of the second group call includes at least one of the following: the identification information of the group call, the method of establishing the group call, the priority of the group call, the list of participants in the group call, the criteria for establishing the group call, the number of participants in the group call, the information of the initiator of the group call, the security level of the group call, the broadcasting method of the group call, or the hang time of the group call.

[0291] Figure 8 shows a schematic block diagram of a communication device 800 according to some embodiments of the present disclosure. The device 800 includes a receiving module 810 and a processing module 820. The receiving module 810 can be configured to receive first information for adding participants of a first group call and participants of a second group call to the same group call. The processing module 820 can be configured to add participants of the first group call and participants of the second group call to the same group call based on the first information.

[0292] In some implementations, the communication device 800 can be implemented as the aforementioned server (e.g., server 201), or an internal device of the server, or an internal chip of the server, etc. In some implementations, the receiving module 810 can be implemented as a receiver or transceiver. In some implementations, the processing module 802 can be implemented as a processor or control circuit, etc. In some implementations, the communication device 700 may also include a transmitting module, for example, it can be implemented as a transmitter or transceiver.

[0293] In some implementations, the first information includes group call update information, which is used to indicate that the second group call should be updated by adding participants from the first group call to the second group call.

[0294] In some implementations, the first information includes group call establishment information, which is used to establish a third group call, wherein the participants in the third group call include the participants in the first group call and the participants in the second group call.

[0295] For example, the sending module can be configured to send a second message to the control function of the second group call, the second message being used to release the second group call.

[0296] For example, the sending module can be configured to send third information to the control function of the first group of calls, the third information being used to release the first group of calls.

[0297] In some embodiments, the first information includes identification information of the first group of calls and identification information of the second group of calls.

[0298] In some implementations, the sending module is configured to send join information to the control function of the first group call based on the first information. The join information is used to add the participants of the first group call to the second group call. In some implementations, the processing module 820 can be configured to establish a third group call based on the first information. The participants of the third group call include the participants of the first group call and the participants of the second group call.

[0299] For example, the sending module can be configured to send a fourth message to the control function of the first group call, the fourth message being used to add the participants of the first group call to the third group call; and to send a fifth message to the control function of the second group call, the fifth message being used to add the participants of the second group call to the third group call.

[0300] For example, the receiving module can be configured to receive information or right-to-speak request information from the speaker of the first group call from the control function of the first group call, the right-to-speak request information being used to request right-to-speak for the speaker of the first group call in the third group call.

[0301] For example, the receiving module can be configured to receive information or right-to-speak request information from the speaker of the second group call from the control function of the second group call, the right-to-speak request information being used to request right-to-speak for the speaker of the second group call in the third group call.

[0302] For example, the processing module can be configured to determine the speaker in the third group of calls, which is either the speaker in the first group of calls or the speaker in the second group of calls.

[0303] In some embodiments, the sending module can be configured to send a sixth message to the control functions of the first group call and the second group call, the sixth message being used to indicate that the right of voice for the third group call is idle.

[0304] It should be noted that the division of modules or units in the embodiments of this disclosure is illustrative and only represents a logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the disclosed embodiments may be integrated into one unit, exist as separate physical entities, or two or more units may be integrated into one unit. The integrated unit described above can be implemented in hardware or as a software functional unit.

[0305] For example, the device 700 in FIG7 can be used to implement the various processes executed by the client 202 as described above in conjunction with FIG2 to FIG6, which will not be described in detail here for the sake of brevity. The device 800 in FIG8 can be used to implement the various processes executed by the server 202 (such as server 114 or server 110) as described above in conjunction with FIG2 to FIG6, which will not be described in detail here for the sake of brevity.

[0306] Figure 9 shows a schematic block diagram of an example device 900 that can be used to implement embodiments of the present disclosure. Device 900 may be implemented as or included in the aforementioned server 201 (or device 800) or client 202 (or device 700).

[0307] As shown in Figure 9, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processors 910, and a communication module 940 coupled to the processors 910.

[0308] The communication module 940 can be used for bidirectional communication. The communication module 940 may have at least one communication interface for communication. The communication interface may include any interface necessary for communication with other devices.

[0309] Processor 910 can be any type suitable for a local technology network and can include, but is not limited to, one or more of the following: a general-purpose computer, a special-purpose computer, a microcontroller, a digital signal processor (DSP), or a controller-based multi-core controller architecture. Device 900 can have multiple processors, such as application-specific integrated circuit chips, which are time-dependent on a clock synchronized with the main processor.

[0310] Memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, at least one of the following: Read-Only Memory (ROM) 924, Erasable Programmable Read Only Memory (EPROM), Flash Memory, Hard Disk, Compact Disc (CD), Digital Versatile Disc (DVD), or other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, at least one of the following: Random Access Memory (RAM) 922, or other volatile memories that do not persist during the duration of a power outage.

[0311] Computer program 930 includes computer-executable instructions that are executed by associated processor 910. Program 930 may be stored in ROM 924. Processor 910 may perform any suitable actions and processes by loading program 930 into RAM 922.

[0312] Embodiments of this disclosure can be implemented using program 930, enabling device 900 to perform any of the processes discussed with reference to FIG2. Embodiments of this disclosure can also be implemented in hardware or a combination of software and hardware.

[0313] Program 930 may be tangibly contained in a computer-readable medium, which may include in device 900 (such as in memory 920) or other storage device accessible by device 900. Program 930 may be loaded from the computer-readable medium into RAM 922 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0314] In some embodiments, the communication module 940 in the device 900 can be implemented as a transmitter and receiver (or transceiver), which can be configured to send / receive, such as multiple TCIs, at least one message, capability information, etc. Additionally, the device 900 may further include one or more of a scheduler, a controller, and a radio frequency / antenna, which will not be described in detail in this disclosure.

[0315] For example, the device 900 in FIG9 may be implemented as an electronic device, or may be implemented as a chip or chip system in an electronic device, and the embodiments of this disclosure are not limited thereto.

[0316] Embodiments of this disclosure also provide a chip, which may include an input interface, an output interface, and processing circuitry. In embodiments of this disclosure, the input and output interfaces can be used to complete the interaction of signaling or data, while the processing circuitry can be used to generate and process the signaling or data information.

[0317] Embodiments of this disclosure also provide a chip system including a processor for supporting a communication device to implement the functions involved in any of the above embodiments. In one possible design, the chip system may further include a memory for storing necessary program instructions and data, which, when executed by the processor, cause a device on which the chip system is installed to implement the methods involved in any of the above embodiments. Exemplarily, the chip system may consist of one or more chips, or may include chips and other discrete devices.

[0318] Embodiments of this disclosure also provide a processor for coupling with a memory storing instructions that, when executed by the processor, cause the processor to perform the methods and functions involved in any of the above embodiments.

[0319] Embodiments of this disclosure also provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods and functions involved in any of the embodiments described above.

[0320] Embodiments of this disclosure also provide a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods and functions involved in any of the above embodiments.

[0321] Embodiments of this disclosure also provide a communication system including the aforementioned server 201 (or device 800) or client 202 (or device 700). Exemplarily, the system includes multiple clients. Exemplarily, the system may include multiple servers.

[0322] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or represented using some other illustration, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as, as non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0323] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which execute in a device on a target real or virtual processor to perform the processes / methods as described above with reference to the accompanying drawings. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or divided among program modules as needed. The machine-executable instructions for the program modules can execute within a local or distributed device. In a distributed device, the program modules can reside in both local and remote storage media.

[0324] Computer program code used to implement the methods of this disclosure may be written in one or more programming languages. This computer program code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that when executed by the computer or other programmable data processing apparatus, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be performed. The program code may be executed entirely on a computer, partially on a computer, as a stand-alone software package, partially on a computer and partially on a remote computer, or entirely on a remote computer or server.

[0325] In the context of this disclosure, computer program code or related data may be carried on any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and so on. Examples of signals may include electrical, optical, radio, sound, or other forms of propagation signals, such as carrier waves, infrared signals, etc.

[0326] A computer-readable medium can be any tangible medium that contains or stores a program for or relating to an instruction execution system, apparatus, or device. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More detailed examples of computer-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage medium as used herein is not to be construed as a transient signal itself, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0327] Furthermore, although the operation of the methods of this disclosure is described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Rather, the steps depicted in the flowcharts may be performed in a different order. 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. It should also be noted that the features and functions of two or more devices according to this disclosure may be embodied in one device. Conversely, the features and functions of one device described above may be further divided and embodied by multiple devices.

[0328] Various implementations of this disclosure have been described above. The foregoing description is exemplary and not exhaustive, nor is it limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to well explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A group call processing method, characterized by, The method is executed by the client and includes: Obtain information from the first call group and the second call group; and Based on the information from the first group call and the second group call, a first message is sent to the server. The first message is used to add the participants of the first group call and the participants of the second group call to the same group call.

2. The method according to claim 1, wherein the first information includes group call update information, the group call update information being used to indicate updating the second group call by adding participants from the first group call to the second group call.

3. The method according to claim 2, further comprising: The second group of calls is determined to be updated by adding participants from the first group of calls to the second group of calls, based on at least one of the following: The number of participants in the first group of calls and the number of participants in the second group of calls; The priority of the first group of calls and the priority of the second group of calls; The method for establishing the first group of calls and the method for establishing the second group of calls; The user preference information corresponding to the client, or The client's local policy.

4. The method of claim 3, wherein determining to update the second group call by adding participants from the first group call to the second group call based on at least one of the following includes: If at least one of the following conditions is met, then the participants in the first group of calls will be added to the second group of calls: The number of participants in the first group of calls is less than the number of participants in the second group of calls. The first group of calls has a lower priority than the second group of calls. The first group of calls is established based on a user list, and the second group of calls is established based on criteria, or The first group of calls is established based on the first criterion, the second group of calls is established based on the second criterion, and the region corresponding to the first criterion is smaller than the region corresponding to the second criterion.

5. The method according to claim 1, wherein the first information includes group call establishment information, the group call establishment information being used to establish a third group call, wherein the participants of the third group call include the participants of the first group call and the participants of the second group call.

6. The method according to claim 5, further comprising: Send a second message to the server of the second group of calls, the second message being used to release the second group of calls.

7. The method according to any one of claims 2-6, further comprising: Send a third message to the server of the first group of calls, the third message being used to release the first group of calls.

8. The method according to any one of claims 2-7, wherein the first information includes at least one of the following: The first group of callers' list, The criteria for establishing the first group of calls, The second group of caller list, or The criteria for establishing the second group of calls.

9. The method according to claim 1, wherein the first information includes information for triggering the merging of the first group of calls and the second group of calls, the method further comprising: Obtain information about multiple group calls, including the first group call and the second group call; as well as Based on the information from the multiple group calls, it is determined that the first group call and the second group call will be merged.

10. The method according to claim 9, wherein the first information includes information of the first group call and / or information of the second group call.

11. The method according to any one of claims 1-10, wherein the first information includes the identification information of the first group call and the identification information of the second group call.

12. The method according to any one of claims 1-11, wherein obtaining the information of the first group of calls and the information of the second group of calls comprises: Obtain information about the first group of calls from the server of the first group of calls; Obtain information about the first group of calls from the server of the second group of calls.

13. The method according to any one of claims 1-12, wherein the information of the first group call and / or the information of the second group call includes at least one of the following: Group call identification information, The method of establishing a group call. Group call priority, List of participants in the group call The guidelines for establishing group calls The number of participants in the group call Information about the initiator of the group call. Group call security level, The broadcasting method of group calls, or The hang time of a group call.

14. A group call processing method, characterized by, The method is executed by a server or control function, including: Receive first information, the first information being used to add participants from the first group call and participants from the second group call to the same group call; and Based on the first information, the participants in the first group of calls and the participants in the second group of calls are added to the same group of calls.

15. The method of claim 14, wherein the first information includes group call update information, the group call update information being used to indicate updating the second group call by adding participants from the first group call to the second group call.

16. The method of claim 14, wherein the first information includes group call establishment information, the group call establishment information being used to establish a third group call, wherein the participants of the third group call include the participants of the first group call and the participants of the second group call.

17. The method of claim 16, further comprising: Send a second message to the control function of the second group of calls, the second message being used to release the second group of calls.

18. The method according to any one of claims 15-17, further comprising: Send a third message to the control function of the first group of calls, the third message being used to release the first group of calls.

19. The method according to any one of claims 14-18, wherein the first information includes the identification information of the first group call and the identification information of the second group call.

20. The method according to claim 14, wherein adding participants of the first group call and participants of the second group call to the same group call based on the first information comprises: Based on the first information, a join information is sent to the control function of the first group call, the join information being used to add the participants of the first group call to the second group call; or Based on the first information, a third group of calls is established, and the participants in the third group of calls include the participants in the first group of calls and the participants in the second group of calls.

21. The method according to claim 20, wherein establishing the third group of calls based on the first information comprises: Send a fourth message to the control function of the first group call, the fourth message being used to add the participants of the first group call to the third group call; as well as Send a fifth message to the control function of the second group call, the fifth message being used to add the participants of the second group call to the third group call.

22. The method of claim 21, further comprising: The system receives information or right-to-speaker request information from the speaker of the first group call, which is used to request right-to-speaker status for the speaker of the first group call in the third group call.

23. The method of claim 22, further comprising: The system receives information or right-to-speaker request information from the speaker of the second group call, which is used to request right-to-speaker status for the speaker of the second group call in the third group call.

24. The method according to claim 22 or 23, further comprising: The speaker in the third group of calls is determined, and the speaker in the third group of calls is either the speaker in the first group of calls or the speaker in the second group of calls.

25. The method of claim 21, further comprising: A sixth message is sent to the control functions of the first group of calls and the control functions of the second group of calls. The sixth message is used to indicate that the right of the third group of calls is idle.

26. A communication device, comprising: At least one memory for storing computer-executable instructions; as well as At least one processor is configured to execute the computer-executable instructions to cause the communication device to perform the method according to any one of claims 1 to 25.

27. A communication system, comprising: The client is configured to perform the method according to any one of claims 1 to 13; as well as The server is configured to perform the method according to any one of claims 14 to 25.

28. A computer-readable storage medium having instructions stored thereon, which, when executed by a communication device, cause the communication device to perform the method according to any one of claims 1 to 25.

29. A computer program product storing instructions that, when executed, cause the method according to any one of claims 1 to 25 to be performed.

30. A chip including processing circuitry configured to perform the method according to any one of claims 1 to 25.