WO2018201306A1 - 群组连接方法及相关设备 - Google Patents

群组连接方法及相关设备 Download PDF

Info

Publication number
WO2018201306A1
WO2018201306A1 PCT/CN2017/082789 CN2017082789W WO2018201306A1 WO 2018201306 A1 WO2018201306 A1 WO 2018201306A1 CN 2017082789 W CN2017082789 W CN 2017082789W WO 2018201306 A1 WO2018201306 A1 WO 2018201306A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
binding relationship
communication system
identifier
request message
Prior art date
Application number
PCT/CN2017/082789
Other languages
English (en)
French (fr)
Inventor
葛翠丽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/082789 priority Critical patent/WO2018201306A1/zh
Publication of WO2018201306A1 publication Critical patent/WO2018201306A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • the present application relates to the field of electronic technologies, and in particular, to a group connection method and related devices.
  • Emergency mission services are cluster communication services for public safety applications and commercial applications, such as in public security systems.
  • the emergency task service supports 1-to-N group communication.
  • the group call message carries the group identifier to the emergency task service server, and the emergency task service server is responsible for calling other group members. , negotiate media information.
  • the group communication After the group communication is established, users joining the group communication can communicate with each other.
  • two or more groups can be associated with each other.
  • the emergency task service server can call the group member and the group associated with the group. A member that enables group communication between members of two or more groups.
  • the first method is a group reorganization method applicable to the broadband access technology of the LTE system or the future 5G system, that is, temporarily establishing a new group for two or more groups; the second method is applicable to the traditional
  • the group connection mode of the narrowband access technology of the communication system is to establish an association relationship for two or more groups.
  • the association between the two groups can only be applied to a specific access technology system. Therefore, how to associate groups in different access technology systems becomes an urgent problem to be solved.
  • the present application provides a group connection method and related devices, which can bind groups in systems of different access technologies.
  • an embodiment of the present application provides a group connection method.
  • the group connection device receives a group connection request message from the first device of the first communication system, where the group connection request message includes an identifier of the first group of the first communication system and a second group of the second communication system An identifier of the group, the first communication system and the second communication system establish a binding relationship between the first group and the second group, and send a first indication message to the first device, where the first indication is based on different access technologies.
  • the message is used to notify the first group that the binding relationship has been established.
  • the group connection device can bind groups in systems of different access technologies.
  • the group connection device sends a second indication message to the second service control entity of the second communication system, where the second indication message is used to notify the second group The binding relationship has been established.
  • the group connection device sends an authorization indication message to an authorization checking entity of the second communication system, where The authorization indication message carries the identifier of the second group, and receives an authorization success response message from the authorization checking entity, where the authorization success response message is used to indicate that the second communication system allows the second group to establish a binding. relationship.
  • the group connection device may notify the authorization checking entity of the second communication system to perform an authorization check to increase security.
  • the group connection device establishes a binding relationship between the first group and the second group.
  • the group connection device can perform an authorization check on the first device to increase security.
  • the group connection device sends a third indication message to the system interworking entity, where the third indication The message includes an identifier of the first group and an identifier of the second group, where the third indication message is used to notify that the binding relationship between the first group and the second group has been established.
  • the group connection request message further includes a group role of the first group and the a group role of the second group; the binding relationship includes a group role of the first group and a group role of the second group; the third indication message further includes the first group a group role corresponding to the second group respectively.
  • the group connection request message includes a group role of the first group and a group role of the second group, so that the binding relationship and the third indication message may also include the group role of the first group.
  • the group role of the second group used for call control according to the group role when the subsequent group call is used.
  • the first indication message includes the first group Binding relationship information, where the binding relationship information includes a binding relationship indication, or the binding relationship information includes a binding relationship indication and an identifier of the second group.
  • the first indication message may further include binding relationship information of the first group, thereby indicating that the first group has a binding relationship, or further indicating a second group having a binding relationship with the first group. group.
  • the group connection request message further includes the first a group role of the group and a group role of the second group; the binding relationship includes a group role of the first group and a group role of the second group; the first The indication message also includes the group role of the first group.
  • the group connection request message includes a group role of the first group and a group role of the second group, so that the binding relationship and the first indication message may also include the group role of the first group.
  • the group role of the second group used for call control according to the group role when the subsequent group call is used.
  • the group connection device receives the group connection release request message, where the group connection release request message includes an identifier of the target group, where the target group is the first group or the second group, and the binding relationship of the target group is released.
  • the group connection device can release the binding relationship of groups in the system of different access technologies.
  • the group connection device receives the group connection release request message, where
  • the group connection release request message includes an identifier of the target group and binding relationship identification information of the target group, where the target group is the first group or the second group, and the The binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • the group connection device can release the binding relationship of groups in the system of different access technologies.
  • the tenth possible implementation in the first aspect In the mode, when the target group is the first group, the group connection device sends a fourth indication message to the first device of the first communication system, where the fourth indication message is used to notify the The binding relationship of the target group is released; or, when the target group is the second group, the group connection device sends a fifth indication message to the second service control entity of the second communication system, The fifth indication message is used to notify that the binding relationship of the target group has been released.
  • the first device includes the first communication system The group management client GMC or the service client of the first communication system or the group management server GMS of the first communication system or the first service control entity of the first communication system.
  • the group connection device receives the first group call request a message, the first group call request message includes an identifier of the first group, and when the first group has a binding relationship with the second group, the second communication system is The second group control request entity sends a second group call request message, where the second group call request message carries the identifier of the second group, and the second group call request message is used to indicate the second service control The entity joins the second group into a group communication with the first group.
  • the group connection device can implement a group call of a system of different access technologies.
  • the group connection device receives the first group call request Message, the first group call request message includes an identifier of the second group, and sends a second group call request message to the second service control entity of the second communication system, the second group call The request message carries the identifier of the second group, where the second group call request message is used to instruct the second service control entity to join the second group to the group communication with the first group. in.
  • the group connection device can implement a group call of a system of different access technologies.
  • a second aspect of the present application provides a group call method.
  • the group call device receives a first group call request message, where the first group call request message includes an identifier of the first group, and when the first group has a binding relationship, sends the message to the system interworking entity.
  • a second group call request message the second group call request message carries an identifier of the first group, and the second group call request message is used to request that there is a relationship with the first group
  • the second group of binding relationships joins the group communication.
  • the second group call request message carries the identifier of the first group.
  • the group calling device further searches for a second group call request message to the system interworking entity, and further searches for a second binding relationship with the identifier of the first group.
  • the identifier of the group, the second group call request message carries the identifier of the second group.
  • the group call device can implement group calls of systems of different access technologies.
  • a third aspect of the present application provides a group connection device. It includes a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface, for example, the processor can be coupled to the memory and communication interface via a bus.
  • the communication interface is used to communicate with devices such as clients.
  • the memory is used to store a group connection request message and the like.
  • the processor is configured to perform some or all of the processes of the first aspect.
  • the fourth aspect of the present application provides another group connection device, including a sending module, a receiving module, and a processing module.
  • the processing module is configured to implement the processor in the third aspect, and the sending module is used in combination with the receiving module to implement the network interface in the third aspect.
  • the group connection device implements some or all of the methods of the first aspect through the above modules.
  • a fifth aspect of the present application provides a group call device. It includes a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface, for example, the processor can be coupled to the memory and communication interface via a bus.
  • the communication interface is used to communicate with devices such as clients.
  • the memory is used to store a group connection request message and the like.
  • the processor is configured to perform some or all of the processes of the second aspect.
  • the sixth aspect of the present application provides another group call device, including a sending module, a receiving module, and a processing module, where the processing module is used to implement the processor in the fifth aspect, and the sending module is combined with the receiving module to implement the fifth aspect.
  • Network interface The group connection device implements some or all of the methods of the second aspect through the above modules.
  • FIG. 1 is a schematic diagram of an interworking architecture provided by an embodiment of the present application.
  • 2a is a schematic flowchart of a group connection method according to an embodiment of the present application.
  • 2b is a schematic flowchart of another method for releasing a population group connection according to an embodiment of the present application
  • 2c is a schematic flowchart of another method for releasing a population group connection according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of another method for connecting a population group according to an embodiment of the present application.
  • FIG. 3b is a schematic flowchart of another method for releasing a population group connection according to an embodiment of the present application.
  • 4a is a schematic flowchart of another method for connecting a population group according to an embodiment of the present application.
  • 4b is a schematic flowchart of another method for releasing a population group connection according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another method for connecting a population group according to an embodiment of the present application.
  • FIG. 5b is a schematic flowchart of another method for releasing a population group connection according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another method for connecting a population group according to an embodiment of the present application.
  • FIG. 6b is a schematic flowchart of another method for releasing a population group connection according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a group call method according to an embodiment of the present application.
  • FIG. 7b is a schematic flowchart diagram of another method for calling a group according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a group connection apparatus according to an embodiment of the present application.
  • FIG. 8b is a schematic structural diagram of another group connection device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a group call apparatus according to an embodiment of the present application.
  • FIG. 9b is a schematic structural diagram of another group call apparatus provided by an embodiment of the present application.
  • a schematic diagram of a system interworking architecture shown in FIG. 1 includes a first communication system 101, a second communication system 102, and a system interworking entity 103, wherein different connections are used between the first communication system 101 and the second communication system 102.
  • the system interworking entity 103 is used to implement the function adaptation of different access technologies and the conversion of the communication protocol, thereby implementing mutual group communication between the first communication system 101 and the second communication system 102.
  • the first communication system 101 may be a group communication system applicable to an access technology of an LTE system or a future 5G system, For example, a mission critical service system;
  • the second communication system 102 may be a group communication system suitable for access technologies of legacy systems prior to LTE system applications, for example, LMR (land mobile radio) Communication system), P25 (Project 25, Engineering 25) or TETRA (terrestrial trunked radio).
  • LMR laand mobile radio
  • P25 Project 25, Engineering 25
  • TETRA terrestrial trunked radio
  • the embodiment of the present application mainly introduces the first communication system as an emergency mission service system, and the other group communication systems are similar to the emergency mission service system, and are not specifically described.
  • Mission critical service server A logical entity that is primarily responsible for call control and media control.
  • the emergency task service server may be a mission-critical push to talk server (MCPTT server), a mission critical video server (MCVideo server), or an emergency task data server (mission).
  • Critical data server MCData server
  • the first service control entity mentioned in the embodiment of the present application may serve as an emergency task server.
  • Mission critical service client An application layer entity that is peered with an emergency mission service server and is primarily responsible for the processing of application layer transactions.
  • the service client mentioned in the embodiment of the present application can serve the client for an emergency task.
  • Group management server It is mainly responsible for group management and group information maintenance in the emergency mission service system, for example, group creation, group dissolution, group member change, and the like.
  • Group management client An application layer entity that is peered with a group management server. It is mainly responsible for initiating group management and maintenance operations, such as initiating group creation, group dissolution, and group members. Change and other operations.
  • Interworking function An application layer functional entity that is used to connect the emergency mission service system with the second communication system. It is mainly responsible for translation and mapping translation and mapping of protocols.
  • the interworking function entity is a logical function entity. In actual implementation and deployment, it can be implemented as a separate network device such as an interworking gateway, or it can be a functional entity placed inside the emergency task service server, or implemented in the second communication. In the network entity in the system, there is no specific limitation here.
  • the group management client and the emergency task service client may be two different logical entities running in the same terminal device.
  • a user can log in to multiple terminal devices at the same time and use the emergency task service client or group management client.
  • one client account corresponding to one user can correspond to multiple terminal devices.
  • Multiple users can also log in and use the same terminal device at the same time.
  • multiple client accounts corresponding to multiple users can correspond to one terminal device.
  • the execution method described in the embodiment of the present application is a method for establishing a group connection in a system environment as shown in FIG. 1, so that the first communication system of different access technologies and the second communication system can be Groups are associated.
  • an embodiment of the present application provides a group connection method.
  • the method includes, but is not limited to, the following steps.
  • Step S001 The first device of the first communication system sends a group connection request message to the group connection device.
  • the first device includes a group management client GMC of the first communication system or a service client of the first communication system or a group management server GMS of the first communication system or the first of the first communication system.
  • the group connection device may be a group management server of the first communication system, or may be a system interworking entity.
  • the group management client GMC of the first communication system may send the group connection request message to the group management server GMS of the first communication system, or may be the first service control entity of the first communication system.
  • the group management server GMS of the communication system sends the group connection request message, and may also be the first communication system after the service client of the first communication system sends the group connection request message to the first service control entity of the first communication system.
  • the first service control entity is in turn sent to the group management server GMS of the first communication system.
  • the group management server GMS of the first communication system may send the group connection request message to the system interworking entity, or the first service control entity of the first communication system may send the group connection request message to the system interworking entity.
  • the group connection request message includes an identifier of the first group of the first communication system and an identifier of the second group of the second communication system, wherein the first communication system and the second communication system are based on different access technologies.
  • the group connection request message is used to request to establish a binding relationship between the first group and the second group.
  • the first group refers to a group in the first communication system
  • the second group refers to a group in the second communication system.
  • the binding relationship between the first group and the second group refers to associating the first group with the second group to form a logical whole. When there is a binding relationship, the first group Or when any one of the second group is called, another group will also be called.
  • the first device of the first communication system may obtain the identifier of the second group by interacting with other devices, or may pre-store the identifier of the second group in the group of the first communication system in a pre-configured manner.
  • group management client there is no specific limitation here.
  • the group connection request message may further include a group role of the first group and a group role of the second group.
  • the group role refers to the role played by the group call, which may be a master group role or a non-master/slave group role. Specifically, if there is only one master group role in a group communication, then only the master group role can be specified. Other group roles can default to non-master/slave group roles by default.
  • the group connection request message may include a first group as a master group role, and a second group is a non-master/slave group role; the group connection request message may also include the first group as a master group The group role, and the group role of the second group defaults, then the second group can be the non-master/slave group role by default.
  • Step S002 The group connection device establishes a binding relationship between the first group and the second group.
  • the group connection device After receiving the group connection request message, the group connection device establishes a binding relationship between the first group and the second group.
  • the binding between the first group and the second group may be established in the form of a table.
  • the relationship is determined by adding the identifier of the first group and the identifier of the second group in the binding relationship table, indicating that the two have a binding relationship. For example, if the identifier of the first group is 1-12 and the identifier of the second group is 2-02, the binding relationship group corresponding to the number 1 may be added in the binding relationship table shown in Table 1. -12 and 2-02.
  • the group connection device can establish a binding relationship between the first group and the second group.
  • the binding relationship established for the first group and the second group may further include binding relationship identifier information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, for example, (1-12 2-02); or may be a group identifier of any one of the binding relationships.
  • 2-02 may also be a newly created identifier for indicating a binding relationship between the first group and the second group, such as the number in Table 1.
  • the binding relationship may also include the group role of the first group and the second group.
  • the group role of the group such as the binding relationship table shown in Table 2.
  • an authorization indication message may be sent to the authorization checking entity of the second communication system, to indicate that the second communication system performs the authorization check.
  • the authorization checking entity of the second communication system allows the second group to establish a binding relationship
  • the authorization checking entity of the second communication system transmits an authorization success response message to the group connection device.
  • the group connection device performs step S002.
  • the step S002 may be specifically: when the first device has the right to request the first group to establish a binding relationship with the second group, the first group and the second group are established. Binding relationship. The binding relationship between the first group and the second group is established when it is determined that the first device has a state that requests the first group to establish a binding relationship with the second group.
  • step S002 when the group connection device is the group management server of the first communication system, before step S002, it is also possible to check whether the user of the first device has the right to request the first group to establish a binding relationship with the second group. If there is permission to request the first group to establish a binding relationship with the second group, step S002 is performed.
  • the specific authorization checking method will be described in detail based on the embodiment shown in Figures 2b-6b below.
  • Step S003 The group connection device sends a first indication message to the first device of the first communication system.
  • the first indication message is used to notify that the binding relationship of the first group has been established.
  • the first indication message may be a group connection response message, and the message name may be used to indicate to the first device that the binding relationship of the first group has been established.
  • the first indication message may include binding relationship information of the first group, and the binding relationship information may be a binding relationship indication.
  • the binding relationship indication is used to indicate that the binding relationship of the first group has been established, for example
  • the binding relationship indication may be one reserved bit position 1 in the first indication message, or may be a new one bit position 0, used to indicate establishment of the first group binding relationship.
  • the binding relationship information of the first group in the first indication message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be a group identifier of any one of the binding relationships, for example, the identifier of the second group. It may also be a newly created identifier for indicating a binding relationship between the first group and the second group. Therefore, the first indication message may indicate that the binding relationship of the first group has been established, and the binding relationship identification information uniquely indicates the binding relationship established between the first group and the second group.
  • the first indication message may further include the group role of the first group, and may also include The group roles corresponding to the first group and the second group respectively.
  • the group connection device may further send a second indication message to the second service control entity of the second communication system, where the second indication message is used to notify that the binding relationship of the second group has been established.
  • the second indication message may include a binding relationship indication, where the binding relationship indication is used to indicate that the binding relationship of the second group has been established.
  • the second indication message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be an identifier of any one of the binding relationships, or may be newly created for indicating the first The identifier of the binding relationship between the group and the second group.
  • the second indication message is used to indicate that the binding relationship of the second group has been established, and the binding relationship identification information uniquely indicates the binding relationship established by the second group with the first group. Further, the second indication message may further include a group role of the second group, and may also include a group role of the first group and the second group respectively.
  • the third indication message may be sent to the system interworking entity, where the third indication message includes the identifier of the first group and the The identifier of the second group is used to notify that the binding relationship between the first group and the second group has been established. Further, if the group connection request message further includes the group role of the first group and the group role of the second group, the binding relationship includes the group role and the location of the first group. The group role of the second group; the third indication message further includes a group role corresponding to the first group and the second group respectively.
  • the group connection device may receive the group connection release request message, where the group connection release request message includes the identifier of the target group, and the target group If the group is the first group or the second group, the group connection device releases the binding relationship of the target group.
  • the group connection device may further receive a group connection release request message, where the group connection release request message includes the identifier of the target group and the binding relationship identification information of the target group, and the target group The group is the first group or the second group. Then, the group connection device releases the binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • the group connection device may send a fourth indication message to the first device of the first communication system, where the fourth indication message is used to notify the target group.
  • the binding relationship has been released;
  • the group connection device may send a fifth indication message to the second service control entity of the second communication system, and the fifth The indication message is used to notify the target group that the binding relationship has been released.
  • the group connection device may further receive a first group call request message, where the first group call request message includes an identifier of the first group, when the first group and the When the second group has a binding relationship, sending a second group call request message to the second service control entity of the second communication system, where the second group call request message carries the second group And the second group call request message is used to indicate that the second service control entity joins the second group into group communication with the first group.
  • This implementation scenario can be specifically implemented in conjunction with the embodiment shown in Figures 7a and 7b.
  • the group connection and the group connection release method will be described in detail below through the embodiments shown in FIGS. 2b to 6b.
  • the group binding relationship is created and maintained by the system interworking entity; in the embodiment shown in FIG. 5a - FIG. 6b, the group binding relationship is determined by the system group. Management server creation and maintenance.
  • an embodiment of the present application provides another method for connecting a population group.
  • the method includes, but is not limited to, the following steps.
  • Step S101 The group management client of the first communication system sends a first group connection request message to the group management server of the first communication system.
  • the first group connection request message includes an identifier of the first group of the first communication system and an identifier of the second group of the second communication system, where the first group connection request message is used to request to establish the first group and the first group
  • the binding relationship between the two groups refers to a group in the first communication system
  • the second group refers to a group in the second communication system.
  • the binding relationship between the first group and the second group refers to associating the first group with the second group to form a logical whole. When there is a binding relationship, the first group Or when any one of the second group is called, another group will also be called.
  • the group management client of the first communication system may obtain the identifier of the second group by interacting with other devices, or may pre-store the identifier of the second group in the first communication system by using a pre-configured manner.
  • the group management client there is no specific limitation here.
  • the first group connection request message may further include a group role of the first group and a group role of the second group.
  • the group role refers to the role played by the group call, which may be a master group role or a non-master/slave group role. Specifically, if there is only one master group role in a group communication, then only the master group role can be specified. Other group roles can default to non-master/slave group roles by default.
  • the first group connection request message may include a first group as a master group role, and the second group is a non-master/slave group role; the first group connection request message may also include the first group The master group role, and the group role of the second group default, then the second group can be the non-master/slave group role by default.
  • Step S102 The group management server of the first communication system checks whether the user of the group management client of the first communication system has the right to request the first group to establish a binding relationship with the second group. If there is a right to request the first group to establish a binding relationship with the second group, steps S103-S112 are performed; otherwise, step S113 is performed.
  • the group management server of the first communication system After receiving the first group connection request message, the group management server of the first communication system needs to perform an authorization check on the user of the group management client of the first communication system, that is, check the group management client of the first communication system. Whether the terminal has the right to request the first group to establish a binding relationship with the second group.
  • the group management server of the first communication system pre-stores the authorization information of the multiple groups of the first communication system, and the authorization information may include authorized users and authorized users corresponding to the respective groups.
  • the rights that are available, that is, the authorization information can be used to obtain the authorization of a group of authorized users to perform operations on the group.
  • the authorization information herein may be group information of each group, or may be a mapping relationship stored as an independent table or an entire array, and is not specifically limited herein.
  • the group management server of the first communication system does not store the authorization information related to the group management client of the first communication system, and may be from the first service control entity of the first communication system. Obtaining user subscription configuration information of the group management client of the first communication system, such as what operations the user can perform, and obtaining authorization information of the user of the group management client of the first communication system from the subscription configuration information. And then conduct an authorization check.
  • the first service control entity may be an emergency task service server, including an emergency task push-to-talk server, an emergency task video server, or an emergency task data server.
  • the group management server of the first communication system can check whether the user of the group management client of the first communication system has the right to request the first group to establish a binding relationship with the second group. If the user of the group management client of the first communication system has the right to request the first group to establish a binding relationship with the second group, the authorization check is successful, otherwise the authorization check fails.
  • the group management server of the first communication system is the network device of the first communication system
  • the object of the check is generally for the first group. That is to say, it is actually checking whether the user of the group management client of the first communication system has the right to request the first group to establish a binding relationship with other groups.
  • step S102 may be an optional step.
  • the embodiment of the present application may also directly perform the steps S103-S112 without performing step S102.
  • Step S103 The group management server of the first communication system sends a second group connection request message to the system interworking entity.
  • the group management server of the first communication system sends a second group connection request message to the system interworking entity, where the second group connection request message is a group connection request message, including the first group The identifier of the first group and the identifier of the second group received in the group connection request message.
  • the second group connection request message also includes the group role of the first group and The group role of the second group.
  • Step S106 The system interworking entity establishes a binding relationship between the first group and the second group.
  • the system interworking entity establishes a binding relationship between the first group and the second group.
  • the binding relationship between the first group and the second group may be established in a form of a table, that is, the binding relationship table is added.
  • the identifier of the first group and the identifier of the second group indicate that the two have a binding relationship. For example, if the identifier of the first group is 1-12 and the identifier of the second group is 2-02, the binding relationship group corresponding to the number 1 may be added in the binding relationship table shown in Table 1. -12 and 2-02.
  • the system interworking entity can establish a binding relationship between the first group and the second group.
  • the binding relationship established for the first group and the second group may further include binding relationship identifier information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, for example, (1-12 2-02); or may be a group identifier of any one of the binding relationships.
  • 2-02 may also be a newly created identifier for indicating a binding relationship between the first group and the second group, such as the number in Table 1.
  • the second group connection request message includes the group role of the first group and the group role of the second group
  • the binding relationship may also include a group role of the first group and a group role of the second group, such as the binding relationship table shown in Table 2.
  • step S106 before step S106, step S104 and step S105 may also be performed:
  • Step S104 The system interworking entity sends an authorization indication message to the authorization checking entity of the second communication system.
  • the authorization checking entity of the second communication system may be a network device or a module in the network device, such as a software program module in a server or a server, which is not limited herein.
  • the authorization indication message carries the identifier of the second group, and is used to indicate that the authorization checking entity of the second communication system performs an authorization check on the second group, and checks whether the second group can establish a binding relationship.
  • the authorization indication message carries the identifier information of the user of the group management client of the first communication system.
  • the authorization checking entity may also pre-store the authorization information of the multiple groups of the second communication system, and the authorization information may include the authorized users corresponding to each group and the authorized users, that is, It is said that the authorization information can obtain the authorized user of a certain group to have the right to perform operations on the group. Therefore, the group management server of the first communication system can check whether the second group is allowed to establish a binding relationship. It should be noted that, since the authorization checking entity of the second communication system is the network device of the second communication system, the object of the check is generally for the second group.
  • Step S105 When the authorization checking entity of the second communication system allows the second group to establish a binding relationship, the authorization checking entity of the second communication system sends an authorization success response message to the system interworking entity.
  • the authorization success response message is used to instruct the second communication system to allow the second group to establish a binding relationship. Thereby step S106 is further performed.
  • Step S107 The system interworking entity sends a first indication message to the group management server of the first communication system.
  • the first indication message may be a group connection response message, and is used to notify that the binding relationship of the first group of the group management server of the first communication system has been established.
  • the system interworking entity can determine that the binding relationship of the first group has been established by using the message name.
  • the first indication message may include binding relationship information of the first group, and the binding relationship information may be a binding relationship indication.
  • the binding relationship indication is used to indicate that the binding relationship of the first group is established.
  • the binding relationship indication may be one reserved bit position 1 in the first indication message, or may be a new bit position 0, used for Indicates the establishment of the first group binding relationship.
  • the binding relationship information of the first group in the first indication message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be a group identifier of any one of the binding relationships, or may be newly created for indicating The identifier of the binding relationship between the first group and the second group. Therefore, the first indication message may indicate that the binding relationship of the first group has been established, and the binding relationship identification information uniquely indicates the binding relationship established between the first group and the second group.
  • the first indication message may further carry an identifier of another group that establishes a binding relationship with the first group.
  • the first indication message may further include a group role of the first group, and may also include a group role of the first group and the second group respectively.
  • Step S108 The system interworking entity sends a second indication message to the second service control entity of the second communication system.
  • the second indication message is used to notify that the binding relationship of the second group has been established.
  • the second indication message may include a binding relationship indication, where the binding relationship indication is used to indicate that the binding relationship of the second group has been established.
  • the second indication message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be an identifier of any one of the binding relationships, or may be newly created for indicating the first The identifier of the binding relationship between the group and the second group.
  • the second indication message is used to indicate that the binding relationship of the second group has been established, and the binding relationship identification information uniquely indicates the binding relationship established by the second group with the first group. Further optionally, the second indication message may further carry an identifier of another group that establishes a binding relationship with the second group.
  • the second indication message may further include a group role of the second group, and may also include a group role of the first group and the second group respectively.
  • steps S109-S112 may also be performed:
  • Step S109 the group management server of the first communication system increases the binding relationship information of the first group.
  • the group management server of the first communication system adds corresponding binding relationship information to the first group.
  • the binding relationship information is determined according to the first indication message.
  • the binding relationship information may be a binding relationship indication that is bound to the first group, and may also include binding relationship identification information, indicating that the binding relationship of the first group is established, and the binding relationship identification information is uniquely indicated.
  • the binding relationship information may further include a group role of the first group, and may also include a group role of the first group and the second group respectively.
  • Step S110 The group management server of the first communication system sends a group connection notification message to the first service control entity of the first communication system.
  • the group connection notification message is used to notify the first group of the first service control entity of the first communication system that the first group has established a connection relationship.
  • the group connection notification message may include an identifier of the first group, and may also include an identifier of the first group and an indication of the binding relationship.
  • the group connection notification message may further include the identifier of the first group, the binding relationship identifier information, and the binding relationship indication.
  • the group connection notification message may further include a group role of the first group, and may also include a group role of the first group and the second group, respectively, according to the group management server of the first communication system.
  • the received first indication message is determined.
  • Step S111 the first service control entity of the first communication system adds the binding relationship information of the first group.
  • the group management server of the first communication system adds corresponding binding relationship information to the first group.
  • the binding relationship information is determined according to the group connection notification message.
  • the binding relationship information may be a binding relationship indication that is bound to the first group, and may also include binding relationship identification information, indicating that the binding relationship of the first group is established, and the binding relationship identification information is uniquely indicated.
  • the binding relationship information may further include a group role of the first group, and may also include a group role of the second group.
  • Step S112 The group management server of the first communication system sends a group connection response message to the group management client of the first communication system, indicating that the group binding relationship is successfully established.
  • the group management server of the first communication system may determine that the binding relationship is successfully established, and send a group connection response message to the group management client of the first communication system, indicating that the group binding relationship is established. success.
  • step S109 there is no necessary sequence of execution between step S109, step S110-S111, and step S112, and adjustment may be made according to the situation.
  • Step S113 The group management server of the first communication system sends a group connection response message to the group management client of the first communication system, indicating that the group binding relationship establishment fails.
  • the group management server of the first communication system After the authorization check fails, the group management server of the first communication system sends a group connection response message to the group management client of the first communication system, indicating that the group binding relationship establishment fails.
  • an embodiment of the present application provides a group connection cancellation method.
  • This method corresponds to the group connection method shown in Fig. 2b, and the solution can be implemented after the embodiment shown in Fig. 2b.
  • the method includes, but is not limited to, the following steps.
  • Step S201 the group management client of the first communication system sends a first group connection release request message to the group management server of the first communication system.
  • the first group connection release request message includes an identifier of the target group, and the target group is the first group or the second group.
  • the first group connection release request message is used to request to release the binding relationship of the target group.
  • the target group may have only one binding relationship, and multiple binding relationships may exist. Then, the first group connection release request message is used to request to cancel all binding relationships of the target group.
  • the first group connection release request message includes an identifier of the target group and binding relationship identification information of the target group, where the target group is the first group or the second group.
  • the target group may have multiple binding relationships, and the binding relationship identification information is used to indicate a specific target binding relationship of the target group.
  • the binding relationship identification information may be a target group. The combination of the identifier of the group and the identifiers of other groups that establish a target binding relationship with the target group; or other information that can identify the target binding relationship, such as a numeric number; or any group in the binding relationship
  • the group logo is not specifically limited here.
  • Step S202 The group management server of the first communication system checks whether the user of the group management client of the first communication system has the right to request the target group to unbind the relationship. If there is a right to request the target group to release the binding relationship, steps S203-S209 are performed; otherwise, step S210 is performed.
  • the group management server of the first communication system After receiving the first group connection release request message, the group management server of the first communication system needs to perform an authorization check on the user of the group management client of the first communication system, that is, check the group management of the first communication system. Whether the client has permission to request the target group to unbind.
  • the group management server of the first communication system pre-stores the authorization information of the multiple groups of the first communication system, and the authorization information may include authorized users and authorized users corresponding to the respective groups. Permissions, that is, authorization information can be used to obtain the authorization of a group of authorized users to perform operations on the group.
  • the authorization information herein may be a part of the group information or the contract configuration information of each group, or may be a mapping relationship stored as an independent table or an entire array, and is not specifically limited herein.
  • the authorization information of the user of the group management client of the first communication system is not stored in the group management server of the first communication system, and may be urgent from the first service control entity of the first communication system.
  • the first service control entity may be an emergency task service server, including an emergency task push-to-talk server, an emergency task video server, or an emergency task data server.
  • the group management server of the first communication system can check whether the user of the group management client of the first communication system has the right to request the target group to unbind the relationship. If the user of the group management client of the first communication system has the right to request the target group to be unbound, the authorization check is successful, otherwise the authorization check fails.
  • step S202 may be used as an optional step.
  • the embodiment of the present application may also directly perform the steps S203-S209 without performing step S202.
  • Step S203 The group management server of the first communication system sends a second group connection release request message to the system interworking entity.
  • the group management server of the first communication system sends a second group connection request message to the system interworking entity, where the second group connection release request message is a group connection release request message.
  • the second group connection release request message may include the identifier of the target group, and may include the identifier of the target group and the binding relationship identifier information of the target group, according to the content carried in the first group connection release request message.
  • the second group connection release request message includes group binding relationship identification information, and step S2041 is performed.
  • the second group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, and step S2042 is performed.
  • the second group connection release request message includes the identifier of the target group, and step S2043 is performed.
  • Step S2041 The system interworking entity releases the binding relationship indicated by the group binding relationship identifier.
  • the system interworking entity releases the binding relationship indicated by the group binding relationship identifier established before.
  • the group binding relationship identifier may be any one of the group identifiers in the binding relationship.
  • Step S2042 The system interworking entity releases the binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • the system interworking entity releases the binding relationship between the target group and other groups in the target binding relationship.
  • the target group A includes two binding relationships, namely, a group binding relationship: A and B are bound, and the group binding relationship is two: A, C, and D are bound, and the binding relationship identification information is assumed to be The identifier of the group binding relationship 2 (such as ⁇ A, C, D>, or number 2), then the system interworking entity releases the binding relationship between the target group A and the group C and the group D, but the group The binding relationship between C and group D still exists. If only two groups are included in the target binding relationship: the target group and another group, the system interworking entity releases the binding relationship between the target group and other groups in the target binding relationship. The binding relationship cannot be established, and the system interworking entity deletes the binding relationship.
  • Step S2043 The system interworking entity releases the binding relationship between the target group and other groups in the binding relationship including the target group identifier.
  • the target group A includes two binding relationships, namely, a group binding relationship: A and B are bound, and the group binding relationship is two: A, C, and D are bound.
  • the system interworking entity unbinds the binding relationship between the two binding relationships and other groups. If only two groups are included in the target binding relationship: the target group and another group, the system interworking entity releases the binding relationship between the target group and other groups in the target binding relationship. The binding relationship cannot be established, and the system interworking entity deletes the binding relationship. In the above example, after the binding relationship of B is released, the binding relationship is also deleted by the system interworking entity.
  • step S2051 is performed; when the target group is the second group, performing step Step S2052.
  • Step S2051 The system interworking entity sends a fourth indication message to the group management server of the first communication system.
  • the fourth indication message is used to notify that the binding relationship of the group management server target group of the first communication system has been released.
  • the fourth indication message may be a group connection cancellation response message, so that the group management server of the first communication system knows that the group connection release request of the target group requested by itself has been responded.
  • Step S2052 The system interworking entity sends a fifth indication message to the second service control entity of the second communication system.
  • the fifth indication message is used to notify the second service control entity that the binding relationship of the target group of the second communication system has been released.
  • the fifth indication message may include an identifier of the target group, and may further include binding relationship identification information of the target group, and is determined according to the second group connection release request message.
  • steps S206-S209 may also be performed:
  • Step S206 the group management server of the first communication system deletes the binding relationship information of the target group.
  • the group management server of the first communication system deletes the previously added binding relationship information of the first group. Specifically, according to the content carried in the first group connection release request message, all the binding relationship information of the target group is deleted, or the binding relationship information of the target group with other groups in the target binding relationship is deleted.
  • Step S207 the group management server of the first communication system sends a group connection cancellation notification message to the first service control entity of the first communication system.
  • the group connection notification message is used to notify that the binding relationship of the first service control entity target group of the first communication system has been released.
  • the group connection release notification message may include the identifier of the first group, and may also include the identifier of the first group and the binding relationship identifier information, and is determined according to the second group connection release request message.
  • Step S208 The first service control entity of the first communication system deletes the binding relationship information of the target group.
  • the first service control entity of the first communication system deletes the previously added binding relationship information of the first group.
  • the binding relationship information of the target group may be deleted according to the content carried in the group connection notification message, or the binding relationship information of the target group with other groups in the target binding relationship may be deleted.
  • Step S209 The group management server of the first communication system sends a group connection cancellation response message to the group management client of the first communication system, indicating that the group binding relationship is successfully cancelled.
  • the group management server of the first communication system may determine that the binding relationship is successfully cancelled, thereby sending a group connection cancellation response message to the group management client of the first communication system, indicating the group binding relationship. Unsuccessful.
  • step S206 steps S207-S208 and step S209, and adjustment can be made according to the situation.
  • Step S210 The group management server of the first communication system sends a group connection cancellation response message to the group management client of the first communication system, indicating that the group binding relationship is unsuccessful.
  • the group management server of the first communication system After the authorization check fails, the group management server of the first communication system sends a group connection release response message to the group management client of the first communication system, indicating that the group binding relationship is unsuccessful.
  • an embodiment of the present application provides another method for connecting a population group.
  • the method includes, but is not limited to, the following steps.
  • Step S301 the service client of the first communication system sends the first service control entity to the first service control entity of the first communication system.
  • a group connection request message A group connection request message.
  • the first group connection request message includes an identifier of the first group of the first communication system and an identifier of the second group of the second communication system, where the first group connection request message is used to request to establish the first group and the first group
  • the binding relationship between the two groups refers to a group in the first communication system
  • the second group refers to a group in the second communication system.
  • the binding relationship between the first group and the second group refers to associating the first group with the second group to form a logical whole. When there is a binding relationship, the first group Or when any one of the second group is called, another group will also be called.
  • the service client of the first communication system may obtain the identifier of the second group by interacting with other devices, or may pre-store the identifier of the second group in the service of the first communication system in a pre-configured manner.
  • the client there is no specific limit here.
  • the first group connection request message may further include a group role of the first group and a group role of the second group.
  • the group role refers to the role played by the group call, which may be a master group role or a non-master/slave group role. Specifically, if there is only one master group role in a group communication, then only the master group role can be specified. Other group roles can default to non-master/slave group roles by default.
  • the first group connection request message may include a first group as a master group role, and the second group is a non-master/slave group role; the first group connection request message may also include the first group The master group role, and the group role of the second group default, then the second group can be the non-master/slave group role by default.
  • Step S302 The first service control entity of the first communication system checks whether the user of the service client of the first communication system has the right to request the first group to establish a binding relationship with the second group. If there is a right to request the first group to establish a binding relationship with the second group, steps S303-S313 are performed; otherwise, step S314 is performed.
  • the first service control entity of the first communication system After receiving the first group connection request message, the first service control entity of the first communication system needs to perform an authorization check on the user of the service client of the first communication system, that is, check whether the service client of the first communication system has Requesting permission for the first group to establish a binding relationship with the second group.
  • the first service control entity of the first communication system pre-stores the subscription configuration information of the user of the service client of the first communication system, and the subscription configuration information includes which groups the user can perform.
  • the subscription configuration information includes which groups the user can perform.
  • the first service control entity of the first communication system pre-stores the authorization information of the multiple groups of the first communication system, and the authorization information may include the authorized users corresponding to each group and Authorized users have the authority, that is, through the authorization information, the authorized users of a certain group can have the right to perform operations on the group.
  • the authorization information herein may be a part of the group information or the contract configuration information of each group, or may be a mapping relationship stored as an independent table or an entire array, and is not specifically limited herein.
  • the authorization information of the user of the service client is not stored in the first service control entity of the first communication system, and the authorization information of the user may be obtained from the first group management server of the first communication system. And then conduct an authorization check.
  • the first service control entity of the first communication system can check the user of the service client of the first communication system Whether there is permission to request the first group to establish a binding relationship with the second group. If the user of the service client of the first communication system has the right to request the first group to establish a binding relationship with the second group, the authorization check is successful, otherwise the authorization check fails.
  • the object of the check is generally for the first group. That is to say, it is actually checking whether the user of the service client of the first communication system has the right to request the first group to establish a binding relationship with other groups.
  • step S302 can be used as an optional step.
  • the embodiment of the present application may also directly perform the steps S303-S313 without performing step S302.
  • Step S303 the first service control entity of the first communication system sends a second group connection request message to the group management server of the first communication system.
  • the second group connection request message includes the identifier of the first group and the identifier of the second group. Further optionally, the second group connection request message may further include a group role of the first group and a group role of the second group.
  • Step S304 the group management server of the first communication system sends a third group connection request message to the system interworking entity.
  • the third group connection request message is a group connection request message, and includes an identifier of the first group and an identifier of the second group received from the second group connection request message. Further optionally, the third group connection request message may further include a group role of the first group and a group role of the second group.
  • the group management server of the first communication system may further perform an authorization check to check whether the first group and the second group can establish a binding relationship.
  • the group management server of the first communication system may further perform an authorization check on the group management client of the first communication system, that is, check the group management of the first communication system. Whether the client has permission to request the target group to unbind.
  • the group management server of the first communication system pre-stores the authorization information of the plurality of groups of the first communication system, and the authorization information may include the authorized users corresponding to each group and the authorized users, that is, Authorization information can give authorized users of a certain group the right to perform operations on the group.
  • the authorization information herein may be a part of the group information or the contract configuration information of each group, or may be a mapping relationship stored as an independent table or an entire array, and is not specifically limited herein.
  • Step S307 the system interworking entity establishes a binding relationship between the first group and the second group.
  • step S307 step S305 and step S306 may also be performed:
  • Step S305 the system interworking entity sends an authorization indication message to the authorization checking entity of the second communication system.
  • Step S306 when the authorization checking entity of the second communication system allows the second group to establish a binding relationship, the authorization checking entity of the second communication system sends an authorization success response message to the system interworking entity.
  • Step S308 the system interworking entity sends a first indication message to the group management server of the first communication system.
  • Step S309 the system interworking entity sends a second indication message to the second service control entity of the second communication system.
  • steps S310-S313 may also be performed:
  • Step S310 the group management server of the first communication system increases the binding relationship information of the first group.
  • Step S311 the group management server of the first communication system sends a group connection response message to the first service control entity of the first communication system.
  • the group connection response message is used to notify the first group of the first service control entity of the first communication system that the first group has established a connection relationship. Similar to step S308, in a possible implementation scenario, the system interworking entity determines that the binding relationship of the first group has been established by using the message name. In another possible implementation scenario, the group connection response message may include binding relationship information of the first group, and the binding relationship information may be a binding relationship indication. The binding relationship indication is used to indicate that the binding relationship of the first group is established. For example, the binding relationship indication may be one reserved bit position 1 in the first indication message, or may be a new bit position 0, used for Indicates the establishment of the first group binding relationship.
  • the binding relationship information of the first group of the group connection response message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be an identifier of any group in the binding relationship, or may be newly created for indicating the first The identifier of the binding relationship between a group and the second group.
  • the group connection response message may indicate that the binding relationship of the first group has been established, and the binding relationship identification information uniquely indicates the binding relationship established between the first group and the second group.
  • the group connection response message may further carry identifiers of other groups that establish a binding relationship with the first group.
  • the group connection response message may further include a group role of the first group, and may also include a group role of the first group and the second group respectively.
  • step S310 there is no necessary sequence of execution between step S310 and step S311, and adjustment may be made according to the situation.
  • Step S312 the first service control entity of the first communication system adds the binding relationship information of the first group.
  • Step S313 The first service control entity of the first communication system sends a group connection response message to the service client of the first communication system, indicating that the group binding relationship is successfully established.
  • the first service control entity of the first communication system may determine that the binding relationship is successfully established, and send a group connection response message to the service client of the first communication system, indicating The group binding relationship was established successfully.
  • step S312 there is no necessary sequence of execution between step S312 and step S313, and adjustment may be made according to the situation.
  • Step S314 The first service control entity of the first communication system sends a group connection response message to the service client of the first communication system, indicating that the group binding relationship establishment fails.
  • the first service control entity of the first communication system After the authorization check fails, the first service control entity of the first communication system sends a group connection response message to the service client of the first communication system, indicating that the group binding relationship establishment fails.
  • an embodiment of the present application provides another method for releasing a population group connection.
  • the method and the group shown in Figure 3a The group connection method is corresponding, and the solution can be implemented after the embodiment shown in Fig. 3a.
  • the method includes, but is not limited to, the following steps.
  • Step S401 the service client of the first communication system sends a first group connection release request message to the first service control entity of the first communication system.
  • the first group connection release request message includes an identifier of the target group, and the target group is the first group or the second group.
  • the first group connection release request message is used to request to release the binding relationship of the target group.
  • the target group may have only one binding relationship, and multiple binding relationships may exist. Then, the first group connection release request message is used to request to cancel all binding relationships of the target group.
  • the first group connection release request message includes an identifier of the target group and binding relationship identification information of the target group, where the target group is the first group or the second group.
  • the target group may have multiple binding relationships, and the binding relationship identification information is used to indicate a specific target binding relationship of the target group.
  • the binding relationship identification information may be a target group. The combination of the identifier of the group and the identifiers of other groups that establish a target binding relationship with the target group; or any group identifier in the binding relationship; or other information that can identify the target binding relationship, such as a number No. There is no specific limit here.
  • Step S402 the first service control entity of the first communication system checks whether the service client of the first communication system has the right to request the target group to unbind the relationship. If there is a right to request the target group to release the binding relationship, steps S403-S410 are performed; otherwise, step S411 is performed.
  • the first service control entity of the first communication system After receiving the first group connection release request message, the first service control entity of the first communication system needs to perform an authorization check on the user of the service client of the first communication system, that is, check whether the service client of the first communication system checks whether the service client of the first communication system is Have permission to request the target group to unbind.
  • the first service control entity of the first communication system pre-stores the subscription configuration information of the user of the service client of the first communication system, and the subscription configuration information includes which groups the user can perform.
  • the subscription configuration information includes which groups the user can perform.
  • the first service control entity of the first communication system pre-stores the authorization information of the multiple groups of the first communication system, and the authorization information may include the authorized users corresponding to each group and Authorized users have the authority, that is, through the authorization information, the authorized users of a certain group can have the right to perform operations on the group.
  • the authorization information herein may be a part of the group information or the contract configuration information of each group, or may be a mapping relationship stored as an independent table or an entire array, and is not specifically limited herein.
  • the authorization information of the user of the service client is not stored in the first service control entity of the first communication system, and the authorization information of the user may be obtained from the first group management server of the first communication system. And then conduct an authorization check.
  • the first service control entity of the first communication system can check whether the user of the service client of the first communication system has the right to request the target group to unbind the relationship. If the user of the service client of the first communication system has the right to request the target group to be unbound, the authorization check is successful, otherwise the authorization check fails.
  • the object of the check is generally for the first group. That is to say, it is actually checking whether the user of the service client of the first communication system has the right to request the first group to unbind the relationship with other groups.
  • step S402 can be used as an optional step.
  • the embodiment of the present application may also directly perform the steps S403-S410 without performing step S102.
  • Step S403 the first service control entity of the first communication system sends a second group connection release request message to the group management server of the first communication system.
  • the second group connection release request message includes the identifier of the target group, and the target group is the first group or The second group.
  • the second group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, where the target group is the first group or the second group.
  • Step S404 the group management server of the first communication system sends a third group connection release request message to the system interworking entity.
  • the third group connection release request message is a group connection release request message, and includes the identifier of the target group or the identifier of the target group and the binding of the target group received from the second group connection release request message. Relationship identification information.
  • the second group connection release request message includes group binding relationship identification information, and step S4051 is performed.
  • the second group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, and step S4052 is performed.
  • the second group connection release request message includes the identifier of the target group, and step S4053 is performed.
  • Step S4051 The system interworking entity releases the binding relationship indicated by the group binding relationship identifier.
  • Step S4052 The system interworking entity releases the binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • Step S4053 The system interworking entity releases the binding relationship between the target group and other groups in the binding relationship including all the target group identifiers.
  • step S4061 When the target group is the first group, step S4061 is performed; when the target group is the second group, step S4062 is performed.
  • Step S4061 The system interworking entity sends a fourth indication message to the group management server of the first communication system.
  • Step S4062 The system interworking entity sends a fifth indication message to the second service control entity of the second communication system.
  • steps S407-S410 may also be performed:
  • Step S407 the group management server of the first communication system deletes the binding relationship information of the target group.
  • the group management server of the first communication system deletes the previously added binding relationship information of the first group. Specifically, according to the content carried in the second group connection release request message, all the binding relationship information of the target group is deleted, or the binding relationship information of the target group with other groups in the target binding relationship is deleted.
  • Step S408 the group management server of the first communication system sends a group connection cancellation response message to the first service control entity of the first communication system.
  • the group connection response message is used to notify the binding relationship of the target group of the first service control entity of the first communication system Has been lifted. Thereby the first service control entity of the first communication system knows that the second group connection release request of the target group requested by itself has been responded.
  • step S407 there is no necessary sequence of execution between step S407 and step S408, and adjustment may be made according to the situation.
  • Step S409 the first service control entity of the first communication system deletes the binding relationship information of the target group.
  • the first service control entity of the first communication system deletes the binding relationship information of the previously added target group. Specifically, according to the content carried in the first group connection release request message, all the binding relationship information of the target group is deleted, or the binding relationship information of the target group with other groups in the target binding relationship is deleted.
  • Step S410 The first service control entity of the first communication system sends a group connection release response message to the service client of the first communication system, indicating that the group binding relationship is successfully cancelled.
  • the first service control entity of the first communication system may determine that the binding relationship is successfully cancelled, thereby sending a group connection cancellation response message to the group management client of the first communication system, indicating the group The binding relationship is unsuccessful.
  • step S409 there is no necessary sequence of execution between step S409 and step S410, and adjustment may be made according to the situation.
  • Step S411 the first service control entity of the first communication system sends a group connection release response message to the service client of the first communication system, indicating that the group binding relationship is unsuccessful.
  • the first service control entity of the first communication system After the authorization check fails, the first service control entity of the first communication system sends a group connection release response message to the service client of the first communication system, indicating that the group binding relationship is unsuccessful.
  • an embodiment of the present application provides another method for connecting a population group.
  • the method includes, but is not limited to, the following steps.
  • Step S501 The service client of the first communication system sends a first group connection request message to the first service control entity of the first communication system.
  • Step S502 The first service control entity of the first communication system checks whether the service client of the first communication system has the right to request the first group to establish a binding relationship with the second group. If there is a right to request the first group to establish a binding relationship with the second group, steps S503-S512 are performed; otherwise, step S513 is performed.
  • step S502 may be used as an optional step.
  • the embodiment of the present application may also directly perform the steps S503-S512 without performing step S502.
  • Step S503 the first service control entity of the first communication system sends a second group connection request message to the system interworking entity.
  • the second group connection request message includes the identifier of the first group and the identifier of the second group. Further optionally, the second group connection request message may further include a group role of the first group and a group role of the second group.
  • Step S506 the system interworking entity establishes a binding relationship between the first group and the second group.
  • step S504 and step S505 may also be performed:
  • Step S504 the system interworking entity sends an authorization indication message to the authorization checking entity of the second communication system.
  • Step S505 When the authorization checking entity of the second communication system allows the second group to establish a binding relationship, the authorization checking entity of the second communication system sends an authorization success response message to the system interworking entity.
  • Step S507 The system interworking entity sends a first indication message to the first service control entity of the first communication system.
  • the first indication message may be a group connection response message, and is used to notify that the binding relationship of the first group of the first service control entity of the first communication system has been established.
  • the system interworking entity can determine that the binding relationship of the first group has been established by using the message name.
  • the first indication message may include binding relationship information of the first group, and the binding relationship information may be a binding relationship indication.
  • the binding relationship indication is used to indicate that the binding relationship of the first group is established.
  • the binding relationship indication may be one reserved bit position 1 in the first indication message, or may be a new bit position 0, used for Indicates the establishment of the first group binding relationship.
  • the binding relationship information of the first group in the first indication message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be a group identifier of any one of the binding relationships, or may be newly created for indicating The identifier of the binding relationship between the first group and the second group. Therefore, the first indication message may indicate that the binding relationship of the first group has been established, and the binding relationship identification information uniquely indicates the binding relationship established between the first group and the second group.
  • the identifier of the other group that establishes the binding relationship with the first group may also be carried in the further optional first indication message.
  • the first indication message may further include a group role of the first group, and may also include a group role of the first group and the second group respectively.
  • Step S508 the system interworking entity sends a second indication message to the second service control entity of the second communication system.
  • steps S509-S510 may also be performed:
  • Step S509 The first service control entity of the first communication system adds the binding relationship information of the first group.
  • Step S510 The first service control entity of the first communication system sends a group connection response message to the service client of the first communication system, indicating that the group binding relationship is successfully established.
  • steps S511-S512 may also be performed:
  • Step S511 the system interworking entity sends a group connection notification message to the group management server of the first communication system.
  • the group connection notification message is used to notify the group management server of the first communication system that the first group has established a connection relationship.
  • the group connection notification message may include an identifier of the first group, and may also include an identifier of the first group and an indication of the binding relationship.
  • the group connection notification message may further include the identifier of the first group, the binding relationship identifier information, and the binding relationship indication.
  • the group connection notification message may further include a group role of the first group, and may also include the first group
  • the group roles of the group and the second group are determined according to the second group connection request message received by the system interworking entity.
  • Step S512 the group management server of the first communication system increases the binding relationship information of the first group.
  • the group management server of the first communication system adds corresponding binding relationship information to the first group.
  • the binding relationship information is determined according to the group connection notification message.
  • the binding relationship information may be a binding relationship indication that is bound to the first group, and may also include binding relationship identification information, indicating that the binding relationship of the first group is established, and the binding relationship identification information uniquely indicates the first The binding relationship between the group and the second group. Further, the binding relationship information may further include a group role of the first group, and may also include a group role of the second group.
  • Step S513 The first service control entity of the first communication system sends a group connection response message to the service client of the first communication system, indicating that the group binding relationship establishment fails.
  • an embodiment of the present application provides another method for releasing a population group connection.
  • This method corresponds to the group connection method shown in Fig. 4a, and the present embodiment can be implemented after the embodiment shown in Fig. 4a.
  • the method includes, but is not limited to, the following steps.
  • Step S601 The service client of the first communication system sends a first group connection release request message to the first service control entity of the first communication system.
  • Step S602 The first service control entity of the first communication system checks whether the service client of the first communication system has the right to request the target group to release the binding relationship. If there is a right to request the target group to release the binding relationship, steps S603-S609 are performed; otherwise, step S610 is performed.
  • step S602 may be an optional step, and the embodiment of the present application may also directly perform step S603-S609 without performing step S602.
  • Step S603 the first service control entity of the first communication system sends a second group connection release request message to the system interworking entity.
  • the second group connection release request message includes the identifier of the target group, and the target group is the first group or The second group.
  • the second group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, where the target group is the first group or the second group.
  • the second group connection release request message includes group binding relationship identification information, and step S6041 is performed.
  • the second group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, and step S6042 is performed.
  • the second group connection release request message includes the identifier of the target group, and step S6043 is performed.
  • Step S6041 The system interworking entity releases the binding relationship indicated by the group binding relationship identifier.
  • Step S6042 The system interworking entity releases the binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • Step S6043 The system interworking entity releases the binding relationship between the target group and other groups in the binding relationship including all the target group identifiers.
  • step S6051 When the target group is the first group, step S6051 is performed; when the target group is the second group, step S6052 is performed.
  • Step S6051 The system interworking entity sends a fourth indication message to the first service control entity of the first communication system.
  • the fourth indication message is used to notify that the binding relationship of the target group of the first service control entity of the first communication system has been released.
  • the fourth indication message may be a group connection cancellation response message, so that the first service control entity of the first communication system knows that the group connection release request of the target group requested by itself has been responded.
  • Step S6052 The system interworking entity sends a fifth indication message to the second service control entity of the second communication system.
  • steps S606-S607 may also be performed:
  • Step S606 The first service control entity of the first communication system deletes the binding relationship information of the target group.
  • the first service control entity of the first communication system deletes the binding relationship information of the previously added target group. Specifically, according to the content carried in the first group connection release request message, all the binding relationship information of the target group is deleted, or the binding relationship information of the target group with other groups in the target binding relationship is deleted.
  • Step S607 The first service control entity of the first communication system sends a group connection release response message to the service client of the first communication system, indicating that the group binding relationship is successfully cancelled.
  • step S606 there is no necessary sequence of execution between step S606 and step S607, and adjustment may be made according to the situation.
  • steps S608-S609 may also be performed:
  • Step S608 the system interworking entity sends a group connection cancellation notification message to the group management server of the first communication system.
  • the group connection notification message is used to notify the group management server of the first communication system that the first group has been disconnected.
  • the group connection notification message may include an identifier of the target group, and may also include an identifier of the target group and binding relationship identification information of the target group.
  • Step S609 the group management server of the first communication system deletes the binding relationship information of the target group.
  • the group management server of the first communication system deletes the binding relationship information of the previously added target group.
  • the binding relationship information of the target group may be deleted according to the content carried in the group connection notification message, or the binding relationship information of the target group with other groups in the target binding relationship may be deleted.
  • Step S610 The first service control entity of the first communication system sends a group connection release response message to the service client of the first communication system, indicating that the group binding relationship is unsuccessful.
  • an embodiment of the present application provides another method for connecting a population group.
  • the method includes, but is not limited to, the following steps.
  • Step S701 the group management client of the first communication system sends the group management client of the first communication system to the group management server of the first communication system.
  • Group connection request message the group management client of the first communication system sends the group management client of the first communication system to the group management server of the first communication system.
  • Step S702 The group management server of the first communication system checks whether the group management client of the first communication system has the right to request the first group to establish a binding relationship with the second group. If there is a right to request the first group to establish a binding relationship with the second group, steps S703-S709 are performed; otherwise, step S710 is performed.
  • step S702 may be an optional step.
  • the embodiment of the present application may also directly perform the steps S703-S709 without performing step S702.
  • Step S703 the group management server of the first communication system establishes a binding relationship between the first group and the second group.
  • the group management server of the first communication system establishes a binding relationship between the first group and the second group.
  • the binding relationship between the first group and the second group may be established in a form of a table, that is, The identifier of the first group and the identifier of the second group are added in the binding relationship table, indicating that the two have a binding relationship.
  • the binding relationship group corresponding to the number 1 may be added in the binding relationship table shown in Table 1. -12 and 2-02.
  • the system interworking entity can establish a binding relationship between the first group and the second group.
  • the binding relationship established for the first group and the second group may further include binding relationship identifier information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, for example, (1-12 2-02); or an identifier of any one of the binding relationships, for example, 2 -02; may also be a newly created identifier for indicating a binding relationship between the first group and the second group, such as the number in Table 1.
  • the binding relationship may also include the group role of the first group and the second group.
  • Group roles such as the binding relationship table shown in Table 2.
  • the group management server of the first communication system may further send an authorization indication message to the authorization checking entity of the second communication system by the system interworking entity, when the authorization checking entity of the second communication system allows the second group to establish the binding.
  • the authorization checking entity of the second communication system transmits an authorization success response message to the system interworking entity, thereby executing step S703.
  • Step S704 the group management server of the first communication system sends a third indication message to the system interworking entity.
  • the third indication message may be a group connection notification message, where the third indication message includes an identifier of the first group and an identifier of the second group, and is used to notify the binding relationship between the first group and the second group of the interworking entity of the system It has been established. Further, the third indication message may further include binding relationship identification information of the first group and the second group. Further, optionally, the third indication message may further include a group role of the first group and a group role of the second group.
  • Step S704 is further performed after steps S705 and S706:
  • Step S705 The system interworking entity saves the binding relationship between the first group and the second group.
  • the system interworking entity may save the binding relationship between the first group and the second group. Similar to step S703, the saved relationship may be a relationship between the identifiers of the first group and the second group, for example, if the save In the binding relationship table, the identifier of the first group and the identifier of the second group are added in the binding relationship table, indicating that the two have a binding relationship. Further optionally, the binding relationship identification information of the first group and the second group may also be saved. Further, optionally, the group role of the first group and the group role of the second group may also be saved.
  • Step S706 the system interworking entity sends a second indication message to the second service control entity of the second communication system.
  • step S705 there is no necessary sequence of execution between step S705 and step S706, and adjustment may be made according to the situation.
  • Step S707 The group management server of the first communication system sends a first indication message to the group management client of the first communication system, indicating that the group binding relationship has been established.
  • the first indication message may be a group connection response message, and is used to notify that the binding relationship of the first group of the group management client of the first communication system has been established.
  • the system interworking entity can determine that the binding relationship of the first group has been established by using the message name.
  • the first indication message may include binding relationship information of the first group, and the binding relationship information may be a binding relationship indication.
  • the binding relationship indication is used to indicate that the binding relationship of the first group is established.
  • the binding relationship indication may be one reserved bit position 1 in the first indication message, or may be a new bit position 0, used for Indicates the establishment of the first group binding relationship.
  • the binding relationship information of the first group in the first indication message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be a group identifier of any one of the binding relationships, or may be newly created for indicating The identifier of the binding relationship between the first group and the second group. Therefore, the first indication message may indicate that the binding relationship of the first group has been established, and the binding relationship identification information uniquely indicates the binding relationship established between the first group and the second group.
  • the identifier of the other group that establishes the binding relationship with the first group may also be carried in the further optional first indication message.
  • the first indication message may further include a group role of the first group, and may also include a group role of the first group and the second group respectively.
  • Step S708 the group management server of the first communication system sends a group connection notification message to the first service control entity of the first communication system.
  • Step S709 the first service control entity of the first communication system adds the binding relationship information of the first group.
  • step S704 there is no necessary sequence of execution between step S704, step S707, and steps S708-S709, and adjustment may be made according to the situation.
  • Step S710 The group management server of the first communication system sends a group connection response message to the group management client of the first communication system, indicating that the group binding relationship establishment fails.
  • an embodiment of the present application provides another method for releasing a population group connection.
  • This method corresponds to the group connection method shown in Fig. 5a, and the present embodiment can be implemented after the embodiment shown in Fig. 5a.
  • the method includes, but is not limited to, the following steps.
  • Step S801 the group management client of the first communication system sends a group connection release request message to the group management server of the first communication system.
  • the group connection release request message includes an identifier of the target group, and the target group is the first group or the second group.
  • the group connection release request message is used to request to unbind the target group.
  • the target group may have only one binding relationship, or multiple binding relationships may exist. Then, the group connection release request message is used to request to cancel all binding relationships of the target group.
  • the group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, where the target group is the first group or the second group.
  • the target group may have multiple binding relationships, and the binding relationship identification information is used to indicate a specific target binding relationship of the target group.
  • the binding relationship identification information may be a target group. The identifier of the group and the identifier of other groups that establish a target binding relationship with the target group; or other information that can identify the target binding relationship, such as a numeric number; or a group of any one of the binding relationships Group identification, which is not specifically limited here.
  • Step S802 the group management server of the first communication system checks whether the group management client of the first communication system has the right to request the target group to establish a binding relationship. If there is a right to request the first group to establish a binding relationship with the second group, step S8031 or step S8032 or step S8033 and steps S804-S808 are performed; otherwise, step S809 is performed.
  • step S802 may be an optional step.
  • the embodiment of the present application may also directly perform step S8031 or step S8032 or step S8033 and steps S804-S808 without performing step S802.
  • the second group connection release request message includes group binding relationship identifier information, and step S8031 is performed.
  • the second group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, and step S8032 is performed.
  • the second group connection release request message includes the identifier of the target group, and step S8033 is performed.
  • Step S8031 The group management server of the first communication system releases the binding relationship indicated by the group binding relationship identifier.
  • the group management server of the first communication system releases the previously established binding relationship indicated by the group binding relationship identifier.
  • the group binding relationship identifier may be any one of the group identifiers in the binding relationship.
  • Step S8032 The group management server of the first communication system releases the binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • the group management server of the first communication system releases the binding relationship of the target group to other groups in the target binding relationship.
  • the target group A includes two binding relationships, namely, a group binding relationship: A and B are bound, and the group binding relationship is two: A, C, and D are bound, and the binding relationship identification information is assumed to be
  • the identifier of the group binding relationship 2 (such as ⁇ A, C, D>, or number 2)
  • the group management server of the first communication system releases the binding of the target group A and the group C and the group D.
  • the relationship is fixed, but the binding relationship between group C and group D still exists. If only two groups are included in the target binding relationship: the target group and another group, the group management server of the first communication system releases the target group in the target binding relationship with other groups. After the binding relationship is established, the binding relationship cannot be established.
  • the system interworking entity deletes the binding relationship.
  • Step S8033 The group management server of the first communication system releases the binding relationship between the target group and other groups in the binding relationship including all the target group identifiers.
  • the target group A includes two binding relationships, namely, a group binding relationship: A and B are bound, and the group binding relationship is two: A, C, and D are bound.
  • the group management server of the first communication system releases the binding relationship between the two binding relationships and the other groups in the target group identifier. If only two groups are included in the target binding relationship: the target group and another group, the group management server of the first communication system releases the target group in the target binding relationship with other groups. After the binding relationship, the binding relationship cannot be established, and the group management server of the first communication system deletes the binding relationship. In the above example, after the binding relationship of B is released, the binding relationship is also deleted by the system interworking entity.
  • Step S804 the group management server of the first communication system sends a first group connection release notification message to the system interworking entity.
  • the first group connection release notification message may include the identifier of the target group, or the identifier of the target group and the binding relationship identification information of the target group, and is determined according to the content carried in the group connection release request message.
  • the first group connection release notification message is used to notify the system interworking entity that the binding relationship of the target group has been released.
  • Step S805 the system interworking entity deletes the binding relationship information of the target group.
  • the system interworking entity deletes the binding relationship information of the previously saved target group.
  • the binding relationship information of the target group may be deleted according to the content carried in the group connection release request message, or the binding relationship information of the target group with other groups in the target binding relationship may be deleted.
  • step S8061 is performed; when the target group is the second group, step S8062 is performed.
  • Step S8061 The group management server of the first communication system sends a fourth indication message to the group management client of the first communication system.
  • the fourth indication message is used to notify the group management client of the first communication system that the binding relationship of the target group has been released.
  • the fourth indication message may be a group connection release response message, so that the group management client of the first communication system knows that the group connection release request of the target group requested by itself has been responded.
  • Step S8062 The system interworking entity sends a fifth indication message to the second service control entity of the second communication system.
  • the fifth indication message is used to notify the second service control entity that the binding relationship of the target group of the second communication system has been released.
  • the fifth indication message may include the identifier of the target group, and may also include the identifier of the target group and the binding relationship identifier information of the target group, and is determined according to the group connection release request message.
  • steps S807-S808 may also be performed:
  • Step S807 the group management server of the first communication system sends a second group connection release notification message to the first service control entity of the first communication system.
  • the second group connection release notification message may include the identifier of the target group, or the identifier of the target group and the binding relationship identification information of the target group, determined according to the content carried in the group connection release request message.
  • the second group connection release notification message is used to notify that the binding relationship of the first service control entity target group of the first communication system has been released.
  • Step S808 The first service control entity of the first communication system deletes the binding relationship information of the target group.
  • the first service control entity of the first communication system deletes the binding relationship information of the previously added target group. Specifically, according to the content carried in the second group connection release notification message, all the binding relationship information of the target group is deleted, or the binding relationship information of the target group with other groups in the target binding relationship is deleted.
  • Step S809 The group management server of the first communication system sends a group connection cancellation response message to the group management client of the first communication system, indicating that the group binding relationship is unsuccessful.
  • an embodiment of the present application provides another method for connecting a population group.
  • the method includes, but is not limited to, the following steps.
  • Step S901 The service client of the first communication system sends a first group connection request message to the first service control entity of the first communication system.
  • Step S902 The first service control entity of the first communication system checks whether the service client of the first communication system has the right to request the first group to establish a binding relationship with the second group. If there is a right to request the first group to establish a binding relationship with the second group, steps S903-S910 are performed; otherwise, step S911 is performed.
  • step S902 may be used as an optional step, and the embodiment of the present application may also directly perform step S903-S910 without performing step S902.
  • Step S903 the first service control entity of the first communication system sends a second group connection request message to the group management server of the first communication system.
  • Step S904 the group management server of the first communication system establishes a binding relationship between the first group and the second group.
  • Step S905 the group management server of the first communication system sends a third indication message to the system interworking entity.
  • steps S906 and S907 are further performed:
  • Step S906 the system interworking entity saves the binding relationship between the first group and the second group.
  • Step S907 the system interworking entity sends a second indication message to the second service control entity of the second communication system.
  • step S906 there is no necessary sequence of execution between step S906 and step S907, and adjustment may be made according to the situation.
  • Step S908 the group management server of the first communication system sends a first indication message to the first service control entity of the first communication system.
  • the first indication message may be a group connection response message, and is used to notify that the binding relationship of the first group of the first service control entity of the first communication system has been established.
  • the system interworking entity can determine that the binding relationship of the first group has been established by using the message name.
  • the first indication message may include binding relationship information of the first group, and the binding relationship information may be a binding relationship indication.
  • the binding relationship indication is used to indicate that the binding relationship of the first group is established.
  • the binding relationship indication may be one reserved bit position 1 in the first indication message, or may be a new bit position 0, used for Indicates the establishment of the first group binding relationship.
  • the binding relationship information of the first group in the first indication message may also include a binding relationship indication and binding relationship identification information.
  • the binding relationship identifier information may be an identifier of the identifier of the first group and the identifier of the second group, or may be a group identifier of any one of the binding relationships, or may be newly created for indicating The identifier of the binding relationship between the first group and the second group. Therefore, the first indication message may indicate that the binding relationship of the first group has been established, and the binding relationship identification information uniquely indicates that the binding relationship between the first group and the second group is established. system.
  • the first indication message may further carry an identifier of another group that establishes a binding relationship with the first group.
  • the first indication message may further include a group role of the first group, and may also include a group role of the first group and the second group respectively.
  • Step S909 the first service control entity of the first communication system adds the binding relationship information of the first group.
  • the group management server of the first communication system adds corresponding binding relationship information to the first group.
  • the binding relationship information is determined according to the first indication message.
  • the binding relationship information may be a binding relationship indication that is bound to the first group, and may also include binding relationship identification information, indicating that the binding relationship of the first group is established, and the binding relationship identification information is uniquely indicated.
  • the binding relationship information may further include a group role of the first group, and may also include a group role of the first group and the second group respectively.
  • Step S910 The first service control entity of the first communication system sends a group connection response message to the service client of the first communication system, indicating that the group binding relationship is successfully established.
  • the first service control entity of the first communication system may determine that the binding relationship is successfully established, and send a group connection response message to the service client of the first communication system, indicating the group.
  • the group binding relationship was established successfully.
  • Step S911 The first service control entity of the first communications system sends a group connection response message to the service client of the first communications system, indicating that the group binding relationship establishment fails.
  • an embodiment of the present application provides another method for releasing a population group connection.
  • This method corresponds to the group connection method shown in Fig. 6a, and the present embodiment can be implemented after the embodiment shown in Fig. 6a.
  • the method includes, but is not limited to, the following steps.
  • Step S1001 The service client of the first communication system sends a first group connection release request message to the first service control entity of the first communication system.
  • Step S1002 The first service control entity of the first communication system checks whether the service client of the first communication system has the right to request the target group to release the binding relationship. If there is a right to request the target group to release the binding relationship, steps S1003-S1009 are performed; otherwise, step S1010 is performed.
  • step S1002 may be an optional step.
  • the embodiment of the present application may also directly perform the steps S1003-S1009 without performing step S1002.
  • Step S1003 The first service control entity of the first communication system sends a second group connection release request message to the group management server of the first communication system.
  • the second group connection release request message includes group binding relationship identification information, and step S10041 is performed.
  • the second group connection release request message includes the identifier of the target group and the binding relationship identifier information of the target group, and step S10042 is performed.
  • the second group connection release request message includes the identifier of the target group, and Step S10043 is performed.
  • Step S10041 The group management server of the first communication system releases the binding relationship indicated by the group binding relationship identifier.
  • Step S10042 The group management server of the first communication system releases the binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • Step S10043 The group management server of the first communication system releases the binding relationship between the target group and other groups in the binding relationship including all the target group identifiers.
  • Step S1005 The group management server of the first communication system sends a group connection cancellation notification message to the system interworking entity.
  • the group connection release notification message may include the identifier of the target group, or the identifier of the target group and the binding relationship identification information of the target group, and is determined according to the content carried in the group connection release request message.
  • the group connection release notification message is used to notify the system interworking entity that the binding relationship of the target group has been released.
  • step S1006 the system interworking entity deletes the binding relationship information of the target group.
  • step S10071 is performed; when the target group is the second group, step S10072 is performed.
  • Step S10071 The group management server of the first communication system sends a fourth indication message to the first service control entity of the first communication system.
  • the fourth indication message is used to notify that the binding relationship of the target group of the first service control entity of the first communication system has been released.
  • the fourth indication message may be a group connection release response message, so that the first service control entity of the first communication system knows that the second group connection release request of the target group requested by itself has been responded.
  • Step S10072 The system interworking entity sends a fifth indication message to the second service control entity of the second communication system.
  • the five indication message is used to notify the second service control entity that the binding relationship of the target group of the second communication system has been released.
  • the fifth indication message may include the identifier of the target group, and may also include the identifier of the target group and the binding relationship identifier information of the target group, and is determined according to the first group connection release request message.
  • steps S1008-S1009 may also be performed:
  • Step S1008 The first service control entity of the first communication system deletes the binding relationship information of the target group.
  • Step S1009 The first service control entity of the first communication system sends a group connection release response message to the service client of the first communication system, indicating that the group binding relationship is successfully cancelled.
  • Step S1010 The first service control entity of the first communication system sends a group connection release response message to the service client of the first communication system, indicating that the group binding relationship is unsuccessful.
  • an embodiment of the present application provides a group call method.
  • the embodiment shown in FIG. 7a can be implemented after the group connection method shown in FIG. 2a to FIG. 6b, and is applicable to the group having the binding relationship after the binding relationship of the group is established. scene.
  • the method includes, but is not limited to, the following steps.
  • Step S1101 The service client of the first communication system sends a first group call request message to the first service control entity of the first communication system.
  • the first group call request message includes an identifier of the first group, where the first group call request message is used to indicate that the first service control entity of the first communication system calls the first group and has a binding with the first group.
  • Other groups of relationships include
  • Step S1102 When the first group has a binding relationship, the first service control entity of the first communication system sends a second group call request message to the system interworking entity.
  • it may include:
  • Step S11021 The first service control entity of the first communication system checks whether the first group has a binding relationship. Step S11022 is performed when the first group has a binding relationship.
  • the binding relationship information of the first group may be saved in the first service control entity of the first communication system, thereby The information indicates that the first group has a binding relationship. Further, if the binding relationship information of the first group is not saved in the first service control entity of the first communications system, the first service control entity of the first communications system may also be sent to the group management server of the first communications system. Obtain binding relationship information of the first group, so as to check whether the first group has a binding relationship according to the binding relationship information. When the binding relationship information indicates that the first group has a binding relationship, steps S1103-S1105 are performed.
  • the first service control entity of the first communication system plays the role of the master in the communication establishment process. . Sending a call request to the system control entity, requesting the system interworking entity to call the second group to join the communication.
  • Step S11022 The first service control entity of the first communication system sends a second group call request message to the system interworking entity.
  • the second group call request message carries the identifier of the first group, and the second group call request message is used to request to join the second group having the binding relationship with the group into the group communication.
  • Step S1103 The system interworking entity searches for an identifier of the second group that has a binding relationship with the identifier of the first group.
  • the system interworking entity After receiving the second group call request message, the system interworking entity searches for the identifier of the second group that has a binding relationship with the identifier of the first group in the multiple binding relationships acquired in advance. For example, the binding relationship table shown in Table 1 exists in advance. If the identifier of the first group in the second group call request message is 1-12, the first binding relationship with the 1-12 group can be obtained.
  • the identity of the two groups is 2-02.
  • Step S1104 The system interworking entity sends a third group call request message to the second service control entity of the second communication system.
  • the third group call request message carries the identifier of the second group, and the third group call request message is used to instruct the second service control entity to join the second group into the group communication with the first group.
  • the second service control entity can call all members of the second group.
  • the first service control entity of the first communication system also calls all members of the first group, so that the second service control entity can join all members of the second group to the first group. In the group communication of all members.
  • step S1104 it is also possible to perform:
  • Step S1105 The system interworking entity sends a group call response message to the first service control entity of the first communication system.
  • Step S1106 The first service control entity of the first communication system sends the group to the service client of the first communication system. Group call response message.
  • the group call response message is used to notify the first service control entity of the first communication system and the service client of the first communication system that the second group has been successfully called, and the group communication has been established. If the group binding relationship includes the role information of the first group, the first service control entity of the first communication system corresponding to the first group performs the group control function of the group communication, and further, the first communication The first service control entity of the system can control the media control of the group communication.
  • an embodiment of the present application provides another method for calling a population group.
  • the embodiment shown in FIG. 7b can be implemented after the group connection method shown in FIG. 2a to FIG. 6b, and is applicable to the group having the binding relationship after the binding relationship of the group is established. scene.
  • the method includes, but is not limited to, the following steps.
  • Step S1201 The service client of the first communication system sends a first group call request message to the first service control entity of the first communication system.
  • the first group call request message includes an identifier of the first group, where the first group call request message is used to indicate that the first service control entity of the first communication system calls the first group and has a binding with the first group.
  • Other groups of relationships include
  • Step S1202 When the first group has a binding relationship, the first service control entity of the first communication system searches for the identifier of the second group that has a binding relationship with the identifier of the first group.
  • the first service control entity of the first communication system determines that the first group has a binding relationship, it searches for an identifier of the second group that has a binding relationship with the identifier of the first group. Specifically, it may include:
  • Step S12021 The first service control entity of the first communication system checks whether the first group has a binding relationship. Step S12022 is performed when the first group has a binding relationship.
  • the binding relationship information of the first group may be saved in the first service control entity of the first communication system, thereby The information indicates that the first group has a binding relationship. Further, if the binding relationship information of the first group is not saved in the first service control entity of the first communications system, the first service control entity of the first communications system may also be sent to the group management server of the first communications system. Obtain binding relationship information of the first group, so as to check whether the first group has a binding relationship according to the binding relationship information.
  • the first service control entity of the first communication system plays the role of the master in the communication establishment process. . Sending a call request to the system control entity, requesting the system interworking entity to call the second group to join the communication.
  • Step S12022 The first service control entity of the first communication system searches for an identifier of the second group that has a binding relationship with the identifier of the first group.
  • the first service control entity of the first communication system After receiving the second group call request message, the first service control entity of the first communication system searches for a second group that has a binding relationship with the identifier of the first group in the multiple binding relationships acquired in advance.
  • the identity of the group For example, the binding relationship table shown in Table 1 exists in advance. If the identifier of the first group in the second group call request message is 1-12, the first binding relationship with the 1-12 group can be obtained.
  • the identity of the two groups is 2-02.
  • Step S1203 The first service control entity of the first communication system sends a second group call request message to the system interworking entity.
  • the second group call request message carries the identifier of the second group, and the second group call request message is used to request the group and the group
  • the second group having a binding relationship between the groups joins the group communication.
  • Step S1204 The system interworking entity sends a third group call request message to the second service control entity of the second communication system.
  • the third group call request message carries the identifier of the second group, and the third group call request message is used to instruct the second service control entity to join the second group into the group communication with the first group.
  • the second service control entity can call all members of the second group.
  • the first service control entity of the first communication system also calls all members of the first group, so that the second service control entity can join all members of the second group to the first group. In the group communication of all members.
  • step S1204 it is also possible to perform:
  • Step S1205 The system interworking entity sends a group call response message to the first service control entity of the first communication system.
  • Step S1206 The first service control entity of the first communication system sends a group call response message to the service client of the first communication system.
  • the group call response message is used to notify the first service control entity of the first communication system and the service client of the first communication system that the second group has been successfully called, and the group communication has been established. If the group binding relationship includes the role information of the first group, the first service control entity of the first communication system corresponding to the first group performs the group control function of the group communication, and further, the first communication The first service control entity of the system can control the media control of the group communication.
  • FIG. 8a is a schematic structural diagram of a group connection apparatus according to an embodiment of the present application.
  • the group connection device can be used for the group management server or system interworking entity of the first communication system to implement the above-described embodiments of Figures 2a-6b.
  • the group connection device includes:
  • the receiving module 11 is configured to receive a group connection request message from a first device of the first communication system, where the group connection request message includes an identifier of the first group of the first communication system and a second communication system The identifier of the second group, the first communication system and the second communication system are based on different access technologies;
  • the processing module 12 is configured to establish a binding relationship between the first group and the second group.
  • the sending module 13 is configured to send a first indication message to the first device, where the first indication message is used to notify that the binding relationship of the first group has been established.
  • the sending module 13 is further configured to:
  • the sending module 133 is further configured to:
  • the receiving module 11 is further configured to:
  • the authorization success response message is used to indicate that the second communication system allows the second group to establish a binding relationship.
  • processing module 12 is specifically configured to:
  • the binding relationship between the first group and the second group is established.
  • the sending module 13 is further configured to:
  • the group connection request message further includes a group role of the first group and a group role of the second group;
  • the binding relationship includes a group role of the first group and a group role of the second group;
  • the third indication message further includes a group role corresponding to the first group and the second group respectively.
  • the first indication message includes binding relationship information of the first group
  • the binding relationship information includes a binding relationship indication, or the binding relationship information includes a binding relationship indication and an identifier of the second group.
  • the group connection request message further includes group role information of the first group and a group role of the second group;
  • the binding relationship includes a group role of the first group and a group role of the second group;
  • the first indication message further includes a group role of the first group.
  • the receiving module 11 is further configured to: receive a group connection release request message, where the group connection release request message includes an identifier of the target group, where the target group is the first group or The second group;
  • the processing module 12 is further configured to: release the binding relationship of the target group.
  • the receiving module 11 is further configured to: receive a group connection release request message, where the group connection release request message includes an identifier of the target group and a binding relationship identifier information of the target group, where The target group is the first group or the second group;
  • the processing module 12 is further configured to: remove the binding relationship between the target group and other groups in the target binding relationship indicated by the binding relationship identifier information.
  • the sending module 13 is further configured to:
  • the target group is the second group
  • the first device includes a group management client GMC of the first communication system or a service client of the first communication system or a group management server GMS of the first communication system or the The first service control entity of the first communication system.
  • the receiving module 11 is further configured to:
  • the sending module 13 is further configured to:
  • the second service control to the second communication system
  • the entity group sends a second group call request message, where the second group call request message carries the identifier of the second group, and the second group call request message is used to indicate that the second service control entity
  • the second group joins the group communication with the first group.
  • FIG. 8b is a schematic structural diagram of another group connection device according to an embodiment of the present application.
  • the group connection device includes a processor 21, a memory 22, and a communication interface 23.
  • the processor 21 is connected to the memory 22 and the communication interface 23, for example, the processor 21 can be connected to the memory 22 and the communication interface 23 via a bus.
  • the group connection device may be a group management server of the first communication system, or may be a system interworking entity.
  • the processor 21 is configured to support the group connection device to perform the corresponding functions in the methods described in Figures 2a-6b.
  • the processor 21 can be a central processing unit (CPU), a network processor (in English: network processor, NP), a hardware chip, or any combination thereof.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and a general array logic (GAL). Or any combination thereof.
  • the memory 22 is used to store program codes and the like.
  • the memory 22 may include a volatile memory (English: volatile memory), such as random access memory (English: random access memory, abbreviation: RAM); the memory 22 may also include non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive , abbreviation: SSD); the memory 72 may also include a combination of the above types of memory.
  • ROM read-only memory
  • flash memory English: flash memory
  • HDD hard disk drive
  • SSD solid state drive
  • the communication interface 23 is configured to communicate with each network device, terminal or entity in the embodiment of the present application to send and receive messages or media streams involved in the foregoing method.
  • the processor 21 can invoke the program code to perform the following operations:
  • the group connection request message including an identifier of the first group of the first communication system and a second group of the second communication system Identifying that the first communication system and the second communication system are based on different access technologies;
  • the processor 21 is further configured to:
  • the method is further configured to:
  • the processor 21 When the processor 21 establishes the binding relationship between the first group and the second group, the processor 21 is specifically configured to:
  • the authorization success response message is used to indicate that the second communication system allows the second group to establish a binding relationship.
  • the method is specifically configured to:
  • the binding relationship between the first group and the second group is established.
  • the processor 21 is further configured to:
  • the group connection request message further includes a group role of the first group and a group role of the second group;
  • the binding relationship includes a group role of the first group and a group role of the second group;
  • the third indication message further includes a group role corresponding to the first group and the second group respectively.
  • the first indication message includes binding relationship information of the first group
  • the binding relationship information includes a binding relationship indication, or the binding relationship information includes a binding relationship indication and an identifier of the second group.
  • the group connection request message further includes a group role of the first group and a group role of the second group;
  • the binding relationship includes a group role of the first group and a group role of the second group;
  • the first indication message further includes a group role of the first group.
  • the processor 21 is further configured to:
  • the group connection release request message includes an identifier of a target group, where the target group is the first group or the second group;
  • the processor 21 is further configured to:
  • the group connection release request message includes an identifier of a target group and binding relationship identification information of the target group, where the target group is the first group or Said second group;
  • the processor 21 is further configured to:
  • the target group is the second group
  • the first device includes a group management client GMC of the first communication system or a service client of the first communication system or a group management server GMS of the first communication system or the The first service control entity of the first communication system.
  • the processor 21 is further configured to:
  • the second group call request The message carries the identifier of the second group, where the second group call request message is used to indicate that the second service control entity joins the second group to the group communication with the first group.
  • FIG. 9a is a schematic structural diagram of another group calling device according to an embodiment of the present application.
  • the group connection device can be used for the group management server of the first communication system or the first service control entity of the first communication system to implement the above-described embodiments of Figures 2a-6b.
  • the group connection device includes:
  • the receiving module 31 is configured to receive a first group call request message, where the first group call request message includes an identifier of the first group;
  • the sending module 32 is configured to: when the group has a binding relationship, send a second group call request message to the system interworking entity, where the second group call request message carries the identifier of the first group, where The second group call request message is used to request that the second group having a binding relationship with the first group be added to the group communication.
  • FIG. 9b is a schematic structural diagram of another group calling device according to an embodiment of the present application.
  • the group connection device includes a processor 41, a memory 42, and a communication interface 43.
  • the processor 41 is connected to the memory 42 and the communication interface 43, for example, the processor 41 can be connected to the memory 42 and the communication interface 43 via a bus.
  • the group connection device may be a first service control entity of the first communication system, or may be a group management server of the first communication system.
  • the processor 41 is configured to support the group connection device to perform the corresponding functions in the methods described in Figures 7a-7b.
  • the processor 41 can be a central processing unit (CPU), a network processor (in English: network processor, NP), a hardware chip, or any combination thereof.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and a general array logic (GAL). Or any combination thereof.
  • the memory 42 is used to store program codes and the like.
  • the memory 42 may include a volatile memory (English: volatile memory), such as a random access memory (English: random access memory, abbreviation: RAM); the memory 42 may also include a non-volatile memory (English: non-volatile memory)
  • ROM read-only memory
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviation: HDD
  • solid state drive English: solid-state drive , abbreviation: SSD
  • the memory 72 may also include a combination of the above types of memory.
  • the communication interface 43 is configured to communicate with each network device, terminal or entity in the embodiment of the present application to transmit and receive messages or media streams involved in the foregoing method.
  • the processor 41 can invoke the program code to perform the following operations:
  • the second group call request message When the first group has a binding relationship, sending a second group call request message to the system interworking entity, where the second group call request message carries the identifier of the first group, the second group The group call request message is used to request that the second group having a binding relationship with the first group join the group communication.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种群组连接方法及相关设备。方法包括：群组连接装置接收来自第一通信系统的第一设备的群组连接请求消息，群组连接请求消息中包括所述第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，第一通信系统与第二通信系统基于不同的接入技术，建立第一群组与所述第二群组的绑定关系，向第一设备发送第一指示消息，第一指示消息用于通知第一群组的绑定关系已建立。在该技术方案中，群组连接装置可以将不同接入技术的系统中的群组进行绑定。

