DOCSLIB.ORG

Multimedia Messaging Service : an Engineering Approach To

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Multimedia Messaging Service : an Engineering Approach To Multimedia Messaging Service Multimedia Messaging Service An Engineering Approach to MMS Gwenael¨ Le Bodic Alcatel, France Copyright 2003 John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England Telephone (+44) 1243 779777 Email (for orders and customer service enquiries): [email protected] Visit our Home Page on www.wileyeurope.com or www.wiley.com All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except under the terms of the Copyright, Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licensing Agency Ltd, 90 Tottenham Court Road, London W1T 4LP, UK, without the permission in writing of the Publisher. Requests to the Publisher should be addressed to the Permissions Department, John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England, or emailed to [email protected], or faxed to (+44) 1243 770620. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold on the understanding that the Publisher is not engaged in rendering professional services. If professional advice or other expert assistance is required, the services of a competent professional should be sought. Other Wiley Editorial Offices John Wiley & Sons Inc., 111 River Street, Hoboken, NJ 07030, USA Jossey-Bass, 989 Market Street, San Francisco, CA 94103-1741, USA Wiley-VCH Verlag GmbH, Boschstr. 12, D-69469 Weinheim, Germany John Wiley & Sons Australia Ltd, 33 Park Road, Milton, Queensland 4064, Australia John Wiley & Sons (Asia) Pte Ltd, 2 Clementi Loop #02-01, Jin Xing Distripark, Singapore 129809 John Wiley & Sons Canada Ltd, 22 Worcester Road, Etobicoke, Ontario, Canada M9W 1L1 Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books. British Library Cataloguing in Publication Data A catalogue record for this book is available from the British Library ISBN 0-470-86253-X Typeset in 10.5/13pt Times by Laserwords Private Limited, Chennai, India Printed and bound in Great Britain by TJ International, Padstow, Cornwall This book is printed on acid-free paper responsibly manufactured from sustainable forestry in which at least two trees are planted for each one used for paper production. Contents Preface xiii About the Author xvii 1 Introduction to MMS 1 1.1 MMS Success Enablers 2 1.2 Commercial Availability of MMS 4 1.3 MMS Compared with Other Messaging Services 4 1.3.1 SMS and EMS 4 1.3.2 Electronic Mail 5 1.3.3 J-phone’s Sha-mail and NTT Docomo’s i-shot 5 1.3.4 RIM’s Blackberry 7 1.4 MMS Added Value and Success Factors 8 1.5 Billing Models 9 1.6 Usage Scenarios 10 1.6.1 Person-to-person Messaging 10 1.6.2 Content-to-person Messaging 11 1.6.3 Further Applications 12 Further Reading 12 2 Standardization of MMS 13 2.1 MMS Standards 14 2.2 Third Generation Partnership Project 15 2.2.1 3GPP Structure 16 2.2.2 3GPP Specifications: Release, Phase and Stage 16 2.2.3 3GPP Specifications: Numbering Scheme 18 2.3 Third Generation Partnership Project 2 20 2.4 WAP Forum Specifications 20 2.5 Internet Engineering Task Force 22 2.5.1 IETF Documents 22 2.5.2 Internet Standard Track 23 2.6 World Wide Web Consortium 23 vi Contents 2.7 Open Mobile Alliance 25 2.7.1 OMA Organization 25 2.7.2 OMA Specifications 27 2.7.3 Available Documents 28 2.8 Standardization Roadmap for MMS 29 Further Reading 33 3 Service Architecture 35 3.1 MMS Architecture 35 3.2 MMS Interfaces 36 3.3 MMS Client 38 3.4 MMS Centre 38 3.5 Wireless Application Protocol 39 3.5.1 Introduction to WAP 39 3.5.2 WAP Architecture 41 3.5.3 Push Technology 41 3.5.4 User Agent Profile 44 3.5.5 WAP 1.x Legacy Configuration 45 3.5.6 WAP HTTP Proxy with Wireless Profiled TCP and HTTP 46 3.5.7 Direct Access 47 3.5.8 WAP Configurations for MMS 47 3.5.9 WTP Segmentation and Reassembly 48 3.6 OMA Digital Rights Management 50 4 Service Features 53 4.1 Message Sending 53 4.2 Message Retrieval 55 4.2.1 Immediate Retrieval 55 4.2.2 Deferred Retrieval 55 4.2.3 Retrieval When Roaming 56 4.2.4 Automatic Rejection of Unsolicited or Anonymous Messages 56 4.3 Message Reports 56 4.3.1 Delivery Reports 57 4.3.2 Read Reports 57 4.4 Message Forward 57 4.5 Reply Charging 57 4.6 Addressing Modes 58 4.7 Settings of MMS Mobile Devices 58 4.7.1 Connectivity Settings 58 4.7.2 User Preferences 59 4.7.3 Storing and Provisioning MMS Settings 60 4.8 Storage of MMS Settings and Notifications in the (U)SIM 61 Contents vii 4.9 Multimedia Message Boxes 62 4.10 Value-added Services 63 4.11 Capability Negotiation 64 4.12 Streaming 68 4.12.1 Example of MMS Architecture for the Support of Streaming 68 4.12.2 Streaming Protocols: RTP and RTSP 70 4.13 Charging and Billing 71 4.14 Security Considerations 73 5 The Multimedia Message 75 5.1 Multipart Structure 75 5.1.1 Message Envelope 76 5.1.2 Encapsulation of Media Objects 77 5.2 Message Content Domains and Classes 78 5.2.1 Message Content Domains 82 5.2.2 Message Content Classes 83 5.2.3 MMS Client Conformance to Message Content Classes 84 5.3 Media Types, Formats and Codecs 85 5.3.1 Text 86 5.3.2 Bitmap and Still Images 86 5.3.3 Vector Graphics 87 5.3.4 Speech 88 5.3.5 Audio and Synthetic Audio 89 5.3.6 Video 91 5.3.7 Personal Information Manager Objects 91 5.4 Scene Description 93 5.4.1 Introduction to SMIL 93 5.4.2 Organization of SMIL 2.0 94 5.4.3 Spatial Description with SMIL 94 5.4.4 Temporal Description with SMIL 96 5.4.5 SMIL Basic Profile 96 5.4.6 MMS SMIL and the OMA Conformance Document 97 5.4.7 SMIL Namespace 102 5.4.8 Linking the Scene Description with Body Parts 102 5.4.9 Support of Video Streaming 104 5.4.10 Support of Colour with SMIL 105 5.4.11 XHTML as an Alternative to SMIL 106 5.5 Example of a Multimedia Message 106 5.6 Forward-lock of Media Objects 109 5.7 Message Size Measurement 109 Further Reading 111 viii Contents 6 Transactions Flows 113 6.1 Introduction to the MMS Transaction Model 113 6.1.1 Person-to-person Scenarios 114 6.1.2 Content-to-person Scenarios 116 6.1.3 How to Read the PDU Description Tables 117 6.2 MM1 Interface, MMS Client – MMSC 118 6.2.1 Message Submission 121 6.2.2 Message Notification 127 6.2.3 Message Retrieval 133 6.2.4 Delivery Report 138 6.2.5 Read Report 140 6.2.6 Message Forward 143 6.2.7 Storing and Updating a Message in the MMBox 147 6.2.8 Viewing Information from the MMBox 149 6.2.9 Uploading a Message to the MMBox 155 6.2.10 Deleting a Message from the MMBox 157 6.2.11 Parameter Description and Binary Encoding 157 6.3 MM2 Interface, Internal MMSC Interface 167 6.4 MM3 Interface, MMSC–External Servers 167 6.5 MM4 Interface, MMSC–MMSC 167 6.5.1 Introduction to SMTP 169 6.5.2 Routing Forward a Message 172 6.5.3 Routing Forward a Delivery Report 175 6.5.4 Routing Forward a Read Report 175 6.5.5 Example for Message Transfer with SMTP 177 6.6 MM5 Interface, MMSC–HLR 179 6.7 MM6 Interface, MMSC–User Databases 180 6.8 MM7 Interface, MMSC–VAS Applications 180 6.8.1 Introduction to SOAP 183 6.8.2 Message Submission 185 6.8.3 Message Delivery 188 6.8.4 Message Cancellation 190 6.8.5 Message Replacement 191 6.8.6 Delivery Report 195 6.8.7 Read Report 202 6.8.8 Generic Error Handling 204 6.9 MM8 Interface, MMSC–Billing System 205 7 Standard Compliance and Interoperability 207 7.1 Standard Conformance and Interoperability Testing 207 7.1.1 Static Conformance Requirements 207 7.1.2 Enabler Implementation Conformance Statement 208 Contents ix 7.1.3 Enabler Test Requirements, Plan and Specification 209 7.1.4 Interoperability Testing 209 7.2 Implementations of Different Versions of the MMS Protocol 210 8 Commercial Solutions and Developer Tools 213 8.1 MMS Handsets Directory 213 8.2 MMSC Directory 213 8.3 Developer Tools 214 9 The Future of MMS 221 9.1 MMS Developments in 3GPP 221 9.1.1 MMS Release 6 221 9.1.2 IMS Messaging 222 9.2 MMS Development in OMA 223 9.3 MMS Developments in 3GPP2 223 9.4 A Bright Future for MMS? 224 Appendices 225 A Content Types of Media Objects 225 B MM1 Interface – Response Status Codes (X-Mms-Response-Status) 225 C MM1 Interface – Retrieve Status Codes (X-Mms-Retrieve-Status) 228 D MM1 Interface – MMBox Store Status Codes (X-Mms-Store-Status) 229 E MM4 Interface – Request Status Codes (X-Mms-Request-Status-Code) 230 F MM7 Interface – Status Code and Status Text 231 References 235 Acronyms and Abbreviations 241 Index 247 The nice thing about standards is that there are so many to choose from Andrew S.
Load more

