Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 29341-20-12: UPnP Telephony Message Service
ISO/IEC 29341-20-12 — Telephony — Message Service Standard for Universal Plug and Play
Introduction to UPnP Telephony Message Service
The ISO/IEC 29341-20-12 standard specifies the UPnP Telephony Message service, which provides a unified messaging interface for managing voicemail, email, SMS, and instant messages within the UPnP telephony environment. As communication modalities converge in the digital home, the Message service acts as a central hub that aggregates messages from multiple sources and delivers them to UPnP control points such as smart displays, media centers, and telephony handsets.
The Message service decouples message storage and retrieval from the transport mechanism, allowing the same UPnP control point to present voicemail, SMS, and email messages through a uniform interface without protocol-specific adaptations.
Message Architecture and Data Model
Each message in the service is represented by a unique MessageID and includes metadata such as sender URI, recipient URI, subject, timestamp, priority level, media type (voice, text, video, multimedia), and read status. Messages are organized into folders — Inbox, Outbox, Drafts, Sent, and custom user-defined folders — with folder metadata exposed via the MessageFolderList state variable.
The service supports both push and pull message delivery models. In the push model, the message service provider initiates a UPnP event to notify control points of new messages. In the pull model, control points periodically query the service for message summaries. The service maintains consistency by tracking message counts per folder and updating the UnreadMessageCount state variable on any change.
Implementers must handle concurrent access scenarios where multiple control points read, move, or delete messages simultaneously. The standard recommends using optimistic concurrency control with revision counters on each message entry.
Key Actions and Message Operations
| Action | Description | Required Arguments |
|---|---|---|
| GetMessageList | Retrieve message summaries from a specified folder | FolderID, StartingIndex, RequestedCount |
| GetMessage | Fetch the full content and attachments of a specific message | MessageID |
| SendMessage | Compose and send a new message | RecipientURI, Subject, Body, MediaType |
| DeleteMessage | Remove a message from a folder | MessageID, ExpungeFlag |
| MoveMessage | Move a message between folders | MessageID, TargetFolderID |
| MarkAsRead | Mark a message as read or unread | MessageID, ReadStatus |
| GetMessageAttachment | Download a message attachment by index | MessageID, AttachmentIndex |
The service is designed to integrate with external message storage providers through a pluggable backend interface. The UPnP Message service does not dictate how messages are physically stored or transported — it only defines the control interface. Implementations commonly back the service with POP3/IMAP email accounts, SIP SIMPLE instant messaging, or proprietary voicemail servers.
One of the strongest design aspects is the content-agnostic attachment model. Any MIME-compatible content type can be attached to a message, and the control point decides how to render it — enabling unified inbox experiences that blend voice recordings, documents, and Rich Communication Services (RCS) messages.
Engineering Design Insights
Efficient message synchronization is critical for battery-powered mobile control points. The service should support delta synchronization using the SyncToken mechanism, allowing control points to retrieve only messages that changed since the last synchronization rather than downloading full folder contents on every query. This reduces bandwidth consumption and improves response times on devices with limited processing power.
Privacy and access control deserve special attention. The Message service carries sensitive personal communications, and the standard recommends implementation of access controls that restrict message retrieval to authenticated control points. When messages contain media attachments such as voice recordings, the service should verify that the requesting control point has the necessary content access rights before streaming attachment data.
Message services that fail to implement proper access controls expose users to serious privacy violations. Any control point on the network must authenticate before accessing message content. The service should also support message encryption at rest and in transit, and provide a mechanism for remote message wipe in case a device is lost or compromised.
Frequently Asked Questions
Q: Can the Message service handle multimedia messages with large attachments?
A: Yes. The service supports streaming of attachment content via HTTP. The GetMessageAttachment action returns a transfer URL, and the actual content transfer occurs out-of-band, allowing efficient handling of large file sizes without blocking the UPnP control channel.
A: Yes. The service supports streaming of attachment content via HTTP. The GetMessageAttachment action returns a transfer URL, and the actual content transfer occurs out-of-band, allowing efficient handling of large file sizes without blocking the UPnP control channel.
Q: Does the standard define a maximum message size?
A: No. Maximum message size is implementation-dependent and should be advertised by the service during the device description phase. Typical implementations support messages up to 10 MB including attachments.
A: No. Maximum message size is implementation-dependent and should be advertised by the service during the device description phase. Typical implementations support messages up to 10 MB including attachments.
Q: How does the service handle message delivery failures?
A: Failed outgoing messages are moved to the Outbox with an error status and error description. The service should implement retry logic with configurable intervals and maximum retry counts, notifying the control point on final delivery failure.
A: Failed outgoing messages are moved to the Outbox with an error status and error description. The service should implement retry logic with configurable intervals and maximum retry counts, notifying the control point on final delivery failure.
