1 / 26

OMA-MEM-2005-0046R01-Mobile_email_RD_Pres_Lemonade Overview of Mobile Email RD

OMA-MEM-2005-0046R01-Mobile_email_RD_Pres_Lemonade Overview of Mobile Email RD. Submitted To: OMA - MEM Date: 23 Sep 2005 Availability: Public OMA Confidential Contact: St é phane H. Maes, stephane.maes@oracle.com Source: OMA - MEM. X.

yasuo
Download Presentation

OMA-MEM-2005-0046R01-Mobile_email_RD_Pres_Lemonade Overview of Mobile Email RD

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. OMA-MEM-2005-0046R01-Mobile_email_RD_Pres_LemonadeOverview of Mobile Email RD Submitted To: OMA - MEM Date: 23 Sep 2005 Availability: Public OMA Confidential Contact: Stéphane H. Maes, stephane.maes@oracle.com Source: OMA - MEM X USE OF THIS DOCUMENT BY NON-OMA MEMBERS IS SUBJECT TO ALL OF THE TERMS AND CONDITIONS OF THE USE AGREEMENT (located at http://www.openmobilealliance.org/UseAgreement.html) AND IF YOU HAVE NOT AGREED TO THE TERMS OF THE USE AGREEMENT, YOU DO NOT HAVE THE RIGHT TO USE, COPY OR DISTRIBUTE THIS DOCUMENT. THIS DOCUMENT IS PROVIDED ON AN "AS IS" "AS AVAILABLE" AND "WITH ALL FAULTS" BASIS. Intellectual Property Rights Members and their Affiliates (collectively, "Members") agree to use their reasonable endeavours to inform timely the Open Mobile Alliance of Essential IPR as they become aware that the Essential IPR is related to the prepared or published Specification. This obligation does not imply an obligation on Members to conduct IPR searches. This duty is contained in the Open Mobile Alliance application form to which each Member's attention is drawn. Members shall submit to the General Manager of Operations of OMA the IPR Statement and the IPR Licensing Declaration. These forms are available from OMA or online at the OMA website at www.openmobilealliance.org.

  2. Reasons for Contribution • This contribution provides an overview of the mobile e-mail enabler RD (Requirement Document) to be presented at the OMA MEM / IETF Lemonade joint workshop.

  3. OMA Mobile E-mail Enabler Status • The latest version of mobile email enabler RD is OMA-RD-MobileEmail-V1_0-20050921-D • It can be found at http://member.openmobilealliance.org/ftp/Public_documents/REQ/Permanent_documents/OMA-RD-MobileEmail-V1_0-20050921-D.zip • Status: • Updated since the previous liaison with Lemonade WG • Completed formal review • Comments / questions received from IETF Lemonade (OMA-MEM-2005-0020-ILS-regarding-MWG-MEM-RD) have considered and addressed. • Submitted for agreement by REQ WG (Target Sept 29, 2005): • See http://member.openmobilealliance.org/ftp/Public_documents/REQ/2005/OMA-REQ-2005-0473-Mobile_Email_RD_for_approval.zip for package (including RDRR). • Will be submitted for Candidate approval to OMA TP (R&A) after REQ agreement (before Sydney meeting – October 17-21, 2005) • RD is still subject to revisions. Comments are still welcome

  4. Scope and definitions • Mobile email is defined as an email enabler optimized to support email usage in mobile devices and wireless networks. • The RD focuses on requirements for the enabler specifications rather than for particular implementations of those: • Some feedback from LEMONADE addressed implementations • The RD does not design the solution: • Some feedback from LEMONADE addressed technical solutions • Mobile email: Enabling technologies that facilitate end-to-end application level interoperable email transactions (e.g. submission, retrieval, notification etc) to and from mobile devices. • Target both consumer and corporate mobile e-mail • Enabler focus: • Between client and server

  5. Main Use Cases (1/4) Note: OMA RDs do not expect an exhaustive list of use cases • Receiving an Email on the go: • Some highlights: • New e-mail arrives in e-mail servers • It is received on mobile client quasi-instantaneously based on settings preferences (whole e-mail or portions of e-mail; adapted or not) • Enterprise and Non-enterprise users • Receiving a email server event on the go: • Some highlights: • E-mail events from the server • Viewing email attachments on the go: • Some highlights: • Attachment adaptation / transcoding (known by server or requested by client) • View attachment

  6. Main Use Cases (2/4) • Sending emails on the go: • Some highlights: • Sending an e-mail from correct SMTP server • Offline / intermittent connectivity • Filtering rule changes while mobile: • Some highlights: • User dynamically changes a filter (add a sender from who notifications / new e-mails should be received) • DS synchronization between clients: • Some highlights: • 3-way pair wise synchronization (e.g. Phone, laptop and server)

  7. Main Use Cases (3/4) • Email with Attachment: • Some highlights: • Details about attachments • Selectively download part or all of attachments if not yet downloaded • Download more • Forwarding Email without Downloading Attachments: • Some highlights: • Forward without download with server-side re-composition including edits • Selection of what attachment to forward • Configuring additional email accounts to be accessed: • Some highlights: • Support multiple e-mail accounts possibly from different e-mail service providers

  8. Main Use Cases (4/4) • Replying to messages that are retrieved from different accounts: • Some highlights: • Determines what account / server to use to send e-mail

  9. Additional Use Cases (1/2) • Replying to messages that are retrieved from different accounts: • Some highlights: • Determines what account / server to use to send e-mail • Client Email Events: • Some highlights: • Reflecting e-mail client events to server • Offline / intermittent connectivity • Filtering Rules: • Some highlights: • Filtering rules on: • Email • Events

  10. Additional Use Cases (2/2) • Replying or Forwarding to Emails 'On the Go': • Some highlights: • User can edit text and attachments • Can edit any email portion including address • Can send to server only differences • Configuring Auto-Reply Message: • Some highlights: • Set auto-reply for accounts while mobile

  11. High-Level Functional Requirements (1/2)

  12. High-Level Functional Requirements (2/2)

  13. Security Requirements (1/2)

  14. Security Requirements (2/2)

  15. Charging Requirements

  16. Administration and Configuration Requirements

  17. Usability Requirements (1/5)

  18. Usability Requirements (2/5)

  19. Usability Requirements (3/5)

  20. Usability Requirements (4/5)

  21. Usability Requirements (5/5)

  22. Interoperability Requirements (1/2)

  23. Interoperability Requirements (2/2)

  24. Privacy Requirements

  25. Overall System Requirements

  26. Additional Considerations • Technology implications are analyzed as part of the AD phase by MEM SWG. • AD phase is started with: • Logical architecture • Technology option analysis • Identification of dependencies

More Related