Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Identifier

Conversation identifier

Conversation Identifier

Identifier →

Conversation identifier is a universally unique identifier that identifies a series of related MCData transactions and enables correlation of messages within a conversation across MCData services, ensuring proper grouping and ordering.

Introduced
Rel-14
Where
Services › IMS
Specifications
2 specs
Conversation identifier Description Purpose What changed Neighbours Specifications

Description

The Conversation Identifier is a key concept in Mission Critical Data (MCData) services defined by 3GPP. It is a universally unique identifier (UUID) assigned to a series of related MCData transactions, allowing the network and applications to group and manage messages that belong to the same conversation. This identifier is essential for maintaining context and ordering in MCData communication, which is used by public safety and mission-critical users for exchanging data such as text messages, files, and location information.

In the MCData architecture, the Conversation Identifier is generated by the originating MCData client or server and included in the signaling and media messages. It is used by MCData servers to route messages to the correct recipients, to enforce policies, and to provide conversation-based features like message threading, delivery status, and history. The identifier is typically a UUID as defined in RFC 4122, ensuring global uniqueness without central coordination. The identifier remains constant for all transactions within a conversation, enabling correlation even when messages are sent over different bearers or at different times.

The Conversation Identifier is defined in 3GPP TS 23.282 (MCData functional architecture) and TS 23.783 (MCData media plane). It is part of the MCData protocol stack, which operates over the IP multimedia subsystem (IMS) and uses SIP for session control and MSRP for media transport. The identifier is carried in SIP headers or MSRP messages, depending on the transaction type. For example, in a one-to-one text message, the Conversation Identifier is included in the SIP MESSAGE request, allowing the recipient to associate the message with an existing conversation.

Key components include the MCData client, which generates the identifier for new conversations, and the MCData server, which validates and uses it for routing and storage. The identifier also plays a role in security, as it can be used to enforce access control and prevent unauthorized access to conversations. Additionally, the identifier supports features like conversation merging, where multiple conversations can be combined if they share the same identifier, and conversation splitting, where a new identifier is created for a subset of messages.

The Conversation Identifier is crucial for interoperability between different MCData systems and for integration with other mission-critical services like MCPTT (Mission Critical Push-to-Talk) and MCVideo. It enables a unified user experience across services, allowing users to view a conversation that spans voice, video, and data. As MCData services evolve, the identifier continues to be a foundational element for conversation management and data correlation.

Purpose & Motivation

The Conversation Identifier was introduced to solve the problem of correlating related MCData transactions in mission-critical communication. In traditional messaging systems, each message is independent, making it difficult to group messages into conversations, especially when messages are sent over unreliable networks or through multiple servers. The identifier provides a persistent, unique reference that ties together all messages in a conversation, enabling features like message threading, delivery tracking, and conversation history.

Before its introduction, MCData services lacked a standardized way to identify conversations, leading to interoperability issues and limited functionality. The identifier addresses these limitations by providing a globally unique, standardized mechanism that works across vendors and networks. It also supports advanced features such as conversation continuity when users switch devices or networks, and conversation synchronization across multiple clients.

The motivation for a universally unique identifier stems from the need for scalability and decentralization. Using a UUID allows identifiers to be generated independently by clients without coordination, reducing latency and single points of failure. This is particularly important in mission-critical environments where network availability may be intermittent. The Conversation Identifier thus enhances the reliability and usability of MCData services, making them more suitable for public safety and other critical communications.

What changed in its specifications

The latest release-to-release comparison of specifications that define Conversation identifier. Each summary describes the whole specification, not only this term.

TS 23.282Rel-18 → Rel-19

Adds ad hoc group data session leave, standalone data/FD, criteria modification procedures, and new information elements.

Full comparison in TS 23.282 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-14 Initial

Initial definition introduced: a universally unique identifier that identifies a series of related MCData transactions. This established the foundation for conversation management in MCData services.

Definition carried over unchanged from Rel-14, reflecting stability as MCData services were refined.

Definition carried over unchanged, with no textual modifications.

Definition carried over unchanged, continuing to support MCData evolution.

Definition carried over unchanged, maintaining the same description.

Definition carried over unchanged, with no changes to the text.

Definition carried over unchanged, showing consistency in the specification.

Defining Specifications

3GPP specifications that define or reference Conversation identifier, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.282 vk31 Mission Critical Data Architecture Rel-20 read
TR 23.783 vi00 Technical Report on Mission Critical Services over 5GS Rel-18 read