© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #1 [OMA-Template-SlideDeck I] Submitted To:OMA - MEM Date:23 Sep 2005 Availability: Public OMA Confidential Contact:Stéphane H. Maes, Source:OMA - MEM OMA-MEM R02- Mobile_ _AD_Pres_Lemonade Overview of Mobile AD X USE OF THIS DOCUMENT BY NON-OMA MEMBERS IS SUBJECT TO ALL OF THE TERMS AND CONDITIONS OF THE USE AGREEMENT (located at 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

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #2 [OMA-Template-SlideDeck I] Reasons for Contribution This contribution provides an overview of the mobile enabler AD (Architecture Document) to be presented at the OMA MEM / IETF Lemonade joint workshop.

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #3 [OMA-Template-SlideDeck I] OMA Mobile Enabler Status The latest version of mobile enabler AD is OMA-AD- Mobile_ _V1_ D It can be found at ocuments/OMA-AD-Mobile_ -V1_0_ D.zip ocuments/OMA-AD-Mobile_ -V1_0_ D.zip Status: Work in progress

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #4 [OMA-Template-SlideDeck I] Scope and definitions Mobile is defined as an enabler optimized to support usage in mobile devices and wireless networks. Target both consumer and corporate mobile So far agreement is that Mobile enabler may be realized with multiple technologies Client to client interworking / interoperability via internet . The AD focuses on logical architecture to support the requirements and use cases. Technology realization neutral Implementation / deployment neutral Enabler focus: Between client and server

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #5 [OMA-Template-SlideDeck I] Logical Architecture Note: server includes mail store and submit server functions that may be split into different components. AD may be better represented with such a split (work in progress)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #6 [OMA-Template-SlideDeck I] Functional Components The mobile enabler client which implements the client-side functionality of the OMA Mobile Enabler. It is also responsible for providing the mobile user experience and interface to the user and storing the and data to be sent to the mobile enabler server when not connected. The mobile enabler server which implements the server-side functionality of the OMA Mobile Enabler. The mobile protocol between the Mobile Client and Mobile Enabling Server. Other OMA enablers are needed to support the mobile enabler: OMA DM/CP, Messaging, Push, XDM.

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #7 [OMA-Template-SlideDeck I] Interfaces ME-1: Mobile client enabler I0 interface to interact via the mobile enabler protocol with the mobile enabler server ME-2: Corresponding I0 interface of the mobile enabler server ME-3: Outband Mobile server enabler I0 interfaces (e.g. to support generation of server to client notifications). ME-4: Outband Mobile client enabler I0 interfaces (e.g. to receive server to client notifications)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #8 [OMA-Template-SlideDeck I] Flows (1/4) Server to client notification: An event (new , change of state of ) takes place in the server. The mobile enabler server generates a notification, if prescribed by enabler settings and filtering rules (as set by administrator or user based on the type of event). If outband notifications are used, the notification is sent in the appropriate channel: E.g. as separate message through ME-3 (e.g. SIP event notify) or bound to another OMA messaging enabler (e.g. as a WAP Push message). If inband notification is used (and therefore a ME-1/ME-2 session is established), the notification is sent via ME-2 interface. The mobile enabler client receives the notification: Respectively via ME-4 (possibly bound to the I0’ of another enabler) or ME-1 I0’ Based on settings of the mobile enabler client, the client: Updates its state (e.g. delete a local ) Queues the notification for the next time it retrieves information from the server Goes back to the mobile enabler server via ME-1 to act on the notification by retrieving appropriate data.

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #9 [OMA-Template-SlideDeck I] Flows (2/4) If no data connection is established between the client enabler server and the server enabler server, the client establishes a connection (including authentication etc…). If a connection exists (e.g. when using inband notification), this steps is not repeated. Through ME-1 the client requests data from the mobile server to act on the notification. This is received by the mobile enabler server through its ME-2 interface. The mobile enabler server provides (via ME-2) the requested data to the mobile e- mail enabler client (via ME-1). The mobile enabler server may provide additional events and data for: Notifications that it has previously sent to the client but to which the mobile enabler client never reacted (e.g. may have been lost) or that it had queued (e.g. because the mobile enabler client was not reachable and there was little value to continue to send server to client notifications. Notifications for new server events that occurred since Additional data and information needed by the server as described above. This robustizes the behaviour of the enabler to intermittent connectivity and unreliable connectivity.

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #10 [OMA-Template-SlideDeck I] Flows (3/4) Client events (deleted mail, read,unread changes etc…) are sent (via ME-1) to the mobile enabler server (received via ME-2) if appropriate based on settings / filtering rules: Depending if a connection exists or not, it is first established as described above when accessing additional data and events After sending the data, the server may reply with data analogous to the notifications and data as descried above in answer to a request for more data. The mobile enabler server then updates the appropriate server. If the mobile enabler client can not connect to the mobile enabler server, the events are queued and stored in the client and sent when connection is eventually established.

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #11 [OMA-Template-SlideDeck I] Flows (4/4) New s are sent from the mobile enabler client (via ME-1) to the mobile enabler server (received via (ME-2) as for the previous case. The mobile enabler server then sends from the s server. If the mobile enabler client can not connect to the mobile enabler server, the new s are queued and stored in the client and sent to the mobile enabler server when connection is eventually established. The mobile enabler server and mobile enabler server can directly interact to support usage of the enabler: Request more data from mobile enabler server (e.g. access more of an partially on the mobile enabler client). Save of draft to mobile enabler server Attachment manipulation: Download an attachment Convert an attachment (mime type / sub-type conversion or transcoding) Server-side (partial) composition for reply / forward: Forward without download Partial edit and partial forward without download of: Address fields, Body Attachments

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #12 [OMA-Template-SlideDeck I] Implementations – firewalls

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #13 [OMA-Template-SlideDeck I] Implementations – proxies and firewalls (1/2)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #14 [OMA-Template-SlideDeck I] Implementations – proxies and firewalls (2/2)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #15 [OMA-Template-SlideDeck I] Deployment model examples (1/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #16 [OMA-Template-SlideDeck I] Related proxy variations (2/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #17 [OMA-Template-SlideDeck I] Deployment model examples (3/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #18 [OMA-Template-SlideDeck I] Related proxy variations (4/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #19 [OMA-Template-SlideDeck I] Deployment model examples (5/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #20 [OMA-Template-SlideDeck I] Related proxy variations (6/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #21 [OMA-Template-SlideDeck I] Deployment model examples (7/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #22 [OMA-Template-SlideDeck I] Related proxy variations (8/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #23 [OMA-Template-SlideDeck I] Deployment model examples (9/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #24 [OMA-Template-SlideDeck I] Deployment model examples (10/10)

© 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. OMA-MEM R02Slide #25 [OMA-Template-SlideDeck I] Additional Considerations Technology implications are analyzed from RD and use cases: Features required Functions of each components are being compiled Note that several logical components may collapse into a single component in practice Technology selections and dependencies are being determined Technology analysis may be the object of one or multiple white paper