Communication method and apparatus

Abstract

The present application provides a communication method and apparatus, applied in the technical field of communications, and capable of flexibly implementing update operations for users in a group call, such as accurately adding or removing users, thereby improving the communication efficiency of the group call. The method can comprise: a terminal sends a first message to a network device, wherein the first message is used for updating users in a first group call, the first message comprises an identifier of a user to be added and a user attribute of the user to be added, and / or an identifier of a user to be removed and a user attribute of the user to be removed; and the network device updates the users in the first group call on the basis of the first message.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on February 7, 2024, with application number 202410175960.5 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0003] Mission Critical (MC) communications, also known as mission-critical communications, refers to communications services that meet critical communications needs. They are used to support trunked communications in public safety scenarios, providing high-quality, highly reliable, and highly secure voice, video, and data communications. MC communications services include Mission Critical push-to-talk (MCPTT), Mission Critical Video (MCVideo), and Mission Critical Data (MCData), corresponding to the voice, video, and data services in MC communications, respectively.

[0004] Currently, an MC communication connection can be established between a terminal user and a server through an instant group communication (Ad-hoc group call) mode. Specifically, the call initiating user can send an instant group call request to the MC server and select a group of called users to enter the instant group. The call initiator can provide the MC server with a user list of called users, or provide user screening rules (criteria), so that the MC server can initiate a group call request to the users in the user list, or to a group of users that meet the rules. Subsequently, the call initiating user can modify the user list of the called users, such as adding or removing users; in addition, the initiator or other authorized users can modify or update the user screening rules, so that the MC server can continue to filter users in the group according to the updated rules, such as removing users that do not meet the rules and adding other users that meet the rules.

[0005] However, the above implementation methods all have certain limitations and cannot meet the diverse needs of users. The group calling method based on the user list is difficult to add all relevant users who meet specific conditions to the group. For example, the user list of users in a certain area is constantly changing due to user movement. When the number of users in the user list is large, the user list is long and the corresponding instruction overhead is large. The group calling method based on user screening rules is not accurate and flexible enough. When the call initiator needs to add or remove one or more specific users, it cannot be achieved by adding or updating rules.

[0006] Summary of the Invention

[0007] The present application provides a communication method and apparatus that can flexibly implement the update operation of users in a group call, accurately add or remove users, and improve the communication efficiency of the group call.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] In a first aspect, a communication method is provided, which can be executed by a terminal or a module (such as a chip or circuit) of the terminal. The method includes: generating a first message for updating users in a first group call, the first message including an identifier of a user to be added and user attributes of the user to be added, and / or an identifier of a user to be removed and user attributes of the user to be removed; and sending the first message to a network device.

[0010] In the above embodiment, the terminal side carries the corresponding user attributes for the users to be added and / or removed in the request message for updating the users in the group call, so that the server processes the two methods of updating the participating users in the group call through the user list update and the user screening rule update, which no longer conflict with each other. The two update methods can be implemented at the same time. The user can flexibly add or remove users in the group call according to these two methods without contradiction or conflict, thereby improving the flexibility and update efficiency of group call user updates, thereby improving the user experience.

[0011] In one embodiment, if the user attribute of the user to be added is a first attribute, the first attribute is used to indicate at least one of the following information: the user to be added is a necessary user in the first group call; or, before the first group call ends, the user to be added is retained in the first group call; or, the user to be added cannot be removed before the first group call ends; or, the user screening rule corresponding to the first group call is not applied to the user to be added, and the user screening rule is used by the network device to update the users in the first group call.

[0012] In the above embodiment, the terminal can set the user attribute of the user to be added as the first attribute, so that the server can update the user to be added according to the first attribute, and the user screening rules added before or after the first group call are not applied to the user with the first attribute. Therefore, the users added through the user list are no longer affected by the user screening rules and are removed from the group call, thereby improving the flexibility and update efficiency of group call users.

[0013] In one embodiment, if the user attribute of the user to be removed is a second attribute, the second attribute is used to indicate at least one of the following information: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be added is not allowed to be added to the first group call by the network device according to the user screening rule corresponding to the first group call; or, the user to be removed is not subject to the user screening rule corresponding to the first group call, and the user screening rule is used by the network device to update the users in the first group call.

[0014] In the above embodiment, the terminal can set the user attribute of the user to be removed as the second attribute, so that the server can remove the user to be removed from the first group call based on the second attribute, and the user screening rules added before or after in the first group call will not be applied to the user with the second attribute. Therefore, the user removed through the user list is no longer affected by the user screening rules and is automatically added to the first group call, thereby improving the flexibility and update efficiency of group call user updates.

[0015] In one embodiment, the method further includes: sending a second message to the network device, wherein the second message includes an identifier of at least one target user; the second message is used to request establishment of the first group call and add the target user to the first group call.

[0016] In one implementation, the second message further includes a first attribute corresponding to the target user.

[0017] In one embodiment, the method further includes: sending a third message to the network device, the third message including information of a first rule, the third message being used to request establishment of the first group call, wherein the first rule is one of user screening rules, and the first rule is used to add users who meet the first rule to the first group call, and remove participating users who do not meet the first rule from the first group call.

[0018] In one embodiment, the third message further includes first information, where the first information is used to indicate that the target users screened according to the first rule are necessary users in the first group call.

[0019] In one embodiment, the third message further includes second information, where the second information is used to indicate whether the attribute of the first rule is read-only or modifiable.

[0020] In one embodiment, the method also includes sending a fourth message to the network device, the fourth message including information of the second rule, or including update information of the first rule, the second rule or the update information being used to update users in the first group call; wherein the second rule is one of the user screening rules, and the second rule is used to add users who meet the second rule to the first group call, and remove participating users who do not meet the second rule from the first group call.

[0021] In one embodiment, the method further includes: receiving a response message from the network device, indicating a result of the user update in the first group call.

[0022] In a second aspect, a communication method is provided, which can be executed by a network device or a module (such as a chip or circuit) of the network device. The method includes: receiving a first message from a first terminal, the first message being used to update a user in a first group call, the first message including an identifier of a user to be added and / or an identifier of a user to be removed; determining user attributes of the user to be added, and adding the user to the first group call based on the first message; and / or determining user attributes of the user to be removed, and removing the user from the first group call based on the first message.

[0023] In the above-mentioned embodiment, through the functional enhancement on the network device side, the network device can automatically generate corresponding user attributes for the users to be added and / or the users to be removed based on the user list in the initial establishment or update request message (such as the first message), so that the server processes the two methods of updating the participating users in the group call through the user list update and the user screening rule update, which no longer conflict. The two update methods can be implemented at the same time. Users can flexibly add or remove users in the group call according to these two methods without contradiction or conflict, thereby improving the flexibility and update efficiency of group call user updates, thereby improving the user experience.

[0024] In one embodiment, if the user attribute is a first attribute, the first attribute is used to indicate at least one of the following information: the user to be added is a necessary user in the first group call; or, the user to be added is retained in the first group call before the first group call ends; or, the user to be added cannot be removed before the first group call ends; or, the user screening rule corresponding to the first group call is not applied to the user to be added, and the user screening rule is used by the network device to update the users in the first group call.

[0025] In one embodiment, if the user attribute is a second attribute, the second attribute is used to indicate at least one of the following information: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be removed is not allowed to be added to the first group call by the network device according to the user screening rule corresponding to the first group call; or, the user to be removed is not subject to the user screening rule corresponding to the first group call, and the user screening rule is used by the network device to update the users in the first group call.

[0026] In one implementation, the first message includes user attributes of the user to be added and / or user attributes of the user to be removed.

[0027] In one embodiment, determining the user attributes of the user to be added includes: generating a first attribute of the user to be added for the user to be added according to the first message, and / or generating a second attribute of the user to be removed for the user to be removed.

[0028] In one embodiment, the method further includes: receiving a second message from the first terminal or from the second terminal, the second message including an identifier of at least one target user, the at least one target user including a user associated with the first terminal; adding the target user to the first group call to establish the first group call.

[0029] In one implementation, the second message further includes a first attribute corresponding to the target user.

[0030] In one embodiment, the method further includes: receiving a third message from the first terminal or from the second terminal, the third message including information of the first rule; adding target users meeting the first rule to the first group call to establish the first group call.

[0031] In one embodiment, the method further includes: updating the participating users in the first group call, adding the target users who meet the first rule to the first group call, and removing the users who do not meet the first rule from the first group call; if the user attribute corresponding to the first user in the first group call is the first attribute, retaining the first user in the first group call; if the second user meets the first rule and the user attribute corresponding to the second user is the second attribute, removing the second user from the first group call, or not adding the second user to the first group call.

[0032] In one embodiment, the third message further includes second information for indicating whether the attribute of the first rule is read-only or modifiable.

[0033] In one embodiment, the method further includes: receiving a fourth message from the terminal, the fourth message including information of the second rule and / or including update information of the first rule; according to the second rule or the update information, adding target users who meet the second rule or the update information to the first group call, and removing participating users who do not meet the second rule from the first group call.

[0034] In one embodiment, the method further includes: saving a user list corresponding to the first group call, and user attributes corresponding to the users in the user list; and / or, saving the first attribute in the first group call and the user list corresponding to the first attribute; and / or, saving the second attribute in the first group call and the user list corresponding to the second attribute; and / or, saving at least one user screening rule corresponding to the first group call, and first information corresponding to the user screening rule, the first information being used to indicate that the target user determined according to the user screening rule is a necessary user in the first group call.

[0035] In one embodiment, the method further includes: sending a response message to the first terminal to indicate a result of user update in the first group call.

[0036] In a third aspect, a communication method is provided, which can be executed by a terminal or by a module (such as a chip or circuit) of the terminal. The method includes: sending a first message to a network device, the first message including information of a first rule and third information, the third information indicating deactivation of the first rule corresponding to a first group call, the first rule being used to add users who meet the first rule to the first group call, and removing participating users who do not meet the first rule from the first group call; sending a second message to the network device, the second message being used to update users in the first group call, the second message including an identifier of a user to be added, and / or an identifier of a user to be removed; wherein the first rule is invalid for the user to be added and the user to be removed.

[0037] In the above implementation mode, the terminal can modify or set the activation status of the user screening rules for the group call by requesting the network device, so that the user screening rules are deactivated for a period of time, thereby authorizing the terminal to flexibly update the participating users in the group call as needed, such as adding or removing users through the user list without being affected by the user screening rules, thereby improving the flexibility of updating the participating users in the group call, improving the communication efficiency of the group call, and thus improving the user experience.

[0038] In one embodiment, the user to be added satisfies at least one of the following conditions: the user to be added is a necessary user in the first group call; or, before the first group call ends, the user to be added remains in the first group call; or, the user to be added cannot be removed before the first group call ends; or, the first rule is not applied to the user to be added.

[0039] In one embodiment, the user to be added satisfies at least one of the following conditions: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be added is not allowed to be added to the first group call by the network device according to the first rule; or, the first rule is not applied to the user to be removed.

[0040] In one embodiment, the method further includes: sending a third message to the network device, the third message including information about the first rule and fourth information, the fourth information indicating activation of the first rule corresponding to the first group call.

[0041] In one embodiment, the method further includes: receiving a response message from the network device, including an activation status of the first rule.

[0042] In a fourth aspect, a communication method is provided, which can be executed by a network device or by a module (such as a chip or circuit) of the network device. The method includes: receiving a first message from a terminal, the first message including information about a first rule and third information, the third information indicating deactivation of the first rule, the first rule being used to add users who meet the first rule to the first group call, and removing participating users who do not meet the first rule from the first group call; receiving a second message from the terminal, the second message being used to update users in the first group, the second message including at least one identifier of a user to be added, and / or including at least one identifier of a user to be removed; according to the second message, adding the user to be added to the first group call, the user to be added being a necessary user in the first group call; and / or removing the user to be removed from the first group call.

[0043] In one embodiment, the user to be added satisfies at least one of the following conditions: the user to be added is a necessary user in the first group call; or, before the first group call ends, the user to be added remains in the first group call; or, the user to be added cannot be removed before the first group call ends; or, the first rule is not applied to the user to be added.

