Management of Telecommunications Networks. Prof. Dr. Aleksandar Tsenov

Transcription

1 Management of Telecommunications Networks Prof. Dr. Aleksandar Tsenov

2 Part 4 Management of Telecommunication Networks I

3 Operation and support Operation is the use of a technical system concerning its purpose in order to derive benefit from it. Supporting the system s functions means supervision and control of its performance parameters in order to keep these functions in a previous defined quality determining bounds. 3

4 Operation vs. Operating Watch out! Operating system! Operation system! 4

5 OSS Operations Support System Short for operations support system, a generic term for a suite of programs that enable an enterprise to monitor, analyze and manage a network system. The term originally was applied to communications service providers, referring to a management system that controlled telephone and computer networks. The term has since been applied to the business world in general to mean a system that supports an organization s network operations. 5

6 BSS Business Support System BSS in Telecom world is Business Support System, part of which is OSS. BSS might, for instance, automate calculation of a subscriber s balance and block services if it is too low. Another usual part of BSS, Billing system, analyzes subscribers activities records, applies rates and bills subscriber s account. CRM (or Order Management system) documents all incoming requests for services (orders) for further processing them inside the organization (like provisioning, activation, maintenance).

7 OSS an example architecture 7

8 OSS an example architecture All network elements (like routers and servers) are usually managed through vendor - specific network managing system (NMS, a computer program that communicates with network equipment to set it up), while typical business processes (for instance, activation of VoIP service, or building of office to office VPN, or VLAN) requires interaction with several pieces of equipment. 8

9 OSS an example architecture So it makes sense to have a platform - independent basement, OSS core (usually Resource and Service Inventory from independent OSS vendor, like NetCracker, Cramer, MetaSolv or Granite), and integrate it with vendorspecific NMS es from another. As a result, OSS database contains / has access to records about Network objects, connections between them and their statuses. 9

10 BSS an example architecture 10

11 BSS an example architecture Having integrated CRM with OSS, a service provider can automate each customer s order decomposition into a set of Network configuration steps through NMS es (plus some manual employee s operations like cabling). Most of network elements configuration commands are typically done and tracked by computers. Employees can also be part of the order workflow, to authorize some tasks or record results of manual operations, but it isn t illustrated here for the sake of simplicity. 11

12 BSS an example architecture As a result, Network is configured to deliver the new service as per subscriber s order. Such a service fulfillment automation lowers time-to-market KPI, improving the service provider s market position. And, saves expensive man-hours per each service fulfillment, thus lowering the operational costs. 12

13 OSS/BSS The bigger Network size and amount of services being activated, the more positive effect you get. Of course, for small networks cost of implementation of full-scale OSS is relatively high, and there may be no reason for such automation. But for really big Networks OSS pays off a lot. 13

14 OSS/BSS OSS also helps a lot as a tool of documenting every operation with the Network. Consistent and up-to-date model of the Network, documented in the OSS and easily accessible by all authorized employees even from remote divisions, is what we name transparency which is crucial for lowering operational expenses. Though it is not that easy to migrate all data sources into OSS and to have employees to work with their data there, but it is doable with enough Telco s management s will and organizational support. 14

15 OSS/BSS To raise effectiveness and make operations more transparent, it is crucial for Telco to get rid of department-owned XLS files and paper workflow, and get holistic OSS with up-to-date database, business-rules, roles and instant reports. Usually, Fault management system efficiency is leveraged by integration with OSS Resource Inventory. Performance management also depends on properly built OSS. One should also think about aligning of all Telco s business processes (not only related to managing the network) with OSS, which usually allows their automation through Workflow component of OSS. 15

16 Network Management: Standards INTERNET INTERNET ENGINEERING TASK FORCE (IETF) OPERATIONS AND MANAGEMENT AREA SNMP ISO ISO-IEC/JTC 1/WG 4 OSI CMIP-CMIS ITU-T SG IV TMN OTHERS DMTF TM FORUM OMG IEEE 16

17 Characteristics IETF Management should be simple Variable oriented approach Management information exchanges may be unreliable ISO Management should be powerful Object oriented approach Management information must be exchanged in a reliable fashion TMN Defines only a management architecture The actual protocols are those of OSI Out-of-band management 17

18 History SNMP OSI TMN

19 ISO Standardization WORKING DOCUMENT nobody implements! COMMITTEE DRAFT TECHNICAL REPORT still nobody implements!! DRAFT INTERNATIONAL STANDARD TECHNICAL REPORT FULL STANDARD 19

20 OSI History SC21/WG4 ESTABLISHED MANAGEMENT FRAMEWORK CMIS/CMIP SYSTEMS MGT. OVERVIEW MANAGEMENT FUNCTIONS

21 OSI Network Management Model OSI Network Management Model Organization Model Functional Model Communication Model Information Model 21

22 OSI Organization Model MDB Manager MDB Agent/Manager MIB Managed Object Managed Object Agent Process MDB Management Database MIB Management Information Base 22

23 OSI Functional Model Fault Management Configuration Management Accounting Management Performance Management Security Management 23

