Telecom Networks Management-電信網(wǎng)絡(luò)管理

1、Telecom Networks & Operations Management OverviewPresented by ex-Nortel-Employee2008.9.24ContentsOSS introductionTMN model and its framework and FCAPS functional areasInfrastructure technologies required in TMNOSS IntroductionWhat is OSS?The term Operations Support System (OSS) generally refers to t

2、he systems that perform service management, inventory, engineering, planning, repair functions for the delivery network of telecommunications providers.Past focus has been on diagnostic, maintenance and network management capabilities used by service providers in controlling their telecommunication

3、services efficiently.OSS infrastructure has significant impact on a service providers overall operational efficiency and cost structure.Other TermsBSS - Business Support Systems, are the systems that support customer-oriented operations e.g. Customer Trouble Report, Customer Account informationOSSs

4、are sometimes referred to as systems that support network oriented operations e.g Alarms, Traffic Analysis.No strict conventions, and the above distinction is becoming increasingly blurred.Front Office - Customer facing functionsBack Office - Internal functions required for service deliveryOAM&POper

5、ations, Administration Maintenance & Planning: nine main areas of telecommunications management:DesignPlanningInstallationProvisioningMaintenancePerformanceSecurityCustomer - query, and control/managementCorporate administration functions like HR, Finance are also integral to operations but are gene

6、rally outside of OAM&POSS EvolutionEarly stage: The old Bell System, in the US, was a leader in the development, delivery and maintenance of the OSSs. Other carriers had essentially similar systems, generally developed in-house.Examples of Telcordia OSSs: LFACS (Loop Facility Assignment), NPS (Netwo

7、rk Planning System)Development stage:TMN standards introduction, for adapting to multi-vendor, mutli-devices environmentSNMP also introduced in this stage.Still focus on the NE managementNGOSSTom and eTom, based on the TMN, the full scope of business processes required by a service provider and defi

8、nes key elements and how they interact. OSS Technology EvolutionTMN and StandardsMain TopicsTMN and Standards:FrameworkFunctional ModelStandard InterfacesLogical ModelTMN SolutionWhat is TMN?TMN - Telecommunications Management Network provides a framework for achieving interconnectivity and communic

9、ations across heterogeneous operating systems and telecommunication networks.Sponsoring organization:ITU-TComplementing organization:ISOStandards: ITU-T M.3000 Recommendation series ISO Systems Management standardsTMN Standard - key featuresObject orientedStandard interfaces for communicationsStanda

10、rd management interfaces built on OSI Systems Management Functional Areas (Fault, Configuration, Accounting, Performance, Security)Standards includeCMIP: defines management services exchanged between entitiesGDMO: provides templates for classifying and describing managed objectsASN.1: provides synta

11、x rules and data typesWhat were the motivating factors?IntegrationInteroperabilitySpeed to marketReduce costMulti-vendor and multi-platformScalable and extensibleProtection of legacy investment Several viewsLogicalorBusinessStandardInterfacesFunctional ModelInterconnectivity and communications achie

12、vedvia standard interfaces that view all managedresources as objects to solve specific business problemTMN Functional Model - Building BlocksTMNWSNEQAMDOSDCNManager/Agent RolesTMN function blocks can act in the manager and/or the agent role. The manager/agent concept are the same as those used by OS

13、I management.A manager process issues directives and receives notifications.An agent process carries out directives, sends responses, and emits events and alarms.TMN Functional ComponentsOSOperations System or Support System, performs operations system functions including monitoring, controlling, an

14、d management. The OS can also provide some of the mediation, q-adaptation, and workstation functions.MDMediation device, performs mediation between local TMN interfaces and the OS information model. Mediation function may be needed to ensure that the information, scope and functionality are presente

15、d in the exact way that the OS expects.QAQ Adapter, enables the TMN to manage network elements that have non-TMN interfaces. The QA translates between TMN and non-TMN interfaces e.g. TL1 Q-Adapter, SNMP Q-Adapter.NE Network Element, contains manageable information that is managed and controlled by a

