Cs702 Anm A Ds M

436 views
376 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
436
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Good afternoon, Today I will talk about Advanced Device self Management. The proposed idea is enabling to self management of mobile terminals by replacing centralized DM Server Architecture with device centric distributed structure ** Reconfigurability denotes the Reconfigurable Computing capability of a system, so that its behaviour can be changed by reconfiguration
  • Cs702 Anm A Ds M

    1. 1. Advanced Device self Management through Autonomics and Reconfigurability Bernd Steinke, Klaus Strohmenger Nokia Research Center, Germany 16 th IST Mobile and Wireless Communications Summit July 2007 Date : Nov. 21 2007 Chang-Keun Park [email_address] DP&NM Lab., Dept. of CSE, POSTECH
    2. 2. Content <ul><li>E2R II Project </li></ul><ul><li>Introduction </li></ul><ul><li>Problem of existing DM method </li></ul><ul><li>NG-AUTONOMIC MOBILE DEVICES </li></ul><ul><li>The proposed DM method </li></ul><ul><ul><li>smart policy based scheduling </li></ul></ul><ul><li>Configuration Control Framework </li></ul><ul><ul><li>Configuration Management Module (CMM) </li></ul></ul><ul><ul><li>Configuration Control Module (CCM) </li></ul></ul><ul><ul><li>Configurable Execution Module (CEM) </li></ul></ul><ul><li>Conclusion </li></ul>
    3. 3. E2R II Project <ul><li>End-to-End Reconfigurability - Phase 2 </li></ul><ul><li>Funding </li></ul><ul><ul><li>6th Framework Programme of the European Commission </li></ul></ul><ul><li>second phase of the project started on Jan. 01, 2006 </li></ul><ul><li>Objective </li></ul><ul><ul><li>“ Mobile and wireless systems and platforms beyond 3G” </li></ul></ul><ul><ul><li>To devise, develop, trial and showcase architectural design of reconfigurable devices </li></ul></ul><ul><li>Key Challenges of Phase 2 </li></ul><ul><ul><li>Enabling sustainable business development of reconfigurable systems in a multi-access/multi-owner environment </li></ul></ul><ul><ul><li>Enabling end-to-end reconfiguration management and control architecture and devising optimal split of intelligence between network elements and end-user equipment </li></ul></ul><ul><ul><li>Enabling efficiency enhancements for radio resource and spectrum management </li></ul></ul><ul><ul><li>Enabling unified stable, secure and reliable reconfigurable connectivity in a multi-access/multi-owner situation </li></ul></ul><ul><ul><li>Building the European reference prototyping environment for end-to-end reconfigurable systems and solutions </li></ul></ul>
    4. 4. Introduction (1/2) <ul><li>Purpose of OMA-DM </li></ul><ul><ul><li>to allow remote device management </li></ul></ul><ul><ul><li>to define an appropriate structure and protocol to handle a vast range of configuration data </li></ul></ul><ul><li>Device Management (DM) of OMA-DM </li></ul><ul><ul><li>management of the device configuration and other managed objects (MO) from the point of view of the various Management Authorities </li></ul></ul>
    5. 5. Introduction (2/2) <ul><li>The complexity of technical systems, especially embedded systems within mobile communication devices, is constantly increasing </li></ul><ul><li> the parameters, which need to be defined to configure such a device, are tremendously growing </li></ul><ul><li>Today’s approach of DM </li></ul><ul><ul><li>characterized by an off-line approach </li></ul></ul><ul><ul><ul><li>device is configured at short sessions during which it is connected to a DM server </li></ul></ul></ul><ul><ul><ul><li>most of the time the device is disconnected from the server </li></ul></ul></ul><ul><ul><ul><li>mobile device operate with the provided DM Server settings </li></ul></ul></ul><ul><ul><li>Operator and device manufacturer centric </li></ul></ul>
    6. 6. Problem of existing DM method <ul><li>Assumption of today’s approach </li></ul><ul><ul><li>server can predict all possible condition of device’s environment so that provided configuration handles properly devices </li></ul></ul><ul><li>Operator and device manufacturer centric approach is relatively inflexible in unforeseen situation </li></ul><ul><li>unforeseen situations might occur more frequently in heterogeneous environment </li></ul><ul><li>it has to be doubted that the assumption of today’s approach is true and will be true in future </li></ul>
    7. 7. <ul><li>It appears beneficial to create an improvement to the existing server-tied DM by utilizing autonomic behavior in the device </li></ul><ul><li>Key target of autonomic self-optimization approach </li></ul><ul><ul><li>to reach at least a good local optimum or maybe even the actual best possible compromise between contradicting requirements of mobile equipment configuration </li></ul></ul><ul><ul><ul><li>Intuitive presentation of instantaneously available services instead of user guided search </li></ul></ul></ul><ul><ul><ul><li>Cost-optimized network access </li></ul></ul></ul><ul><ul><ul><li>Utilization of the available network bandwidth for fast data communication with low latencies </li></ul></ul></ul><ul><ul><ul><li>Power reduction to gain more active run time and standby time </li></ul></ul></ul>NG-AUTONOMIC MOBILE DEVICES
    8. 8. Proposed DM method <ul><li>smart policy based scheduling to achieve self-management and configuration capabilities </li></ul><ul><ul><li>allows the client to perform sequential management actions requested by a DM server without being in a session with that DM server </li></ul></ul><ul><ul><li>a special terminal resident method for the client to perform management actions requested by the server or user at given times or certain conditions </li></ul></ul><ul><ul><li>the server does not need to monitor the status of the device because smart policies, traps and schedules have the capability to alert the device autonomously about certain conditions </li></ul></ul><ul><ul><li>Under a some given condition, reconfiguration is triggered </li></ul></ul><ul><ul><li>be implemented in a hierarchical way </li></ul></ul><ul><ul><ul><li>the system may take corrective actions if it can solve the issue. If not, it calls for support from the next upper hierarchy layer or finally from the human operators </li></ul></ul></ul>
    9. 9. Configuration Control Framework <ul><li>The definition of a set of collaborating instances or modules that are logically located between the DM server and the device’s functional components is needed to implement autonomous device self-DM inside a mobile device </li></ul><ul><li>These modules need to take over tasks of communication, observation, data logging and decision making </li></ul><ul><li>The configuration control framework for the reconfigurable equipment architecture consists of three types of modules </li></ul><ul><ul><li>Configuration Management Module (CMM) </li></ul></ul><ul><ul><li>Configuration Control Module (CCM) </li></ul></ul><ul><ul><li>Configurable Execution Module (CEM) </li></ul></ul>
    10. 10. CMM reconfiguration related communication between services and CMM Configuration Profile Repository discovering available network & monitoring context information downloads device management components security functions required during the reconfiguration support context and policy management procedures provide the means for configuration representation and configuration deployment provides a reporting interface to the CCM Negotiate and Select network offers among available networks
    11. 11. CCM primary interface between the CMM and the CCM which sets up a new configuration in terms of overall RATs interface between the CMM and the CCM to supply a set of functions unique to the selected RAT provide information, which configuration the underlying layer is able to surpport provides access to databases
    12. 12. Conclusion <ul><li>Contribution </li></ul><ul><ul><li>outlined the key-functionality of the Advanced Device self Managing framework </li></ul></ul><ul><li>By using the self configuration and management capabilities in addition to OMA DM, proposed reconfiguration architecture may either send to the reconfigurable terminal &quot;Knowledge&quot; on how to behave in certain conditions, or analyze some conditions </li></ul><ul><li>Future work </li></ul><ul><ul><li>The policy driven autonomic self-configuration extends the DM server based approach </li></ul></ul>

    ×