mtnl bb ericcson

7/29/2019 MTNL BB Ericcson

1/27

MTNL Broadband Project

(partners)

- MTNL

- Ericsson- Houston Technologies Ltd.


2/27

MTNL Broadband Project Modules PMS (Provisioning Management System)

Integration Module

BRAS ( Broadband Remote Access

Server)

Dorado

Firewall


3/27

Project Deployment Sites

Mumbai NOC Delhi NOC


4/27

Solution Architecture


5/27

Order Management System (OMS)

- MTNLs OMS will send provisioning information to MetaSolv ASAP.

-The work orders that would come from MTNLs OMS will request

the following activation operations:

Creating a user

Deleting a user Blocking a service

Unblocking a service

Change of service

- The OMS will send work order with all the parameters to ASAPrequired for provisioning


6/27

ASAP - Introduction The MetaSolv Automated Service Activation

Program (ASAP) equips telecommunications

service providers with a single intelligent platformfor flow-through service activation.

ASAP receives service requests from any sourceand transmits the required service activation

information to any destination network device. ASAP can activate services on network elements

or element management systems


7/27

ASAP - Introduction ASAP supports a full range of interfaces based

on international standards, including:

-TCP/IP

-Telnet

-FTP

-CORBA

-LDAP

-TL1-SNMP

-OSS through JAVA


8/27

ASAP Activates All

Service TypesCustomer

The

Network

IP Services

Local

Services

Data

Services

Wireless

ServicesService

Rep.

Automated

Service

Activation

ASAP

Customer request is entered into an order entry system

Service order is created and passed to ASAP

ASAP automatically activates service on required equipment


9/27

ASAP Component Overview MetaSolv ASAP uses a multi-tier architecture that

operates on an Oracle database engine.

To run ASAP, we need to install the ASAP core

software, and then implement the service orderand network element interfaces to support

specific services and network elements using the

following customizable modules:

Service Request Processor (SRP) modulesthat interface with the host system

Network Element Processor (NEP) modules

that interface with network elements


10/27

Customer Service Request

Sources The ASAP provisioning process begins when customer

service requests are sent from an order managementor service order entry system.

Work orders generally require other activities, such asupdates to customer, billing, and assignment records,in addition to the provisioning operation.

ASAP provides an interface to external systems, such

as a facilities or billing system, through an InformationSystems Processor (ISP). It is functionally equivalent to

an NEP.


11/27

ASAP Architecture The ASAP application consists of a set of

multithreaded UNIX client/server processes

and J2EE applications that communicate with

one another and with the appropriatedatabase server.

This advantages of this architecture over

traditional program architectures includes

flexibility, manageability, customization,

improved performance and communication

between applications.


12/27

Translation Overview


13/27

ASAP Clients AIMS

A GUI-based application that allows you to easily administer

an ASAP installation and supply the information you need to

provide quality services to the customer.

OCA

A Java-based GUI, that communicates with the CORBA SRP

and enable the user to query and create work orders,

monitor work order-related events, define notifications based

on generated events, and manage fallout work orders.


14/27

ASAP Clients Service Request Processor

Receives the Work order from the external sources andsends the ASAP version of the work order to the Service

Activation Request Manager (SARM).

Service Activation Request Manager

Acts as a request controller that determines and coordinatesrequests between the various SRPs and NEPs in the ASAPsystem.

Network Element Processor It provides transparent connections to network elements or

Element Management Systems.


15/27

ASAP Servers Admin Server

Maintains performance data generated by other ASAP

components.

Control Server Manages the overall run-time distribution of ASAP

components.

AIMS Server

Provides the AIMS client with a single point of

communication to the rest of ASAP, enabling controlled

access to minimize network traffic and performance impact.


16/27

ASAP Process and Database

Components Every ASAP component application can have its own database.

ASAP uses Oracle RDBMS as the database engine.

A single database can contain one or more ASAP databases.

