Upload
michael-lucas
View
215
Download
2
Tags:
Embed Size (px)
Citation preview
1
Network Management
Chapter 2 Architecture and Business
Process
POSTEC Lecture
March18-April 10, 2008
Masayoshi Ejiri Japan
2
Agenda
1. ICT Operations and Management - Service Industries - ICT Services and Networks— - Target of the Management 2, Architecture ,Function ,Information Model and Business Process - ITU-T TMN( Telecommunications Management Network) - TeleManagement Forum Telecommunications Operations Map ( TOM) - Multi domain management and System Integration - Standardization3. OSS( Operations Support System ) Development - Software Architecture ,Key Technologies and Product Evaluation—4. SLA( Service Level Agreement) and QoS( Quality of Service) - SLA Definition , reference point and policy based negotiation5, IP/eBusiness Management - Paradigm shift , Architecture beyond TMN and enhanced TOM6. NGN( Next Generation Networks) Management - NGN Networks and Services , New Paradigm of ICT Business and Ma
nagement
3
OSS Development -Individually without Ground Plan-
Service OpSNetwork OpS
NE NE NE NESwitching Transmission Cables Power Supply
OpSOpSOpS
OpSOpS
OpSOpS
ISDNNetwork
DDX Network
TrafficFree Dial
MassCalling
Personal Phone
Mobile
ISDN Services
DDX Services
Leased Line Services
Information Transmision Network
NE OpS OpSOpSOpS OpSOpSOpS OpSOpSOpS OpSOpSOpS
OpSOpSOpS
OpSOpSOpS
OpSOpSOpS
OpS=OSS
4
New Gen. Plug and Play Systems:Current Implementation Architecture
• N2 Complexity• New Services
hard• Data Consistency• Heavy messages
*Quote from TMF document
5
New Gen. Plug and Play Systems:Program Principles to be Validated
Directory
M1 M3 Mn
M2 Mn-1
...
WorkFlow
Bus
Common BusComponent ApplicationsWorkflow controlDirectory
*Quote from TMF document
6
Systematic OSS Development
마구만들고 , 뿔뿔만들고 , 내버려두다“Haphazard, individual and No PDCA”
“Strategic, Cooperative and Lifecycle Care “ ・ Ground Plan/View of Operations ・ Analysis not Process disordered Enumerati
on Share common operations view, architecture and b
usiness process
7
Trend of OSS Development
Ops to supervise andcontrol NEs
Ops to supervise andcontrol NEs
Centralized OpS fornetwork management
Centralized OpS fornetwork management
Customer orientedtotal OpS
Customer orientedtotal OpS
DCNDCN
DCNDCN
DCNDCN
NE OpS
Network OpS
Z company Customers
SP
NetworkOpS
NEOpS
A company
DCNDCN
8
Systematic Approach
• Operations Overview
• Functional Architecture
• Business Process
• Telecom Operations Map by SMART Team ( Service Management Automation
and Reengineering Team)
9
ITU-T TMN Recommendations
• Overview of TMN : Recommendations M3000• Principle of TMN : M3010 TMN Functional Architecture LLA : Logical Layered Architecture TMN Information Architecture TMN Physical Architecture • TMN Management Area and Management Services : M3200
ITU-T : http://www.itu.int/ITU-T/index.html Recommendation : http://www.itu.int/ITU-T/publications/recs.html
10
TMN related ITU-T Recommendation Series
• Series E : Overall network operation, telephone service, service operation and human factors
• Series F : Non-telephone telecommunication services• Series G : Transmission systems and media, digital systems and
networks• Series I : ISDN Integrated services digital network• Series M : TMN and network maintenance: international transmission
systems, telephone circuits, telegraphy, facsimile and leased circuits• Series Q : Switching and signalling• Series Y ; Global information infrastructure and Internet protocol aspe
cts---NGN• Series X : Data networks and open system communications
Note : ITU-T Recommendation URL http://www.itu.int/ITU-T/publications/recs.html
11
TMN Referenced Recommendation
• Telecommunication services : F-series Recs.• Telecommunication network architecture and component
s : I/Q/G-series-Recs.• Communication protocol, services and messages : I/Q/X-
series-Recs.• Telecommunication network management for traffic, mai
ntenance,provisioning and security : E/M-series-Recs.• ISPs ,managed object naming and addressing : X-series
Recs.
12
TMN Subject Areas
• Architecture : M.3010,M.3013 ; Methodology : M.3020 ; Security : M.3016 ; Terminology : M60
• Management services and functions : M.3200 series, M.3300, M.3320, M3400
• Management information model and catalogues : M3100, M.3101, M3108.x, M3180, G774, G85x-series,I.751
• Communication services, messages and ISPs : Q81x-series, Q82x-series, G773, Q94x-series
ISP : International Standardized Profile
13
TMN Objectives
• Ensure OSS Interoperability by providing standardized management
framework ,interface and information model.
For
planning, installation, operations, administration, maintenance and provisioning
of telecommunications networks and services.
14
TMN(Telecommunications Management Network)General Relationship
ITU-T Rec. M3010
15
T0412990-99
OSF
TF
TF
NEF
WSF
TMN
NEF Network Element FunctionOSF Operation Systems FunctionTF Transformation FunctionWSF Workstation Function
The TMN functional boundary
TMN function blocks M.3010
16
T0413010-99
g g
WSF
OSF
NEF
WSF
OSF
OSF
NEF
f
fxq
q
q
q
q
q
m
f
q
q
TF
TMN TMN
Reference points between management function blocks
q, f, x, g, m
17
Model for layering of TMN Management function
18
TMN Pyramid
NEM
NWM
SM
BM
Vendor Independent View
Technology Independent View
SLA View
19
Business Management
• A part of the overall management of the enterprise : goal setting tasks rather than goal achievement
• Principle roles 1)supporting the decision-making process for the optimal
investment and use of new telecommunications resources;
2)supporting the management of OA&M related budget;
3)supporting the supply and demand of OA&M related manpower;
4)maintaining aggregate data about the total enterprise.
OA&M : Operations, Administration and Maintenance
20
TMN defines
•Architecture Functional, Information ,Physical•Management Layer : BM,SM,NM,NEM•Management Functional Area: FCAPS•Management Platform•Management Information Model•Management Applications
21
Interface
Message
Flow & Timing
Protocol
Common Language
Hand Shake
Process
Managed Object、Information/Data Model
Process ManagementWork Flow Engine
CMIP,SNMP,CORBA,tMN
22
Q-Mediation Device(QMD)
Workstation(WS)
Operation System(OS)
Data Communication Network(DCN)
G
TMN
X/F/Q
Q
FX
Q
Q
Q-Adaptor(QA)
NetworkElement
(NE)
Q
TMN Simplified Physical Architecture
NetworkElement
(NE)
M
Rec. M3010, 2000
23
Mediation Device(MD)
Workstation(WS)
Operation System(OS)
Data Communication Network(DCN)
TMN
Q3
Qx
FX
Q3
Data Communication Network(DCN)
QxQx
Q-Adaptor(QA)
NetworkElement
(NE)
Q3
Network Level IntegrationAcross Managed Area
Network Level IntegrationAcross Managed Area
Element Level Integrationwithin Managed Area
TMN Physical Architecture
NetworkElement
(NE)
Q-Adaptor(QA)
Modified Rec.M3010 1998
Service Level Integration for Customers/Service Providers
24
FCAPS Rec. M3400on OSI ( Open System Interconnection ) Management
5. Performance Management 5.1 Performance Quality Assurance 5.2 Performance Monitoring 5.3 Performance Management Control 5.4 Performance Analysis
6. Fault Management 6.1 RAS Quality Assurance 6.2 Alarm surveillance 6.3 Fault localization 6.4 Fault Correction 6.5 Testing 6.6 Trouble administration
7. Configuration Management 7.1 Network Planning and Engineering 7.2 Installation 7.3 Service Planning and Negotiation 7.4 Provisioning 7.5 Status and control
8. Accounting Management 8.1 Usage Measurement 8.2 Tariffing/pricing 8.3 Collections and Finance 8.4 Enterprise Control
9. Security Management 9.1 Prevention 9.2 Detection 9.3 Containment and Recovery 9.4 Security Administration
25
5. Performance Management•
5.1 Performance Quality Assurance• 5.1.1 QOS performance goal setting function
set• 5.1.2 Network performance goal setting
function set• 5.1.3 Subscriber service quality criteria
function set• 5.1.4 QOS performance assessment function
set• 5.1.5 Network performance assessment
function set• 5.1.6 NE(s) performance assessment function
set• 5.1.7 Data integrity check function set
5.2 Performance Monitoring
• 5.2.1 Performance monitoring policy function set
• 5.2.2 Network performance monitoring event correlation and filtering function set
• 5.2.3 Data aggregation and trending function set
• 5.2.4 Circuit-specific data collection function set
• 5.2.5 Traffic status function set• 5.2.6 Traffic performance monitoring function
set• 5.2.7 NE(s) threshold crossing alert processing
function set• 5.2.8 NE(s) trend analysis function set
• 5.2.9 Performance monitoring data accumulation function set
• 5.2.10 Detection, counting, storage and reporting function set
5.3 Performance Management Control
• 5.3.1 Network traffic management policy function set
• 5.3.2 Traffic control function set• 5.3.3 Traffic administration function set
• 5.3.4 Performance administration function set
• 5.3.5 Execution of traffic control function set• 5.3.6 Audit report function set
5.4 Performance Analysis
• 5.4.1 Recommendations for performance improvement function set
• 5.4.2 Exception threshold policy function set• 5.4.3 Traffic forecasting function set
• 5.4.4 Customer service performance summary (excludes traffic) function set
• 5.4.5 Customer traffic performance summary function set
• 5.4.6 Traffic exception analysis function set
• 5.4.7 Traffic capacity analysis function set
• 5.4.8 Network performance characterization function set
• 5.4.9 NE(s) performance characterization function set
• 5.4.10 NE(s) traffic exception analysis function set
• 5.4.11 NE(s) traffic capacity analysis function set
26
QoS in M3400 PM
Quality of Service includes monitoring and recording of parameters relating to:
• a) Connection establishment (e.g. call set-up delays, successful and failed call requests).
• b) Connection retention.• c) Connection quality.• d) Billing integrity.• e) Keeping and examining of logs of system state histories.• f) Cooperation with fault (or maintenance) management to
establish possible failure of a resource and with configuration management to change routing and load control parameters/limits for links, etc.
• g) Initiation of test calls to monitor QOS parameters.
27
6. Fault Management (1) 6.1 RAS Quality Assurance
• 6.1.1 Network RAS goal setting function set
• 6.1.2 Service availability goal setting function set
• 6.1.3 RAS assessment function set
• 6.1.3.1 Management requirements
• 6.1.4 Service outage reporting function set
• 6.1.5 Network outage reporting function set
• 6.1.6 NE(s) outage reporting function set
6.2 Alarm surveillance
• 6.2.1 Alarm policy function set
• 6.2.2 Network fault event analysis, including correlation and filtering function set
• 6.2.3 Alarm status modification function set
• 6.2.4 Alarm reporting function set
• 6.2.5 Alarm summary function set
• 6.2.6 Alarm event criteria function set
• 6.2.7 Alarm indication management function set
• 6.2.8 Log control function set
• 6.2.9 Alarm correlation and filtering function set
• 6.2.10 Failure event detection and reporting function set
6.3 Fault localization
• 6.3.1 Fault localization policy function set
• 6.3.2 Verification of parameters and connectivity function set
• 6.3.3 Network fault localization function set
• 6.3.4 NE(s) fault localization function set
• 6.3.5 Running of diagnostic function set
28
6. Fault Management (2)
6.4 Fault Correction
• 6.4.1 Management of repair process function set
• 6.4.2 Arrangement of repair with customer function set
•Page
• 6.4.3 Scheduling and dispatch administration of repair forces function set
• 6.4.4 NE(s) fault correction function set
• 6.4.5 Automatic restoration function set
6.5 Testing
• 6.5.1 Test point policy function set
• 6.5.2 Service test function set
• 6.5.3 Circuit selection, test correlation and fault location function set
• 6.5.4 Selection of test suite function set
• 6.5.5 Test access network control and recovery function set
6.5.6 Test access configuration function set
• 6.5.7 Test circuit configuration function set
• 6.5.8 NE(s) test control function set
• 6.5.9 Results and status reporting function set
• 6.5.10 Test access path management function set
• 6.5.11 Test access function set
6.6 Trouble administration
• 6.6.1 Trouble report policy function set
• 6.6.2 Trouble reporting function set
• 6.6.3 Trouble report status change notification function set
• 6.6.4 Trouble information query function set
• 6.6.5 Trouble ticket creation notification function set
• 6.6.6 Trouble ticket administration function set
• 6.6.7 Management of trouble by service customer function set (new function set)
29
7. Configuration Management (1)7.1 Network Planning and Engineering
• 7.1.1 Product line budget function set• 7.1.2 Supplier and technology policy function
set• 7.1.3 Area boundary definition function set• 7.1.4 Infrastructure planning function set• 7.1.5 Management of planning and engineering
process function set• 7.1.6 Demand forecasting function set• 7.1.7 Network infrastructure design function set• 7.1.8 Access infrastructure design function set
• 7.1.9 Facility infrastructure design function set• 7.1.10 Routing design function set• 7.1.11 NE(s) design function set
7.2 Installation
• 7.2.1 Procurement function set• 7.2.2 Management of installation function set• 7.2.3 Contracting function set• 7.2.4 Real estate management function set• 7.2.5 Arrangement of installation with customer
function set• 7.2.6 Network installation administration
function set• 7.2.7 Material management function set• 7.2.8 Scheduling and dispatch administration of
installation force function set• 7.2.9 Installation completion reporting function
set
• 7.2.10 Software administration function set• 7.2.11 NE installation administration function set• 7.2.12 Loading software into NEs function set
7.3 Service Planning and Negotiation
• 7.3.1 Service planning function set• 7.3.2 Service feature definition function set• 7.3.3 Marketing function set• 7.3.4 Management of sales process function set• 7.3.5 External relations (legal, stockholders,
regulators, public relations) function set• 7.3.6 Customer identification function set• 7.3.7 Customer need identification function set• 7.3.8 Customer service planning function set• 7.3.9 Customer service feature definition function
set• 7.3.10 Solution proposal function set
7.4 Provisioning
• 7.4.1 Provisioning policy function set• 7.4.2 Material management policy function set• 7.4.3 Access route determination function set• 7.4.4 Directory address determination function set• 7.4.5 Leased circuit route determination function
set• 7.4.6 Request for service function set• 7.4.7 Service status administration function set• 7.4.8 Network resource selection and assignment
function set
30
7. Configuration Management (2)• 7.4.9 Interexchange circuit design function
set• 7.4.10 Access circuit design function set
• 7.4.11 Leased circuit design function set
• 7.4.12 Facility design function set
• 7.4.13 Manage pending network changes function set
• 7.4.14 Network connection management function set
• 7.4.15 Circuit inventory notification function set
• 7.4.16 Circuit inventory query function set
7.4.17 NE(s) configuration function set
• 7.4.18 NE(s) administration function set
• 7.4.19 NE(s) database management function set
• 7.4.20 Assignable inventory management function set
• 7.4.21 NE(s) resource selection and assignment function set
• 7.4.22 NE(s) path design function set
• 7.4.23 Loading program for service feature(s) function set
• 7.4.24 NE(s) inventory notification function set
• 7.4.25 NE(s) inventory query function set
• 7.4.26 Manage pending changes in NE(s) function set
• 7.4.27 Access to parameters and cross-connects in NEs function set
• 7.4.28 Access to service features in NEs function set
• 7.4.29 Self-inventory function set
7.5 Status and control
• 7.5.1 Priority service policy function set
• 7.5.2 Priority service restoration function set
• 7.5.3 Message handling systems network status function set
• 7.5.4 Leased circuit network status function set
• 7.5.5 Transport network status function set
• 7.5.6 NE(s) status and control function set
• 7.5.7 Access to state information in NEs function set
• 7.5.8 Notification of state changes by NEs function set
31
8. Accounting Management (1)
8.1 Usage Measurement
• 8.1.1 Planning of the usage measurement process function set
• 8.1.2 Management of the usage measurement process function set
• 8.1.3 Usage aggregation function set
• 8.1.4 Service usage correlation function set
• 8.1.5 Service usage validation function set
• 8.1.6 Usage distribution function set
• 8.1.7 Usage surveillance function set
• 8.1.8 Usage error correction function set
• 8.1.9 Usage testing function set
• 8.1.10 Measurement rules identification function set
• 8.1.11 Network usage correlation function set
• 8.1.12 Usage short-term storage function set
•
• 8.1.13 Usage long-term storage function set
• 8.1.14 Usage accumulation function set
• 8.1.15 Usage validation function set
• 8.1.16 Administration of usage data collection function set
• 8.1.17 Usage generation function set
8.2 Tariffing/pricing
• 8.2.1 Pricing strategy function set
• 8.2.2 Tariff and price administration function set
• 8.2.3 Costing function set
• 8.2.4 Settlements policy function set
• 8.2.5 Feature pricing function set
• 8.2.6 Provision of access to tariff/price information function set
• 8.2.7 Rating usage function set
• 8.2.8 Totalling usage charges function set
32
8.Accounting Management (2)
8.3 Collections and Finance
• 8.3.1 Planning of the billing process function set
• 8.3.2 Management of the billing process function set
• 8.3.3 General accounting operations function set
• 8.3.4 General ledger function set
• 8.3.5 Accounts receivable function set
• 8.3.6 Accounts payable function set
• 8.3.7 Payroll function set
• 8.3.8 Benefits administration function set
• 8.3.9 Pension administration function set
• 8.3.10 Taxation function set
• 8.3.11 Human resources function set
• 8.3.12 Invoice assembly function set
• 8.3.13 Sending invoice function set
• 8.3.14 Customer tax administration function set
• 8.3.15 In-call service request function set• 8.3.16 Storage of invoice function set• 8.3.17 Receipt of payment function set• 8.3.18 Inquiry response function set• 8.3.19 Collections function set• 8.3.20 Customer account administration
function set• 8.3.21 Customer profile administration function
set
8.4 Enterprise Control
• 8.4.1 Budgeting function set• 8.4.2 Auditing function set• 8.4.3 Cash management function set• 8.4.4 Raising equity function set• 8.4.5 Cost reduction function set• 8.4.6 Profitability analysis function set• 8.4.7 Financial reporting function set• 8.4.8 Insurance analysis function set• 8.4.9 Investments function set• 8.4.10 Assets management function set• 8.4.11 Tracking of liabilities function set
33
9. Security Management (1)9.1 Prevention
• 9.1.1 Legal review function set
• 9.1.2 Physical access security function set
• 9.1.3 Guarding function set
• 9.1.4 Personnel risk analysis function set
• 9.1.5 Security screening function set
9.2 Detection
• 9.2.1 Investigation of changes in revenue patterns function set
• 9.2.2 Support element protection function set
• 9.2.3 Customer security alarm function set
• 9.2.4 Customer (external user) profiling function set
• 9.2.5 Customer usage pattern analysis function set
• 9.2.6 Investigation of theft of service function set
• 9.2.7 Internal traffic and activity pattern analysis function set
• 9.2.8 Network security alarm function set
• 9.2.9 Software intrusion audit function set
• 9.2.10 Support element security alarm reporting function set
9.3 Containment and Recovery
• 9.3.1 Protected storage of business data function set
• 9.3.2 Exception report action function set
• 9.3.3 Theft of service action function set
• 9.3.4 Legal action function set
• 9.3.5 Apprehending function set
• 9.3.6 Service intrusion recovery function set
• 9.3.7 Administration of customer revocation list function set
• 9.3.8 Protected storage of customer data function set
• 9.3.9 Severing external connections function set
• 9.3.10 Network intrusion recovery function set
• 9.3.11 Administration of network revocation list function set
• 9.3.12 Protected storage of network configuration data function set
• 9.3.13 Severing internal connections function set
• 9.3.14 NE(s) intrusion recovery function set
• 9.3.15 Administration of NE(s) revocation list function set
• 9.3.16 Protected storage of NE(s) configuration data function set
34
9.Security Management (2)9.4 Security Administration
• 9.4.1 Security policy function set
• 9.4.2 Disaster recovery planning function set
• 9.4.3 Manage guards function set
• 9.4.4 Audit trail analysis function set
• 9.4.5 Security alarm analysis function set
• 9.4.6 Assessment of corporate data integrity function set
• 9.4.7 Administration of external authentication function set
• 9.4.8 Administration of external access control function set
• 9.4.9 Administration of external certification function set
• 9.4.10 Administration of external encryption and keys function set
• 9.4.11 Administration of external security protocols function set
• 9.4.12 Customer audit trail function set
• 9.4.13 Customer security alarm management function set
• 9.4.14 Testing of audit trail mechanism function set
•
• 9.4.15 Administration of internal authentication function set
• 9.4.16 Administration of internal access control function set
• 9.4.17 Administration of internal certification function set
• 9.4.18 Administration of internal encryption and keys function set
• 9.4.19 Network audit trail management function set
• 9.4.20 Network security alarm management function set
• 9.4.21 NE(s) audit trail management function set
• 9.4.22 NE(s) security alarm management function set
• 9.4.23 Administration of keys for NEs function set
• 9.4.24 Administration of keys by an NE function set
35
6.1.3 RAS assessment function setThis set provides access to quantitative goals that are set and provides access to reports of
measurements of reliability, availability and survivability in comparison with goals.
6.1.3.1 Management requirementsThis function set may be supported by an OSF, that shall retain a master database, or by a person working through a WSF, who shall retain a human-readable copy of the master data.
6.1.3.2 General Functional ModelThis function set is associated with a B-OSF that performs manager roles of the current
TMN Management Functions of this set. The function block of this set receives, stores and summarizes information from function blocks that report RAS information, including Network outage reporting and Service outage reporting. These associated function blocks perform
agent roles. TMN Management Functions that provide access to the summarized informationand access to goals are for further study.
6.1.3.3 TMN Management Functions1)Report network outage – Agent reports network outage to manager.2)Report service outage – Agent reports service outage to manager.
3)Request network outage summary report – Manager requests agent to send network outage summary reports. Agent responds with the requested information.
4)Request service outage summary report – Manager requests agent to send service outage summary reports. Agent responds with the requested information.
36
TMN Management Services Rec.M3200
List of Management Services• 1) Customer Administration;• 2) Network Provisioning Management;• 3) Work Force Management;• 4) Tariff, Charging and Accounting Administration;• 5) Quality of Service and Network Performance
Administration;• 6) Traffic Measurement and Analysis Administration;• 7) Traffic Management;• 8) Routing and Digit Analysis Administration;• 9) Maintenance Management;• 10) Security Administration;
37
Examples of generic scenarios (1)
I.1 Customer Administration• I.1.1 Service activation (CM, PM, FM, AM, SM)• I.1.2 Immediate service activation with pre-equipped resources (CM, PM,
FM, AM, SM)• I.1.3 Customer request to activate capacity (CM, PM, AM, SM)• I.1.4 Request for network information (CM)• I.1.5 Customer trouble report (FM, CM)I.2 Network provisioning management• I.2.1 Capacity provisioning for new and/or existing services (CM, AM)
I.3 Work force management• I.3.1 Enterprise management (AM, FM, CM, SM)I.4 Tariff, charging and accounting administration• I.4.1 Pricing and billing process set-up (AM, CM)• I.4.2 Billing and collections (AM, PM, FM, CM, SM)I.5 Quality of Service and network performance administration• I.5.1 Traffic quality assurance (PM, CM)• I.5.2 Performance quality assurance (PM, CM, AM)• I.5.3 Reliability, Availability and Survivability Quality Assurance (FM)
38
Examples of generic scenarios (2)
I.6 Traffic measurement and analysis administration• I.6.1 Traffic analysis (PM, CM)I.7 Traffic management• I.7.1 Network traffic control (PM, FM, CM)• I.7.2 Customer-related traffic control (PM, CM)I.8 Routing and digit analysis administrationI.9 Maintenance management• I.9.1 PM Proactive Maintenance (PM, FM, CM)• I.9.2 Network detected trouble (FM, PM, CM, AM)• I.9.3 Fault localization (FM, PM, CM)• I.9.4 Fault correction (FM, CM)I.10 Security administration• I.10.1 Establish/change privileges (SM)• I.10.2 Audit detection of a security violation (SM, CM, AM)
39
Generic scenarios Ex. 1.2.1 : Network Provisioning Management Capacity provisioning for new and/or existing services( CM, AM)
40
T0406770-96
1
2 5
67
9
8
10
11
12
1314
15
16
3
17
18
4
Alarm Surveillance– Failure event detection and reporting
Fault Localization– Running of diagnostic
Testing– Test access
Testing– Test access configuration– Test circuit configuration– NE(s) test control– Results and status reporting– Test access path management
Fault Localization– NE(s) fault localization
Alarm Surveillance– Alarm reporting– Log control– Alarm summary– Alarm correlation and filtering
Alarm Surveillance– Network fault event correlation and filtering
Fault Localization– Network fault localization
Trouble Administration– Trouble ticket administration
Fault Localization– Verification of parameters and connectivity
Testing– Test point policy
Configuration:Provisioning– Facility design
Performance:Performance Monitoring– Network performance monitoring event correlation and filtering
Fault Localization– Fault localization policy
Testing– Circuit selection, test correlation and fault location– Selection of test suite– Test access network control and recovery
Generic scenarios Ex. 1.9.3 :Maintenance management
Fault localization ( FM,PM,CM)
41
Interface
• Unified Modeling Language• OSI System Management
System Management Application
Management Information Architecture
Manager/Agent concept
Managed Object
Management Information Services
42
Interface specification methodologyRec. M3020
• UTRAD(Unified TMN Requirement, Analysis and Design) described using UML ( Unified Modeling Language)
• GDMI ( Guidelines for the Definition of Management Interface )
Requirement: Business requirement & Specification Requirement
Analysis : Implementation Independent specification. ( Class description, Data definition, Class relationship, Interaction diagrams( Sequence and/or Collaboration ) , Date transition diagrams and Activity diagrams
Design : Implementable Interoperable Technology specific specification ( Information model specification using GDMO for Managed Object Class, Attributes, Behaviour, Notification, Action, Naming instances and Error/Exception )
43
UML( Unified Modeling Language )1997 OMG standard
• UML : Graphical language to describe( show) the abstraction of problems ( visual business models)
• Describe Objects, their Attributes (facts and Data) , Behaviors (function )and Relationship ( communications among them)
• Actors interact Systems to achieve Goals.• Applicable to planning , OOA/D ( analysis and design ) and implementation for Business process and Computer system development
• Rule : Syntax and Semantics
OMG : Object Management Group
44
UML Diagrams (1)• Use Case Diagrams “Show relationship between Actor, function and other
systems. “ Scenario : What happen when Actor : who or what initiates events• Class Diagrams “Show static system overview, structure and relationship of
class; what interact , not what happens” Interaction : association, aggregation and generalization• Object Diagrams “Static model , show snapshot of instances state. “• Sequence Diagrams “Show dynamic objects interaction“
“ How operations carried out , what messages sent and when “
45
UML Diagram ( 2)
• Collaboration Diagrams “Show collaboration focus on objects roles “
• Statechart Diagrams “ Show objects states and transitions “
• Active Diagrams “ Show how activities depend on one another , work flow of a
ctivities “
• Component Diagrams “Show physical unit of software/hardware and mutual depen
dency“
• Deployment Diagrams “ Show physical configuration of software/hardware “
46
T0412320-99Service Provisioning
service providerservice customer
MaintenanceTrouble Administration
Customer Admin LCS
<<include>>
<<include>><<include>>
M.3020 – Customer Administration of LCS Use Case
LCS : Leased Circuit Service
47
T0412330-99
LCS administrative Function Set
service providerservice customer service Provisioning
<<extends>>
<<include>> <<include>>
Link administrative Function Set
Link Configuration Function SetConfigure LCS
<<extends>>
M.3020 – Service Provisioning Use Case for CNM of LCS and Link Connections
48
T0412340-99
service providerservice customer Configure LCS
<<include>> <<include>> <<include>>
Create LCS Delete LCS Modify LCS
Cancel LCS Request Invalid Parameters Encountered
<<extends>>
<<extends>><<extends>>
<<extends>>
M.3020 – Decomposition of LCS Configuration Function Set Use Case
49T0412380-99
service(subclass)
service request(subclass)
service requestcreated if input valid
: service provider: service customer
[input valid] newservice request
[input valid]: create response(accepted/modified inputparameters)
[invalid input]: createrequest reject
modify request of service request parameters
response to modify (accepted/modified/reject)
report service request state/parameter value changes
report service creation
[accept request]: createresponse service request
M.3020 – Sequence diagram: Successful creation of service
50
ServiceProvider
Service Customer
Service Request
Service( subclass)
1:
2:
3:4:
5:
6:7: 8:
1: new service request2: valid request, service request created3: valid input parameters, respond with service request creation4: invalid request parameters, respond with service request failure5: modify service request6: respond to modify service request ( accept/modify/reject)7: report request state/parameter change8: service creation report
Collaboration diagram: Successful creation of service Rec. M3020
51
SMAE ( System Management Application Entity)
Consists of
• SMASE : System Management Application Service Element specify management information ( semantics and syntaxes)
• ACSE : Association Control Service Element
• CMISE : Common Management Information Service Element provides means of information exchange
• ROSE : Remote Operations Service Element
52
TMN Information Architecture
• Exchange management information between managing and managed systems on standardized open management paradigm, e.g. object oriented techniques.
• Interaction Model :managing role( information user)/ managed role( information resource)
ex. manager/agent, client/server, invoker/responder, peer-to-peer, publisher/subscriber, consumer/producer
• Information Model is composed of Information Elements( = objects)• Information Architecture is unified at Reference point into TMN
functional architecture and LLA.
53
OSI System Management Overview
System Management
Managing Process Agent
Process
Managed Objects( MIB)
Manager Managed System
Operations
Notification
Resource
54
TISO0030-92/d03
MIS-User
(manager role)
Communicating
Management operations
Notifications
Accesscontrol
Notificationdissemination
MIS-User(agent role)
Performing
operations
Notifications
emitted
Managedobjects
Managed open system
management
Figure 3 – Communication support for notifications and managements operations
System management interaction, Information and OSI Communications aspect
Rec.X701 MIS : Management Information Service
55
TISO0020-92/do2
Application
Presentation
Session
Transport
Network
Data-link
Physical
Mapping to standardized communication
Systems management application process
Local mapping
Systems managed objects
(N)-layer managed objects
Managed object
Containment hierarchy of managed objects
Systems management information model space
Use standardized OSI management communication
OSI environment Local environment
Figure 2 – Relationship between information and communication aspectsof the systems management model
Relationship between information and communications aspect
Rec.X701
56
Manager/Agent RelationshipManager/Agent Relationship
CustomerCustomerManager
NENEA/M
NENEA/M
NENEA/M
SM.
NM.
EM.
Agent
Manager
Agent
Manager
Agent
Manager
Agent
Manager
Agent
Manager
Agent
Manager
NE
A/M : Agent/Manager
57
Agent Role
Agent
Manager
Resource
Communication(Access Control, Notification Dissemination)
Adaptation
Object Representation(Perform Operation, Emit Notification)
Q3
58
Manager Role
Manager
Operator/Application
Agent
Communication
Interface
Management Application
Q3
Manager
Agent ??Object Representation
59
MO : Managed Object
• What MOs are• What they are composed• What they can do• What can be done to them• How they can related to each other • How they are named
60
MO
• Abstraction of Physical/Logical resources and Target of Operations
• Definition GDMO : Guidelines for the Definition of Managed
Object for object class definition ASN.1 : Abstract Syntax Notation One for data type
definition
61
MO features
• Object composition Attributes Behaviors Actions Notifications Packages• Object class Class hierarchy : superclass, subclass Inheritance Polymorphism• Containment• Naming : Relative distinguished Name, Distinguished Name, Local
Distinguished Name
62
MO Class Rec. X720
managed object class: A named set of managed objects sharing the same (named) sets of attributes, notifications, management operations (packages), and which share the same conditions for presence of those packages.
Super class –Sub class
• inheritance: The conceptual mechanism by which attributes,
notifications, operations and behaviour are acquired by a subclass from its super class
63
MIB
• GDMO name –binding specifies valid location of an object instances in MIB
(Object containment tree)
Object instance is identified by it’s object identifier ( object class and object instance identifier )
64
Management Information Services
• Association services Functional unit, Access control, User information
• Management notification services M-EVENT-REPORT
• Management operations services M-GET, SET, ACTION, CREATE, DELETE,
• Management information tree• Managed object selection
65
CMISE Services Rec. X710
• M-EVENT-REPORT report• M-GET attribute value• M-CANCEL-GET attribute value• M-SET attribute value• M-ACTION to other object• M-CREATE objects class instances• M-DELETE objects class instances
66
CMISE Service parameters example• Invoke identifier• Linked identifier• Mode• Base object class• Base object instance• Scope• Filter• Access control• Synchronization• Attribute identifier list• Managed object class• Managed object instance• Current time• Attribute list• Error
• Invoke identifier• Mode• Event type• Event time• Event information• Managed object class• Managed object instance• Current time• Eveny reply• Error
67
CMOT ISO 7 layers Model• Layer 7 : CMISE , ACSE/ROSE• Layer 6 : LPP• Layer 5 : ISO Session• Layer 4 : TCP/UDP • Layer 3 : IP • Layer 2 : ISO Data link• Layer 1 : Physical
CMOT:Common Managemnt Information Services and Protocol over TCP/IP ACSE : Association Control Service Element
ROSE : Remote Operations Service Element LPP : Lihghtweight Presentation Protocol
68
SNMP messages
• Get-Request
• Get-Response
• Get-Next-Request
• Set-Request
• Trap
69
SNMP ISO 7 layers Model
• Layer 7 : Application ( SNMP)• Layer 6 : Presentation• Layer 5 : Session• Layer 4 : Transport ( UDP )• Layer 3 : Network ( IP )• Layer 2 : Data link• Layer 1 : Physical
UDP : User Datagram Protocol
70
Shared management knowledgeRec.X701
Share the Knowledge of
• Protocol ( application context)• Functions ( functions and functional unit )• Managed Object ( class, instance , identification , attribute )• Constraint ( functions , managed object, relationship )• Definition ( Managed Object class definition )• Repertoire (classes of managed object in given system)
71
System management Organizational aspect
Management Policy
Management Domain
Policysemantics
DomainMembership
( Managed objects)Management Jurisdiction
Rec. X701
72
TMN Implementation
73
Telecommunications Management Network--20 years with TMN --
• 四面無歌 Ignored 1985-1990
• 四面楚歌 Objection 1990-1995
• 四面謳歌 Enjoy 1995-2005
• 四面変歌 Change 2005ー2010
74
Gandhi
• First they ignore you.
• Then they laugh at you.
• Then they fight you.
• Then you win.
75
Business process and Architecture
• Business process overview
• Functional Architecture
• Business process model
• Information Networking
• Telecom Operations Map
76
OpS Development on Ground Plan
77
Operations Process View NTT 1991
6
78運転系 OpS Architecture
79
Performance OpS Architecture
User OpS
Service OpS
Leased line service OpS
Leased line NE
Common NE for Services
Traffic OpS
Network Management OpS
Path Network OpS
Path NE OpS
NodeOpS
I-OpS
S-OpS
U-OpS
Network OpS
80
Functional Service ArchitectureSTBSTB PCPC TelephoneTelephone CPNCPNClient
Layer
Service ApplicationLayer
Service ControlLayer
TrailLayer
MediumLayer
PDAPDA MobileMobile
POTSPOTS VODVOD ConferenceConference xSPxSP ININ
access/callcontrol
access/callcontrol
connectioncontrol
connectioncontrol
configurationcontrol
configurationcontrol
sessioncontrol
sessioncontrol
QoScontrol
QoScontrol
SONETSONET SDHSDH FDDIFDDI WLLWLL xDSLxDSL PONPON FWAFWAWDMWDM
OpticalOptical COXCOX pairpair RadioRadio
81Basic Architecture of OpS on Execution Plane
Maintenance OperationService Order Planning
Customer
NE
Operation Services
Service Front( SF)
Bach Yard( BY)
NEOperation
Operations Function
82ResourceResource
Resource faced Operation
AM : Account ManagementSO : Service OrderPM : Performance ManagementTM : Trouble ManagementRP : Resource Provisioning
Basic Process and Process Components
TM PM SO
AM
RP
Mediation
Customer
Customer faced Operation
83
Operations Networking
84
Networking?
• Pattern 1 : No Information• Pattern 2 : No Deliverable Information• Pattern 3 : Delayed Information• Pattern 4 : Timely Information
Create Deliver Receive Apply/React
85
86
87
TOM : Telecom Operations Map TOM : Telecom Operations Map A Service Management Business Process ModelA Service Management Business Process Model
(TMF : TeleManagement Forum 1995)(TMF : TeleManagement Forum 1995)http://www.tmforum.orghttp://www.tmforum.org
Customer Care Process
SalesOrder
HandlingProblemHandling
CustomerQoS
Management
Invoicing/Collections
Service Development and Operations Processes
ServicePlanning/
Development
ServiceConfiguration
ServiceProblem
Resolution
ServiceQuality
Management
Rating andDiscounting
Network and Systems Management Processes
NetworkPlanning/
Development
NetworkProvisioning
NetworkInventory
Management
NetworkMaintenance& Restoration
Network DataManagement
Customer Interface Management Process
Customer
Physical Network and Information Technology
InformationSystemsManagementProcesses
Element Management Technology Related
ServiceManagement
NetworkManagement
88
Example of TOM Spider Chart--Network Provisioning--
89
CustomerInterface
Management
OtherProvider(s)
CustomerInterface
Management
ServiceConfiguration
Sales
Customer QoSManagement
OtherProvider(s)
Service ProblemManagement
Rating andDiscounting
INPUTS OUTPUTS
Problem Handling
• Receive Trouble Notification
• Determine cause & resolve/refer
• Track progress of resolution
• Initiate action to reconfigure, if needed
• Generate trouble tickets to Providers
• Confirm trouble cleared
•Notify customer when trouble cleared
• Schedule with and notify customer of planned work
CustomerCustomer
OrderHandling
ServiceConfiguration
Service ProblemManagement
Customer QoSManagement
Service QualityManagement
Trouble Reports
QoS and SLA TermsProfiles
CompletionNotification/Detail
Trouble TicketTrouble Cleared
Trouble Ticket, TroubleCleared, Planned Maintenance
SLA violations, PlannedMaintenance, Scheduling &Notification
QoS Violations
Problem Reports
Request to Re-configure
Trouble-tickets
Trouble Tickets
SLA/QoS Violations,Trouble Tickets
Major Trouble TicketNotification
Notofications (e.g. Problem and ResolutionNotifications) Trouble Tickets, Status Reports
Example of TOM Spider Chart – Problem Handling --
90
Service Assurance Process Flow
Service ProblemResolution
Service QualityManagement
2. reportdegradation
8. reportproblemdata
9. SLAimpact
to FulfilmentProcesses
Problem Handling
7. trouble report (Trouble Ticket)
customeralert(TT)
(SLA rebate, etc)
to BillingProcesses
3. (Network(Re) Configuration)
Monitor SLAs
Report
Network DataManagement
1.network data
Network InventoryManagement
AllocateResources
DetermineSLA Violations
Network Maintenance& Restoration
DecideRepair
TestIsolateRoot
Cause
5.notifyproblem/fix
10. serviceimpact
Detect Fault
DetectPerf/TrafficProblems
1.alarm/event data
4.Workorder
6. (Service(Re) Configuration)
DecideRepair
Network Element Management & Network Elements
Other Providers
Customer QoSManagement
Key: Activities
Processes
Cross FAB Process I/f
Inter-process I/f
Inter SP process I/f
91
Cross-industry view of end-to-end processes
Customer
Networking equipment
Fulfillment
AssuranceBilling
OtherService
Providersor
NetworkOperators
92
Integration
• System Integration
• Migration plan
• Multi domain management
• Process Integration
93
Integration
• Integrated Products Portfolio
• System Integration
• Multi domain Management
• Process Integration
• Horizontal Integration
• Vertical Integration
94
TMN Layers and OSS Products Line
TMN Layers
BM
NM
EM
NM
CO
MM
ON
Fo
un
datio
nC
OM
MO
N F
ou
nd
ation EM FoundationEM Foundation
NM FoundationNM Foundation
OSS Products Line
SM
-NM
TR NEs SW NEs AC NEs
TR AC
SM FoundationSM Foundation
/SW
-SM
Ex.Q3/IDL interface
Ex.Q3/IDL interface
EMEM
Network Elements
95
Integration !!
・・ Why?Why? Enterprise Policy and StrategyEnterprise Policy and Strategy
・・What?What? Process, Function,Process, Function,System, Domain, System, Domain,
GUI, etc.GUI, etc.
・・ How?How? DPEDPE( Distributed Process Engineering)( Distributed Process Engineering)
96
Simplified Value Chain
Provider
Customer
SP1
Provider
Customer
SP2
Supplier
InternalProvider
Customer
Customer
End Users End-to-End Service Management
Service Provider 1
Service Provider 2
Customer
Customer Management
Service Management
Network Management
NE Management
(b) Telecommunication Management Chain
Customer Management
Service Management
Network Management
NE Management
User Management
Service Management
Network Management
NE Management
(a) Service Delivery Chain - A Simplified view
97
NE Mgmt.
NE Mgmt.
Path
Config.
Mgmt.
Path
Performance
Mgmt.
SwitchingNE Mgmt.
TrafficMgmt.
Circuit Config.Mgmt.
Circuit PerformanceMgmt.
Network Mgmt.
Service Mgmt.
Service Dedicated
Network Mgmt.
Customer Mgmt.
Service Mgmt.
POTS Service NEService
Dedicated NE
Customer Premises
NE
Example of ManagementPhysical Architecture End User
TrafficMgmt.
Service Provider
Transport NE Mgmt.
Transport NE
Customer
Network Mgmt.
Customer/SP
SM
NM
EM
NE
98
NM OS
System Integration
NE
MDF MDF
EM OS
NE
EM OS
NE
EM OS
NE
EM OS
MDSNMP
CMISE Proprietary
Standard NM/EM InterfaceCORBA/IDL
OS:Operations SystemMDF:Mediation Device Function
99
Case 3Add Mediation
Ex. CORBA IDL
SNMP
yyy www
CMIP Etc.. XXXX ZZZZ
YYYY WWW
Library
= Mediation Function
Case 1Mediation Box (Adaptor)
Case 2Plug & Play Mediation
Case 4Add Mediation
NMS(Integrator)
EMS EMS EMS
Scenarios for Mediation/Migration
100
SW ASW B
SDHPDH
Ethernet FDDIPON ADSL
WLL
Access Service DM E-E Service DM BackboneService DME-E NW DM
CPN NWDM
Access NWDM BackboneNWDM
PathNWDM SW NEDM
DM: Domain Management
Agent for Upper DM
Domain Manager
Multi Domain Management
101
Functional Service ArchitectureSTBSTB PCPC TelephoneTelephone CPNCPNClient
Layer
Service ApplicationLayer
Service ControlLayer
TrailLayer
MediumLayer
PDAPDA MobileMobile
POTSPOTS VODVOD ConferenceConference xSPxSP ININ
access/callcontrol
access/callcontrol
connectioncontrol
connectioncontrol
configurationcontrol
configurationcontrol
sessioncontrol
sessioncontrol
QoScontrol
QoScontrol
SONETSONET SDHSDH FDDIFDDI WLLWLL xDSLxDSL PONPON FWAFWAWDMWDM
OpticalOptical COXCOX pairpair RadioRadio
102
Domain
Service Domain
Functional Domain
System Domain
NE Domain
Vender Domain
Area Domain
Access, Backbone, CPN
PON, ADSL, SDH, PDH
SW, Transmission, Cable, Power
A Vendor, B Vendor,,,
POTS, ISDN, Leased Line,FR, ATM
Metropolitan, Northern Area,,,
Example of Domain Definition
Example
103
Process Integration (Conventional)
DB
DB
APAP APAP APAP
APAP DB DB
APAPWF
= Work Flow Function WF
WF
WF
WF WF
APAPWF
APAPWF
104
Process Integration (Today)
DB
DB
APAP APAP APAP APAP
WFEWFE
APAP APAP
WFEWFE
DB DB
- Directory- Interface Conversion- Logical Gate AND/OR Split Multicast- Correlation, Filtering . . .
APAP
PolicyManagement
PolicyManagement
WFE : Work Flow Engine WFE : Work Flow Engine
105
Communications Technology Services
Process FlowEngine
FS FS FS FS FS
BAC BAC BAC BAC
Process DefinitionTool
Process FlowBAC: Business Aware ComponentFS: Framework Service
NGOSS FrameworkTM
NGOSS FrameworkNGOSS FrameworkTMTM NGOSS RegistryTM
NGOSS Shared Data ModelTM
106
Standardization
•De jure Standard•De facto Standard
STO : Standardize Organization
Copyright © FUJITSU LIMITED, 1998
107
Structure of De facto STD.
Copyright © FUJITSU LIMITED, 1998
TeamworkPartnership
TeamworkPartnership
CooperationCooperationAllianceOEM
AllianceOEM
M & AM & A
“best-in class”Solution
BilateralNon Disclose
•ISO, ITU-T etc.•Industry Consortium
CompetitionCo-ProsperitySurvival
OEM : Original Equipment ManufacturingM&A : Merger and Acquisition
108
Teamwork• ITU-T• ISO :International Organization for Standardization• TM Forum• OMG : Open Management Group• OASIS : Organization for the Advancement of Structured Information
Standards• ECMA : European Computer Manufacturers Association• ATIS : Alliance for Telecommunications Industry Solutions• ETSI : European Telecommunications Standards Institute • TISPAN : Telecommunications and Internet converged Services and
Protocols for Advanced Networking• IETF : Internet Engineering Task Force• W3C : World Wide Web Consortium• OSS/J : OSS Java• 3GPP, 3GPP2 : 3rd Generation Partnership Project
Copyright © FUJITSU LIMITED, 1998
109
Alliance/Partner
Copyright © FUJITSU LIMITED, 1998
A
B
C
(1) (2)
A社
B社 C社Capital Coalition
Competition
Products
Competition
Products
Competition
110
TMF DirectionTMF Direction
• Interoperable OSS: as the de-facto standard.– Multi-Service Providers, Vendors, Technologies, .…– Common Business process and Components
• Source of new technologies for OSS developments. – COTS, CORBA, XML, SOAP, JINI, …
• International Promotion for OSS products. – Catalyst Showcase , Product Expo…
111
TMF Consensus
• Web/Javauser interface
• CORBA to link business application
• SNMP manage the network
Copyright © FUJITSU LIMITED, 1998
112
TMF Products
• TMN/C++API– TMN AP Development Environment– GDMO/C++ Information Model API– CMIS/C++ Protoco l ; API– ASN.1/C++ ASN.1 API
• A CORBA-CMIP-SNMP Inter-working– CMIP/GDMO to CORBA IDL
– CORBA IDL to CMIP/GDMO– SNMP MIB to CORBA IDL
Copyright © FUJITSU LIMITED, 1998
113
Members’ Target of TMF ActivitiesMembers’ Target of TMF Activities
•Products Promotion Proof of Interoperability Products Exhibitionby•Obtaining New Technologies and Know-how Business Process
Software Architecture, COTS, PnP •Establishing Partnership/Networks
Service Providers ISVs, System Integrators, OSS vendors
114
NOMS : Network Operation and Management Symposium IEEE/IFIP(every even year)IM : Integrated Management IFIP/IEEE(every odd year)DSOM : Distributed Systems Operation and Management IFIP/IEEE(every year)IPOM : International Work Shop on IP Operations and Management IEEE ( every year)MMNS : International Conference on Management of Multimedia Networks and Services IFIP/IEEE(every year)
Asia-Pacific AreaAPNOMS : Asia-Pacific Network Operations and Management Symposium IEICE,Japan KNOM,Korea (every year)
Academic Activitieshttp://www.comsoc.org/