The
figure below illustrates the TMS software module architecture. The
T1/E1 software API consists of a set of ANSI-C functions
and macros that encapsulate all functionality and data of
the T1/E1 software. The API provides a clean interface
to the T1/E1 software simplifying the integration of the
T1/E1 software to the target customer application. The
target application is implemented on top of the T1/E1 software
API layer, using the API to access the functionality provided
by the T1/E1 software. The
Configuration Manager Module (CMM) provides the interface
point for administering and configuring any of the T1/E1
spans controlled by the T1/E1 software. The CMM 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 run time. The
Alarm Manager Module (AMM) maintains and controls
the operating state of the individual spans , processing
alarm conditions and other runtime conditions as they occur.
T1 alarm capabilities meet the standards per T1.231; E1 per
I.431, G.731, & ETSI 300-233. |
|
The
optional Maintenance Manager Module (MMM) provides
support for span maintenance operations like loop backs and
performance monitoring. For T1, the MMM includes FDL
reports for both ANSI T1.403 and AT&T Pub 54016. It
also handles bit-oriented code processing. For E1,
Performance Monitoring meets the standards per G.826 and
provide a 15 min/24 hour data performance database as well. SA
bit processing will conform to G.704. The application
can request current performance reports from the MMM for
both the remote and local side.
The
optional Signaling Manager Module (SMM) processes
the robbed bit/CAS signaling information on the channels
within a T1/E1 span. The SMM processes the signaling
bits according to one of several signaling modes (e.g. E+M,
FXO, FXS, LS, GS, GR-303 Hybrid Signaling and E1 signaling
models as those defined in Q.421 & Q.422.) on a channel
by channel basis. Additionally, the SMM allows custom
signaling protocols to be defined and processed as well. For
applications that do not require signaling bit processing,
the SMM functionality can be disabled on each timeslot. |