[0044] In one embodiment, the user to be removed satisfies at least one of the following conditions: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be added is not allowed to be added to the first group call by the network device according to the first rule; or, the first rule is not applied to the user to be removed.

[0045] In one embodiment, if the user to be added does not meet the first rule, the first user is retained in the first group call; if the user to be removed meets the first rule, the user to be removed is removed from the first group call, or the user to be removed is not added to the first group call.

[0046] In one embodiment, the method further includes: updating the state of the first rule to a deactivated state.

[0047] In one embodiment, the method also includes: receiving a third message from the terminal, the third message including information of the first rule and fourth information, the fourth information indicating activation of the first rule; adding users who meet the first rule to the first group call, removing participating users who do not meet the first rule from the first group call, and updating the status of the first rule to an activated state.

[0048] In one embodiment, the method further includes: sending a response message to an authorized terminal in the first group call, including an activation status of the first rule.

[0049] In a fifth aspect, a communication device is provided for implementing the above method. The communication device may be a terminal in the first or third aspect, or a network device in the second or fourth aspect, or a node or device including the above network device or terminal, or a module in the above network device or terminal, such as a chip, chip system, or circuit, or a logical node, logic module, or software that can implement some or all of the functions.

[0050] The communication device includes modules, units, or means corresponding to the above-mentioned method, which can be implemented by hardware, software, or hardware executing corresponding software implementation. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions.

[0051] In conjunction with the fifth aspect, in one possible implementation, the communication device may include a processing module and a transceiver module. The processing module may be configured to implement the processing functions described in any of the above aspects and any possible implementations thereof. The processing module may, for example, be a processor. The transceiver module, also referred to as a transceiver unit, may be configured to implement the transmitting and / or receiving functions described in any of the above aspects and any possible implementations thereof. The transceiver module may be comprised of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0052] In combination with the fifth aspect above, in a possible implementation, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in any of the above aspects and any possible implementations thereof.

[0053] In a sixth aspect, a communication device is provided, comprising: a processor; the processor is configured to be coupled to a memory, and after reading instructions from the memory, execute the method described in any of the above aspects according to the instructions. The communication device may be the terminal described in the first or third aspect, or the network device described in the second or fourth aspect, or a node or device including the network device or terminal described above, or a module in the network device or terminal described above, such as a chip, chip system, or circuit, or a logical node, logic module, or software that can implement some or all of the functions.

[0054] In combination with the sixth aspect above, in a possible implementation, the communication device further includes a memory, which is used to store necessary program instructions and data.

[0055] In conjunction with the sixth aspect above, in one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0056] In a seventh aspect, a communication device is provided, comprising: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instruction and transmit it to the processor; and the processor is configured to execute the computer program or instruction so that the communication device performs the method described in any of the above aspects. The communication device may be a terminal as described in the first or third aspect, or a network device as described in the second or fourth aspect, or a node or device including the network device or terminal, or a module in the network device or terminal, such as a chip, chip system, or circuit, or a logical node, logical module, or software capable of implementing some or all of the functions.

[0057] In conjunction with the seventh aspect above, in one possible implementation, the communication device is a chip or a chip system. Optionally, when the communication device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0058] In an eighth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium. When the computer-readable storage medium is run on a computer, the computer can execute the method described in any one of the above aspects.

[0059] In a ninth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method described in any one of the above aspects.

[0060] In a tenth aspect, a communication system is provided, comprising a terminal for executing any possible implementation of the first aspect, and a network device for executing any possible implementation of the second aspect. Alternatively, the communication system comprises a terminal for executing any possible implementation of the third aspect, and a network device for executing any possible implementation of the fourth aspect.

[0061] Among them, the technical effects brought about by any possible implementation method in the second to tenth aspects can refer to the technical effects brought about by different possible implementation methods in the above-mentioned first aspect, and will not be repeated here.

[0062] It is understandable that, provided that the solutions are not contradictory, the solutions in each aspect can be combined. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0064] FIG2 is a schematic diagram of a method for establishing or updating an instant group communication provided in an embodiment of the present application;

[0065] FIG3 is a schematic diagram of the architecture of a communication device provided in an embodiment of the present application;

[0066] FIG4 is a flow chart of a communication method provided in an embodiment of the present application;

[0067] 5-8 are flowcharts 1 to 4 of another communication method provided in an embodiment of the present application;

[0068] FIG9 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0069] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0070] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0071] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0072] First, a brief introduction to the implementation environment and application scenarios of the embodiments of the present application is given.

[0073] The communication method provided in the embodiments of the present application can be applied to the MC communication system shown in Figure 1. As shown in Figure 1, the communication system may include an MC server (Mission Critical Service Server, MC Service Server / MC server) and a terminal, wherein an MC client (Mission Critical Service Client, MC Service Client / MC client) can be installed or integrated on the terminal.

[0074] A terminal is a device with wireless transceiver capabilities and may also be referred to as user equipment (UE), terminal device, mobile station, mobile terminal, access terminal device, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal device, mobile device, UE terminal device, wireless communication device, machine terminal, UE agent, or UE device. A terminal can be fixed or mobile. It can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships); or it can be deployed in the air (such as on aircraft, balloons, and / or satellites). The terminal may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a terminal in industrial control, a vehicle-mounted terminal device, a terminal in self-driving, a terminal in assisted driving, a terminal in remote medical care, a terminal in smart grid, a terminal in transportation safety, a terminal in smart city, a terminal in smart home, etc. The embodiments of the present application do not limit the application scenarios.

[0075] The MC server is mainly responsible for call control and media control, service authorization or user registration, etc., and can be a logical entity. In a specific implementation, the corresponding MC server may be different depending on the MC service. For example, the MC servers corresponding to the MCPTT service, MCVideo service and MCData service can be MCPTT servers, MCVideo servers or MCData servers, etc. Alternatively, the processing functions of different MC services may be integrated into the same server, which is not limited in this application.

[0076] The MC client is primarily responsible for processing application-layer transactions, including service registration, security authentication, authorization, call control, location management, or media processing. The MC client can be a software program module on the terminal, serving as a system application of the terminal's operating system, a post-installed application (APP), a runtime library within the software, or a software development kit (SDK). An MC user is a user who uses an MC terminal to complete MC tasks, and an MC terminal is a terminal with an MC application installed. An MC user can use an MC terminal to communicate with an MC server.

[0077] For example, the MC client can interact with the MC server through the MCPTT-1 interface (or reference point) to implement call creation, update, release, etc., or implement location management, such as accepting location reporting configuration from the MC server and reporting location information to the MC server. In addition, the MC client can interact with the MC server through the MCPTT-7 / 8 interface to implement media processing, such as receiving, sending, or encoding and decoding of media data. The MC client can receive broadcast and multicast data through MCPTT-8.

[0078] Optionally, as shown in Figure 1, the MC server may include a transmission control server (or floor control server), which refers to a media transmission control entity on the media plane and is primarily responsible for uplink and / or downlink transmission control of the media. In the following embodiments of the present application, when a network device (or server) sends transmission control signaling to a terminal, or when a network device (or server) receives transmission control signaling from a terminal, unless otherwise specified, the network device (or server) may specifically refer to a transmission control server.

[0079] Optionally, as shown in Figure 1, the MC server may include a media distribution function entity (MDF), which may be a logical entity responsible for receiving uplink media data and sending downlink media data. In the following embodiments of the present application, when a terminal sends media data to a network device (or server), or when a network device (or server) sends media data to a terminal, unless otherwise specified, the network device (or server) may specifically refer to the MDF entity.

[0080] Optionally, as shown in FIG1 , the MC client may include a transmission control participant (Transmission control participant / Floor participant), which refers to a media transmission control entity on the media plane, responsible for uplink and / or downlink transmission control of the media, and may serve as a peer entity of the media control server on the terminal side.

[0081] Optionally, as shown in FIG1 , the MC client may include a media mixing function (Media mixer), which is responsible for processing media packets and may serve as a peer entity of the media distribution function entity on the terminal side.

[0082] MC communication can include an Ad hoc group call mode, which can establish an MC communication connection between a terminal user and an MC server. Specifically, the call initiating user can send an Ad hoc group call request (or Ad hoc group call update request) to the MC server to select a group of called users to join the Ad hoc group.

[0083] Specifically, there are currently two ways to establish / update the instant group communication mode:

[0084] Method 1: The call-initiating user terminal can provide the MC server with a user list (e.g., a user list) of the called users. For example, as shown in Figure 2, User Terminal 1 requests the MC server to initiate a group call. The user list it carries may include designated user terminals, such as User Terminal 2, User Terminal 3, and User Terminal 4. Based on the user list, the MC server can trigger requests to these user terminals to join the group call, thus implementing an instant group communication service.

[0085] Method 2: The call-initiating user terminal or the authorized user terminal can provide user screening criteria, allowing the MC server to automatically identify a group of users that meet the criteria based on the user screening criteria to initiate a group call request and add them to the group call. For example, as shown in Figure 2, the user screening criteria can specifically be a location condition. The MC server can add users that meet the location condition to the group call and remove users that do not meet the location condition from the group call.

[0086] For example, in conjunction with the communication system shown in Figure 1, terminal 1 can send an instant group communication request message (such as an ad hoc group call request) to the MC server, carrying the user list shown in the above method 1, requesting the MC server to add users to the group call according to the user list; or, the request message can carry the user screening rules described in the above method 2, requesting the MC server to automatically add or remove users from the group call according to the user screening rules. Then, the MC server can send an instant group communication request to terminal 2, terminal 3 and other user terminals based on the instant group communication request. The group call is successfully established, and the media plane and voice control plane are established. The users in the group call can use the voice control mechanism to conduct instant communication.

[0087] Subsequently, the call initiating user terminal or the authorized user terminal can modify the user list in the group call, such as adding or removing users; in addition, the call initiating user terminal or the authorized user terminal can modify or update the user screening rules, so that the MC server can continue to screen users in the group according to the updated rules, such as removing users who do not comply with the rules, adding other users who comply with the rules, etc.

[0088] However, in actual applications, the above implementation methods all have certain limitations and cannot meet the diverse needs of users. The group calling method based on the user list is difficult to add all relevant users who meet specific conditions to the group. For example, the user list of users in a certain area is constantly changing due to user movement. When the number of users in the user list is large, the user list is long and the corresponding indication overhead is large. The group calling method based on user screening rules is not accurate and flexible enough. When the call initiator needs to add or remove one or more specific users, it cannot be achieved by adding or updating rules.

[0089] It should be understood that the communication system shown in FIG1 of the present application is for illustrative purposes only and is not intended to limit the technical solutions of the present application. Those skilled in the art should understand that, in a specific implementation, the communication system may further include other network elements or devices, and the number of nodes may also be determined based on specific needs without limitation.

[0090] Optionally, each network element or device in Figure 1 of the present application may also be referred to as a communication device, which may be a general device or a dedicated device, and the present application does not make any specific limitations on this.

[0091] Optionally, the relevant functions of each network element or device in Figure 1 of the present application can be implemented by a single device, or by multiple devices, or by one or more functional modules within a single device, and this application does not impose any specific restrictions on this. It is understood that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0092] In specific implementations, each network element or device in Figure 1 of this application may adopt the structure shown in Figure 3, or include the components shown in Figure 3. Figure 3 shows a schematic diagram of the hardware structure of a communication device applicable to this application. The communication device 300 includes at least one processor 301 and at least one communication interface 304, which are used to implement the methods provided in this application. The communication device 300 may also include a communication circuit 302 and a memory 303.

[0093] The processor 301 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0094] The communication link 302 may include a path for transmitting information between the above components, such as a bus.

[0095] Communication interface 304 is used to communicate with other devices or communication networks. Communication interface 304 can be any transceiver-like device, such as an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, a transceiver, a pin, a bus, or a transceiver circuit.

[0096] The memory 303 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this. The memory can be independent and coupled to the processor 301 via a communication line 302. The memory 303 can also be integrated with the processor 301. The memory provided in this application can generally be non-volatile.

