new technologies for nm n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
New Technologies for NM PowerPoint Presentation
Download Presentation
New Technologies for NM

Loading in 2 Seconds...

play fullscreen
1 / 22

New Technologies for NM - PowerPoint PPT Presentation


  • 59 Views
  • Uploaded on

New Technologies for NM. Where are we heading in ITU and other Fora ?. Overview. Technology Dimensions for NM Business drivers and goals impacting Network Management Architectures for NM support Logical and Physical representations Network Management Architectural Choices – wxample

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'New Technologies for NM' - lel


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
new technologies for nm

New Technologies for NM

Where are we heading in ITU and other Fora ?

overview
Overview
  • Technology Dimensions for NM
  • Business drivers and goals impacting Network Management
  • Architectures for NM support
    • Logical and Physical representations
    • Network Management Architectural Choices – wxample
  • Implementation considerations for Network Management SW
    • Interoperability at protocol and application levels
    • Protecting current investments with future proof considerations
    • Addressing market drivers
    • Initiatives with APIs and Model Driven Architecture
  • Conclusions
nm technology dimensions
NM Technology Dimensions
  • Architectural choices
    • Levels of Management Systems required
    • Distribution of functions across NM systems
    • How and where to store NM data and the stewards for data
  • Interoperability Choices
    • What protocols to be used across different interfaces between management systems
    • Coordination between control plane and management plane as is necessary with ASON services
    • Management information communicated across the interfaces and their representation
  • Semantics and Syntax of Informatio
    • Syntax depends on the protocol choice
    • Semantics derived from Information Models
business drivers and goals infrastructure
Business Drivers and Goals Infrastructure
  • Integrated Operations Support Systems
  • Flow through provisioning
  • Integrated customer care
  • More customer control
  • Interfaces to service providers of varying sizes
  • Reduced time to resolve troubles
  • Seamless management of different access, and core technologies
  • Maintaining quality of service for services with varying characteristics
architectural considerations goals and strategies
Architectural ConsiderationsGoals and Strategies
  • Operations Architecture
    • Use of multi-supplier Network Elements (NEs) and Element Management Systems (EMSs)
    • Element Management Layer (EML) approaches that support supplier independence to network and service management layers
    • Cross-technology domain management
  • Customer Interface Management
    • Electronic communications interfaces to other carriers and customers to support electronic commerce
    • Integrated customer contact and customer care services
architectural implications
Architectural Implications
  • Information Architecture
    • Use of the network as an ultimate source of inventory data
    • Corporate data as an asset and stewardhip
  • Physical (Implementation) Architecture
    • Integration of legacy OSSs
    • Use of commercial off the shelf OSSs and applications
    • Open standard interoperable interfaces where appropriate and practical
    • Design and/or procurement of new OSSs consistent with business drivers
    • OSSs built on specified/approved computing platforms
nm architectural choices hybrid circuit and packet network example
NM Architectural ChoicesHybrid Circuit and Packet Network Example

Layer Domain

Switched services

Circuit

-

switched

Architecture

IP services

IP

ATM

Private line

(DS1, DS3) services

SDH

SDH

STM

-

N services

MS SPRING (BLSR)

or UPSR

OTN

l

services

OTN

ATM

Physical

XC

Sw.

OTN

OTN/SDH

OTN

Architecture

ADM

XC

XC

POTS

Mesh physical

Sw.

topology

Optical rings in

other domains

OTN

OTN

OTN/SDH

XC

/ATM XC

XC

IP

SDH

Rtr.

IP

ATM

POTS

DCS

Rtr.

Sw.

Sw.

From ITU Recommendation M.3017

ason a next generation network feature
ASONA Next Generation Network Feature
  • Features (G.8080)
    • Configure to support fast set up of switched and soft permanent connections
    • Reconfiguration for previously set up calls
    • Restoration
  • Some traditional NM Functions performed by control plane signaling
    • Path set up
    • Automatic Discovery of links
    • Routing related functions
  • Control Plane and Management Plane coordination necessary for reliable and smooth operation of network

CP

MP

management of hybrid networks one example approach
Management of Hybrid NetworksOne Example Approach

Service Management System

Interface

Network Management System

Element Management

System

Interworking NE

Circuit NE

Packet NE

ITU Recommendation M.3017

slide11

TMN

ATM

SDHRing

CNM

CORBA

USHR

Home

Banking

DWDM

OTN

XML/

/Web services

Directory