Description

群组连接方法及相关设备 技术领域
本申请涉及电子技术领域，尤其涉及一种群组连接方法及相关设备。
背景技术
紧急任务服务是用于公共安全应用及商业应用的一种集群通信服务，如公安系统中。紧急任务服务支持1-to-N的群组通信，当用户发起群组通信时，在群组呼叫消息中携带群组标识发送给紧急任务服务服务器，由紧急任务服务服务器负责呼叫其他群组成员，协商媒体信息。群组通信建立完成后，加入该群组通信的用户可以相互通信。
为了满足通信需求，两个或两个以上群组之间可以关联起来，当用户向任一群组发起群组呼叫时，紧急任务服务服务器可以呼叫该群组成员以及与该群组关联的群组中的成员，让两个或两个以上群组的成员之间建立群组通信。
目前将两个或两个以上群组进行关联的方式有两种。第一种方式为适用于LTE系统或者未来5G系统的宽带接入技术的群组重组方式，即为两个或两个以上群组临时建立一个新的群组；第二种方式为适用于传统通信系统的窄带接入技术的群组连接方式，即为两个或两个以上群组建立关联关系。但是，这两种群组的关联方式均只能单独应用在某一种特定接入技术的系统中，因此如何将不同接入技术的系统中的群组进行关联成为亟待解决的问题。
发明内容
本申请提供一种群组连接方法及相关设备，可以将不同接入技术的系统中的群组进行绑定。
第一方面，本申请实施例提供了一种群组连接方法。群组连接装置接收来自第一通信系统的第一设备的群组连接请求消息，群组连接请求消息中包括所述第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，第一通信系统与第二通信系统基于不同的接入技术，建立第一群组与所述第二群组的绑定关系，向第一设备发送第一指示消息，第一指示消息用于通知第一群组的绑定关系已建立。
在该技术方案中，群组连接装置可以将不同接入技术的系统中的群组进行绑定。
在第一方面的第一种可能的实现方式中，群组连接装置向第二通信系统的第二业务控制实体发送第二指示消息，所述第二指示消息用于通知所述第二群组的绑定关系已建立。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，群组连接装置向第二通信系统的授权检查实体发送授权指示消息，所述授权指示消息携带所述第二群组的标识，接收来自授权检查实体的授权成功响应消息，所述授权成功响应消息用于指示所述第二通信系统允许所述第二群组建立绑定关系。
在该技术方案中，群组连接装置可以通知第二通信系统的授权检查实体进行授权检查，增加安全性。
在第一方面的第三种可能的实现方式中，当第一设备具备请求第一群组与第二群组建 立绑定关系的权限时，群组连接装置建立第一群组与第二群组的绑定关系。
在该技术方案中，群组连接装置可以对第一设备进行授权检查，增加安全性。
结合第一方面或者第一方面的第三种可能的实施方式，在第一方面的第四种可能的实现方式中，群组连接装置向系统互通实体发送第三指示消息，所述第三指示消息包括所述第一群组的标识和所述第二群组的标识，所述第三指示消息用于通知所述第一群组与所述第二群组的绑定关系已建立。
结合第一方面的第四种可能的实施方式，在第一方面的第五种可能的实现方式中，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；所述第三指示消息还包括所述第一群组和所述第二群组分别对应的群组角色。
在该技术方案中，群组连接请求消息包括第一群组的群组角色和第二群组的群组角色，从而绑定关系以及第三指示消息也可以包括第一群组的群组角色和第二群组的群组角色，用于后续群组呼叫时根据群组角色进行呼叫控制。
结合第一方面以及第一方面第一种至第五种中任一可能的实施方式，在第一方面的第六种可能的实现方式中，所述第一指示消息包括所述第一群组的绑定关系信息；其中，所述绑定关系信息包括绑定关系指示，或，所述绑定关系信息包括绑定关系指示和所述第二群组的标识。
在该技术方案中，第一指示消息还可以包括第一群组的绑定关系信息，从而指示第一群组具有绑定关系，或者进一步指示与第一群组具有绑定关系的第二群组。
结合第一方面以及第一方面第一种至第六种中任一可能的实施方式，在第一方面的第七种可能的实现方式中，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；所述第一指示消息还包括所述第一群组的群组角色。
在该技术方案中，群组连接请求消息包括第一群组的群组角色和第二群组的群组角色，从而绑定关系以及第一指示消息也可以包括第一群组的群组角色和第二群组的群组角色，用于后续群组呼叫时根据群组角色进行呼叫控制。
结合第一方面以及第一方面第一种至第七种中任一可能的实施方式，在第一方面的第八种可能的实现方式中，群组连接装置接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识，所述目标群组为所述第一群组或所述第二群组，解除所述目标群组的绑定关系。
在该技术方案中，群组连接装置可以解除不同接入技术的系统中群组的绑定关系。
结合第一方面以及第一方面第一种至第七种中任一可能的实施方式，在第一方面的第九种可能的实现方式中，群组连接装置接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识和所述目标群组的绑定关系标识信息，所述目标群组为所述第一群组或所述第二群组，解除所述绑定关系标识信息所指示的目标绑定关系中所述目标群组与其他群组之间的绑定关系。
在该技术方案中，群组连接装置可以解除不同接入技术的系统中群组的绑定关系。
结合第一方面的第八种或者第九种可能的实现方式，在第一方面的第十种可能的实现 方式中，当所述目标群组为所述第一群组时，群组连接装置向所述第一通信系统的第一设备发送第四指示消息，所述第四指示消息用于通知所述目标群组的绑定关系已解除；或者，当所述目标群组为所述第二群组时，群组连接装置向所述第二通信系统的第二业务控制实体发送第五指示消息，所述第五指示消息用于通知所述目标群组的绑定关系已解除。
结合第一方面以及第一方面第一种至第十种中任一可能的实施方式，在第一方面的第十一种可能的实现方式中，所述第一设备包括所述第一通信系统的群组管理客户端GMC或所述第一通信系统的业务客户端或所述第一通信系统的群组管理服务器GMS或所述第一通信系统的所述第一业务控制实体。
结合第一方面以及第一方面第一种至第十一种中任一可能的实施方式，在第一方面的第十二种可能的实现方式中，群组连接装置接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识，当所述第一群组与所述第二群组具有绑定关系时，向所述第二通信系统的第二业务控制实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第二群组的标识，所述第二群组呼叫请求消息用于指示所述第二业务控制实体将所述第二群组加入与所述第一群组的群组通信中。
在该技术方案中，群组连接装置可以实现不同接入技术的系统的群组呼叫。
结合第一方面以及第一方面第一种至第十一种中任一可能的实施方式，在第一方面的第十三种可能的实现方式中，群组连接装置接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第二群组的标识，向所述第二通信系统的第二业务控制实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第二群组的标识，所述第二群组呼叫请求消息用于指示所述第二业务控制实体将所述第二群组加入与所述第一群组的群组通信中。
在该技术方案中，群组连接装置可以实现不同接入技术的系统的群组呼叫。
本申请第二方面提供了一种群组呼叫方法。群组呼叫装置接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识，当所述第一群组具有绑定关系时，向系统互通实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第一群组的标识，所述第二群组呼叫请求消息用于请求将与所述第一群组之间具有绑定关系的第二群组加入群组通信。
在第二方面的第一种可能的实现方式中，所述第二群组呼叫请求消息携带所述第一群组的标识。
在第二方面的第二种可能的实现方式中，群组呼叫装置向系统互通实体发送第二群组呼叫请求消息之前，还查找与所述第一群组的标识具有绑定关系的第二群组的标识，则所述第二群组呼叫请求消息携带所述第二群组的标识。
在该技术方案中，群组呼叫装置可以实现不同接入技术的系统的群组呼叫。
本申请第三方面提供了一种群组连接装置。包括处理器、存储器以及通信接口。处理器连接到存储器和通信接口，例如处理器可以通过总线连接到存储器和通信接口。通信接口用于与客户端等设备进行通信。存储器用于存储群组连接请求消息等。处理器用于执行第一方面的部分或全部流程。
本申请第四方面提供了另一种群组连接装置，包括发送模块、接收模块和处理模块， 处理模块用于实现第三方面中的处理器，发送模块结合接收模块用于实现第三方面中的网络接口。群组连接装置通过上述模块实现第一方面的部分或全部方法。
本申请第五方面提供了一种群组呼叫装置。包括处理器、存储器以及通信接口。处理器连接到存储器和通信接口，例如处理器可以通过总线连接到存储器和通信接口。通信接口用于与客户端等设备进行通信。存储器用于存储群组连接请求消息等。处理器用于执行第二方面的部分或全部流程。
本申请第六方面提供了另一种群组呼叫装置，包括发送模块、接收模块和处理模块，处理模块用于实现第五方面中的处理器，发送模块结合接收模块用于实现第五方面中的网络接口。群组连接装置通过上述模块实现第二方面的部分或全部方法。
附图说明
图1是本申请实施例提供的一种互通架构示意图；
图2a是本申请实施例提供的一种群组连接方法的流程示意图；
图2b是本申请实施例提供的另一种群组连接解除方法的流程示意图；
图2c是本申请实施例提供的另一种群组连接解除方法的流程示意图；
图3a是本申请实施例提供的另一种群组连接方法的流程示意图；
图3b是本申请实施例提供的另一种群组连接解除方法的流程示意图；
图4a是本申请实施例提供的另一种群组连接方法的流程示意图；
图4b是本申请实施例提供的另一种群组连接解除方法的流程示意图；
图5a是本申请实施例提供的另一种群组连接方法的流程示意图；
图5b是本申请实施例提供的另一种群组连接解除方法的流程示意图；
图6a是本申请实施例提供的另一种群组连接方法的流程示意图；
图6b是本申请实施例提供的另一种群组连接解除方法的流程示意图；
图7a是本申请实施例提供的一种群组呼叫方法的流程示意图；
图7b是本申请实施例提供的另一种群组呼叫方法的流程示意图；
图8a是本申请实施例提供的一种群组连接装置的结构示意图；
图8b是本申请实施例提供的另一种群组连接装置的结构示意图；
图9a是本申请实施例提供的一种群组呼叫装置的结构示意图；
图9b是本申请实施例提供的另一种群组呼叫装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案适用于基于不同接入技术的通信系统之间进行相互群组通信的场景。例如，图1所示的一种系统互通架构示意图，包括第一通信系统101、第二通信系统102以及系统互通实体103，其中第一通信系统101与第二通信系统102之间采用不同的接入技术，系统互通实体103则用于实现对不同的接入技术的功能适配和通信协议的转换，从而实现第一通信系统101和第二通信系统102之间的相互群组通信。具体来说，第一通信系统101可以为适用于LTE系统或者未来5G系统的接入技术的群组通信系统， 例如，紧急任务服务系统(mission critical service system)；第二通信系统102可以为适用于LTE系统应用之前的传统系统的接入技术的群组通信系统，例如，LMR(land mobile radio，陆地移动无线通信系统)，P25(Project 25，工程25)或TETRA(terrestrial trunked radio，陆上集群无线电)等。
本申请实施例主要以第一通信系统为紧急任务服务系统为例进行详细介绍，其他群组通信系统与紧急任务服务系统的原理相似，不具体赘述。
下面主要对紧急任务服务系统的相关网元进行介绍。
紧急任务服务服务器(mission critical service server)：主要负责呼叫控制和媒体控制的逻辑实体。在具体实现中，紧急任务服务服务器可以是紧急任务一键通服务器(mission-critical push to talk server，MCPTT server)，紧急任务视频服务器(mission critical video server，MCVideo server)或紧急任务数据服务器(mission critical data server，MCData server)等。本申请实施例中提到的第一业务控制实体就可以为紧急任务服务服务器。
紧急任务服务客户端(mission critical service client)：与紧急任务服务服务器对等的应用层实体，主要负责应用层事务的处理。本申请实施例中提到的业务客户端就可以为紧急任务服务客户端。
群组管理服务器(group management server，GMS)：主要负责紧急任务服务系统中群组的管理与群组信息的维护，例如，群组创建、群组解散、群组成员变更等。
群组管理客户端(group management client，GMC)：与群组管理服务器对等的应用层实体，主要负责发起群组的管理和维护操作，例如，发起群组创建、群组解散、群组成员变更等操作。
系统互通实体(interworking function，IWF)：一个应用层的功能实体，用于连接紧急任务服务系统与第二通信系统，主要负责协议的翻译、标识的翻译和映射等。互通功能实体是一个逻辑功能实体，在实际的实现和部署中，可以作为一个单独的网络设备实现如互通网关，也可以是置于紧急任务服务服务器内部的一个功能实体，或者实现在第二通信系统中的网络实体中，这里不作具体限定。
需要说明的是，群组管理客户端与紧急任务服务客户端可以是运行在同一终端设备中的两个不同逻辑实体。一个用户可以同时在多个终端设备上登陆并使用紧急任务服务客户端或群组管理客户端，此时一个用户对应的一个客户端账号可以对应多个终端设备。多个用户也可以同时登陆并使用同一个终端设备，此时多个用户分别对应的多个客户端账号可以对应一个终端设备。
本申请实施例中描述的执行方法就是在如图1所示的系统环境中，对群组连接的一种建立方法，从而可以使不同接入技术的第一通信系统与第二通信系统中的群组进行关联。
参见图2a，本申请实施例提供了一种群组连接方法。该方法包括但不限于以下步骤。
步骤S001，第一通信系统的第一设备向群组连接装置发送群组连接请求消息。
在本申请实施例中，第一设备包括第一通信系统的群组管理客户端GMC或第一通信系统的业务客户端或第一通信系统的群组管理服务器GMS或第一通信系统的第一业务控制实体。群组连接装置可以是第一通信系统的群组管理服务器，也可以是系统互通实体。
具体来说，可以是第一通信系统的群组管理客户端GMC向第一通信系统的群组管理服务器GMS发送群组连接请求消息，也可以是第一通信系统的第一业务控制实体向第一通信系统的群组管理服务器GMS发送群组连接请求消息，还可以是第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送群组连接请求消息后，第一通信系统的第一业务控制实体又发送给第一通信系统的群组管理服务器GMS的。进一步的，可以是第一通信系统的群组管理服务器GMS向系统互通实体发送群组连接请求消息，也可以是第一通信系统的第一业务控制实体向系统互通实体发送群组连接请求消息。具体情况由以下图2b-6b所示的实施例详细说明。
群组连接请求消息中包括第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，其中，第一通信系统与第二通信系统基于不同的接入技术。群组连接请求消息用于请求建立第一群组与第二群组之间的绑定关系。其中，第一群组是指第一通信系统中的群组，第二群组是指第二通信系统中的群组。第一群组与第二群组的绑定关系是指，将第一群组与第二群组之间关联起来，形成一个逻辑意义上的整体，在具有绑定关系时，第一群组或第二群组中的任意一个群组被呼叫时，另一个群组也会被呼叫。需要说明的是，本申请实施例仅以第一群组与第二群组两个群组为例描述绑定关系建立的过程，在实际应用过程中，建立绑定关系的群组数量可以是两个以上，原理与本申请实施例中的方法完全一致，这里不具体赘述。
具体实施中，第一通信系统的第一设备可以通过与其他设备的交互来获取第二群组的标识，也可以通过预先配置的方式将第二群组的标识预存在第一通信系统的群组管理客户端中，这里不作具体限定。
进一步可选的，群组连接请求消息中还可以包括第一群组的群组角色和第二群组的群组角色。其中，群组角色指的是群组呼叫时担任的角色，具体可以是主控群组角色，也可以是非主控/从属群组角色。具体来说，一个群组通信中只能有一个主控群组角色，那么也可以仅指定主控群组角色，其他群组角色缺省即可默认为非主控/从属群组角色。例如，群组连接请求消息可以包括第一群组为主控群组角色，第二群组为非主控/从属群组角色；群组连接请求消息也可以包括第一群组为主控群组角色，而第二群组的群组角色缺省，那么可以默认为第二群组为非主控/从属群组角色。
步骤S002，群组连接装置建立第一群组与第二群组的绑定关系。
群组连接装置在接收到群组连接请求消息后，建立第一群组与第二群组的绑定关系，例如，可以通过表格的形式建立第一群组与第二群组之间的绑定关系，即在绑定关系表中增加第一群组的标识以及第二群组的标识，表明两者具有绑定关系。例如，若第一群组的标识为1-12，第二群组的标识为2-02，那么如表1所示的绑定关系表中，可以增加编号1对应的绑定关系群组1-12和2-02。从而，群组连接装置就可以建立第一群组与第二群组的绑定关系。
Figure PCTCN2017082789-appb-000001
表1：绑定关系表
进一步的，在一种可能的实施场景中，为第一群组与第二群组建立的绑定关系中还可以包括绑定关系标识信息。绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，例如(1-12 2-02)；也可以是绑定关系中任意一个群组的群组标识，例如2-02；还可以是新建的用于表示第一群组与第二群组的绑定关系的标识，例如表1中的编号。
进一步的，第二群组连接请求消息中包括第一群组的群组角色和第二群组的群组角色时，绑定关系也可以包括第一群组的群组角色和所述第二群组的群组角色，例如表2所示的绑定关系表。
Figure PCTCN2017082789-appb-000002
表2：绑定关系表
可选的，群组连接装置为系统互通实体时，在步骤S002之前，还可以向第二通信系统的授权检查实体发送授权指示消息，用于指示第二通信系统进行授权检查。当第二通信系统的授权检查实体允许第二群组建立绑定关系时，第二通信系统的授权检查实体向群组连接装置发送授权成功响应消息。从而群组连接装置执行步骤S002。
可选的，步骤S002具体可以为当第一设备具备请求所述第一群组与所述第二群组建立绑定关系的权限时，建立所述第一群组与所述第二群组的绑定关系。即在确定第一设备具备请求所述第一群组与所述第二群组建立绑定关系的权限的状态时，建立所述第一群组与所述第二群组的绑定关系。
可选的，群组连接装置为第一通信系统的群组管理服务器时在步骤S002之前，还可以检查第一设备的用户是否具备请求第一群组与第二群组建立绑定关系的权限，如果具备请求第一群组与第二群组建立绑定关系的权限执行步骤S002。具体的授权检查方法根据由以下图2b-6b所示的实施例详细说明。
步骤S003，群组连接装置向第一通信系统的第一设备发送第一指示消息。
第一指示消息用于通知第一群组的绑定关系已建立。
在一种可能的实施场景中，第一指示消息可以为群组连接响应消息，通过消息名称即可向第一设备说明第一群组的绑定关系已建立。
在另一种可能的实施场景中，第一指示消息可以包括第一群组的绑定关系信息，绑定关系信息可以为绑定关系指示。绑定关系指示用于指示第一群组的绑定关系已建立，例如 绑定关系指示可以是第一指示消息中的一个保留比特位置1，也可以是新增的一个比特位置0，用于指示第一群组绑定关系的建立。
在又一种可能的实施场景中，第一指示消息中的第一群组的绑定关系信息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中任意一个群组的群组标识，例如第二群组的标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。从而第一指示消息可以指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。
进一步的，群组连接请求消息中如果携带了第一群组的群组角色和第二群组的群组角色，则第一指示消息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别对应的群组角色。
进一步可选的，步骤S002之后，群组连接装置还可以向第二通信系统的第二业务控制实体发送第二指示消息，第二指示消息用于通知第二群组的绑定关系已建立。可选的，第二指示消息可以包括绑定关系指示，绑定关系指示用于指示第二群组的绑定关系已建立。第二指示消息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中任意一个群组的标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。第二指示消息用于指示第二群组的绑定关系已建立，并且绑定关系标识信息唯一指示第二群组与第一群组建立的绑定关系。进一步的，第二指示消息还可以包括第二群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
进一步的，群组连接装置为第一通信系统的群组管理服务器时，还可以向系统互通实体发送第三指示消息，所述第三指示消息包括所述第一群组的标识和所述第二群组的标识，所述第三指示消息用于通知所述第一群组与所述第二群组的绑定关系已建立。进一步的，若群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；则绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；则第三指示消息还包括所述第一群组和所述第二群组分别对应的群组角色。
进一步可选的，绑定关系建立完成之后，在一种可能的实施场景中，群组连接装置可以接收群组连接解除请求消息，群组连接解除请求消息中包括目标群组的标识，目标群组为第一群组或所述第二群组，则群组连接装置解除目标群组的绑定关系。在另一种可能的实施场景中，群组连接装置还可以接收群组连接解除请求消息，群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，目标群组为第一群组或第二群组。则群组连接装置解除绑定关系标识信息所指示的目标绑定关系中所述目标群组与其他群组之间的绑定关系。
进一步的，当目标群组为第一群组时，解除绑定关系之后，群组连接装置可以向第一通信系统的第一设备发送第四指示消息，第四指示消息用于通知目标群组的绑定关系已解除；当目标群组为所述第二群组时，解除绑定关系之后，群组连接装置可以向第二通信系统的第二业务控制实体发送第五指示消息，第五指示消息用于通知目标群组的绑定关系已解除。
进一步的，步骤S003之后，群组连接装置还可以接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识，当所述第一群组与所述第二群组具有绑定关系时，向所述第二通信系统的第二业务控制实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第二群组的标识，所述第二群组呼叫请求消息用于指示所述第二业务控制实体将所述第二群组加入与所述第一群组的群组通信中。该实施场景具体可以结合图7a和图7b所示的实施例实现。
以下通过图2b-图6b所示的实施例对群组连接以及群组连接解除方法进行详细描述。其中，图2b-图4b所示的实施例中，群组的绑定关系由系统互通实体创建和维护；图5a-图6b所示的实施例中，群组的绑定关系由系统群组管理服务器创建和维护。
参见图2b，本申请实施例提供了另一种群组连接方法。该方法包括但不限于以下步骤。
步骤S101，第一通信系统的群组管理客户端向第一通信系统的群组管理服务器发送第一群组连接请求消息。
第一群组连接请求消息中包括第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，第一群组连接请求消息用于请求建立第一群组与第二群组之间的绑定关系。其中，第一群组是指第一通信系统中的群组，第二群组是指第二通信系统中的群组。第一群组与第二群组的绑定关系是指，将第一群组与第二群组之间关联起来，形成一个逻辑意义上的整体，在具有绑定关系时，第一群组或第二群组中的任意一个群组被呼叫时，另一个群组也会被呼叫。需要说明的是，本申请实施例仅以第一群组与第二群组两个群组为例描述绑定关系建立的过程，在实际应用过程中，建立绑定关系的群组数量可以是两个以上，原理与本申请实施例中的方法完全一致，这里不具体赘述。
具体实施中，第一通信系统的群组管理客户端可以通过与其他设备的交互来获取第二群组的标识，也可以通过预先配置的方式将第二群组的标识预存在第一通信系统的群组管理客户端中，这里不作具体限定。
进一步可选的，第一群组连接请求消息中还可以包括第一群组的群组角色和第二群组的群组角色。其中，群组角色指的是群组呼叫时担任的角色，具体可以是主控群组角色，也可以是非主控/从属群组角色。具体来说，一个群组通信中只能有一个主控群组角色，那么也可以仅指定主控群组角色，其他群组角色缺省即可默认为非主控/从属群组角色。例如，第一群组连接请求消息可以包括第一群组为主控群组角色，第二群组为非主控/从属群组角色；第一群组连接请求消息也可以包括第一群组为主控群组角色，而第二群组的群组角色缺省，那么可以默认为第二群组为非主控/从属群组角色。
步骤S102，第一通信系统的群组管理服务器检查第一通信系统的群组管理客户端的用户是否具备请求第一群组与第二群组建立绑定关系的权限。若具备请求第一群组与第二群组建立绑定关系的权限，则执行步骤S103-S112；否则，执行步骤S113。
第一通信系统的群组管理服务器在接收到第一群组连接请求消息后，需要对第一通信系统的群组管理客户端的用户进行授权检查，也即检查第一通信系统的群组管理客户端是否具备请求第一群组与第二群组建立绑定关系的权限。
在一种可能的实施场景中，第一通信系统的群组管理服务器中预存有第一通信系统的多个群组的授权信息，授权信息中可以包括各群组分别对应的授权用户以及授权用户具备的权限，也就是说，通过授权信息可以得到某一群组的授权用户具备对该群组进行何种操作的权限。需要说明的是，这里的授权信息可以是分别存在各个群组的群组信息，也可以是作为独立的表格或者数组整体进行存储的映射关系，这里不在具体限定。
在另一种可能的实施场景中，第一通信系统的群组管理服务器中未存储第一通信系统的与群组管理客户端有关的授权信息，可以从第一通信系统的第一业务控制实体中获取第一通信系统的群组管理客户端的用户签约配置信息，如该用户可以对哪些群组执行何种操作，从签约配置信息中获取第一通信系统的群组管理客户端的用户的授权信息，进而进行授权检查。这里，第一业务控制实体可以是紧急任务服务服务器，包括紧急任务一键通服务器、紧急任务视频服务器或紧急任务数据服务器等。
因此，第一通信系统的群组管理服务器可以检查第一通信系统的群组管理客户端的用户是否具备请求第一群组与第二群组建立绑定关系的权限。若第一通信系统的群组管理客户端的用户具备请求第一群组与第二群组建立绑定关系的权限，则说明授权检查成功，否则说明授权检查失败。
需要说明的是，由于第一通信系统的群组管理服务器为第一通信系统的网络设备，通常来说检查的对象是针对第一群组的。也就是说，实际是检查第一通信系统的群组管理客户端的用户是否具备请求第一群组与其他群组建立绑定关系的权限。
需要说明的是，步骤S102可以作为可选的步骤，本申请实施例也可以不执行步骤S102，直接执行步骤S103-S112。
步骤S103，第一通信系统的群组管理服务器向系统互通实体发送第二群组连接请求消息。
在授权检查成功后，第一通信系统的群组管理服务器向系统互通实体发送第二群组连接请求消息，这里的第二群组连接请求消息即为群组连接请求消息，包括从第一群组连接请求消息中接收到的第一群组的标识和第二群组的标识。
进一步的，当第一群组连接请求消息中包括第一群组的群组角色和第二群组的群组角色时，第二群组连接请求消息也包括第一群组的群组角色和第二群组的群组角色。
步骤S106，系统互通实体建立第一群组与第二群组的绑定关系。
系统互通实体建立第一群组与第二群组的绑定关系，例如，可以通过表格的形式建立第一群组与第二群组之间的绑定关系，即在绑定关系表中增加第一群组的标识以及第二群组的标识，表明两者具有绑定关系。例如，若第一群组的标识为1-12，第二群组的标识为2-02，那么如表1所示的绑定关系表中，可以增加编号1对应的绑定关系群组1-12和2-02。从而，系统互通实体就可以建立第一群组与第二群组的绑定关系。
进一步的，在一种可能的实施场景中，为第一群组与第二群组建立的绑定关系中还可以包括绑定关系标识信息。绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，例如(1-12 2-02)；也可以是绑定关系中任意一个群组的群组标识，例如2-02；还可以是新建的用于表示第一群组与第二群组的绑定关系的标识，例如表1中的编号。
进一步的，第二群组连接请求消息中包括第一群组的群组角色和第二群组的群组角色 时，绑定关系也可以包括第一群组的群组角色和所述第二群组的群组角色，例如表2所示的绑定关系表。
可选的，步骤S106之前，还可以执行步骤S104和步骤S105：
步骤S104，系统互通实体向第二通信系统的授权检查实体发送授权指示消息。
第二通信系统的授权检查实体可以是具备授权检查功能的网络设备或网络设备中的模块，例如服务器或服务器中的软件程序模块，这里不作具体限定。授权指示消息中携带第二群组的标识，用于指示第二通信系统的授权检查实体对第二群组进行授权检查，检查第二群组是否能够建立绑定关系。可选地，授权指示消息中携带第一通信系统的群组管理客户端的用户的标识信息。
与第一通信系统相似的，授权检查实体中也可以预存第二通信系统的多个群组的授权信息，授权信息中可以包括各群组分别对应的授权用户以及授权用户具备的权限，也就是说，通过授权信息可以得到某一群组的授权用户具备对该群组进行哪些操作的权限。因此，第一通信系统的群组管理服务器可以检查是否允许第二群组建立绑定关系。需要说明的是，由于第二通信系统的授权检查实体为第二通信系统的网络设备，通常来说检查的对象是针对第二群组的。
步骤S105，当第二通信系统的授权检查实体允许第二群组建立绑定关系时，第二通信系统的授权检查实体向系统互通实体发送授权成功响应消息。
授权成功响应消息用于指示第二通信系统允许第二群组建立绑定关系。从而进一步执行步骤S106。
步骤S107，系统互通实体向第一通信系统的群组管理服务器发送第一指示消息。
在一种可能的实施场景中，第一指示消息可以为群组连接响应消息，用于通知第一通信系统的群组管理服务器第一群组的绑定关系已建立。系统互通实体通过消息名称即可确定第一群组的绑定关系已建立。
在另一种可能的实施场景中，第一指示消息可以包括第一群组的绑定关系信息，绑定关系信息可以为绑定关系指示。绑定关系指示用于指示第一群组的绑定关系已建立，例如绑定关系指示可以是第一指示消息中的一个保留比特位置1，也可以是新增的一个比特位置0，用于指示第一群组绑定关系的建立。
在又一种可能的实施场景中，第一指示消息中的第一群组的绑定关系信息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中任意一个群组的群组标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。从而第一指示消息可以指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。
进一步可选的，第一指示消息还可以携带与第一群组建立绑定关系的其他群组的标识。
进一步的，第一指示消息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
步骤S108，系统互通实体向第二通信系统的第二业务控制实体发送第二指示消息。
第二指示消息用于通知第二群组的绑定关系已建立。第二指示消息可以包括绑定关系指示，绑定关系指示用于指示第二群组的绑定关系已建立。第二指示消息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中任意一个群组的标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。第二指示消息用于指示第二群组的绑定关系已建立，并且绑定关系标识信息唯一指示第二群组与第一群组建立的绑定关系。进一步可选的，第二指示消息还可以携带与第二群组建立绑定关系的其他群组的标识。
进一步的，第二指示消息还可以包括第二群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
进一步的，步骤S107或者步骤S108之后，还可以执行步骤S109-S112：
步骤S109，第一通信系统的群组管理服务器增加第一群组的绑定关系信息。
第一通信系统的群组管理服务器为第一群组增加相应的绑定关系信息。具体来说，绑定关系信息是根据第一指示消息确定的。绑定关系信息可以指第一群组被绑定的绑定关系指示，也可以还包括绑定关系标识信息，指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。进一步的，绑定关系信息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
步骤S110，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送群组连接通知消息。
群组连接通知消息用于通知第一通信系统的第一业务控制实体第一群组已建立连接关系。群组连接通知消息中可以包括第一群组的标识，也可以包括第一群组的标识以及绑定关系指示。当第一指示消息能够携带绑定关系标识信息时，群组连接通知消息还可以包括第一群组的标识、绑定关系标识信息以及绑定关系指示。
进一步的，群组连接通知消息中还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色，具体根据第一通信系统的群组管理服务器接收到的第一指示消息确定。
步骤S111，第一通信系统的第一业务控制实体增加第一群组的绑定关系信息。
第一通信系统的群组管理服务器为第一群组增加相应的绑定关系信息。具体来说，绑定关系信息是根据群组连接通知消息确定的。绑定关系信息可以指第一群组被绑定的绑定关系指示，也可以还包括绑定关系标识信息，指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。进一步的，绑定关系信息还可以包括第一群组的群组角色，也可以还包括第二群组的群组角色。
步骤S112，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接响应消息，指示群组绑定关系建立成功。
第一通信系统的群组管理服务器接收到第一指示消息后可以确定绑定关系建立成功，从而向第一通信系统的群组管理客户端发送群组连接响应消息，指示群组绑定关系建立成功。
需要说明的是，步骤S109、步骤S110-S111以及步骤S112之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S113，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接响应消息，指示群组绑定关系建立失败。
在授权检查失败后，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接响应消息，指示群组绑定关系建立失败。
参见图2c，本申请实施例提供了一种群组连接解除方法。该方法与图2b所示的群组连接方法是对应的，可以在图2b所示的实施例之后实施本方案。该方法包括但不限于以下步骤。
步骤S201，第一通信系统的群组管理客户端向第一通信系统的群组管理服务器发送第一群组连接解除请求消息。
在一种可能的实施场景中，第一群组连接解除请求消息中包括目标群组的标识，目标群组为第一群组或第二群组。第一群组连接解除请求消息用于请求解除目标群组的绑定关系。在该实施场景中，目标群组可能只存在一个绑定关系，也可能存在多个绑定关系，那么，第一群组连接解除请求消息用于请求解除目标群组的所有绑定关系。
在另一种可能的实施场景中，第一群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，目标群组为第一群组或第二群组。在该实施场景中，目标群组可能存在多个绑定关系，绑定关系标识信息用于指示目标群组的一个特定的目标绑定关系，具体来说，绑定关系标识信息可以是目标群组的标识以及与目标群组建立目标绑定关系的其他群组的标识的组合；也可以是其他可以识别目标绑定关系的信息，如数字编号；还可以是绑定关系中任意一个群组的群组标识，这里不做具体限定。
步骤S202，第一通信系统的群组管理服务器检查第一通信系统的群组管理客户端的用户是否具备请求目标群组解除绑定关系的权限。若具备请求目标群组解除绑定关系的权限，则执行步骤S203-S209；否则，执行步骤S210。
第一通信系统的群组管理服务器在接收到第一群组连接解除请求消息后，需要对第一通信系统的群组管理客户端的用户进行授权检查，也即检查第一通信系统的群组管理客户端是否具备请求目标群组解除绑定关系的权限。
在一种可能的实施场景中，第一通信系统的群组管理服务器中预存有第一通信系统的多个群组的授权信息，授权信息中可以包括各群组分别对应的授权用户以及授权用户具备的权限，也就是说，通过授权信息可以得到某一群组的授权用户具备对该群组进行哪些操作的权限。需要说明的是，这里的授权信息可以是分别存在各个群组的群组信息或者签约配置信息中的部分内容，也可以是作为独立的表格或者数组整体进行存储的映射关系，这里不在具体限定。
在另一种可能的实施场景中，第一通信系统的群组管理服务器中未存储第一通信系统的群组管理客户端的用户的授权信息，可以从第一通信系统的第一业务控制实体急获取第一通信系统的群组管理客户端的用户签约配置信息，从签约配置信息中获取第一通信系统的群组管理客户端的用户的授权信息，进而进行授权检查。这里，第一业务控制实体可以是紧急任务服务服务器，包括紧急任务一键通服务器、紧急任务视频服务器或紧急任务数据服务器等。
因此，第一通信系统的群组管理服务器可以检查第一通信系统的群组管理客户端的用户是否具备请求目标群组解除绑定关系的权限。若第一通信系统的群组管理客户端的用户具备请求目标群组解除绑定关系的权限，则说明授权检查成功，否则说明授权检查失败。
需要说明的是，步骤S202可以作为可选的步骤，本申请实施例也可以不执行步骤S202，直接执行步骤S203-S209。
步骤S203，第一通信系统的群组管理服务器向系统互通实体发送第二群组连接解除请求消息。
在授权检查成功后，第一通信系统的群组管理服务器向系统互通实体发送第二群组连接请求消息，这里的第二群组连接解除请求消息即为群组连接解除请求消息。根据第一群组连接解除请求消息携带的内容，第二群组连接解除请求消息中可以包括目标群组的标识，也可以包括目标群组的标识和目标群组的绑定关系标识信息。
在一种可能的实施场景中，第二群组连接解除请求消息中包括群组绑定关系标识信息，执行步骤S2041。
在另一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，执行步骤S2042。
在又一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识，执行步骤S2043。
步骤S2041，系统互通实体解除群组绑定关系标识指示的绑定关系。
系统互通实体解除之前建立的由群组绑定关系标识指示的绑定关系。当仅允许每个群组有一个群组绑定关系时，群组绑定关系标识可以是绑定关系中的任意一个群组标识。
步骤S2042，系统互通实体解除绑定关系标识信息所指示的目标绑定关系中目标群组与其他群组之间的绑定关系。
系统互通实体解除的是目标群组在目标绑定关系中与其他群组的绑定关系。例如，目标群组A包括两个绑定关系，分别为群组绑定关系一：A与B绑定，群组绑定关系二：A、C与D绑定，假设绑定关系标识信息为群组绑定关系二的标识(如<A,C,D>,或者编号2)，那么系统互通实体解除的就是目标群组A与群组C和群组D的绑定关系，但是群组C和群组D的绑定关系依然存在。如果目标绑定关系中仅包两个群组：即目标群组和另外一个群组，则系统互通实体解除的是目标群组在目标绑定关系中与其他群组的绑定关系后，该绑定关系也无法成立，系统互通实体删除该绑定关系。
步骤S2043，系统互通实体解除所有包含目标群组标识的绑定关系中目标群组与其他群组的绑定关系。
例如，目标群组A包括两个绑定关系，分别为群组绑定关系一：A与B绑定，群组绑定关系二：A、C与D绑定。系统互通实体分别解除目标群组标识在两个绑定关系与其他群组的绑定关系。如果目标绑定关系中仅包两个群组：即目标群组和另外一个群组，则系统互通实体解除的是目标群组在目标绑定关系中与其他群组的绑定关系后，该绑定关系也无法成立，系统互通实体删除该绑定关系。在上述实例中，绑定关系一在B的绑定关系解除后，也被系统互通实体删除。
当目标群组为第一群组时，执行步骤S2051；当目标群组为所述第二群组时，执行步 骤S2052。
步骤S2051，系统互通实体向第一通信系统的群组管理服务器发送第四指示消息。
第四指示消息用于通知第一通信系统的群组管理服务器目标群组的绑定关系已解除。具体来说，第四指示消息可以为群组连接解除响应消息，从而第一通信系统的群组管理服务器知道自身请求的目标群组的群组连接解除请求已经被响应。
步骤S2052，系统互通实体向第二通信系统的第二业务控制实体发送第五指示消息。
第五指示消息用于通知第二通信系统的第二业务控制实体目标群组的绑定关系已解除。具体来说，第五指示消息可以包括目标群组的标识，还可以包括目标群组的绑定关系标识信息，根据第二群组连接解除请求消息来确定。
进一步的，步骤S2051之后，还可以执行步骤S206-S209：
步骤S206，第一通信系统的群组管理服务器删除目标群组的绑定关系信息。
第一通信系统的群组管理服务器将之前增加的第一群组的绑定关系信息删除。具体可以根据第一群组连接解除请求消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
步骤S207，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送群组连接解除通知消息。
群组连接通知消息用于通知第一通信系统的第一业务控制实体目标群组的绑定关系已解除。群组连接解除通知消息中可以包括第一群组的标识，也可以包括第一群组的标识以及绑定关系标识信息，根据第二群组连接解除请求消息来确定。
步骤S208，第一通信系统的第一业务控制实体删除目标群组的绑定关系信息。
第一通信系统的第一业务控制实体将之前增加的第一群组的绑定关系信息删除。具体可以根据群组连接通知消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
步骤S209，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接解除响应消息，指示群组绑定关系解除成功。
第一通信系统的群组管理服务器接收到第四指示消息后可以确定绑定关系解除成功，从而向第一通信系统的群组管理客户端发送群组连接解除响应消息，指示群组绑定关系解除成功。
需要说明的是，步骤S206、步骤S207-S208以及步骤S209之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S210，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接解除响应消息，指示群组绑定关系接解除失败。
在授权检查失败后，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接解除响应消息，指示群组绑定关系解除失败。
参见图3a，本申请实施例提供了另一种群组连接方法。该方法包括但不限于以下步骤。
步骤S301，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第 一群组连接请求消息。
第一群组连接请求消息中包括第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，第一群组连接请求消息用于请求建立第一群组与第二群组之间的绑定关系。其中，第一群组是指第一通信系统中的群组，第二群组是指第二通信系统中的群组。第一群组与第二群组的绑定关系是指，将第一群组与第二群组之间关联起来，形成一个逻辑意义上的整体，在具有绑定关系时，第一群组或第二群组中的任意一个群组被呼叫时，另一个群组也会被呼叫。需要说明的是，本申请实施例仅以第一群组与第二群组两个群组为例描述绑定关系建立的过程，在实际应用过程中，建立绑定关系的群组数量可以是两个以上，原理与本申请实施例中的方法完全一致，这里不具体赘述。
具体实施中，第一通信系统的业务客户端可以通过与其他设备的交互来获取第二群组的标识，也可以通过预先配置的方式将第二群组的标识预存在第一通信系统的业务客户端中，这里不作具体限定。
进一步可选的，第一群组连接请求消息中还可以包括第一群组的群组角色和第二群组的群组角色。其中，群组角色指的是群组呼叫时担任的角色，具体可以是主控群组角色，也可以是非主控/从属群组角色。具体来说，一个群组通信中只能有一个主控群组角色，那么也可以仅指定主控群组角色，其他群组角色缺省即可默认为非主控/从属群组角色。例如，第一群组连接请求消息可以包括第一群组为主控群组角色，第二群组为非主控/从属群组角色；第一群组连接请求消息也可以包括第一群组为主控群组角色，而第二群组的群组角色缺省，那么可以默认为第二群组为非主控/从属群组角色。
步骤S302，第一通信系统的第一业务控制实体检查第一通信系统的业务客户端的用户是否具备请求第一群组与第二群组建立绑定关系的权限。若具备请求第一群组与第二群组建立绑定关系的权限，则执行步骤S303-S313；否则，执行步骤S314。
第一通信系统的第一业务控制实体在接收到第一群组连接请求消息后，需要对第一通信系统的业务客户端的用户进行授权检查，也即检查第一通信系统的业务客户端是否具备请求第一群组与第二群组建立绑定关系的权限。
在一种可能的实施场景中，第一通信系统的第一业务控制实体中预存有第一通信系统的业务客户端的用户的签约配置信息，签约配置信息中包含该用户可以对哪些群组执行何种操作。
在另一种可能的实施场景中，第一通信系统的第一业务控制实体中预存有第一通信系统的多个群组的授权信息，授权信息中可以包括各群组分别对应的授权用户以及授权用户具备的权限，也就是说，通过授权信息可以得到某一群组的授权用户具备对该群组进行哪些操作的权限。需要说明的是，这里的授权信息可以是分别存在各个群组的群组信息或者签约配置信息中的部分内容，也可以是作为独立的表格或者数组整体进行存储的映射关系，这里不在具体限定。
在又一种可能的实施场景中，第一通信系统的第一业务控制实体中未存储业务客户端的用户的授权信息，可以从第一通信系统的第一群组管理服务器中获取用户的授权信息，进而进行授权检查。
因此，第一通信系统的第一业务控制实体可以检查第一通信系统的业务客户端的用户 是否具备请求第一群组与第二群组建立绑定关系的权限。若第一通信系统的业务客户端的用户具备请求第一群组与第二群组建立绑定关系的权限，则说明授权检查成功，否则说明授权检查失败。
需要说明的是，由于第一通信系统的第一业务控制实体为第一通信系统的网络设备，通常来说检查的对象是针对第一群组的。也就是说，实际是检查第一通信系统的业务客户端的用户是否具备请求第一群组与其他群组建立绑定关系的权限。
需要说明的是，步骤S302可以作为可选的步骤，本申请实施例也可以不执行步骤S302，直接执行步骤S303-S313。
步骤S303，第一通信系统的第一业务控制实体向第一通信系统的群组管理服务器发送第二群组连接请求消息。
与第一群组连接请求消息中包含的内容相似的，第二群组连接请求消息中包括第一群组的标识和第二群组的标识。进一步可选的，第二群组连接请求消息中还可以包括第一群组的群组角色和第二群组的群组角色。
步骤S304，第一通信系统的群组管理服务器向系统互通实体发送第三群组连接请求消息。
这里的第三群组连接请求消息即为群组连接请求消息，包括从第二群组连接请求消息中接收到的第一群组的标识和第二群组的标识。进一步可选的，第三群组连接请求消息中还可以包括第一群组的群组角色和第二群组的群组角色。
可选的，步骤S304之前，第一通信系统的群组管理服务器可以进一步进行授权检查，检查第一群组与第二群组是否能够建立绑定关系。
第一通信系统的群组管理服务器在接收到第二群组连接解除请求消息后，可以进一步对第一通信系统的群组管理客户端进行授权检查，也即检查第一通信系统的群组管理客户端是否具备请求目标群组解除绑定关系的权限。第一通信系统的群组管理服务器中预存有第一通信系统的多个群组的授权信息，授权信息中可以包括各群组分别对应的授权用户以及授权用户具备的权限，也就是说，通过授权信息可以得到某一群组的授权用户具备对该群组进行哪些操作的权限。需要说明的是，这里的授权信息可以是分别存在各个群组的群组信息或者签约配置信息中的部分内容，也可以是作为独立的表格或者数组整体进行存储的映射关系，这里不在具体限定。
步骤S307，系统互通实体建立第一群组与第二群组的绑定关系。
参见步骤S106。
可选的，步骤S307之前，还可以执行步骤S305和步骤S306：
步骤S305，系统互通实体向第二通信系统的授权检查实体发送授权指示消息。
步骤S306，当第二通信系统的授权检查实体允许第二群组建立绑定关系时，第二通信系统的授权检查实体向系统互通实体发送授权成功响应消息。
参见步骤S104-S105。
步骤S308，系统互通实体向第一通信系统的群组管理服务器发送第一指示消息。
步骤S309，系统互通实体向第二通信系统的第二业务控制实体发送第二指示消息。
参见步骤S107-S108。
进一步的，步骤S308或者步骤S309之后，还可以执行步骤S310-S313：
步骤S310，第一通信系统的群组管理服务器增加第一群组的绑定关系信息。
参见步骤S109。
步骤S311，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送群组连接响应消息。
群组连接响应消息用于通知第一通信系统的第一业务控制实体第一群组已建立连接关系。与步骤S308相似的，在一种可能的实施场景中，系统互通实体通过消息名称即可确定第一群组的绑定关系已建立。在另一种可能的实施场景中，群组连接响应消息可以包括第一群组的绑定关系信息，绑定关系信息可以为绑定关系指示。绑定关系指示用于指示第一群组的绑定关系已建立，例如绑定关系指示可以是第一指示消息中的一个保留比特位置1，也可以是新增的一个比特位置0，用于指示第一群组绑定关系的建立。
在又一种可能的实施场景中，群组连接响应消息的第一群组的绑定关系信息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中的任意一个群组的标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。从而群组连接响应消息可以指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。
进一步可选的，群组连接响应消息还可以携带与第一群组建立绑定关系的其他群组的标识。
进一步的，群组连接响应消息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
需要说明的是，步骤S310与步骤S311之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S312，第一通信系统的第一业务控制实体增加第一群组的绑定关系信息。
参见步骤S111。
步骤S313，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立成功。
第一通信系统的第一业务控制实体接收到群组管理服务器发送的群组连接响应消息后可以确定绑定关系建立成功，从而向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立成功。
需要说明的是，步骤S312与步骤S313之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S314，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立失败。
在授权检查失败后，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立失败。
参见图3b，本申请实施例提供了另一种群组连接解除方法。该方法与图3a所示的群 组连接方法是对应的，可以在图3a所示的实施例之后实施本方案。该方法包括但不限于以下步骤。
步骤S401，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第一群组连接解除请求消息。
在一种可能的实施场景中，第一群组连接解除请求消息中包括目标群组的标识，目标群组为第一群组或第二群组。第一群组连接解除请求消息用于请求解除目标群组的绑定关系。在该实施场景中，目标群组可能只存在一个绑定关系，也可能存在多个绑定关系，那么，第一群组连接解除请求消息用于请求解除目标群组的所有绑定关系。
在另一种可能的实施场景中，第一群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，目标群组为第一群组或第二群组。在该实施场景中，目标群组可能存在多个绑定关系，绑定关系标识信息用于指示目标群组的一个特定的目标绑定关系，具体来说，绑定关系标识信息可以是目标群组的标识以及与目标群组建立目标绑定关系的其他群组的标识的组合；也可以是绑定关系中任意一个群组标识；也可以是其他可以识别目标绑定关系的信息，如数字编号，这里不做具体限定。
步骤S402，第一通信系统的第一业务控制实体检查第一通信系统的业务客户端是否具备请求目标群组解除绑定关系的权限。若具备请求目标群组解除绑定关系的权限，则执行步骤S403-S410；否则，执行步骤S411。
第一通信系统的第一业务控制实体在接收到第一群组连接解除请求消息后，需要对第一通信系统的业务客户端的用户进行授权检查，也即检查第一通信系统的业务客户端是否具备请求目标群组解除绑定关系的权限。
在一种可能的实施场景中，第一通信系统的第一业务控制实体中预存有第一通信系统的业务客户端的用户的签约配置信息，签约配置信息中包含该用户可以对哪些群组执行何种操作。
在另一种可能的实施场景中，第一通信系统的第一业务控制实体中预存有第一通信系统的多个群组的授权信息，授权信息中可以包括各群组分别对应的授权用户以及授权用户具备的权限，也就是说，通过授权信息可以得到某一群组的授权用户具备对该群组进行哪些操作的权限。需要说明的是，这里的授权信息可以是分别存在各个群组的群组信息或者签约配置信息中的部分内容，也可以是作为独立的表格或者数组整体进行存储的映射关系，这里不在具体限定。
在又一种可能的实施场景中，第一通信系统的第一业务控制实体中未存储业务客户端的用户的授权信息，可以从第一通信系统的第一群组管理服务器中获取用户的授权信息，进而进行授权检查。
因此，第一通信系统的第一业务控制实体可以检查第一通信系统的业务客户端的用户是否具备请求目标群组解除绑定关系的权限。若第一通信系统的业务客户端的用户具备请求目标群组解除绑定关系的权限，则说明授权检查成功，否则说明授权检查失败。
需要说明的是，由于第一通信系统的第一业务控制实体为第一通信系统的网络设备，通常来说检查的对象是针对第一群组的。也就是说，实际是检查第一通信系统的业务客户端的用户是否具备请求第一群组与其他群组解除绑定关系的权限。
需要说明的是，步骤S402可以作为可选的步骤，本申请实施例也可以不执行步骤S102，直接执行步骤S403-S410。
步骤S403，第一通信系统的第一业务控制实体向第一通信系统的群组管理服务器发送第二群组连接解除请求消息。
与第一群组连接解除请求消息中包含的内容相似的，在一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识，目标群组为第一群组或第二群组。在另一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，目标群组为第一群组或第二群组。
步骤S404，第一通信系统的群组管理服务器向系统互通实体发送第三群组连接解除请求消息。
这里的第三群组连接解除请求消息即为群组连接解除请求消息，包括从第二群组连接解除请求消息中接收到的目标群组的标识或目标群组的标识和目标群组的绑定关系标识信息。
在一种可能的实施场景中，第二群组连接解除请求消息中包括群组绑定关系标识信息，执行步骤S4051。
在另一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，执行步骤S4052。
在又一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识，执行步骤S4053。
步骤S4051，系统互通实体解除群组绑定关系标识指示的绑定关系。
步骤S4052，系统互通实体解除绑定关系标识信息所指示的目标绑定关系中目标群组与其他群组之间的绑定关系。
步骤S4053，系统互通实体解除所有包含目标群组标识的绑定关系中目标群组与其他群组的绑定关系。
参见步骤S2041-S2043。
当目标群组为第一群组时，执行步骤S4061；当目标群组为所述第二群组时，执行步骤S4062。
步骤S4061，系统互通实体向第一通信系统的群组管理服务器发送第四指示消息。
步骤S4062，系统互通实体向第二通信系统的第二业务控制实体发送第五指示消息。
参见步骤S2051-S2052。
进一步的，步骤S4061之后，还可以执行步骤S407-S410：
步骤S407，第一通信系统的群组管理服务器删除目标群组的绑定关系信息。
第一通信系统的群组管理服务器将之前增加的第一群组的绑定关系信息删除。具体可以根据第二群组连接解除请求消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
步骤S408，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送群组连接解除响应消息。
群组连接响应消息用于通知第一通信系统的第一业务控制实体目标群组的绑定关系 已解除。从而第一通信系统的第一业务控制实体知道自身请求的目标群组的第二群组连接解除请求已经被响应。
需要说明的是，步骤S407与步骤S408之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S409，第一通信系统的第一业务控制实体删除目标群组的绑定关系信息。
第一通信系统的第一业务控制实体将之前增加的目标群组的绑定关系信息删除。具体可以根据第一群组连接解除请求消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
步骤S410，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接解除响应消息，指示群组绑定关系解除成功。
第一通信系统的第一业务控制实体接收到群组连接解除响应消息后可以确定绑定关系解除成功，从而向第一通信系统的群组管理客户端发送群组连接解除响应消息，指示群组绑定关系解除成功。
需要说明的是，步骤S409与步骤S410之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S411，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接解除响应消息，指示群组绑定关系接解除失败。
在授权检查失败后，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接解除响应消息，指示群组绑定关系解除失败。
参见图4a，本申请实施例提供了另一种群组连接方法。该方法包括但不限于以下步骤。
步骤S501，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第一群组连接请求消息。
步骤S502，第一通信系统的第一业务控制实体检查第一通信系统的业务客户端是否具备请求第一群组与第二群组建立绑定关系的权限。若具备请求第一群组与第二群组建立绑定关系的权限，则执行步骤S503-S512；否则，执行步骤S513。
参见步骤S301-S302。
需要说明的是，步骤S502可以作为可选的步骤，本申请实施例也可以不执行步骤S502，直接执行步骤S503-S512。
步骤S503，第一通信系统的第一业务控制实体向系统互通实体发送第二群组连接请求消息。
与第一群组连接请求消息中包含的内容相似的，第二群组连接请求消息中包括第一群组的标识和第二群组的标识。进一步可选的，第二群组连接请求消息中还可以包括第一群组的群组角色和第二群组的群组角色。
步骤S506，系统互通实体建立第一群组与第二群组的绑定关系。
参见步骤S106。
可选的，步骤S506之前，还可以执行步骤S504和步骤S505：
步骤S504，系统互通实体向第二通信系统的授权检查实体发送授权指示消息。
步骤S505，当第二通信系统的授权检查实体允许第二群组建立绑定关系时，第二通信系统的授权检查实体向系统互通实体发送授权成功响应消息。
参见步骤S104-S105。
步骤S507，系统互通实体向第一通信系统的第一业务控制实体发送第一指示消息。
在一种可能的实施场景中，第一指示消息可以为群组连接响应消息，用于通知第一通信系统的第一业务控制实体第一群组的绑定关系已建立。系统互通实体通过消息名称即可确定第一群组的绑定关系已建立。
在另一种可能的实施场景中，第一指示消息可以包括第一群组的绑定关系信息，绑定关系信息可以为绑定关系指示。绑定关系指示用于指示第一群组的绑定关系已建立，例如绑定关系指示可以是第一指示消息中的一个保留比特位置1，也可以是新增的一个比特位置0，用于指示第一群组绑定关系的建立。
在又一种可能的实施场景中，第一指示消息中的第一群组的绑定关系信息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中任意一个群组的群组标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。从而第一指示消息可以指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。
进一步可选的第一指示消息中还可以携带与第一群组建立绑定关系的其他群组的标识。
进一步的，第一指示消息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
步骤S508，系统互通实体向第二通信系统的第二业务控制实体发送第二指示消息。
参见步骤S108。
进一步的，步骤S507或者步骤S508之后，还可以执行步骤S509-S510：
步骤S509，第一通信系统的第一业务控制实体增加第一群组的绑定关系信息。
步骤S510，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立成功。
参见步骤S312-S313。
需要说明的是，步骤S509和S510之间没有必然的执行先后顺序，可以根据情况进行调整。
进一步的，步骤S506之后，还可以执行步骤S511-S512：
步骤S511，系统互通实体向第一通信系统的群组管理服务器发送群组连接通知消息。
群组连接通知消息用于通知第一通信系统的群组管理服务器第一群组已建立连接关系。群组连接通知消息中可以包括第一群组的标识，也可以包括第一群组的标识以及绑定关系指示。当第一指示消息能够携带绑定关系标识信息时，群组连接通知消息还可以包括第一群组的标识、绑定关系标识信息以及绑定关系指示。
进一步的，群组连接通知消息中还可以包括第一群组的群组角色，也可以包括第一群 组和第二群组分别的群组角色，具体根据系统互通实体接收到的第二群组连接请求消息确定。
步骤S512，第一通信系统的群组管理服务器增加第一群组的绑定关系信息。
第一通信系统的群组管理服务器为第一群组增加相应的绑定关系信息。具体来说，绑定关系信息是根据群组连接通知消息确定的。绑定关系信息可以指第一群组被绑定的绑定关系指示，也可以包括绑定关系标识信息，指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。进一步的，绑定关系信息还可以包括第一群组的群组角色，也可以还包括第二群组的群组角色。
步骤S513，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立失败。
参见步骤S314。
参见图4b，本申请实施例提供了另一种群组连接解除方法。该方法与图4a所示的群组连接方法是对应的，可以在图4a所示的实施例之后实施本方案。该方法包括但不限于以下步骤。
步骤S601，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第一群组连接解除请求消息。
步骤S602，第一通信系统的第一业务控制实体检查第一通信系统的业务客户端是否具备请求目标群组解除绑定关系的权限。若具备请求目标群组解除绑定关系的权限，则执行步骤S603-S609；否则，执行步骤S610。
参见步骤S401-S402。
需要说明的是，步骤S602可以作为可选的步骤，本申请实施例也可以不执行步骤S602，直接执行步骤S603-S609。
骤S603，第一通信系统的第一业务控制实体向系统互通实体发送第二群组连接解除请求消息。
与第一群组连接解除请求消息中包含的内容相似的，在一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识，目标群组为第一群组或第二群组。在另一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，目标群组为第一群组或第二群组。
在一种可能的实施场景中，第二群组连接解除请求消息中包括群组绑定关系标识信息，执行步骤S6041。
在另一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，执行步骤S6042。
在又一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识，执行步骤S6043。
步骤S6041，系统互通实体解除群组绑定关系标识指示的绑定关系。
步骤S6042，系统互通实体解除绑定关系标识信息所指示的目标绑定关系中目标群组与其他群组之间的绑定关系。
步骤S6043，系统互通实体解除所有包含目标群组标识的绑定关系中目标群组与其他群组的绑定关系。
参见步骤S2041-S2043。
当目标群组为第一群组时，执行步骤S6051；当目标群组为所述第二群组时，执行步骤S6052。
步骤S6051，系统互通实体向第一通信系统的第一业务控制实体发送第四指示消息。
第四指示消息用于通知第一通信系统的第一业务控制实体目标群组的绑定关系已解除。具体来说，第四指示消息可以为群组连接解除响应消息，从而第一通信系统的第一业务控制实体知道自身请求的目标群组的群组连接解除请求已经被响应。
步骤S6052，系统互通实体向第二通信系统的第二业务控制实体发送第五指示消息。
参见步骤S2052。
进一步的，步骤S6051之后，还可以执行步骤S606-S607：
步骤S606，第一通信系统的第一业务控制实体删除目标群组的绑定关系信息。
第一通信系统的第一业务控制实体将之前增加的目标群组的绑定关系信息删除。具体可以根据第一群组连接解除请求消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
步骤S607，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接解除响应消息，指示群组绑定关系解除成功。
参考步骤S410。
需要说明的是，步骤S606和步骤S607之间没有必然的执行先后顺序，可以根据情况进行调整。
进一步的，步骤S6041或步骤S6042之后，还可以执行步骤S608-S609：
步骤S608，系统互通实体向第一通信系统的群组管理服务器发送群组连接解除通知消息。
群组连接通知消息用于通知第一通信系统的群组管理服务器第一群组已解除连接关系。群组连接通知消息中可以包括目标群组的标识，也可以包括目标群组的标识和目标群组的绑定关系标识信息。
步骤S609，第一通信系统的群组管理服务器删除目标群组的绑定关系信息。
第一通信系统的群组管理服务器将之前增加的目标群组的绑定关系信息删除。具体可以根据群组连接通知消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
步骤S610，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接解除响应消息，指示群组绑定关系解除失败。
参见步骤S411。
参见图5a，本申请实施例提供了另一种群组连接方法。该方法包括但不限于以下步骤。
步骤S701，第一通信系统的群组管理客户端向第一通信系统的群组管理服务器发送 群组连接请求消息。
步骤S702，第一通信系统的群组管理服务器检查第一通信系统的群组管理客户端是否具备请求第一群组与第二群组建立绑定关系的权限。若具备请求第一群组与第二群组建立绑定关系的权限，则执行步骤S703-S709；否则，执行步骤S710。
参见步骤S101-S102。
需要说明的是，步骤S702可以作为可选的步骤，本申请实施例也可以不执行步骤S702，直接执行步骤S703-S709。
步骤S703，第一通信系统的群组管理服务器建立第一群组与第二群组的绑定关系。
第一通信系统的群组管理服务器建立第一群组与第二群组的绑定关系，例如，可以通过表格的形式建立第一群组与第二群组之间的绑定关系，即在绑定关系表中增加第一群组的标识以及第二群组的标识，表明两者具有绑定关系。例如，若第一群组的标识为1-12，第二群组的标识为2-02，那么如表1所示的绑定关系表中，可以增加编号1对应的绑定关系群组1-12和2-02。从而，系统互通实体就可以建立第一群组与第二群组的绑定关系。
进一步的，在一种可能的实施场景中，为第一群组与第二群组建立的绑定关系中还可以包括绑定关系标识信息。绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，例如(1-12 2-02)；也可以是绑定关系中任意一个群组的标识，例如2-02；还可以是新建的用于表示第一群组与第二群组的绑定关系的标识，例如表1中的编号。
进一步的，群组连接请求消息中包括第一群组的群组角色和第二群组的群组角色时，绑定关系也可以包括第一群组的群组角色和所述第二群组的群组角色，例如表2所示的绑定关系表。
可选的，第一通信系统的群组管理服务器还可以通过系统互通实体向第二通信系统的授权检查实体发送授权指示消息，当第二通信系统的授权检查实体允许第二群组建立绑定关系时，第二通信系统的授权检查实体向系统互通实体发送授权成功响应消息，从而执行步骤S703。
步骤S704，第一通信系统的群组管理服务器向系统互通实体发送第三指示消息。
第三指示消息可以为群组连接通知消息，第三指示消息包括第一群组的标识和第二群组的标识，用于通知系统互通实体第一群组与第二群组的绑定关系已建立。进一步可选的，第三指示消息中还可以包括第一群组与第二群组的绑定关系标识信息。再进一步可选的，第三指示消息中还可以包括第一群组的群组角色和第二群组的群组角色。
步骤S704后进一步执行步骤S705和S706：
步骤S705，系统互通实体保存第一群组与第二群组的绑定关系。
系统互通实体可以将第一群组与第二群组的绑定关系保存起来，与步骤S703相似的，保存的可以是第一群组与第二群组的标识之间的关系，例如如果保存在绑定关系表中，则在绑定关系表中增加第一群组的标识以及第二群组的标识，表明两者具有绑定关系。进一步可选的，还可以保存第一群组与第二群组的绑定关系标识信息。再进一步可选的，还可以保存第一群组的群组角色和第二群组的群组角色。
步骤S706，系统互通实体向第二通信系统的第二业务控制实体发送第二指示消息。
参见步骤S108。
需要说明的是，步骤S705和步骤S706之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S707，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送第一指示消息，指示群组绑定关系已建立。
在一种可能的实施场景中，第一指示消息可以为群组连接响应消息，用于通知第一通信系统的群组管理客户端第一群组的绑定关系已建立。系统互通实体通过消息名称即可确定第一群组的绑定关系已建立。
在另一种可能的实施场景中，第一指示消息可以包括第一群组的绑定关系信息，绑定关系信息可以为绑定关系指示。绑定关系指示用于指示第一群组的绑定关系已建立，例如绑定关系指示可以是第一指示消息中的一个保留比特位置1，也可以是新增的一个比特位置0，用于指示第一群组绑定关系的建立。
在又一种可能的实施场景中，第一指示消息中的第一群组的绑定关系信息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中任意一个群组的群组标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。从而第一指示消息可以指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。
进一步可选的第一指示消息中还可以携带与第一群组建立绑定关系的其他群组的标识。
进一步的，第一指示消息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
步骤S708，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送群组连接通知消息。
步骤S709，第一通信系统的第一业务控制实体增加第一群组的绑定关系信息。
参见步骤S110-S111。
需要说明的是，步骤S704、步骤S707、步骤S708-S709之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S710，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接响应消息，指示群组绑定关系建立失败。
参见步骤S113。
参见图5b，本申请实施例提供了另一种群组连接解除方法。该方法与图5a所示的群组连接方法是对应的，可以在图5a所示的实施例之后实施本方案。该方法包括但不限于以下步骤。
步骤S801，第一通信系统的群组管理客户端向第一通信系统的群组管理服务器发送群组连接解除请求消息。
在一种可能的实施场景中，群组连接解除请求消息中包括目标群组的标识，目标群组为第一群组或第二群组。群组连接解除请求消息用于请求解除目标群组的绑定关系。在该 实施场景中，目标群组可能只存在一个绑定关系，也可能存在多个绑定关系，那么，群组连接解除请求消息用于请求解除目标群组的所有绑定关系。
在另一种可能的实施场景中，群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，目标群组为第一群组或第二群组。在该实施场景中，目标群组可能存在多个绑定关系，绑定关系标识信息用于指示目标群组的一个特定的目标绑定关系，具体来说，绑定关系标识信息可以是目标群组的标识以及与目标群组建立目标绑定关系的其他群组的标识；也可以是其他可以识别目标绑定关系的信息，如数字编号；还可以是绑定关系中任意一个群组的群组标识，这里不做具体限定。
步骤S802，第一通信系统的群组管理服务器检查第一通信系统的群组管理客户端是否具备请求目标群组建立绑定关系的权限。若具备请求第一群组与第二群组建立绑定关系的权限，则执行步骤S8031或步骤S8032或步骤S8033以及步骤S804-S808；否则，执行步骤S809。
参见步骤S202。
需要说明的是，步骤S802可以作为可选的步骤，本申请实施例也可以不执行步骤S802，直接执行步骤S8031或步骤S8032或步骤S8033以及步骤S804-S808。
在一种可能的实施场景中，第二群组连接解除请求消息中包括群组绑定关系标识信息，执行步骤S8031。
在另一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，执行步骤S8032。
在又一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识，执行步骤S8033。
步骤S8031，第一通信系统的群组管理服务器解除群组绑定关系标识指示的绑定关系。
第一通信系统的群组管理服务器解除之前建立的由群组绑定关系标识指示的绑定关系。当仅允许每个群组有一个群组绑定关系时，群组绑定关系标识可以是绑定关系中的任意一个群组标识。
步骤S8032，第一通信系统的群组管理服务器解除绑定关系标识信息所指示的目标绑定关系中目标群组与其他群组之间的绑定关系。
第一通信系统的群组管理服务器解除的是目标群组在目标绑定关系中与其他群组的绑定关系。例如，目标群组A包括两个绑定关系，分别为群组绑定关系一：A与B绑定，群组绑定关系二：A、C与D绑定，假设绑定关系标识信息为群组绑定关系二的标识(如<A,C,D>,或者编号2)，那么第一通信系统的群组管理服务器解除的就是目标群组A与群组C和群组D的绑定关系，但是群组C和群组D的绑定关系依然存在。如果目标绑定关系中仅包两个群组：即目标群组和另外一个群组，则第一通信系统的群组管理服务器解除的是目标群组在目标绑定关系中与其他群组的绑定关系后，该绑定关系也无法成立，系统互通实体删除该绑定关系。
步骤S8033，第一通信系统的群组管理服务器解除所有包含目标群组标识的绑定关系中目标群组与其他群组的绑定关系。
例如，目标群组A包括两个绑定关系，分别为群组绑定关系一：A与B绑定，群组绑定关系二：A、C与D绑定。第一通信系统的群组管理服务器分别解除目标群组标识在两个绑定关系与其他群组的绑定关系。如果目标绑定关系中仅包两个群组：即目标群组和另外一个群组，则第一通信系统的群组管理服务器解除的是目标群组在目标绑定关系中与其他群组的绑定关系后，该绑定关系也无法成立，第一通信系统的群组管理服务器删除该绑定关系。在上述实例中，绑定关系一在B的绑定关系解除后，也被系统互通实体删除。
步骤S804，第一通信系统的群组管理服务器向系统互通实体发送第一群组连接解除通知消息。
第一群组连接解除通知消息可以包括目标群组的标识，或者，目标群组的标识和目标群组的绑定关系标识信息，根据群组连接解除请求消息携带的内容确定。第一群组连接解除通知消息用于通知系统互通实体目标群组的绑定关系已解除。
步骤S805，系统互通实体删除目标群组的绑定关系信息。
系统互通实体将之前保存的目标群组的绑定关系信息删除。具体可以根据群组连接解除请求消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
当目标群组为第一群组时，执行步骤S8061；当目标群组为第二群组时，执行步骤S8062。
步骤S8061，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送第四指示消息。
第四指示消息用于通知第一通信系统的群组管理客户端目标群组的绑定关系已解除。具体来说，第四指示消息可以为群组连接解除响应消息，从而第一通信系统的群组管理客户端知道自身请求的目标群组的群组连接解除请求已经被响应。
步骤S8062，系统互通实体向第二通信系统的第二业务控制实体发送第五指示消息。
第五指示消息用于通知第二通信系统的第二业务控制实体目标群组的绑定关系已解除。具体来说，第五指示消息可以包括目标群组的标识，也可以包括目标群组的标识以及目标群组的绑定关系标识信息，根据群组连接解除请求消息来确定。
进一步的，步骤S8031或步骤S8032之后，还可以执行步骤S807-S808：
步骤S807，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送第二群组连接解除通知消息。
第二群组连接解除通知消息可以包括目标群组的标识，或者，目标群组的标识和目标群组的绑定关系标识信息，根据群组连接解除请求消息携带的内容确定。第二群组连接解除通知消息用于通知第一通信系统的第一业务控制实体目标群组的绑定关系已解除。
步骤S808，第一通信系统的第一业务控制实体删除目标群组的绑定关系信息。
第一通信系统的第一业务控制实体将之前增加的目标群组的绑定关系信息删除。具体可以根据第二群组连接解除通知消息携带的内容，删除目标群组的所有绑定关系信息，或者，删除目标群组在目标绑定关系中与其他群组的绑定关系信息。
步骤S809，第一通信系统的群组管理服务器向第一通信系统的群组管理客户端发送群组连接解除响应消息，指示群组绑定关系解除失败。
参见步骤S210。
参见图6a，本申请实施例提供了另一种群组连接方法。该方法包括但不限于以下步骤。
步骤S901，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第一群组连接请求消息。
步骤S902，第一通信系统的第一业务控制实体检查第一通信系统的业务客户端是否具备请求第一群组与第二群组建立绑定关系的权限。若具备请求第一群组与第二群组建立绑定关系的权限，则执行步骤S903-S910；否则，执行步骤S911。
需要说明的是，步骤S902可以作为可选的步骤，本申请实施例也可以不执行步骤S902，直接执行步骤S903-S910。
步骤S903，第一通信系统的第一业务控制实体向第一通信系统的群组管理服务器发送第二群组连接请求消息。
参见步骤S301-S303。
步骤S904，第一通信系统的群组管理服务器建立第一群组与第二群组的绑定关系。
参见步骤S703。
步骤S905，第一通信系统的群组管理服务器向系统互通实体发送第三指示消息。
参见步骤S704。
步骤S905后进一步执行步骤S906和S907：
步骤S906，系统互通实体保存第一群组与第二群组的绑定关系。
步骤S907，系统互通实体向第二通信系统的第二业务控制实体发送第二指示消息。
参见步骤S705-S706。
需要说明的是，步骤S906和步骤S907之间没有必然的执行先后顺序，可以根据情况进行调整。
步骤S908，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送第一指示消息。
在一种可能的实施场景中，第一指示消息可以为群组连接响应消息，用于通知第一通信系统的第一业务控制实体第一群组的绑定关系已建立。系统互通实体通过消息名称即可确定第一群组的绑定关系已建立。
在另一种可能的实施场景中，第一指示消息可以包括第一群组的绑定关系信息，绑定关系信息可以为绑定关系指示。绑定关系指示用于指示第一群组的绑定关系已建立，例如绑定关系指示可以是第一指示消息中的一个保留比特位置1，也可以是新增的一个比特位置0，用于指示第一群组绑定关系的建立。
在又一种可能的实施场景中，第一指示消息中的第一群组的绑定关系信息也可以包括绑定关系指示和绑定关系标识信息。其中，绑定关系标识信息可以是第一群组的标识与第二群组的标识组成的标识，也可以是绑定关系中任意一个群组的群组标识，还可以是新建的用于表示第一群组与第二群组的绑定关系的标识。从而第一指示消息可以指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关 系。
进一步可选的，第一指示消息中还可以携带与第一群组建立绑定关系的其他群组的标识。
进一步的，第一指示消息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
步骤S909，第一通信系统的第一业务控制实体增加第一群组的绑定关系信息。
第一通信系统的群组管理服务器为第一群组增加相应的绑定关系信息。具体来说，绑定关系信息是根据第一指示消息确定的。绑定关系信息可以指第一群组被绑定的绑定关系指示，也可以还包括绑定关系标识信息，指示第一群组的绑定关系已建立，并且绑定关系标识信息唯一指示第一群组与第二群组建立的绑定关系。进一步的，绑定关系信息还可以包括第一群组的群组角色，也可以包括第一群组和第二群组分别的群组角色。
步骤S910，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立成功。
第一通信系统的第一业务控制实体接收到群组管理服务器发送的第一指示消息后可以确定绑定关系建立成功，从而向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立成功。
步骤S911，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接响应消息，指示群组绑定关系建立失败。
参见步骤S314。
参见图6b，本申请实施例提供了另一种群组连接解除方法。该方法与图6a所示的群组连接方法是对应的，可以在图6a所示的实施例之后实施本方案。该方法包括但不限于以下步骤。
步骤S1001，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第一群组连接解除请求消息。
步骤S1002，第一通信系统的第一业务控制实体检查第一通信系统的业务客户端是否具备请求目标群组解除绑定关系的权限。若具备请求目标群组解除绑定关系的权限，则执行步骤S1003-S1009；否则，执行步骤S1010。
需要说明的是，步骤S1002可以作为可选的步骤，本申请实施例也可以不执行步骤S1002，直接执行步骤S1003-S1009。
步骤S1003，第一通信系统的第一业务控制实体向第一通信系统的群组管理服务器发送第二群组连接解除请求消息。
参见步骤S401-S403。
在一种可能的实施场景中，第二群组连接解除请求消息中包括群组绑定关系标识信息，执行步骤S10041。
在另一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识和目标群组的绑定关系标识信息，执行步骤S10042。
在又一种可能的实施场景中，第二群组连接解除请求消息中包括目标群组的标识，执 行步骤S10043。
步骤S10041，第一通信系统的群组管理服务器解除群组绑定关系标识指示的绑定关系。
步骤S10042，第一通信系统的群组管理服务器解除绑定关系标识信息所指示的目标绑定关系中目标群组与其他群组之间的绑定关系。
步骤S10043，第一通信系统的群组管理服务器解除所有包含目标群组标识的绑定关系中目标群组与其他群组的绑定关系。
参见步骤S8031-S8033。
步骤S1005，第一通信系统的群组管理服务器向系统互通实体发送群组连接解除通知消息。
群组连接解除通知消息可以包括目标群组的标识，或者，目标群组的标识和目标群组的绑定关系标识信息，根据群组连接解除请求消息携带的内容确定。群组连接解除通知消息用于通知系统互通实体目标群组的绑定关系已解除。
步骤S1006，系统互通实体删除目标群组的绑定关系信息。
参见步骤S805。
当目标群组为第一群组时，执行步骤S10071；当目标群组为第二群组时，执行步骤S10072。
步骤S10071，第一通信系统的群组管理服务器向第一通信系统的第一业务控制实体发送第四指示消息。
第四指示消息用于通知第一通信系统的第一业务控制实体目标群组的绑定关系已解除。具体来说，第四指示消息可以为群组连接解除响应消息，从而第一通信系统的第一业务控制实体知道自身请求的目标群组的第二群组连接解除请求已经被响应。
步骤S10072，系统互通实体向第二通信系统的第二业务控制实体发送第五指示消息。
五指示消息用于通知第二通信系统的第二业务控制实体目标群组的绑定关系已解除。具体来说，第五指示消息可以包括目标群组的标识，也可以包括目标群组的标识以及目标群组的绑定关系标识信息，根据第一群组连接解除请求消息来确定。
进一步的，步骤S10071之后，还可以执行步骤S1008-S1009：
步骤S1008，第一通信系统的第一业务控制实体删除目标群组的绑定关系信息。
步骤S1009，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接解除响应消息，指示群组绑定关系解除成功。
参见步骤S409-S410。
步骤S1010，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组连接解除响应消息，指示群组绑定关系解除失败。
参见步骤S411。
参见图7a，本申请实施例提供了一种群组呼叫方法。图7a所示的实施例可以基于图2a-图6b所示的任一种群组连接方法之后实施，适用于群组的绑定关系建立以后，对具有绑定关系的群组进行呼叫时的情景。该方法包括但不限于以下步骤。
步骤S1101，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第一群组呼叫请求消息。
第一群组呼叫请求消息中包括第一群组的标识，第一群组呼叫请求消息用于指示第一通信系统的第一业务控制实体呼叫第一群组以及与第一群组具有绑定关系的其他群组。
步骤S1102，当第一群组具有绑定关系时，第一通信系统的第一业务控制实体向系统互通实体发送第二群组呼叫请求消息。
具体可以包括：
步骤S11021，第一通信系统的第一业务控制实体检查第一群组是否具有绑定关系。当第一群组具有绑定关系时执行步骤S11022。
根据上述实施例可以看出，如果第一群组已经建立了绑定关系，那么第一通信系统的第一业务控制实体中可以保存有第一群组的绑定关系信息，从而根据绑定关系信息指示第一群组具有绑定关系。进一步的，若第一通信系统的第一业务控制实体中未保存第一群组的绑定关系信息，那么第一通信系统的第一业务控制实体还可以向第一通信系统的群组管理服务器获取第一群组的绑定关系信息，从而根据绑定关系信息检查第一群组是否具有绑定关系。当绑定关系信息指示第一群组具有绑定关系时，执行步骤S1103-S1105。
进一步的，若查询到绑定关系信息中包括第一群组的群组角色，且群组角色为主控角色，则第一通信系统的第一业务控制实体在通信建立过程中担任主控角色。向系统控制实体发送呼叫请求，要求系统互通实体呼叫第二群组加入通信中。
步骤S11022，第一通信系统的第一业务控制实体向系统互通实体发送第二群组呼叫请求消息。
第二群组呼叫请求消息携带第一群组的标识，第二群组呼叫请求消息用于请求将与群组之间具有绑定关系的第二群组加入群组通信。
步骤S1103，系统互通实体查找与第一群组的标识具有绑定关系的第二群组的标识。
系统互通实体在接收到第二群组呼叫请求消息后，就在预先获取到的多个绑定关系中查找与第一群组的标识具有绑定关系的第二群组的标识。例如预先存在表1所示的绑定关系表，假设第二群组呼叫请求消息中的第一群组的标识为1-12，那么可以查询得到与1-12群组具有绑定关系的第二群组的标识为2-02。
步骤S1104，系统互通实体向第二通信系统的第二业务控制实体发送第三群组呼叫请求消息。
第三群组呼叫请求消息携带第二群组的标识，第三群组呼叫请求消息用于指示第二业务控制实体将第二群组加入与第一群组的群组通信中。具体来说，第二业务控制实体在接收到第三群组呼叫请求消息之后，就可以呼叫第二群组的所有成员。事实上，步骤S1102之后，第一通信系统的第一业务控制实体也会呼叫第一群组的所有成员，从而第二业务控制实体可以将第二群组的所有成员加入与第一群组的所有成员的群组通信中。
进一步地，步骤S1104之后，还可以执行：
步骤S1105，系统互通实体向第一通信系统的第一业务控制实体发送群组呼叫响应消息。
步骤S1106，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群 组呼叫响应消息。
群组呼叫响应消息用于通知第一通信系统的第一业务控制实体以及第一通信系统的业务客户端，当前已经成功呼叫第二群组，群组通信已建立。若群组绑定关系中包含第一群组的角色信息，因此此时第一群组对应的第一通信系统的第一业务控制实体执行群组通信的主控功能，进一步的，第一通信系统的第一业务控制实体可以控制群组通信的媒体控制。
参见图7b，本申请实施例提供了另一种群组呼叫方法。图7b所示的实施例可以基于图2a-图6b所示的任一种群组连接方法之后实施，适用于群组的绑定关系建立以后，对具有绑定关系的群组进行呼叫时的情景。该方法包括但不限于以下步骤。
步骤S1201，第一通信系统的业务客户端向第一通信系统的第一业务控制实体发送第一群组呼叫请求消息。
第一群组呼叫请求消息中包括第一群组的标识，第一群组呼叫请求消息用于指示第一通信系统的第一业务控制实体呼叫第一群组以及与第一群组具有绑定关系的其他群组。
步骤S1202，当第一群组具有绑定关系时，第一通信系统的第一业务控制实体查找与第一群组的标识具有绑定关系的第二群组的标识。
当第一通信系统的第一业务控制实体确定第一群组具有绑定关系，那么查找与第一群组的标识具有绑定关系的第二群组的标识。具体可以包括：
步骤S12021，第一通信系统的第一业务控制实体检查第一群组是否具有绑定关系。当第一群组具有绑定关系时执行步骤S12022。
根据上述实施例可以看出，如果第一群组已经建立了绑定关系，那么第一通信系统的第一业务控制实体中可以保存有第一群组的绑定关系信息，从而根据绑定关系信息指示第一群组具有绑定关系。进一步的，若第一通信系统的第一业务控制实体中未保存第一群组的绑定关系信息，那么第一通信系统的第一业务控制实体还可以向第一通信系统的群组管理服务器获取第一群组的绑定关系信息，从而根据绑定关系信息检查第一群组是否具有绑定关系。
进一步的，若查询到绑定关系信息中包括第一群组的群组角色，且群组角色为主控角色，则第一通信系统的第一业务控制实体在通信建立过程中担任主控角色。向系统控制实体发送呼叫请求，要求系统互通实体呼叫第二群组加入通信中。
步骤S12022，第一通信系统的第一业务控制实体查找与第一群组的标识具有绑定关系的第二群组的标识。
第一通信系统的第一业务控制实体在接收到第二群组呼叫请求消息后，就在预先获取到的多个绑定关系中查找与第一群组的标识具有绑定关系的第二群组的标识。例如预先存在表1所示的绑定关系表，假设第二群组呼叫请求消息中的第一群组的标识为1-12，那么可以查询得到与1-12群组具有绑定关系的第二群组的标识为2-02。
步骤S1203，第一通信系统的第一业务控制实体向系统互通实体发送第二群组呼叫请求消息。
第二群组呼叫请求消息携带第二群组的标识，第二群组呼叫请求消息用于请求将与群 组之间具有绑定关系的第二群组加入群组通信。
步骤S1204，系统互通实体向第二通信系统的第二业务控制实体发送第三群组呼叫请求消息。
第三群组呼叫请求消息携带第二群组的标识，第三群组呼叫请求消息用于指示第二业务控制实体将第二群组加入与第一群组的群组通信中。具体来说，第二业务控制实体在接收到第三群组呼叫请求消息之后，就可以呼叫第二群组的所有成员。事实上，步骤S1202之后，第一通信系统的第一业务控制实体也会呼叫第一群组的所有成员，从而第二业务控制实体可以将第二群组的所有成员加入与第一群组的所有成员的群组通信中。
进一步地，步骤S1204之后，还可以执行：
步骤S1205，系统互通实体向第一通信系统的第一业务控制实体发送群组呼叫响应消息。
步骤S1206，第一通信系统的第一业务控制实体向第一通信系统的业务客户端发送群组呼叫响应消息。
群组呼叫响应消息用于通知第一通信系统的第一业务控制实体以及第一通信系统的业务客户端，当前已经成功呼叫第二群组，群组通信已建立。若群组绑定关系中包含第一群组的角色信息，因此此时第一群组对应的第一通信系统的第一业务控制实体执行群组通信的主控功能，进一步的，第一通信系统的第一业务控制实体可以控制群组通信的媒体控制。
请参阅图8a，图8a是本申请实施例提供的一种群组连接装置的结构示意图。该群组连接装置可以用于第一通信系统的群组管理服务器或者系统互通实体实现上述图2a-6b实施例。如图8a所示，该群组连接装置包括：
接收模块11，用于接收来自第一通信系统的第一设备的群组连接请求消息，所述群组连接请求消息中包括所述第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，所述第一通信系统与所述第二通信系统基于不同的接入技术；
处理模块12，用于建立所述第一群组与所述第二群组的绑定关系；
发送模块13，用于向所述第一设备发送第一指示消息，所述第一指示消息用于通知所述第一群组的绑定关系已建立。
可选的，所述发送模块13还用于：
向所述第二通信系统的第二业务控制实体发送第二指示消息，所述第二指示消息用于通知所述第二群组的绑定关系已建立。
可选的，所述建立所述第一群组与所述第二群组的绑定关系之前，所述发送模块133还用于：
向所述第二通信系统的授权检查实体发送授权指示消息，所述授权指示消息携带所述第二群组的标识；
所述接收模块11还用于：
接收来自所述授权检查实体的授权成功响应消息，所述授权成功响应消息用于指示所述第二通信系统允许所述第二群组建立绑定关系。
可选的，所述处理模块12具体用于：
当所述第一设备具备请求所述第一群组与所述第二群组建立绑定关系的权限时，建立所述第一群组与所述第二群组的绑定关系。
可选的，所述发送模块13还用于：
向系统互通实体发送第三指示消息，所述第三指示消息包括所述第一群组的标识和所述第二群组的标识，所述第三指示消息用于通知所述第一群组与所述第二群组的绑定关系已建立。
可选的，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；
所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
所述第三指示消息还包括所述第一群组和所述第二群组分别对应的群组角色。
可选的，所述第一指示消息包括所述第一群组的绑定关系信息；
其中，所述绑定关系信息包括绑定关系指示，或，所述绑定关系信息包括绑定关系指示和所述第二群组的标识。
可选的，所述群组连接请求消息还包括所述第一群组的群组角色信息和所述第二群组的群组角色；
所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
所述第一指示消息还包括所述第一群组的群组角色。
可选的，所述接收模块11还用于：接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识，所述目标群组为所述第一群组或所述第二群组；
所述处理模块12还用于：解除所述目标群组的绑定关系。
可选的，所述接收模块11还用于：接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识和所述目标群组的绑定关系标识信息，所述目标群组为所述第一群组或所述第二群组；
所述处理模块12还用于：解除所述绑定关系标识信息所指示的目标绑定关系中所述目标群组与其他群组之间的绑定关系。
可选的，所述发送模块13还用于：
当所述目标群组为所述第一群组时，向所述第一通信系统的第一设备发送第四指示消息，所述第四指示消息用于通知所述目标群组的绑定关系已解除；或者，
当所述目标群组为所述第二群组时，向所述第二通信系统的第二业务控制实体发送第五指示消息，所述第五指示消息用于通知所述目标群组的绑定关系已解除。
可选的，所述第一设备包括所述第一通信系统的群组管理客户端GMC或所述第一通信系统的业务客户端或所述第一通信系统的群组管理服务器GMS或所述第一通信系统的所述第一业务控制实体。
可选的，所述向所述第一设备发送第一指示消息之后，所述接收模块11还用于：
接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识；
所述发送模块13还用于：
当所述第一群组与所述第二群组具有绑定关系时，向所述第二通信系统的第二业务控 制实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第二群组的标识，所述第二群组呼叫请求消息用于指示所述第二业务控制实体将所述第二群组加入与所述第一群组的群组通信中。
请参阅图8b，图8b是本申请实施例提供的另一种群组连接装置的结构示意图。如图8b所示，该群组连接装置包括处理器21、存储器22以及通信接口23。处理器21连接到存储器22和通信接口23，例如处理器21可以通过总线连接到存储器22和通信接口23。具体来说该群组连接装置可以为第一通信系统的群组管理服务器，也可以为系统互通实体。
处理器21被配置为支持所述群组连接装置执行图2a-图6b所述方法中相应的功能。该处理器21可以是中央处理器(英文：central processing unit，CPU)，网络处理器(英文：network processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，ASIC)，可编程逻辑器件(英文：programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，FPGA)，通用阵列逻辑(英文：generic array logic,GAL)或其任意组合。
存储器22存储器用于存储程序代码等。存储器22可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random access memory，缩写：RAM)；存储器22也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器72还可以包括上述种类的存储器的组合。
通信接口23用于与本申请实施例中的各网络设备、终端或实体进行通信以收发上述方法中所涉及的消息或媒体流。
处理器21可以调用所述程序代码以执行以下操作：
接收来自第一通信系统的第一设备的群组连接请求消息，所述群组连接请求消息中包括所述第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，所述第一通信系统与所述第二通信系统基于不同的接入技术；
建立所述第一群组与所述第二群组的绑定关系；
向所述第一设备发送第一指示消息，所述第一指示消息用于通知所述第一群组的绑定关系已建立。
可选的，处理器21还用于：
向所述第二通信系统的第二业务控制实体发送第二指示消息，所述第二指示消息用于通知所述第二群组的绑定关系已建立。
可选的，处理器21建立所述第一群组与所述第二群组的绑定关系之前，还用于：
向所述第二通信系统的授权检查实体发送授权指示消息，所述授权指示消息携带所述第二群组的标识；
处理器21建立所述第一群组与所述第二群组的绑定关系时具体用于：
接收来自所述授权检查实体的授权成功响应消息，所述授权成功响应消息用于指示所述第二通信系统允许所述第二群组建立绑定关系。
可选的，处理器21建立所述第一群组与所述第二群组的绑定关系时具体用于：
当所述第一设备具备请求所述第一群组与所述第二群组建立绑定关系的权限时，建立所述第一群组与所述第二群组的绑定关系。
可选的，处理器21还用于：
向系统互通实体发送第三指示消息，所述第三指示消息包括所述第一群组的标识和所述第二群组的标识，所述第三指示消息用于通知所述第一群组与所述第二群组的绑定关系已建立。
可选的，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；
所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
所述第三指示消息还包括所述第一群组和所述第二群组分别对应的群组角色。
可选的，所述第一指示消息包括所述第一群组的绑定关系信息；
其中，所述绑定关系信息包括绑定关系指示，或，所述绑定关系信息包括绑定关系指示和所述第二群组的标识。
可选的，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；
所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
所述第一指示消息还包括所述第一群组的群组角色。
可选的，处理器21还用于：
接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识，所述目标群组为所述第一群组或所述第二群组；
解除所述目标群组的绑定关系。
可选的，处理器21还用于：
接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识和所述目标群组的绑定关系标识信息，所述目标群组为所述第一群组或所述第二群组；
解除所述绑定关系标识信息所指示的目标绑定关系中所述目标群组与其他群组之间的绑定关系。
可选的，处理器21还用于：
当所述目标群组为所述第一群组时，向所述第一通信系统的第一设备发送第四指示消息，所述第四指示消息用于通知所述目标群组的绑定关系已解除；或者，
当所述目标群组为所述第二群组时，向所述第二通信系统的第二业务控制实体发送第五指示消息，所述第五指示消息用于通知所述目标群组的绑定关系已解除。
可选的，所述第一设备包括所述第一通信系统的群组管理客户端GMC或所述第一通信系统的业务客户端或所述第一通信系统的群组管理服务器GMS或所述第一通信系统的所述第一业务控制实体。
可选的，所述向所述第一设备发送第一指示消息之后，处理器21还用于：
接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识；
当所述第一群组与所述第二群组具有绑定关系时，向所述第二通信系统的第二业务控制实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第二群组的标识，所述第二群组呼叫请求消息用于指示所述第二业务控制实体将所述第二群组加入与所述第一群组的群组通信中。
请参阅图9a，图9a是本申请实施例提供的另一种群组呼叫装置的结构示意图。该群组连接装置可以用于第一通信系统的群组管理服务器或者第一通信系统的第一业务控制实体实现上述图2a-6b实施例。如图9a所示，该群组连接装置包括：
接收模块31，用于接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识；
发送模块32，用于当所述群组具有绑定关系时，向系统互通实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第一群组的标识，所述第二群组呼叫请求消息用于请求将与所述第一群组之间具有绑定关系的第二群组加入群组通信。
请参阅图9b，图9b是本申请实施例提供的另一种群组呼叫装置的结构示意图。如图9b所示，该群组连接装置包括处理器41、存储器42以及通信接口43。处理器41连接到存储器42和通信接口43，例如处理器41可以通过总线连接到存储器42和通信接口43。具体来说该群组连接装置可以为第一通信系统的第一业务控制实体，也可以为第一通信系统的群组管理服务器。
处理器41被配置为支持所述群组连接装置执行图7a-图7b所述方法中相应的功能。该处理器41可以是中央处理器(英文：central processing unit，CPU)，网络处理器(英文：network processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，ASIC)，可编程逻辑器件(英文：programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，FPGA)，通用阵列逻辑(英文：generic array logic,GAL)或其任意组合。
存储器42存储器用于存储程序代码等。存储器42可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random access memory，缩写：RAM)；存储器42也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器72还可以包括上述种类的存储器的组合。
通信接口43用于与本申请实施例中的各网络设备、终端或实体进行通信以收发上述方法中所涉及的消息或媒体流。
处理器41可以调用所述程序代码以执行以下操作：
接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识；
当所述第一群组具有绑定关系时，向系统互通实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第一群组的标识，所述第二群组呼叫请求消息用于请求将与所述第一群组之间具有绑定关系的第二群组加入群组通信。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所揭露的仅为本申请较佳实施例而已，当然不能以此来限定本申请之权利范围，因此依本申请权利要求所作的等同变化，仍属本申请所涵盖的范围。