[0097] Among them, the memory 303 is used to store computer-executable instructions involved in executing the solution provided by this application, and is controlled by the processor 301. The processor 301 is used to execute the computer-executable instructions stored in the memory 303, thereby implementing the method provided by this application. Alternatively, optionally, in this application, the processor 301 may also perform processing-related functions in the method provided in the following embodiments of this application, and the communication interface 304 is responsible for communicating with other devices or communication networks, which is not specifically limited in this application.

[0098] Optionally, the computer-executable instructions in this application may also be referred to as application code, which is not specifically limited in this application.

[0099] The coupling in this application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.

[0100] As an embodiment, the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3 .

[0101] As an embodiment, the communication device 300 may include multiple processors, such as processor 301 and processor 307 in Figure 3. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0102] As an embodiment, the communication device 300 may further include an output device 305 and / or an input device 306. The output device 305 is coupled to the processor 301 and can display information in a variety of ways. For example, the output device 305 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 306 is coupled to the processor 301 and can receive user input in a variety of ways. For example, the input device 306 can be a mouse, a keyboard, a touch screen device, or a sensor device.

[0103] It is understandable that the composition structure shown in Figure 3 does not constitute a limitation on the communication device. In addition to the components shown in Figure 3, the communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0104] The method provided by the present application will be described below with reference to the accompanying drawings. Each network element in the following embodiment may include the components shown in FIG3 , which will not be described in detail.

[0105] It can be understood that the message names between network elements or the names of parameters in the messages in the following embodiments of the present application are only examples, and other names may be used in specific implementations, and the present application does not make any specific limitations on this.

[0106] It is understood that the "embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It is understood that in the various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the present application.

[0107] It can be understood that in this application, "when", "if" and "if" all mean that corresponding processing will be taken under certain objective circumstances, and do not limit the time, nor do they require judgment actions when implementing them, nor do they mean that there are other limitations.

[0108] The term "simultaneously" in this application may be understood as at the same time point, within a period of time, or within the same cycle.

[0109] It is understood that some optional features in this application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in certain scenarios as needed. Accordingly, the devices provided in this application may also implement these features or functions accordingly, which will not be described in detail here.

[0110] It is understandable that the same step or steps or technical features with the same function in different embodiments of the present application can be referenced to each other.

[0111] It can be understood that in this application, "sending certain information (such as a first message) to (such as a first device)" can be understood as the destination end of the information being the first device. It can include sending the information to the first device directly or indirectly. "Receiving certain information (such as a first message) from (such as a second device)" can be understood as the source end of the information being the second device, which can include receiving information from the second device directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated here.

[0112] It is understood that the method provided below in this application uses a node or communication device as an example to illustrate the method, but this application does not limit the execution subject of the interaction diagram. For example, the method executed by the communication device in this application can also be executed by a module of a network device (such as a chip, chip system, or processor), and can also be implemented by a logical node, logical module, or software that can implement all or part of the functions of the network device.

[0113] The present application provides a communication method, which, through terminal-side functional enhancement or server-side functional enhancement, enables flexible configuration and flexible update of participating users in a group call by combining the above two methods. For example, the terminal can establish a group call through a user list, and can also update the participating users in the group call through user screening rules. The two methods are implemented simultaneously and do not conflict. Similarly, the terminal can establish a group call through user screening rules, and can also update the participating users in the group call (such as adding and removing users) by updating the user list. The two methods can be implemented simultaneously and do not conflict.

[0114] As shown in Figure 4, the communication method provided in the embodiment of the present application can be applied to a terminal and a network device, wherein the network device can be the MC server in the communication system of Figure 1, and the terminal can be the user terminal including the MC client in Figure 1. The method can include the following steps.

[0115] 401: The terminal sends a first message to a network device to update users in a first group call.

[0116] Specifically, the terminal may generate a first message based on the service requirements of the group call, the first message being used to update users in the first group call, the first message including identifiers of users to be added and / or identifiers of users to be removed, and then send the first message to the network device.

[0117] Exemplarily, the first message can specifically be a group call establishment request message for the first group call, for example, an instant group communication request (such as an ad hoc group call request) message, then the first message can include a list of users to be added (such as a user list), and the user list can include identifiers of multiple users to be added. At this time, updating the users in the first group call can also be expressed as / understood as creating a new first group call and inviting the users to be added to join the call (or understood as creating a first group call with the users to be added as the initial call users). The message can be implemented by an INVITE message of the Session Initialization Protocol (SIP).

[0118] Alternatively, the first message may also be a group call update request message for the first group call, used to update the participating users (participants) in the established first group call. For example, the first message may be an instant group communication update request (Modify ad hoc group call request) message, instructing the network device to add users to the group call or remove participating users in the group call.

[0119] For example, the first message may include information of users to be added, including information of at least one user to be added, which may be a list of users (such as list of user to be added), or the first message may include information of users to be removed, including information of at least one user to be removed, which may be a list of users (such as list user to be removed), or the first message may include information of users to be added (such as list of user to be added) and information list of users to be removed (such as list of user to be removed).

[0120] For the implementation method in which the first message is a group call update request message, the implementation process of establishing the first group call may also be included before step 401. The initiating terminal of the first group call can be the aforementioned terminal such as the first terminal, or it can also be another terminal, such as the second terminal. That is to say, the call initiating user who initiates the first group call and the user who initiates the participant update of the subsequent first group call can be the same user, or different users. Generally, different users use different terminals, and there are also scenarios of shared terminals, that is, the call initiating user and the user who initiates the call participant update use the same terminal, that is, the terminal in the aforementioned 401. In the present invention, one user using one terminal is used as an example for explanation, so the terminal and the user can be used interchangeably. This application does not limit this. The following embodiments are only implemented with the same terminal as an example, and do not constitute a limitation to the implementation methods of this application.

[0121] Subsequently, steps 400-1a and 400-1b describe the process of establishing a group call by providing a user list for addition via the terminal. Steps 400-2a and 400-2b describe the process of establishing a group call by providing user screening rules via the terminal. For example, the terminal may request the establishment of a first group call based on a first rule. The first rule enables the server to automatically add users who meet the first rule to the first group call based on the first rule. After the call is established, participating users who do not meet the corresponding first rule are removed from the first group call. This description is omitted here.

[0122] In one embodiment, through terminal-side functional enhancement, the terminal can carry corresponding user attributes for the user to be updated in the first message, so as to indicate that the network device's update operation on the user is not affected by the update method of user screening rules (i.e., the server manages the participating users of the first group call according to the user screening rules).

[0123] Optionally, the first message may further include user attributes of the user to be added and / or user attributes of the user to be removed, wherein the user attributes may indicate the continued existence requirements or update characteristics of the user (the user to be added and / or the user to be removed) in the first group call.

[0124] Specifically, the user attribute of the user to be added may be a first attribute, which may be used to indicate that the user to be added is a necessary user in the first group call (e.g., used to indicate that the user is always-in, keep-in, or required). In other words, the user to be added is a necessary user in the first group call, and before the first group call ends, the user to be added remains (last, sustain, persist, or preserve) in the first group call, or the user to be added cannot be removed before the first group call ends. When the user to be added is successfully added to the first group call, it becomes a participating user in the first group call.

[0125] It should be understood that the first attribute can also be used to indicate that the user to be added is not subject to any user screening rule corresponding to the first group call, that is, any user screening rule corresponding to the first group call is not effective or applied to the user to be added (the user marked with the first attribute). That is to say, when the network device automatically filters users according to the user screening rule corresponding to the first group call and updates the participating users in the first group call, even if a terminal (such as a user to be added that is successfully added to the group call as a participating user) does not meet the user screening rule, if the terminal is marked with the first attribute, it means that the terminal is a necessary user in the first group call. Therefore, the network device can retain the terminal in the first group call, do not apply the user screening rule to the terminal, and remove it. Among them, the user screening rules that currently exist and may be added in the future corresponding to the first group call are not applied to the user to be added.

[0126] Correspondingly, for a user to be removed, the corresponding user may be a second attribute, which may be used to indicate that the user to be removed is a released user in the first group call (e.g., used to indicate to be removed or keep-out), or a user to be removed unconditionally. The user to be removed is a participating user in the first group call. In other words, the user to be removed is no longer a necessary user in the first group call.

[0127] It should be understood that the second attribute can also be used to indicate that the user to be removed is not subject to any user screening rule corresponding to the first group call, that is, any user screening rule corresponding to the first group call is not effective or applied to the user to be removed (the user marked with the second attribute). In other words, the user to be removed is not allowed to be added to the first group call by the network device according to the user screening rule corresponding to the first group call. Even if a terminal (such as the user to be removed) meets the user screening rule, if the terminal is marked with the second attribute, it means that the terminal is not a necessary user in the first group call. Therefore, the network device may not add the terminal to the first group call. Among them, the user screening rules that currently exist and may be added in the future corresponding to the first group call are not applied to the user to be removed.

[0128] It should be noted that, if the user to be removed has the second attribute and needs to be added to the first group call, he or she can be added to the first group call again by other users / terminals through the to-be-added user list (add user list).

[0129] It should be understood that the above-mentioned multiple descriptions of the first attribute or the second attribute can coexist or be implemented one by one, and this application does not limit this.

[0130] It should be noted that in the above embodiments of the present application, the user attribute may be a first attribute or a second attribute, where the first attribute and the second attribute may be the same information or different information. In a specific embodiment, a specific indication bit may be set in the first message to indicate the first attribute and / or the second attribute.

[0131] Exemplarily, taking MCPTT as an example, the following Table 1 shows the information elements included in the instant group communication update request message in the MCPTT service.

[0132] Table 1

[0133] Among them, for the information elements with a status of "optional" in Table 1, the instant group communication update request message may or may not carry this information element; for the information elements with a status of "mandatory", the instant group communication update request message usually carries this information element. The following other tables are also applicable and will not be repeated here.

[0134] In Table 1, if the user attribute is used to indicate that the update of the user is not affected by the user screening rule, such as the user attribute does not distinguish between the first attribute and the second attribute, then the user attribute can be effective for each user in the user list of users to be added and the user list of users to be removed in Table 1, that is, each user in the above two user lists has the user attributes in the above table.

[0135] Alternatively, the terminal may also indicate corresponding user attributes (per user) based on different users. Taking the following Table 2 as an example, the user may be identified by the MCPTT ID, that is, the MCPTT ID is associated with the user attributes, and different users (MCPTT IDs) correspond to different user attributes. For example, the terminal may set the MC client to set the user attributes of the selected users to the first attribute by selecting some users as necessary users in the group call. That is, among the users to be added, as shown in the following Table 2, some users have the first attribute, and some users may not have the user attribute such as the first attribute. Alternatively, the terminal may set the MC client to set the user attributes of the selected users to the second attribute by selecting some users as users to be removed from the group call, and who are non-essential users. As shown in the following Table 2, for the users to be added, some users have user attributes such as the second attribute, and some users may not have indicated user attributes such as the second attribute.

[0136] Table 2

[0137] In one embodiment, the terminal can receive the user's selection through the interactive interface of the MC client and set the user attributes of the users in the group call. For example, the user can determine the user attributes of the users in the currently initiated group call by checking the box, such as checking the user attributes of some users as the first attribute, the user attributes of some users as the second attribute, and some users without user attributes.

[0138] Alternatively, in another example, the terminal may further indicate corresponding user attributes based on the user list as a whole (per list), taking the following Table 3 as an example, where the user list of the user to be added corresponds to the first attribute, and the user list of the user to be removed corresponds to the second attribute. For example, the terminal may set user attributes for all user lists of instant group call services (such as Ad-hoc group call) by default, such as setting user attributes for the user list of the user to be added, such as setting the first attribute by default; and setting user attributes for the user list of the user to be removed, such as setting the second attribute by default.

[0139] Table 3

[0140] In one embodiment, the terminal may request the network device to establish a first group call using the aforementioned method 1 (specifying a user list) or method 2 (specifying a user screening rule), and may send the group call establishment request to the network device, such as the first terminal or the second terminal sending a second message or a third message to the network device. Specifically, the following steps may be included.

[0141] 400-1a: The terminal sends a second message to the network device, including the identifier of the target user.

[0142] 400-1b: The network device adds the target user to the first group call, and establishes the first group call.

