Path Management System for TDM

• “Point-and-click” provisioning from a central workstation for MAP networks
  
• Automatic periodic self-healing of faulty services
  
• Service security management, support user network access profiles and allow network partitioning
  
• Service availability report
  
• Physical and logical graphic representation of network links, services, nodes and clouds and network status indication
  
• Dynamic filter displays service and network link-related alarms
  
• CORBA-based client-server architecture and northbound CORBA interface
  
• Java client and Unix (Solaris)-based server

• Automatic service routing, for error-free and efficient bandwidth utilization
  
• Automatic reroute of protected paths maximize network uptime
  
• Network services discovery alerts potential network configuration problems
  
• Easy integration with third-party NMS products via CORBA

The RADview-SC/TDM service center application enables end-to-end management of RAD's Multiservice Access Platform (MAP) devices for simplified provisioning. An intuitive GUI, “point-and-click” functionality and easy-to-follow wizards increase the efficiency and accuracy of the service provisioning process.

The open, scalable, multi-access management capabilities enable network operators to add new services while minimizing overall operating costs, reducing provisioning times and maximizing efficiency of the network infrastructure.

Network discovery

Discovery of existing network services alerts to potential network configuration conflicts, and assures best utilization of existing network resources and easy migration steps.

Automated service provisioning

RV-SC/TDM supports automatic path routing based on efficient bandwidth resource analysis and user-configurable cost per link. As part of the service provisioning process, the user can select different service priorities and protection levels.

Intuitive GUI increases the efficiency and accuracy of the service provisioning process.

Provisioning is aided by “point-and-click” functionality and easy-to-follow wizards, with tips and hints that are displayed during the workflow. Full provisioning roll-back at network and device access failure is supported.

Automatic path reroute

An automatic path reroute algorithm ensures network resilience and maximizes the uptime of critical service. This important capability enables the service provider to uphold service level agreements (SLAs) per provisioned service.

Service level fault management

The RADview-SC/TDM fault management module correlates incoming events to service paths and helps present the actual status of the provisioned services.

History log enables reviewing events filtered according to event types and users.

Automatic periodic self-healing of faulty services. Various ways to maximize path integrity:

• All at once restoration
• Priority-based restoration
• Periodic restoration attempts
• Manual restoration

Network monitoring

Dynamic network status indication and alarms are displayed per node, link and path. Only the relevant alarms are displayed by filtering out the non-relevant alarms, allowing the user to focus on relevant information only.

Online maps display various types of parameters such as:

• Clock source flow
• Resource utilization
• Network link costs
• Security access permission

Security

Network access security based on network authorization rights of:

• Access level (administrator, operator, technician, and monitor)
• Device level (write, read and no access)
• User profile architecture

Service availability report

Service level reporting capabilities allow service providers to quickly and efficiently determine the uptime (in percentage) of a provisioned customer circuit. In addition to a user-friendly GUI-based interface, direct SQL-based access to the system database allows integration of service uptime information to third-party reporting systems.

Third-party integration

RV-SC/TDM uses CORBA-based client-server architecture and a northbound interface, which can be easily integrated with the carrier’s front office and back office systems, and any third-party application.

All system events published as CORBA events allow an OSS application to listen for well-filtered and relevant events from one central system.