sedlacek, dostal

1 © Nokia Siemens Networks Mobile Internet Applications / Ivo Sedlacek, Pavel Dostal / 2008-09-10

Mobile Internet Applications• How to Design User Friendly and Interoperable Mobile

Applications


Who we are

• Presenters

• Pavel Dostál, http://www.linkedin.com/in/pdostal

• Ivo Sedláček, http://www.linkedin.com/in/isedlacek• ANF DATA employees contracted to represent Nokia Siemens Networks in

Open Mobile Alliance

• Nokia Siemens Networks

• a leading global enabler of communications services. The companyprovides a complete, well-balanced product portfolio of mobile and fixed network infrastructure solutions and addresses the growing demand for services with 20,000 service professionals worldwide.

• ANF DATA

• a subsidiary of Siemens AG Austria, providing services as research and development partner, system integrator and solution provider.


Standardization benefits

• What standardization provides

• interoperability between functional entities (clients, servers, ...) provided by different vendors

• everything works, and if not, it is clear whom to blame

• similar user experience everywhere

• reduces costs for operators and vendors

• precondition for wide deployment in multivendor, multioperator environment

• What standardization does not provide

• Unified user interface

• Internal functional entity design and implementation

• Success guarantee


About Open Mobile Alliance (1)

• Open Mobile Alliance is the leading industry forum for developing market driven, interoperable mobile service enablers.

• Since June 2002 – consolidation of efforts in mobile service enabler organizations – e.g. WAP Forum, LIF, SyncML Initiative, MMS-IOP, WV, …

• Nearly 200 companies• Operators

• Telecommunication equipment vendors

• IT/applications/software vendors

• Content/media/service providers

• Others

• Different membership level• Sponsor

• Full

• Associate

• Supporter

• Example of Approved Enablers• Data Synchronization, Mobile Broadcasting Services, IMPS, MMS, Presence, Push to

Talk over Cellular


About Open Mobile Alliance (2)

• The principles of the Open Mobile Alliance• Products and services are based on open, global standards, protocols and interfaces and

are not locked to proprietary technologies

• The applications layer is bearer agnostic (examples: GPRS, EDGE, CDMA, UMTS, WiFi, ADSL)

• The architecture framework and service enablers are independent of operating systems

• Applications and platforms are interoperable, providing seamless geographic and inter-generational roaming

• Cooperation with other existing fora• The Open Mobile Alliance works with several existing fora and standardization bodies

such as IETF, 3GPP, 3GPP2. The alliance is not competing with the existing standards but, rather, complementing them to focus on interoperability of services across markets, across terminals and across operators.

• Openness Policy• Majority of the produced documents publicly available for members and non-members.

• Contact• www.openmobilealliance.org


Open Mobile Alliance process (1)

• OMA specifications, so called Enablers, are developed in several stages

• Work Item definition stage• scope of the Enabler

• Requirement Document creation stage• use cases and detailed market requirements on the Enabler

• Architecture Document creation stage• functional entities with their high level tasks

• reference points between the functional entities

• security concepts and dependency on other Enablers

• Technical Specification creation stage• detail description of each functional entity acting

• instructions how to validate that the Enabler technical specifications are sufficiently correct, exact and understandable

• Candidate validation and approval stage• test reports proving that network infrastructure vendors and handset vendors are able

to create products interworking with each other based on the Enabler technical specifications

• Approved Enabler stage


Open Mobile Alliance process (2)

• Each stage is followed by a review and approval

• Contribution driven process

• OMA members meet regularly to discuss contributions to Enablers

• any member can participate in any discussion on any Enabler

• any member can bring any contribution and present it to other members

• any member can object to any contribution

• contributions agreed by consensus become part of the Enabler

• if consensus cannot be reached, contributions agreed by 2/3 majority vote become part of the Enabler

• IPRs

• OMA specifications may contain solution protected by IPRs

• any OMA member aware of an IPR must declare that to OMA

• declared IPRs must be licensed to other OMA members on fair, reasonable and non-discriminatory terms


Converged Address Book

• Goals

• Improve the user’s experience with a single address book environment.

• Synchronize the contact information available in the user’s device(s) with a

network based contact repository.

• Manage the distribution of user’s own contact information

• Provide interface for searching of contacts based on various criteria

• Progress

• Requirement Document near to be finalized

• Architecture Document ongoing


Converged Address Book Use Cases

• Sharing own contact information

• User’s own contact information updates are propagated to the other user’s

address book

• Authorization rules for own contact information

• Synchronization of address books

• Contact added to one device is automatically synchronized to other devices of

the same user

• Sharing address book

• Address book items are available to other users

• Importing contacts from other repositories

• Bulk import of contacts, merging, …


Mobile Advertisement

• Actors

• Users – end users using the mobile phones

• Service Providers – mobile network operators “owning” the Users

• Content Providers – providers offering content deliverable to the Users, e.g. owner of video on demand service

• Advertisers – anyone interested to advertise to the Users and get information about the Users’ behaviour after consuming the advertisement and willing to pay for it

• Goals

• Advertisers - simple preparation of the advertising campaigns towards target user set and getting the metrics on the advertising campaign effects

• Content Providers - generate extra revenue by allowing delivery of the advertisements together with content to the Users

• Service Providers – generate extra revenue by selecting individual Users for the required target set, by delivering advertisements along the content to selected Users and by measuring the advertising effects at the selected Users

• Users – get personalized advertisements and may get services at a reduced price

• Progress

• Requirement Document near to be finalized

• Architecture Document just started


Mobile Advertisement Use Cases

• Advertisement delivery

• Advertisement delivery irrespective to any running communication

• Advertisement insertion within running communication

• Metrics collection

• Providing information on Users acceptance of the advertisements

• Getting data for personalization

• Scanning the communication of the user

• Maintaining the user preferences

• Criteria for the target user selection

• location of the user

• data published by the users – preferences, status

• capabilities of User’s clients

• subscriptions of the Users to other services

• ....

sedlacek, dostal

Documents