NETWORK AND SERVICES MANAGEMENT AND CONTROL MSc MODULE (EEM.nsm)

Transcription

1 NETWORK AND SERVICES MANAGEMENT AND CONTROL MSc MODULE (EEM.nsm) Lecture Component: The Telecommunications Management Network Lectures Prof. George Pavlou Centre for Communication Systems Research Tel:

2 2

3 THE TMN FRAMEWORK AND PRINCIPLES 3

4 WHAT IS THE TELECOMMUNICATIONS MANAGEMENT NETWORK (TMN) ITS PURPOSE IS TO SUPPORT TELECOM OPERATORS IN MANAGING TELECOMMUNICATIONS NETWORKS AND SERVICES TO DO THAT IT PROVIDES A FRAMEWORK TO ACHIEVE INTERCONNECTION OF OPERATIONS SYSTEMS AND TELECOMMUNICATIONS EQUIPMENT THIS IS ACHIEVED THROUGH AN AGREED ARCHITECTURE WITH STANDARDISED INTERFACES AND PROTOCOLS 4

5 WHAT IS THE TMN (cont d) SERIES OF ITU-T RECOMMENDATIONS (M.3xxx) INITIALLY USED THE OSI SYSTEMS MANAGEMENT MODEL (OSI-SM) AS THE BASIS FOR ITS INTEROPERABLE INTERFACES RECENT EVOLUTION TOWARDS TECHNOLOGY-NEUTRAL REFERENCE POINTS INTERFACES MAY BE REALISED WITH EITHER OSI-SM OR OMG CORBA HIERARCHICAL LAYERED ARCHITECTURE RICH AND GENERAL ARCHITECTURAL FRAMEWORK 5

6 TMN RELATIONSHIP TO A TELECOM NETWORK Management Plane Control Plane 6

7 TMN AND THE TELECOM NETWORK: AN EXAMPLE PHYSICAL VIEW TN TMN Interworking Unit Computer TMN Operations System 7

8 TMN AND THE CONTROL PLANE THE TMN IMPLEMENTS THE MANAGEMENT PLANE OF THE BROADBAND ISDN REFERENCE MODEL THE CONTROL PLANE IS RESPONSIBLE FOR THE ESTABLISHMENT AND RELEASE OF ON-DEMAND CALLS FOR: BEARER SERVICES e.g. BASIC TELEPHONY THROUGH SS#7 OR, IN THE FUTURE, THROUGH B-ISDN SIGNALLING ENHANCED SERVICES e.g. IN TELEPHONY SERVICES AND, IN THE FUTURE, MULTIMEDIA MULTIPARTY SERVICES THE TMN DOES NOT AIM TO SUPPORT ON-DEMAND SERVICES, SO IT HAS LESS STRINGENT REAL-TIME REQUIREMENTS MANAGEMENT SERVICES FOR THE OPERATOR MANAGEMENT SERVICES FOR END-USERS 8

9 TMN AND THE CONTROL PLANE (cont d) THE TMN IS ORTHOGONAL TO THE CONTROL PLANE BUT ITS DECISIONS AFFECT THE WAY THE LATTER OPERATES IT INITIALLY CONFIGURES THE NETWORK BASED ON PLANNING CONSIDERATIONS IT SUBSEQUENTLY MONITORS THE NETWORK AND MAKES DECISIONS BASED ON NETWORK CONDITIONS, MANAGEMENT POLICY AND KNOWLEDGE OF FUTURE EVENTS MANAGEMENT INTELLIGENCE OPERATES OUTSIDE THE NETWORK, IN A SIMILAR FASHION TO IN AND TINA 9

10 BASIC TMN OBJECTIVES GENERIC MANAGEMENT MODELS MANAGEMENT OF DIVERSE EQUIPMENT THROUGH STANDARD INTERFACES DISTRIBUTED FUNCTIONALITY SECURITY AND DATA INTEGRITY OSI APPLICATION LAYER PROTOCOLS WERE INITIALLY USED EMERGING ODP-INFLUENCED TECHNOLOGIES, e.g. OMG CORBA, HAVE RECENTLY BEEN ADOPTED 10

11 ARCHITECTURAL REQUIREMENTS MINIMISE REACTION TIMES TO NETWORK EVENTS MINIMISE LOAD CAUSED BY MANAGEMENT TRAFFIC ALLOW FOR GEOGRAPHIC DISPERSION OF CONTROL PROVIDE ISOLATION MECHANISMS FOR FAULTS IMPROVE SERVICE ASSISTANCE AND INTERACTION WITH CUSTOMERS 11

12 TMN SECURITY REQUIREMENTS AUTHENTICATION DATA INTEGRITY DATA CONFIDENTIALITY ACCESS CONTROL 12

13 TMN ARCHITECTURES TMN FUNCTIONAL ARCHITECTURE TMN INFORMATION ARCHITECTURE TMN PHYSICAL ARCHITECTURE 13