HFC

Virtual

Reality

Electronic

Commerce

ADSL

DCE

HTTP

Multiple Technology Choices and Trends

Transport

Middleware

Applications

Java

DCOM

/ OLE

Web

Hosting

TCP/IP

No more specific to Telecom world alone

nm protocol interoperability evolution
NM Protocol Interoperability Evolution

XML/web services

CORBAGIOP/IIOP with IDL

CMIP with GDMO/ASN.1

SNMP V1,V2,V3, MIB

TL1, FCIF (MML based)

Proprietary

1980

1984

1990

1999

2003

Second Law of Thermodynamics Prevails

what is information modeling
What is Information Modeling?
  • Schema definition as a result of system analysis
  • Identification of entities (objects), relationships and operations
  • Model of a system as seen by the external view without internal implementation details
  • Techniques used include Entity Relationship, Object Oriented
evolving methodology for nm specifications
Evolving Methodology for NM Specifications
  • Initial Goal of TMN to use a single management protocol is no longer true
  • The management information model must be resilient to changes in the interface paradigm
  • Requirements Traceability is critical for good understanding between domain expert and protocol/modeling SW experts
  • UML has become the de-facto standard based on its visual modeling easy to understand features, power of expression and commercial availability of tools
uml mechanisms for modeling
UML Mechanisms for Modeling
  • Inheritance
  • Relationships
  • Navigation
  • Constraints and Comments
  • Stereotypes
  • Type and Implementation Classes
  • Interfaces
  • Associations
  • State
  • Packages
application level interoperability ngoss tmf framework
Application Level interoperabilityNGOSS (TMF) Framework

Components

Framework Services

Business Services

Contracts

Basic Framework

Policy Framework

Distribution Support

Business Service Support

  • Naming
  • Trading
  • Invocation
  • Shared information
  • Transaction Processing
  • Process Management
market drivers
Market drivers
  • Shorter time to market and faster return on investment
    • Reduced Development time and Efforts
  • Performance and Scalability
  • Robustness and Reliability
  • Creation of applications that function across multiple networks
    • Write once, run anywhere, any network, by any one
  • Faster Development and Integration of OSS/BSS solutions
  • Standardize infrastructure services for distributed environment
    • Focus on application logic
addressing market drivers for nm what is to be protected
Addressing Market Drivers for NMWhat is to be protected?
  • Facts to reconcile with…
    • Management interface protocols will change
    • Redefining management information to suit the protocol will become expensive
    • Time to market for services will reduce to grow the business
    • Maintaining redundant information with slight differences will become resource intensive
  • Wrapper changes should not require data redefinition
    • Modeling information can counter these issues to a large extent

Key Resource = Corporate Data

industry initiatives
Industry Initiatives
  • API Specifications supporting
    • Service Creation (Parlay, JAIN™ etc.)
    • OSS/J built on J2EE
  • Architectures for integration back end systems
    • JCA and technology specific support for CORBA and SNMP
    • APIs for OSS/J applicable for multiple technologies
  • Model Driven Architecture
    • An OMG driven approach gaining interest in developing OSSs
mda what and why
MDA what and why
  • Why move away from APIs?
    • Inflexibility with tight integration of business process and API
    • Difficult to respond rapidly to changing requirements and technology
    • Middleware proliferation (CORBA,Java/EJB,XML/SOAP…)
    • Need an Architecture and Infrastructure that can survive changes and future technology evolutions in SW development
  • What is MDA?
    • Separates business process and application logic
    • Higher level of abstraction than APIs
    • Built on Object Oriented Modeling Approach of UML OO modeling and Design Patterns
    • Code Generation Tools and Repository reduces development time
    • Enhancements achieved without requiring major changes to existing infrastructure and business processes
    • Technology and API decisions can be deferred to later
mda deployment scenario
MDADeployment Scenario

Platform

Independent

Model (PIM)

Mapping to multiple

Deployment

Middleware technologies

PSM

CORBA

Java/EJB

XML/SOAP

Next New

Platform

Technology Independent representation of business

conclusions
conclusions
  • NM spans
    • Service creation
    • Service Assurance
    • Service Maintenance
    • Amidst multiple new technologies with fixed and mobile, with circuit and packet environments
  • Goals for New Technologies in Network Management
    • Preserving business processes and application logic offers future proof for service providers
    • Agility in development and deployment to achieve increased ROI
    • Integration across multiple technologies

Thank You!