1 / 7

DMDN

This document outlines the development of OMA SIMPLE IM, initiated in 2004 and based on IETF specifications. With a detailed design completed in December 2006, the final review is underway. The system supports 1-1 and 1-n communications, including page mode, session mode, and deferred messaging. Notably, it addresses the need for user-friendly delivery notifications without requiring user awareness. The document emphasizes the importance of consistent user experience through efficient delivery and read notifications for various messaging modes, leading to improved communication quality in mobile messaging services.

lyndon
Download Presentation

DMDN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DMDN draft-stafford-simple-dmdn-00.txt Jerry Shih – Cingular Wireless now the New AT&T

  2. OMA SIMPLE IM Background • Started development in 2004 • Based on IETF SIMPLE IM specs • Detailed design completed in 12-2006 • It is in final review comment resolution • Supports 1-1, 1-n communications • Support page mode, session mode and deferred messaging • Plan to become OMA candidate Service Enabler in June 2007

  3. OMA Taxonomy for IMS-based Messaging

  4. Message Delivery Notification • User is un-aware (doesn’t care) of how message is sent • Delivery notification is important (delivery or read) • Should provide consistent user experience • IMDN is good for Page mode messaging using SIP MESSAGE • Need IMDN-like notification mechanism for session mode messaging such as “Large Message Mode” and “Deferred messaging”

  5. READ Notification for Large Message Mode

  6. Delivery Notification for Session Based Deferred messaging

  7. Conclusion • Need to provide consistent end user experience for message delivery notification • OMA supports Large Message Mode that use MSRP to delivery Page Mode message • OMA supports Deferred Messaging that will store a message for later delivery • IMDN is supported for Page Mode and we need similar mechanism to support both Large Message Mode and Deferred Messaging • Would like to see these requirements refined and published and to find a venue to work on a solution

More Related