14 TMN FUNCTIONAL ARCHITECTURE THE TMN FUNCTIONAL ARCHITECTURE DEFINES: THE TYPES OF FUNCTION BLOCKS THAT MAY BE PRESENT IN A TMN THE TYPES OF REFERENCE POINTS INTERCONNECTING THEM NETWORK ELEMENT, Q-ADAPTOR, OPERATIONS SYSTEM AND WORKSTATION FUNCTION BLOCKS 14

15 TMN FUNCTION BLOCKS TMN OSF WSF MF QAF NEF T

16 TMN REFERENCE POINTS g g TMN WSF WSF TMN f f f q 3 q 3 OSF x OSF q 3 OSF q 3 q 3 q 3 q 3 q 3 NEF NEF QAF NEWT m 16

17 TMN PHYSICAL ARCHITECTURE IN THE TMN PHYSICAL ARCHITECTURE: FUNCTION BLOCKS BECOME PHYSICAL BLOCKS REFERENCE POINTS BECOME INTEROPERABLE INTERFACES PHYSICAL BLOCKS RESIDE IN TMN NODES WHICH ARE CONNECTED THROUGH THE TMN DATA COMMUNICATION NETWORK (DCN) 17

18 INTEROPERABLE REFERENCE POINTS AND INTERFACES Interface Conceptual Facet Reference Point Physical Facet M-Part P-Part 18

19 TMN INTEROPERABLE INTERFACES MAKE POSSIBLE TO MANAGE A MULTI-VENDOR, MULTI- CAPABILITY NETWORK AN INTERFACE IS DEFINED BY A PROTOCOL SUITE AND A SET OF MESSAGES MESSAGES IN TRANSACTION-ORIENTED INTERFACES MANIPULATE OBJECTS, HENCE INTERFACE = ACCESS SERVICE / PROTOCOL + INFORMATION MODEL SHARED MANAGEMENT KNOWLEDGE ENSURES THAT EACH END UNDERSTANDS THE EXACT MESSAGE MEANING 19

20 TMN INTERFACE SPECIFICATION TMN MANAGEMENT SERVICES ARE DECOMPOSED TOP-DOWN TO RESULT IN INTERFACE SPECIFICATIONS TMN MANAGEMENT SERVICE TMN MANAGEMENT SERVICE COMPONENT TMN MANAGEMENT FUNCTION TMN MANAGEMENT FUNCTION SET MANAGEMENT FUNCTIONS ARE USED FOR OBJECT MODELLING AND RESULT IN TMN INTERFACE MODELS 20

21 TMN INTERFACE REALISATION Q - CMIS/P, FTAM BUT ALSO CORBA PROTOCOLS X - SAME AS Q BUT NEEDS SECURITY F - NOT YET STANDARDISED M - NON-TMN MANAGEMENT PROTOCOLS e.g. SNMP, TL1, etc. (OUTSIDE THE TMN) G - THE GUI FUNCTIONAL SPECIFICATION (OUTSIDE THE TMN) 21

22 THE TMN LAYERED MODEL Business Management Service Management Network Management Element Management Network Elements manager to agent relationship 22

23 TMN LAYERS AND FUNCTIONAL AREAS F C A P S Business Management Layer Service Management Layer Network Management Layer Network Element Management Layer 23

24 CLASSES OF Q AND X REFERENCE POINTS TMN OSF B q b OSF B q s q s OSF S q s OSF S x s q n q n OSF N q n OSF N x n q e q e OSF E q e OSF E x e q ne NEF NEF q ne 24

25 THE NETWORK ELEMENT MANAGEMENT LAYER COMPRISES A SET OF ELEMENT MANAGEMENT OSFs THESE CONTROL AND COORDINATE A SUBSET OF ELEMENTS ALLOW THE NETWORK LAYER TO ACCESS THEM MAINTAIN ELEMENT RELATED DATA PROVIDE AN ABSTRACTION OF THE SERVICES PROVIDED TO THE NETWORK LAYER (UNIFIED VIEW) 25

26 THE NETWORK MANAGEMENT LAYER CONTROLS AND COORDINATES NETWORK ELEMENTS WITHIN ITS SCOPE PROVIDES, CEASES, OR MODIFIES THE NETWORK CAPABILITIES FOR SERVICE PROVISION MAINTAIN THE NETWORK CAPABILITIES INTERACTS WITH THE SERVICE MANAGEMENT LAYER 26

27 THE SERVICE MANAGEMENT LAYER CUSTOMER FACING - SERVICE PROVISION, CESSATION, QoS etc. INTERACTION WITH THE SERVICE PROVIDERS INTERACTION BETWEEN SERVICES MAINTAINING STATISTICAL DATA INTERACTION WITH THE NETWORK AND BUSINESS MANAGEMENT LAYERS 27

28 THE BUSINESS MANAGEMENT LAYER RESPONSIBILITY FOR THE TOTAL ENTERPRISE ITS FUNCTIONALITY IS TYPICALLY PROPRIETARY NO X INTERFACE SUPPORTED SETS GOALS RATHER THAN GOAL ACHIEVEMENT (WHAT RATHER THAN HOW) 28

29 TMN INTERACTIONS - EXAMPLE 1 29

30 TMN INTERACTIONS - EXAMPLE 2 30