Recommended publications
  • An Architecture of Mobile Web 2.0 Context-Aware Applications in Ubiquitous Web
    JOURNAL OF SOFTWARE, VOL. 6, NO. 4, APRIL 2011 705 An Architecture of Mobile Web 2.0 Context-aware Applications in Ubiquitous Web I-Ching Hsu Department of Computer Science and Information Engineering National Formosa University 64, Wenhua Rd., Huwei Township, Yunlin County 632, Taiwan [email protected] Abstract—The rapid development of the wireless an uniformly access to cope with the heterogeneous communication technologies, including wireless sensors, effects, including various context presentation, context intelligent mobile devices, and communication protocols, information, mobile device constraints, and context has led to diverse mobile devices of accessing various middleware [4]. To allow interoperability among the context-aware systems. Existing context-aware systems only various context-aware systems and mobile devices, a focus on characterize the situation of an entity to exhibit the advantage of contextual information association. The common standard is needed to uniformly access context contextual information can represent semantic implications information provided via a fundamental infrastructure. to provide decidable reasoning services, but it has no The Web 2.0 technologies provide a catalytic solution to mechanism to facilitating the interoperability and this problem. reusability among heterogeneous context-aware systems and Within the last two to three years, the Internet has various mobile devices. This study addresses these issues greatly changed our way of sharing resources and developing a Multi-layer Context Framework (MCF) that information. As well known, Web 2.0 is recognized as integrates Web 2.0 technologies into context-aware system the next generation of web applications proposed by T. for supporting ubiquitous mobile environment. The O’Reilly [5].
    [Show full text]
  • Web & Mobile Security
    WEB & MOBILE SECURITY KNOWLEDGE AREA (DRAFT FOR COMMENT) AUTHOR: Sascha Fahl – Leibniz University EDITOR: Emil Lupu – Imperial College London © Crown Copyright, The National Cyber Security Centre 2019. Following wide community consultation with both academia and industry, 19 Knowledge Areas (KAs) have been identified to form the scope of the CyBOK (see diagram below). The Scope document provides an overview of these top-level KAs and the sub-topics that should be covered under each and can be found on the project website: https://www.cybok.org/. We are seeking comments within the scope of the individual KA; readers should note that important related subjects such as risk or human factors have their own knowledge areas. It should be noted that a fully-collated CyBOK document which includes issue 1.0 of all 19 Knowledge Areas is anticipated to be released in October 2019. This will likely include updated page layout and formatting of the individual Knowledge Areas. Web and Mobile Security Sascha Fahl September 2019 INTRODUCTION The purpose of this Knowledge Area is to provide an overview of security mechanisms, attacks and defences in modern web and mobile ecosystems. This overview is intended for use in academic courses in web and mobile security, and to guide industry professionals who are interested in an overview of web and mobile security. Web and mobile security have a long history, and their impact on overall information security is tremendous due to the sheer prevalence of web and mobile applications. Covering both web and mobile security, this Knowledge Area emphasises the intersection of their security mechanisms, vul- nerabilities and mitigations.
    [Show full text]
  • Management Enablement(OMA)
    ONEM2M TECHNICAL SPECIFICATION Document Number TS-0005-V3.5.1 Document Name: Management Enablement (OMA) Date: 2019-04-18 Abstract: Specifies the usage of OMA DM and OMA LwM2M resources and the corresponding message flows including normal cases as well as error cases to fulfill the oneM2M management requirements. • Mapping between the oneM2M management related resources and the resources from OMA. • Protocol translation between the oneM2M service layer and OMA. The Mca reference point, ms interface and la interface are possibly involved in this protocol translation. • Resource definitions in OMA to fulfill the oneM2M management requirements. This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification. The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices. © oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC) Page 1 of 92 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. About oneM2M The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. More information about oneM2M may be found at: http//www.oneM2M.org Copyright Notification No part of this document may be reproduced, in an electronic retrieval system or otherwise, except as authorized by written permission.
    [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]
  • Mobile Banking Frequently Asked Questions How Much Does This Service Cost?
    Mobile Banking Frequently Asked Questions How much does this service cost? There is currently no charge associated with the service. However, there may be charges associated with text messaging and data usage on your phone. Check with your wireless phone carrier for more information. Is it secure? Yes, the mobile banking service utilizes best practices from online banking, such as HTTPS, 128-bit SSL encryption, PIN, or password access and application time-out when your phone is not in use. Only the phones that you personally enroll in the service can access your accounts. In addition, no account data is ever stored on your phone. And in the event your phone is lost or stolen, the service can be immediately disabled by either going online to the Mobile Banking enrollment website or calling us. Do I need a text message or data plan? Yes, a text messaging and/or data plan is typically needed, as data usage can become expensive without them. Please check with your wireless carrier for more information. I'm not enrolled for online banking. What mobile carriers are supported? The Norrymobile banking app can be accessed through the following carriers: AT&T, Sprint, Verizon, T- Mobile, and any of their supported carriers. Can I still use this? You must first enable your bank account(s) for online banking before using mobile. What is Activation? Activation is a one-time process that helps ensure your security. After you enroll a phone, you will receive an activation code which will be required to begin using Text or Mobile Banking on your device.
    [Show full text]
  • Critical Mass the Worldwide State of the Mobile Web
    Critical Mass The Worldwide State of the Mobile Web Nielsen Mobile July 2008 Critical Mass: The Worldwide State of the Mobile Web Introduction Key Takeaways It is increasingly difficult to talk about the Internet, or media and marketing in general, without the conversation quickly • The US, UK and Italy are leaders in mobile Internet turning to mobile phones. penetration. 15.6 percent of mobile subscribers in the US, 12.9 percent of subscribers in the UK and 40 million mobile subscribers in the US, plus millions more 11.9 percent in Italy actively use the mobile Internet across Europe and Asia, surf the web through a mobile phone each month—checking email, exploring their social • We believe mobile Internet has reached a critical networks, making bank transactions and engaging in other mass as an advertising medium in the US. As of web activities right from their hands. May 2008, there were 40 million active users of the mobile Internet in the US, with individual sites that How has mobile Internet so quickly become part of the attract millions of unique users. This provides consumer media experience for millions? Through a scalable marketing potential with demographic confluence of essential factors in mobile Internet adoption breadth. and use, mobile Internet reached a critical mass this year, offering a large and diverse enough base of users to • Unlimited data packages are an important part of support large-scale mobile marketing efforts. the growth of the mobile Internet and are increasingly popular with US consumers. Today 14 percent of US wireless subscribers have unlimited data packages, and 50 percent of data users say they would prefer to have such a package.
    [Show full text]
  • Mobile Web Design This Webinar Is Presented by W3C to the Web Community As Part of an EU IST Project (3Gweb)
    Mobile Web Design This webinar is presented by W3C to the Web community as part of an EU IST project (3GWeb). The content of this webinar does not necessarily represent the official position of the W3C, or the position of any of the W3C members or W3C’s host institutions. (Lawyer says ‘Hi’!) 2 © MMVI Cameron Moll. This document is available under the W3C Document License. You are... Experienced with XHTML/CSS. Familiar with good markup techniques. Unsure about this “mobile web thing”. 3 © MMVI Cameron Moll. This document is available under the W3C Document License. Legacy 1910 5 © MMVI Cameron Moll. This document is available under the W3C Document License. “Pocket watches provide the closest historical parallel to the remarkable rise of the mobile phone.” —Jon Agar, Constant Touch 6 © MMVI Cameron Moll. This document is available under the W3C Document License. Staggering Numbers 1996 GSM phones in 103 countries 2000 10 million i-mode users (Japan) 2002 1 billion mobile phone users worldwide 2009 3 billion mobile phone users worldwide 7 © MMVI Cameron Moll. This document is available under the W3C Document License. UK More mobile phones than humans... 8 © MMVI Cameron Moll. This document is available under the W3C Document License. Quandary Reader Poll Highly scientific, statistically significant (not really!) 10 © MMVI Cameron Moll. This document is available under the W3C Document License. ~400 Participants 159 Unique handsets (Motorola RAZR, Palm Treo 650, Sony Ericsson K750i / K700i / T610, Nokia 6230...) 19 Manufacturers 44 Countries 11 © MMVI Cameron Moll. This document is available under the W3C Document License.
    [Show full text]
  • Cell Phones and Pdas
    eCycle Group - Check Prices Page 1 of 19 Track Your Shipment *** Introductory Print Cartridge Version Not Accepted February 4, 2010, 2:18 pm Print Check List *** We pay .10 cents for all cell phones NOT on the list *** To receive the most for your phones, they must include the battery and back cover. Model Price Apple Apple iPhone (16GB) $50.00 Apple iPhone (16GB) 3G $75.00 Apple iPhone (32GB) 3G $75.00 Apple iPhone (4GB) $20.00 Apple iPhone (8GB) $40.00 Apple iPhone (8GB) 3G $75.00 Audiovox Audiovox CDM-8930 $2.00 Audiovox PPC-6600KIT $1.00 Audiovox PPC-6601 $1.00 Audiovox PPC-6601KIT $1.00 Audiovox PPC-6700 $2.00 Audiovox PPC-XV6700 $5.00 Audiovox SMT-5500 $1.00 Audiovox SMT-5600 $1.00 Audiovox XV-6600WOC $2.00 Audiovox XV-6700 $3.00 Blackberry Blackberry 5790 $1.00 Blackberry 7100G $1.00 Blackberry 7100T $1.00 Blackberry 7105T $1.00 Blackberry 7130C $2.00 http://www.ecyclegroup.com/checkprices.php?content=cell 2/4/2010 eCycle Group - Check Prices Page 2 of 19 Search for Pricing Blackberry 7130G $2.50 Blackberry 7290 $3.00 Blackberry 8100 $19.00 Blackberry 8110 $18.00 Blackberry 8120 $19.00 Blackberry 8130 $2.50 Blackberry 8130C $6.00 Blackberry 8220 $22.00 Blackberry 8230 $15.00 Blackberry 8300 $23.00 Blackberry 8310 $23.00 Blackberry 8320 $28.00 Blackberry 8330 $5.00 Blackberry 8350 $20.00 Blackberry 8350i $45.00 Blackberry 8520 $35.00 Blackberry 8700C $6.50 Blackberry 8700G $8.50 Blackberry 8700R $7.50 Blackberry 8700V $6.00 Blackberry 8703 $1.00 Blackberry 8703E $1.50 Blackberry 8705G $1.00 Blackberry 8707G $5.00 Blackberry 8707V
    [Show full text]
  • Symbianos by Himal Humagain Fall.Ppt
    2 Overview In this chapter we’ll present a brief overview of the different parts of Symbian OS we’re going to talk about in this book. Detailed explanations of how things work will be left to the individual technology chapters, but here we’ll take a quick look at what each area does. First we have something of an aside, but on an important topic – that of binary compatibility (BC). Symbian OS v9.0 introduced a major BC break with versions 8.1 and earlier, due to the introduction of a new (standardized) application binary interface (ABI). Therefore applications compiled against v8.1 and earlier of Symbian OS will not run on v9.1 and later. In addition to this, the platform security model requires some changes to applications using communications functionality. Depending on the application this might be as simple as adding a CAPABILITY statement to the MMP file. To start with we take a quick look at a very high-level model of how a Symbian OS-based phone is constructed in order to see where various components fit in. This isn’t to say every phone looks like this, but it is a good enough model to help understand the different layers that exist within Symbian OS. The signalling stack (also referred to as the ‘baseband’ or ‘cellular modem’) is provided by the manufacturer of the device, so Symbian OS contains a series of adaptation layers to allow standard Symbian OS APIs to be adapted to the specific signalling stack in use. Today, all shipping products use either a 2.5G GSM/GPRS or 3G UMTS (aka W-CDMA, aka 3GSM) signalling stack.
    [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]
  • W380 April 2008
    W380 April 2008 Feel music, see music, hear music White paper W380 Preface Purpose of this document This White paper will be published in several revisions as the phone is developed. Therefore, some of the headings and tables below contain limited information. Additional information and facts will be forthcoming in later revisions. The aim of this White paper is to give the reader an understanding of technology used in the phone and its main applications, as well as the main functions and features of the phone. Note: This document contains general descriptions for this specific Sony Ericsson mobile phone. People who can benefit from this document include: • Operators • Service providers • Software developers • Support engineers • Application developers • Market units and sales people This White paper is published by: This document is published by Sony Ericsson Mobile Communications AB, without any warranty*. Improvements and changes to this text Sony Ericsson Mobile Communications AB, necessitated by typographical errors, inaccuracies SE-221 88 Lund, Sweden of current information or improvements to programs and/or equipment, may be made by Phone: +46 46 19 40 00 Sony Ericsson Mobile Communications AB at any Fax: +46 46 19 41 00 time and without notice. Such changes will, however, be incorporated into new editions of this www.sonyericsson.com/ document. Printed versions are to be regarded as temporary reference copies only. © Sony Ericsson Mobile Communications AB, 2008. All rights reserved. You are hereby granted *All implied warranties, including without limitation the implied warranties of merchantability or fitness a license to download and/or print a copy of this for a particular purpose, are excluded.
    [Show full text]
  • Mobile Connection Explorer for Windows Introduction and Features
    Mobile Connection Explorer 15 May 2013 for Windows Version 21 Introduction and Features Public version Gemfor s.r.o. Tyršovo nám. 600 252 63 Roztoky Czech Republic Gemfor s.r.o. Tyršovo nám. 600 252 63 Roztoky Czech Republic e-mail: [email protected] Contents Contents ...................................................................................................................... 2 History ......................................................................................................................... 3 1. Scope ..................................................................................................................... 3 2. Abbreviations ......................................................................................................... 4 3. Solution .................................................................................................................. 5 4. Specification ........................................................................................................... 5 5. Product description ................................................................................................. 9 5.1 Supported operating systems ....................................................................... 9 5.2 Hardware device connections ....................................................................... 9 5.3 Network connection types ............................................................................. 9 5.4 Customizable graphical skin ......................................................................
    [Show full text]