1 / 65

Telecommunications Management Architecture and Technologies for New Generation

Telecommunications Management Architecture and Technologies for New Generation. 2000.12.12 Seong-Beom Kim Korea Telecom sbkimm@kt.co.kr. Content. Environmrntal Challenges Definition and Scope Activities New Generation Operation Support System and Software(NGOSS) Summary.

chess
Download Presentation

Telecommunications Management Architecture and Technologies for New Generation

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. Telecommunications Management Architecture and Technologies for New Generation 2000.12.12 Seong-Beom Kim Korea Telecom sbkimm@kt.co.kr

  2. Content • Environmrntal Challenges • Definition and Scope • Activities • New Generation Operation Support System and Software(NGOSS) • Summary

  3. Environmrntal Challenges

  4. competition QoS configurability & verification Service level Guarantee Operation cost Meet capacity On-demand request Business Challanges Telecommunication Business • Voice/Data integrated operation • Interoperability: Multivendor equipment • Rapid introduction of new technology

  5. Broader Spectrum of Services • Spectrum of services • – From voice services to data services • – Mobile data services • – Data voice services • – Unified services • Modality of services • – From fixed line to wireless • – From pull when needed to always on • The target of services • – From individual to groups and to communities • – From mess market to individuals

  6. Service & network Provider (S&NP) Service Provider Software Vendor (SV) System Integrator (SI) Equipment Vendor (EV) Business-focused requirements • faster TTM service • cost effective & more choices • flexibility & adaptability  process re-engineering • higher demand for new products • more potential & less efforts • systematic & predictable approach • interoperability • more partnership • rapid introduction of new service • support for SP’s requirement

  7. Network Management - Definition and Scope

  8. Network Management Trafic management Traffic Control Traffic Measurement Performance Analysis Network Surveillance real-time Traffic Analysis Telecommunications Network Network Planning non-realtime Planning Scope of Management Business management Customer service management Security Management Account Management Operation & Maintenance Fault Analysis Operation & Control Service Order Handling

  9. Fundamental specification for NMA and functions Layered architecture Functional specification Customer Service Management Business Management Customer Relationship Management FCAPS Service Management Fault Management Configuration Management Network Management Account Management Performance Management Network Elemenet Management Security Management

  10. Organization & staffs Process re-engineering components • set of mgnt. appl. • protocol & technology neutral • plug & play (P&P) =>re-usable component • flow-through & one-stop mgmt. => work force mgmt. => Org. re-structuring Process Data (Info.) • subs./network/billing info. -> integrity & duplication • dataware housing & mining • analysis & decision support => provide interworking/sharing func. How can they be merged and integrated together ?

  11. DSS Customer Info. Accounting Info. Network D/W order Customer Service order billing traffic fault Billing & Traffic Info. Fault Info. Facility Info. Config. Info. Work Order Maintenance staff Fault Management Help Desk (Test) Configuration Management Facility Deployment Performance Management Account Management InformationFlow “ Flow-through information flow and relationships between customers and service providers “

  12. customer fault order Fault info. Config. Info. Service Provisioning Help Desk Network Management fix Reallocate resources Config. work order maintenance Test Facility Management Fault Management Performance Management Service Activation Configuration Management Account Management • Traffic • Performance • Tariff • Circuit Test • Alarm • Fault • Status • Capacity • Reconfiguration Maintenance staff Work Flow “Procedure & message flow between users of OSSs in service provider organization”

  13. Network operation center Data Communication Network Surveillance System With Event correlation process Few Trouble Tickets Needed technologies Network Elements from multi-vendor • Rule-based • fuzzy logic • model-based reasoning • filtering • event forwarded discriminator • case based reasoning • corelation by voting • data mining • knowledge discovery • distributed corelation • artificial neural networks • divide & conquer Network Surveillance & Event correlation Many Alarms !!

  14. Activities

  15. TM Forum ITU-T TOM/TIM/SIM NGOSS (Next Gen. OSS) OTMA (TMN2000) Activities & forward …. IETF,ATMF… IETF,ATMF… IETF,ATMF… More evolutionary and practical OSS Architecture design for NGN Including IP, mobile Integrated Mgmt. For Circuit & Packet/IP network based on multi-protocol • Distributed computing environment • Heterogeneous networking environment • Commercial Off The Shelf(COTS) • Technology Neutral components • Emerging new services : IP, Mobile,… • Agreed framework for management

  16. TMN-2000(ITU-T)

  17. TMN Activities ….(ITU-T) • Principles and Architectures - Reviced principles and architectures to support the multiple management technology paradigm environment (M.3010) - TMN considerations, including focus on existing and emerging paradigms (M.3013) • Methodology using UML to support a multi-paradigm environment(M.3020) • Protocols : CORBA and EDI for Inter-TMNinterface (Q.812, Q.814) • Enhance Functional requirements and Information modelling ( M.3400, Q.82x, Q.83x )

  18. TMN dead or alive ? • Words, words…. - ”The telecom industry has long held up the Telecommunications Management Network (TMN) as the ideal blueprint for operations management…. The question on everybody’s mind seems to be whether TMN works as well in practice as it does in theory.‘ - “Last month’s Global TMN and OSS summit focused on issues and innovations shaping the future of next -generation networks…But things got ugly when various speakers and attendees at the conference were seen mouthing the words ”TMN is dead.‘ • But, TMN really provides: — Logical Layered Architecture : ”TMN products should clearly identify the functionality they provide in terms of the five logical layers.‘ — Management Functional Areas (”FCAPS‘) : ”TMN products should clearly identify the functionality they provide in terms of the five Management Functional Areas...[and] also provide common operations functions...‘ — Information Models: ”TMN... describes an object- oriented approach for in formation exchanges in interactive management transactions…‘ — Open Standard Interfaces :”Open standard interfaces should be used whenever possible... ” • TMN is still alive and ….. - Most aspects of TMN have been very widely accepted and have been extremely influential in the OSS marketpla ce - Major exception TMN has been traditionally associated with the CMIP protocol, which has not been widely accepted

  19. TMN for Next Generation(TMN 2000) • Current generation of TMN infrastrucure • => single manager and agent system • => single communication protocol • => static domain • Next generation of TMN infrastructure • => distributed management: diffused functionality • => inter-domain management : OSI,DPE,Internet • => interoperability and portability evolution

  20. TMN2000 for Next Generation • Two track approach including existing and new emerging paradigm environment • Management paradigm: CORBA for intra-TMN use and other emerging paradigm(eg. XML) • Integrated management of mixed circuit and packet/IP networks: support of SNMP • TMN management support for IMT2000

  21. Management Application Solution Set Managementt Platform Component Set Communication Component Set TMN 2000 - OTMA Open Telecommunication Management Architecture (OTMA) Teleoperator Requirements Future Requirements Future Compliance TMN Compliance solution sets leased line Alarm reporting solution sets component sets General Mgmt. Capabilities component sets Legacy TL1.. X.500 Future solution? CMIP CORBA IDL X.400 TINA ODL FTAM Mobile ? SNMP Evolution Path

  22. New Generation Operation Support System and Software (NGOSS)

  23. Product Marketing Program Technical Program Market Collaboration NGOSS Knowledge Services • TMW • Conference • Expo • Showcase* • TMF Univ** Business Case Market Outreach Member Collaboration Business Framework Systems Framework Arch Board • WWW Portal • Member Educ • TMF Univ** • Strategy • Mkt. Research • Focus Groups • Instigate Work • Mkt. ‘Magnetism’ • Catalysts* • TOM • Processes • Models • BA Comps • Shared Data Model • Requirements • Neutral • Architecture • Tech Specific • Architectures DA/Repository Marketing Communications Promotion, PR, Web, TM Times, Member Communications, Shows & Conferences Operations Meeting Management, Team Support, Member Services, Adminisration, Legal Finance TeleManagement Forum

  24. TMF Market Centre and Technical Program Structure Project n Project C Program Board Steering Team Project B Project A Systems Requirements Project n Architecture Project C Market Centre Steering Team Steering Team Program Board Operations Neutral Project B Finance Shared Data Model Project A Architecture Specific1 Business Aware Component I/fs Architecture Project n Specific n Project C Steering Team Program Board Project B Project A MCF - Project Mgmt & Support Market Centres NGOSS Strategy Management Team NGOSS Steering Group NGOSS Business Case TOM Sector - Neutral Program Board Architecture Board modelling teams Marketing Web based Repository Business Framework & Services Systems Framework & Services Marketing Mgmt & Support

  25. Business Context Off the Shelf Integration SMART TMN & NGOSS Smooth Operation NGOSSTM System Context Advanced Operation

  26. Fulfillment(F) Assurance(A) Billing(B) Customer Order Invoicing/ Problem Sales QoS Handling Collection Handling Management Customer Care Processes Service Service Service Service Rating and Planning/ Problem Quality Configuration Discounting Development Resolution Management Service/Product Development and Maintenance Processes Network Network Network Network Network Data Planning/ Maintenance Inventory Provisioning Management Development & Restoration Management Network and Systems Management Processes Telecom Operation Map(TOM)- TeleManagement Forum(TMF) -

  27. Service Fulfillment Process Flow

  28. Service Assurance Process Flow

  29. Billing Process Flow

  30. Example of Detail Process [ Network Provisioning Process ]

  31. e-TOM • Characterize the e-business environment • Enhance the Business Relationship Model to reflect the increased complexity of an e-business environment • Evolve the TOM to support an e-business oriented enterprise—create an e-business Business Framework Map • Introduces formal process modeling to TM Forum • Provide process flows and more detail for linkage to NGOSS

  32. Business Relationship Reference Model for the eTOM Complementary Provider

  33. e-TOM Business Process Framework

  34. Process - Level 1 [ The Enterprise Support process – Level 1 ] [ The Marketing and Sales Management process – Level 1 ]

  35. Process - Level 1 (con’t) [ The Supplier / Partner Relationship Management process – Level 1 ] [ The Customer Relationship Management process – Level 1 ]

  36. Process - Level 1 (con’t) [ Service Development and Operation process – Level 1 ] [ The Resource and System Management process – Level 1 ]

  37. The e-TOM Business Process Framework – General View

  38. Technology Integration Map (TIM) • 필요성 : • 시스템 개발에 필요한 막대한 예산의 절감을 위하여 장래 업계에서 필요하지 않을 기능과 업무에 부적절한 기능을 축소 또는 삭제가 필요 • 빠르게 발전하는 개발기술의 안전한 도입을 위해 장래성이 있을 기술 선별이 필요 • 각 사업자의 역할이 점차 통신 서비스 제공을 위한 사슬의 한 부분으로 축소되고 있어 이에따른 시스템간의 역할 조정이 필요 • TIM의 구성 • Part I: An Application Components Direction Statement • Part II: A Technology Direction Statement • Part III: A Procurement Guide

  39. TIM Framework Analyze Business Process Business Element Service Network Analyze Requirement Telecom Operations Map Defining Bldng Blk Bound (supplying Management services) Applications Direction Define Contracts (how system solutions are formed ) (re-usable application components) Security Systems Management Specify Technology Specific Business Scenario Business Drivers Technology Direction (technology selections) Build vs Buy Decision (systems infrastructure services) Buy BB Buy Tools Procurement Guide (SPIRIT - extended) OOAD (Standards selections) Other Industry Organizations relationships gap analysis (e.g OMG, ITU, TOG, etc.)

  40. Interface Type Technology Customer/Operational Staff access Web/Browser/ Java 1 Business process interaction /Backbone distribution CORBA (+Workflow?) 2 Business process control of network resources CMIP/GDMO SNMP/MIBs 3 Business process access to operational data (not discussed) SQL, SQL-Net, ODBC, Data Distribution? 4 Technology Selections (TD) Technology Selections SP integrated needs Technology Alternatives (TD) • Distributed Systems • CORBA, propritary ORBs • DCE • DCOM • DTP • General Purpose Access • intranets • web browsers • Mobile Code/Java • CMIS/CMIP, SNMP, etc.

  41. Technology Integration Points (TD) • IP1: CORBA  CMIP/GDMO • IP2: CORBA Services  CMIP Services • IP3: CORBA Objects  HTTP/HTML based Browser Services • IP4: Java Objects  CORBA Objects • TMN Manager/Agent Programming Interface

  42. The Dilemma Business Opportunities • Introduction of 3G mobile in 2002 • Explosive growth of new IP based services • e-Commerce self care • Business Constraints OSS inflexibility reduces • roll out of new services • procurement of equipment and software

  43. Hurdles to Overcome • No “generally accepted” architecture that we can all base our systems on. • We spend too much time “getting systems to connect” and not enough time on “getting the functionality we need”! • We cannot change the systems as fast as the business is changing. … 50% of the work of integrating two systems in in the “plumbing” and “adapters”. This wasted work that takes away from creating actual usable functionality. • We cannot buy/ build/ lease new systems functionality without affecting everything currently installed.

  44. NGOSS (New Generation Operation System and Software) Goal • Secure a leadership position by successfully delivering NGOSS with significant industry support. Program Objectives • Establish the NGOSS reference architecture as the industry’s umbrella architecture for all OSS solutions (Q1 2001) • Deliver NGOSS reference implementation (Q2 2001) • Gain involvement from key groups by launching collaborative work on key elements • Create market momentum by attracting support of pacesetter companies • Extend acceptance into other key sectors (ASPs, ISPs, etc.)

  45. NGOSS™ Project Organization Business Case Requirements NGOSS Architecture Technology-Neutral Projection Technology-Specific Projections Implementation-Specific Projections

  46. NGOSS Architecture • System Definitions and Mappings • System equivalent view of TOM • Enterprise Solution • System Components • Component Interactions • Component Interfaces • 3 types of system components • Business deployable components • Mapping BP to Function interactions • Applying Technology to Concept • Technology neutral system architecture • Technology specific system architecture

  47. Functions and Domain • System관점 : function과 그 function이 미치는 impact 상관관계 정의 • Domain : 복수의 function과 information의 묶음(cluster)

  48. System Equivalent Viewpoint [ Systems Equivalent View of TOM ] [Relationships between Multiple Domains with a System

  49. Application Component One Application Component Two Contract Interface Communications Infrastructure Infrastructure Service NGOSSTM Major Concepts • Application/Business Services Provided by cooperating Application Components • Infrastructure Services to facilitate communication and enable Application Components to work together • Communications Infrastructure is the mechanism by which all communicate

  50. Application Service Contract Interfaces System Management Application Component • Instrumentation • Configuration • Faults • Etc. Framework Service support Component Interface and Types of Component

More Related