|
|
|
Trunk
Management Software Does
the TMS employ an Application Programmers Interface (API)? Is
the framer device driver extra? What Operating Systems are supported? What is the typical porting time? What processor is the software written for? What kind of system resources does the TMS consume? Does the license include source code? What is the source code written in? What support is included in the license? What capabilities are in your T1/E1 TMS modules? What robbed bit signaling models are supported? What capabilities are in your T3 and E3 TMS modules? What
capabilities are in your SONET TMS modules? Does NComm have any other software offerings? |
|||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||
Trunk Management SoftwareWhat is NComm’s Trunk Management Software?NComm’s Trunk Management Software, or TMS, is a completely functional suite of T1/E1, and T3 software providing configuration, alarm, maintenance/performance monitoring, loopback activation, Robbed-Bit Signaling (T1) and Channel-Associated Signaling (E1), functionality. The TMS sits between the developers product and the framer driver below. It does not deal with the data payload, but handles the control, monitoring and reporting required to keep the trunk operating as effectively as possible and in a standard compliant manner. NComm’s
TMS is available for T1, E1 and T3. We have recently released
a T1/E1 LIU package when combined with the T3 TMS provides full functionality
for an M13 mux application. A variety of framer drivers are
ready to ship now. What advantage do I have with NComm TMS rather than developing this software in-house?With NComm’s TMS software, you collapse your T1/E1/T3 development schedule from the better part of a year to just a few days, thus gaining time-to-market. You also spend less money and conserve scarce development resources. First
time development of T1, E1 or T3 standard compliant programming in-house
takes about 2 staff-years and 9-12 months of elapsed time. When you
are done, you have nothing that differentiates your product. You
just have something that works. You also have consumed more engineering
expenses than going with NComm and have lost a couple of staff-years
of effort that could have been applied to adding value to your product.
Further, you added another branch of development activity that probably
delayed your product release and added risk to the entire product
in terms of the software being standards compliant and even functional. Does the TMS employ an Application Programmers Interface (API)?Yes,
there are two API layers, each with three function calls. The first
API layer is between the customer’s application and the TMS software. The
second API layer is between the TMS software and the framer device
driver. Usually, the developer will only need to work with the application
API layer. Are multiple span devices supported?Yes. The
TMS APIs support single and multiple span devices. Part of
the TMS initialization process binds the logical span number to the
particular device and the span offset in the device. Thus,
the TMS codes allows multi-span framers as well as framers from different
vendors to operate with a unified application layer API. What framer devices are supported?Most
of the Dallas, Infineon, PMC and Agere as well as several other
T1, E,1 T3, E3 and SONET/SDH devices are currently supported.
If a
specific device is not currently supported, NComm will develop
a new device driver within 8 weeks of order. Is the framer device driver extra?No,
a framer device driver for the customer’s specific framer device
is included with the TMS package at no additional charge. Additional
drivers are available for an additional license fee. How portable is my application if I want to change platforms?NComm’s
TMS is architected to make the framer device transparent to the
customer application. The device driver acts as the “shock absorber”
and takes care of hardware nuances. Both the TMS and customer application
layers are totally portable to another platform simply by changing
the framer device driver. We aim for 100% preservation of the investment
the user makes to their software. What Operating Systems are supported?The TMS package comes already ported to Linux, VxWorks, OSE, and Nucleus Plus real time operating systems. A LINUX port will be completed by the end of February (2004). It can also run under a simple visitation loop, although this is not recommended. The
NComm TMS software is designed to be O/S-independent. The TMS
package is easily ported to most real time operating systems. The
porting issues are generally restricted to only one header file containing
a few macros that resolve to operating system kernel calls. A
porting guide is available to ease migration to other operating systems
if the customer wishes to perform their own port. What is the typical porting time?Provided
that your hardware is debugged, porting time is typically a few days.
About a third of our users are up in less that a single day. What processor is the software written for?The
TMS software is standard ANSI C-code, and is therefore processor
independent. NComm tests all software on a Motorola 860 platform
with the customer’s specific framer device prior to release. What kind of system resources does the TMS consume?The following table illustrates CPU bandwidth consumption for various TMS configurations; these are standard Dhrystone Ver 2.1 MIPs measured on an MPC860 or an MPC8260 platform. Note that resource figures are similar across processors with framer devices that do not utilize indirect register access.
* MIPs are conservative estimates; Text/Code is per system; Data/BSS is per line or span; T1/E1 Data/BSS is less than the sum; E3 MIPS estimated #
Signaling is not applicable for T3,
E3 or SONET/SDH Does the license include source code?Source
code is included in the software deliverable. The user is free
to modify the source code with the caveat that modification would
restrict NComm support. The license is for distribution of compiled
object code embedded in a product. What is the source code written in?The
source code is written in standard ANSI-C. No assembly code is used. Does NComm offer trial code?No.
NComm does offer a 30 day money back guarantee that allows a developer
to actually use the software and return it for a full refund if not
satisfied. What support is included in the license?60 days of implementation
support to answer questions about TMS is included. In addition, a
day of training is provided at NComm’s offices. Is extended support offered?Yes,
extended support is available for 12% of the license price per
year. This entitles the user to bug fixes, enhancements and reasonable
telephone support. If issues are found in the users code, NComm
will fix the users version of code if requested rather than force
the user to move to a new code base. What capabilities are in your T1/E1 TMS modules?· Configuration Manager Module (CMM) - Configuration for the T1/E1 span, and for other modules purchased Ø Line Encoding (AMI, B8ZS, HDB3) Ø Line Framing Format § T1: D4-Super Frame or Extended Super Frame § E1: Multiframe Non-multiframe CRC Non-CRC Ø Line Build-Out (Short haul/Long haul w/ distance parameters) Ø Alarm integration including programmable integration timers Ø Selection of clear channel, idle channel, and/or signaling model. Selectable on a per voice channel basis. Ø Selection of user side or network side for the interface Ø Configuration of addresses for maintenance protocols Ø Selection of remote, local, payload, and diagnostic loopbacks under application control · Alarm Manager Module (AMM) Ø Standards compliant detection, declaration, and clearing of all alarm conditions per T1.231 Ø Programmable alarm integration timers for OOF, LOS, AIS, and RAI. Standards compliant responses to far-end alarm conditions as per T1.231 Ø The E1 alarm capabilities will meet standards per I.431, G.732, ETSI 300-233 · Maintenance Manager Module (MMM) Ø Manages and responds to the Facility Data Link (FDL) per TR-54016 Ø Bit Oriented Message (BOM/BOC) handling per T1.403 Ø Programmable Loop Back codes Ø In band and out of band Loop Up and Loop Down code reception and transmission Ø 1 second performance report collection and transmission per T1.403 Ø 96, 15 minute performance data bucket collection and transmission for the Near End per TR-54016 Ø Responding to and transmitting 15 minute performance data bucket over the FDL for the Near End per TR-54016 Ø Far End performance data collection in 96, 15 minute buckets and 24-hour summary based upon receipt of T1.403 PRMs from the far end. Ø For E1, Performance Monitoring will meet the standards per G.826 and provide a 15min/24 hour data performance database as well. SA bit processing will conform to G.704 Ø For E1, control of Sa, Si, and X bits. · Signaling Manager Module (SMM) Ø Establishes Robbed Bit or Channel Associated Signaling (CAS) communication per timeslot Ø T1 Robbed-bit signaling allows customer choice of signaling models per T1.403 – 1999, TR-03, or GR-303-CORE-Rev3 (Tables 12-3 & 12-4). Choice may be done on a per DS0 basis Ø E1 CAS signaling models are those defined in Q.421, Q.422 and may be done on a per E0 basis Ø Processes signaling freezing and debouncing Ø Provides call state information such as wink, flash, on-hook, loop open, etc. to the application layer per the selected signaling model Ø Transmission and reception of dial pulse digits are fully supported. Ø Timers associated with signaling such as wink, hook flash, and digit on/off ratios, are programmable on a per timeslot basis Ø TR-08/SLC-96
and T1.403 Tri-level signaling supported with external hardware support
for generation and detection of the toggling state. What robbed bit signaling models are supported?Currently, all robbed bit signaling model specified in T1.403.02-1999 are supported including: · Loop start · Loop start with RLCF · Ground Start · Ground Start with RLCF · Loop-Reverse Battery Signaling · Network provided reverse battery signaling · E & M Signaling · Customer-installation-provided loop-start supervision (FXS/FXO) · Private line auto ring · Ringdown Both SF/D4 and ESF version of these signaling models are supported. In addition, the DS0 alarms states are provided for all ESF models. All 6 signaling models specified by TR-08 are supported including: · Superimposed Ringing Multiparty · Direct Inward Dialing Dial Pulse Terminating · Frequency Selective Ringing Multiparty · Single Party · Superimposed Ringing Multiparty · Universal Voice Grade The GR-303 models from tables 12-3 and 12-4 are supported including: · Coin CF/DTF · Loop Reverse Battery – Differs from the definition in T1.403.02-1999 · Multiparty Signaling New signaling models are being added. If you don’t find what you need, Contact NComm for an up to date list or your signaling model requirements. What capabilities are in your T3 and E3 TMS modules?DS3 Configuration/Alarm Manager Module (D3MM)
What capabilities are in your SONET TMS modules?SONET Configuration/Alarm Manager Module (SONMM)
SONET Automatic Protection Switching Module (SONET APS)
What support does NComm have for T1, E1, T3 and E3 protection switching?
Other SoftwareDoes NComm have any other software offerings?Through the Altera AMP program, NComm offers the ToneGen and GainGen Megafunctions. NComm HardwareDoes NComm have any hardware offerings?Yes, NComm also sells the same hardware it uses for software development and test. This includes our Salem2, five slot, 860 development platform, and Telecom Interface Modules for all of the framer devices we support. Our hardware can be used to verify framer and software functionality, as a target for early software development and as a reference platform to trouble shoot customer software issues. NCommWho is NComm?NComm’s roots are in software and hardware telecom consulting engineering. We are in our fifth year of operation. NComm’s experience ranges from DS0, though T1/E1 and T3 to Primary Rate ISDN. We have completed projects for the Central Office and Customer including central office switches, edge devices and PBXs. From it’s roots in consulting, TMS was conceived and is now the central focus of our business. Do you do consulting work?Yes. We have on-going software contracts and are very active in the hardware area. In 1999, NComm produced 26 hardware designs. That number will increase in 2000. While
we will entertain any need, we try to reserve our consulting resources
for those TMS customers that need additional help to get their
products to market more quickly. We can also provide an extra pair
of eyes to insure a thorough design review. |
|||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||