16、n OS via a standard TMN interface. The NE provides the OS with a representation of its manageable information and functionality i.e. the MIB (Management Information Base)WS Workstation translates information between TMN format and a displayable format for the user.DCN Data Communication Network is t

17、he communication network within a TMN. The DCN represents OSI layers 1 to 3.TMN Functional Components (contd)TMN InterfacesQThe Q interface exists between two TMN-conformant functional blocks that are within the same TMN domain. Q3 is the standard OS interface. Any functional component that interfac

18、es directly to the OS is Q3 interface. The Qx interface exists between the NE and MD, QA and MD, and MD and MD.FThe F interface exists between WS and OS and between WS and MD.XThe X interface exists between two TMN OSSs in two separate domains.Q3TMN Standard InterfacesWSMDOSQAQANENEFQ3QxQxQ3TMNOSTMN

19、OSXTMN Logical ModelNELEMLNMLSMLBMLBML Business Management LayerSML Service Management LayerNML Network Management LayerEML Element Management LayerNEL Network Element LayerTechnicalCapabilityBusinessDriversTMN Logical LayersBMLHigh level business functions e.g. HR, budgeting, goal setting, etc.SMLM

20、anage contracted service to existing and potential customers, point of contact with customers for provisioning, accounts, QoS, fault management. It is also the key point of interaction with other service providers and other administrative domains.NMLIt has the view of the entire network. It co-ordin

21、ates all network activities and supports the demands of the SML.TMN Logical Layers (contd)EMLIt is responsible for the management of network elements within its domain, generally a subset of the network. It has element managers or OSSs each of which are responsible for the information of the network

22、 elements. It is one of the most significant layers in the network management process as it provides the first view of manageable information and data. Vendor supplied.NELIt represents the manageable information in an individual NE, and includes Q adapters.Management Functional Areas - FCAPSFault Ma

23、nagement Deals with the activities of detection, isolation and correction of abnormal network operation.Configuration Management activities include the configuration, maintenance, and updating of network components (objects). It also includes notification to network users of pending and performed co

24、nfiguration changes.Accounting Management tracks network usage for purposes of billing, abuse of network privileges or usage patterns.Management Functional Areas - FCAPSPerformance Management covers the monitoring and maintenance of acceptable network performance, and collection and analysis of stat

25、istics critical to network performance.Security Management encompasses the activities of controlling access to the network and associated network management information. It includes controlling of passwords and user authorization, and collecting and analyzing security or access logs.TMN SummaryA set

26、 of standardsHolistic view of everything telecom service provider has to do to provide telecom servicesDefined interfaces and protocols for communication and information sharing among collection of systemsPresently, customer care a higher priority with service providers while EM systems are a low pr

27、iorityOperations Infrastructure TechnologiesEvolution of Network ManagementUntil Late 80sLate 80s to Late 90sProprietaryTL1 (1984)NetviewDevice ManagementOpenSNMPCMIPTL1 as Command Line I/FLimited InteroperabilityNetwork ManagementOpen and DistributedDirectories End-to-End: Network ManagementService

28、 Management Significant Contribution:HP OpenViewUNIXMain TopicsManagement Protocols and Information ModelingTL1SNMPCMIPGDMOCORBADistributed vs. Centralized MiddlewareImplementationTransaction Language 1Telcordia proprietary ?Interactive communications between network Operations people and network de

29、vices and supporting databases Unique message for each command Functionality:Alarm SurveillancePerformance MonitoringProtection SwitchingControl (State of device e.g. out of service)ProvisioningSecurityTL1Primarily used by Telcordias clients, and by vendors as Command Line InterfaceHuman-Machine Lan

30、guage. Plain TextAcronyms and shorthand used to convey informationExample:NE-NAME-ID 97-03-01 12:04:34 *C 8874 REPT ALM OC3 “main-2:MN, LOS, NSA, 03-01, 12-04-34:”inc. OC3 LOS” Device NameDate & TimeAlarm SeverityEquipment Affected by ConditionPriority ofActionConditionType Affect on ServiceCommentU