[0143] The terminal sends a second message to the network device, corresponding to the method of requesting to establish a group call based on the user list in the above-mentioned method 1. The second message may include an identifier of at least one target user, which is used to request to add the target user to the first group call to establish the first group call.

[0144] Specifically, the network device receives the second message from the terminal, and sends a group call establishment request to the corresponding target user (such as at least one other terminal) based on the identifier of the target user carried, such as sending an instant group communication request (such as an ad hoc group call request) message. The target user receives the group call establishment request and can feedback a group call establishment response to the network device, such as accepting or rejecting access to the group call.

[0145] Furthermore, the network device can also assign a group identifier to the group call, and the group call establishment request sent to the target user can carry the group identifier. In one example, the network device assigns a group identifier to the group call, which can be considered as establishing a first group call, and then adding the target user to the first group call. In another example, the network device assigns a group identifier to the group call, adds all necessary users to the first group call, and is considered to be call establishment completed. In another example, the network device assigns a group identifier to the group call, adds all necessary users to the first group call, and returns a response to the call establishment request to the initiating user, which is considered to be call establishment completed. This application does not make specific limitations on this.

[0146] For example, a group call corresponds to information that uniquely identifies the group call, such as a first group call corresponding to a first identifier. The first identifier may be generated by the user terminal initiating the group call, or may be generated by a network device such as an MC server. The first message in step 401 may carry the first identifier to indicate that the participating users in the first group call corresponding to the first identifier should be updated based on the first identifier.

[0147] 400-2a: The terminal sends a third message to the network device, including information about the first rule.

[0148] For example, the MC client on the terminal can provide users with multiple different user screening rules through the interface display, and the user can click and select to add the first rule through the human-computer interaction interface. Optionally, the parameter value corresponding to the first rule can also be set, such as the parameters of the location area.

[0149] Optionally, the first rule may also be configured with attributes, such as indicating that target users added to the group call according to the first rule also possess a "permanent" attribute (such as the aforementioned first attribute), and cannot be removed based on not meeting other user screening rules. Furthermore, the user may also configure the first rule to be read-only (non-modifiable) or modifiable, which prevents the relevant parameter values ​​of the first rule from being modified.

[0150] 400-2b: The network device adds the target users meeting the first rule to the first group call, and establishes the first group call.

[0151] The terminal sends a third message to the network device, corresponding to the aforementioned method 2, in which the terminal requests to establish a group call based on specific user screening rules. The third message may include information about one or more user screening rules, where the user screening rules are used by the network device to automatically update participating users in the group call. For example, the first message may carry information about a first rule, requesting that the network device automatically add target users that meet the first rule to a first group call to establish the first group call.

[0152] Specifically, the network device receives the third message from the terminal, filters out target users that meet the first rule according to the carried first rule, and sends a group call establishment request to the corresponding target user (such as at least one other terminal), such as sending an instant group communication request (such as an ad hoc group call request) message. The target user receives the group call establishment request and can feedback a group call establishment response to the network device, such as accepting or rejecting access to the group call.

[0153] Exemplarily, a user screening rule (criteria) may indicate a location area. For example, a first rule may carry latitude and longitude information corresponding to the location area or relative location information with respect to the call initiating user terminal (for example, the coordinates and radius value of the initiating user terminal, or specified coordinates and radius value). The network device may obtain the locations of other terminals, and then determine whether the terminal is located within the location area specified by the user screening rule based on the locations of the other terminals. If the terminal is within the specified location area, the network device may send a group call establishment request to the target user terminal to add the target user to the first group call.

[0154] In one embodiment, the network device can continuously detect users who meet or do not meet the user screening rules during the life cycle of the group call, such as through periodic scanning or regular detection. The network device adds target users who meet the first rules to the first group call and removes users who do not meet the first rules from the first group call.

[0155] Optionally, during the duration of the group call, the initiating user of the group call or other authorized users may modify the user screening rules corresponding to the first group call, such as modifying the relevant parameter values ​​of the first rule, such as narrowing or expanding the location area, or modifying the latitude and longitude values. Modifying the user screening rules requires the network device to re-evaluate the participating users in the group call, add some other users who meet the modified first rule to the group call (specifically, by sending an ad hoc group call request message), and remove some users who no longer meet the modified first rule from the group participants (specifically, by sending an ad hoc group call remove or ad hoc group call leave request message).

[0156] 402: The network device adds the user to be added to the first group call according to the first message, and / or removes the user to be removed from the first group call.

[0157] Correspondingly, the network device receives the first message from the terminal, adds the user to be added to the first group call according to the first message, and / or removes the user to be removed from the first group call (which may be the participating user provided by the terminal to be added, or the participating user added to the call by the network device via the user screening rules).

[0158] The network device determines user attributes of a user to be added, and / or determines user attributes of a user to be removed.

[0159] In the embodiment of the present application, the network device determines the user attributes of the user to be added / removed, specifically in the following two ways.

[0160] Method 1: The request message sent by the terminal carries the user attributes of the user to be added and / or the user attributes of the user to be removed. The request message sent by the terminal can be the first message and / or the second message.

[0161] That is, in the aforementioned implementation method of enhancing the terminal side's functions, when the terminal sends a request message to establish / update a group call to the network device, it can carry user attributes, so that the network device determines the user attributes corresponding to the user based on the received user attributes for subsequent update operations or continued needs.

[0162] Exemplarily, the first message may include: the user attribute of the user to be added is a first attribute, and / or the user attribute of the user to be removed is a second attribute.

[0163] Optionally, the second message in the above step 400-1a may also carry user attributes, that is, the first group call is initially established by specifying a user list. When the terminal sends a group call establishment request message to the network device, user attributes, such as the first attribute, may be indicated for some or all of the users to be added.

[0164] Method 2: The network device automatically generates user attributes corresponding to the user according to the request message received from the terminal. The request message sent by the terminal can be the first message and / or the second message.

[0165] That is, the aforementioned implementation method for enhancing the functionality of the network device side is that the network device can automatically generate corresponding user attributes for the users to be added or removed carried in the request message for establishing / updating a group call based on the message received from the terminal, for marking, indicating subsequent update operations or continued needs for the user.

[0166] For example, the network device may generate a first attribute of a user to be added and / or generate a second attribute of a user to be removed based on the first message.

[0167] Optionally, for the above step 400 - 1b, when the terminal initially establishes the first group call by specifying a user list, the network device may automatically generate a second attribute corresponding to the user according to the received second message.

[0168] It should be noted that the user attributes generated by the network device side, such as the first attribute for adding a user tag and / or the second attribute for removing a user tag, can refer to the aforementioned introduction to the first attribute and the second attribute, and will not be repeated here.

[0169] In one embodiment, the network device may store a user list corresponding to the first group call and user attributes corresponding to the users in the user list. Furthermore, the network device may store a first attribute in the first group call and a user list corresponding to the first attribute. Furthermore, the network device may store a second attribute in the first group call and a user list corresponding to the second attribute.

[0170] Subsequently, when the network device regularly performs user screening according to user screening rules such as the first rule, it can make decisions based on the relevant information of the above-mentioned saved user attributes, thereby updating the participating users in the first group call. Specifically, the network device can add the target users that meet the first rule to the first group call, and remove the users that do not meet the first rule from the first group call. Further, the network device can save the target users that meet the first rule and their attributes (if they have the first attribute) in the user list corresponding to the first group call, or save the target users that meet the first rule in the user list corresponding to the first attribute. The network device removes the users that do not meet the first rule from the first group call, further including the network device deleting the users that do not meet the first rule from the user list corresponding to the first group call, or deleting them from the list corresponding to the user list corresponding to the second attribute. When different lists are used for different attributes, when the network device updates the user according to the attribute, the network device can only operate on a specific attribute and its corresponding user list, and will not check or process the user lists corresponding to other attributes.

[0171] If the user attribute corresponding to the first user in the first group call is the first attribute, the first user is retained in the first group call. The first user may be a to-be-added user included in the first message in step 401, and is added to the first group call via the first message request. In one example, the user attribute corresponding to the first user is the first attribute. When the network device selects participating users according to the first rule, even if the first user does not meet the first rule, the network device still retains the first user in the first group call because the first user possesses the first attribute.

[0172] Additionally, if the second user satisfies the first rule and the user attribute corresponding to the second user is the second attribute, the second user is removed from the first group call, or the network device is not allowed to add the second user to the first group call based on the first rule being satisfied. The second user may be a user to be removed included in the first message in step 401, and the first message requests removal of the second user from the first group call. Optionally, the second user with the second attribute can be added to the first group call by other users or terminals through an add user list.

[0173] In one embodiment, after the above step 402 is completed, the network device may feed back the execution result to the terminal. The communication method may further include the following steps.

[0174] 403: The network device sends a response message to the terminal, indicating the result of the user update in the first group call.

[0175] Exemplarily, the network device may send a response to the first message, an acknowledgment (ACK) response to the first message, or a notification message to the terminal, indicating that the update operation requested by the terminal was successfully completed or failed. Alternatively, the network device may send a non-acknowledgment (NACK) response to the terminal, indicating that the update operation requested by the terminal failed. Optionally, when the response message indicates that the update operation failed, the response message may also include a reason for the failure.

[0176] Alternatively, the network device may send to the terminal a user identifier successfully added to the first group call and / or a user identifier successfully removed from the first group call. The network device may send the above information to the terminal in a response message to the first message or in a separate notification message. Furthermore, the network device may carry, together with the above information, an identifier corresponding to the first group call, such as a group identifier or at least one of a group call identifier and a group call session identifier.

[0177] In the above-mentioned implementation manner, the terminal side carries the corresponding user attributes for the users to be added and / or removed in the request message for updating the users in the group call, or the network device automatically generates the corresponding user attributes for the users to be added and / or removed based on the initial establishment or update request message. With these two implementation methods, the server processes the two methods of updating the participating users in the group call, namely, updating through the user list and updating through the user screening rules, without conflict. The two update methods can be implemented at the same time, and users can flexibly add or remove users in the group call according to these two methods without contradiction or conflict, thereby improving the flexibility and update efficiency of group call user updates, thereby improving the user experience.

[0178] Furthermore, referring to the aforementioned method of marking the first attribute for added users, in one possible implementation, the user screening rule corresponding to the group call may also be marked with first information to indicate that the target users screened according to the first rule are required users in the first group call. Consequently, the target users added to the first group call according to the first rule will all have the first attribute as their corresponding user attribute, i.e., they are required users in the first group call and will not be removed from the first group call by applying other user screening rules.

[0179] Exemplarily, when the terminal initially establishes a group call, that is, the aforementioned step 400-2a, the terminal sends a third message to the network device, including information of the first rule, wherein the third message may also include the first information, used to indicate that the target user screened according to the first rule is a necessary user in the first group call, for example, the first information is set to be permanent (always-in).

[0180] In addition, authorized users of group calls can modify user screening rules for group calls or add additional user screening rules. For example, if a group call initiating user terminal, such as a first terminal, configures a first rule for a first group call, a second terminal can subsequently update the first rule during the group call, such as by modifying the location area parameter value mentioned above. Alternatively, the second terminal can add a second rule to the first group call to update the participating users in the first group call.

[0181] In one embodiment, the communication method may further include the following steps.

[0182] The terminal can send a fourth message to the network device, wherein the fourth message includes information of the second rule, or includes update information of the first rule, and the information or update information of the second rule is used to update the users in the first group call; wherein the second rule is one of the user screening rules, and the information of the second rule is used to add users who meet the second rule to the first group call, and remove participating users who do not meet the second rule from the first group call.

[0183] In one embodiment, the third message also includes second information indicating whether the attribute of the first rule is read-only or modifiable. The network device may store this second information. If the attribute of the first rule is read-only, the network device may not subsequently update the first rule. If the attribute of the first rule is modifiable, the network device may subsequently modify the first rule based on the updated information of the first rule, so that the network device can screen the participating users of the first group call based on the updated first rule, add target users that meet the updated first rule, and remove users that do not meet the updated first rule.

[0184] For example, if the original parameter 1 corresponds to the first rule, the update information of the first rule may indicate that the parameter 1 corresponding to the first rule is modified to parameter 2.