Claims (28)

  1. 一种群组连接方法，其特征在于，包括：
    接收来自第一通信系统的第一设备的群组连接请求消息，所述群组连接请求消息中包括所述第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，所述第一通信系统与所述第二通信系统基于不同的接入技术；
    建立所述第一群组与所述第二群组的绑定关系；
    向所述第一设备发送第一指示消息，所述第一指示消息用于通知所述第一群组的绑定关系已建立。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    向所述第二通信系统的第二业务控制实体发送第二指示消息，所述第二指示消息用于通知所述第二群组的绑定关系已建立。
  3. 如权利要求2所述的方法，其特征在于，所述建立所述第一群组与所述第二群组的绑定关系之前，所述方法还包括：
    向所述第二通信系统的授权检查实体发送授权指示消息，所述授权指示消息携带所述第二群组的标识；
    所述建立所述第一群组与所述第二群组的绑定关系，包括：
    接收来自所述授权检查实体的授权成功响应消息，所述授权成功响应消息用于指示所述第二通信系统允许所述第二群组建立绑定关系。
  4. 如权利要求1所述的方法，其特征在于，所述建立所述第一群组与所述第二群组的绑定关系包括：
    当所述第一设备具备请求所述第一群组与所述第二群组建立绑定关系的权限时，建立所述第一群组与所述第二群组的绑定关系。
  5. 如权利要求1或4所述的方法，其特征在于，所述方法还包括：
    向系统互通实体发送第三指示消息，所述第三指示消息包括所述第一群组的标识和所述第二群组的标识，所述第三指示消息用于通知所述第一群组与所述第二群组的绑定关系已建立。
  6. 如权利要求5所述的方法，其特征在于，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；
    所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
    所述第三指示消息还包括所述第一群组和所述第二群组分别对应的群组角色。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述第一指示消息包括所述第一群组的绑定关系信息；
    其中，所述绑定关系信息包括绑定关系指示，或，所述绑定关系信息包括绑定关系指示和所述第二群组的标识。
  8. 如权利要求1-7任一项所述的方法，其特征在于，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；
    所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
    所述第一指示消息还包括所述第一群组的群组角色。
  9. 如权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：
    接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识，所述目标群组为所述第一群组或所述第二群组；
    解除所述目标群组的绑定关系。
  10. 如权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：
    接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识和所述目标群组的绑定关系标识信息，所述目标群组为所述第一群组或所述第二群组；
    解除所述绑定关系标识信息所指示的目标绑定关系中所述目标群组与其他群组之间的绑定关系。
  11. 如权利要求9或10所述的方法，其特征在于，所述方法还包括：
    当所述目标群组为所述第一群组时，向所述第一通信系统的第一设备发送第四指示消息，所述第四指示消息用于通知所述目标群组的绑定关系已解除；或者，
    当所述目标群组为所述第二群组时，向所述第二通信系统的第二业务控制实体发送第五指示消息，所述第五指示消息用于通知所述目标群组的绑定关系已解除。
  12. 如权利要求1-11任一项所述的方法，其特征在于，所述第一设备包括所述第一通信系统的群组管理客户端GMC或所述第一通信系统的业务客户端或所述第一通信系统的群组管理服务器GMS或所述第一通信系统的所述第一业务控制实体。
  13. 如权利要求1-12任一项所述的方法，其特征在于，所述向所述第一设备发送第一指示消息之后，还包括：
    接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识；
    当所述第一群组与所述第二群组具有绑定关系时，向所述第二通信系统的第二业务控制实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第二群组的标识，所述第二群组呼叫请求消息用于指示所述第二业务控制实体将所述第二群组加入与所述第一群组的群组通信中。
  14. 一种群组呼叫方法，其特征在于，所述方法包括：
    接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括第一群组的标识；
    当所述第一群组具有绑定关系时，向系统互通实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息用于请求将与所述第一群组之间具有绑定关系的第二群组加入群组通信。
  15. 一种群组连接装置，其特征在于，包括：
    接收模块，用于接收来自第一通信系统的第一设备的群组连接请求消息，所述群组连接请求消息中包括所述第一通信系统的第一群组的标识和第二通信系统的第二群组的标识，所述第一通信系统与所述第二通信系统基于不同的接入技术；
    处理模块，用于建立所述第一群组与所述第二群组的绑定关系；
    发送模块，用于向所述第一设备发送第一指示消息，所述第一指示消息用于通知所述第一群组的绑定关系已建立。
  16. 如权利要求15所述的装置，其特征在于，所述发送模块还用于：
    向所述第二通信系统的第二业务控制实体发送第二指示消息，所述第二指示消息用于通知所述第二群组的绑定关系已建立。
  17. 如权利要求16所述的装置，其特征在于，所述建立所述第一群组与所述第二群组的绑定关系之前，所述发送模块还用于：
    向所述第二通信系统的授权检查实体发送授权指示消息，所述授权指示消息携带所述第二群组的标识；
    所述接收模块还用于：
    接收来自所述授权检查实体的授权成功响应消息，所述授权成功响应消息用于指示所述第二通信系统允许所述第二群组建立绑定关系。
  18. 如权利要求15所述的装置，其特征在于，所述处理模块具体用于：
    当所述第一设备具备请求所述第一群组与所述第二群组建立绑定关系的权限时，建立所述第一群组与所述第二群组的绑定关系。
  19. 如权利要求15或18所述的装置，其特征在于，所述发送模块还用于：
    向系统互通实体发送第三指示消息，所述第三指示消息包括所述第一群组的标识和所述第二群组的标识，所述第三指示消息用于通知所述第一群组与所述第二群组的绑定关系已建立。
  20. 如权利要求19所述的装置，其特征在于，所述群组连接请求消息还包括所述第一群组的群组角色和所述第二群组的群组角色；
    所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
    所述第三指示消息还包括所述第一群组和所述第二群组分别对应的群组角色。
  21. 如权利要求15-20任一项所述的装置，其特征在于，所述第一指示消息包括所述第一群组的绑定关系信息；
    其中，所述绑定关系信息包括绑定关系指示，或，所述绑定关系信息包括绑定关系指示和所述第二群组的标识。
  22. 如权利要求15-21任一项所述的装置，其特征在于，所述群组连接请求消息还包括所述第一群组的群组角色信息和所述第二群组的群组角色；
    所述绑定关系包括所述第一群组的群组角色和所述第二群组的群组角色；
    所述第一指示消息还包括所述第一群组的群组角色。
  23. 如权利要求15-22任一项所述的装置，其特征在于，
    所述接收模块还用于：接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识，所述目标群组为所述第一群组或所述第二群组；
    所述处理模块还用于：解除所述目标群组的绑定关系。
  24. 如权利要求15-22任一项所述的装置，其特征在于，
    所述接收模块还用于：接收群组连接解除请求消息，所述群组连接解除请求消息中包括目标群组的标识和所述目标群组的绑定关系标识信息，所述目标群组为所述第一群组或所述第二群组；
    所述处理模块还用于：解除所述绑定关系标识信息所指示的目标绑定关系中所述目标群组与其他群组之间的绑定关系。
  25. 如权利要求23或24所述的装置，其特征在于，所述发送模块还用于：
    当所述目标群组为所述第一群组时，向所述第一通信系统的第一设备发送第四指示消息，所述第四指示消息用于通知所述目标群组的绑定关系已解除；或者，
    当所述目标群组为所述第二群组时，向所述第二通信系统的第二业务控制实体发送第五指示消息，所述第五指示消息用于通知所述目标群组的绑定关系已解除。
  26. 如权利要求15-25任一项所述的装置，其特征在于，所述第一设备包括所述第一通信系统的群组管理客户端GMC或所述第一通信系统的业务客户端或所述第一通信系统的群组管理服务器GMS或所述第一通信系统的所述第一业务控制实体。
  27. 如权利要求15-26任一项所述的装置，其特征在于，所述向所述第一设备发送第一指示消息之后，所述接收模块还用于：
    接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识；
    所述发送模块还用于：
    当所述第一群组与所述第二群组具有绑定关系时，向所述第二通信系统的第二业务控制实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息携带所述第二群组的标识，所述第二群组呼叫请求消息用于指示所述第二业务控制实体将所述第二群组加入与所述第一群组的群组通信中。
  28. 一种群组呼叫装置，其特征在于，所述装置包括：
    接收模块，用于接收第一群组呼叫请求消息，所述第一群组呼叫请求消息包括所述第一群组的标识；
    发送模块，用于当所述第一群组具有绑定关系时，向系统互通实体发送第二群组呼叫请求消息，所述第二群组呼叫请求消息用于请求将与所述第一群组之间具有绑定关系的第二群组加入群组通信。
