Transcript TMN - Catatan Hasdi Putra

POSTEC Lecture
Network Management
Chapter 2 Architecture and Business Process
March18-April 10, 2008
Masayoshi Ejiri
Japan
1
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
- Standardization
3. 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 negotiation
5, IP/eBusiness Management
- Paradigm shift , Architecture beyond TMN and enhanced TOM
6. NGN( Next Generation Networks) Management
- NGN Networks and Services , New Paradigm of ICT Business and
Management
2
OSS Development
-Individually without Ground PlanNetwork OpS
Free Dial
Traffic
DDX Network
ISDN
Network
OpS
OpS
OpS
MassCalling
Service OpS
Personal
Phone
Mobile
OpS
OpS
OpS
OpSOpS
OpS
OpS
ISDN Services
OpS
OpS
OpS
DDX Services
OpS
OpS
Information Transmision
OpS Leased Line
Network
Services
NE OpS
OpS
OpS
OpS
NE
Switching
OpS=OSS
OpS
OpS
OpS
OpS
OpS
OpS
OpS
OpS
OpS
NE
NE
NE
Transmission
Cables
Power Supply
3
New Gen. Plug and Play Systems:
Current Implementation Architecture
• N2 Complexity
• New Services
hard
• Data Consistency
• Heavy messages
*Quote from TMF document
4
New Gen. Plug and Play Systems:
Program Principles to be Validated
WorkFlow
M1
...
M3
Mn
Bus
Common Bus
Component Applications
Workflow control
Directory
M2
D
i
r
e
c
t
o
r
y
Mn-1
*Quote from TMF document
5
Systematic OSS Development
마구만들고, 뿔뿔만들고, 내버려두다
“Haphazard, individual and No PDCA”
“Strategic, Cooperative and Lifecycle Care “
・Ground Plan/View of Operations
・Analysis not Process disordered Enumeration
Share common operations view, architecture and
business process
6
Trend of OSS
Development
Customers
Z company
A company
SP
DCN
Network OpS
DCN
NE OpS
Network
OpS
DCN
DCN
NE
OpS
Ops to supervise and
control NEs
Centralized OpS for
network management
Customer oriented
total OpS
7
Systematic Approach
•
•
•
•
Operations Overview
Functional Architecture
Business Process
Telecom Operations Map
by SMART Team ( Service Management Automation
and Reengineering Team)
8
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
9
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
aspects---NGN
Series X : Data networks and open system communications
Note : ITU-T Recommendation URL
http://www.itu.int/ITU-T/publications/recs.html
10
TMN Referenced Recommendation
• Telecommunication services : F-series Recs.
• Telecommunication network architecture and
components : I/Q/G-series-Recs.
• Communication protocol, services and messages : I/Q/Xseries-Recs.
• Telecommunication network management for traffic,
maintenance,provisioning and security : E/M-series-Recs.
• ISPs ,managed object naming and addressing : X-series
Recs.
11
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 : Q81xseries, Q82x-series, G773, Q94x-series
ISP : International Standardized Profile
12
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.
13
TMN(Telecommunications Management Network)
General Relationship
ITU-T Rec. M3010
14
TMN function blocks
M.3010
TMN
TF
OSF
TF
WSF
NEF
T0412990-99
NEF
OSF
TF
WSF
Network Element Function
Operation Systems Function
Transformation Function
Workstation Function
The TMN functional boundary
15
Reference points between management function blocks
TMN
g
g
WSF
WSF
f
f
TMN
f
q
x
OSF
OSF
q
q
q
OSF
q
q
q
q
NEF
NEF
TF
m
q, f, x, g, m
T0413010-99
16
Model for layering of TMN Management function
17
TMN Pyramid
BM
SLA View
SM
Technology Independent
View
NWM
Vendor Independent
View
NEM
18
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
19
TMN defines
•Architecture
Functional, Information ,Physical
•Management Layer : BM,SM,NM,NEM
•Management Functional Area: FCAPS
•Management Platform
•Management Information Model
•Management Applications
20
Interface
Common Language
Message
Process
Hand Shake
Flow & Timing
Protocol
Managed Object、
Information/Data Model
Process Management
Work Flow Engine
CMIP,SNMP,CORBA,tMN
21
TMN Simplified Physical Architecture
Rec. M3010, 2000
Operation System
(OS)
TMN
X/F/Q
F
X
G
Workstation
(WS)
Data Communication Network
(DCN)
Q
Q-Mediation Device
(QMD)
Q
Q
Q-Adaptor
(QA)
M
Q
Network
Element
(NE)
Network
Element
(NE)
22
TMN Physical Architecture
TMN
Service Level Integration for
Customers/Service Providers
Operation System
(OS)
Q3
F
X
Data Communication Network
(DCN)
Workstation
(WS)
Q3
Q3
Mediation Device
(MD)
Network Level Integration
Across Managed Area
Qx
Data Communication Network
(DCN)
Element Level Integration
within Managed Area
Qx
Q-Adaptor
(QA)
Modified Rec.M3010 1998
Network
Element
(NE)
Q-Adaptor
(QA)
Qx
Network
Element
(NE)
23
FCAPS
Rec. M3400
on 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
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
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
24
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
•
5.3 Performance Management Control
•
Network traffic management policy function
Subscriber service quality criteria function set
•
•
5.3.1
set
5.3.2
5.3.3
5.1.4
QOS performance assessment function set
•
5.3.4
Performance administration function set
•
5.1.5
Network performance assessment function set
•
•
5.3.5
5.3.6
Execution of traffic control function set
Audit report function set
•
5.1.6
NE(s) performance assessment function set
•
5.1.7
Data integrity check function set
5.2 Performance Monitoring
Traffic control function set
Traffic administration 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.2.1
•
•
•
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.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.2.5
5.2.6
Traffic status function set
Traffic performance monitoring function set
•
5.4.7
•
•
5.2.7
NE(s) threshold crossing alert processing
function set
5.2.8
NE(s) trend 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
•
•
•
Performance monitoring policy function set
5.2.9
Performance monitoring data accumulation
function set
5.2.10 Detection, counting, storage and reporting
function set
•
•
Traffic capacity analysis function set
NE(s) traffic capacity analysis function set25
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.
26
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
set
•
6.1.5
set
•
6.1.6
set
6.2 Alarm
6.2.6 Alarm event criteria function set
•
6.2.7 Alarm indication management
function set
6.2.8 Log control function set
•
•
•
Service outage reporting function
6.2.9 Alarm correlation and filtering
function set
6.2.10 Failure event detection and
reporting function set
Network outage reporting function
6.3 Fault localization
NE(s) outage reporting function
•
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
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
•
•
•
•
•
27
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
•
•
•
•
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
•
•
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.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)
•
•
6.6 Trouble administration
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
•
•
28
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
29
7. Configuration Management (2)
•
7.4.9
•
7.4.10 Access circuit 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.11
Leased circuit design function set
•
7.4.25 NE(s) inventory query function set
•
•
Facility design function set
Manage pending network changes function
•
•
7.4.12
7.4.13
set
7.4.14
set
7.4.15
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.4.16 Circuit inventory query function set
•
Interexchange circuit design function set
Network connection management function
Circuit inventory notification function set
7.4.17 NE(s) configuration function set
•
•
•
•
7.5 Status and control
•
7.4.18 NE(s) administration function set
•
7.5.1
Priority service policy function set
•
7.4.19 NE(s) database management function set
•
7.5.2
Priority service restoration 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.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
•
•
•
30
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
8.2.4
Costing function set
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
•
•
31
8.Accounting Management (2)
8.3 Collections and Finance
•
8.3.1
Planning of the billing process function set
•
Management of the billing process function
•
8.3.2
set
8.3.3
•
•
8.3.4
8.3.5
General ledger function set
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
•
8.3.12 Invoice assembly function set
General accounting operations function set
Human resources 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
8.4.2
8.4.3
Budgeting function set
Auditing function set
Cash management function set
•
•
•
•
8.4.4
8.4.5
8.4.6
8.4.7
Raising equity function set
Cost reduction function set
Profitability analysis function set
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
32
9. Security Management (1)
9.1 Prevention
9.3 Containment and Recovery
•
•
9.1.1
9.1.2
Legal review function set
Physical access security function set
•
•
•
9.1.3
9.1.4
Guarding function set
Personnel risk analysis function set
•
9.1.5
Security screening function set
Protected storage of business data function
•
9.3.1
set
9.3.2
•
9.3.3
Theft of service action function set
9.2 Detection
•
•
•
9.3.4
9.3.5
9.3.6
Legal action function set
Apprehending function set
Service intrusion recovery function set
•
•
Exception report action function set
•
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.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.2.4
set
9.2.5
set
9.2.6
Customer (external user) profiling function
•
9.3.10 Network intrusion recovery function set
Customer usage pattern analysis function
•
Investigation of theft of service 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.2.7
Internal traffic and activity pattern analysis
function set
9.2.8
Network security alarm function set
•
9.2.9
•
9.2.10 Support element security alarm reporting
function set
Software intrusion audit 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
33
9.Security Management (2)
9.4 Security Administration
•
•
•
•
9.4.1
9.4.2
Security policy function set
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.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
9.4.13 Customer security alarm management
function set
9.4.14 Testing of audit trail mechanism function
set
34
6.1.3 RAS assessment function set
This 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 requirements
This 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 Model
This 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 Functions
1)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.
35
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;
36
Examples of generic scenarios （１）
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
•
I.4
•
•
I.5
•
•
•
Work force management
I.3.1 Enterprise management (AM, FM, CM, SM)
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)
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)
37
Examples of generic scenarios （２）
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 administration
I.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)
38
Generic scenarios Ex. 1.2.1 : Network Provisioning Management
Capacity provisioning for new and/or existing services( CM, AM)
Network Planning and
Engineering
– Technology and supplier
policy
– Area boundary definition
– Infrastructure planning
– Management of planning
and engineering process
– Product line budget
Service Planning and
Negotiation
– Marketing
– Service planning
– Service feature
definition
1a
Accounting:
Tariffing/Pricing
– Pricing strategy
2
Status and Control
– Priority service policy
5
Provisioning
– Provisioning policy
– Material management policy
3
Installation
– Procurement
– Management of installation
– Contracting
– Real estate management
1c
Customer
6
4
Accounting:
Collections and Finance
– Accounts payable
1b
Network Planning and Engineering
– Demand forecasting
7
9
Network Planning and Engineering
– Network infrastructure design
– Access infrastructure design
– Facility infrastructure design
– Routing design
Service Planning and
Negotiation
– Customer service planning
– Customer service feature
definition
10
Status and Control
– Priority service
restoration
13
11
Installation
– Material management
– Network installation administration
– Scheduling and dispatch administration of installation force
14
12
Network Planning and Engineering
– NE(s) design
8
16
Installation
– Installation completion reporting
– NE installation administration
– Software administration
15
Installation
– Loading software into NEs
17
39
Generic scenarios Ex. 1.9.3 :Maintenance management
Fault localization ( FM,PM,CM)
Fault Localization
– Fault localization policy
Testing
– Test point policy
Configuration:
Provisioning
– Facility design
16
Fault Localization
– Verification of parameters
and connectivity
9
Performance:
Performance Monitoring
– Network performance monitoring
event correlation and filtering
2
Alarm Surveillance
– Failure event detection
and reporting
Fault Localization
– Network
18
fault localization
Testing
– Circuit selection,
test correlation
and fault location
– Selection of test suite
– Test access network
control and recovery
Trouble Administration
– Trouble ticket
administration
10
7
Alarm Surveillance
– Alarm reporting
– Log control
– Alarm summary
– Alarm correlation and
filtering
11
1
8
Alarm Surveillance
– Network fault event
correlation and filtering
12
17
14
6
3
Fault Localization
– NE(s) fault localization
4
13
Testing
– Test access configuration
– Test circuit configuration
– NE(s) test control
– Results and status reporting
– Test access path management
5
15
Fault Localization
– Running of diagnostic
Testing
– Test access
40
T0406770-96
Interface
• Unified Modeling Language
• OSI System Management
System Management Application
Management Information Architecture
Manager/Agent concept
Managed Object
Management Information Services
41
Interface specification methodology
Rec. 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 )
42
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
43
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 “
44
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
activities “
• Component Diagrams
“Show physical unit of software/hardware and mutual
dependency“
• Deployment Diagrams
“ Show physical configuration of software/hardware “
45
M.3020 – Customer Administration of LCS Use Case
service customer
Customer Admin LCS
<<include>>
service provider
<<include>>
<<include>>
T0412320-99
Service Provisioning
Maintenance
Trouble Administration
LCS : Leased Circuit Service
46
M.3020 – Service Provisioning Use Case for CNM of LCS and Link Connections
service customer
service Provisioning
<<include>>
Configure LCS
<<extends>>
service provider
<<include>>
Link Configuration Function Set
<<extends>>
T0412330-99
LCS administrative Function Set
Link administrative Function Set
47
M.3020 – Decomposition of LCS Configuration Function Set Use Case
service customer
Configure LCS
<<include>>
Create LCS
<<include>>
Delete LCS
service provider
<<include>>
Modify LCS
<<extends>>
<<extends>>
<<extends>>
<<extends>>
T0412340-99
Cancel LCS Request
Invalid Parameters Encountered
48
M.3020 – Sequence diagram: Successful creation of service
service request
created if input valid
: service customer
: service provider
[input valid] new
service request
service request
(subclass)
service
(subclass)
[accept request]: create
response service request
[input valid]: create response
(accepted/modified input
parameters)
[invalid input]: create
request reject
modify request of service request parameters
response to modify (accepted/modified/reject)
report service request state/parameter value changes
report service creation
T0412380-99
49
Collaboration diagram: Successful creation of service
Rec. M3020
3:
4:
Service
Customer
Service
Provider
1:
6:
7:
8:
2:
5:
Service
Request
1: new service request
2: valid request, service request created
3: valid input parameters, respond with
service request creation
4: invalid request parameters, respond with
service request failure
5: modify service request
6: respond to modify service request
( accept/modify/reject)
7: report request state/parameter change
8: service creation report
Service( subclass)
50
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
51
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.
52
OSI System Management Overview
System Management
Managed System
Manager
Operations
Managing
Process
Agent
Process
Managed Objects
( MIB)
Notification
Resource
53
System management interaction,
Information and OSI Communications aspect
Managed open system
Communicating
MIS-User
(manager role)
Access
control
Performing
management
operations
Management operations
Notifications
Notification
dissemination
MIS-User
(agent role)
Notifications
emitted
Managed
objects
TISO0030-92/d03
Rec.X701
MIS : Management
Information
Figure 3 – Communication
support for notifications
and Service
managements operations
54
Relationship between information and communications aspect
Systems management application process
Mapping to standardized communication
Application
Presentation
Session
Local
mapping
Transport
Network
Data-link
Physical
Systems managed objects
(N)-layer managed objects
OSI environment
Local environment
TISO0020-92/do2
Managed object
Containment hierarchy of managed objects
Systems management information model space
Rec.X701
Use standardized OSI management communication
Figure 2 – Relationship between information and communication aspects
55
Manager/Agent Relationship
Customer
Manager
SM.
Agent
Manager
Agent
Agent
Manager
NM.
Manager
EM.
Agent
Manager
Agent
Manager
Agent
Manager
NE
A/M
NE
A/M
NE
A/M
NE
A/M : Agent/Manager
56
Agent Role
Manager
Q3
Communication
(Access Control, Notification Dissemination)
Object Representation
Agent
(Perform Operation, Emit Notification)
Adaptation
Resource
57
Manager Role
Operator/
Application
Manager
Communication
Object
Representation
Agent ??
Management Application
Manager
Interface
Q3
Agent
58
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
59
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
60
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
61
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
62
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 )
63
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
64
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
65
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
66
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
67
SNMP messages
•
•
•
•
•
Get-Request
Get-Response
Get-Next-Request
Set-Request
Trap
68
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
69
Shared management knowledge
Rec.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)
70
System management Organizational aspect
Management
Policy
Policy
semantics
Management
Domain
Management
Jurisdiction
Domain
Membership
( Managed objects)
Rec. X701
71
ve together in partnership.
TMN Implementation
Map to an implementation
The constraints between:
– Cost
– Performance
– Time to Market
– Availability/Reliability
– Existing Deployment
72
Telecommunications Management Network
--20 years with TMN --
• 四面無歌 Ignored
１９８５－１９９０
• 四面楚歌 Objection １９９０－１９９５
• 四面謳歌 Enjoy
• 四面変歌 Change
１９９５－２００５
２００５ー２０１０
73
Gandhi
•
•
•
•
First they ignore you.
Then they laugh at you.
Then they fight you.
Then you win.
74
Business process and Architecture
•
•
•
•
•
Business process overview
Functional Architecture
Business process model
Information Networking
Telecom Operations Map
75
OpS Development on Ground Plan
76
Operations Process View
NTT 1991
77
6
運転系OpS Architecture
78
Performance OpS Architecture
U-OpS
User ＯｐＳ
Service ＯｐＳ
S-OpS
Leased line service ＯｐＳ
Network Management ＯｐＳ
I-OpS
Leased line ＮＥ
Network ＯｐＳ
Traffic
ＯｐＳ
Node Path Network ＯｐＳ
ＯｐＳ
Path NE OpS
Common NE for Services
79
Functional Service Architecture
Client
Layer
Service
Application
Layer
Service
Control
Layer
Trail
Layer
Medium
Layer
STB
PC
PDA
POTS
VOD
access/call
control
connection
control
WDM SONET
Optical
SDH
Telephone
Conference
configuration
control
FDDI
COX
WLL
pair
Mobile
CPN
xSP
IN
session
control
QoS
control
xDSL
PON
FWA
Radio
80
Customer
Operation Services
Operations Function
Service Front
（SF)
Maintenance Operation
Service
Order
Planning
Bach Yard
（BY)
NEOperation
NE
Basic Architecture of OpS on Execution Plane
81
Basic Process and Process Components
Customer
TM
PM SO
AM
Customer faced Operation
Mediation
RP
Resource
Resource faced Operation
AM : Account Management
SO : Service Order
PM : Performance Management
TM : Trouble Management
RP : Resource Provisioning
82
Operations Networking
83
Networking?
Create Deliver Receive Apply/React
•
•
•
•
Pattern 1 : No Information
Pattern 2 : No Deliverable Information
Pattern 3 : Delayed Information
Pattern 4 : Timely Information
84
85
86
TOM : Telecom Operations Map
A Service Management Business Process Model
(TMF : TeleManagement Forum 1995)
http://www.tmforum.org
Customer
Customer Interface Management Process
Sales
Service
Management
Order
Handling
Problem
Handling
Customer
QoS
Management
Invoicing/
Collections
Customer Care Process
Service
Planning/
Development
Service
Configuration
Service
Problem
Resolution
Service
Quality
Management
Rating and
Discounting
Information
Systems
Management
Processes
Service Development and Operations Processes
Network
Management
Network
Planning/
Development
Network
Provisioning
Network
Inventory
Management
Network
Maintenance
& Restoration
Network Data
Management
Network and Systems Management Processes
Element Management Technology Related
Physical Network and Information Technology
87
Example of TOM Spider Chart
--Network Provisioning--
88
Example of TOM Spider Chart – Problem Handling -INPUTS
Customer
Customer
Interface
Management
Notofications (e.g. Problem and Resolution
Notifications) Trouble Tickets, Status Reports
Trouble Reports
Order
Handling
Problem Handling
QoS and SLA Terms
Profiles
• Receive Trouble Notification
Completion
Notification/Detail
Service
Configuration
Customer
OUTPUTS
Customer
Interface
Management
Major Trouble Ticket
Notification
Sales
Problem Reports
Customer QoS
Management
• Determine cause & resolve/refer
• Track progress of resolution
Other
Provider(s)
• Initiate action to reconfigure, if needed
Trouble Ticket
Trouble Cleared
Service
Configuration
Request to Re-configure
• Generate trouble tickets to Providers
Service Problem
Management
Trouble Ticket, Trouble
Cleared, Planned Maintenance
• Confirm trouble cleared
•Notify customer when trouble cleared
• Schedule with and notify customer of
planned work
Customer QoS
Management
Trouble Tickets
SLA violations, Planned
Maintenance, Scheduling &
Notification
Service Quality
Management
Other
Provider(s)
Trouble-tickets
QoS Violations
SLA/QoS Violations,
Trouble Tickets
Service Problem
Management
Rating and
Discounting
89
Service Assurance Process Flow
customer
alert(TT)
10. service
impact
Problem Handling
Customer QoS
Management
Determine
SLA Violations
Report
7. trouble report
(Trouble Ticket)
6. (Service
(Re) Configuration)
to
Fulfilment
Processes
4.Work
order
Network Inventory
Management
Allocate
Resources
8. report
problem
data
Service Problem
Resolution
Decide
Repair
5.notify
problem/fix
Key:
Activities
Service Quality
Management
Monitor SLAs
Processes
Cross FAB Process I/f
Inter SP process I/f
Other Providers
Network Maintenance
& Restoration
Detect
Fault
9. SLA
impact
to Billing
Processes
Inter-process I/f
Decide
Repair
3. (Network
(Re) Configuration)
(SLA rebate,
etc)
Test
1.alarm/event data
Isolate
Root
Cause
2. report
degradation
Network Data
Management Detect
Perf/Traffic
Problems
1.network data
Network Element Management & Network Elements
90
Cross-industry view of end-to-end
processes
Customer
Fulfillment
Assurance
Billing
Other
Service
Providers
or
Network
Operators
Networking equipment
91
Integration
•
•
•
•
System Integration
Migration plan
Multi domain management
Process Integration
92
Integration
•
•
•
•
•
•
Integrated Products Portfolio
System Integration
Multi domain Management
Process Integration
Horizontal Integration
Vertical Integration
93
TMN Layers and OSS Products Line
-SM
SM
NM
EM
COMMON Foundation
BM
SM Foundation
-NM
Ex.Q3/IDL interface
NM Foundation
TR
AC
Ex.Q3/IDL interface
/SW
EM Foundation
Network Elements
TR NEs
TMN Layers
SW NEs
AC NEs
OSS Products Line
94
Integration !!
・Why?
Enterprise Policy and Strategy
・What?
Process, Function,
System, Domain, GUI, etc.
・How?
DPE( Distributed Process Engineering)
95
Simplified Value Chain
User Management
Customer Management
Service Management
Customer Management
Network Management
NE Management
Service Management
Network Management
Network Management
NE Management
Customer
Service Management
NE Management
Service Provider 1
(b) Telecommunication Management Chain
Service Provider 2
Customer
Internal
Provider
SP1
SP2
Provider
Provider
Supplier
Customer
End Users
Customer
Customer
End-to-End Service Management
(a) Service Delivery Chain - A Simplified view
96
Example of Management
Physical Architecture
Customer
End User
Customer Mgmt.
SM
Service Mgmt.
Service Mgmt.
Network Mgmt.
Service Dedicated
Network Mgmt.
Network Mgmt.
NM
Circuit Config.
Mgmt.
Traffic
Mgmt.
EM
NE
Circuit Performance
Mgmt.
Path
Config.
Mgmt.
Switching
NE Mgmt.
POTS Service NE
Path
Performance
Mgmt.
Transport NE Mgmt.
Transport NE
Service Provider
Traffic
Mgmt.
NE
Mgmt.
Service
Dedicated NE
NE
Mgmt.
Customer Premises
NE
Customer/SP
97
System Integration
NM OS
Standard NM/EM Interface
CORBA/IDL
MDF MDF
SNMP
MD
CMISE
Proprietary
EM OS
EM OS
EM OS
EM OS
NE
NE
NE
NE
OS:Operations System
MDF:Mediation Device Function
98
Scenarios for Mediation/Migration
Case 2
Plug & Play Mediation
NMS
(Integrator)
= Mediation
Function
Case 4
Add Mediation
Ex. CORBA IDL
SNMP CMIP
Case 1
Mediation Box (Adaptor)
yyy
YYYY
EMS
XXXX
Etc..
ZZZZ
Case 3
Add Mediation
Library
www
WWW
EMS
EMS
99
Multi Domain Management
Access Service DM
E-E Service DM
Backbone
Service DM
E-E NW DM
CPN NWDM
Backbone
NWDM
Access NWDM
Path
NWDM
WLL
Ethernet FDDI
PON
SW NEDM
ADSL
SDH
DM: Domain Management
PDH
SW A
SW B
Agent for Upper DM
Domain Manager
100
Functional Service Architecture
Client
Layer
Service
Application
Layer
Service
Control
Layer
Trail
Layer
Medium
Layer
STB
PC
PDA
POTS
VOD
access/call
control
connection
control
WDM SONET
Optical
SDH
Telephone
Conference
configuration
control
FDDI
COX
WLL
pair
Mobile
CPN
xSP
IN
session
control
QoS
control
xDSL
PON
FWA
Radio
101
Example of Domain Definition
Domain
Example
Service Domain
POTS, ISDN, Leased Line,
FR, ATM
Functional Domain
Access, Backbone, CPN
System Domain
PON, ADSL, SDH, PDH
NE Domain
SW, Transmission, Cable, Power
Vender Domain
A Vendor, B Vendor,,,
Area Domain
Metropolitan, Northern Area,,,
102
Process Integration (Conventional)
AP
AP
WF
AP
WF
AP
WF
WF
DB
WF
AP
WF
DB
AP
WF
DB
DB
AP
WF = Work Flow Function
103
Process Integration (Today)
AP
AP
AP
AP
DB
Policy
Management
AP
WFE
DB
Policy
Management
WFE
AP
AP
DB
DB
WFE : Work Flow Engine
- Directory
- Interface Conversion
- Logical Gate AND/OR Split Multicast
- Correlation, Filtering . . .
104
NGOSSTM Registry
TM
NGOSS Framework
NGOSS TM Shared Data Model
Process Definition
Tool
BAC
BAC
BAC
BAC
Communications Technology Services
Process Flow
Engine
FS
FS
FS
FS
FS
NGOSSTM Framework
Process Flow
BAC: Business Aware Component
FS: Framework Service
105
Standardization
•De jure Standard
•De facto Standard
STO : Standardize Organization
106
Copyright © FUJITSU LIMITED, 1998
Structure of De facto STD.
Teamwork
Partnership
•ISO, ITU-T etc.
•Industry Consortium
“best-in class”
Solution
Alliance
OEM
Competition
Co-Prosperity
Survival
Cooperation
Bilateral
Non Disclose
M&A
OEM : Original Equipment Manufacturing
M&A : Merger and Acquisition
Copyright © FUJITSU LIMITED, 1998
107
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
108
Copyright © FUJITSU LIMITED, 1998
Alliance/Partner
(1)
(2)
Competition
A
Ｃ社
Ｂ社
Capital
Coalition
Competition
B
Products
Products
Competition
C
Ａ社
109
Copyright © FUJITSU LIMITED, 1998
TMF 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…
110
TMF Consensus
• Web/Java user interface
• CORBA
to link business application
• SNMP manage the network
111
Copyright © FUJITSU LIMITED, 1998
TMF Products
• TMN/C++API
–
–
–
–
TMN AP Development Environment
GDMO/C++ Information Model API
CMIS/C++
Protocoｌ; 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
112
Copyright © FUJITSU LIMITED, 1998
Members’ Target of TMF Activities
•Products Promotion
Proof of Interoperability
Products Exhibition
by
•Obtaining New Technologies and Know-how
Business Process
Software Architecture, COTS, PnP
•Establishing Partnership/Networks
Service Providers
ISVs, System Integrators, OSS vendors
113
Academic Activities
http://www.comsoc.org/
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 Area
APNOMS : Asia-Pacific Network Operations and Management
Symposium
IEICE,Japan KNOM,Korea (every year)
114