[0185] Further optionally, the second information may also be used to indicate information of a user who is authorized to modify the first rule, such as a user identifier.

[0186] For example, if the fourth message sent by the second terminal to the network device includes update information for the first rule, the network device may determine whether the first rule is allowed to be modified and whether it is allowed to be modified by the second terminal. If it is determined that the first rule is allowed to be modified by the second terminal, the network device may update the first rule according to the update information and update the participating users in the first group call according to the updated first rule.

[0187] Below, several implementation methods provided by this application will be introduced in combination with the specific implementation process, taking the MCPTT service as an example and the interaction between the terminal (specifically, the MC client) and the server (specifically, the MC server) as an example.

[0188] Embodiment 1: The terminal side adds user attributes for users to be added and / or users to be removed.

[0189] As shown in FIG5 , the communication method may include the following steps.

[0190] 501: The first terminal sends an instant group communication request message to the server.

[0191] The group call initiating user terminal, ie, the first terminal, sends an ad hoc group call request message to the server. The request includes a list of users to be added to the group call, and is used to request the establishment of the group call.

[0192] Exemplarily, the user list may include user identifiers corresponding to the second terminal, the third terminal, and the fourth terminal.

[0193] Optionally, the request may include as a first attribute the user attributes corresponding to all users in the user list, or may include as a first attribute the user attributes corresponding to some users in the user list. The first attribute is used to indicate that the user is a required user in the currently initiated group call and that user screening rules are not permitted to be applied to remove the user from the group call. The function of other information indicating the first attribute can be found in the aforementioned content and will not be further elaborated here.

[0194] 502: The server performs an authorization check and the authorization is passed.

[0195] Specifically, the server performs an authorization check on the request message, and when it is determined that the first terminal is authorized to execute the request, it is determined that the authorization is passed.

[0196] In addition, the server stores the group call identifier (ad hoc group ID), such as the identifier of the first group call, and stores the corresponding user list and related user attributes. The group call identifier may be carried in the request message of step 501, or may be automatically configured by the server.

[0197] 503: The server sends an instant group communication return message to the first terminal.

[0198] Specifically, the server may return an instant group communication return (ad hoc group call request return) message to the group call initiating user terminal, ie, the first terminal. The return message may include an identifier of the group call (ad hoc group ID) and an authorization result.

[0199] Optionally, the return message may further include a pre-configured group ID, where the group ID is used to indicate configuration information of the instant group communication, and the configuration information in the pre-configured group is used.

[0200] 504a: The server sends an instant group communication request message to the second terminal.

[0201] 504b: The server sends an instant group communication request message to the third terminal.

[0202] 504c: The server sends an instant group communication request message to the fourth terminal.

[0203] Specifically, the server may send an instant group communication request message to the users in the user list in step 501 to request access to the group call. The request message may include a group call identifier (ad hoc group ID) and a pre-configured group identifier (group ID).

[0204] 505a: The second terminal sends a message to the server indicating receipt of the instant group communication request.

[0205] 505b: The third terminal sends a message to the server indicating receipt of the instant group communication request.

[0206] 505c: The fourth terminal sends a message to the server indicating that an instant group communication request has been received.

[0207] 506a: The second terminal sends an instant group communication response message to the server.

[0208] The response message is used to instruct the second terminal to accept or reject the group call.

[0209] 506b: The third terminal sends an instant group communication response message to the server.

[0210] The response message is used to instruct the third terminal to accept or reject the group call.

[0211] 506c: The fourth terminal sends an instant group communication response message to the server.

[0212] The response message is used to instruct the fourth terminal to accept or reject the group call.

[0213] 507: The server sends an instant group communication response message to the first terminal, indicating that the call is successfully established.

[0214] Optionally, the response message may further include information such as user terminals that have joined the group call session, user terminals that have not joined the group call session, or user terminals that refuse to accept the group call.

[0215] 508: The server sends a notification message to the first terminal.

[0216] Optionally, if the users designated by the first terminal to join the group call do not respond to the group call within a specified time, the server may notify the first terminal of which designated users have not responded to the call within the specified time through a notification message.

[0217] 509: The media plane and voice control plane are established.

[0218] After the media plane and voice control plane are established, users in the group call can use the voice control mechanism to speak and communicate in the group.

[0219] 510: The first terminal sends an instant group communication update request message to the server.

[0220] According to the service requirements of the group communication, the first terminal wishes to update the participating users in the current first group call, and may update the users through the first rule, or through the list of users to be added and / or the list of users to be removed.

[0221] For example, step 510 in this embodiment is described by taking the updating method of adding the first rule as an example. The following step 513 is described by taking the updating method of adding the list of users to be added / removed as an example.

[0222] For example, the instant group communication update request message may include information about the first rule. Specifically, the instant group communication update request message may be a modify ad hoc group call criteria message or a modify ad hoc group call participant message.

[0223] Optionally, the instant group communication update request message may further include first information, where the first information is used to indicate that the target user determined according to the first rule is a necessary user in the first group call.

[0224] Optionally, the server may save the first rule corresponding to the first group call and the first information corresponding to the first rule.

[0225] 511: The server updates the users in the group call according to the first rule.

[0226] Specifically, the server adds users who meet the first rule to the first group call according to the first rule, and removes participating users who do not meet the first rule from the first group call. Specific processing may include the following.

[0227] 1. For a user marked with the first attribute, the server does not apply the first rule to the user.

[0228] That is, if the first user is marked with the first attribute, even if the first user does not meet the first rule, the server will not remove the first user from the first group call, that is, the server will retain the first user in the first group call.

[0229] Exemplarily, the server may first determine that the user attribute of the first user is the first attribute based on the stored user list corresponding to the first attribute, and then the server may no longer verify the first user according to the first rule and retain the first user in the first group call.

[0230] Alternatively, the server may first verify whether the first user meets the first rule according to the first rule, then query the user attribute of the first user, determine that the first user corresponds to the first attribute, and then retain the first user in the first group call.

[0231] 2. For users who do not mark the first attribute, the server applies the first rule.

[0232] For users not marked with the first attribute, the server may apply the first rule to remove users who do not meet the first rule from the first group call.

[0233] 3. If the first rule is associated with the first information, the server may also mark the target users added to the group call according to the first rule with the first attribute.

[0234] 4. During the group call, the server may regularly or periodically detect according to the first rule, add users that meet the first rule to the first group call, and remove participating users that do not meet the first rule from the first group call, except for users corresponding to the first attribute.

[0235] The operation of the server triggering the addition of other users to the first group call may refer to the aforementioned steps 504a-506a, 504b-506b or 504c-506c, which will not be repeated here.

[0236] In addition, the server removes a user who does not meet the first rule, such as the second user, from the first group call, which may include: the server sends an instant group removal request message to the second user's terminal, and then receives an instant group removal response message, thereby removing the terminal from the first group call.

[0237] 512: The server sends an instant group communication update response message to the first terminal.

[0238] Optionally, the server may send an instant group communication update response message to the first terminal, where the message may inform the first terminal of information such as which new users have joined the first group call, which users have been removed from the first group call, and so on.

[0239] 513: The first terminal sends an instant group communication update request message to the server.

[0240] In parallel with step 510, in this step, the first terminal or other authorized terminal may send an instant group communication update request message to the server, which may carry a list of users to be added and / or a list of users to be removed, to update the participating users in the first group call.

[0241] Alternatively, in another possible embodiment, the instant group communication update request message is only used to update the user attributes of some users in the group call. For example, the request message may carry the identifier of the user to be updated (the user in the first group call), and the user attribute corresponding to the user to be updated is the first attribute. Exemplarily, when the user initially establishes the group call, the user attribute of the user to be added is not marked as the first attribute. The update method described in step 513 can be used to update the user attribute of the user to the first attribute, so that the user can be used as a necessary user in the first group call without being affected by other user screening conditions. In this way, the user can flexibly set the update attributes of a specific user, thereby improving the flexibility and convenience of user updates in group calls.

[0242] Optionally, the instant group communication update request message sent by the first terminal may include a list of users to be added, including an identifier of at least one user to be added. Optionally, a first attribute corresponding to the user to be added may be included, indicating that the user to be added is a required user in the first group call, and that no user screening rules are allowed to be applied to remove the user from the first group call, and that no user screening rules currently in existence or to be added in the future will be applied to the user to be added.

[0243] Optionally, the instant group communication update request message sent by the first terminal may include a list of users to be removed, including an identifier of at least one user to be removed. Optionally, a second attribute corresponding to the user to be removed may be included, indicating that the user to be removed is a released user of the first group call, and that no user screening rules are allowed to be applied to add the user to the first group call, and that no user screening rules currently in existence or to be added in the future are applied to the user to be removed.

[0244] Exemplarily, in the instant group communication update request message, the user to be removed includes an identifier of the third terminal.

[0245] 514: The server sends an instant group communication removal request message to the third terminal.

[0246] Specifically, the instant group communication removal request message may be an ad hoc group call leave request message or an ad hoc group call remove request message.

[0247] 515: The third terminal sends an instant group communication removal response message to the server.

[0248] The response message may be used to indicate that the third terminal has received the instant group communication removal request message and has determined to be removed from the first group call.

[0249] 516: The server sends an instant group communication update response message to the first terminal.

[0250] Optionally, the server may send an instant group communication update response message to the first terminal, where the message may inform the first terminal of information such as which new users have joined the first group call, which users have been removed from the first group call, and so on.

[0251] Optionally, the aforementioned step 510 and step 513 may be combined into the same message for implementation.

[0252] In the above implementation, by carrying user attributes in the establishment request or update request message of the group call on the terminal side, the server can manage the participating users in the group call according to the user attributes, and does not apply user screening rules to them. Therefore, the update method of the user list and the update method of the user screening rules do not conflict, and can be applied to user management of the group call at the same time, thereby improving the flexibility and communication efficiency of the group call service.

[0253] Embodiment 2: The server generates user attributes for users to be added and / or removed according to a user list.

[0254] As shown in FIG6 , the communication method may include the following steps.

[0255] 601: The first terminal sends an instant group communication request message to the server.

[0256] The group call initiating user terminal, ie, the first terminal, sends an ad hoc group call request message to the server. The request includes a list of users to be added to the group call.

[0257] Exemplarily, the user list may include user identifiers corresponding to the second terminal and the third terminal.

[0258] 602: The server performs an authorization check and if the authorization is passed, generates and saves the first attribute for the user to be added.

[0259] The server automatically generates and stores a first attribute of the user to be added based on the list of users to be added received from the first terminal. For example, the first attribute can be marked as always-in or keep-in, or marked as not affected by user screening rules and not applied to user screening rules, etc., which is not limited in this application.

[0260] 603: The server sends an instant group communication return message to the first terminal.

[0261] 604a: The server sends an instant group communication request message to the second terminal.

[0262] 604b: The server sends an instant group communication request message to the third terminal.

[0263] 605a: The second terminal sends a message to the server indicating receipt of the instant group communication request.

[0264] 605b: The third terminal sends a message to the server indicating receipt of the instant group communication request.

[0265] 606a: The second terminal sends an instant group communication response message to the server.

[0266] 606b: The third terminal sends an instant group communication response message to the server.

[0267] 607: The server sends an instant group communication response message to the first terminal, indicating that the call is successfully established.

[0268] 608: The server sends a notification message to the first terminal.

[0269] 609: The media plane and voice control plane are established.

[0270] Refer to the aforementioned steps 603-609.

[0271] Optionally, the implementation process of establishing the above-mentioned group call can also be achieved by providing user screening rules through the terminal. The server can add users according to the user screening rules specified by the terminal, establish a first group call, and continuously update the participating users in the first group call according to the user screening rules.

[0272] 610: The first terminal sends an instant group communication update request message to the server.

[0273] Optionally, the instant group communication update request message may include the identifier of the user to be added and / or the identifier of the user to be removed, for requesting to add the user to be added to the first group call and / or for requesting to remove the user to be removed from the first group call.

[0274] 611: The server determines to update the users in the first group call.

[0275] At this point, the server can perform the following operations:

[0276] 1. For the user to be added in step 610, the server adds the user to be added to the first group call and marks the user attribute as the first attribute.