Alternately, every ASAP database in a fully-distributed

environment can reside on a separate RDBMS, on separate

machines.


17/27

ASAP Process and Database

Components

Network Elements

ASAP Components &

Databases

Service Request

Ctrl DB

SRP DB SRP

SARM DB

NEP DB

SARM

NEP

SARM DBAdmin Server

Ctrl Server

NE 1 NE 2 NE 3


18/27

Service Request

Processor(SRP) SRP bridges external systems and the SARM. Itperforms the following functions.

Receives work orders from external sources.

Updates work order status requests to the SARM. Deletes work order requests to the SARM.

Receives work order event notifications from the

SARM.

Submits work order queries to the SARM foradditional work order details.

Transmits work order provisioning notifications

and details back to the originating system.


19/27

Service Activation Request Manager(

SARM ) It Coordinates the requests between various SRPs

and NEPs in a ASAP Systems. The SARM performs

the following functions.

Maintains connections to all SRPs and NEPs

within ASAP

Controls all ASAP operations in both directions

Manages host feedback. Manages connection load balancing


20/27

Network Element

Processor(NEP) NEP is the ASAP component that manages allinteractions with network elements.

An NEP sends work orders in the form of ASDL

commands to a network element and receivesresponses from the network element about network

activity. Through the NEP, ASAP can manage

multiple connections to network elements.

ASAP provides a robust framework that supportsboth proprietary State Tables as well as Java.


21/27

Public Ethernet Manager (PEM)

-PEM is an element manager, it will focus on part of an overall network

solution at an operator.

-PEM provides open interfaces to allow integration into the operators

Operational Support System (OSS).

-PEM is responsible for :--

Create, update, read and delete end-users.

Read information about End-user Profiles defined

Read all defined ports in the network

Add and remove End-user Profiles to/from end-users

Add and remove Services to/from end-users

Link an end-user to a port


22/27

IP Service Engine (IPSE)-IPSE is a service management solution supporting all services in a Public

Ethernet network.

-It controls both access and IP networks to define, publish and then

control services.

- The overall aim of the IPSE is to support a quick and smooth introduction

of services into the communication network by providing a "single point"

interface for IP service information, regardless of access network .


23/27

-PORTAL Infranet is a billing system for IP and

telecommunications service providers.

-Infranet integrates seamlessly with services to

provide customer registration, service provisioning,

authentication and authorization, customer activity

tracking, billing, account management, and data

collection and reporting.

PORTAL INFRANET


24/27

Project Status for Mumbai SitePending Activities

Clustering of the DNS servers (dependency on MTNLsside, power supply hasnt been supplied as yet)

Labeling and cabling at NOC.

Integration of ASAP server with IPSE (new version is yetto be deployed by Ericsson)

Integration of ASAP server with Portal

Infranet (IPSE deployment has to take place before this)

Integration of ASAP server with SSSS

Web Portal Infranet (DNS server not yet provided onsitefor deployment)


25/27

Project Status for Mumbai SiteCompleted Activities

PMS Integration Module (Installation, Clusteringand configuration of SUN OS, Oracle, Bea

Weblogic on the ASAP servers).

Successful Integration of ASAP server with

PEM.


26/27

Project Status for Delhi SitePending Activities

Integration of ASAP server with Portal

Infranet (the test server has been provided in a

ready state by MTNL as yet) Integration of ASAP server with SSSS

Web Portal Infranet (DNS server not yetprovided onsite for deployment)

Integration of ASAP server with CSMS

database through OMS (connectivity not yetprovided by MTNL)


27/27

Project Status for Delhi SiteCompleted Activities

Clustering of the DNS servers

Labeling and cabling at NOC.

PMS Integration Module (Installation, Clusteringand configuration of SUN OS, Oracle, BeaWeblogic on the ASAP servers).

Successful Integration of ASAP server with

PEM. Successful Integration of ASAP server with

IPSE.

mtnl bb ericcson

Documents