PCT/CN2017/082789 2017-05-02 2017-05-02 群组连接方法及相关设备 WO2018201306A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/082789 WO2018201306A1 (zh) 2017-05-02 2017-05-02 群组连接方法及相关设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/082789 WO2018201306A1 (zh) 2017-05-02 2017-05-02 群组连接方法及相关设备

Publications (1)

Publication Number Publication Date
WO2018201306A1 true WO2018201306A1 (zh) 2018-11-08

Family

ID=64015956

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/082789 WO2018201306A1 (zh) 2017-05-02 2017-05-02 群组连接方法及相关设备

Country Status (1)

Country Link
WO (1) WO2018201306A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1889722A (zh) * 2006-07-20 2007-01-03 华为技术有限公司 一种PoC群组会话的实现方法及装置
CN101729498A (zh) * 2008-10-14 2010-06-09 中兴通讯股份有限公司 基于会话初始协议的用户名协商方法和系统
WO2014125036A1 (en) * 2013-02-13 2014-08-21 Nec Europe Ltd. Method and system for supporting communication with a group of devices via a mobile network
CN104780191A (zh) * 2014-01-13 2015-07-15 腾讯科技（深圳）有限公司 群组信息的获取、共享方法和群组信息的获取、共享装置
WO2016161591A1 (zh) * 2015-04-09 2016-10-13 华为技术有限公司 多群组通话建立方法和设备
CN106255074A (zh) * 2016-07-27 2016-12-21 广东欧珀移动通信有限公司 一种群组建立方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1889722A (zh) * 2006-07-20 2007-01-03 华为技术有限公司 一种PoC群组会话的实现方法及装置
CN101729498A (zh) * 2008-10-14 2010-06-09 中兴通讯股份有限公司 基于会话初始协议的用户名协商方法和系统
WO2014125036A1 (en) * 2013-02-13 2014-08-21 Nec Europe Ltd. Method and system for supporting communication with a group of devices via a mobile network
CN104780191A (zh) * 2014-01-13 2015-07-15 腾讯科技（深圳）有限公司 群组信息的获取、共享方法和群组信息的获取、共享装置
WO2016161591A1 (zh) * 2015-04-09 2016-10-13 华为技术有限公司 多群组通话建立方法和设备
CN106255074A (zh) * 2016-07-27 2016-12-21 广东欧珀移动通信有限公司 一种群组建立方法和装置