[0277] During the duration of subsequent group calls, regardless of whether user screening rules are added to the first group call in the aforementioned steps 601-609, or whether user screening rules are added to the first group call after step 610, user terminals marked with the first attribute are retained in the first group call, and user terminals marked with the first attribute are not applied to any user screening rule, that is, they are not allowed to be removed from the first group call due to failure to meet the user screening rules.

[0278] 2. For the user to be removed in step 610, the server removes the user to be removed from the first group call and marks the user attribute as the second attribute.

[0279] During the duration of subsequent group calls, regardless of whether user screening rules are added to the first group call in the aforementioned steps 601-609, or whether user screening rules are added to the first group call after step 610, user terminals marked with the second attribute will remain in the first group call, and user terminals marked with the first attribute will not be applied to any user screening rule, that is, they are not allowed to be removed from the first group call due to failure to meet the user screening rules.

[0280] Optionally, the server removes the user to be removed from the first group call and may no longer evaluate whether the user meets the user screening rules for these users. Alternatively, even if the user meets the user screening rules, the server will not proactively add the user terminal marked with the second attribute to the first group call, unless the server receives an update request from an authorized terminal and requests to add the user terminal to the first group call again by updating the user list.

[0281] Exemplarily, the instant group communication update request message includes that the identifier of the user to be added is the identifier of the fourth terminal. The communication method may specifically include the following steps.

[0282] 612: The server sends an instant group communication update request message to the fourth terminal.

[0283] Specifically, the request message may include a group call identifier (ad hoc group ID) and a pre-configured group identifier (group ID).

[0284] 613: The fourth terminal sends an instant group communication update response message to the server.

[0285] The response message may instruct the fourth terminal to accept or reject the group call.

[0286] The specific process may refer to the aforementioned steps 504a-506a, 504b-506b or 504c-506c, which will not be repeated here.

[0287] 614: The server sends an instant group communication update response message to the first terminal.

[0288] Optionally, the server may send an instant group communication update response message to the first terminal, which message may inform the first terminal of information such as which new users have joined the first group call, which users have been removed from the first group call, etc. Based on the above example, the response message may notify the first terminal that the fourth terminal has been successfully added to the first group call.

[0289] In addition, if the instant group communication update request message includes the user to be removed, the process of removing the user terminal may refer to steps 514-515 in the aforementioned embodiment, which will not be described in detail here.

[0290] In the above-mentioned embodiment, when a terminal establishes or updates users for a group call through a user list, the server can automatically generate corresponding user attributes for the added or removed users, or mark specific indication information, so that the server can manage the participating users in the group call without applying user screening rules to them. Therefore, the update method through the user list and the update method through the user screening rules do not conflict and can be applied to the user management of the group call at the same time, thereby improving the flexibility and communication efficiency of the group call service. In addition, compared with the aforementioned embodiment 1, this embodiment does not require the terminal side to carry user attributes, which reduces signaling overhead, avoids improvements and function enhancements on the terminal side, and improves the feasibility of the solution.

[0291] Embodiment 3: The terminal indicates first information of a user screening rule, and the target user determined by the user screening rule is a necessary user in the group call.

[0292] As shown in FIG7 , the communication method may include the following steps.

[0293] 701: The first terminal sends an instant group communication request message to the server.

[0294] Among them, the user terminal initiating the group call, i.e., the first terminal, sends an instant group communication request (ad hoc group call request) message to the server. The request includes information about at least one user screening rule, such as information about the first rule, which is used to instruct the server to screen users according to the first rule and add target users that meet the first rule to the group call to establish the first group call.

[0295] Optionally, the request message may also include first information corresponding to the first rule, which is used to indicate that the target user added by the first rule is a necessary user in the first group call. The role of the first information is similar to the aforementioned user attribute being the first attribute. It can be understood that the user attribute of the target user added by the first rule in the first group call can be the first attribute, such as marked as always-in; or, the target user added by the first rule should always remain in the first group call; or, the target user determined by the first rule is not allowed to apply other user screening rules. Among them, user screening rules that currently exist in the first group call or will be added in the future are not applied, that is, other user screening rules cannot take effect on the above-mentioned target users.

[0296] Optionally, the request information further includes second information corresponding to the first rule, which is used to indicate that the attribute of the first rule is read-only or modifiable.

[0297] 702: The server performs an authorization check and the authorization is passed.

[0298] Refer to the aforementioned step 502.

[0299] The server saves the first rule; optionally, saves the first information and the second information associated with the first rule.

[0300] 703: The server sends an instant group communication return message to the first terminal.

[0301] Refer to the aforementioned step 503.

[0302] 704a: The server sends an instant group communication request message to the second terminal.

[0303] 704b: The server sends an instant group communication request message to the third terminal.

[0304] Specifically, the server may screen user terminals that meet the first rule according to step 701. If the server determines that the second terminal and the third terminal meet the first rule, the server may send an instant group communication request message to the second terminal and the fourth terminal, requesting access to the group call. The request message may include a group call identifier (ad hoc group ID) and a preconfigured group identifier (group ID).

[0305] 705a: The second terminal sends an instant group communication response message to the server.

[0306] 705b: The third terminal sends an instant group communication response message to the server.

[0307] 706: The server sends an instant group communication response message to the first terminal.

[0308] Optionally, the response message may further include information such as user terminals that have joined the group call session, user terminals that have not joined the group call session, or user terminals that refuse to accept the group call.

[0309] 707: The server sends a notification message to the first terminal.

[0310] 708: The media plane and voice control plane are established.

[0311] After the media plane and voice control plane are established, users in the group call can use the voice control mechanism to speak and communicate in the group.

[0312] 709: The second terminal sends an instant group communication update request message to the server.

[0313] According to the business needs of group communication, the second terminal, as an authorized user, wishes to update the participating users in the current first group call. The participating users in the first group call can be updated by modifying the first rule, adding the second rule, or through at least one of the following methods: a list of users to be added and / or a list of users to be removed.

[0314] For example, in step 709 of this embodiment, the updating method of adding the second rule and / or indicating the update information of the first rule can be used as an example for description. In the subsequent step 714, the updating method of adding the user list (the list of users to be added and / or removed) can be used as an example for description.

[0315] For example, the instant group communication update request message in step 709 may include information about the second rule and / or update information about the first rule. Exemplarily, the instant group communication update request message may be a modify ad hoc group call criteria message or a modify ad hoc group call participant message.

[0316] Optionally, the second rule in the update request message may also correspond to the first information, for indicating to the server that the target user added according to the second rule is a necessary user in the first group call and is not allowed to be removed by applying other user screening rules.

[0317] Optionally, the second rule in the update request message may further correspond to second information, which is used to indicate whether the attribute of the second rule is read-only or modifiable.

[0318] 710: The server updates the users in the group call according to the second rule and / or the updated information of the first rule.

[0319] Optionally, the server performs an authorization check on the request message, and when it is determined that the second terminal is authorized to execute the request, it is determined that the authorization is passed.

[0320] Specifically, the server updates the first rule according to the update information of the first rule, adds target users that meet the updated first rule to the first group call, and removes participating users that do not meet the updated first rule from the first group call.

[0321] Optionally, the server screens users according to the second rule, adds target users that meet the second rule to the first group call, and removes participating users that do not meet the second rule from the first group call.

[0322] The server can specifically include the following processing.

[0323] 1. For a first rule marked with the first information, the server does not apply the first rule to a target user corresponding to the first rule.

[0324] The target user corresponding to the first rule may refer to a target user who satisfies the first rule and is screened by the server according to the first rule. The server automatically adds the target user corresponding to the first rule to the first group call.

[0325] The first rule is marked with first information, such as always-in. Therefore, the server no longer checks whether the target user corresponding to the existing first rule meets the first rule or the second rule. That is, the target user corresponding to the first rule does not need to be removed even if it does not meet the second rule.

[0326] 2. If the update request message includes information about the second rule, the server filters users according to the second rule and may add target users that meet the second rule to the first group call, while removing users that do not meet the second rule from the first group call. The server does not apply the second rule to users whose user attributes are marked with the first or second attribute, nor does it apply the second rule to target users corresponding to the first rule marked with the first information.

[0327] 3. If the update request message includes update information of the first rule, the server first determines the attribute of the first rule, whether it is read-only or modifiable; optionally, further determines the identifier of the user who is authorized to modify the rule.

[0328] If the attribute of the first rule is modifiable and allows modification by the second terminal, the server can modify the first rule according to the update information. For example, the server can update the original first rule to a new first rule according to the update information.

[0329] At this time, since the first rule is marked with the first information, such as always-in, the server does not apply the new first rule to the target user corresponding to the old first rule; nor does it apply the old first rule to the target user corresponding to the new first rule.

[0330] That is to say, the server may no longer check whether the target users added in the first group call according to the original first rule meet the new first rule or the old first rule, that is, the target users corresponding to the old first rule are not allowed to be removed from the first group call even if they do not meet the new first rule or the newly added second rule.

[0331] For example, the original first rule corresponds to parameter 1, and the new first rule corresponds to parameter 2. If the first user in the first group call meets parameter 1 but not parameter 2, the server will retain the first user in the first group call. Additionally, if the server detects a new user meeting parameter 2, it can add the new user to the first group call. If the second user does not meet parameter 1 but meets parameter 2, the server will add the second user to the first group call.

[0332] 4. During the first group call, the server may regularly or periodically detect according to the updated new first rule and / or second rule, add users that meet the new first rule to the first group call, and add users that meet the second rule to the first group call.

[0333] Exemplarily, the server determines that the fourth device meets the second rule and needs to be added to the first group call, and performs the following steps.

[0334] 711: The server sends an instant group communication request message to the fourth terminal.

[0335] 712: The fourth terminal sends an instant group communication response message to the server.

[0336] The response message is used to instruct the fourth terminal to accept or reject the group call.

[0337] 713: The server sends an instant group communication update response message to the second terminal.

[0338] 714: The second terminal sends an instant group communication update request message to the server.

[0339] In parallel with step 709 , in this step, the update request message may include a list of users to be added and / or a list of users to be removed, so as to update the participating users in the first group call.

[0340] Optionally, the update request message may further include: a first attribute corresponding to the user to be added, and / or a second attribute corresponding to the user to be removed. As can be seen from the foregoing, the user to be added is a required user in the first group call and is not removed based on any user screening rule; the user to be removed is a released user in the first group call and is not added to the first group call based on any user screening rule.

[0341] Exemplarily, if the user to be added included in the update request message is a user associated with the fifth terminal, the communication party further includes the following steps.

[0342] 715: The server sends an instant group communication request message to the fifth terminal.

[0343] 716: The fifth terminal sends an instant group communication response message to the server.

[0344] The response message is used to instruct the fifth terminal to accept or reject the group call.

[0345] 717: The server sends an instant group communication update response message to the second terminal.

[0346] Optionally, the server may send an instant group communication update response message to the group call initiator, ie, the first terminal, which message may inform the first terminal of information such as which new users have joined the first group call, which users have been removed from the first group call, and so on.

[0347] Optionally, the aforementioned step 709 and step 714 may be combined into the same message for implementation.

[0348] In addition, the present application also provides another implementation method, in which the terminal requests the server to deactivate the user screening rule corresponding to the first group call, so that the network device can update the status of the user screening rule corresponding to the first group call to a deactivated state according to the request of the terminal. Exemplary, the user screening rule can be marked as frozen, deactivated, disabled, or suspended, indicating that the user screening rule is no longer in use. The server will not remove the user screening rule, but can record the status of the user screening rule.

[0349] At this time, when the initiating user of the group call or other authorized users requests to update the users in the first group call, the user to be updated may not be applied to the user screening rule in the deactivated state. In other words, the user screening rule in the deactivated state is invalid for the user to be updated.

[0350] The following describes a specific implementation method through Example 4 in conjunction with FIG8 .

[0351] Embodiment 4: The terminal requests the network device to deactivate the user screening rule.

[0352] As shown in FIG8 , the communication method may include the following steps.

[0353] 801: A first terminal sends a first message to a network device, including information about a first rule and third information, where the third information indicates deactivation of the first rule corresponding to a first group call.

