1. © 2004 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-MCC-2004-0131R01Slide #1 [OMA-Template-SlideDeck-20040305] Submitted To:MCC Date:20 Sep 2004 Availability: Public OMA Confidential Contact:Karsten Lüttge, karsten.luettge@siemens.com Source:Siemens OMA-MCC-2004-0131R01 Introduction to OMA Charging 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.http://www.openmobilealliance.org/UseAgreement.html 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. © 2004 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-MCC-2004-0131R01Slide #2 [OMA-Template-SlideDeck-20040305] General Information about OMA OMA is specifying enablers that enable the creation of mobile application. An enabler is basically a set of specs around a certain topic, e.g. Location enabler – describes architecture and protocols for an application to query a subscriber’s location information, for networks to securely exchange location information, and to control access to this information. Browsing enabler – basically the evolution of WAP, including markup language, protocols, architecture … Presence and Instant Messaging – architecture and protocols to determine subscriber’s presence status and to send/receive instant messages Enabler development is all ruled by well-defined processes (but those will not be introduced here).

3. © 2004 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-MCC-2004-0131R01Slide #3 [OMA-Template-SlideDeck-20040305] Source: OMA-ARC-2004-0245R07 Current view of overall OMA Architecture (OMA Service Environment - OSE) Other bindings Web service bindings … Enabler implementation Enabler implementation Enabler implementation Policy Enforcer Applications … Enabler implementation Service Provider Domain To Resources in Operators, terminals, Service Providers Execution Environment (Software Life Cycle Mgmt, Load balancing, caching, etc.) Execution Environment (Software Life Cycle Mgmt, Load balancing, caching, etc.) Applications Yet to beapprovedby OMATP!Integration ofterminals into theOSE is currentlyunder discussion! PE is a logicalfunction and can becontained in enablerimplementations!

4. © 2004 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-MCC-2004-0131R01Slide #4 [OMA-Template-SlideDeck-20040305] Other bindings Web service bindings … Enabler implementation Enabler implementation Enabler implementation … Enabler implementation Policy Enforcer To Resources in Operators, terminals, Service Providers Applications Third Party – Un-trusted Domain Enabler implementation Service Provider Domain Applications Sample OSE Flows Policy Enforcer enforces policies on request (relying on available enablers) Appropriate request reach target enabler Application issues a request to an enabler Request invokes the target resource of the Enabler implementation 1a 1c 1d 1b Enabler implementation issues a request to another enabler Policy Enforcer enforces policies on requests between enabler implementations Appropriate request reach target enabler Enabler implementation issues a request to another enabler 2a 2c/3c 3a 2d/3d 2b/3b 4a 4d 4b Application issues a request to an enabler Policy Enforcer enforces policies on request (relying on available enablers) 4c

5. © 2004 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-MCC-2004-0131R01Slide #5 [OMA-Template-SlideDeck-20040305] Sources of Charging Information within OSE Charging information can be generated by the following OSE elements: Resources Policy Enforcer (if present) Applications and Enablers

6. © 2004 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-MCC-2004-0131R01Slide #6 [OMA-Template-SlideDeck-20040305] Charging for Resource usage What to charge for? Charging information reflects resource usage by applications/enablers. How to charge? Involved network elements measure resource usage and generate charging events as defined for the underlying network technology. This will not be addressed by OMA MCC.

7. © 2004 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-MCC-2004-0131R01Slide #7 [OMA-Template-SlideDeck-20040305] Charging by Policy Enforcer What to charge for? Charging information reflects resource usage by applications/enablers How to charge? The Policy Enforcer intercepts (by definition) all resource invocations. Policies in place may request that the invocation shall be charged for in a certain way. The Policy Enforcer delegates the actual charging to the appropriate Enabler Implementation entity. This will be addressed by OMA MCC activities.

8. © 2004 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-MCC-2004-0131R01Slide #8 [OMA-Template-SlideDeck-20040305] Charging by Applications/Enablers What to charge for? Charging information reflects application or enabler usage. How to charge? The application may want to control charging for using it by itself. It will talk to a charging enabler implementation (possibly going through the Policy Enforcer). This charging enabler implementation may be the same as the one used by the Policy Enforcer itself. This will be addressed by OMA MCC activities.

9. © 2004 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-MCC-2004-0131R01Slide #9 [OMA-Template-SlideDeck-20040305] The OMA Charging Enabler The OMA Charging Enabler is expected to be a set of specifications that describe how applications, enablers or a policy enforcer perform charging?