31、nique IDSome General ConceptsMIB: A conceptual repository for management informationMIT: Managed Objects are organized in a tree structureSNMPSNMP - Simple Network Management Protocol (UDP based)A set of protocols for managing TCP/IP networks. Lightweight & relatively simple.SNMP-compliant devices,

32、called agents, store data about themselves in Management Information Bases (MIBs) and return this data to the SNMP requesters. Managed devices house SNMP agent softwareA management information exchange can be initiated by the manager (get or set information) or by the agent (via a trap).SNMP Standar

33、dsThree Standards:A Standard Message FormatStandard protocol with defined UDP messagesA Standard Set of (Managed) ObjectsStandard set of values (IETF Standard RFC-1213) that can be queried for a device. Each SNMP object has a name and numeric identifiersA Standard way of adding ObjectsThe standard s

34、et of SNMP Objects can be augmented by device vendors with new objectsEvolution:SNMP has evolved over time from SNMPv1 to SNMPv2 and now SNMPv3SNMP Message SetGet RequestTo fetch a specific value (object) for a deviceGet Next RequestTo step through all SNMP values for a device, until an error messag

35、e is receivedSet RequestTo set a value for a device (e.g. disable). Provides a mechanism for configuring and controlling network devicesTrap MessageSent by an SNMP agent to notify the manager of change in value SNMP Managed ObjectsThe various SNMP values in the Standard MIB are defined in RFC-1213 (

36、Internet Engineering Task Force (IETF) standard). These values have a name and a numeric identifier e.g.:Name: sysUpTime “Elapsed Time since device booted”Identifier: .0 Managed objects can be of two types:Discrete MIB Object: contains one precise piece of management data and ends with a “.0” extens

37、ion in the identifierTable MIB Object:contains multiple pieces of management data and have a “.n” extension to their names which provides the index into the SNMP table.SNMP objects are documented in ASN.1 SyntaxSNMP ObjectSyntax for declaring SNMP object:(objectname) OBJECT-TYPESYNTAX (syntax)ACCESS

38、 (access)DESCRIPTION (description):= (parent) (number) Words in Bold are required keywordsobjectname - official name of the SNMP object and begins with a lower case and must be uniquesyntax - the type of object e.g. Counteraccess - defines the type of access e.g. read-onlydescription - text descript

39、ion usually delimited with “ ”parent - parent name identifies the MIT branch to which this leaf is attachednumber - indicated the unique numerical value of the object. The (parent)(number) combination must be unique.SNMP ExtensibilityA key feature for its popularity, especially with vendors, is its

40、ability to augment standard set of MIB objects with new values specific to the application and device.MIB for an SNMP device is constructed by the equipment vendor and cannot be modified. The MIB definitions are supplied by the vendor in a specially formatted file using ASN.1 syntax.The extensibilit

41、y is accomplished by SNMP management software by compiling the MIB definitions supplied by the device vendor.Most SNMP Managers provide MIB Compiler and Management Tool Set” as standard functionality. The Management Tool Set includes MIB Browser.SNMP - Positives/NegativesPositives:Widespread popular

42、ity (especially in Data world)Flexible and Extensible (can be extended to cover device specific data)Low overhead, and hence can be deployed in simple network devices e.g. printers, bridgesNo log-in for remote operations (UDP) hence lower overheadNegatives:Complex encoding rules hence implementation

43、s can tend to be complexProtocol Data Units (PDUs) can become large hence concerns about overhead and network efficiencyLatency - due to pollingUnconfirmed communications (UDP) only, best effortScalabilitySNMP EvolutionOver the years SNMP has progressed from SNMPv1 to SNMPv2 to SNMPv3, incorporating

44、 several enhancements.Key SNMPv3 Features:User Based Security ModelGetBulkMIB ImprovementsViews-Based Access ControlAdministrative FramreworkOSI Management ProtocolsCommon Information Management Services (CMIS) - IS 9595 - defines Services/Primitives or command types to accomplish network management

45、 functions.Notification Service: EVENT-REPORTOperation Services: GET, SET, CREATE, ACTION, DELETE and CANCEL-GETCommon Management Information Protocol (CMIP) - IS 9596 - describes exchange of basic management information between open systems.OSI Management uses Object Orientation ISO Management Fram

