MTNL Broadband Project (partners)

- MTNL - Ericsson - Houston Technologies Ltd.

MTNL Broadband Project Modules

PMS (Provisioning Management System) Integration Module BRAS ( Broadband Remote Access Server) Dorado Firewall

Project Deployment Sites

Mumbai NOC Delhi NOC

Solution Architecture

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 ASAP required for provisioning

ASAP - Introduction
The MetaSolv Automated Service Activation Program (ASAP) equips telecommunications service providers with a single intelligent platform for flow-through service activation. ASAP receives service requests from any source and transmits the required service activation information to any destination network device. ASAP can activate services on network elements or element management systems

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

Customer

ASAP Activates All Service Types

Local Services

Automated Service Activation

IP Services

Data Services Wireless Services

ASAP

The Network

Service Rep.

Customer request is entered into an order entry system Service order is created and passed to ASAP ASAP automatically activates service on required equipment

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 order and network element interfaces to support specific services and network elements using the following customizable modules: Service Request Processor (SRP) modules that interface with the host system Network Element Processor (NEP) modules that interface with network elements

Customer Service Request Sources

The ASAP provisioning process begins when customer service requests are sent from an order management or service order entry system. Work orders generally require other activities, such as updates 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 Information Systems Processor (ISP). It is functionally equivalent to an NEP.

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 appropriate database server. This advantages of this architecture over traditional program architectures includes flexibility, manageability, customization, improved performance and communication between applications.

Translation Overview

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.

ASAP Clients
Service Request Processor Receives the Work order from the external sources and sends 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 coordinates requests between the various SRPs and NEPs in the ASAP system. Network Element Processor It provides transparent connections to network elements or Element Management Systems.

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.

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.

ASAP Process and Database Components

Service Request ASAP Components & Databases
SRP DB

Ctrl DB

Ctrl Server

SRP

SARM DB

SARM

Admin Server

SARM DB

NEP DB

NEP

NE 1

NE 2

NE 3

Network Elements

 SRP bridges external systems and the SARM. It performs 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 for additional work order details. Transmits work order provisioning notifications and details back to the originating system.

Service Request Processor(SRP)

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

Network Element Processor(NEP)

NEP is the ASAP component that manages all interactions with network elements. An NEP sends work orders in the form of ASDL commands to a network element and receives responses from the network element about network activity. Through the NEP, ASAP can manage multiple connections to network elements. ASAP provides a robust framework that supports both proprietary State Tables as well as Java.

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

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 .

PORTAL INFRANET
-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.

Project Status for Mumbai Site

Pending Activities

Clustering of the DNS servers (dependency on MTNLs side, power supply hasnt been supplied as yet) Labeling and cabling at NOC. Integration of ASAP server with IPSE (new version is yet to 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 onsite for deployment)

Project Status for Mumbai Site

Completed Activities
PMS Integration Module (Installation, Clustering and configuration of SUN OS, Oracle, Bea Weblogic on the ASAP servers). Successful Integration of ASAP server with PEM.

Project Status for Delhi Site

Pending 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 yet provided onsite for deployment) Integration of ASAP server with CSMS database through OMS (connectivity not yet provided by MTNL)

Project Status for Delhi Site

Completed Activities Clustering of the DNS servers Labeling and cabling at NOC. PMS Integration Module (Installation, Clustering and configuration of SUN OS, Oracle, Bea Weblogic on the ASAP servers). Successful Integration of ASAP server with PEM. Successful Integration of ASAP server with IPSE.