Description
Group affiliation is a core concept in the Mission Critical Push To Talk (MCPTT) service defined by 3GPP in TS 23.179. In MCPTT, communication is organised around groups: a user talks to a group rather than to an individual. Before a user can participate in group communication, the network must know which groups that user is interested in. Group affiliation is precisely the mechanism that establishes and maintains this knowledge. It answers the question: 'which MCPTT groups does this user currently want to be part of?'
The affiliation procedure can be triggered in three distinct ways. First, it can be performed explicitly by the MCPTT user, for example by selecting a group on the MCPTT UE or by pressing a dedicated group-select button. Second, it can be performed implicitly by the MCPTT UE, for instance when the UE automatically affiliates to a preconfigured default group upon power-on or upon entering a particular coverage area. Third, it can be performed implicitly by the MCPTT service itself, for example when an emergency call requires the user to be affiliated to an emergency group, or when the service performs regrouping (dynamic group reorganisation) and needs to attach users to a newly formed group.
Architecturally, affiliation is handled between the MCPTT UE and the MCPTT server, with the group management server holding the authoritative definition of groups and their members. When a user affiliates to a group, the MCPTT server records the affiliation state and uses it to decide whether to deliver group communications (such as group call announcements) to that user. Affiliation is therefore a prerequisite for receiving group traffic: an unaffiliated user will not be paged or alerted for group calls. Affiliation state is typically maintained for the duration of the user's session and can be revoked or changed at any time.
Group affiliation interacts closely with group membership. Membership defines which groups a user is allowed to join, while affiliation defines which of those groups the user currently wants to receive. A user may be a member of many groups but affiliate only to a subset at any given time, which conserves radio resources and avoids unnecessary paging. The MCPTT server uses affiliation information to route group call requests only to affiliated users, making affiliation a key scalability mechanism in large mission-critical deployments.
The concept was introduced in Release 13 as part of the first MCPTT specification and has remained stable since. It is defined in TS 23.179 (functional architecture and information flows) and TS 23.779 (application layer). Because affiliation directly affects whether a user receives group calls, it is a fundamental building block for push-to-talk services used by public safety organisations such as police, fire and ambulance services.
Purpose & Motivation
Group affiliation exists to solve a fundamental problem in group-based mission-critical communication: how does the network know which users currently want to receive traffic for which groups? Without affiliation, the network would have to deliver every group call to every member of every group, which would waste radio resources, overload devices and annoy users with irrelevant traffic.
Before MCPTT, push-to-talk systems often relied on static group membership and always-on delivery, which scaled poorly and gave users little control. Group affiliation introduces a dynamic, user-controllable layer on top of static membership: users can choose which groups they are actively listening to, while the network can also affiliate users automatically for emergency or regrouping scenarios. This balances user control, network efficiency and mission-critical reliability.
The three affiliation modes (explicit user, implicit UE, implicit service) were motivated by different operational needs. Explicit affiliation gives users control in everyday operations. Implicit UE affiliation supports hands-free and automatic scenarios. Implicit service affiliation ensures that critical users are always reachable during emergencies, even if they did not manually affiliate. Together they make MCPTT group communication both efficient and dependable.
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Group affiliation, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.179 vd50 | MCPTT Functional Architecture | Rel-13 read |
| TS 23.779 vd00 | MCPTT over LTE Stage 2 Study | Rel-13 read |