46、eworkISO/ITU-T Information StandardsStructure of Management Information (SMI) Parts 1- 7Management Information Model - Part 1: defines how the management data must be structured, including what manage objects and attributes are, what operations can be performed on them, and what managed objects are

47、allowed to say to a management system via notifications.Guidelines for Definition of Managed Objects (GDMO) - Part 4: specifies what managed definition should look like. Goal being to ensure consistency among various vendor implementations thereby enhancing interoperability.Generic Relationship Mode

48、l - Part 7: extends information architecture to relationships and specifies the syntax of their templates.GDMOGDMO is a structured description language that provides a way of specifying the class of objects, the object behavior, attributes and class ancestry.Makes use of ASN.1 for definition of synt

49、ax - data typesObject Class: MANAGED OBJECT CLASS DERIVED FROM *; CHARACTERIZED BY ,*; CONDITIONAL PACKAGES PRESENT IF condition-definition , PRESENT IF condition-definition*; REGISTERED AS object-identifier; GDMO (Contd)DERIVED FROM specifies the superclass or superclasses for the objectCHARACTERIZ

50、ED BY identifies the packages included in the object class definitionREGISTERED AS clause identifies the location of the managed object class on the ISO Registration TreeManaged Object class contain packages which are a collection of:Attributes: that contain values describing object conditionAttribu

51、te GroupsActions: services provided by the MO that can be acted uponNotifications: messages that can be emitted by the objectBehavior: readable text to document the nature of the object being representedCMIS/CMIP - PositivesScoping and filtering - applying a single command to a large number of objec

52、tsEvent driven notification - allowing objects to notify the management system of changesWider range of attribute data typesSupports confirmed and unconfirmed operationsSupports independent naming and registrationMore operations in fewer commandsInternationally accepted and emphasis on open interope

53、rable standardsCMIS/CMIP - NegativesLarger processing burden on network devicesMore complex and hence expensiveLonger standardization processBudget constraints forces a short term make-do-with-what weve-got-approachConservative technology investment strategy settles for limited functionality if it r

54、educes technology exposureCo-Existence ? SNMP is widely accepted and deployed despite its limitations primarily in monitoring role. Efforts to enhance the standard (to SNMPv2, and now SNMPv3) have not been overly successful to-date. OSI standards are relatively stable and thorough for full function

55、approach to network management. Still limited deployments. End to End management solution will probably make use of multiple standards. Reference Protocol StacksApplicationSessionTransportNetworkLinkPhysicalPresentationTCP, UDPARP, RARPRPCXDRNFSFTP, TelenetSMTP, SNMPRouting Protocols IPROSEACSETP4FT

56、AMCMISELAPDCLNP, ES-IS, IS-ISOSI ManagementInternetReferenceASN.1Centralized vs. Decentralized OAM&P ArchitecturesCentralized ApproachScarce expert resources concentrationRemote site support for physical actions onlySoftware upgrades, configuration & troubleshooting done centrallyDecentralized Appro

57、achGood when the equipment has a number of actions that can be performed locallyTraditionally an approach when only few sites are deployedAssumption, less sophisticated network management systemCORBACommon Object Request Broker Architecture (CORBA):A set of industry standards that facilitate distrib

58、uted object based computingValue:Location IndependencePlatform IndependenceLanguage IndependenceReliability and SecurityKey Concepts:Object Request Broker (ORB)Interface Definition LanguageInter-ORB ProtocolObject Request Broker (ORB)Key element of CORBA technologyORB delivers client requests to ser

59、ver applicationsClient interface is completely independent of the object implementationClient has no knowledge about location, implementation of the object. It has access to an object reference for the objectObject reference is the information needed to specify an object within an ORBOMG Object Mana

60、gement ArchitectureNamingPersistenceSecurityExternalizationTraderQueryCollectionsLife CyclePropertiesConcurrencyTransactionsEventsLicensingChange ManagementRelationshipTimeApplication ObjectsInformationManagementSystemManagementTaskManagementUserManagementCommonFacilitiesObject Request BrokerCORBA O