Description
The Folder Identifier is a data type defined in the 3GPP Mission Critical Data (MCData) specifications (23.282 and 23.783) that uniquely identifies a folder within the MCData message store. The MCData message store is the functional entity responsible for the storage and retrieval of short data messages, file transfers, and related communication items exchanged between MCData users. Each folder in this store is assigned a Folder Identifier so that both the MCData client and the MCData server can unambiguously reference a specific folder when performing operations such as creating, listing, moving, or deleting stored items.
The identifier is used in the MCData message store protocol, which is based on HTTP/XML interfaces as defined in 23.282. When a client wishes to organize its stored messages, it issues requests to the MCData server referencing the Folder Identifier of the target folder. The server uses this identifier to locate the folder in its internal data model and to perform the requested operation. Because the identifier is unique within the scope of a user's message store, it provides a stable handle that survives across sessions and reconnections, allowing the client to reconstruct its folder view after a restart or network change.
Architecturally, the Folder Identifier sits within the MCData functional model alongside other identifiers such as the message identifier and the conversation identifier. The message store maintains a hierarchy in which folders can contain messages and possibly sub-folders, and the Folder Identifier is the key that ties the client's view to the server's stored representation. The identifier is typically generated by the MCData server when a folder is created, and it is returned to the client in the response to the folder creation request. Clients then persist this identifier locally to reference the folder in subsequent operations.
The Folder Identifier also plays a role in synchronization. When an MCData client reconnects or performs a resynchronization of its message store, it can use folder identifiers to reconcile its local cache with the server's authoritative state. This is important in mission-critical environments where users may operate over unreliable networks and need to recover their stored data reliably. The identifier also supports multi-device scenarios, where several clients associated with the same user access the same message store and must agree on folder references.
Because MCData is built on the broader Mission Critical Services (MCX) framework, the Folder Identifier follows the general design principles of MCData identifiers: it is opaque to the client, generated and managed by the server, and scoped to the user's message store. This opacity allows the server implementation freedom in how it generates identifiers (for example, UUIDs or sequential values) without affecting interoperability. The term was introduced in Release 16 together with the initial MCData specifications and has been carried forward unchanged through subsequent releases, reflecting the stability of the message store data model.
Purpose & Motivation
The Folder Identifier exists to give the MCData message store a stable, unambiguous way to reference folders that organize stored mission-critical messages. Without such an identifier, clients and servers would have to rely on folder names or positional indices, which are fragile: names can be duplicated or changed by the user, and positions shift as folders are added or removed. A unique, server-generated identifier decouples the client's logical view from the server's storage representation.
The concept was motivated by the requirements of mission-critical users, such as public safety personnel, who need to organize large volumes of short data messages and files into folders for later retrieval. These users often operate across multiple devices and intermittent connectivity, so the message store must support reliable resynchronization. A persistent Folder Identifier enables a client to re-establish its folder structure after reconnection and to reconcile local caches with the server's authoritative state.
Prior to MCData, mission-critical communication services focused primarily on voice (MCPTT) and video (MCVideo). Release 16 introduced MCData to cover short data and file transfer, and with it the need for a message store data model. The Folder Identifier was defined as part of that model from the outset, providing a foundation for folder management operations in the MCData message store protocol defined in 23.282.
What changed in its specifications
The latest release-to-release comparison of specifications that define Folder Identifier. Each summary describes the whole specification, not only this term.
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.
Defining Specifications
3GPP specifications that define or reference Folder Identifier, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |