DOCSLIB.ORG

Mobile Messaging Technologies and Services: SMS, EMS And

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mobile Messaging Technologies and Services: SMS, EMS And 336 Mobile Messaging Technologies and Services † Presence and Instant Messaging Protocol (PRIM) † SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE) SIMPLE is an IMPS protocol based on the Session Initiation Protocol (SIP) [RFC-3261] and is particularly well suited for UMTS phase 2. SIMPLE defines a mechanism for subscribing to a service which manages subscriber status changes over a SIP network. The Wireless Village Initiative was recently set up by several manufacturers to consider the support of IMPS in the mobile environment. The prime objective of this initiative is to develop an industry standard to guarantee interoperability between various IMPS services that could be deployed in the near future. The IMPS model, proposed by the Wireless Village, includes four primary features: † Presence: this feature manages information such as device availability (e.g. mobile device has been switched on/off, voice call under progress), user status (e.g. available, not avail- able, having a meeting), user location, mobile device capabilities, personal status/moods (e.g. happy, angry), etc. To ensure confidentiality, presence information is provided according to user instructions only. † Immediate Messaging: this feature allows the exchange of messages delivered instanta- neously to the recipient(s). This means that, upon sending by the originator, the message is perceived as being immediately delivered to the message recipient(s). Compared with traditional messaging services, instant messaging allows the establishment of interactive messaging sessions between users. These sessions are usually displayed using a threaded conversational interface, also known as chat. † Groups: this feature allows users to create and manage their own groups. The manager of a group can invite other users to chat with the group members. Network operators can create general interest groups. † Shared Content: this feature provides users with storage zones where pictures, audio and other multimedia contents can be posted and retrieved. These contents can be shared among several users during group messaging sessions. The general architecture of the Wireless Village initiative solutions is depicted in Figure 7.1. In the architecture shown in the figure, the Wireless Village server is a central element. This server manages the following services: presence, instant messaging, groups and content sharing. Two types of Wireless Village clients can communicate with the server: the Wireless Village embedded client and the Wireless Village Command Line Interface (CLI) client. The Wireless Village embedded client is a dedicated application embedded in a mobile device. This client communicates with the server over the Client Server Protocol (CSP). On the other hand, the Wireless Village CLI client uses text messages (e.g. SMS) to communicate with the server using the Command Line Protocol (CLP). A CLI client is usually a legacy mobile device. Two Wireless Village servers, located in the same provider domain or in two distinct provider domains, can communicate with the Server-Server Protocol (SSP). A Wireless Village server may also be connected to a proprietary IMPS system via a proprietary gateway. In this configuration, the gateway transcodes SSP instructions into instructions supported by the proprietary system, and vice versa. The Server-Mobile Core Network Protocol (SMCNP) allows the server to obtain presence information and service capabilities from the mobile core network. In addition, the SMCNP can also be used for authentication and authorization of users, clients and servers. 337 Other Mobile Messaging Services Figure 7.1 General Wireless Village architecture Wireless Village technical specifications can be downloaded from http://www.wireless- village.org. 7.2 Mobile Email Email is the de facto messaging service on the Internet. However, due to the bandwidth limitations of mobile systems and the fact that mobile devices are seldom permanently connected to the network, Email is not widely used in the mobile telecommunications domain. Nevertheless, several manufacturers have designed Email clients for mobile devices using standard Internet messaging protocols such as the Post Office Protocol-3 (POP3), defined in [RFC-1939] and the Interactive Mail Access Protocol (IMAP), defined in [RFC- 1730]. These solutions have the advantage of allowing mobile subscribers to communicate seamlessly with remote Internet users (using the same message formats and server access protocols). However, these solutions have proven to be very impractical to use without a minimum adaptation to the constraints of mobile devices and networks. The major barriers to the success of these solutions are the ‘pull’ model for retrieving messages which requires frequent accesses to the Email server and the fact that server access protocols are not resource efficient. In order to offer an Email service adapted to the requirements of mobile subscribers, the company Research in Motion (RIM) designed a set of extensions for the existing Email service. This extended Email service, offered to subscribers under the denomination ‘Black- berry service’, bypasses Email inadequacies to the mobile domain by enabling: † a ‘push’ model for message retrieval † a compression of messages † an encryption of messages. Two main configurations are available for the Blackberry service. The first configuration 338 Mobile Messaging Technologies and Services Figure 7.2 The Blackberry service configuration limits the impact on existing Email architectures by integrating a ‘desktop’ Blackberry application (the Blackberry desktop redirector) in the user’s personal computer used for accessing Email messages. When the user is on the move, the desktop application intercepts incoming messages, compresses them, encrypts them and pushes them to the Blackberry device via a mobile network. The other way round, the user can compose a new message with the Blackberry device. The message is compressed and encrypted by the device and sent via the mobile network to the desktop application. The desktop application receives the message (by polling the Email server), decompresses and decrypts it and sends it normally to the message recipients as if the message had been sent out directly by the user from his/her personal computer. A more sophisticated configuration of the Blackberry service consists of installing an extension to the Email server itself (the Blackberry enterprise server). Basically, in the second configuration, the user’s personal computer does not have to be left running when the user is on the move. With this configuration, messaging functions performed by the desktop application in the first configuration are performed here by the server extension. In addition, this configuration also allows the synchronization of calendaring and scheduling data between shared corporate databases and remote Blackberry devices. The enterprise configuration of the Blackberry service is depicted in Figure 7.2. The Blackberry service is already available in North America and is currently being deployed in other countries in Europe (United Kingdom and France). The service fulfils particularly well the needs of itinerant professional users, who avoid using laptop computers while on the move (because of long dial-up time for accessing Email servers, etc.). The Multimedia Messaging Service (MMS), described in the previous chapter, targets the mass market by supporting a messaging service, similar to the Email service, with small handsets. On the other hand, the Blackberry service targets the professional market with devices 339 Other Mobile Messaging Services designed as Personal Digital Assistants. More information can be obtained on the Blackberry service from Research in Motion (RIM) at http://www.rim.com and Blackberry service at http://www.blackberry.net. 7.3 IMS Messaging Chapter 1 introduced the two phases for UMTS. The second phase of UMTS is built on the IP-based Multimedia Service (IMS) based on the Session Initiation Protocol (SIP) for session/ call management. The 3GPP recently initiated work on messaging services based on a combination of IMS service capabilities (e.g. presence) and already defined messaging services (SMS, EMS and MMS). The scope of this work initially consists of identifying (in the release 6 timeframe) the requirements for messaging services in the IMS environment. These requirements will be detailed in the technical report [3GPP-22.940]. Appendices A TP-PID Values for Telematic Interworking For enabling SMS interworking with various telematic devices, the set of protocol identifiers (TP-Protocol-Identifier) listed in Table 1 can be used. Table 1 Protocol identifiers for telematic interworking TP-PID value (hex) Description 0x20 Type of telematic device is defined by the message destination or originator address. 0x21 Telex (or teletex reduced to telex format) 0x22 Group 3 telefax 0x23 Group 4 telefax 0x24 Voice telephone (i.e. conversion to speech) 0x25 European Radio Messaging System (ERMES) 0x26 National paging system (type known to the service centre) 0x27 Videotext such as T.100 or T101 0x28 Teletex, carrier unspecified 0x29 Teletex, in PSPDN 0x2A Teletex, in CSPDN 0x2B Teletex, in analogue PSTN 0x2C Teletex, in digital ISDN 0x2D Universal Computer Interface (UCI) 0x2E…0x2F Reserved (2 values) 0x30 Message handling facility (type known to the service centre) 0x31 Public X.400-based message handling system 0x32 Internet electronic mail 0x33…0x37 Reserved (5 values) 0x38…0x3E SC specific use (7 values) 0x3F GSM or UMTS
Load more

Recommended publications
  • Tdoc TP-020013 Jeju, Korea, March 2002
    3GPP TSG-T (Terminals) Meeting #15 Tdoc TP-020013 Jeju, Korea, March 2002 Agenda Item: 5.2.3 Source: T2 Title: "MExE" Change Requests Document for: Approval ___________________________________________________________________________ Spec CR Rev Rel Subject Cat Vers- Vers- T2 Tdoc Workitem Curr New 23.057 107 Rel-5 Adding ARPK to the abbreviation list F 4.4.0 5.0.0 T2-020054 MEXE-ENHANC 23.057 108 Rel-5 Updating the references F 4.4.0 5.0.0 T2-020070 MEXE-ENHANC 23.057 109 Rel-5 Replacing MExE application with F 4.4.0 5.0.0 T2-020073 MEXE-ENHANC MExE executable 23.057 110 Rel-4 Changing the urls for the CLDC/MIDP F 4.4.0 4.5.0 T2-020078 MEXE-ENHANC references 23.057 111 Rel-5 Classmark 4 non-security B 4.4.0 5.0.0 T2-020285 MEXE-ENHANC 23.057 112 Rel-5 Classmark 4 security B 4.4.0 5.0.0 T2-020089 MEXE-ENHANC 23.057 113 Rel-5 Adding MSISDN to the security table F 4.4.0 5.0.0 T2-020286 MEXE-ENHANC 23.057 114 Rel-5 Making storage of ORPK in ME F 4.4.0 5.0.0 T2-020287 MEXE-ENHANC optional 23.057 115 Rel-5 Interpretation of user control F 4.4.0 5.0.0 T2-020288 MEXE-ENHANC 23.057 116 Rel-5 Specify more explicitly the MExE F 4.4.0 5.0.0 T2-020289 MEXE-ENHANC executable definition 23.057 117 Rel-5 Remove unused abbreviations F 4.4.0 5.0.0 T2-020290 MEXE-ENHANC 3GPP TSG-T2 #16 T2-020054 Sophia Antipolis, France 11-15 February 2002 CR-Form-v5 CHANGE REQUEST a 23.057 CR 107 a rev - a Current version: 4.4.0 a For HELP on using this form, see bottom of this page or look at the pop-up text over the a symbols.
    [Show full text]
  • Frequently Asked Questions
    Frequently Asked Questions www.wireless-village.org The Wireless Village initiative: FAQs 26 April 2001 1. Instant Messaging and Presence Services (IMPS) 1.1 What is IMPS? It stands for “instant messaging and presence service”, and includes four primary features: · Presence · Instant Messaging · Groups · Shared Content In the mobile Internet society, people have a greater need to communicate than ever before. In wire-line networks, people can use online chat software to communicate across the Internet using short text, or even multimedia, messages. This type of service is called an “instant messaging service”. In mobile networks, similar short message services have existed since the introduction of digital mobile phone service. The utility of instant messaging is greatly enhanced by the addition of a service that will keep track of the online status and availability of your chat partners or “friends”; as well as notify you of changes to their status or availability. This type of service is called a “presence service”. The combination of instant messaging, presence, groups, and shared content is called an IMPS. 1.2 Is the concept of IMPS new? No. Ever since the introduction of early time-sharing computer systems, there has been the availability of services desired to allow users of these systems to communicate or “chat” between terminals using short text messages. Some have even provided session based services that provide a “chat room” feature. Digital mobile phone users are also familiar with mobile-terminated and mobile- originated short messaging services. These services allow text-based messaging between mobile phone users. Internet “web portal” and online services users are also familiar with chat, chat room capabilities and “friends lists” for maintaining chat addresses of friends; along with their online status and availability.
    [Show full text]
  • CDG IOTA/HCM Stage-3
    1 3GPP2 C.S0040 2 Version 1.0 3 Date: July 18, 2003 4 5 6 IP Based Over-the-Air 7 Handset Configuration Management (IOTA-HCM) 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 COPYRIGHT 3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information. 23 24 3GPP2 C.S0040 1 No text. 2 ii 3GPP2 C.S0040 CONTENTS 1 2 FOREWORD................................................................................................................ vii 3 NOTES ....................................................................................................................... viii 4 REFERENCES..............................................................................................................ix 5 1. Introduction ......................................................................................................11 6 1.1. Scope ................................................................................................................11 7 1.2. Definitions.........................................................................................................11 8 2. General Requirements .......................................................................................17
    [Show full text]
  • DRM Specification Approved Version 2.1 – 06 Nov 2008
    DRM Specification Approved Version 2.1 – 06 Nov 2008 Open Mobile Alliance OMA-TS-DRM-DRM-V2_1-20081106-A 2008 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-Template-DRM-20080101-I] OMA-TS-DRM-DRM-V2_1-20081106-A Page 2 (214) Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html. Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document. Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification.
    [Show full text]
  • TSG RAN Meeting #20 RP-030281 Hämeenlinna, Finland, 3 - 6 June, 2003
    TSG RAN Meeting #20 RP-030281 Hämeenlinna, Finland, 3 - 6 June, 2003 Title: 3GPP-OMA Overlap Report Source: TSG-T Vice Chair (Kevin Holley) Agenda Item: Document for: Discussion During the TSG SA #19 meeting in Birmingham it was proposed that a study be undertaken to identify work underway in 3GPP which is related to work in OMA, in order that SA can decide on what additional co-ordination mechanisms (if any) are required with OMA work. This report is presented to RAN, CN, T and SA for discussion and conclusion on a way forwards during the SA meeting. Introduction The Open Mobile Alliance (OMA) was formed in June 2002, creating an organisation suited to the development and publication of applications specifications. It was formed from the WAP Forum, with the addition of several other fora including SyncML, Wireless Village and LIF. The working procedures in OMA have substantially changed from the WAP forum procedures and are in many ways now similar to 3GPP’s, with Work Items (4 supporting companies), Requirements and Architecture documents, plus more detailed technical specifications. There is also a Change Request procedure which replaced the old WAP Forum method of publishing separate change documents alongside the original specification. The intention of OMA, as outlined in a presentation to the 3GPP PCG in October 2002, is to develop application enablers or “service enablers” which can run over a variety of different mobile networks including those specified by 3GPP. OMA already has activity underway on many service enablers including Instant Messaging, Multimedia Messaging (MMS), Location Services, Device Management, Device Synchronisation, Games Services, Download, DRM and mobile browsing capabilities.
    [Show full text]
  • Lecture Set 4 - the Mobile Internet
    COMP327 Mobile Computing Lecture Set 4 - The Mobile Internet 1 In this Lecture Set • Challenges of Mobile access to the Internet • Early Wireless Internet Systems • AT&T PocketNet • Palm.Net WebClipping • i-Mode • Wireless Application Protocol • Architecture and Application Environment • Multimedia Messaging Service • Short Messaging Service • OTA Programming 2 The challenges in moving from fixed line PCs to Mobile Devices • To understand the challenges (and pitfalls) of moving to a Mobile Internet, first consider the fixed line Internet! • Initially, most usage was email and web • Mostly free, other than modem connection charges • Top down content distribution model • The web was “read-only” - Web 1.0 • Early retailers (e.g. Amazon) exposed inventory, but offered few value-based services • Evolved slowly over several years (“incubation time”), driven by access and expectation • Technologies had the chance to settle and be tested before large-scale adoption 3 The challenges in moving from fixed line PCs to Mobile Devices • Things were different when the Mobile Internet launched • Access was initially targeted at general public • Previous technologies were tried and tested by students and universities, which ironed out problems • Access was charged from day one! • Reduced adoption, and raised false expectation • Content and Services was adapted from the Web, rather than redesigned to exploit mobility • Very few sites or services had any appeal or use for users • WAP stack required new tools and additional effort, yet served a small user base!
    [Show full text]
  • Emerging Technologies in Mobile and Wireless Data Network Evolution Proceedings of the Research Seminar on Telecommunications Business
    Helsinki University of Technology Publications in Telecommunications Software and Multimedia Teknillisen korkeakoulun tietoliikenneohjelmistojen ja multimedian julkaisuja Espoo 2003 TML-C11 Emerging Technologies in Mobile and Wireless Data Network Evolution Proceedings of the Research Seminar on Telecommunications Business Editor Sakari Luukkainen ISBN 951-22-6622-9 ISSN 1455-9749 2 Helsinki University of Technology Telecommunications Software and Multimedia Laboratory P.O. Box 5400 FIN-02015 HUT Tel. +358-9-451 2870 Fax. +358-9-451 5253 Helsinki University of Technology Telecommunications Software and Multimedia Laboratory Publications in Telecommunications Software and Multimedia Teknillisen korkeakoulun tietoliikenneohjelmistojen ja multimedian julkaisuja TML-C11 Espoo, 2003 Emerging Technologies in Mobile and Wireless Data Network Evolution Proceedings of the Research Seminar on Telecommunications Business II, spring 2003 Editor: Sakari Luukkainen (Lic.Tech.) Keywords: mobile networks, wireless neworks, telecommunication business & investments, UWB, AdHoc, UMTS, WLAN, SDR, CDPD, EDGE, MMW, 60 GHz, MPEG-4, MVAS, Wireless Instant Messaging, Mobile Entertainment The articles have been written by the students of the course T-109.551 Research Seminar on Telecommunications Business II in the spring 2003. The authors have full copyright to their articles. Technical editing by Eino Kivisaari. http://www.tml.hut.fi/Studies/T-109.551/2003/Proceedings.pdf ISBN: 951-22-6622-9 ISSN: 1455-9749 URN:NBN:fi-fe20031401 3 Preface Mobile and wireless technologies are now in a discontinuous phase. As cellular mobile networks evolve from enhanced GSM to next generation systems by pro- viding faster data connections, personal area networks (PAN) and wireless local area networks (WLAN) are also gaining popularity. Several wireless technologies are emerging, the success of which is unclear due to complex market dynamics, technology development and risks related to both.
    [Show full text]
  • Now SMS/MMS Developer Toolkit
    Now SMS/MMS Gateway 2006 Edition http://www.nowsms.com © Copyright 2002-2006 by Now Wireless Limited, All Rights Reserved Publication Date: March 1, 2006 © Copyright 2002-2006 by Now Wireless Limited, All Rights Reserved Publication Date: March 1, 2006 NOW SMS/MMS GATEWAY...................................................................................................................... 1 SMS AND MMS PROTOCOLS IMPLEMENTED BY NOWSMS..................................................................................3 MMS Gateway Connectivity (client protocols).......................................................................................3 SMS Gateway Connectivity (client protocols)........................................................................................3 Application Connectivity for MMS Submission (server protocols)........................................................ 3 Application Connectivity for SMS Submission (server protocols)......................................................... 3 EXAMPLES OF HOW CUSTOMERS USE NOWSMS.................................................................................................4 NOWSMS QUICK START: BASIC CONFIGURATION........................................................................6 NEED HELP?................................................................................................................................................... 7 INSTALLING NOWSMS..............................................................................................................................8
    [Show full text]
  • Winwap Browser Application Environment
    Winwap Technologies Oy WinWAP Browser Application Environment WinWAP Browser version 4.0 WAP Specification version 2.0 Wireless Markup Language Specification version 2.0 Document dated: 26 Mar 2007 WinWAP Browser Application Environment http://www.winwap.com Notice of Confidentiality This document contains proprietary and confidential information that belongs to Winwap Technologies Oy. The recipient agrees to maintain this information in confidence and to not reproduce or otherwise disclose this information to any person outside of the group directly responsible for the evaluation of the content. Revision history Date Author Description 22-Jun-2004 S Markelov Draft version of the document. 05-Jan-2005 Maria Sandell English spell checked. 26-Mar-2007 S Markelov Updated and extended with XHTML and HTML static conformances. Preamble Wireless Application Environment (WAE) is part of the Open Mobile Alliance’s effort to specify an application framework for wireless terminals such as mobile phones, pagers, and PDAs. The framework extends and leverages other WAP technologies, including WTP and WSP, as well as other Internet technologies such as XML, URLs, scripting, and various media types. The effort enables operators, manufacturers, and content developers to meet the challenges in building advanced and differentiated services and implementations in a fast and flexible manner. WinWAP Browser is a WAE User Agent in terms of the “Wireless Application Environment Specification” Version 2.2, OMA-WAP-WAESpec-V2_2-20040609-C, Candidate Version 2.2 — 09 Jun 2004. This document describes a set of features implemented to ensure that the WAE User Agent and the WAE Server are able to inter-operate.
    [Show full text]
  • Wireless Presence and Instant Messaging © JISC 2002
    TSW 02-07 November 2002 Wireless Presence and Instant Messaging Yanna Vogiazou Knowledge Media Institute The Open University MK7 6AA Milton Keynes United Kingdom Tel: +44(0) 1908 654775 Email: [email protected] © JISC 2002 TABLE OF CONTENTS 1. EXECUTIVE SUMMARY 2 2. THE TECHNOLOGY 2 3. THE TECHNOLOGY WATCH ISSUE 5 4. TECHNICAL OVERVIEW 6 4.1 M ESSAGING DEVELOPMENTS 6 4.1.1 MOBILE MESSAGING STANDARDS 6 4.1.2 PROTOCOLS AND NETWORKS 7 4.1.3 JAVA APPLICATION DEVELOPMENT 8 4.2 INTEROPERABILITY 8 4.2.1 BILLING – RELATED PROBLEMS 8 4.2.2 STANDARDS BODIES AND PROTOCOLS 9 4.2.3 THE EXAMPLE OF JABBER 10 4.3 OTHER CONSTRAINTS 12 4.3.1 PRIVACY CONCERNS 12 4.3.2 SECURITY 12 4.3.3 USABILITY 12 5. WHAT IS THE VALUE FOR HE/FE 12 6. FUTURE DIRECTIONS 14 7. ACKNOWLEDGMENTS 15 8. RESOURCES FOR FURTHER INFORMATION 15 9. GLOSSARY 16 10. REFERENCES 18 Yanna Vogiazou, KMi, The Open University November 2002 © JISC Report Page 1 of 21 1. Executive Summary The advances of new technologies and the convergence of different communication media are constantly changing not only our means and modes of communication with other people, but the notion of connectivity itself. Rather that being online or offline, we can be ‘connected’ in many different ways and without directly interacting with technology itself. ‘Presence’ awareness, facilitated by Instant Messaging applications, mobile phones, wireless handheld devices, location tracking and so on, can make someone reachable almost at any time. In view of this rapidly developing field, this report aims to identify the most important issues related to the development of Instant Messaging and Presence enabled applications for wireless devices.
    [Show full text]
  • Instant Messaging and Wireless Presence
    Instant Messaging and Wireless Presence Craig Peddie General Manager Motorola Lexicus Division Market Opportunity • Instant Messaging is just the beginning – Popularity is indicator of customer desire for presence • 623 million worldwide instant messaging users by 2003 (IDC) • Wireless messages sent per month will balloon from 3 Billion in 2000 to 244 Billion by 2005 (Cahners) – Wireless internet users will benefit from presence • Cell phones, pagers, PDA’s, network appliances • By 2004 3 Million two-way pagers will be used in the US (Forrester) – Peer-to-Peer (P2P) enabler • Presence will be as pervasive as e-mail – 1.3 Billion wireless Internet users by 2004 (Source: Cahners InStat) – Presence is viral and grows exponentially - “network effect” – All wireless devices and applications will use presence • Increased business/corporate spending – Wireless application spending among North American enterprise businesses will increase six-fold in the next two years to $878 million (Source: Research Portal.com) IM Market Demand Most Desired Internet Applications on a Wireless Phone • Instant Messaging is Sending and Receiving e- 3rd most desired 70% mail Internet Application 66% on a wireless phone 58% Instant Messaging 56% • IM is #1 feature on Pulling down specific 51% Smart phones for info from the web both mobile 47% Purchasing products professionals and 29% over the web mobile consumers 24% Researchportal.com Online trading of 17% securities & stocks Source: Cahners In-Stat Group 9/00 Wireless IM Market Projections End users Value Year
    [Show full text]
  • CDMA2000 Workshop Paul Le Rossignol Nortel Networks, OMA Board Director Open Mobile Alliance
    CDMA2000 Workshop Paul Le Rossignol Nortel Networks, OMA Board Director Open Mobile Alliance 1Vision and Mission of OMA 2OMA’s Market Position & Industry Benefits 3Structure & Scope 4OMA Interoperability & Service Enablers 5Summary Copyright © March 2004 2 Open Mobile Alliance Ltd. All Rights Reserved. OMA Vision No matter what device I have, no “matter what service I want, no matter what carrier or network I’m using, I can communicate, access and exchange information.” Copyright © March 2004 3 Open Mobile Alliance Ltd. All Rights Reserved. OMA Mission The mission of the Open Mobile Alliance is to facilitate global user adoption of mobile data services by specifying market driven mobile service enablers that ensure service interoperability across devices, geographies, service providers, operators, and networks while allowing businesses to compete through innovation and differentiation. Copyright © March 2004 4 Open Mobile Alliance Ltd. All Rights Reserved. OMA: Strength in Numbers Over 380 OMA member companies represent a truly global organization with members from all regions of the world OMA Regional Membership 22 134 156 83 Americas Asia Europe Middle East Copyright © March 2004 5 Open Mobile Alliance Ltd. All Rights Reserved. Why OMA is the Right Solution for the Mobile Industry? Open, interoperable specifications implemented by multiple vendors can result it: De-facto interoperability between geographies, Enriched user experience across service providers Compelling new business opportunities through a global market Faster time to market Reduced R&D costs Copyright © March 2004 6 Open Mobile Alliance Ltd. All Rights Reserved. Current Cooperation Agreements and Frameworks in Place… 3GPP MOBEY Forum 3GPP2 MPA CDG MPF ETSI OASIS GSMA Parlay IETF PayCircle IFPI RIAA ITU-T WiFi Alliance Liberty Alliance W3C MeT Copyright © March 2004 7 Open Mobile Alliance Ltd.
    [Show full text]