Description
Auto-receive is a delivery mechanism defined in 3GPP TS 23.282 (Functional architecture and information flows to support Mission Critical Data) and TS 23.783 (Mission Critical Data services), introduced in Release 14. It specifies that data smaller than a configured size threshold are delivered to the receiving MCData client(s) from the MCData server automatically — that is, without waiting for the receiving user to indicate a present need for the data. This is a key optimization for mission-critical communications, where timely delivery of small data items (e.g., short messages, location reports, status updates) can be operationally significant.
In the MCData architecture, the MCData server manages data delivery between MCData clients. The default delivery model is 'pull' or 'on-demand': the server notifies the receiving client that data is available, and the client fetches it when the user requests it. This conserves bandwidth and device resources, which is important for large files or when the user is not actively engaged. However, for small data items, the notification-and-fetch round trip adds latency and requires user interaction that may be inappropriate in an emergency. Auto-receive addresses this by allowing the server to push small data directly to the client.
The mechanism is governed by a configured size threshold. The threshold is set by the MCData service configuration (managed by the MCData administrator) and can be tailored to the operational profile of the mission-critical organization. Data items below the threshold are auto-delivered; data items above the threshold follow the standard on-demand delivery model. The threshold is communicated to the MCData clients and the MCData server as part of the service configuration, ensuring consistent behavior across the system.
Auto-receive is particularly relevant for MCData short data service (SDS) messages, location information, and small file transfers. It reduces the time-to-delivery for time-sensitive information and simplifies the user experience by eliminating the need to manually accept small data items. The mechanism is designed to be transparent to the user: the data simply appears in the client's inbox or data store without an explicit fetch action.
The feature is part of the broader MCData service enablers, which include SDS, file distribution, and data streaming. It complements other MCData features such as delivery and read receipts, which provide confirmation that data has been delivered and consumed. Together, these features support the stringent requirements of mission-critical communications for reliability, timeliness, and user situational awareness.
Purpose & Motivation
Auto-receive exists to solve the latency and usability problem of delivering small data items in mission-critical communications. In the standard MCData on-demand delivery model, the receiving client is notified of available data and must fetch it when the user indicates a present need. For large files, this is appropriate: it conserves bandwidth and device storage. But for small, time-sensitive data items — a short status message, a location update, a brief instruction — the notification-and-fetch round trip adds latency and requires user action that may be impossible or dangerous in an emergency.
The mechanism was introduced in Release 14 as part of the initial MCData specifications, alongside the broader push to standardize mission-critical data services for public safety and critical infrastructure users. It provides a configurable, threshold-based compromise between the efficiency of on-demand delivery and the timeliness of automatic push. By allowing operators to set the threshold, it accommodates different operational profiles: an organization that prioritizes immediacy can set a high threshold, while one that prioritizes bandwidth efficiency can set a low one. This flexibility is essential for the diverse user communities that rely on MCData.
What changed in its specifications
The latest release-to-release comparison of specifications that define Auto-receive. 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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference Auto-receive, 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 |