DOCSLIB.ORG

CDG IOTA/HCM Stage-3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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 9 2.1 Operations ........................................................................................................17 10 2.2 Protocol Requirements.......................................................................................18 11 2.3 Architecture ......................................................................................................18 12 2.3.1 Trusted Provisioning Server (TPS) ......................................................................18 13 2.3.2 Communication with the Mobile Station............................................................19 14 2.3.2.1 Provisioning Transaction Agent........................................................................19 15 2.3.2.2 Provisioning Service Agent...............................................................................20 16 2.3.2.3 Bootstrap Service Agent...................................................................................20 17 2.3.3 Security Mechanisms .........................................................................................20 18 2.3.3.1 The Trusted Provisioning Domain (TPD).......................................................20 19 2.3.3.2 Subscriber Parameter Administration Security Mechanism (SPASM)............20 20 2.3.3.3 Service Programming Lock (SPL)..................................................................20 21 2.3.3.4 Bootstrap Security.......................................................................................20 22 2.3.3.5 NAI Authentication for cdma2000 Mobile Stations .......................................21 23 2.3.3.6 Session Security ..........................................................................................21 24 3. Provisioning ......................................................................................................22 25 3.1 The Provisioning Processes................................................................................22 26 3.1.1 Initiation ...........................................................................................................22 27 3.1.2 Mobile Station Rendezvous................................................................................22 28 3.1.3 Provisioning Message Exchanges.......................................................................22 29 3.1.4 Bootstrap Mechanism........................................................................................22 30 3.1.5 Provisioning Activation (PA) Code ......................................................................23 31 3.2 Provisioning Content .........................................................................................23 32 3.2.1 Overall Approach...............................................................................................23 33 3.2.2 Major Elements of MMC ....................................................................................23 34 3.3 XML specifications of MMC................................................................................23 35 3.3.1 MMC DTD .........................................................................................................23 36 3.3.2 MMC DTD Elements..........................................................................................24 37 3.3.2.1 The ‘mmc’ Element ......................................................................................24 38 3.3.2.2 The ‘status’ Element....................................................................................25 39 3.3.2.3 The ‘detail’ Element.....................................................................................25 40 3.3.2.4 The ‘method’ Element...................................................................................26 41 3.4 MIME Types and HTTP Headers ........................................................................28 42 3.4.1 MIME Types ......................................................................................................28 43 3.4.2 Accept Headers for Supported MIME Content Types ..........................................29 44 3.4.3 Including IOTA Version in the HTTP Headers.....................................................29 45 3.5 Example IOTA Commands.................................................................................29 46 3.5.1 Opening a Session.............................................................................................29 47 3.5.1.1 Request (Server to Client) ............................................................................29 48 3.5.1.2 Response (Client to Server) ..........................................................................30 49 3.5.2 OTASP and OTAPA Tunneling............................................................................30 50 3.5.2.1 Request (Server to Client) ............................................................................30 51 3.5.2.2 Response (Client to Server) ..........................................................................31 52 3.5.3 Arbitrary Binary Object Download .....................................................................31 53 3.5.3.1 Request (Server to Client) ............................................................................31 54 3.5.3.2 Response (Client to Server) ..........................................................................32 55 3.5.4 Disconnect ........................................................................................................33 iii 3GPP2 C.S0040 CONTENTS 1 3.5.4.1 Request (Server to Client) ............................................................................33 2 3.5.4.2 Response (Client to Server) ..........................................................................33 3 3.6 Use of HTTP and WSP Methods ........................................................................33 4 3.7 The Provisioning Multipart ................................................................................34 5 3.7.1 Example of Provisioning Multipart.....................................................................34 6 3.7.2 The Provisioning Multipart Response.................................................................35 7 4. Encoding Based on WBXML ..............................................................................37 8 5. IOTA Objects .....................................................................................................40 9 6. OTASP and OTAPA Tunneling............................................................................40 10 7. IOTA Bootstrap Message....................................................................................40 11 8. IOTA Error Codes ..............................................................................................41 12 9. IOTA Trigger Message ........................................................................................42 13 10. Handling User Interrupts during IOTA Sessions ................................................42 14 Appendix A. IOTA-HCM Message Flows..................................................................43 15 A.1 Bootstrapping Message Flow Examples..............................................................43 16 A.1.1 Voice-Call Assisted Bootstrapping of Un-programmed Mobile Station (Default IMSI) – 17 Mobile Station is Pre-loaded into HLR................................................................43 18 A.1.2 Voice-call Assisted Bootstrapping of Un-programmed Mobile Station (Default IMSI) – 19 Mobile Station is Not Pre-loaded into HLR .........................................................46 20 A.1.3 Automated Bootstrapping After Power-up ..........................................................49 21 A.1.4 Mobile Station Initiated Session – No Voice Call.................................................52 22 A.1.5 Network Initiated Session – No Voice Call ..........................................................53 23 A.2 Provisioning Message Flow Examples ................................................................54
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]
  • 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]
  • 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]
  • 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]
  • Syncml Representation Protocol Approved Version 1.2.2 – 24 Jul 2009
    SyncML Representation Protocol Approved Version 1.2.2 – 24 Jul 2009 Open Mobile Alliance OMA-TS-SyncML-RepPro-V1_2_2-20090724-A 2009 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-Spec-20090101I] OMA-TS-SyncML-RepPro-V1_2_2-20090724-A Page 2 (60) 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]
  • WAP Overview Protocol Stack
    Page 1 WAP Overview An overview of the 'Wireless Application Protocol' to the IAB. Copyright IBM 2000 A J Angwin, March 2000 Page 2 WAP Overview Introduction Request for Information WAP enabled Response GSM Phone Application Server WAP enabled PDAs Mobile device with wireless Application server delivering communications, WAP protocol stack appropriate content meeting and Microbrowser environment to render the clients needs information Copyright IBM 2000 A J Angwin, March 2000 Page 3 WAP Overview WAP Forum TM What is the WAP ForumTM ? An Industry Forum established in 1997 whose stated aim is '..to develop the de-facto world standard for wireless information and telephony services on digital mobile phones and other wireless terminals.'. Comprised over 200 members Network Operators, e.g. DeTeMobile, Cellnet, Sonera.. Network Infrastructure suppliers, e.g. Ericsson, Nokia... Mobile Device suppliers, e.g. Ericsson, Nokia, Panasonic.... IT companies, e.g. IBM, HP, Microsoft, Sun... Content developers Copyright IBM 2000 A J Angwin, March 2000 Page 4 WAP Overview WAP Technology What is WAP Technology ? WAP Technology is an architecture and set of specifications that provide : Access to information/services efficiently Wireless Application Environment (WAE) targeted at devices with constrained size, power, MMI etc.. Protocol stack permitting network and bearer agnostic use by the Wireless Application Environment. Transport layer security with authentication and encryption suitable for wireless devices. Additional specifications for Wireless Telephony Applications (WTA), PUSH etc.. Workplan addressing many emerging network, bearer, application and security improvements Copyright IBM 2000 A J Angwin, March 2000 Page 5 WAP Overview The Inspirations What are/were the inspirations for WAP Technology ? The Internet Browser as thin client, IP as transport, Transport security.
    [Show 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.
    [Show full text]
  • Readingsample
    Enabling Technologies for Wireless E-Business Bearbeitet von Weidon Kou, Yelena Yesha 1. Auflage 2006. Buch. x, 387 S. Hardcover ISBN 978 3 540 30449 4 Format (B x L): 15,5 x 23,5 cm Gewicht: 760 g Weitere Fachgebiete > EDV, Informatik > Datenbanken, Informationssicherheit, Geschäftssoftware > SAP Zu Inhaltsverzeichnis schnell und portofrei erhältlich bei Die Online-Fachbuchhandlung beck-shop.de ist spezialisiert auf Fachbücher, insbesondere Recht, Steuern und Wirtschaft. Im Sortiment finden Sie alle Medien (Bücher, Zeitschriften, CDs, eBooks, etc.) aller Verlage. Ergänzt wird das Programm durch Services wie Neuerscheinungsdienst oder Zusammenstellungen von Büchern zu Sonderpreisen. Der Shop führt mehr als 8 Millionen Produkte. 4 Wireless Application Protocol W. Kou ISN National Key Laboratory, Xidian University, P.R. China 4.1 Introduction The wireless application protocol (WAP) is a suite of emerging standards to en- able mobile Internet applications. The WAP standards have been created as a re- sult of the WAP Forum that was formed in June 1997 by Ericsson, Motorola, and Nokia. The WAP Forum is designed to assistt the convergence of two fast-growing network technologies, namely, wireless communications and the Internet. The convergence is based on rapidly increasing numbers of mobile phone users and the dramatic effect of e-business over the Internet. The combination of these two technologies will have a big impact on current e-business practice, and it will create huge market potential. In this chapter, a detailed introduction to WAP is presented, including the appli- cation environment and various protocols. The security aspect in the present Inter- net environment is dealt with in Sect.
    [Show full text]
  • Input Contribution
    Doc# OMA-TP-2005-0050R02-Notification-to-TP-of-changes-in-IPR-rules.doc Input Contribution INPUT CONTRIBUTION Title: Notification to OMA Technical Plenary of changes in IPR Public OMA Confidential rules To: OMA Technical Plenary Submission Date: 28 January 2005 Source: Peter Arnby, Ericsson on behalf of the Release Planning and Management committee Attachments: n/a Replaces: n/a 1 Reason for Contribution This input contribution has been created to ensure that material that falls under the pre-2005 IPR rules of the Open Mobile Alliance can be moved under the new IPR rules that are in place starting January 1st, 2005. 2 Summary of Contribution The Technical Plenary has previously been informed of changes to the IPR policy of the Open Mobile Alliance. In light of these changes and in accordance with the OMA Organization and Process document version 1.2 the TP is notified about which documents that presently fall under old IPR rules so that these can be approved by the Board of Directors to be put under the new 2005 IPR rules. Revision 1 of this contribution contains an update of the list of material based on discussions with the OMA Board of Directors Legal, Trademark and Regulatory Committee. Revision 2 of this contribution reinserts documents WAP-273, WAP conformance process and certification policy and WAP-221, Specification of WAP Conformance Requirements on the list of material to be approved by the BoD, this after receiving further input from BoD LTR 3 Detailed Proposal On Monday December 13, 2004, Jari Alvinen, chair of the Board of Directors of the Open Mobile Alliance sent a notice to all members of OMA that a new IPR policy was being introduced starting January 1, 2005.
    [Show full text]
  • Wireless Application Environment Specification Approved Version 2.3 – 31 Mar 2008
    Wireless Application Environment Specification Approved Version 2.3 – 31 Mar 2008 Open Mobile Alliance OMA-WAP-TS-WAESpec-V2_3-20080331-A Continues the Technical Activities Originated in the WAP Forum 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-Spec-20080101-I] OMA-WAP-TS-WAESpec-V2_3-20080331-A Page 2 (63) 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.
    [Show full text]
  • T610/T612 White Paper T610/T612 Preface
    T610/T612 White Paper T610/T612 Preface Purpose of this document • Software developers • Support engineers • Business decision-makers The Sony Ericsson T610/T612 White Paper is designed to give the reader a deeper technical understanding of More information, useful for product, service and appli- how the T610 and T612 is designed, and of how it inter- cation developers, is published at acts with other media. This document will make it easier http://www.SonyEricsson.com/mobilityworld/, which to integrate the T610 and T612with the IT and communi- contains up-to-date information about technologies, cations solutions of a company or organization. products and tools. People who can benefit from this document include: • Corporate buyers • IT Professionals This White Paper is published by: This document is published by Sony Ericsson Mobile Communications AB, without any warranty. Sony Ericsson Mobile Communications AB, SE-221 88 Lund, Sweden Improvements and changes to this text necessitated by typographical errors, Phone:+46 46 19 40 00 inaccuracies of current information or Fax: +46 46 19 41 00 improvements to programs and/or equipment, may be made by Sony Ericsson Mobile www.SonyEricsson.com/ Communications AB at any time and without notice. Such changes will, however, be incorporated into new editions of this document. Any hard copies of this document Second edition (December 2002) R2A are to be regarded as temporary reference copies only. Publication number: EN/LZT 108 6196 White Paper T610/612 Contents Purpose of this document .....................................................................................................2
    [Show full text]
  • Study of Open Mobile Alliance Device Management Sessions for Most Effective Device Management
    Master’s Thesis Computer Science Thesis no: MCS:2011:22 September 2011 Study of Open Mobile Alliance Device Management sessions for most effective device management. Tomasz Smolarek School of Computing Blekinge Institute of Technology SE – 371 79 Karlskrona Sweden This thesis is submitted to the School of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science in Computer Science. The thesis is equivalent to 20 weeks of full time studies. Contact Information: Author: Tomasz Smolarek 870321-P378 [email protected] University advisor: Dr Andrew Moss School of computing School of Computing Internet : www.bth.se/com Blekinge Institute of Technology Phone : +46 455 38 50 00 SE – 371 79 Karlskrona Fax : +46 455 38 50 57 Sweden ii ABSTRACT Effective device management is not trivial due to a variety of devices and software. To keep costs to minimum companies must effectively utilize a unified solution for device management. This research investigated Funambol’s implementation of Open Mobile Alliance Device Management (OMA DM) which is the most popular device management solution. Interviews were used to set experiments and create realistic test cases. A set of devices and a collection of Funambol software were used to create device management sessions. All of the sessions were recorded, analysed, manipulated and resent to identify efficient ways of device management. Additionally, an influence of compression and buffer-like mechanisms were checked. Methods and guidelines are provided for efficient use of OMA DM as well as a reliable analysis of OMA DM Sessions under various conditions.
    [Show full text]