Similar Documents

Publication Publication Date Title
EP3005759B1 (en) Access control for wireless docking
US10952036B2 (en) Method for regrouping multiple groups and device
JP6359646B2 (ja) ワイヤレスドッキング環境の利用および構成
CN105453620A (zh) 无线对接架构
AU2015374472B2 (en) Method and apparatus for providing access to local services and applications to multi-agency responders
CN105230056B (zh) 无线对接的方法和装置
KR102051839B1 (ko) M2m 시스템에서 메시지를 처리하는 방법 및 그 장치
WO2015168974A1 (zh) 资源的创建方法及装置
WO2015117362A1 (zh) 终端上个人信息的共享方法及装置
JP5947254B2 (ja) 無線ｌａｎ装置、無線ｌａｎ装置のプログラムおよび無線ｌａｎ装置の制御方法
CN106464666A (zh) 用户与群组关联的方法和设备
WO2015003603A1 (zh) 一种资源迁移的方法、装置
WO2018201306A1 (zh) 群组连接方法及相关设备
WO2021115464A1 (zh) 一种网络切片选择方法及相关装置
EP2891270B1 (en) Method and apparatus for updating personal information in communication system
CN112153580B (zh) 设置mcptt群组的方法、设备及系统
WO2021136301A1 (zh) 通信方法及装置
WO2022067509A1 (zh) 设备升级控制方法、装置、计算机设备及存储介质
WO2022228229A1 (zh) 一种终端信息共享的方法及通信装置
WO2011047587A1 (zh) 闭合用户组成员的管理方法及装置
WO2016187805A1 (zh) 一种数据处理方法及装置
EP2793427A1 (en) Method for managing personal network
JP6223878B2 (ja) 通信システム、通信端末及び端末制御方法
JP2006286011A (ja) 状態情報管理システム及び状態情報管理サーバ
JP2017147582A (ja) 無線通信端末

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17908393

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17908393

Country of ref document: EP

Kind code of ref document: A1