24 OSI Communication Model Management Applications FTAM (ISO 8571) ACSE (ISO 8650) CMISE (ISO 9595) ACSE (ISO 8650) ROSE (ISO 9072) Layer 6 24

25 OSI Information Model Management System acts on Managed Object represents Real Resource MIB MO - Class MO2 MO1 MO3 Real resource (RR) RR6 RR3 RR2 RR1 MO6 MO4 RR4 MO5 RR5 25

26 TMN History WORK ON TMN STARTED BY SGIV M30 IDEAS FROM OSI MGT. WORK STARTED ON DERIVED STANDARDS RESPONSIBILITY MODEL BECAME ANNEX M3010 RESPONSIBILITY MODEL PART OF MAIN TEXT M3010 (rev.)

27 Telecommunications Management Networks (TMN) The X.700 series of standards were developed to support generic OSI network management services and include: X.700 Management Framework X.701 System Management Overview X.710 Common Management Information Service (CMIS) Definition X.711 Common Management Information Protocol (CMIP) Specification X.712 CMIP Protocol Implementation Conformance Statement (PICS) X.720 Management Information Model X.721 Definition of Management Information X.722 Guidelines for the Definition of Managed Objects (GDMO) X.730 Object Management Function X.731 State Management Function X.732 Attributes for Representing Relationships X.733 Alarm Reporting Function X.734 Event Report Management Function X.735 Log Control Function X.736 Security Alarm Reporting Function X.738 Summarization Function X.739 Workload Monitoring Function X.740 Security Audit Trail Function X.745 Test Management Function 27

28 Telecommunications Management Networks (TMN) Extending this information into a framework that is useful for the TMN services, the M.3000 series of standards have been developed. The TMN M.3000 series includes the following recommendations: M.3000 Tutorial Introduction to TMN M.3010 Principles for a TMN M.3020 TMN Interface Specification Methodology M.3100 Generic Network Information Model for TMN M.3200 TMN Management Services Overview M.3300 TMN Management Capabilities at the F Interface 28

29 TMN Conceptual Model OSF Operation Support Function WSF Workstation Support Function NEF Network Element Function QAF Q-Adapter Function NE Network Element 29

30 TMN Reference Points Q3 or q3, CMISE/CMIP Common Management Information Service Element - CMISE Common Management Information Protocol - CMIP Qx or qx, usually CMISE/CMIP with shortened OSI stack X or x, CMISE/CMIP with security additions, FTAM, X.500 File Transfer Access and Management X.500 is a directory service F or f, interface to WSF m, proprietary management interface to a network element g, interface to WSF, a user interface outside TMN 30

31 TMN-Logical Layered Architecture Business Management Layer Vaguely defined, business strategic goal setting Service Management Layer QoS management, customer configuration, accounting etc. Network Management Layer Routing and dedicated network paths, link utilization monitoring, optimizing etc. Element Management Layer Collects information from individual network elements and sets the configuration in NEs Network Element Layer Contains the actual network elements (switches, SS7 components etc.) 31

32 IETF Standardization 32

33 p r o p o s e d s t a n d a r d h i s t o r i c d r a f t s t a n d a r d f u l l s t a n d a r d p r o p o s e d s t a n d a r d i m p l e m e n t a t i o n e x p e r i e n c e d r a f t s t a n d a r d p r o p o s e d s t a n d a r d d r a f t s t a n d a r d SNMP History SGMP SNMP SNMP security SMP SNMPv2 (parties) SNMPv2 (community) SNMPv3 CMOT HEMS/HEMP

34 IETF Standards SMI STRUCTURE OF MANAGEMENT INFORMATION RFC 1155 MIB-II MANAGEMENT INFORMATION BASE RFC 1213 A LARGE NUMBER OF ADDITIONAL MIBs EXIST SNMP SIMPLE NETWORK MANAGEMENT PROTOCOL RFC 1157 NAME IS USED IN A MORE GENERAL SENSE NEWER VERSIONS: SNMPv2 & SNMPv3 34

35 Internet Management Principal Operation MANAGER SNMP AGENTS MIB 35

36 Internet Management Principal Operation MANAGER POLLING TRAPS AGENTS MIB 36

37 SMI Structure of Management Information RFC 1155: SMIv1 RFC 1212: CONCISE MIB DEFINITIONS RFC 2578: SMIv2 RFC 2579: TEXTUAL CONVENTIONS 37

38 SMI Structure of Management Information Management information within managed systems must be represented as: Scalars Tables address MANAGED OBJECT INSTANCES name uptime SNMP MANAGER AGENT 38

39 MIB II Management Information Base II Contain the managed objects (variables) That represent the resources of a system and which may be monitored and modified by a (remote) manager To control the behaviour of that system SNMP MIB MANAGER AGENT 39

40 MIB II Naming root ccitt (0) iso (1) joint-iso-ccitt (2) stnd (0) reg-auth (1) mb (2) org (3) dod (6) internet (1) directory (1) mngt (2) experimental (3) private (4) security (5) snmpv2 (6) mib-2 (1) system (1) interfaces (2)... transmission (10) snmp (11) ospf (14) bgp (15) ethernet (6) token ring (9) fddi (15) adsl (94)... 40

