1 / 16

Evolution of Telecom Management Systems

Evolution of Telecom Management Systems. ACTS. Clusters. NIM. Targets. Facilitation. SIA Targets. SIA Chain. Industry. DIFFERENCE. Fora. Area 1&5. NIM Chain. KEY SIA: Service Integration Architecture NIM: Network Interoperability Management. Society. Telecoms. IT. Market -

toya
Download Presentation

Evolution of Telecom Management Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Evolution of Telecom Management Systems

  2. ACTS Clusters NIM Targets Facilitation SIA Targets SIA Chain Industry DIFFERENCE Fora Area 1&5 NIM Chain KEY SIA: Service Integration Architecture NIM: Network Interoperability Management

  3. Society Telecoms IT Market - Value Chains ITU/ETSI NMF ACTS Eurescom Requirements Construction Rules Architectures FIPA TMN OMG Capabilities WWW Workflow Information & communications technologies OSI JAVA CORBA DCOM Architecture Convergence Note: diagram based on SIA Chain view of archal drivers

  4. Focusing Agent Technology • Relatively new • Issues identified • Agent Technology maturation • ** Mobile Agent Tech & CORBA convergence • Mobile Agent v Intelligent Agent • Application Area issues • Marked with ** above • Analysis • Identify Issues • Work Items Fora ACTS

  5. NEW Evolution of Telecoms Management • Through several events (see later) • Issues suitable for convergence • ** Strengths/Weaknesses TMN • Mgmt Internet technologies with TMN • ** Application of Advanced IT • Conformance • IN/TMN convergence • ** Systems & Enterprise Mgmt for Telecoms Mgmt • ** Neutral Business & Info Modelling • Skills & Tool Support • Marked with ** above • Analysis • IdentifyIssues • Work Items Fora ACTS

  6. Application of Advanced IT Issue

  7. Appl Advanced IT • Milestones DIFFERENCE • Late 1996 - NMF Long Beach meeting • July 1997 - Workshop in Dublin • Aug 1997 and Aug1998 - Review of Fora work • Nov 1997 - DOT Eurescom workshop • Jan 1998 - Deliverable 5 • Sep 1998 - DOT Eurescom workshop • Ongoing - Present to ACTS, NMF,OMG, Eurescom

  8. Interface Type Technology 1 Customer / Operational Web browser / Java Staff access 2 Business Process interaction CORBA / Backbone distribution (+ Workflow?) 3 Business Process control CMIP / GDMO of Network Resources SNMP / MIBs 4 Business Process access SQL, SQL-Net, to Operational Data Data Distribution? NMF Long Beach position

  9. July ‘97 workshop -Some Insights • DOT selection based on non-funcal requirements • Starting Point will drive selection of DOT to use • Telecoms style starting point (IN, ATM, TMN..) • “heritage” important, very important Telecom influences IT! • Coexistence and openness key • Internet style starting point (TCP, SNMP, WWW..) • which DOT will embrace push technologies, Intelligent Agents, Security Frameworks quickest? • DOT Selection will also be driven by • Cost Effectiveness, Openness of Frameworks

  10. Internet Java Web Browsers CORBA Facilities Domain I/Fs Application Objects 1 2 3 4 CORBA Services Object Request Broker GDMO / SMI CMIS / SNMP Manager 5 Manager / Agent Environment Agents Points of Convergence

  11. Strengths/Weaknesses TMN

  12. Ref Model Gradually being accepted in some areas Technology up N/W Info models Support for Sys Architects Support for Sys Designers Support for Sys Implementors The Strengths of TMN • Layering & FCAPS • Command/Control archal support • Comprehensive abstraction Managed resources • Generic Mgmt services • Good link to OSI • Well defined protocol stacks

  13. Business Process support, not top down approach Granularity OSs Neglects General IT support Support for Legacy Heuristics of when to use -LT invest Customer control Support for Sys Architects Support for Sys Designers Support for Sys Implementors The Weaknesses of TMN • Lack Peer to Peer • Not take account of DOT or IT tools • “Neutrality” • FCAPS/Business processes ? • ADEs not good at Trans, persist etc. • Suitability for multiple n/ws or Internet • Lack support for simple coop interactions • Lack conformance stmts • Lack cost effective tools/technologies • Lack confidence longevity products, TMN component market

  14. Going forward... • Process going forward • consensus on issues • select work items that can be progressed together with Fora • application of Advanced IT • Strengths/Weaknesses TMN • System/Enterprise mgmt of Telecoms Mgmt • Neutral Business/Info modelling • Workshops and White papers Fora ACTS

  15. Evolution of Telecom Management • DIFFERENCE plan to progress work items • July 1998 - initial discussion • Sep 1998 - DOT Eurescom workshop • Sep 1998 - OMG Telecoms DTF meeting • Oct 1998 - ACTS ACM • Oct 1998 - NMF meeting • Nov 1998 - DIFFERENCE Workshop

  16. Going forward...together! • Mutual benefit to going forward together • How? • this workshop • consensus building with other fora • November workshop follow on • an open invitation! • Get involved, follow the work.. • Register at …. • We’ll keep you informed

More Related