Facing Future Internet service and network management complexity

Transcription

1 Facing Future Internet service and network management complexity Christian Destré, Orange Labs Technical Manager of the FP7 UNIVERSELF project

2 Telcos' management operations Operations in etom (TMF) Processes are instantiated for the CRM network segments (Access, Backhaul, CORE networks) and services With several organizational entities OAM / OSS / BSS NE/EMS/NMS provided by vendors OSS/BSS, part of telco IS Multiple Interfaces and data models issue Too many tools depending on the management entities and network segments

3 Legacy services and network resources (~40 years of R&D) Network resources Mobile & fixed convergence Separated management IP QoS management complexity Several mechanisms to configure Increasing number of devices Mobile devices, Customer Premise Equipments, Services Facing IP mobile & fixed convergent service management complexity End to end management issue (QoS, QoE) IMS Increasing number of services Management issues: silo and ossification From service requirement to network configuration = dedicated (not reused) processes = manual operations and IS static operation made = effort, delay and consistency issue Change/update of management functions Extremely costly and time consuming (adding significant costs to OPEX) No deployment tools for new management functions Separate Management for Networks & Services Placement of Management functionality External management to managed systems

4 Towards Future Internet Management is the primary enabler Increasing managed entities : services and devices M2M, Internet of things Increasing management tasks Green Networking and Energy Efficiency Dynamic / on demand management Dynamic processes management On demand service and resource configuration/provisioning related to on demand subscribing or situation evolution Managing new types of resources and services Virtual resources (e.g. Cloud Computing, Virtual Networks, Virtual Storage) Dynamically provisioned and shared Virtual Infrastructure based on different types of Virtual Machines ( e.g. virtual rooters, virtual service components,..) Customized services based on customer profile/situation Interconnection/interoperability & Extensibility Between network operators, service providers, third parties (e.g. different chains of players) Higher level of integration Orchestration of the closed management loops across federated domains or in a single domain Context and Knowledge plane focus

5 Autonomic Networking/communication, autonomic as enabler Simplify management at all levels (access networks, core networks, services, fulfillment & assurance) Potential to reduce OpEx Various aspects of Self-Chop: Configuration, Healing, Optimization Performance Cross-technologies Relies on Standards Lot of works concerning Autonomic Networking architectures Need of Unification Need of being operational and impactful Related to Telco's processes and governance & trust constraints Integration of management for Services/Applications with network Large scale deployability of management functions

6 UNIVERSELF Consortium (FP )

7 Federating UNIVERSELF Objectives: Realizing Autonomics for Future Networks Unification of existing architectures and convergence of network management principles across multiple technological contents Empowering Embed intelligence inside network equipments Impactful Impact the telecommunication industry and push towards exploitation of its results Trustworthy Foster adoption by means of trust and confidence Orange Labs - Research & Development UniverSelf 02/12/2010

8 "Cleaned state", "not clean slate"

9 Unified Management Framework

10 UNIVERSELF: Use case oriented Perimeter: mono-operator, multi-vendor Scenario 1: Operators' Service and data management Lack of a global end to end view of all data (both Users and net data), especially in NGN Lack of mappings/views correlating these data to services at different levels Cross-layer network data are not used for optimizing use of network resources & the management No means of using data flows for enabling new business opportunities (e.g. brokering specific data to third parties) Scenario 2: SON for Radio Access and Core Networks Evolving the management plane to allow the introduction of high level policies Enhancing cognitive capabilities in SON enabled network elements, including learning, decision making and knowledge sharing geared towards enforcing policies Framework for coordinated SON mechanisms and entities to enforce policies Scenario 3: Future Internet Services Management and Network Resource Optimization Configure and manage the necessary number of network components for Future Internet services: Real-time experience social networking, global inter-connectivity, cooperation services Easing configuration / deployment

11 UNIVERSELF: Use case life-cycle and experimentation strategy

12 Conclusion More and more complexity to manage Management and managebility are the key enablers for realizing Future Internet Unified management Embedding Autonomicity in shared Infrastructure With trust Operational impact and related standards

13 Thanks Acknowledgement to Alex Galis for his useful remarks

14 About UniverSelf FP7 Call 5 Integrating Project Total Cost: ~16M ; EC Contribution: ~10M ; 17 Partners Duration: 36 months Start date: 01/09/2010 Project Coordinator: Alcatel Lucent Bell Labs France Technical Manager: Orange/France Telecom

15 Project structure WP1 Project Management WP2 WP3 WP4 WP5 Unified Management Framework Specification and design of a service oriented and network agnostic Unified Management Framework Network governance Information and knowledge management Embodiment mechanisms Network Empowerment Develop algorithms with self-x and cognitive capabilities together with their requirements for their embodiment into network functions Parameter optimization Observation and actions (learning & control) Cooperation strategies and incentives (orchestrating control loops) Deployment and Impacts Use case definition, integration and solution deployment (validation via simulation prototyping, and experimentations), certification, trust building Trend setting

16 Conclusion Substitute KISS principle with KII principle KISS principle Keep it Simple, Stupid - today optimisation is tomorrow s bottleneck (Source: D. Isenberg) KII principle Keep it Intelligent today fundamental is tomorrow s secondary (Source: A. Galis)