|
About - AdventNet TL1 API
Driving Factors
Over the last couple of decades, TL1 has emerged as a popular and widely used management protocol in the Telecommunications equipment market, and especially as a dominant one in the RBOC space. The importance of TL1 has increased further with OSMINE compliance becoming a crucial gating factor for OEM vendors accessing the vital RBOC space. Building sound management applications, such as EMSs / NMSs for specific telecommunications devices/domains and OSSs for NOC based on TL1 in the least possible time-to-market has become critical for both OEM vendors and Service Provider vendors. Apart from meeting tough deadlines, building good management applications based on TL1 requires developers to deal with various unpleasant technical realities specific to the TL1 world.
Often developers are faced with the arduous task of getting the management applications to interface with devices belonging to diverse technologies, domains, and vendors. These devices, although conforming to the Bellcore (Telcordia) standards at a high level often do have many variations and flavors when it comes to specific TL1 messages. Apart from this, each standard TL1 message has its own information structure and size, and there is no standard way of capturing TL1 message formats for management applications to automate message processing /rationalization.
In general, TL1 devices are fault critical. Loss of device alarms and notifications can have a direct bearing on the QoS delivered by the management applications, especially under production environment. Prevention against such data loss mandates the management applications to maintain a perpetual TL1 connection to each device. However in reality, connection termination is common and the management application needs to identify and re-establish the TL1 connection immediately. In other words, the management application has to maintain a robust communication channel with the TL1 devices.
Above all, when the need of the hour is to focus on management functionalities and maximize the ROI, understanding the complexities of the TL1 protocol will take time and effort.
AdventNet TL1 Solution
Using AdventNet TL1 API, building management applications is easier and elegant than ever before. It offers a rich set of features and enables TL1 management application development with good quality, lesser development effort, and quicker market delivery. AdventNet TL1 API libraries are carefully designed for performance, scalability, robustness, and importantly usability. They are easy to comprehend and use. Most importantly, they adopt a unique design approach and are geared up to enable management applications to gracefully and effectively deal with all TL1 device specifics and intricacies in a transparent and scalable manner.
Apart from providing core TL1 protocol functionality, the product also offers valuable tools and components. These tools help both application building and testing. It allows vendors to re-brand and bundle these tools as part of their management applications, contributing towards building feature-rich management applications easily.
Using AdventNet TL1 APIs, our customers have successfully built EMSs that have been integrated with popular Telcordia OSSs, such as NMA, TIRKs, etc. and certified OSMINE compliant.
Key Features
Following are the key features provided by AdventNet TL1 API.
|
Feature |
Benefits |
|
Open standards and cross-platform |
Built on Internet standard technologies, such as Java and XML, it ensures greater productivity and interoperability. |
|
Scalable TL1 communication APIs |
Robust and intuitive TL1 communication APIs and interfaces. Enables management applications to maintain robust TL1 connectivity and allows it to scale to manage a large number of diverse TL1 devices. |
|
Multiple transport protocol support |
Off-the-shelf support for TCP, Telnet, and Serial transport protocols. TCP is the default implementation. Users can also plug in their own transport protocol easily by implementing an easy interface. |
|
Robust TL1 message parser |
Parses the complex TL1 messages seamlessly and generates easy-to-use TL1 message objects. The Message Parser implements powerful recognition-based algorithms which can effortlessly handle TL1 messages with various flavors. |
|
TL1 session logging |
Generate historic information of TL1 device transactions for debugging and routine auditing. Offers transaction-based information logs as well as raw data logs. |
|
TL1 message filtering and formatting |
Offers dynamic filtering and formatting of specific TL1 messages. Users can plug in their own filter or formatter by implementing an easy interface. |
|
Automatic TL1 message rationalization |
Enables XML-based TL1 message definitions. Offers objects and APIs for various automation tools and applications to access these definitions. Offers seamless upgrade of actual TL1 messages based on their XML definitions. |
|
TL1 Message Builder |
Intuitive editor tool for creating XML-based TL1 message definitions. These XML message definitions play a crucial role in automating various TL1 operations. The tool supports Internationalization and a re-brandable user interface. |
|
TL1 Craft Interface |
Allows field engineers to easily interface with multiple TL1 devices simultaneously. Enables loading of pre-built TL1 commands and simplifies the tedious task of dealing with various device-specific TL1 messages. The tool supports Internationalization and a re-brandable user interface. |
|