T3 / E3 Trunk Management Software
For T3 / E3 Framers
The NComm T3 E3 WAN Protocol Software provides
a complete software solution for the implementation of T3 and E3
systems using T3 framers. Each package consists of a set of T3
E3 software modules that perform all aspects of low and mid-level
T3 and E3 support, from span alarming and maintenance to the collection
and reporting of performance data as specified in ANSI T1.231,
G.747, and G.704 for T3, and G.751, G.832 and G.826 for E3. Additionally,
the T3 E3 source code is completely data driven, allowing operating
mode, alarm timers, and thresholds to be configurable on a static
or run time basis. The suite includes 2 levels of ANSI-C Application
Programming Interfaces (APIs), encapsulating the details of T3/E3
operation and the underlying hardware elements, and providing a
clean integration to the target system's operating environment. NComm's T3 E3 TMS preserves T3 framer
and E3 framer independence.
Target Applications
|
Main
Features (Including T3 Framer Independence)
-
"Off-the-shelf" T3/E3
interface software providing multiple levels
of functionality in support of product applications
-
Supports
1 to N T3/E3 spans, making it ideal for multi-span
applications
-
Provides
full T3/E3 span maintenance and alarming support,
with configurable timers and thresholds for alarm detection,
loopback activation, and other span conditions
-
Full
support for T3 PMDL processing per ANSI T1.107, T1.107a
and T1.404, Performance Monitoring per T1.231 and FEAC
codes for T3.
-
Full
support for E3 G.751 and G.832 framing including
timing mark, trail trace messages, and performance monitoring
per G.826.
-
Supports
user choice of T3 framer, and drivers are immediately available. . Call
Call for details.
-
Runs
with or without Real Time Operating System (RTOS)
on virtually any processor and host environment. Currently
ported to Linux, VxWorks, OSE, and Nucleus Plus.
-
Simple
Application Programming Interfaces (APIs)
-
Processor
independent ANSI-C source code
-
Fully
customizable - Interworks with T1 TMS for T1 T3 and T1 E3 Applications
|
T3/E3
Trunk Management Software (TMS) Architecture
The figure
below illustrates the TMS software module architecture. Each
software component performs specific functions that represent
a part of the total T3 or E3 software solution. The T3/E3 Software
API is comprised of a set of ANSI C functions and macros that
encapsulate all functionality and data of the T3/E3 TMS Software.
The API provides a clean interface with both T3 framers and
higher layer customer applications simplifying the integration
of the TMS Software to the target application. The target application
is implemented on top of the T3/E3 TMS API layer using the
API to access all functionality provided within the TMS Software.
The T3/E3
Configuration & Alarm Manager Module (CAMM) provides
the interface points for administering and configuring any
of the T3 and E3 spans being controlled by the T3/E3 -Software.
The CAMM maintains the configuration data for the spans, providing
a clean interface to configuration data for the other software
components, and controlling how span data is updated at runtime.
Further, the CAMM maintains and controls the operating state
of the individual spans, processing alarm conditions and responses,
and other runtime conditions as they occur. |
Full T3 support is provided for FEAC codes per ANSI T1.107 and T1.107a and
T1.404 Path Maintenance Data Link. It supports detection and
reception of standard trunk alarms (LOS/OOF/Red, RAI/Yellow,
Idle and AIS/ Blue). Full E3 support is provided per G.751
and G.832. Timers for declaration and clearing of alarms are
configurable via the CAMM. The CAMM also communicates with
the T3/E3 PMMM for processing performance reports.
The optional
Performance Monitoring Manager Module (PMMM) will collect
T3 performance data as specified in ANSI T1.231 and G.704.
E3 performance data is collected per G.826. The PMMM will collect
performance statistics for both the near end, and in C-bit
parity format, the far end of the T3 Interface. Performance
data is collected in 24 hour intervals with 15 minute buckets
and summary information. In addition, the PMMM supports collections
of data locked to the time of day. The application can retrieve
performance information upon request to the PMMM.
The Device
Driver and its associated API provides the interface between
the T3/E3 TMS Software and the device driver. The T3/E3 Driver API is comprised
of a set of ANSI C functions and macros that handle the interaction
with the device driver. This driver can be used with the T1
E1 driver for T1 T3 or E1 E3 applications. NComm provides the
driver for the users choice of device. |
|
|
|