[0354] 802: The network device updates the state of the first rule to a deactivated state.

[0355] Optionally, the network device may send a response message to the authorized terminal in the first group call to indicate the activation state of the first rule. Specifically, the response message may include that the first rule is in a deactivated state.

[0356] In one implementation, before step 801 , the first group call has been established, which may be established by the server according to the first rule configured by the terminal, and may include the following process.

[0357] 800a: The first terminal sends an instant group communication request message to the network device.

[0358] In which, the first terminal sends an instant group communication request (ad hoc group call request) message to the network device, and the request includes information of at least one user screening rule, such as information including a first rule, which is used to instruct the network device to screen users according to the first rule, and add target users that meet the first rule to the group call to establish a first group call.

[0359] 800b: The network device performs an authorization check and authorizes the request.

[0360] Refer to the aforementioned step 502. The network device saves the first rule.

[0361] 800c: The network device sends an instant group communication return message to the first terminal.

[0362] Refer to the aforementioned step 503.

[0363] Exemplarily, the network device detects that the second terminal satisfies the first rule.

[0364] 800d: The network device sends an instant group communication request message to the second terminal.

[0365] 800e: The second terminal sends an instant group communication response message to the network device.

[0366] The response message is used to instruct the second terminal to accept or reject the group call.

[0367] 800f: The network device sends an instant group communication response message to the first terminal, indicating that the call is successfully established.

[0368] Optionally, the response message may further include information such as user terminals that have joined the group call session, user terminals that have not joined the group call session, or user terminals that refuse to accept the group call.

[0369] 800g: The network device sends a notification message to the first terminal.

[0370] 800h: The media plane and voice control plane are established.

[0371] After the media plane and voice control plane are established, users in the group call can use the voice control mechanism to speak and communicate in the group.

[0372] It should be understood that the network device sending a response message to the user in the first group call to indicate the activation status of the first rule in step 802 may specifically include the network device sending a notification message to the second terminal, where the second terminal is an authorized terminal in the first group call.

[0373] At this time, according to the service requirements of the group communication, the first terminal needs to update the participating users in the current first group call, which includes the following steps.

[0374] 803: The first terminal sends a second message to the network device to update the users in the first group call. The second message includes the identifier of the user to be added and / or the identifier of the user to be removed.

[0375] The first rule is ineffective for users to be added or removed. That is, the network device directly adds the user to the first group call without determining whether the user satisfies the first rule. Alternatively, the network device can directly remove the user from the first group call without determining whether the user satisfies the first rule.

[0376] Exemplarily, the user to be added included in the second message is a third terminal. The method further includes the following steps.

[0377] 804: The network device sends an instant group communication request message to the third terminal.

[0378] 805: The third terminal sends an instant group communication response message to the network device.

[0379] The response message is used to instruct the third terminal to accept or reject the group call.

[0380] Subsequently, when it is necessary to continue updating users in the first group call according to the first rule based on the business needs of the group communication, the initiating user or authorized user of the first group call may send a request to the network device to instruct activation of the first rule.

[0381] 806: The first terminal sends a third message to the network device, including information about the first rule and fourth information, where the fourth information indicates activation of the first rule corresponding to the first group call.

[0382] Exemplarily, the third message sent by the first terminal to the network device can be an ad hoc group call criteria update or modify ad hoc group call criteria message, which can include fourth information, which can be used to indicate unfreeze, activation, enable or resume of the first rule in the first group call.

[0383] At this point, the network device may begin to continue screening users according to the first rule, add users who meet the first rule to the first group call, remove participating users who do not meet the first rule from the first group call, and update the status of the first rule to an active state.

[0384] 807: The network device sends a response message to the authorized user, including the activation status of the first rule.

[0385] Optionally, the network device may send a response message to the authorized user corresponding to the first group call, which may optionally include the latest status of the user screening rules in the first group call, for example, the first rule is activated so that other users can perceive that the first rule is restored and can modify the first rule.

[0386] Exemplarily, if the authorized users in the first group call include the first terminal, the second terminal, and the fourth terminal, the network device sends a response message to the above terminals to notify that the activation status of the first rule is activated.

[0387] In the above implementation mode, the terminal can modify or set the activation status of the user screening rules for the group call by requesting the network device, so that the user screening rules are deactivated for a period of time, thereby authorizing the terminal to flexibly update the participating users in the group call as needed, such as adding or removing users through the user list without being affected by the user screening rules, thereby improving the flexibility of updating the participating users in the group call, improving the communication efficiency of the group call, and thus improving the user experience.

[0388] The various embodiments mentioned above in this application can be combined without limitation if there is no contradiction between the solutions.

[0389] The above mainly introduces the solution provided by this application from the perspective of interaction between various nodes. Accordingly, this application also provides a communication device, which can be the network device in the above method embodiment, or a node or device including the above network device, or a component that can be used for the network device; or, the communication device can be the terminal in the above method embodiment, or a node or device including the above terminal, or a component that can be used for the terminal.

[0390] It is understandable that, in order to implement the above functions, the above communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithmic operations of the various examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0391] It should be understood that the above description only uses network devices and terminals as examples to describe the interaction between nodes. In fact, the processing performed by the above network devices is not limited to being performed by a single node, and the processing performed by the above terminals is not limited to being performed by a single node.

[0392] The present application can divide the functional modules of the communication device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software functional modules. It is understood that the division of modules in this application is schematic and is only a logical functional division. In actual implementation, other division methods may be used.

[0393] For example, in the case of dividing the functional modules in an integrated manner, FIG9 shows a schematic structural diagram of a communication device 900. The communication device 900 includes a processing module 901 and a communication module 902.

[0394] In some embodiments, the communication device 900 may further include a storage module (not shown in FIG. 9 ) for storing program instructions and data.

[0395] Exemplarily, the communication device 900 can be used to implement the functions of a terminal. The communication device 900 is, for example, the terminal described in the embodiments of FIG4 to FIG7 , or can be an MC client on the terminal.

[0396] Among them, the processing module 901 can be used to generate a first message, which is used to update the users in the first group call. The first message includes the identifier of the user to be added and the user attributes of the user to be added, and / or the identifier of the user to be removed and the user attributes of the user to be removed.

[0397] The communication module 902 is configured to send the first message to the network device.

[0398] In one embodiment, if the user attribute of the user to be added is a first attribute, the first attribute is used to indicate at least one of the following information: the user to be added is a necessary user in the first group call; or, before the first group call ends, the user to be added is retained in the first group call; or, the user to be added cannot be removed before the first group call ends; or, the user screening rule corresponding to the first group call is not applied to the user to be added, and the user screening rule is used by the network device to update the users in the first group call.

[0399] In one embodiment, if the user attribute of the user to be removed is a second attribute, the second attribute is used to indicate at least one of the following information: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be added is not allowed to be added to the first group call by the network device according to the user screening rule corresponding to the first group call; or, the user to be removed is not subject to the user screening rule corresponding to the first group call, and the user screening rule is used by the network device to update the users in the first group call.

[0400] In one implementation, the communication module 902 is configured to send a second message to the network device, where the second message includes an identifier of at least one target user; the second message is used to request establishment of the first group call and to add the target user to the first group call.

[0401] In one implementation, the second message further includes a first attribute corresponding to the target user.

[0402] In one embodiment, the communication module 902 is used to send a third message to the network device, the third message including information of the first rule, and the third message is used to request establishment of the first group call, wherein the first rule is one of the user screening rules, and the first rule is used to add users who meet the first rule to the first group call, and remove participating users who do not meet the first rule from the first group call.

[0403] In one embodiment, the third message further includes first information, where the first information is used to indicate that the target users screened according to the first rule are necessary users in the first group call.

[0404] In one embodiment, the third message further includes second information, where the second information is used to indicate whether the attribute of the first rule is read-only or modifiable.

[0405] In one embodiment, the communication module 902 is used to send a fourth message to the network device, wherein the fourth message includes information of the second rule, or includes update information of the first rule, and the second rule or the update information is used to update the users in the first group call; wherein the second rule is one of the user screening rules, and the second rule is used to add users who meet the second rule to the first group call, and remove participating users who do not meet the second rule from the first group call.

[0406] In one implementation, the communication module 902 is configured to receive a response message from the network device, indicating a result of the user update in the first group call.

[0407] In addition, the communication device 900 can be used to implement the functions of a network device. The communication device 900 is, for example, the network device or server described in the embodiments of Figures 4 to 7 above, and specifically can be an MC server.

[0408] The communication module 902 is configured to receive a first message from a first terminal, where the first message is used to update users in a first group call, and the first message includes an identifier of a user to be added and / or an identifier of a user to be removed.

[0409] The processing module 901 is used to determine the user attributes of the user to be added, and add the user to be added to the first group call according to the first message; and / or determine the user attributes of the user to be removed, and remove the user to be removed from the first group call according to the first message.

[0410] In one embodiment, if the user attribute is a first attribute, the first attribute is used to indicate at least one of the following information: the user to be added is a necessary user in the first group call; or, the user to be added is retained in the first group call before the first group call ends; or, the user to be added cannot be removed before the first group call ends; or, the user screening rule corresponding to the first group call is not applied to the user to be added, and the user screening rule is used by the network device to update the users in the first group call.

[0411] In one embodiment, if the user attribute is a second attribute, the second attribute is used to indicate at least one of the following information: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be removed is not allowed to be added to the first group call by the network device according to the user screening rule corresponding to the first group call; or, the user to be removed is not subject to the user screening rule corresponding to the first group call, and the user screening rule is used by the network device to update the users in the first group call.

[0412] In one implementation, the first message includes user attributes of the user to be added and / or user attributes of the user to be removed.

[0413] In one embodiment, the processing module 901 is configured to generate, for the user to be added, a first attribute of the user to be added, and / or generate, for the user to be removed, a second attribute of the user to be removed, according to the first message.

[0414] In one embodiment, the communication module 902 is configured to receive a second message from the first terminal or from the second terminal, the second message including an identifier of at least one target user, the at least one target user including a user associated with the first terminal. The processing module 901 is configured to add the target user to the first group call to establish the first group call.

[0415] In one implementation, the second message further includes a first attribute corresponding to the target user.

[0416] In one embodiment, the communication module 902 is configured to receive a third message from the first terminal or from the second terminal, the third message including information of the first rule. The processing module 901 is configured to add target users that meet the first rule to the first group call to establish the first group call.

[0417] In one embodiment, the processing module 901 is used to update the participating users in the first group call, add the target users who meet the first rule to the first group call, and remove the users who do not meet the first rule from the first group call; if the user attribute corresponding to the first user in the first group call is the first attribute, the first user is retained in the first group call; if the second user meets the first rule and the user attribute corresponding to the second user is the second attribute, the second user is removed from the first group call, or the second user is not added to the first group call.

[0418] In one embodiment, the third message further includes second information for indicating whether the attribute of the first rule is read-only or modifiable.

[0419] In one embodiment, the communication module 902 is configured to receive a fourth message from the terminal, the fourth message including information about the second rule and / or including update information about the first rule. The processing module 901 is configured to, based on the second rule or the update information, add target users that meet the second rule or the update information to the first group call, and remove participating users that do not meet the second rule from the first group call.

[0420] In one embodiment, the processing module 901 is used to save the user list corresponding to the first group call, and the user attributes corresponding to the users in the user list; and / or, to save the first attribute in the first group call and the user list corresponding to the first attribute; and / or, to save the second attribute in the first group call and the user list corresponding to the second attribute; and / or, to save at least one user screening rule corresponding to the first group call, and the first information corresponding to the user screening rule, the first information being used to indicate that the target user determined according to the user screening rule is a necessary user in the first group call.

[0421] In one implementation, the communication module 902 is configured to send a response message to the first terminal, indicating an update result of users in the first group call.

[0422] In addition, the communication device 900 can be used to implement the functions of a terminal. The communication device 900 is, for example, the terminal described in the embodiment of FIG8 , or can be an MC client on the terminal.

