Service Management And Control


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Service Management And Control

    1. 1. Service Management and Control Presentation to NNEC Workshop NATO HQ 16 December 2005 Mr. Tamas Halmai NC3A CISD Principal Scientist
    2. 2. Agenda <ul><li>Introduction </li></ul><ul><li>Requirement Analysis </li></ul><ul><li>Service Management and Control Architecture </li></ul><ul><li>Domain Specific SMC Aspects </li></ul><ul><li>SMC Roadmap </li></ul><ul><li>Challenges / Open Questions </li></ul><ul><li>Summary </li></ul>
    3. 3. Requirement Analysis <ul><li>Operational and service requirements </li></ul><ul><ul><li>End-to-end service creation, operational control, assurance and termination of services </li></ul></ul><ul><ul><li>Maintain end-to-end visibility of services and create situation awareness </li></ul></ul><ul><ul><li>High diversity of managed systems </li></ul></ul><ul><ul><li>Support of decentralized operations and mobility </li></ul></ul><ul><li>Coalition-specific requirements </li></ul><ul><ul><li>Relationship between CIS operators on the SMC level will be hub-less and will be arranged on a bilateral basis => Federated service management approach required </li></ul></ul><ul><ul><li>Build coalition - wide common operations picture </li></ul></ul>
    4. 4. Coalition-wide SMC Architecture
    5. 5. Key SMC Interfaces <ul><li>External Interfaces </li></ul><ul><ul><li>SMC – SMC: SLA maintenance </li></ul></ul><ul><ul><li>NNI signaling: Dynamic service setup </li></ul></ul><ul><li>National SMC architecture </li></ul><ul><ul><li>National responsibility </li></ul></ul><ul><ul><li>Layered network management approach is recommended </li></ul></ul><ul><ul><li>Managed elements associated with SLAs (one-to-many) </li></ul></ul><ul><li>Central co-ordination function </li></ul><ul><ul><li>Unambiguous SLA semantics </li></ul></ul><ul><ul><li>SLA template development </li></ul></ul><ul><ul><li>SMC interface standardization </li></ul></ul>Service Manager . . . Domain A Manager C2 Element . . . C2 Element Domain B Manager C2 Element . . . C2 Element . . . . . . Nation X Service Manager . . . Domain A Manager C2 Element . . . C2 Element Domain B Manager C2 Element . . . C2 Element . . . . . . Nation Y Central Administrative Management Network Signaling Service Management Control . .
    6. 6. SMC Architecture for Static CIS <ul><li>Design aspects: </li></ul><ul><ul><li>Enabler for other services </li></ul></ul><ul><ul><li>Availability, resiliency </li></ul></ul><ul><ul><li>Redundant network management centres with synchronisation </li></ul></ul><ul><ul><li>Dual-homing </li></ul></ul><ul><ul><li>Object based management approach </li></ul></ul><ul><li>SLA aspects: </li></ul><ul><ul><li>Support of SLAs of multiply SLA instances </li></ul></ul><ul><ul><li>SLA is a formalised contract, will evolve in time </li></ul></ul><ul><ul><li>Performance data collection and correlation </li></ul></ul>
    7. 7. SMC Architec. for Deployed CIS <ul><li>Design aspects: </li></ul><ul><ul><li>Tailored to mission size (small to large) => scalability </li></ul></ul><ul><ul><li>Autonomous operations </li></ul></ul><ul><ul><li>Minimum on-site maintenance requirement </li></ul></ul><ul><ul><li>Shared management responsibilities between Static and Deployed NMSs </li></ul></ul>
    8. 8. SMC Architecture for Static CIS
    9. 9. SMC Roadmap <ul><ul><li>Short term ( - 2008): Reactive Mode of Operation </li></ul></ul><ul><ul><ul><li>Network elements containing only limited network management intelligence, but remotely manageable </li></ul></ul></ul><ul><ul><ul><li>SMC acts upon system events, aiming to service restoration </li></ul></ul></ul><ul><ul><ul><li>Network planning and reconfiguration will be made manually leading to long implementation cycles </li></ul></ul></ul><ul><ul><ul><li>Well developed and documented network management processes, procedures and rules will be required </li></ul></ul></ul><ul><ul><li>Mid term (- 2012/2014): Policy-Based Networking </li></ul></ul><ul><ul><ul><li>Network assets can act automatically upon the environment changes </li></ul></ul></ul><ul><ul><ul><li>Resources will pull new configurations from central databases </li></ul></ul></ul><ul><ul><ul><li>A mediation layer based on vendor-independent interfaces will be required to support multi-layer/vendor/security integration </li></ul></ul></ul>
    10. 10. SMC Roadmap (cont’d) <ul><ul><li>Long term ( - 2020): Self-adaptive SMC approach </li></ul></ul><ul><ul><ul><li>Under the control of the SMC the network can be self-adaptive </li></ul></ul></ul><ul><ul><ul><li>Tight integration between communication and core information system will be possible </li></ul></ul></ul><ul><ul><ul><li>SMC will be part of the complete end-to-end service chain </li></ul></ul></ul><ul><ul><ul><li>Change policies are constrained by a meta-database describing the integration rules </li></ul></ul></ul><ul><ul><ul><li>Standardisation work will be required to achieve coalition-wide interoperability where service description semantics will be defined </li></ul></ul></ul>
    11. 11. Long Term Vision SMC Integration w. coalition-wide SOA
    12. 12. Challenges / Open Questions <ul><li>Technology issues </li></ul><ul><ul><li>Current segmented network architecture and the related security policies are the main limiting factors to achieve: </li></ul></ul><ul><ul><ul><li>End-to-end service provisioning (performance monitoring seams feasible, though) </li></ul></ul></ul><ul><ul><ul><li>Fast and dynamic service creation </li></ul></ul></ul><ul><li>Open questions: </li></ul><ul><ul><li>Input is expected from Nations about under what conditions they are willing to provide services for each other (static or dynamic SLA agreements, seamless roaming of user terminals between home and foreign networks, etc.). </li></ul></ul><ul><ul><li>Are the Nations considering to implement more relaxed security policies to release NMS information cross domain once network management guards become available? </li></ul></ul>
    13. 13. Summary <ul><li>Federated Service Management Control is required </li></ul><ul><ul><li>Different systems with their own autonomous management </li></ul></ul><ul><ul><li>But, enterprise data structures, procedures will be needed </li></ul></ul><ul><li>Bilateral agreements (aka. Service Level Agreements) will determine relationship </li></ul><ul><ul><li>Fast contract negotiation </li></ul></ul><ul><ul><li>Quick and accurate service delivery </li></ul></ul><ul><ul><li>SLAs has to be unambiguous => NATO shall be in a co-ordination role </li></ul></ul><ul><li>Quick wins are possible </li></ul><ul><ul><li>Introduction of strong customer care and helpdesk activity ASAP </li></ul></ul><ul><ul><li>Standardize operational procedures and then automate if required </li></ul></ul>
    14. 14. Questions?