WO2017024470A1 - 变更mcptt用户与mcptt群组关联关系的方法、装置及系统 - Google Patents

变更mcptt用户与mcptt群组关联关系的方法、装置及系统 Download PDF

Info

Publication number
WO2017024470A1
WO2017024470A1 PCT/CN2015/086516 CN2015086516W WO2017024470A1 WO 2017024470 A1 WO2017024470 A1 WO 2017024470A1 CN 2015086516 W CN2015086516 W CN 2015086516W WO 2017024470 A1 WO2017024470 A1 WO 2017024470A1
Authority
WO
WIPO (PCT)
Prior art keywords
mcptt
user
group
association
change
Prior art date
Application number
PCT/CN2015/086516
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
Priority to KR1020187002288A priority Critical patent/KR102005204B1/ko
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to SG11201800035SA priority patent/SG11201800035SA/en
Priority to JP2018506389A priority patent/JP6609690B2/ja
Priority to EP20171897.0A priority patent/EP3780892B1/en
Priority to MYPI2018700076A priority patent/MY193852A/en
Priority to EP15900668.3A priority patent/EP3310108B1/en
Priority to CN202010123485.9A priority patent/CN111432354B/zh
Priority to RU2018107265A priority patent/RU2684574C1/ru
Priority to PCT/CN2015/086516 priority patent/WO2017024470A1/zh
Priority to CN201580024970.8A priority patent/CN107005976B/zh
Publication of WO2017024470A1 publication Critical patent/WO2017024470A1/zh
Priority to US15/892,713 priority patent/US10841750B2/en
Priority to US17/082,696 priority patent/US11617063B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • 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
    • 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/10—Push-to-Talk [PTT] or Push-On-Call services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a method, device, and system for changing an association relationship between an MCPTT user and an MCPTT group.
  • the MCPTT Mobility Critical Push To Talk
  • the user equipment (UE, User Equipment) (the MCPTT user is the user who uses the UE) sends a group association request message to the MCPTT server to request the MCPTT.
  • Groups establish relationships. There is a need in an actual application that an MCPTT user may need a group communication of one (or more) MCPTT users to join an MCPTT group, or terminate the one (or more) MCPTT users in a certain MCPTT. Group communication in the group.
  • some specific MCPTT users for example, authorized senior MCPTT users such as dispatchers, administrators, etc.
  • MCPTT users want a certain MCPTT user to participate in group communication of a certain MCPTT group due to business requirements; therefore, an MCPTT is needed.
  • Users can change the relationship between other MCPTT users and MCPTT groups.
  • the embodiment of the invention provides a method, a device and a system for changing the association relationship between an MCPTT user and an MCPTT group, which are used to solve the problem that the function of one MCPTT user to change the relationship between other MCPTT users and a group is not supported in the prior art.
  • an embodiment of the present invention provides a method for changing an emergency task, that is, a relationship between an MCPTT user and an MCPTT group, including:
  • an association change request sent by the first user equipment UE where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests the change An association relationship between the two MCPTT users and the first MCPTT group; the first MCPTT user is an MCPTT user that uses the first UE;
  • the first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is An MCPTT server; the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used for Instructing to request the second MCPTT user to associate or de-associate with the first MCPTT group.
  • the request information includes:
  • a user identifier of the second MCPTT user and a group identifier of the first MCPTT group or a group identifier of the second MCPTT group to which the second MCPTT user belongs and the first MCPTT group Group ID.
  • the first network element device is changed according to the association, in combination with the first aspect or the third aspect of the first aspect,
  • the request, before setting the association relationship between the first MCPTT user and the first MCPTT group further includes:
  • the first network element device determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • the first network element device is changed according to the association
  • the request, before setting the association relationship between the first MCPTT user and the first MCPTT group further includes:
  • the first network element device according to the association change request, setting an association relationship between the second MCPTT user and the first MCPTT group, including:
  • the first network element device sets the association relationship between the second MCPTT user and the first MCPTT group as a target association relationship according to the association change request; the target association relationship is the first network element The device is determined according to the association change request.
  • the method further includes:
  • Determining, by the first network element device, that the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be set according to the group policy of the first MCPTT group.
  • the target relationship
  • the first network element device receives the association change request sent by the first UE, including:
  • the second network element device is a second MCPTT server or a third MCPTT server;
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user;
  • the MCPTT server is an MCPTT server in the MCPTT system that defines the user profile of the second MCPTT user.
  • the first network element device according to the association change request, the second MCPTT user and the The association relationship of the first MCPTT group is set as a target association relationship, including:
  • the first network element device stores the target association relationship between the second MCPTT user and the first MCPTT group
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is a target association relationship, and the second MCPTT user is to use the second UE. MCPTT users.
  • the method further includes:
  • the first network element device sends a change message to the second UE, where the change message is used to request the second MCPTT user to set the association relationship between the second MCPTT user and the first MCPTT group as The target association relationship; the second MCPTT user is an MCPTT user using the second UE;
  • the first network element device according to the association change request, the second MCPTT user
  • the association relationship of the first MCPTT group is set to the target association relationship, including:
  • the first network element device stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • the first network element device according to the association change request, The association relationship between the second MCPTT user and the first MCPTT group is set to the target association relationship, including:
  • the first network element device sends a change message to the second UE, where the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship;
  • the second MCPTT user is an MCPTT user who uses the second UE;
  • the first network element device stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • the first network element device sends a change message to the second UE ,include:
  • the first network element device defines a user profile of the second MCPTT user by using The MCPTT server in the MCPTT system sends the change message to the second UE.
  • the first network element device is configured according to the association change request, After the association relationship between the second MCPTT user and the first MCPTT group is set to the target association relationship, the method further includes:
  • the first network element device sends an association change response to the first UE.
  • the change message includes: a user of the first MCPTT user Logo.
  • the association change request further includes: a user identifier of the first MCPTT user.
  • an embodiment of the present invention provides a method for changing an emergency task, that is, a relationship between an MCPTT user and an MCPTT group, including:
  • the second network element device receives the association change request sent by the first user equipment UE;
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group.
  • An association relationship ; the first MCPTT user is an MCPTT user using the first UE;
  • the second network element device sends a change message to the second UE, where the change message is used to request the second MCPTT user to set the association relationship between the second MCPTT user and the first MCPTT group as a target association. a relationship; the second MCPTT user is an MCPTT user using the second UE;
  • the second network element device receives the change response sent by the second UE, and the change response is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is allowed to be set as the target association. relationship;
  • the second network element device sends the association change request to the first network element device.
  • the second network element device is a second MCPTT server or a third MCPTT server
  • the second MCPTT server is configured to define the first MCPTT The MCPTT server in the MCPTT system of the user profile of the user
  • the third MCPTT server is a user profile defining the second MCPTT user The MCPTT server in the MCPTT system.
  • the first network element device is a group management server of the first MCPTT group.
  • the first network element device is a first MCPTT server; and the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • an embodiment of the present invention provides a method for changing an emergency task, that is, a relationship between an MCPTT user and an MCPTT group, including:
  • the first user equipment UE sends an association change request to the first network element device, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association between the second MCPTT user and the first MCPTT group. a relationship, wherein the first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request; the first MCPTT user is a user using the first UE;
  • the first UE receives an association change response sent by the first network element device.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is defined MCPTT server in the MCPTT system of the first MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used for Instructing to request the second MCPTT user to associate or de-associate with the first MCPTT group.
  • the request information includes:
  • a user identifier of the second MCPTT user and a group identifier of the first MCPTT group or a group identifier of the second MCPTT group to which the second MCPTT user belongs and the first MCPTT group Group ID.
  • the association change request further includes: User ID of an MCPTT user.
  • the embodiment of the present invention provides a device for changing an emergency task, that is, a MCPTT user and an MCPTT group.
  • the device is a first network element device, and the device includes:
  • a receiving module configured to receive an association change request sent by the first user equipment UE, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group.
  • An association relationship the first MCPTT user is an MCPTT user using the first UE;
  • a setting module configured to set an association relationship between the second MCPTT user and the first MCPTT group according to the association change request.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is An MCPTT server; the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used for Instructing to request the second MCPTT user to associate or de-associate with the first MCPTT group.
  • the request information includes:
  • a user identifier of the second MCPTT user and a group identifier of the first MCPTT group or a group identifier of the second MCPTT group to which the second MCPTT user belongs and the first MCPTT group Group ID.
  • the setting module is further configured to:
  • the setting module is further configured to:
  • the setting module is configured according to the association change request
  • the association relationship between the second MCPTT user and the first MCPTT group includes:
  • the setting module is further configured to:
  • the receiving module is specifically configured to:
  • the second network element device is a second MCPTT server or a third MCPTT server;
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user;
  • the MCPTT server is an MCPTT server in the MCPTT system that defines the user profile of the second MCPTT user.
  • the device further includes: a sending module
  • the setting module sets the association relationship between the second MCPTT user and the first MCPTT group as a target association relationship according to the association change request, which specifically includes:
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is a target association relationship; and the second MCPTT user is an MCPTT user that uses the second UE.
  • the device further includes: a sending module
  • the setting module is further configured to:
  • the setting module according to the association change request, the second MCPTT user and the first An association relationship of an MCPTT group is set to the target association relationship, and specifically includes:
  • the device further includes: a sending module
  • the setting module is configured to set the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship according to the association change request, which specifically includes:
  • the sending module Sending, by the sending module, a change message to the second UE, where the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship;
  • the MCPTT user is an MCPTT user who uses the second UE;
  • the sending module sends a change message to the second UE, specifically including :
  • the change message is sent to the second UE by an MCPTT server in an MCPTT system that defines a user profile of the second MCPTT user.
  • the sending module is further configured to:
  • the change message includes: a user identifier of the first MCPTT user.
  • the association change request further includes: a user identifier of the first MCPTT user.
  • the embodiment of the present invention provides a device for changing an emergency task, that is, a MCPTT user and an MCPTT group, and the device is a second network element device, and the device includes:
  • a receiving module configured to receive an association change request sent by the first user equipment UE, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group.
  • An association relationship the first MCPTT user is an MCPTT user using the first UE;
  • a sending module configured to send a change message to the second UE, where the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as a target association relationship;
  • the second MCPTT user is an MCPTT user using the second UE;
  • the receiving module is further configured to receive a change response sent by the second UE, where the change response is used to indicate that an association relationship between the second MCPTT user and the first MCPTT group is allowed to be set to the target connection relation;
  • the sending module is further configured to send the association change request to the first network element device.
  • the second network element device is a second MCPTT server or a third MCPTT server; and the second MCPTT server is configured to define the first MCPTT The MCPTT server in the MCPTT system of the user profile of the user; the third MCPTT server is the MCPTT server in the MCPTT system that defines the user profile of the second MCPTT user.
  • the first network element device is a group management server of the first MCPTT group
  • the first network element device is a first MCPTT server
  • the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • an embodiment of the present invention provides a device for changing an emergency task, that is, a relationship between an MCPTT user and an MCPTT group, where the device is a first user equipment UE, and the device package include:
  • a sending module configured to send an association change request to the first network element device, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association between the second MCPTT user and the first MCPTT group.
  • the first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request; the first MCPTT user is a user using the first UE;
  • the receiving module is configured to receive an association change response sent by the first network element device.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is defined MCPTT server in the MCPTT system of the first MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used for Instructing to request the second MCPTT user to associate or de-associate with the first MCPTT group.
  • the request information includes:
  • a user identifier of the second MCPTT user and a group identifier of the first MCPTT group or a group identifier of the second MCPTT group to which the second MCPTT user belongs and the first MCPTT group Group ID.
  • the related change request further includes: User ID of an MCPTT user.
  • an embodiment of the present invention provides a system for changing an emergency task, that is, a system for associating an MCPTT user with an MCPTT group, including the first to the sixteenth aspects of the fourth aspect or the fourth aspect.
  • the first network element device and the first user equipment UE according to any one of the sixth to fourth aspects of the sixth aspect.
  • the second network element device of any one of the first to second aspects of the fifth aspect or the fifth aspect is further included.
  • An embodiment of the present invention provides a method, device, and system for changing an association relationship between an MCPTT user and an MCPTT group, and receiving, by using the first network element device, an association change request sent by the first UE;
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group; the first MCPTT user is to use the first UE.
  • a first network element device setting an association relationship between the second MCPTT user and the first MCPTT group; so that the first MCPTT user can change the first MCPTT user and the first MCPTT
  • the association relationship of the group thus, the function of changing the relationship between other MCPTT users and the group by one MCPTT user is realized.
  • Embodiment 1 is a flowchart of Embodiment 1 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 2 is a flowchart of Embodiment 2 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 3 is a flowchart of Embodiment 3 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 4 is a flowchart of Embodiment 4 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 5 is a flowchart of Embodiment 5 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 6 is a flowchart of Embodiment 6 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 7 is a flowchart of Embodiment 7 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 8 is a flowchart of Embodiment 8 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • FIG. 9 is a schematic diagram of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention.
  • Embodiment 10 is a flowchart of Embodiment 10 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 11 is a flowchart of Embodiment 11 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 12 is a flowchart of Embodiment 12 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 13 is a flowchart of Embodiment 13 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 14 is a flowchart of Embodiment 14 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 15 is a schematic structural diagram of Embodiment 1 of an apparatus for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 16 is a schematic structural diagram of Embodiment 2 of an apparatus for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • Embodiment 17 is a schematic structural diagram of Embodiment 3 of an apparatus for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • FIG. 18 is a schematic structural diagram of Embodiment 5 of an apparatus for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention
  • FIG. 19 is a schematic structural diagram of Embodiment 6 of an apparatus for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention.
  • FIG. 1 is a flowchart of Embodiment 1 of a method for changing an association between an MCPTT user and an MCPTT group according to the present invention; as shown in FIG. 1 , the method in this embodiment may include:
  • Step 101 The first network element device receives an association change request sent by the first UE, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • the first MCPTT user is a user who uses the first UE
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is a first MCPTT server; MCPTT server in the MCPTT system of an MCPTT group.
  • the UE in the present invention may be a device that can be operated by any person such as a mobile phone, a computer, a tablet computer, a background controller, or the like.
  • Step 102 The first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request.
  • the first network element device receives the association change request sent by the first UE; the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first An association relationship of the MCPTT group; the first MCPTT user is a user who uses the first UE; and the first network element device sets the second MCPTT user and the first MCPTT according to the association change request
  • the association relationship of the group is such that the first MCPTT user can change the association relationship between the first MCPTT user and the first MCPTT group; thereby implementing the function that one MCPTT user changes the relationship between other MCPTT users and the group.
  • Embodiment 2 is a flowchart of Embodiment 2 of a method for changing an association between an MCPTT user and an MCPTT group according to the present invention; as shown in FIG. 2, the method in this embodiment may include:
  • Step 201 The first UE sends an association change request to the first network element device, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group.
  • An association relationship so that the first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request;
  • the first MCPTT user is a user who uses the first UE
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is a first MCPTT server; MCPTT server in the MCPTT system of an MCPTT group.
  • the MCPTT server is used to implement group session and user registration.
  • the network element device which is a group management server (GMS), is a network element device for managing group policies and maintaining group information.
  • GMS group management server
  • Step 202 The first UE receives an association change response sent by the first network element device.
  • the first UE sends an association change request to the first network element device, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT.
  • An association relationship between the group so that the first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request; so that the first MCPTT user can change the second MCPTT user and the first
  • the association relationship of MCPTT groups thus, the function of one MCPTT user to change the relationship between other MCPTT users and groups is realized.
  • FIG. 3 is a flowchart of a third embodiment of a method for changing an association between an MCPTT user and an MCPTT group according to the present invention
  • the application scenario in this embodiment may be: an MCPTT system that defines a user profile of a first MCPTT user, and defines a second MCPTT user.
  • the MCPTT system of the user profile and the MCPTT system of the first MCPTT group are the same; as shown in FIG. 3, the method in this embodiment may include:
  • Step 301 The first UE sends an association change request to the first MCPTT server, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association between the second MCPTT user and the first MCPTT group. relationship;
  • the first MCPTT user is a user who uses the first UE;
  • the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used to indicate that the second MCPTT user is requested to be associated or de-associated with the first MCPTT group.
  • the request information includes: a user identifier of the second MCPTT user and a group identifier of the first MCPTT group; or a group of a second MCPTT group to which the second MCPTT user belongs A group identifier and a group identifier of the first MCPTT group.
  • the association change request further includes: a user identifier of the first MCPTT user.
  • an association change request in step 301 only the identifier of one target MCPTT user (for example, the second MCPTT user) and the target of the target MCPTT user may be included.
  • An identifier of the MCPTT group (for example, the first MCPTT group); or, an association change request may include a user identifier of the plurality of target MCPTT users (that is, may be a list of user identifiers of a target MCPTT user) and the The identifier of the target MCPTT group of the plurality of target MCPTT users; or an association change request may include the user identifiers of the plurality of target MCPTT users and the identifiers of the same MCPTT group corresponding to the plurality of target MCPTT users.
  • the method may further include:
  • the first UE determines, according to the input of the first MCPTT user, that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group; or the first UE sends the information according to other devices. And determining that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • Step 302 The first MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 303 If yes, go to step 303; otherwise, end, or send an association change response indicating that the change failed to the first UE.
  • the step 302 is specifically: the first MCPTT server determines whether the number of MCPTT groups associated with the second MCPTT user is less than or equal to the threshold;
  • Step 303 The first MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 304 If yes, go to step 304. Otherwise, it ends or sends an association change response indicating that the change has failed to the first UE.
  • the first MCPTT server may pre-store a condition that needs to be met by another MCPTT user (for example, the first MCPTT user) that can change the association relationship of the second MCPTT user; for example, the role assumed by the user needs to be Which roles and user's user priority need to be greater than or equal to the preset priority.
  • another MCPTT user for example, the first MCPTT user
  • the role assumed by the user needs to be Which roles and user's user priority need to be greater than or equal to the preset priority.
  • Step 304 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • the group management server is a group management server of the first MCPTT group.
  • the policy does not need to be performed in step 304 to obtain from the group management server.
  • the group management server may be in the MCPTT system to which the first MCPTT server belongs; or the group management server may be shared by multiple MCPTT systems outside the MCPTT system to which the first MCPTT server belongs.
  • a group management server may be in the MCPTT system to which the first MCPTT server belongs; or the group management server may be shared by multiple MCPTT systems outside the MCPTT system to which the first MCPTT server belongs.
  • Step 305 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 306 If yes, go to step 306; otherwise, end, or send an association change response indicating that the change failed to the first UE.
  • the target association relationship is determined by the first MCPTT server according to the association change request.
  • the first MCPTT server determines the target association relationship according to the association change request, including:
  • the first MCPTT server indicates the association relationship included in the association change request as the target association relationship. For example, when the association relationship is indicated as de-association, the target association relationship is de-association; when the association relationship is indicated as association, the target-related relationship is association.
  • the first MCPTT server determines that the current association relationship between the second MCPTT user and the first MCPTT group is de-association, and the request information included in the association change request indicates that the association between the first MCPTT user and the first MCPTT group is changed.
  • the target relationship is determined to be an association
  • the first MCPTT server determines that the current association relationship between the second MCPTT user and the first MCPTT group is associated, and the request information included in the association change request indicates that the first MCPTT user and the first MCPTT group are changed.
  • the target association is determined to be de-association.
  • the group policy may be a maximum number of users in the group, a lowest user priority of the MCPTT user, and the like.
  • Step 306 The first MCPTT server sends a change message to the second UE.
  • the second MCPTT user is a user who uses the second UE.
  • step 306 may specifically be:
  • the first MCPTT server sends the change message to the second UE by using an MCPTT server in an MCPTT system that defines a user profile of the second MCPTT user.
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship (that is, the target association relationship determined in step 305) or
  • the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship.
  • the method further includes:
  • the change response is used to indicate that an association relationship between the second MCPTT user and the first MCPTT group is allowed to be set as the target association relationship.
  • the change response is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is denied to be set as the target association relationship.
  • the change response is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is denied to be the target association relationship, send an association to indicate that the change is failed to the first UE.
  • the response is changed without performing step 307 and step 308.
  • the change message may include: a user identifier of the first MCPTT user, so that the first MCPTT user may determine an MCPTT user that changes an association relationship between the first MCPTT user and the first MCPTT group. For the first MCPTT user.
  • Step 307 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • step 307 there is no order between step 307 and step 306.
  • the step 307 may further include: the first MCPTT server sends the first association information to the group management server, where the first association information is used to indicate the association between the second MCPTT user and the first MCPTT group.
  • the relationship is the target association relationship, so that the group management server updates the association relationship between the second MCPTT user and the first MCPTT group to the target association relationship.
  • Step 308 The first MCPTT server sends an association change response indicating that the change is successful to the first UE.
  • step 308 there is no order between step 308 and step 307.
  • the first UE sends an association change request to the first MCPTT server.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group.
  • a first MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and the first MCPTT group allows the second MCPTT user to be the first MCPTT After the association relationship of the group is set as the target association relationship, the first MCPTT server sends a change message to the second UE, where the change message is used to indicate the second MCPTT user and the first MCPTT group.
  • the association relationship is the target association relationship; or the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship)
  • the first MCPTT user can change the association relationship between the first MCPTT user and the first MCPTT group; thereby implementing the function of one MCPTT user changing the relationship between other MCPTT users and the group .
  • Embodiment 4 is a flowchart of Embodiment 4 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention.
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 3; as shown in FIG.
  • the methods can include:
  • Step 401 The first UE sends an association change request to the first MCPTT server, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association between the second MCPTT user and the first MCPTT group. relationship;
  • step 401 is similar to step 301, and details are not described herein again.
  • Step 402 The first MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 403 If yes, go to step 403; otherwise, end, or send an association change response indicating that the change failed to the first UE.
  • step 402 is similar to step 302 and will not be further described herein.
  • Step 403 The first MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 404 ends or sends an association change response indicating that the change has failed to the first UE.
  • step 403 is similar to step 303, and details are not described herein again.
  • Step 404 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 404 is similar to step 304, and details are not described herein again.
  • Step 405 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 406 If yes, go to step 406; otherwise, end, or send an association change response indicating that the change failed to the first UE.
  • step 405 is similar to step 305, and details are not described herein again.
  • Step 406 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • Step 407 The first MCPTT server sends an update message to the group management server, where the update message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship.
  • step 407 there is no order between step 407 and step 406.
  • Step 408 After receiving the update message, the group management server sends a change message to the second UE.
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship, and the second MCPTT user is a user that uses the second UE.
  • the step 408 may further include: the group management server storing the target association relationship between the second MCPTT user and the first MCPTT group;
  • step 408 may also be considered as the first MCPTT server.
  • the second UE sends a change message.
  • Step 409 The first MCPTT server sends an association change response indicating that the change is successful to the first UE.
  • step 409 there is no order between step 409 and step 406-step 408.
  • the first UE sends an association change request to the first MCPTT server.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group.
  • a first MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and the first MCPTT group allows the second MCPTT user to be the first MCPTT
  • an update message is sent to the group management server, so that the group management server sends a change message to the second UE (where the change message is used to indicate the second MCPTT user
  • the association relationship with the first MCPTT group is the target association relationship), so that the first MCPTT user can change the association relationship between the first MCPTT user and the first MCPTT group; thereby implementing one MCPTT user to change other MCPTT users.
  • the ability to associate with a group is the target association relationship.
  • the difference between the embodiment shown in FIG. 4 and the embodiment shown in FIG. 3 is mainly as follows: 1) In the embodiment shown in FIG. 3, the first MCPTT server sends a change message to the second UE, as shown in FIG. In the embodiment, the group management server sends a change message to the second UE; 2) the change message in the embodiment shown in FIG. 4 is used to indicate that the relationship between the second MCPTT user and the first MCPTT group is the In the target association relationship, the change message in the embodiment shown in FIG. 3 is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship, or is used to request the second MCPTT user. Setting an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship.
  • FIG. 5 is a flowchart of Embodiment 5 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention.
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 3; as shown in FIG.
  • the methods can include:
  • Step 501 The first UE sends an original association change request to the first MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • step 501 is similar to step 301, and details are not described herein again.
  • Step 502 The first MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 503 is performed; otherwise, it ends, or an original association change response indicating that the change has failed is sent to the first UE.
  • Step 503 The first MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 504 ends or sends an original association change response indicating that the change failed to the first UE.
  • step 503 is similar to step 303, and details are not described herein again.
  • Step 504 The first MCPTT server sends an association change request to the group management server according to the original association change request.
  • the group management server is a group management server of the first MCPTT group; the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT.
  • the association of the group is a group management server of the first MCPTT group; the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT.
  • association change request and the original association change request may be the same message (that is, the first MCPTT server directly forwards the received original association change request to the group management server); or, the association The change request and the original associated change request may be different messages.
  • the target MCPTT user 1 corresponds to the target MCPTT group 1.
  • the target MCPTT user 2 corresponds to the target MCPTT group 2, the MCPTT server in the MCPTT system defining the target MCPTT group 1 is the MCPTT server A, and the MCPTT server in the MCPTT system defining the target MCPTT group 2 is the MCPTT server B;
  • the group management server of the target MCPTT group 1 does not include related information of the target MCPTT user 2 and the target MCPTT group 2 in the association change request received; for the group management server of the target MCPTT group 2, The related information of the target MCPTT user 1 and the target MCPTT group 1 is not included in the received association change request.
  • the group management server may be considered as the group management server receiving the association change request sent by the first UE.
  • Step 505 The group management server determines according to the group policy of the first MCPTT group. Determining whether the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be a target association relationship;
  • step 506 If yes, go to step 506; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • step 505 is only that the execution subject is different, and other similarities are not described herein.
  • Step 506 The group management server sends a change message to the second UE.
  • the second MCPTT user is a user who uses the second UE.
  • step 506 may specifically be:
  • the group management server sends the change message to the second UE by using an MCPTT server in an MCPTT system that defines a user profile of the second MCPTT user.
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship (that is, the target association relationship determined in step 505);
  • the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship.
  • the method further includes:
  • the group management server receives the change response sent by the second UE, and the change response is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is allowed to be set to the target association relationship. Or the change response is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is denied to be set as the target association relationship.
  • the change response is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is denied as the target association relationship, send the original UE to indicate that the change fails.
  • the change response is associated without performing steps 507-509.
  • Step 507 The group management server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • step 507 there is no order between step 507 and step 506.
  • the step 507 may further include: the group management server sends the second association information to the first MCPTT server, where the second association information is used to indicate the association between the second MCPTT user and the first MCPTT group.
  • the relationship is the target association relationship, so that the first MCPTT server updates the association relationship between the second MCPTT user and the first MCPTT group to the target association relationship.
  • Step 508 The group management server sends an association change response indicating that the change is successful to the first MCPTT server.
  • step 508 there is no order between step 508 and step 507.
  • Step 509 The first MCPTT server sends an original association change response to the first UE according to the association change response.
  • the original association change response is a response message corresponding to the original association change request; the relationship with the association change response is similar to the relationship between the original association change request and the association change request. That is, the association change response and the original association change response may be the same message; or the original association change response may be obtained by the first MCPTT server according to the association change response sent by one (or more) group management servers.
  • the first UE sends an original association change request to the first MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first Correlation relationship of the MCPTT group; the first MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and sends an association change request to the group management server; the group management server determines the first After the MCPTT group sets the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship, sending a change message to the second UE, where the change message is used to indicate the second The association relationship between the MCPTT user and the first MCPTT group is the target association relationship; or the change message is used to request the second MCPTT user to use the second MCPTT user and the first MCPTT group The association relationship is set to the target association relationship); enabling the first MCPTT user to change the association relationship between the first MCPTT
  • the difference between the embodiment shown in FIG. 5 and the embodiment shown in FIG. 3 is mainly that the execution body of the method in the embodiment shown in FIG. 5 is mainly a group management server, and the execution of the method in the embodiment shown in FIG.
  • the main body is the first MCPTT server.
  • the step of determining whether the first MCPTT user has the right to change the association relationship of the second MCPTT user in the embodiment shown in FIG. 3 and FIG. 5 is performed by the first MCPTT server.
  • FIG. 6 is a flowchart of Embodiment 6 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention.
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 3; as shown in FIG.
  • the methods can include:
  • Step 601 The first UE sends an original association change request to the first MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • step 601 is similar to step 301, and details are not described herein again.
  • Step 602 The first MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 603 is performed; otherwise, it ends, or an original association change response indicating that the change has failed is sent to the first UE.
  • Step 603 The first MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 604 ends or sends an original association change response indicating that the change failed to the first UE.
  • step 603 is similar to step 303, and details are not described herein again.
  • Step 604 The first MCPTT server sends an association change request to the group management server according to the original association change request.
  • the group management server is a group management server of the first MCPTT group.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • step 604 is similar to step 504, and details are not described herein again.
  • Step 605 The group management server determines according to the group policy of the first MCPTT group. Determining whether the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be a target association relationship;
  • step 606 is performed; otherwise, the process ends, or an original association change response indicating that the change has failed is sent to the first UE.
  • step 605 is similar to step 505, and details are not described herein again.
  • Step 606 The group management server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • Step 607 The group management server sends an update message to the first MCPTT server, where the update message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship.
  • step 607 there is no order between step 607 and step 606.
  • Step 608 After receiving the update message, the first MCPTT server sends a change message to the second UE.
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship, and the second MCPTT user is a user that uses the second UE.
  • the step 608 may further include: the first MCPTT server storing the target association relationship between the second MCPTT user and the first MCPTT group;
  • step 608 may also be considered as the group management server.
  • the second UE sends a change message.
  • Step 609 The first MCPTT server sends an original association change response indicating that the change is successful to the first UE.
  • the first UE sends an original association change request to the first MCPTT server (the original association original change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first An association relationship of an MCPTT group; the first MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and sends an association change request to the group management server; the group management server determines the first After the MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be the target association relationship, the update message is sent to the first MCPTT server.
  • the original association original change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first An association relationship of an MCPTT group
  • the first MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and sends an association change request to the group management
  • the first MCPTT server sends a change message to the second UE, where the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship;
  • the first MCPTT user can change the association relationship between the first MCPTT user and the first MCPTT group; thereby implementing the function that one MCPTT user changes the relationship between other MCPTT users and the group.
  • the difference between the embodiment shown in FIG. 6 and the embodiment shown in FIG. 5 is mainly as follows: 1) In the embodiment shown in FIG. 5, the group management server sends a change message to the second UE, and the implementation shown in FIG. In the example, the first MCPTT server sends a change message to the second UE; 2) the change message in the embodiment shown in FIG. 6 is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is In the target association relationship, the change message in the embodiment shown in FIG. 5 is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship, or is used to request the second MCPTT user. Setting an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship.
  • FIG. 7 is a flowchart of Embodiment 7 of a method for changing an association relationship between an MCPTT user and an MCPTT group according to the present invention.
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 3; as shown in FIG.
  • the methods can include:
  • Step 701 The first UE sends an association change request to the first MCPTT server, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association between the second MCPTT user and the first MCPTT group. relationship;
  • step 701 is similar to step 301, and details are not described herein again.
  • Step 702 The first MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 703. If yes, go to step 703. Otherwise, it ends or sends an association change response indicating that the change has failed to the first UE.
  • step 702 is similar to step 303, and details are not described herein again.
  • the first MCPTT server may also perform the determination in step 302.
  • Step 703 The first MCPTT server sends a change message to the second UE.
  • the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship.
  • Step 704 The second UE sends a change response to the first MCPTT server.
  • the change response is used to indicate that an association relationship between the second MCPTT user and the first MCPTT group is allowed to be set as the target association relationship.
  • the second UE may further determine, according to the user input, that the second MCPTT user allows the association relationship between the second MCPTT user and the first MCPTT group to be the target. connection relation.
  • Step 705 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 705 is similar to step 304, and details are not described herein again.
  • Step 706 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 707 is performed; otherwise, the process ends, or an association change response indicating that the change has failed is sent to the first UE.
  • Step 707 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • Step 708 The first MCPTT server sends an association change response indicating that the change is successful to the first UE.
  • step 708 there is no order between step 708 and step 707.
  • the first UE sends an association change request to the first MCPTT server.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group.
  • the first MCPTT server determines that the second MCPTT user allows the association relationship between the second MCPTT user and the first MCPTT group to be the target association relationship, and further determines the first MCPTT group.
  • the target association relationship is enabled to enable the first MCPTT user to change the association relationship between the first MCPTT user and the first MCPTT group; thereby implementing the function of an MCPTT user changing the relationship between other MCPTT users and the group.
  • the difference between the embodiment shown in FIG. 7 and the embodiment shown in FIG. 3 mainly lies in:
  • the change message is sent to the second UE.
  • the change message is sent to the second UE, and the consent of the second MCPTT user is first sought.
  • FIG. 8 is a flowchart of Embodiment 8 of a method for changing an association between an MCPTT user and an MCPTT group according to the present invention
  • the application scenario in this embodiment may be: an MCPTT system that defines a user profile of a first MCPTT user, and defines a second MCPTT user.
  • the MCPTT system of the user profile is the same as the MCPTT system that defines the first MCPTT group, and is different from the MCPTT system that defines the first MCPTT group.
  • the method in this embodiment may include:
  • Step 801 The first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user.
  • step 801 is similar to step 301, and details are not described herein again.
  • Step 802 The second MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 803 If yes, go to step 803; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • Step 803 The second MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 804 ends or sends an original association change response indicating that the change failed to the first UE.
  • step 803 is only that the execution subject is different, and other similarities are not described herein.
  • Step 804 The second MCPTT server is first according to the original association change request.
  • the MCPTT server sends an association change request;
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • Step 805 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 805 is similar to step 304, and details are not described herein again.
  • Step 806 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 807 If yes, go to step 807; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • step 806 is similar to step 305, and details are not described herein again.
  • Step 807 The first MCPTT server sends a change message to the second UE.
  • the second MCPTT user is a user who uses the second UE.
  • step 807 is similar to step 306, and details are not described herein again.
  • Step 808 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • step 808 there is no order between step 808 and step 807.
  • step 808 is similar to step 307, and details are not described herein again.
  • Step 809 The first MCPTT server sends an association change response indicating that the change is successful to the second MCPTT server.
  • Step 810 The second MCPTT server sends an original association change response to the first UE according to the association change response.
  • the first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first Correlation relationship of the MCPTT group;
  • the second MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and sends an association change request to the first MCPTT server;
  • the first MCPTT server Determining that the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be set as a target association relationship, and sending a change message to the second UE (where the change message is used for And indicating that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship; or the change message is used to request the second MCPTT user to use the second MCPTT user with the The association relationship of the first MCPTT group is set to the target association relationship), so that the first M
  • the difference between the embodiment shown in FIG. 8 and the embodiment shown in FIG. 3 is mainly as follows: in the embodiment shown in FIG. 8, the first UE sends the original association change request to the second MCPTT server, and the second MCPTT server. After determining that the first MCPTT user has the right to change the association relationship of the second MCPTT user, send an association change request to the first MCPTT server; in FIG. 3, the first UE directly sends the association change request to the first MCPTT server, where the first The MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT server.
  • FIG. 9 is a flowchart of Embodiment 9 of a method for changing an association between an MCPTT user and an MCPTT group according to the present invention.
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 8; as shown in FIG.
  • the methods can include:
  • Step 901 The first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • step 901 is similar to step 801, and details are not described herein again.
  • Step 902 The second MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 903 If yes, go to step 903; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • Step 903 The second MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 904 ends or sends an original association change response indicating that the change failed to the first UE.
  • step 903 is similar to step 803, and details are not described herein again.
  • Step 904 The second MCPTT server forwards the original association change request to the first MCPTT server.
  • step 904 is similar to step 804, and details are not described herein again.
  • Step 905 The first MCPTT server sends an association change request to the group management server according to the original association change request.
  • Step 906 The group management server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Target relationship;
  • step 906 is similar to step 505, and details are not described herein again.
  • Step 907 The group management server sends a change message to the second UE.
  • the second MCPTT user is a user who uses the second UE.
  • step 907 is similar to step 506, and details are not described herein again.
  • Step 908 The group management server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • step 908 there is no order between step 908 and step 907.
  • step 908 is similar to step 507, and details are not described herein again.
  • Step 909 The group management server sends an association change response indicating that the change is successful to the first MCPTT server.
  • step 909 there is no order between step 909 and step 908.
  • Step 910 The first MCPTT server sends an original association change response to the second MCPTT server according to the association change response.
  • Step 911 The second MCPTT server forwards the original association change response to the first UE.
  • the first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate the first MCPTT.
  • the user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • the second MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and then uses the first MCPTT server to the group management server.
  • the group management server determines that the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be set as a target association relationship, and then sends a change to the second UE a message, wherein the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship; or the change message is used to request the second MCPTT user Setting the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship; enabling the first MCPTT user to change the association relationship between the first MCPTT user and the first MCPTT group; An MCPTT user changes the relationship between other MCPTT users and groups.
  • the difference between the embodiment shown in FIG. 9 and the embodiment shown in FIG. 5 is mainly that: in the embodiment shown in FIG. 9, the first UE sends an original association change request to the second MCPTT server, and the second MCPTT server is configured by the second MCPTT server. After determining that the first MCPTT user has the right to change the association relationship of the second MCPTT user, send an association change request to the first MCPTT server; in FIG. 5, the first UE directly sends an association change request to the first MCPTT server, by using the first MCPTT. The server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT server.
  • FIG. 10 is a flowchart of a tenth embodiment of a method for changing an association relationship between an MCPTT user and an MCPTT group.
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 8. As shown in FIG. 10, this embodiment is shown in FIG.
  • the methods can include:
  • Step 1001 The first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user.
  • step 1001 is similar to the step 301, and details are not described herein again.
  • Step 1002 The second MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 1003 ends or sends an original association change response indicating that the change failed to the first UE.
  • step 1002 is similar to step 303, and details are not described herein again.
  • the second MCPTT server may also perform the determination in step 302.
  • Step 1003 The second MCPTT server sends a change message to the second UE.
  • the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship.
  • Step 1004 The second UE sends a change response to the second MCPTT server.
  • the change response is used to indicate that an association relationship between the second MCPTT user and the first MCPTT group is allowed to be set as the target association relationship.
  • Step 1005 The second MCPTT server sends an association change request to the first MCPTT server according to the original association change request.
  • the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • Step 1006 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 1006 is similar to step 304, and details are not described herein again.
  • Step 1007 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 1008 If yes, go to step 1008; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • Step 1008 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • Step 1009 The first MCPTT server sends an association change response indicating that the change is successful to the second MCPTT server.
  • Step 1010 The second MCPTT server changes the response according to the association, to the first A UE sends an original association change response.
  • the second MCPTT server may further include:
  • the first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first Correlation relationship of the MCPTT group; the second MCPTT server determines that the second MCPTT user allows the association relationship between the second MCPTT user and the first MCPTT group to be the target association relationship, and sends the association to the first MCPTT server.
  • the first MCPTT server determines whether the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be a target association relationship, and when the first MCPTT group allows And storing, by the first MCPTT user, the association relationship between the first MCPTT user and the first MCPTT group; thereby implementing an MCPTT user changing other MCPTTs. The function of the user's association with the group.
  • the difference between the embodiment shown in FIG. 10 and the embodiment shown in FIG. 7 is mainly that: in the embodiment shown in FIG. 10, the first UE sends an original association change request to the second MCPTT server, and the second MCPTT server is configured by the second MCPTT server. After determining that the first MCPTT user has the right to change the association relationship of the second MCPTT user, send an association change request to the first MCPTT server; in FIG. 7, the first UE directly sends an association change request to the first MCPTT server, by using the first The MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT server.
  • FIG. 11 is a flowchart of Embodiment 11 of a method for changing an association between an MCPTT user and an MCPTT group according to the present invention.
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 8;
  • the method of the example may include:
  • Step 1101 The first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • step 1101 is similar to step 301, and details are not described herein again.
  • Step 1102 The second MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 1103. If yes, go to step 1103. Otherwise, it ends or sends an original association change response indicating that the change failed to the first UE.
  • step 1103 is similar to step 303, and details are not described herein again.
  • the second MCPTT server may also perform the determination in step 302.
  • Step 1103 The second MCPTT server sends an association change request to the first MCPTT server according to the original association change request.
  • the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • Step 1104 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 1104 is similar to step 304, and details are not described herein again.
  • Step 1105 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 1106 If yes, go to step 1106; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • Step 1106 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • Step 1107 The first MCPTT server sends an association change response indicating that the change is successful to the second MCPTT server.
  • Step 1108 The second MCPTT server sends a change message to the second UE.
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship.
  • the second MCPTT server may include the foregoing in the association change response message.
  • the target association relationship is obtained by the target association relationship; or the second MCPTT server may obtain the target association relationship according to the association change request sent by the first UE.
  • Step 1109 The second MCPTT server sends an original association change response to the first UE according to the association change response.
  • the second MCPTT server may further include:
  • the first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first An association relationship of the MCPTT group; the second MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and sends an association change request to the first MCPTT server; the first MCPTT server determines the After the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be the target association relationship, the second MCPTT server sends a change message to the second UE (where the change message is used) Instructing the association relationship between the second MCPTT user and the first MCPTT group to be the target association relationship; enabling the first MCPTT user to change the association relationship between the first MCPTT user and the first MCPTT group; An MCPTT user changes the relationship between other MCPTT users and groups.
  • FIG. 12 is a flowchart of Embodiment 12 of a method for changing an association between an MCPTT user and an MCPTT group according to the present invention
  • the application scenario in this embodiment may be: an MCPTT system that defines a user profile of a first MCPTT user, and defines a second MCPTT.
  • the MCPTT system of the user profile and the MCPTT system of the first MCPTT group are different.
  • the method in this embodiment may include:
  • Step 1201 The first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • the second MCPTT server is configured to define a user of the first MCPTT user.
  • File MCPTT server in the MCPTT system is configured to define a user of the first MCPTT user.
  • step 1201 is similar to step 301, and details are not described herein again.
  • Step 1202 The second MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 1203 ends or sends an original association change response indicating that the change failed to the first UE.
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user.
  • step 1202 is similar to step 803, and details are not described herein again.
  • Step 1203 The second MCPTT server forwards the original association change request to a third MCPTT server.
  • the third MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the second MCPTT user.
  • Step 1204 The third MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 1205 If yes, go to step 1205; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • the number of MCPTT groups associated with the second MCPTT user may be controlled by the third MCPTT server by step 1204.
  • Step 1205 The third MCPTT server sends an association change request to the first MCPTT server according to the original association change request.
  • the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • Step 1206 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 1206 is similar to step 304, and details are not described herein again.
  • Step 1207 The first MCPTT server is configured according to the group of the first MCPTT group. a policy, determining whether the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be a target association relationship;
  • step 1208 If yes, go to step 1208; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • step 1207 is similar to step 305, and details are not described herein again.
  • Step 1208 The first MCPTT server sends a change message to the second UE.
  • the second MCPTT user is a user who uses the second UE.
  • step 1208 is similar to step 306, and details are not described herein again.
  • Step 1209 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • step 1209 there is no order between step 1209 and step 1208.
  • step 1209 is similar to step 307, and details are not described herein again.
  • Step 1210 The first MCPTT server sends an association change response indicating that the change is successful to the third MCPTT server.
  • Step 1211 The third MCPTT server forwards the association change response for indicating that the change is successful to the second MCPTT server.
  • Step 1212 The second MCPTT server sends an original association change response to the first UE according to the association change response.
  • the first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first
  • the relationship between the MCPTT group and the second MCPTT determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and sends an original association change request to the third MCPTT server;
  • the threshold of the number of MCPTT groups associated with the second MCPTT user determines to change the association relationship between the second MCPTT user and the first MCPTT group, and then sends an association change request to the first MCPTT server;
  • the first MCPTT server Determining that the first MCPTT group allows the association relationship between the second MCPTT user and the first MCPTT group to be set as a target association relationship, and sending a change message to the second UE (where the change message is used for Indicating the second The association relationship between the MCPTT user and the first M
  • the difference between the embodiment shown in FIG. 12 and the embodiment shown in FIG. 8 is mainly as follows: in the embodiment shown in FIG. 12, the first MCPTT server receives the association change request sent by the first UE through the second MCPTT server; The first MCPTT server in the 8 receives the association change request sent by the first UE through the second MCPTT server and the third MCPTT server.
  • FIG. 13 is a flowchart of a thirteenth embodiment of a method for changing a relationship between an MCPTT user and an MCPTT group according to the present invention; the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 12; The method of the example may include:
  • Step 1301 The first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user.
  • step 1301 is similar to the step 301, and details are not described herein again.
  • Step 1302 The second MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 1303 ends or sends an original association change response indicating that the change failed to the first UE.
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user.
  • step 1302 is similar to step 803, and details are not described herein again.
  • Step 1303 The second MCPTT server forwards the original association change request to a third MCPTT server.
  • the third MCPTT server is configured to define a user of the second MCPTT user.
  • File MCPTT server in the MCPTT system is configured to define a user of the second MCPTT user.
  • Step 1304 The third MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 1305 is performed; otherwise, the process ends, or an original association change response indicating that the change has failed is sent to the first UE.
  • Step 1305 The third MCPTT server sends a change message to the second UE.
  • the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as the target association relationship.
  • Step 1306 The second UE sends a change response to the second MCPTT server.
  • the change response is used to indicate that an association relationship between the second MCPTT user and the first MCPTT group is allowed to be set as the target association relationship.
  • Step 1307 The third MCPTT server sends an association change request to the first MCPTT server according to the original association change request.
  • the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • Step 1308 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 1308 is similar to step 304, and details are not described herein again.
  • Step 1309 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 1310 is performed; otherwise, the process ends, or an original association change response indicating that the change has failed is sent to the first UE.
  • step 1309 is similar to step 305, and details are not described herein again.
  • Step 1310 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • step 1310 is similar to step 307, and details are not described herein again.
  • Step 1311 The first MCPTT server sends an association change response indicating that the change is successful to the third MCPTT server.
  • Step 1312 The third MCPTT server sends an original association change response to the second MCPTT server according to the association change response.
  • Step 1313 The second MCPTT server forwards the original association change response to the first UE.
  • the first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first
  • the MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and then forwards the original association change request to the third MCPTT server; the third MCPTT server determines the second After the MCPTT user sets the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship, the association change request is sent to the first MCPTT server; the first MCPTT server determines the first MCPTT group.
  • the difference between the embodiment shown in FIG. 13 and the embodiment shown in FIG. 10 is mainly that: in the embodiment shown in FIG. 13, the third MCPTT server sends a change message to the second UE; in FIG. 10, the second MCPTT The server sends a change message to the second UE.
  • FIG. 14 is a flowchart of Embodiment 14 of the method for changing the association between an MCPTT user and an MCPTT group according to the present invention
  • the application scenario of the embodiment is the same as the application scenario of the embodiment shown in FIG. 12
  • the method of the example may include:
  • Step 1401 The first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Relationship
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user.
  • step 1401 is similar to step 301, and details are not described herein again.
  • Step 1402 The second MCPTT server determines whether the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • step 1403 ends or sends an original association change response indicating that the change failed to the first UE.
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user.
  • step 1402 is similar to step 803, and details are not described herein again.
  • Step 1403 The second MCPTT server forwards the original association change request to a third MCPTT server.
  • the third MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the second MCPTT user.
  • the second MCPTT server may directly forward the original association change request sent by the first UE to the third MCPTT server; or the second MCPTT server may also receive the same. After the original association change request sent by the first UE, a new message is sent to the first MCPTT server according to the original association change request.
  • Step 1404 The third MCPTT server determines, according to a threshold of the number of MCPTT groups associated with the second MCPTT user, whether to change an association relationship between the second MCPTT user and the first MCPTT group.
  • step 1405 If yes, go to step 1405; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • Step 1405 The third MCPTT server sends an association change request to the first MCPTT server according to the original association change request.
  • the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the association relationship between the second MCPTT user and the first MCPTT group.
  • Step 1406 The first MCPTT server acquires a group policy of the first MCPTT group from a group management server.
  • step 1406 is similar to step 304, and details are not described herein again.
  • Step 1407 The first MCPTT server determines, according to the group policy of the first MCPTT group, whether the first MCPTT group allows association between the second MCPTT user and the first MCPTT group. Set as the target association;
  • step 1408 If yes, go to step 1408; otherwise, end, or send an original association change response indicating that the change failed to the first UE.
  • step 1407 is similar to step 305, and details are not described herein again.
  • Step 1408 The first MCPTT server stores the target association relationship between the second MCPTT user and the first MCPTT group.
  • step 1408 is similar to step 307, and details are not described herein again.
  • Step 1409 The first MCPTT server sends an association change response indicating that the change is successful to the third MCPTT server.
  • Step 1410 The third MCPTT server sends a change message to the second UE.
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship.
  • the third MCPTT server may obtain the target association relationship by including the target association relationship in the association change response message; or the third MCPTT server may also be configured according to the association change request sent by the first UE. Obtaining the target association relationship.
  • Step 1411 The third MCPTT server sends an original association change response to the second MCPTT server according to the association change response.
  • step 1411 there is no relationship between step 1411 and step 1410.
  • Step 1412 The second MCPTT server forwards the original association change response to the first UE.
  • the first UE sends an original association change request to the second MCPTT server, where the original association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first
  • the relationship between the MCPTT group and the second MCPTT server determines that the first MCPTT user has the right to change the association relationship of the second MCPTT user, and forwards the original association change request to the third MCPTT server; Threshold determination of the number of MCPTT groups associated with the second MCPTT user After the relationship between the two MCPTT users and the first MCPTT group, sending an association change response to the first MCPTT server; the first MCPTT server determining whether the first MCPTT group allows the second MCPTT user to The association relationship of the first MCPTT group is set as the target association relationship; and after the first MCPTT server determines that the first MCPTT group allows, the third MCPTT server sends a change message to the second UE (where the change message is used to indicate the
  • FIG. 15 is a schematic structural diagram of Embodiment 1 of a device for changing an association between an MCPTT user and an MCPTT group according to the present invention
  • the device is a first network element device, as shown in FIG. 15, the device includes: a receiving module 1501 and a setting module. 1502.
  • the receiving module 1501 is configured to receive an association change request sent by the first user equipment UE, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT.
  • An association relationship of the group; the first MCPTT user is an MCPTT user that uses the first UE; and the setting module 1502 is configured to set the second MCPTT user and the first MCPTT group according to the association change request Group associations.
  • the device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 1 , and the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 16 is a schematic structural diagram of Embodiment 2 of an apparatus for changing an association between an MCPTT user and an MCPTT group according to the present invention; as shown in FIG. 16, the apparatus of this embodiment is further based on the apparatus structure shown in FIG.
  • the method includes: a sending module 1503.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is a first MCPTT server; MCPTT server in the MCPTT system of an MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used to indicate that the second MCPTT user is requested to be associated or de-associated with the first MCPTT group.
  • the request information includes:
  • a user identifier of the second MCPTT user and a group identifier of the first MCPTT group Or the group identifier of the second MCPTT group to which the second MCPTT user belongs and the group identifier of the first MCPTT group.
  • the setting module 1502 is further configured to: determine that the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • the setting module 1502 is further configured to: determine, according to a threshold value of the number of MCPTT groups associated with the second MCPTT user, to change an association relationship between the second MCPTT user and the first MCPTT group.
  • the setting module 1502 sets the association relationship between the second MCPTT user and the first MCPTT group according to the association change request, and specifically includes:
  • the setting module 1502 is further configured to: determine, according to the group policy of the first MCPTT group, that the first MCPTT group allows the second MCPTT user and the first MCPTT group to The association relationship is set to the target association relationship.
  • the receiving module 1501 is specifically configured to:
  • the second network element device is a second MCPTT server or a third MCPTT server;
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user;
  • the MCPTT server is an MCPTT server in the MCPTT system that defines the user profile of the second MCPTT user.
  • the mode 1 the setting module 1502 sets the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship according to the association change request, which specifically includes:
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is a target association relationship, and the second MCPTT user is to use the second UE. MCPTT users.
  • the setting module 1502 is further configured to:
  • the receiving module 1501 Receiving, by the receiving module 1501, the change response sent by the second UE, where the change response is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is allowed to be set to the target association relationship.
  • the setting module 1502 sets the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship according to the association change request, which specifically includes: And storing the target association relationship between the second MCPTT user and the first MCPTT group.
  • the setting module 1502 sets, according to the association change request, the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship, specifically:
  • the sending module 1503 Sending, by the sending module 1503, a change message to the second UE, where the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is the target association relationship; the second MCPTT The user is an MCPTT user who uses the second UE;
  • the sending module 1503 sends a change message to the second UE, specifically:
  • the change message is sent to the second UE by an MCPTT server in an MCPTT system that defines a user profile of the second MCPTT user.
  • the sending module 1503 is further configured to send an association change response to the first UE.
  • the change message includes: a user identifier of the first MCPTT user.
  • the association change request further includes: a user identifier of the first MCPTT user.
  • the apparatus of this embodiment may be used to execute the first MCPTT of the method embodiment shown in FIG. 3-14.
  • the technical solution of the server or group management server is similar in its implementation principle and technical effects, and is not described here.
  • FIG. 17 is a schematic structural diagram of Embodiment 3 of a device for changing an association between an MCPTT user and an MCPTT group according to the present invention
  • the device is a second network element device, as shown in FIG. 17, the device includes: a receiving module 1701 and a sending module. 1702.
  • the receiving module 1701 is configured to receive an association change request sent by the first user equipment UE, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT.
  • the second network element device is a second MCPTT server or a third MCPTT server;
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user;
  • the third MCPTT server is an MCPTT server in the MCPTT system that defines a user profile of the second MCPTT user.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is a first MCPTT server; MCPTT server in the MCPTT system of an MCPTT group.
  • the device in this embodiment may be used to execute the second MCPTT server in the method embodiment shown in FIG. 10 and the third MCPTT server side in the method embodiment shown in FIG. 13 , and the implementation principle and technical effects are similar. Let me repeat.
  • the device in this embodiment is the first UE; the structure of the embodiment is similar to the structure of the device shown in FIG. 17, and may also include a sending module and a receiving module.
  • the sending module is configured to send an association change request to the first network element device, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT group. Close The association relationship, so that the first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request; the first MCPTT user is a user who uses the first UE; and receives And a module, configured to receive an association change response sent by the first network element device.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used to indicate that the second MCPTT user is requested to be associated or de-associated with the first MCPTT group.
  • the request information includes: a user identifier of the second MCPTT user and a group identifier of the first MCPTT group; or a group of a second MCPTT group to which the second MCPTT user belongs A group identifier and a group identifier of the first MCPTT group.
  • the association change request includes: a user identifier of the first MCPTT user.
  • the device in this embodiment may be used to implement the technical solution of the first UE side in the method embodiment shown in FIG. 3 to FIG. 14.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • the present invention further provides a system for changing an emergency task, that is, a system for associating an MCPTT user with an MCPTT group, including: a device for changing an association relationship between an MCPTT user and an MCPTT group, or a first network according to the second embodiment And the first UE described in Embodiment 4 of the apparatus for changing the relationship between the MCPTT user and the MCPTT group.
  • a system for changing an emergency task that is, a system for associating an MCPTT user with an MCPTT group, including: a device for changing an association relationship between an MCPTT user and an MCPTT group, or a first network according to the second embodiment And the first UE described in Embodiment 4 of the apparatus for changing the relationship between the MCPTT user and the MCPTT group.
  • system of this embodiment may further include: a second network element device according to Embodiment 3 of the device that changes the association between the MCPTT user and the MCPTT group.
  • the system of the present embodiment can be used to implement the technical solution of the method embodiment shown in FIG. 3 and FIG. 13 , and the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 18 is a schematic structural diagram of Embodiment 5 of a device for changing an association between an MCPTT user and an MCPTT group according to the present invention
  • the device is a first network element device, as shown in FIG. 18, the device includes: a receiver 1801 and a processor 1802.
  • the receiver 1801 is configured to receive an association change request sent by the first user equipment UE, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first MCPTT.
  • An association relationship of the group; the first MCPTT user is an MCPTT user that uses the first UE; and the processor 1802 is configured to set the second MCPTT user and the first according to the association change request The association of MCPTT groups.
  • the device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 1 , and the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 19 is a schematic structural diagram of Embodiment 6 of the apparatus for changing the relationship between an MCPTT user and an MCPTT group according to the present invention; as shown in FIG. 19, the apparatus of this embodiment is further based on the apparatus structure shown in FIG. Including: transmitter 1803.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is a first MCPTT server; MCPTT server in the MCPTT system of an MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used to indicate that the second MCPTT user is requested to be associated or de-associated with the first MCPTT group.
  • the request information includes: a user identifier of the second MCPTT user and a group identifier of the first MCPTT group; or a group of a second MCPTT group to which the second MCPTT user belongs A group identifier and a group identifier of the first MCPTT group.
  • the processor 1802 is further configured to: determine that the first MCPTT user has the right to change the association relationship of the second MCPTT user.
  • the processor 1802 is further configured to: determine, according to a threshold value of the number of MCPTT groups associated with the second MCPTT user, to change an association relationship between the second MCPTT user and the first MCPTT group.
  • the processor 1802 sets an association relationship between the second MCPTT user and the first MCPTT group, and specifically includes:
  • the processor 1802 is further configured to: determine, according to the group policy of the first MCPTT group, that the first MCPTT group allows the second MCPTT user and the first MCPTT group to The association relationship is set to the target association relationship.
  • the receiver 1801 is specifically configured to:
  • the second network element device is a second MCPTT server or a third MCPTT server;
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user;
  • the MCPTT server is an MCPTT server in the MCPTT system that defines the user profile of the second MCPTT user.
  • the processor 1802 sets the association relationship between the second MCPTT user and the first MCPTT group as a target association relationship according to the association change request, which specifically includes:
  • the change message is used to indicate that the association relationship between the second MCPTT user and the first MCPTT group is a target association relationship; and the second MCPTT user is an MCPTT user that uses the second UE.
  • the processor 1802 is further configured to:
  • the transmitter 1803 Sending, by the transmitter 1803, a change message to the second UE, where the change message is used to request the second MCPTT user to set an association relationship between the second MCPTT user and the first MCPTT group as the target An association relationship; the second MCPTT user is an MCPTT user using the second UE;
  • the processor 1802 sets the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship according to the association change request, which specifically includes: And storing the target association relationship between the second MCPTT user and the first MCPTT group.
  • Mode 3 the processor 1802 sets, according to the association change request, the association relationship between the second MCPTT user and the first MCPTT group as the target association relationship, specifically:
  • the sender 1803 sends the change message to the second UE, specifically:
  • the change message is sent to the second UE by an MCPTT server in an MCPTT system that defines a user profile of the second MCPTT user.
  • the transmitter 1803 is further configured to send an association change response to the first UE.
  • the device in this embodiment may be used to perform the technical solution on the first MCPTT server or the group management server side of the method embodiment shown in FIG. 3, and the implementation principle and technical effects are similar, and details are not described herein again.
  • the device in this embodiment is a second network element device; the structure of this embodiment is similar to the structure of the device shown in FIG. 19, and may also include a receiver, a processor, and a transmitter.
  • the processor is configured to receive, by the receiver, an association change request sent by the first user equipment UE, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first An MCPTT group association relationship; the first MCPTT user is an MCPTT user that uses the first UE; and the processor is further configured to send, by using a transmitter, a change message, where the change message is used to request the location
  • the second MCPTT user sets the association relationship between the second MCPTT user and the first MCPTT group as a target association relationship; the second MCPTT user is an MCPTT user using the second UE; And receiving, by the receiver, a change response sent by the second UE, where the change response is used to indicate that an association relationship between the second MCPTT
  • the second network element device is a second MCPTT server or a third MCPTT server;
  • the second MCPTT server is an MCPTT server in an MCPTT system that defines a user profile of the first MCPTT user;
  • the third MCPTT server is an MCPTT server in the MCPTT system that defines a user profile of the second MCPTT user.
  • the first network element device is a group management server of the first MCPTT group, Or the first network element device is a first MCPTT server; the first MCPTT server is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the device in this embodiment may be used to execute the second MCPTT server in the method embodiment shown in FIG. 10 and the third MCPTT server side in the method embodiment shown in FIG. 13 , and the implementation principle and technical effects are similar. Let me repeat.
  • the device in this embodiment is a first UE; the structure of this embodiment is similar to the structure of the device shown in FIG. 19, and may also include a receiver, a processor, and a transmitter.
  • the processor is configured to send, by using a sender, an association change request to the first network element device, where the association change request includes request information, where the request information is used to indicate that the first MCPTT user requests to change the second MCPTT user and the first An association relationship of the MCPTT group, so that the first network element device sets an association relationship between the second MCPTT user and the first MCPTT group according to the association change request; the first MCPTT user uses the first UE
  • a processor configured to receive, by the receiver, an association change response sent by the first network element device.
  • the first network element device is a group management server of the first MCPTT group, or the first network element device is an MCPTT server in an MCPTT system that defines the first MCPTT group.
  • the association change request further includes: an association relationship indication, where the association relationship indication is used to indicate that the second MCPTT user is requested to be associated or de-associated with the first MCPTT group.
  • the request information includes: a user identifier of the second MCPTT user and a group identifier of the first MCPTT group; or a group of a second MCPTT group to which the second MCPTT user belongs A group identifier and a group identifier of the first MCPTT group.
  • the device in this embodiment may be used to implement the technical solution of the first UE side in the method embodiment shown in FIG. 3 to FIG. 14.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Abstract

本发明实施例提供一种变更MCPTT用户与MCPTT群组关联关系的方法、装置及系统。一种变更MCPTT用户与MCPTT群组关联关系的方法，包括：第一网元设备接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一紧急任务即按即说MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系。本发明实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。

Description

变更MCPTT用户与MCPTT群组关联关系的方法、装置及系统 技术领域
本发明实施例涉及通信技术，尤其涉及一种变更MCPTT用户与MCPTT群组关联关系的方法、装置及系统。
背景技术
紧急任务即按即说(MCPTT，Mission Critical Push To Talk)用户在一个MCPTT群组中进行群组通信时，需要先与该MCPTT群组建立关联关系。
现有技术中，MCPTT用户需要与MCPTT群组建立关联关系时，用户设备(UE，User Equipment)(该MCPTT用户为使用该UE的用户)向MCPTT服务器发送组关联请求消息，以请求与该MCPTT群组建立关联关系。在实际应用中存在一种需求就是一个MCPTT用户可能需要某一个(或多个)MCPTT用户加入到某个MCPTT群组的群组通信，或者终止该一个(或多个)MCPTT用户在某个MCPTT群组中的群组通信。例如，某些特定MCPTT用户(例如，被授权的高级MCPTT用户如调度员、管理员等)由于业务需求，希望某个MCPTT用户参与到某个MCPTT群组的群组通信；因此就需要一个MCPTT用户能够变更其他MCPTT用户与MCPTT群组的关联关系。
但是，现有技术中尚不能支持一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
发明内容
本发明实施例提供一种变更MCPTT用户与MCPTT群组关联关系的方法、装置及系统，用以解决现有技术中尚不能支持一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能的问题。
第一方面，本发明实施例提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的方法，包括：
第一网元设备接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第 二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
结合第一方面，在第一方面的第一种可能实现的方式中，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
结合第一方面或第一方面的第一种可能实现的方式，在第一方面的第二种可能实现的方式中，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
结合第一方面或第一方面的第一种至第二种任一种可能实现的方式，在第一方面的第三种可能实现的方式中，所述请求信息，包括：
所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
结合第一方面或第一方面的第一种至第三种任一种可能实现的方式，在第一方面的第四种可能实现的方式中，所述第一网元设备根据所述关联变更请求，设置所述第一MCPTT用户与所述第一MCPTT群组的关联关系之前，还包括：
所述第一网元设备确定所述第一MCPTT用户有权限变更所述第二MCPTT用户的关联关系。
结合第一方面或第一方面的第一种至第四种任一种可能实现的方式，在第一方面的第五种可能实现的方式中，所述第一网元设备根据所述关联变更请求，设置所述第一MCPTT用户与所述第一MCPTT群组的关联关系之前，还包括：
所述第一网元设备根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
结合第一方面或第一方面的第一种至第五种任一种可能实现的方式，在 第一方面的第六种可能实现的方式中，所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系，包括：
所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述目标关联关系为所述第一网元设备根据所述关联变更请求确定的。
结合第一方面的第六种可能实现的方式，在第一方面的第七种可能实现的方式中，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之前，还包括：
所述第一网元设备根据所述第一MCPTT群组的群组策略，确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
结合第一方面的第六种或第七种可能实现的方式，在第一方面的第八种可能实现的方式中，所述第一网元设备接收第一UE发送的关联变更请求，包括：
所述第一网元设备接收所述第一UE通过第二网元设备发送的所述关联变更请求；
其中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
结合第一方面的第八种可能实现的方式，在第一方面的第九种可能实现的方式中，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，包括：
所述第一网元设备存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
所述第一网元设备向所述第二网元设备发送关联变更响应，以使所述第二网元设备将所述关联变更响应转发至所述第一UE，并向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为目标关联关系；所述第二MCPTT用户为使用所述第二UE 的MCPTT用户。
结合第一方面的第六种至第八种任一种可能实现的方式，在第一方面的第十种可能实现的方式中，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系之前，还包括：
所述第一网元设备向第二UE发送变更消息；其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
所述第一网元设备接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
结合第一方面的第十种可能实现的方式，在第一方面的第十一种可能实现的方式中，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，包括：
所述第一网元设备存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
结合第一方面的第六种至第八种任一种可能实现的方式，在第一方面的第十二种可能实现的方式中，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，包括：
所述第一网元设备向第二UE发送变更消息；其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
所述第一网元设备存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
结合第一方面的第十种至第十二种任一种可能实现的方式，在第一方面的第十三种可能实现的方式中，所述第一网元设备向第二UE发送变更消息，包括：
所述第一网元设备通过定义所述第二MCPTT用户的用户配置文件的 MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
结合第一方面的第十种至第十三种任一种可能实现的方式，在第一方面的第十四种可能实现的方式中，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系之后，还包括：
所述第一网元设备向所述第一UE发送关联变更响应。
结合第一方面的第九种至第十四种任一种可能实现的方式，在第一方面的第十五种可能实现的方式中，所述变更消息包括：所述第一MCPTT用户的用户标识。
结合第一方面的第十五种可能实现的方式，在第一方面的第十六种可能实现的方式中，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
第二方面，本发明实施例提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的方法，包括：
第二网元设备接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
所述第二网元设备向第二UE发送变更消息，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
所述第二网元设备接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；
所述第二网元设备将所述关联变更请求发送至第一网元设备。
结合第二方面，在第二方面的第一种可能实现的方式中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件 的MCPTT系统中的MCPTT服务器。
结合第二方面或第二方面的第一种可能实现的方式，在第二方面的第二种可能实现的方式中，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
第三方面，本发明实施例提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的方法，包括：
第一用户设备UE向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；
所述第一UE接收所述第一网元设备发送的关联变更响应。
结合第三方面，在第三方面的第一种可能实现的方式中，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
结合第三方面或第三方面的第一种可能实现的方式，在第三方面的第二种可能实现的方式中，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
结合第三方面或第三方面的第一种至第二种任一种可能实现的方式，在第三方面的第三种可能实现的方式中，所述请求信息，包括：
所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
结合第三方面或第三方面的第一种至第三种任一种可能实现的方式，在第三方面的第四种可能实现的方式中，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
第四方面，本发明实施例提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的装置，所述装置为第一网元设备，所述装置包括：
接收模块，用于接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
设置模块，用于根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
结合第四方面，在第四方面的第一种可能实现的方式中，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
结合第四方面或第四方面的第一种可能实现的方式，在第四方面的第二种可能实现的方式中，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
结合第四方面或第四方面的第一种至第二种任一种可能实现的方式，在第四方面的第三种可能实现的方式中，所述请求信息，包括：
所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
结合第四方面或第四方面的第一种至第三种任一种可能实现的方式，在第四方面的第四种可能实现的方式中，所述设置模块，还用于：
确定所述第一MCPTT用户有权限变更所述第二MCPTT用户的关联关系。
结合第四方面或第四方面的第一种至第四种任一种可能实现的方式，在第四方面的第五种可能实现的方式中，所述设置模块，还用于：
根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
结合第四方面或第四方面的第一种至第五种任一种可能实现的方式，在第四方面的第六种可能实现的方式中，所述设置模块根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系，具体包括：
根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述目标关联关系为所述设置模块根据所述关联变更请求确定的。
结合第四方面的第六种可能实现的方式，在第四方面的第七种可能实现的方式中，所述设置模块，还用于：
根据所述第一MCPTT群组的群组策略，确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
结合第四方面的第六种或第七种可能实现的方式，在第四方面的第八种可能实现的方式中，所述接收模块，具体用于：
接收所述第一UE通过第二网元设备发送的所述关联变更请求；
其中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
结合第四方面的第八种可能实现的方式，在第四方面的第九种可能实现的方式中，所述装置还包括：发送模块；
所述设置模块根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，具体包括：
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
通过所述发送模块向所述第二网元设备发送关联变更响应，以使所述第二网元设备将所述关联变更响应转发至所述第一UE，并向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户。
结合第四方面的第六种至第八种任一种可能实现的方式，在第四方面的第十种可能实现的方式中，所述装置还包括：发送模块；
所述设置模块，还用于：
通过所述发送模块向第二UE发送变更消息；其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
通过所述接收模块接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
结合第四方面的第十种可能实现的方式，在第四方面的第十一种可能实现的方式中，所述设置模块根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，具体包括：
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
结合第四方面的第六种至第八种任一种可能实现的方式，在第四方面的第十二种可能实现的方式中，所述装置还包括：发送模块；
所述设置模块根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，具体包括：
通过所述发送模块向第二UE发送变更消息；其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
结合第四方面的第十种至第十二种任一种可能实现的方式，在第四方面的第十三种可能实现的方式中，所述发送模块向第二UE发送变更消息，具体包括：
通过定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
结合第四方面的第十种至第十三种任一种可能实现的方式，在第四方面的第十四种可能实现的方式中，所述发送模块，还用于：
向所述第一UE发送关联变更响应。
结合第四方面的第九种至第十四种任一种可能实现的方式，在第四方面 的第十五种可能实现的方式中，所述变更消息包括：所述第一MCPTT用户的用户标识。
结合第四方面的第十五种可能实现的方式，在第四方面的第十六种可能实现的方式中，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
第五方面，本发明实施例提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的装置，所述装置为第二网元设备，所述装置包括：
接收模块，用于接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
发送模块，用于向第二UE发送变更消息，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
所述接收模块，还用于接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；
所述发送模块，还用于将所述关联变更请求发送至第一网元设备。
结合第五方面，在第五方面的第一种可能实现的方式中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
结合第五方面或第五方面的第一种可能实现的方式，在第五方面的第二种可能实现的方式中，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
第六方面，本发明实施例提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的装置，所述装置为第一用户设备UE，所述装置包 括：
发送模块，用于向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；
接收模块，用于接收所述第一网元设备发送的关联变更响应。
结合第六方面，在第六方面的第一种可能实现的方式中，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
结合第六方面或第六方面的第一种可能实现的方式，在第六方面的第二种可能实现的方式中，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
结合第六方面或第六方面的第一种至第二种任一种可能实现的方式，在第六方面的第三种可能实现的方式中，所述请求信息，包括：
所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
结合第六方面或第六方面的第一种至第三种任一种可能实现的方式，在第六方面的第四种可能实现的方式中，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
第七方面，本发明实施例提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的系统，包括第四方面或第四方面的第一种至第十六种任一种所述的第一网元设备及第六方面或第六方面的第一种至第四种任一种所述的第一用户设备UE。
结合第七方面，在第七方面的第一种可能实现的方式中，还包括：第五方面或第五方面的第一种至第二种任一种所述的第二网元设备。
本发明实施例提供一种变更MCPTT用户与MCPTT群组关联关系的方法、装置及系统，通过第一网元设备接收第一UE发送的关联变更请求； 所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例一的流程图；
图2为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例二的流程图；
图3为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例三的流程图；
图4为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例四的流程图；
图5为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例五的流程图；
图6为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例六的流程图；
图7为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例七的流程图；
图8为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例八的流程图；
图9为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例九 的流程图；
图10为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十的流程图；
图11为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十一的流程图；
图12为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十二的流程图；
图13为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十三的流程图；
图14为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十四的流程图；
图15为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例一的结构示意图；
图16为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例二的结构示意图；
图17为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例三的结构示意图；
图18为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例五的结构示意图；
图19为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例六的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
图1为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例一的流程图；如图1所示，本实施例的方法可以包括：
步骤101、第一网元设备接收第一UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第一MCPTT用户为使用所述第一UE的用户；
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
需要说明的是，本发明中的UE可以是手机、计算机、平板电脑、后台控制器等任何人可以操作的设备。
步骤102、所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
本实施例中，通过第一网元设备接收第一UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
图2为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例二的流程图；如图2所示，本实施例的方法可以包括：
步骤201、第一UE向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第一MCPTT用户为使用所述第一UE的用户；
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
需要说明的是，本发明中MCPTT服务器为用于实现组会话、用户注册 的网元设备；组管理服务器(GMS，Group Management Server)，为用于管理组策略，维护组信息的网元设备。
步骤202、所述第一UE接收所述第一网元设备发送的关联变更响应。
本实施例中，通过第一UE向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；使得第一MCPTT用户能够变更第二MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
图3为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例三的流程图；本实施例的应用场景可以为：定义第一MCPTT用户的用户配置文件的MCPTT系统，定义第二MCPTT用户的用户配置文件的MCPTT系统，及定义第一MCPTT群组的MCPTT系统，三者相同；如图3所示，本实施例的方法可以包括：
步骤301、第一UE向第一MCPTT服务器发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第一MCPTT用户为使用所述第一UE的用户；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
可选的，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
可选的，所述请求信息，包括：所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
可选的，所述关联变更请求还包括：所述第一MCPTT用户的用户标识。
需要说明的是，步骤301中一条关联变更请求中可以只包含一个目标MCPTT用户(例如，第二MCPTT用户)的标识及该目标MCPTT用户的目 标MCPTT群组的标识(例如，第一MCPTT群组)；或者，一条关联变更请求中可以包括多个目标MCPTT用户的用户标识(也即，可以是一个目标MCPTT用户的用户标识列表)以及该多个目标MCPTT用户分别的目标MCPTT群组的标识；或者，一条关联变更请求中可以包括多个目标MCPTT用户的用户标识以及该多个目标MCPTT用户对应的同一个MCPTT群组的标识。
可选的，步骤301之前还可以包括：
所述第一UE根据所述第一MCPTT用户的输入，确定所述第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；或者，所述第一UE根据其他设备发送的信息，确定所述第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
步骤302、所述第一MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤303；否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
可选的，步骤302具体可以为：所述第一MCPTT服务器判断与所述第二MCPTT用户关联的MCPTT群组的个数是否小于或等于所述阈值；
步骤303、所述第一MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤304。否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
可选的，所述第一MCPTT服务器中可以预先存储了能够变更第二MCPTT用户的关联关系的其他MCPTT用户(例如，第一MCPTT用户)需要满足的条件；例如，用户所承担的角色需要为哪些角色、用户的用户优先级需要大于或等于预设优先级等。
步骤304、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
其中，所述组管理服务器为所述第一MCPTT群组的组管理服务器。
需要说明的是，当第一MCPTT服务器上保存有第一MCPTT群组的群组 策略，则不需要执行步骤304从组管理服务器获取。
需要说明的是，所述组管理服务器可以在所述第一MCPTT服务器所属的MCPTT系统中；或者，所述组管理服务器可以在所述第一MCPTT服务器所属的MCPTT系统外，多个MCPTT系统共用一个组管理服务器。
步骤305、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤306；否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
其中，所述目标关联关系为所述第一MCPTT服务器根据所述关联变更请求确定的。
可选的，所述第一MCPTT服务器根据关联变更请求，确定目标关联关系，包括：
第一MCPTT服务器将所述关联变更请求中包括的关联关系指示，作为目标关联关系。例如，当关联关系指示为去关联时，则目标关联关系为去关联；当关联关系指示为关联时，则目标关联关系为关联。
或者，
第一MCPTT服务器确定第二MCPTT用户与第一MCPTT群组当前的关联关系为去关联，且所述关联变更请求中包括的请求信息指示变更所述第一MCPTT用户与第一MCPTT群组的关联关系时，则确定目标关联关系为关联；
或者，第一MCPTT服务器确定第二MCPTT用户与第一MCPTT群组当前的关联关系为关联，且所述关联变更请求中包括的请求信息指示变更所述第一MCPTT用户与第一MCPTT群组的关联关系时，则确定目标关联关系为去关联。
可选的，所述群组策略可以为群组中用户个数的最大值、MCPTT用户的最低用户优先级等。
需要说明的是，本实施例中进行判断的步骤，步骤302、步骤303、步骤305之间并没有先后顺序的限制。
步骤306、所述第一MCPTT服务器向第二UE发送变更消息；
其中，所述第二MCPTT用户为使用所述第二UE的用户。
可选的，当定义所述第二MCPTT用户的用户配置文件的MCPTT系统与定义所述第一MCPTT群组的MCPTT系统不同时，步骤306具体可以为：
所述第一MCPTT服务器通过定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
可选的，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系(也即，步骤305中所确定出的目标关联关系)或者，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
若所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，则步骤306之后，还包括：
所述第一MCPTT服务器接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，或者，所述变更响应用于指示拒绝将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
若所述变更响应用于指示拒绝将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，则向所述第一UE发送用于指示变更失败的关联变更响应，而不再执行步骤307、步骤308。
可选的，所述变更消息可以包括：所述第一MCPTT用户的用户标识，以使所述第一MCPTT用户可以确定更改所述第一MCPTT用户与第一MCPTT群组的关联关系的MCPTT用户为所述第一MCPTT用户。
步骤307、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，步骤307与步骤306之间并没有先后顺序。
可选的，步骤307之后还可以包括：第一MCPTT服务器向组管理服务器发送第一关联信息，所述第一关联信息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系，以使所述组管理服务器将所述第二MCPTT用户与所述第一MCPTT群组的关联关系更新为所述目标关联关系。
步骤308、所述第一MCPTT服务器向所述第一UE发送用于指示变更成功的关联变更响应。
需要说明的是，步骤308与步骤307之间并没有先后顺序。
本实施例中，通过第一UE向第一MCPTT服务器发送关联变更请求(所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第一MCPTT服务器确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系，且所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之后，所述第一MCPTT服务器向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；或者，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
图4为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例四的流程图，本实施例的应用场景与图3所示实施例的应用场景相同；如图4所示，本实施例的方法可以包括：
步骤401、第一UE向第一MCPTT服务器发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
需要说明的是，步骤401与步骤301类似，在此不再赘述。
步骤402、所述第一MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤403；否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
需要说明的是，步骤402与步骤302类似，在此不再赘述。
步骤403、所述第一MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤404。否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
需要说明的是，步骤403与步骤303类似，在此不再赘述。
步骤404、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤404与步骤304类似，在此不再赘述。
步骤405、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤406；否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
需要说明的是，步骤405与步骤305类似，在此不再赘述。
步骤406、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
步骤407、所述第一MCPTT服务器向组管理服务器发送更新消息；所述更新消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；
需要说明的是，步骤407与步骤406之间并没有先后顺序。
步骤408、所述组管理服务器在接收到所述更新消息后，向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的用户。
可选的，步骤408还可以包括：所述组管理服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，由于步骤408中组管理服务器向第二UE发送变更消息的触发条件是组管理服务器接收到第一MCPTT服务器发送的更新消息；因此，步骤408也可以认为是第一MCPTT服务器向第二UE发送变更消息。
步骤409、所述第一MCPTT服务器向所述第一UE发送用于指示变更成功的关联变更响应。
需要说明的是，步骤409与步骤406-步骤408之间并没有先后顺序。
本实施例中，通过第一UE向第一MCPTT服务器发送关联变更请求(所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第一MCPTT服务器确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系，且所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之后，向组管理服务器发送更新消息，以使所述组管理服务器向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图4所示实施例与图3所示实施例的区别主要在于：1)图3所示实施例中是由第一MCPTT服务器向第二UE发送变更消息，图4所示实施例中是由组管理服务器向第二UE发送变更消息；2)图4所示实施例中变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系，图3所示实施例中变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系，或者用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
图5为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例五的流程图，本实施例的应用场景与图3所示实施例的应用场景相同；如图5所示，本实施例的方法可以包括：
步骤501、第一UE向第一MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
需要说明的是，步骤501与步骤301类似，在此不再赘述。
步骤502、所述第一MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤503；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤503、所述第一MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤504。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤503与步骤303类似，在此不再赘述。
步骤504、所述第一MCPTT服务器根据所述原始关联变更请求，向组管理服务器发送关联变更请求；
其中，所述组管理服务器为所述第一MCPTT群组的组管理服务器；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
可选的，所述关联变更请求与所述原始关联变更请求可以是同一条消息(也即，第一MCPTT服务器将接收到的原始关联变更请求直接转发至组管理服务器)；或者，所述关联变更请求与所述原始关联变更请求可以为不同的消息。
例如，当原始关联变更请求中包括目标MCPTT用户1和目标MCPTT用户2的用户标识、目标MCPTT群组1的标识及目标MCPTT群组2的标识，目标MCPTT用户1与目标MCPTT群组1对应，目标MCPTT用户2与目标MCPTT群组2对应，定义目标MCPTT群组1的MCPTT系统中的MCPTT服务器为MCPTT服务器A，定义目标MCPTT群组2的MCPTT系统中的MCPTT服务器为MCPTT服务器B；则对于目标MCPTT群组1的组管理服务器来说，其收到的关联变更请求中不包括目标MCPTT用户2及目标MCPTT群组2的相关信息；对于目标MCPTT群组2的组管理服务器来说，其收到的关联变更请求中不包括目标MCPTT用户1及目标MCPTT群组1的相关信息。
需要说明的是，无论所述原始联变更请求与所述联变更请求是否为同一消息；对于组管理服务器来说，都可以认为是组管理服务器接收到第一UE发送的关联变更请求。
步骤505、所述组管理服务器根据所述第一MCPTT群组的群组策略，判 断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤506；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤505与步骤305的区别仅在于执行主体不同，其他类似，在此不再赘述。
步骤506、所述组管理服务器向第二UE发送变更消息；
其中，所述第二MCPTT用户为使用所述第二UE的用户。
可选的，当定义所述第二MCPTT用户的用户配置文件的MCPTT系统与定义所述第一MCPTT群组的MCPTT系统不同时，步骤506具体可以为：
所述组管理服务器通过定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
可选的，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系(也即，步骤505中所确定出的目标关联关系)；或者，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
若所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，则步骤506之后，还包括：
所述组管理服务器接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，或者，所述变更响应用于指示拒绝将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
若所述变更响应用于指示拒绝将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，则向所述第一UE发送用于指示变更失败的原始关联变更响应，而不再执行步骤507-步骤509。
步骤507、所述组管理服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，步骤507与步骤506之间并没有先后顺序。
可选的，步骤507之后还可以包括：组管理服务器向第一MCPTT服务器发送第二关联信息，所述第二关联信息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系，以使所述第一MCPTT服务器将所述第二MCPTT用户与所述第一MCPTT群组的关联关系更新为所述目标关联关系。
步骤508、所述组管理服务器向所述第一MCPTT服务器发送用于指示变更成功的关联变更响应；
需要说明的是，步骤508与步骤507之间并没有先后顺序。
步骤509、所述第一MCPTT服务器根据所述关联变更响应，向所述第一UE发送原始关联变更响应。
其中，所述原始关联变更响应为与原始关联变更请求对应的响应消息；其与关联变更响应的关系，与原始关联变更请求与关联变更请求的关系类似。也即，关联变更响应与原始关联变更响应可以是同一条消息；或者，原始关联变更响应可以是第一MCPTT服务器根据一个(或多个)组管理服务器发送的关联变更响应获得。
需要说明的是，无论所述原始关联变更响应与所述关联变更响应是否为同一消息；对于组管理服务器来说，都可以认为是组管理服务器向第一UE发送关联变更响应。
本实施例中，通过第一UE向第一MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第一MCPTT服务器确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向组管理服务器发送关联变更请求；所述组管理服务器确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之后，向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；或者，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关 联关系的功能。
需要说明的是，图5所示实施例与图3所示实施例的区别主要在于：图5所示实施例中方法的执行主体主要为组管理服务器，图3所示实施例中方法的执行主体主要为第一MCPTT服务器。但是，在图3及图5所示实施例中所述判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系的步骤都由所述第一MCPTT服务器执行。
图6为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例六的流程图，本实施例的应用场景与图3所示实施例的应用场景相同；如图6所示，本实施例的方法可以包括：
步骤601、第一UE向第一MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
需要说明的是，步骤601与步骤301类似，在此不再赘述。
步骤602、所述第一MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤603；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤603、所述第一MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤604。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤603与步骤303类似，在此不再赘述。
步骤604、所述第一MCPTT服务器根据所述原始关联变更请求，向组管理服务器发送关联变更请求；
其中，所述组管理服务器为所述第一MCPTT群组的组管理服务器。
其中，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
需要说明的是，步骤604与步骤504类似，在此不再赘述。
步骤605、所述组管理服务器根据所述第一MCPTT群组的群组策略，判 断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤606；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤605与步骤505类似，在此不再赘述。
步骤606、所述组管理服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
步骤607、所述组管理服务器向所述第一MCPTT服务器发送更新消息；所述更新消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；
需要说明的是，步骤607与步骤606之间并没有先后顺序。
步骤608、所述第一MCPTT服务器在接收到所述更新消息后，向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的用户。
可选的，步骤608还可以包括：所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，由于步骤608中第一MCPTT服务器向第二UE发送变更消息的触发条件是第一MCPTT服务器接收到组管理服务器发送的更新消息；因此，步骤608也可以认为是组管理服务器向第二UE发送变更消息。
步骤609、所述第一MCPTT服务器向所述第一UE发送用于指示变更成功的原始关联变更响应。
本实施例中，通过第一UE向第一MCPTT服务器发送原始关联变更请求(所述原始关联原始变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第一MCPTT服务器确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向组管理服务器发送关联变更请求；所述组管理服务器确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之后，向第一MCPTT服务器发送更新消息， 以使所述第一MCPTT服务器向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图6所示实施例与图5所示实施例的区别主要在于：1)图5所示实施例中是由组管理服务器向第二UE发送变更消息，图6所示实施例中是由第一MCPTT服务器向第二UE发送变更消息；2)图6所示实施例中变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系，图5所示实施例中变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系，或者用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
图7为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例七的流程图，本实施例的应用场景与图3所示实施例的应用场景相同；如图7所示，本实施例的方法可以包括：
步骤701、第一UE向第一MCPTT服务器发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
需要说明的是，步骤701与步骤301类似，在此不再赘述。
步骤702、所述第一MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤703。否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
需要说明的是，步骤702与步骤303类似，在此不再赘述。
需要说明的是，本实施例中第一MCPTT服务器也可以进行步骤302的判断。
步骤703、所述第一MCPTT服务器向第二UE发送变更消息；
其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
步骤704、所述第二UE向所述第一MCPTT服务器发送变更响应；
其中，所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
需要说明的是，步骤704之前还可以包括：第二UE根据用户输入，确定所述第二MCPTT用户允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
步骤705、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤705与步骤304类似，在此不再赘述。
步骤706、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤707；否则，结束，或者向所述第一UE发送用于指示变更失败的关联变更响应。
步骤707、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
步骤708、所述第一MCPTT服务器向所述第一UE发送用于指示变更成功的关联变更响应。
需要说明的是，步骤708与步骤707之间并没有先后顺序。
本实施例中，通过第一UE向第一MCPTT服务器发送关联变更请求(所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第一MCPTT服务器确定第二MCPTT用户允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系后，进一步确定所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，并在第一MCPTT群组允许时存储所述第二MCPTT用户与所述第一MCPTT群组的目标关联关系；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图7所示实施例与图3所示实施例的区别主要在于：图 3所示实施例中是在第一MCPTT群组允许将第二MCPTT用户与第二MCPTT群组的关联关系设置为目标关联关系之后，向第二UE发送变更消息；图7所示实施例中是在第一MCPTT群组允许将第二MCPTT用户与第二MCPTT群组的关联关系设置为目标关联关系之前，就向第二UE发送变更消息，先征求第二MCPTT用户的同意。
图8为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例八的流程图；本实施例的应用场景可以为：定义第一MCPTT用户的用户配置文件的MCPTT系统，定义第二MCPTT用户的用户配置文件的MCPTT系统，及定义第一MCPTT群组的MCPTT系统两者相同，而与定义第一MCPTT群组的MCPTT系统不同；如图8所示，本实施例的方法可以包括：
步骤801、第一UE向第二MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤801与步骤301类似，在此不再赘述。
步骤802、所述第二MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤803；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤803、所述第二MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤804。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤803与步骤303的区别仅在于执行主体不同，其他类似，在此不再赘述。
需要说明的是，本实施例中进行判断的步骤，步骤802、步骤803之间并没有先后顺序的限制。
步骤804、所述第二MCPTT服务器根据所述原始关联变更请求，向第一 MCPTT服务器发送关联变更请求；
其中，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
步骤805、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤805与步骤304类似，在此不再赘述。
步骤806、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤807；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤806与步骤305类似，在此不再赘述。
步骤807、所述第一MCPTT服务器向第二UE发送变更消息；
其中，所述第二MCPTT用户为使用所述第二UE的用户。
需要说明的是，步骤807与步骤306类似，在此不再赘述。
步骤808、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，步骤808与步骤807之间并没有先后顺序。
需要说明的是，步骤808与步骤307类似，在此不再赘述。
步骤809、所述第一MCPTT服务器向所述第二MCPTT服务器发送用于指示变更成功的关联变更响应；
步骤810、所述第二MCPTT服务器根据所述关联变更响应，向所述第一UE发送原始关联变更响应。
需要说明的是，本实施例中原始关联变更请求与关联变更请求的关系，以及原始关联变更响应与关联变更响应的关系，与图5所示实施例相同。
本实施例中，通过第一UE向第二MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第二MCPTT服务器确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向第一MCPTT服务器发送关联变更请求；所述第一MCPTT服务器 确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系后，向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；或者，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图8所示实施例与图3所示实施例的区别主要在于：图8所示实施例中第一UE将原始关联变更请求发送至第二MCPTT服务器，在第二MCPTT服务器判断第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向第一MCPTT服务器发送关联变更请求；图3中第一UE直接将关联变更请求发送至第一MCPTT服务器，由第一MCPTT服务器判断第一MCPTT用户是否有权变更第二MCPTT服务器的关联关系。
需要说明的是，图8所示实施例与图3所示实施例的上述差别还可以应用于图4所示实施例中，形成新的技术方案。
图9为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例九的流程图，本实施例的应用场景与图8所示实施例的应用场景相同；如图9所示，本实施例的方法可以包括：
步骤901、第一UE向第二MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
需要说明的是，步骤901与步骤801类似，在此不再赘述。
步骤902、所述第二MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤903；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤903、所述第二MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤904。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤903与步骤803类似，在此不再赘述。
步骤904、所述第二MCPTT服务器将所述原始关联变更请求转发至第一MCPTT服务器；
需要说明的是，步骤904与步骤804类似，在此不再赘述。
步骤905、所述第一MCPTT服务器根据所述原始关联变更请求，向组管理服务器发送关联变更请求；
步骤906、所述组管理服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
需要说明的是，步骤906与步骤505类似，在此不再赘述。
步骤907、所述组管理服务器向第二UE发送变更消息；
其中，所述第二MCPTT用户为使用所述第二UE的用户。
需要说明的是，步骤907与步骤506类似，在此不再赘述。
步骤908、所述组管理服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，步骤908与步骤907之间并没有先后顺序。
需要说明的是，步骤908与步骤507类似，在此不再赘述。
步骤909、所述组管理服务器向所述第一MCPTT服务器发送用于指示变更成功的关联变更响应；
需要说明的是，步骤909与步骤908之间并没有先后顺序。
步骤910、所述第一MCPTT服务器根据所述关联变更响应，向所述第二MCPTT服务器发送原始关联变更响应；
步骤911、所述第二MCPTT服务器向所述第一UE转发所述原始关联变更响应。
需要说明的是，本实施例中原始关联变更请求与关联变更请求的关系，以及原始关联变更响应与关联变更响应的关系，与图5所示实施例相同。
本实施例中，通过第一UE向第二MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT 用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第二MCPTT服务器确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，通过第一MCPTT服务器向组管理服务器发送关联变更请求；所述组管理服务器确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之后，向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；或者，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图9所示实施例与图5所示实施例的区别主要在于：图9所示实施例中第一UE向第二MCPTT服务器发送原始关联变更请求，由第二MCPTT服务器在确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向第一MCPTT服务器发送关联变更请求；图5中第一UE直接向第一MCPTT服务器发送关联变更请求，由第一MCPTT服务器判断第一MCPTT用户是否有权变更第二MCPTT服务器的关联关系。
需要说明的是，图9所示实施例与图5所示实施例的上述差别还可以应用于图6所示实施例中，形成新的技术方案。
图10为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十的流程图，本实施例的应用场景与图8所示实施例的应用场景相同；如图10所示，本实施例的方法可以包括：
步骤1001、第一UE向第二MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤1001与步骤301类似，在此不再赘述。
步骤1002、所述第二MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤1003。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤1002与步骤303类似，在此不再赘述。
需要说明的是，本实施例中第二MCPTT服务器也可以进行步骤302的判断。
步骤1003、所述第二MCPTT服务器向第二UE发送变更消息；
其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
步骤1004、所述第二UE向所述第二MCPTT服务器发送变更响应；
其中，所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
步骤1005、所述第二MCPTT服务器根据所述原始关联变更请求，向第一MCPTT服务器发送关联变更请求；
其中，所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
其中，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
步骤1006、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤1006与步骤304类似，在此不再赘述。
步骤1007、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤1008；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤1008、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
步骤1009、所述第一MCPTT服务器向所述第二MCPTT服务器发送用于指示变更成功的关联变更响应；
步骤1010、所述第二MCPTT服务器根据所述关联变更响应，向所述第 一UE发送原始关联变更响应。
需要说明的是，第二MCPTT服务器在接收到用于指示变更成功的关联变更响应之后，还可以包括：
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
需要说明的是，本实施例中原始关联变更请求与关联变更请求的关系，以及原始关联变更响应与关联变更响应的关系，与图5所示实施例相同。
本实施例中，通过第一UE向第二MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第二MCPTT服务器确定第二MCPTT用户允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系后，向第一MCPTT服务器发送关联变更请求；第一MCPTT服务器确定所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，并在第一MCPTT群组允许时存储所述第二MCPTT用户与所述第一MCPTT群组的目标关联关系；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图10所示实施例与图7所示实施例的区别主要在于：图10所示实施例中第一UE向第二MCPTT服务器发送原始关联变更请求，由第二MCPTT服务器在判定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向第一MCPTT服务器发送关联变更请求；图7中第一UE直接将向第一MCPTT服务器发送关联变更请求，由第一MCPTT服务器判断第一MCPTT用户是否有权变更第二MCPTT服务器的关联关系。
图11为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十一的流程图，本实施例的应用场景与图8所示实施例的应用场景相同；如图11所示，本实施例的方法可以包括：
步骤1101、第一UE向第二MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
需要说明的是，步骤1101与步骤301类似，在此不再赘述。
步骤1102、所述第二MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤1103。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤1103与步骤303类似，在此不再赘述。
需要说明的是，本实施例中第二MCPTT服务器也可以进行步骤302的判断。
步骤1103、所述第二MCPTT服务器根据所述原始关联变更请求，向第一MCPTT服务器发送关联变更请求；
其中，所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
其中，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
步骤1104、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤1104与步骤304类似，在此不再赘述。
步骤1105、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤1106；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤1106、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
步骤1107、所述第一MCPTT服务器向所述第二MCPTT服务器发送用于指示变更成功的关联变更响应；
步骤1108、所述第二MCPTT服务器向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系。
可选的，第二MCPTT服务器可以通过在关联变更响应消息中包括所述 目标关联关系的方式，获得所述目标关联关系；或者，第二MCPTT服务器也可以根据第一UE发送的关联变更请求，获得所述目标关联关系。
步骤1109、所述第二MCPTT服务器根据所述关联变更响应，向所述第一UE发送原始关联变更响应。
需要说明的是，第二MCPTT服务器在接收到用于指示变更成功的关联变更响应之后，还可以包括：
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
需要说明的是，本实施例中原始关联变更请求与关联变更请求的关系，以及原始关联变更响应与关联变更响应的关系，与图5所示实施例相同
本实施例中，通过第一UE向第二MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第二MCPTT服务器确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向第一MCPTT服务器发送关联变更请求；所述第一MCPTT服务器确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之后，第二MCPTT服务器向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
图12为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十二的流程图；本实施例的应用场景可以为：定义第一MCPTT用户的用户配置文件的MCPTT系统，定义第二MCPTT用户的用户配置文件的MCPTT系统，及定义第一MCPTT群组的MCPTT系统，三者不同；如图12所示，本实施例的方法可以包括：
步骤1201、第一UE向第二MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置 文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤1201与步骤301类似，在此不再赘述。
步骤1202、所述第二MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤1203。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤1202与步骤803类似，在此不再赘述。
步骤1203、所述第二MCPTT服务器将所述原始关联变更请求转发至第三MCPTT服务器；
其中，所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
步骤1204、所述第三MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤1205；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
通过步骤1204使得所述第三MCPTT服务器可以控制所述第二MCPTT用户关联的MCPTT群组的个数。
步骤1205、所述第三MCPTT服务器根据所述原始关联变更请求，向第一MCPTT服务器发送关联变更请求；
其中，所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
其中，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
步骤1206、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤1206与步骤304类似，在此不再赘述。
步骤1207、所述第一MCPTT服务器根据所述第一MCPTT群组的群组 策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤1208；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤1207与步骤305类似，在此不再赘述。
步骤1208、所述第一MCPTT服务器向第二UE发送变更消息；
其中，所述第二MCPTT用户为使用所述第二UE的用户。
需要说明的是，步骤1208与步骤306类似，在此不再赘述。
步骤1209、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，步骤1209与步骤1208之间并没有先后顺序。
需要说明的是，步骤1209与步骤307类似，在此不再赘述。
步骤1210、所述第一MCPTT服务器向所述第三MCPTT服务器发送用于指示变更成功的关联变更响应；
步骤1211、所述第三MCPTT服务器将所述用于指示变更成功的关联变更响应转发至所述第二MCPTT服务器；
步骤1212、所述第二MCPTT服务器根据所述关联变更响应，向所述第一UE发送原始关联变更响应。
需要说明的是，本实施例中原始关联变更请求与关联变更请求的关系，以及原始关联变更响应与关联变更响应的关系，与图5所示实施例相同。
本实施例中，通过第一UE向第二MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第二MCPTT确定第一MCPTT用户有权变更所述第二MCPTT用户的关联关系后，向第三MCPTT服务器发送原始关联变更请求；所述第三MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系后，向第一MCPTT服务器发送关联变更请求；所述第一MCPTT服务器确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系后，向第二UE发送变更消息(其中，所述变更消息用于指示所述第二 MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；或者，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图12所示实施例与图8所示实施例的区别主要在于：图12所示实施例中第一MCPTT服务器接收第一UE通过第二MCPTT服务器发送的关联变更请求；图8中第一MCPTT服务器接收第一UE通过第二MCPTT服务器及第三MCPTT服务器发送的关联变更请求。
需要说明的是，图12所示实施例与图8所示实施例的上述差别还可以应用于图8所示实施例中，形成新的技术方案。
图13为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十三的流程图；本实施例的应用场景与图12所示实施例的应用场景相同；如图13所示，本实施例的方法可以包括：
步骤1301、第一UE向第二MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤1301与步骤301类似，在此不再赘述。
步骤1302、所述第二MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤1303。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤1302与步骤803类似，在此不再赘述。
步骤1303、所述第二MCPTT服务器将所述原始关联变更请求转发至第三MCPTT服务器；
其中，所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置 文件的MCPTT系统中的MCPTT服务器。
步骤1304、所述第三MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤1305；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤1305、所述第三MCPTT服务器向第二UE发送变更消息；
其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
步骤1306、所述第二UE向所述第二MCPTT服务器发送变更响应；
其中，所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
步骤1307、所述第三MCPTT服务器根据所述原始关联变更请求，向第一MCPTT服务器发送关联变更请求；
其中，所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
其中，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
步骤1308、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤1308与步骤304类似，在此不再赘述。
步骤1309、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤1310；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤1309与步骤305类似，在此不再赘述。
步骤1310、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，步骤1310与步骤307类似，在此不再赘述。
步骤1311、所述第一MCPTT服务器向所述第三MCPTT服务器发送用于指示变更成功的关联变更响应；
步骤1312、所述第三MCPTT服务器根据所述关联变更响应，向所述第二MCPTT服务器发送原始关联变更响应；
步骤1313、所述第二MCPTT服务器将原始关联变更响应转发至所述第一UE。
本实施例中，通过第一UE向第二MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第二MCPTT服务器确定第一MCPTT用户有权变更第二MCPTT用户的关联关系后，将所述原始关联变更请求转发至第三MCPTT服务器；第三MCPTT服务器确定第二MCPTT用户允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系后，向第一MCPTT服务器发送关联变更请求；第一MCPTT服务器确定所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，并在第一MCPTT群组允许时存储所述第二MCPTT用户与所述第一MCPTT群组的目标关联关系；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
需要说明的是，图13所示实施例与图10所示实施例的区别主要在于：图13所示实施例中由第三MCPTT服务器向第二UE发送变更消息；图10中由第二MCPTT服务器向第二UE发送变更消息。
图14为本发明变更MCPTT用户与MCPTT群组关联关系的方法实施例十四的流程图；本实施例的应用场景与图12所示实施例的应用场景相同；如图14所示，本实施例的方法可以包括：
步骤1401、第一UE向第二MCPTT服务器发送原始关联变更请求，所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤1401与步骤301类似，在此不再赘述。
步骤1402、所述第二MCPTT服务器判断所述第一MCPTT用户是否有权限变更所述第二MCPTT用户的关联关系；
若是，则执行步骤1403。否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
其中，所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，步骤1402与步骤803类似，在此不再赘述。
步骤1403、所述第二MCPTT服务器将所述原始关联变更请求转发至第三MCPTT服务器；
其中，所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
需要说明的是，图12-图14所示实施例中，第二MCPTT服务器可以直接将第一UE发送的原始关联变更请求转发至第三MCPTT服务器；或者，第二MCPTT服务器也可以是接收到第一UE发送的原始关联变更请求后，根据原始关联变更请求向第一MCPTT服务器发送新的消息。
步骤1404、所述第三MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定是否变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系；
若是，则执行步骤1405；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
步骤1405、所述第三MCPTT服务器根据所述原始关联变更请求，向第一MCPTT服务器发送关联变更请求；
其中，所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
其中，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系。
步骤1406、所述第一MCPTT服务器从组管理服务器获取所述第一MCPTT群组的群组策略；
需要说明的是，步骤1406与步骤304类似，在此不再赘述。
步骤1407、所述第一MCPTT服务器根据所述第一MCPTT群组的群组策略，判断所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；
若是，则执行步骤1408；否则，结束，或者向所述第一UE发送用于指示变更失败的原始关联变更响应。
需要说明的是，步骤1407与步骤305类似，在此不再赘述。
步骤1408、所述第一MCPTT服务器存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
需要说明的是，步骤1408与步骤307类似，在此不再赘述。
步骤1409、所述第一MCPTT服务器向所述第三MCPTT服务器发送用于指示变更成功的关联变更响应；
步骤1410、所述第三MCPTT服务器向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系。
可选的，第三MCPTT服务器可以通过在关联变更响应消息中包括所述目标关联关系的方式，获得所述目标关联关系；或者，第三MCPTT服务器也可以根据第一UE发送的关联变更请求，获得所述目标关联关系。
步骤1411、所述第三MCPTT服务器根据所述关联变更响应，向所述第二MCPTT服务器发送原始关联变更响应；
需要说明的是，步骤1411与步骤1410并没有先后关系。
步骤1412、所述第二MCPTT服务器将所述原始关联变更响应转发至所述第一UE。
需要说明的是，本实施例中原始关联变更请求与关联变更请求的关系，以及原始关联变更响应与关联变更响应的关系，与图5所示实施例相同。
本实施例中，通过第一UE向第二MCPTT服务器发送原始关联变更请求(所述原始关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系)；第二MCPTT服务器确定第一MCPTT用户有权变更第二MCPTT用户的关联关系后，将所述原始关联变更请求转发至第三MCPTT服务器；第三MCPTT服务器根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定变更所述第 二MCPTT用户与所述第一MCPTT群组的关联关系后，向第一MCPTT服务器发送关联变更响应；第一MCPTT服务器确定所述第一MCPTT群组是否允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；并第一MCPTT服务器确定第一MCPTT群组允许后，第三MCPTT服务器向第二UE发送变更消息(其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系)；使得第一MCPTT用户能够变更第一MCPTT用户与第一MCPTT群组的关联关系；从而实现了一个MCPTT用户变更其他MCPTT用户与群组关联关系的功能。
图15为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例一的结构示意图；所述装置为第一网元设备，如图15所示，所述装置包括：接收模块1501和设置模块1502。其中，接收模块1501，用于接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；设置模块1502，用于根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
本实施例的装置，可以用于执行图1所示方法实施例的技术方案，其实现原理和技术效果类似，此处不再赘述。
图16为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例二的结构示意图；如图16所示，本实施例的装置在图15所示装置结构的基础上，进一步的，还可以包括：发送模块1503。
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
可选的，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
可选的，所述请求信息，包括：
所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识； 或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
可选的，设置模块1502，还用于：确定所述第一MCPTT用户有权限变更所述第二MCPTT用户的关联关系。
可选的，设置模块1502，还用于：根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
可选的，设置模块1502根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系，具体包括：
根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述目标关联关系为所述设置模块根据所述关联变更请求确定的。
可选的，设置模块1502，还用于：根据所述第一MCPTT群组的群组策略，确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
可选的，接收模块1501，具体用于：
接收所述第一UE通过第二网元设备发送的所述关联变更请求；
其中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
方式1：设置模块1502根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，具体包括：
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
通过发送模块1503向所述第二网元设备发送关联变更响应，以使所述第二网元设备将所述关联变更响应转发至所述第一UE，并向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为目标关联关系；所述第二MCPTT用户为使用所述第二UE 的MCPTT用户。
方式2：设置模块1502，还用于：
通过发送模块1503向第二UE发送变更消息；其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
通过接收模块1501接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
在方式2的基础上，可选的，设置模块1502根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，具体包括：存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
方式3：可选的，设置模块1502根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，具体包括：
通过发送模块1503向第二UE发送变更消息；其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
可选的，发送模块1503向第二UE发送变更消息，具体包括：
通过定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
在方式2和方式3的基础上，可选的，发送模块1503，还用于向所述第一UE发送关联变更响应。
可选的，所述变更消息包括：所述第一MCPTT用户的用户标识。
可选的，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
本实施例的装置，可以用于执行图3-图14所示方法实施例第一MCPTT 服务器或组管理服务器侧的技术方案，其实现原理和技术效果类似，此处不再赘述。
图17为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例三的结构示意图；所述装置为第二网元设备，如图17所示，所述装置包括：接收模块1701和发送模块1702。其中，接收模块1701，用于接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；发送模块1702，用于向第二UE发送变更消息，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；接收模块1701，还用于接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；发送模块1702，还用于将所述关联变更请求发送至第一网元设备。
可选的，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
本实施例的装置，可以用于执行图10所示方法实施例第二MCPTT服务器，及图13所示方法实施例第三MCPTT服务器侧的技术方案，其实现原理和技术效果类似，此处不再赘述。
变更MCPTT用户与MCPTT群组关联关系的装置实施例四
本实施例的装置为第一UE；本实施例的结构与图17所示装置的结构类似，同样可以包括发送模块和接收模块。其中，发送模块，用于向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关 联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；接收模块，用于接收所述第一网元设备发送的关联变更响应。
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
可选的，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
可选的，所述请求信息，包括：所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
可选的，所述关联变更请求，包括：所述第一MCPTT用户的用户标识。
本实施例的装置，可以用于执行图3-图14所示方法实施例第一UE侧的技术方案，其实现原理和技术效果类似，此处不再赘述。
本发明还提供一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的系统，包括：变更MCPTT用户与MCPTT群组关联关系的装置实施例一或实施例二所述的第一网元设备，及变更MCPTT用户与MCPTT群组关联关系的装置实施例四所述的第一UE。
可选的，本实施例的系统还可以包括：变更MCPTT用户与MCPTT群组关联关系的装置实施例三所述的第二网元设备。
本实施例的系统，可以用于执行图3-图13所示方法实施例的技术方案，其实现原理和技术效果类似，此处不再赘述。
图18为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例五的结构示意图；所述装置为第一网元设备，如图18所示，所述装置包括：接收器1801和处理器1802。其中，接收器1801，用于接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；处理器1802，用于根据所述关联变更请求，设置所述第二MCPTT用户与所述第一 MCPTT群组的关联关系。
本实施例的装置，可以用于执行图1所示方法实施例的技术方案，其实现原理和技术效果类似，此处不再赘述。
图19为本发明变更MCPTT用户与MCPTT群组关联关系的装置实施例六的结构示意图；如图19所示，本实施例的装置在图18所示装置结构的基础上，进一步的，还可以包括：发送器1803。
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
可选的，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
可选的，所述请求信息，包括：所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
可选的，处理器1802，还用于：确定所述第一MCPTT用户有权限变更所述第二MCPTT用户的关联关系。
可选的，处理器1802，还用于：根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
可选的，处理器1802根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系，具体包括：
根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述目标关联关系为所述设置模块根据所述关联变更请求确定的。
可选的，处理器1802，还用于：根据所述第一MCPTT群组的群组策略，确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
可选的，接收器1801，具体用于：
接收所述第一UE通过第二网元设备发送的所述关联变更请求；
其中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
方式1：处理器1802根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，具体包括：
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
通过发送器1803向所述第二网元设备发送关联变更响应，以使所述第二网元设备将所述关联变更响应转发至所述第一UE，并向第二UE发送变更消息；
其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户。
方式2：处理器1802，还用于：
通过发送器1803向第二UE发送变更消息；其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
通过接收器1801接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
在方式2的基础上，可选的，处理器1802根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，具体包括：存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
方式3：可选的，处理器1802根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，具体包括：
通过发送器1803向第二UE发送变更消息；其中，所述变更消息用于指 示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
可选的，发送器1803向第二UE发送变更消息，具体包括：
通过定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
在方式2和方式3的基础上，可选的，发送器1803，还用于向所述第一UE发送关联变更响应。
本实施例的装置，可以用于执行图3-图14所示方法实施例第一MCPTT服务器或组管理服务器侧的技术方案，其实现原理和技术效果类似，此处不再赘述。
变更MCPTT用户与MCPTT群组关联关系的装置实施例七
本实施例的装置为第二网元设备；本实施例的结构与图19所示装置的结构类似，同样可以包括接收器、处理器和发送器。其中，处理器，用于通过接收器接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；处理器，还用于通过发送器向第二UE发送变更消息，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；处理器，还用于通过接收器接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；处理器，还用于通过发送器将所述关联变更请求发送至第一网元设备。
可选的，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器， 或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
本实施例的装置，可以用于执行图10所示方法实施例第二MCPTT服务器，及图13所示方法实施例第三MCPTT服务器侧的技术方案，其实现原理和技术效果类似，此处不再赘述。
变更MCPTT用户与MCPTT群组关联关系的装置实施例八
本实施例的装置为第一UE；本实施例的结构与图19所示装置的结构类似，同样可以包括接收器、处理器和发送器。其中，处理器，用于通过发送器向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；处理器，还用于通过接收器接收所述第一网元设备发送的关联变更响应。
可选的，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
可选的，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
可选的，所述请求信息，包括：所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
本实施例的装置，可以用于执行图3-图14所示方法实施例第一UE侧的技术方案，其实现原理和技术效果类似，此处不再赘述。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (52)

  1. 一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的方法，其特征在于，包括：
    第一网元设备接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
    所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
  3. 根据权利要求1或2所述的方法，其特征在于，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述请求信息，包括：
    所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，设置所述第一MCPTT用户与所述第一MCPTT群组的关联关系之前，还包括：
    所述第一网元设备确定所述第一MCPTT用户有权限变更所述第二MCPTT用户的关联关系。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，设置所述第一MCPTT用户与所述第一MCPTT群组的关联关系之前，还包括：
    所述第一网元设备根据所述第二MCPTT用户关联的MCPTT群组个数的 阈值确定变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系，包括：
    所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述目标关联关系为所述第一网元设备根据所述关联变更请求确定的。
  8. 根据权利要求7所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系之前，还包括：
    所述第一网元设备根据所述第一MCPTT群组的群组策略，确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第一网元设备接收第一UE发送的关联变更请求，包括：
    所述第一网元设备接收所述第一UE通过第二网元设备发送的所述关联变更请求；
    其中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
  10. 根据权利要求9所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，包括：
    所述第一网元设备存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
    所述第一网元设备向所述第二网元设备发送关联变更响应，以使所述第二网元设备将所述关联变更响应转发至所述第一UE，并向第二UE发送变更消息；
    其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT 群组的关联关系为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户。
  11. 根据权利要求7-9任一项所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系之前，还包括：
    所述第一网元设备向第二UE发送变更消息；其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
    所述第一网元设备接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
  12. 根据权利要求11所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，包括：
    所述第一网元设备存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
  13. 根据权利要求7-9任一项所述的方法，其特征在于，所述第一网元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，包括：
    所述第一网元设备向第二UE发送变更消息；其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
    所述第一网元设备存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，所述第一网元设备向第二UE发送变更消息，包括：
    所述第一网元设备通过定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
  15. 根据权利要求11-14任一项所述的方法，其特征在于，所述第一网 元设备根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系之后，还包括：
    所述第一网元设备向所述第一UE发送关联变更响应。
  16. 根据权利要求10-15任一项所述的方法，其特征在于，所述变更消息包括：所述第一MCPTT用户的用户标识。
  17. 根据权利要求16所述的方法，其特征在于，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
  18. 一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的方法，其特征在于，包括：
    第二网元设备接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
    所述第二网元设备向第二UE发送变更消息，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
    所述第二网元设备接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；
    所述第二网元设备将所述关联变更请求发送至第一网元设备。
  19. 根据权利要求18所述的方法，其特征在于，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
  20. 根据权利要求18或19所述的方法，其特征在于，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
  21. 一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的方法，其特征在于，包括：
    第一用户设备UE向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；
    所述第一UE接收所述第一网元设备发送的关联变更响应。
  22. 根据权利要求21所述的方法，其特征在于，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
  23. 根据权利要求21或22所述的方法，其特征在于，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
  24. 根据权利要求21-23任一项所述的方法，其特征在于，所述请求信息，包括：
    所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
  25. 根据权利要求21-24任一项所述的方法，其特征在于，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
  26. 一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的装置，所述装置为第一网元设备，其特征在于，所述装置包括：
    接收模块，用于接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
    设置模块，用于根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
  27. 根据权利要求26所述的装置，其特征在于，所述第一网元设备为所 述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
  28. 根据权利要求26或27所述的装置，其特征在于，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
  29. 根据权利要求26-28任一项所述的装置，其特征在于，所述请求信息，包括：
    所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
  30. 根据权利要求26-29任一项所述的装置，其特征在于，所述设置模块，还用于：
    确定所述第一MCPTT用户有权限变更所述第二MCPTT用户的关联关系。
  31. 根据权利要求26-30任一项所述的装置，其特征在于，所述设置模块，还用于：
    根据所述第二MCPTT用户关联的MCPTT群组个数的阈值确定变更所述第二MCPTT用户与所述第一MCPTT群组的关联关系。
  32. 根据权利要求26-31任一项所述的装置，其特征在于，所述设置模块根据所述关联变更请求，设置所述第二MCPTT用户与所述第一MCPTT群组的关联关系，具体包括：
    根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述目标关联关系为所述设置模块根据所述关联变更请求确定的。
  33. 根据权利要求32所述的装置，其特征在于，所述设置模块，还用于：
    根据所述第一MCPTT群组的群组策略，确定所述第一MCPTT群组允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
  34. 根据权利要求32或33所述的装置，其特征在于，所述接收模块， 具体用于：
    接收所述第一UE通过第二网元设备发送的所述关联变更请求；
    其中，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
  35. 根据权利要求34所述的装置，其特征在于，所述装置还包括：发送模块；
    所述设置模块根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系，具体包括：
    存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系；
    通过所述发送模块向所述第二网元设备发送关联变更响应，以使所述第二网元设备将所述关联变更响应转发至所述第一UE，并向第二UE发送变更消息；
    其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户。
  36. 根据权利要求32-34任一项所述的装置，其特征在于，所述装置还包括：发送模块；
    所述设置模块，还用于：
    通过所述发送模块向第二UE发送变更消息；其中，所述变更消息用于请求所述第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
    通过所述接收模块接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系。
  37. 根据权利要求36所述的装置，其特征在于，所述设置模块根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系 设置为所述目标关联关系，具体包括：
    存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
  38. 根据权利要求32-34任一项所述的装置，其特征在于，所述装置还包括：发送模块；
    所述设置模块根据所述关联变更请求，将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系，具体包括：
    通过所述发送模块向第二UE发送变更消息；其中，所述变更消息用于指示所述第二MCPTT用户与所述第一MCPTT群组的关联关系为所述目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
    存储所述第二MCPTT用户与所述第一MCPTT群组的所述目标关联关系。
  39. 根据权利要求36-38任一项所述的装置，其特征在于，所述发送模块向第二UE发送变更消息，具体包括：
    通过定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器向所述第二UE发送所述变更消息。
  40. 根据权利要求36-39任一项所述的装置，其特征在于，所述发送模块，还用于：
    向所述第一UE发送关联变更响应。
  41. 根据权利要求35-40任一项所述的装置，其特征在于，所述变更消息包括：所述第一MCPTT用户的用户标识。
  42. 根据权利要求41所述的装置，其特征在于，所述关联变更请求，还包括：所述第一MCPTT用户的用户标识。
  43. 一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的装置，所述装置为第二网元设备，其特征在于，所述装置包括：
    接收模块，用于接收第一用户设备UE发送的关联变更请求；所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的MCPTT用户；
    发送模块，用于向第二UE发送变更消息，所述变更消息用于请求所述 第二MCPTT用户将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为目标关联关系；所述第二MCPTT用户为使用所述第二UE的MCPTT用户；
    所述接收模块，还用于接收所述第二UE发送的变更响应；所述变更响应用于指示允许将所述第二MCPTT用户与所述第一MCPTT群组的关联关系设置为所述目标关联关系；
    所述发送模块，还用于将所述关联变更请求发送至第一网元设备。
  44. 根据权利要求43所述的装置，其特征在于，所述第二网元设备为第二MCPTT服务器或第三MCPTT服务器；所述第二MCPTT服务器为定义所述第一MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器；所述第三MCPTT服务器为定义所述第二MCPTT用户的用户配置文件的MCPTT系统中的MCPTT服务器。
  45. 根据权利要求43或44所述的装置，其特征在于，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为第一MCPTT服务器；所述第一MCPTT服务器为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
  46. 一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的装置，所述装置为第一用户设备UE，其特征在于，所述装置包括：
    发送模块，用于向第一网元设备发送关联变更请求，所述关联变更请求包括请求信息，所述请求信息用于指示第一MCPTT用户请求变更第二MCPTT用户与第一MCPTT群组的关联关系，以使所述第一网元设备根据所述关联变更请求设置第二MCPTT用户与第一MCPTT群组的关联关系；所述第一MCPTT用户为使用所述第一UE的用户；
    接收模块，用于接收所述第一网元设备发送的关联变更响应。
  47. 根据权利要求46所述的装置，其特征在于，所述第一网元设备为所述第一MCPTT群组的组管理服务器，或者，所述第一网元设备为定义所述第一MCPTT群组的MCPTT系统中的MCPTT服务器。
  48. 根据权利要求46或47所述的装置，其特征在于，所述关联变更请求还包括：关联关系指示，所述关联关系指示用于指示请求所述第二MCPTT用户与所述第一MCPTT群组关联或者去关联。
  49. 根据权利要求46-48任一项所述的装置，其特征在于，所述请求信息，包括：
    所述第二MCPTT用户的用户标识及所述第一MCPTT群组的群组标识；或者，所述第二MCPTT用户所属的第二MCPTT群组的群组标识及所述第一MCPTT群组的群组标识。
  50. 根据权利要求46-49任一项所述的装置，其特征在于，所述关联变更请求，包括：所述第一MCPTT用户的用户标识。
  51. 一种变更紧急任务即按即说MCPTT用户与MCPTT群组关联关系的系统，其特征在于，包括权利要求26-42任一项所述的第一网元设备及权利要求46-50任一项所述的第一用户设备UE。
  52. 根据权利要求51所述的系统，其特征在于，还包括：权利要求43-45任一项所述的第二网元设备。
PCT/CN2015/086516 2015-08-10 2015-08-10 变更mcptt用户与mcptt群组关联关系的方法、装置及系统 WO2017024470A1 (zh)

Priority Applications (12)

Application Number Priority Date Filing Date Title
EP15900668.3A EP3310108B1 (en) 2015-08-10 2015-08-10 Method and apparatus for changing association relationship between mcptt user and mcptt group
SG11201800035SA SG11201800035SA (en) 2015-08-10 2015-08-10 Method, apparatus, and system for changing association relationship between mcptt user and mcptt group
JP2018506389A JP6609690B2 (ja) 2015-08-10 2015-08-10 Ｍｃｐｔｔユーザとｍｃｐｔｔグループとの間の関連性関係を変更する方法、装置、及びシステム
EP20171897.0A EP3780892B1 (en) 2015-08-10 2015-08-10 Method, apparatus, and system for changing association relationship between mcptt user and mcptt group
MYPI2018700076A MY193852A (en) 2015-08-10 2015-08-10 Method, apparatus, and system for changing association relationship between mcptt user and mcptt group
KR1020187002288A KR102005204B1 (ko) 2015-08-10 2015-08-10 Mcptt 사용자와 mcptt 그룹 간의 연관 관계를 변경하기 위한 방법, 장치 및 시스템
CN202010123485.9A CN111432354B (zh) 2015-08-10 2015-08-10 变更mcptt用户与mcptt群组关联关系的方法、装置及系统
CN201580024970.8A CN107005976B (zh) 2015-08-10 2015-08-10 变更mcptt用户与mcptt群组关联关系的方法、装置及系统
PCT/CN2015/086516 WO2017024470A1 (zh) 2015-08-10 2015-08-10 变更mcptt用户与mcptt群组关联关系的方法、装置及系统
RU2018107265A RU2684574C1 (ru) 2015-08-10 2015-08-10 Система, способ и устройство для изменения ассоциации взаимосвязи между mcptt пользователем и mcptt группой
US15/892,713 US10841750B2 (en) 2015-08-10 2018-02-09 Method, apparatus, and system for changing association relationship between MCPTT user and MCPTT group
US17/082,696 US11617063B2 (en) 2015-08-10 2020-10-28 Method, apparatus, and system for changing association relationship between MCPTT user and MCPTT group

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/086516 WO2017024470A1 (zh) 2015-08-10 2015-08-10 变更mcptt用户与mcptt群组关联关系的方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/892,713 Continuation US10841750B2 (en) 2015-08-10 2018-02-09 Method, apparatus, and system for changing association relationship between MCPTT user and MCPTT group

Publications (1)

Publication Number Publication Date
WO2017024470A1 true WO2017024470A1 (zh) 2017-02-16

Family

ID=57983444

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/086516 WO2017024470A1 (zh) 2015-08-10 2015-08-10 变更mcptt用户与mcptt群组关联关系的方法、装置及系统

Country Status (9)

Country Link
US (2) US10841750B2 (zh)
EP (2) EP3310108B1 (zh)
JP (1) JP6609690B2 (zh)
KR (1) KR102005204B1 (zh)
CN (2) CN111432354B (zh)
MY (1) MY193852A (zh)
RU (1) RU2684574C1 (zh)
SG (1) SG11201800035SA (zh)
WO (1) WO2017024470A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170374633A1 (en) * 2015-03-12 2017-12-28 Huawei Technologies Co., Ltd. Real-time transport protocol rtp packet transmission method and apparatus
CN110830925A (zh) * 2018-08-14 2020-02-21 华为技术有限公司 一种用户群组的会话管理方法及装置
EP3713372A4 (en) * 2017-11-30 2020-12-02 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR GENERATING A USER GROUP

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822644B (zh) * 2019-11-18 2022-04-26 成都鼎桥通信技术有限公司 群组建立方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101072390A (zh) * 2006-05-12 2007-11-14 中兴通讯股份有限公司 一种数字集群系统的动态群组管理方法
WO2015050395A1 (en) * 2013-10-03 2015-04-09 Lg Electronics Inc. Method and apparatus for handling radio resources for device-to-device operation upon mobility in wireless communication system
CN104602351A (zh) * 2015-01-08 2015-05-06 上海华为技术有限公司 一种实现宽带集群业务的方法、装置及系统
CN104618349A (zh) * 2015-01-13 2015-05-13 上海华为技术有限公司 一种集群通信系统、服务器及通信方法

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7711382B2 (en) * 2004-02-27 2010-05-04 Motorola, Inc. Method for dynamic group call
US8150437B2 (en) * 2004-09-09 2012-04-03 Nextel Communications Company L.P. Architecture to facilitate the monetization of disparate, inter-worked pushed to talk technologies
EP1701571B1 (en) * 2005-03-09 2012-06-13 Alcatel Lucent Method and server for performing a dynamic push-to-talk service
JP4823876B2 (ja) * 2006-11-29 2011-11-24 株式会社エヌ・ティ・ティ・ドコモ 呼制御システム及びメッセージ送信方法
CN101137114B (zh) * 2006-12-20 2010-04-14 中兴通讯股份有限公司 一种获得数字集群系统激活呼叫信息的方法
CN101540957A (zh) * 2008-03-19 2009-09-23 中兴通讯股份有限公司 一种具有权限的集群终端及其实现群组成员管理的方法
CN102137338B (zh) * 2010-01-22 2014-08-27 深圳市源通世纪科技有限公司 一键通业务用户管理、呈现及会话状态管理的方法及系统
EP2854471A1 (en) * 2013-09-27 2015-04-01 Alcatel Lucent Floor management method, system, node for dormant PTT UE
WO2015065022A1 (ko) * 2013-10-28 2015-05-07 삼성전자 주식회사 이동성에 강인한 그룹 통신을 위한 방법 및 장치
WO2015102445A1 (ko) * 2014-01-05 2015-07-09 엘지전자 주식회사 근접 서비스 기반의 그룹 통신을 중계하는 방법 및 사용자 장치
WO2017003175A1 (en) * 2015-06-29 2017-01-05 Samsung Electronics Co., Ltd. Method and apparatus for providing service in a wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101072390A (zh) * 2006-05-12 2007-11-14 中兴通讯股份有限公司 一种数字集群系统的动态群组管理方法
WO2015050395A1 (en) * 2013-10-03 2015-04-09 Lg Electronics Inc. Method and apparatus for handling radio resources for device-to-device operation upon mobility in wireless communication system
CN104602351A (zh) * 2015-01-08 2015-05-06 上海华为技术有限公司 一种实现宽带集群业务的方法、装置及系统
CN104618349A (zh) * 2015-01-13 2015-05-13 上海华为技术有限公司 一种集群通信系统、服务器及通信方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170374633A1 (en) * 2015-03-12 2017-12-28 Huawei Technologies Co., Ltd. Real-time transport protocol rtp packet transmission method and apparatus
US10448348B2 (en) * 2015-03-12 2019-10-15 Huawei Technologies Co., Ltd. Real-time transport protocol RTP packet transmission method and apparatus
EP3713372A4 (en) * 2017-11-30 2020-12-02 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR GENERATING A USER GROUP
CN110830925A (zh) * 2018-08-14 2020-02-21 华为技术有限公司 一种用户群组的会话管理方法及装置
CN110830925B (zh) * 2018-08-14 2021-10-19 华为技术有限公司 一种用户群组的会话管理方法及装置
US11812496B2 (en) 2018-08-14 2023-11-07 Huawei Technologies Co., Ltd. User group session management method and apparatus

Also Published As

Publication number Publication date
KR102005204B1 (ko) 2019-07-29
EP3310108B1 (en) 2020-05-13
JP6609690B2 (ja) 2019-11-20
US20210044939A1 (en) 2021-02-11
CN111432354B (zh) 2021-09-14
RU2684574C1 (ru) 2019-04-09
SG11201800035SA (en) 2018-03-28
CN107005976A (zh) 2017-08-01
CN111432354A (zh) 2020-07-17
JP2018527812A (ja) 2018-09-20
EP3310108A4 (en) 2018-07-11
KR20180021835A (ko) 2018-03-05
US20180167786A1 (en) 2018-06-14
US10841750B2 (en) 2020-11-17
MY193852A (en) 2022-10-28
US11617063B2 (en) 2023-03-28
EP3780892B1 (en) 2023-10-04
CN107005976B (zh) 2020-03-10
EP3310108A1 (en) 2018-04-18
EP3780892A1 (en) 2021-02-17

Similar Documents

Publication Publication Date Title
EP2800302B1 (en) Method, device and system for determining a policy and charging rule function
EP3723413B1 (en) Policy control method, apparatus, and system
US11617063B2 (en) Method, apparatus, and system for changing association relationship between MCPTT user and MCPTT group
US11128991B2 (en) Method, apparatus, and system for floor control on multiple MCPTT systems
US10470003B2 (en) Method for regrouping multiple groups and device
US11108837B2 (en) Media downlink transmission control method and related device
US11251981B2 (en) Communication method and apparatus
CN109155939A (zh) 一种负载迁移方法、装置及系统
WO2021062738A1 (zh) 通信处理方法以及通信处理装置
US11510030B2 (en) Method for setting MCPTT group, device, and system
WO2016197637A1 (zh) 一种实现远程访问的方法、AllJoyn网关代理、云服务器及移动设备
WO2024020760A1 (zh) 一种QoS流的控制方法、装置及计算机存储介质
WO2022160104A1 (zh) 应用功能会话处理方法、应用功能会话处理装置及存储介质
US9615362B2 (en) Method and apparatus used for communication
US20160036664A1 (en) Continued deep packet inspection classification after roaming
TW202306356A (zh) 網路切片允入控制
US9203958B1 (en) System, method, and computer program for communication channel-independent business flow management
TW202029700A (zh) 即時診斷方法及系統
KR20110110456A (ko) 모바일 단말, 올웨이즈 온 기반의 데이터 푸쉬 방법 및 시스템
US20170048685A1 (en) Real-Time Parental Monitoring

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: 15900668

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2015900668

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20187002288

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018506389

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 11201800035S

Country of ref document: SG

WWE Wipo information: entry into national phase

Ref document number: 2018107265

Country of ref document: RU