[0423] Among them, the communication module 902 is used to send a first message to the network device, the first message includes information of the first rule and third information, the third information indicates deactivation of the first rule corresponding to the first group call, the first rule is used to add users who meet the first rule to the first group call, and remove participating users who do not meet the first rule from the first group call; send a second message to the network device, the second message is used to update the users in the first group call, the second message includes the identification of the user to be added, and / or, includes the identification of the user to be removed; wherein, the first rule is invalid for the user to be added and the user to be removed.

[0424] In one embodiment, the user to be added satisfies at least one of the following conditions: the user to be added is a necessary user in the first group call; or, before the first group call ends, the user to be added remains in the first group call; or, the user to be added cannot be removed before the first group call ends; or, the first rule is not applied to the user to be added.

[0425] In one embodiment, the user to be added satisfies at least one of the following conditions: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be added is not allowed to be added to the first group call by the network device according to the first rule; or, the first rule is not applied to the user to be removed.

[0426] In one implementation, the communication module 902 is further configured to send a third message to the network device, where the third message includes information about the first rule and fourth information, where the fourth information indicates activation of the first rule corresponding to the first group call.

[0427] In one embodiment, the communication module 902 is further configured to receive a response message from the network device, including an activation status of the first rule.

[0428] In addition, the communication device 900 can be used to implement the functions of a network device. The communication device 900 is, for example, the network device described in the embodiment of FIG8 , and specifically can be an MC server.

[0429] Among them, the communication module 902 is used to receive a first message from the terminal, the first message includes information about the first rule and third information, the third information indicates deactivation of the first rule, the first rule is used to add users who meet the first rule to the first group call, and remove participating users who do not meet the first rule from the first group call.

[0430] The processing module 901 is used to receive a second message from the terminal, where the second message is used to update the users in the first group, and the second message includes at least one identifier of a user to be added, and / or includes at least one identifier of a user to be removed; according to the second message, the user to be added is added to the first group call, and the user to be added is a necessary user in the first group call; and / or, the user to be removed is removed from the first group call.

[0431] In one embodiment, the user to be added satisfies at least one of the following conditions: the user to be added is a necessary user in the first group call; or, before the first group call ends, the user to be added remains in the first group call; or, the user to be added cannot be removed before the first group call ends; or, the first rule is not applied to the user to be added.

[0432] In one embodiment, the user to be removed satisfies at least one of the following conditions: the user to be removed is a released user in the first group call; or, the user to be removed is no longer a necessary user in the first group call; or, the user to be added is not allowed to be added to the first group call by the network device according to the first rule; or, the first rule is not applied to the user to be removed.

[0433] In one embodiment, if the user to be added does not meet the first rule, the first user is retained in the first group call; if the user to be removed meets the first rule, the user to be removed is removed from the first group call, or the user to be removed is not added to the first group call.

[0434] In one implementation, the processing module 901 is configured to update the state of the first rule to a deactivated state.

[0435] In one embodiment, the communication module 902 is further configured to receive a third message from the terminal, the third message including information about the first rule and fourth information indicating activation of the first rule. The processing module 901 is configured to add users who meet the first rule to the first group call, remove participating users who do not meet the first rule from the first group call, and update the status of the first rule to an activated state.

[0436] In one implementation, the communication module 902 is further configured to send a response message to the authorized terminal in the first group call, including the activation status of the first rule.

[0437] In a simple embodiment, those skilled in the art may appreciate that the communication device 900 may be in the form shown in Figure 3. For example, the processor 301 in Figure 3 may call the computer-executable instructions stored in the memory 303 to enable the communication device 900 to execute the method described in the above method embodiment.

[0438] Exemplarily, the functions / implementation processes of the processing module 901 in FIG. 9 may be implemented by the processor 301 in FIG. 3 .

[0439] Exemplarily, the functions / implementation processes of the communication module 902 in FIG. 9 may be implemented through the communication interface 304 in FIG. 3 .

[0440] It is understandable that one or more of the above modules or units can be implemented by software, hardware or a combination of the two. When any of the above modules or units is implemented by software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow. The processor can be built into an SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions to perform calculations or processing within the processor, it can further include necessary hardware accelerators, such as field programmable gate arrays (FPGAs), PLDs (programmable logic devices), or logic circuits that implement dedicated logic operations.

[0441] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0442] Optionally, the present application also provides a chip system, comprising: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instruction in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the chip system also includes a memory. Optionally, the chip system can be composed of a chip, or can include a chip and other discrete devices, which is not specifically limited in this application.

[0443] Optionally, the present application also provides a computer-readable storage medium. All or part of the processes in the above-mentioned method embodiments can be completed by a computer program to instruct the relevant hardware. The program can be stored in the above-mentioned computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The computer-readable storage medium can be an internal storage unit of the communication device of any of the above-mentioned embodiments, such as a hard disk or memory of the communication device. The above-mentioned computer-readable storage medium can also be an external storage device of the above-mentioned communication device, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. equipped on the above-mentioned communication device. Furthermore, the above-mentioned computer-readable storage medium can also include both the internal storage unit of the above-mentioned communication device and an external storage device. The above-mentioned computer-readable storage medium is used to store the above-mentioned computer program and other programs and data required by the above-mentioned communication device. The above-mentioned computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.

[0444] Optionally, the present application also provides a computer program product. All or part of the processes in the above method embodiments may be completed by a computer program instructing related hardware. The program may be stored in the above computer program product, and when executed, the program may include the processes in the above method embodiments.

[0445] Optionally, the present application also provides a computer instruction. All or part of the process in the above method embodiment can be completed by the computer instruction to instruct the relevant hardware (such as a computer, processor, network device or terminal, etc.). The program can be stored in the above computer-readable storage medium or in the above computer program product.

[0446] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0447] Optionally, the present application also provides a communication system, including: the network device and terminal in the above embodiments.

[0448] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0449] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0450] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0451] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0452] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method comprises: Generate a first message, where the first message is used to update users in the first group call, the first message including an identifier of a user to be added and user attributes of the user to be added, and / or an identifier of a user to be removed and user attributes of the user to be removed; The first message is sent to the network device.

2. The method according to claim 1, characterized in that If the user attribute of the user to be added is a first attribute, the first attribute is used to indicate at least one of the following information: The user to be added is a necessary user in the first group call; or, Before the first group call ends, the user to be added is kept in the first group call; or, The user to be added cannot be removed before the first group call ends; or, The to-be-added user is not subject to a user screening rule corresponding to the first group call, and the user screening rule is used by a network device to update users in the first group call.

3. The method according to claim 1 or 2, characterized in that If the user attribute of the user to be removed is a second attribute, the second attribute is used to indicate at least one of the following information: The user to be removed is a released user in the first group call; or, The user to be removed is no longer a necessary user in the first group call; or, The to-be-added user is not allowed to be added to the first group call by the network device according to the user screening rule corresponding to the first group call; or, The user to be removed is not subject to the user screening rule corresponding to the first group call, and the user screening rule is used by the network device to update the users in the first group call.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: A second message is sent to the network device, where the second message includes an identifier of at least one target user; the second message is used to request establishment of the first group call and to add the target user to the first group call.

5. The method according to claim 4, characterized in that The second message also includes a first attribute corresponding to the target user.

6. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Sending a third message to the network device, the third message including information of a first rule, the third message being used to request establishment of the first group call, wherein the first rule is one of user screening rules, and the first rule is used to add users who meet the first rule to the first group call, and remove participating users who do not meet the first rule from the first group call.

7. The method according to claim 6, characterized in that The third message further includes first information, where the first information is used to indicate that the target users screened according to the first rule are necessary users in the first group call.

8. The method according to claim 6 or 7, characterized in that The third message further includes second information, where the second information is used to indicate whether the attribute of the first rule is read-only or modifiable.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Send a fourth message to the network device, the fourth message including information of the second rule, or including update information of the first rule, the second rule or the update information being used to update users in the first group call; wherein the second rule is one of the user screening rules, and the second rule is used to add users who meet the second rule to the first group call, and remove participating users who do not meet the second rule from the first group call.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: A response message is received from the network device, indicating a result of the user update in the first group call.

11. A communication method, characterized in that: The method comprises: receiving a first message from a first terminal, where the first message is used to update users in a first group call, and the first message includes an identifier of a user to be added and / or an identifier of a user to be removed; Determining user attributes of the user to be added, and adding the user to be added to the first group call according to the first message; and / or, Determine user attributes of the user to be removed, and remove the user to be removed from the first group call according to the first message.

12. The method according to claim 11, characterized in that If the user attribute is a first attribute, the first attribute is used to indicate at least one of the following information: The user to be added is a necessary user in the first group call; or, Before the first group call ends, the user to be added is kept in the first group call; or, The user to be added cannot be removed before the first group call ends; or, The to-be-added user is not subject to a user screening rule corresponding to the first group call, and the user screening rule is used by a network device to update users in the first group call.

13. The method according to claim 11 or 12, characterized in that If the user attribute is a second attribute, the second attribute is used to indicate at least one of the following information: The user to be removed is a released user in the first group call; or, The user to be removed is no longer a necessary user in the first group call; or, The user to be removed is not allowed to be added to the first group call by the network device according to the user screening rule corresponding to the first group call; or, The user to be removed is not subject to the user screening rule corresponding to the first group call, and the user screening rule is used by the network device to update the users in the first group call.

14. The method according to any one of claims 11 to 13, characterized in that: The first message includes user attributes of the user to be added and / or user attributes of the user to be removed.

15. The method according to any one of claims 11 to 13, characterized in that: Determining the user attributes of the user to be added includes: According to the first message, a first attribute of the user to be added is generated for the user to be added, and / or a second attribute of the user to be removed is generated for the user to be removed.

16. The method according to any one of claims 11 to 15, characterized in that The method further comprises: receiving a second message from the first terminal or from a second terminal, where the second message includes an identifier of at least one target user, and the at least one target user includes a user associated with the first terminal; Add the target user to the first group call to establish the first group call.

17. The method according to claim 16, characterized in that The second message also includes a first attribute corresponding to the target user.

18. The method according to any one of claims 11 to 15, characterized in that: The method further comprises: receiving a third message from the first terminal or from the second terminal, wherein the third message includes information about the first rule; Add target users that meet the first rule to the first group call to establish the first group call.

19. The method according to claim 18, characterized in that The method further comprises: Updating participating users in the first group call, adding target users that meet the first rule to the first group call, and removing users that do not meet the first rule from the first group call; If the user attribute corresponding to the first user in the first group call is the first attribute, retaining the first user in the first group call; If the second user meets the first rule and the user attribute corresponding to the second user is the second attribute, the second user is removed from the first group call, or the second user is not added to the first group call.

20. The method according to claim 18 or 19, characterized in that The third message further includes second information for indicating whether the attribute of the first rule is read-only or modifiable.

21. The method according to any one of claims 18 to 20, characterized in that The method further comprises: receiving a fourth message from the terminal, the fourth message including information about the second rule and / or including update information about the first rule; According to the second rule or the updated information, target users that meet the second rule or the updated information are added to the first group call, and participating users that do not meet the second rule are removed from the first group call.

22. The method according to any one of claims 11 to 21, characterized in that The method further comprises: saving a user list corresponding to the first group call and user attributes corresponding to the users in the user list; and / or, saving the first attribute in the first group call and a user list corresponding to the first attribute; and / or, saving the second attribute in the first group call and a user list corresponding to the second attribute; and / or, At least one user screening rule corresponding to the first group call and first information corresponding to the user screening rule are saved, where the first information is used to indicate that a target user determined according to the user screening rule is a necessary user in the first group call.

23. The method according to any one of claims 11 to 22, characterized in that The method further comprises: A response message is sent to the first terminal to indicate a result of user update in the first group call.

24. A communication device, characterized in that: The communication device is used to implement the method according to any one of claims 1 to 23.

25. A communication device, characterized in that: include: A processor is coupled to a memory, wherein the memory is used to store a program or an instruction, and when the program or the instruction is executed by the processor, the method according to any one of claims 1 to 23 is performed.

26. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instructions are executed, the method according to any one of claims 1 to 23 is performed.

27. A computer program product, comprising computer program code, characterized in that: When the computer program code is run on a computer, the method according to any one of claims 1 to 23 is executed.

Images