The figure below illustrates the TMS LIU software module
architecture. Each software component performs specific functions
that represent a part of the total LIU software solution.
The APIs are comprised of a set of ANSI C functions and macros
that encapsulate all functionality and data of the LIU Software.
The API provides a clean interface simplifying the integration
to the target application. The target application is implemented
on top of the API layer, using the API to access all functionality
provided by the LIU Software.
The Configuration & Alarm Manager Modules provide the
interface point for administering and configuring any of
the spans controlled by the software.
The Configuration Manager (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 (AMM) maintains and
controls the operating state of the individual spans , processing
alarm conditions and other runtime conditions as they occur.
T1 & T3 alarm capabilities meet the standards per T1.231;
E1/E3 alarm capabilities meet the standards per I.431, G.731, & ETSI
300-233.
|
|
The Performance Manager Module (PMM) provides
support for span maintenance operations like loop backs and
near end line performance monitoring. For T1/T3 LIU, performance
monitoring meets the standards per T1.231. It also handles
bit-oriented code processing. For E1/E3 LIU, performance
monitoring meets the standards per G.826.
The Device Driver and its associated API provide the interface
between the LIU-Software and the driver device. The LIU Driver
API is comprised of a set of ANSI C functions and macros
that handle the interaction with the device driver.
M13 Multiplexing to T1/E1
The T1/E1 LIU TMS package provides full functionality for
M13 multiplexing applications when used in conjunction with
DS3 TMS, see figure below. The T3/E3 LIU package works in precisely
the same way. |