41 SNMP Simple Network Management Protocol 41

42 SNMPv3 Architecture 42

43 TeleManagement Forum The TeleManagement Forum is an international non-profit organization serving the information services and communications industry. Its mission is to help service providers and network operators automate their business processes in a cost- and time-effective way. 43

44 Telecommunications Operations Map (TOM) The Telecommunications Operations Map (TOM) is a business process framework that provides the enterprise processes required for a telecommunications service provider. The customer operations processes of fulfilment assurance and billing are the focus of this framework. TOM is used to instantiate the business model. The Telecom Operations Map serves as the blueprint for process direction and the starting point for development and integration of Business and Operations Support Systems (OSS). Now, it also helps to drive TM Forum members work to develop NGOSS. 44

45 Telecommunications Operations Map (TOM) It consists of: A description of the role of the Telecom Operations Map A high-level view of Communications Operations processes, subprocesses and activities that is top down, customer-centric, and end-to-end focused A high-level identification of the primary end-to-end processes of fulfillment, assurance, and billing, and sub-processes within each Illustrative examples of process flows that show end-to-end process A more detailed view of the functions of each sub-process, including activities of each sub-process box, as well as its inputs and outputs to other sub-process boxes Uses of the map 45

46 Telecommunications Operations Map (TOM) The basic model continues to be stable even as the Telecommunications industry continues to change, largely because the Telecom Operations Map: Uses a high level and generic approach Reflects a broad range of operations views Reflects the way service providers run and are architecting their Businesses Is widely used It is the de facto standard for operations management processes for the industry. 46

47 Telecommunications Operations Map (TOM) Terms and Definitions End User An end user is in the domain of the customer. An end user is interested in using communications and data services, e.g., Telecom, Internet/Intranet, Mobile/Wireless, etc. Customer The customer purchases communications and or data services from a service provider and/or network operator. 47

48 Telecommunications Operations Map (TOM) Service Provider In the TOM, the term service provider refers to companies who provide communications and/or data services as a business. Service providers may operate networks, or they may integrate the services of other providers to deliver a total service to their customers. Providing communications services to any customer may involve multiple service providers and/or network operators, where one provider may "subcontract" with other providers to fulfill the customer's needs. When necessary to account for this relationship, the term service provider is used in this document to describe the company responsible to provide service to a customer. The term other provider is used to denote companies which have a sub-contractual responsibility. 48

49 Telecommunications Operations Map (TOM) Network Operator An organization that operates a communications network, network or data services capability, acting basically as a wholesaler. A network operator is a service provider. A service provider may provide the network operator role or may subcontract this role. Other Provider Other providers include service providers and network operators who are subcontracted by the customer s service provider to deliver the original customer request fully or as a component of the request. 49

50 Telecommunications Operations Map (TOM) End-to-End Process Flow TM Forum uses the term end-to-end process flow to include all subprocesses and activities, and the sequence required to accomplish the goals of the process. An end-to-end process has a beginning and an end with specific result expectations. TM Forum uses the term flow-through to mean automation across an interface or set of interfaces within an end-to-end process flow. TM Forum s focus is on top down, meaning customer point of view, end-toend processes that deliver the required result to the customer with flowthrough between the customer and the network elements. 50

51 Telecommunications Operations Map (TOM) The Business Reference Model 51

52 Telecommunications Operations Map Telecom Operations Map, Business Process Framework 52

53 Telecommunications Operations Map FAB End-To-End Process Breakdown 53

54 Telecommunications Operations Map Rough Example of Fulfillment Process Flow Instance 54

55 Telecommunications Operations Map Customer Interface Management Processes 55

56 A Brief History : development of TOM (Telecom Operations Map) 1999: stabilization of TOM : evolution of TOM towards ETOM 2001: etom v1.0, and v2.0 for Member Evaluation Jan 2002: etom v2.5 for Public Evaluation May 2002: etom v3.0 is TMF Approved : Updates to core etom released to Members and Public March 2004: New release etom 4.0 is TMF Approved extends v3.0 with further process decompositions and flows in selected application areas, also B2B support and ITIL mappings April 2004: Submission of etom 4.0 to ITU-T as a standard May/June 2004: Formal acceptance of etom by ITU-T August 2004: etom 4.5 released as part of NGOSS 4.5 and work never stops 56

57 Enhanced Telecommunications Operations Map (etom) 57

58 etom Operations Area 58

59 etom Operations Area 59

60 etom The SIP Area 60

61 etom The SIP Area 61

62 etom Enterprise Management Area 62

63 Example Interactions Flow: Ordering (Fulfillment) 63

64 Example Process Dynamics Flow: Ordering (Fulfillment) 64

65 65

66 66

67 67

68 Sources ISO OSI Management Framework, ISO, 1980 M.3010 Principles for a TMN, ITU T, 1988 TOM - GB910 Main document, TeleManagement Forum, 2000 etom GB921 - Main document, TeleManagement Forum,