Billing BIS3
Network Analysis
Why you need NEAT?
Latest News

Pegasus Network Engineering Analysis Tool (NEAt) ON-LINE

Used for the independent validation and monitoring of contracted levels of network coverage throughout the life time of the PMR (e.g. TETRA) system. This is what we offer, as well as Planning & Optimization.


With NEAt you can either:

Use the Standard SQL Library of Queries Pegasus Supplies or:

Use direct manual SQL Queries on

the Pegasus Internal CDR SQL database....

With the advancements and evolution of wireless networks over the past few years, the ability to monitor the performance of the entire network and to identify the impact of changes in any network element on end-customer service levels is becoming mission critical.

NEAt, the Network Engineers' Analysis Tool, provides mobile network operators with an in-depth understanding of what's going on in their networks by looking at real-time or historical CDR data from all of their switches, inter-switch and back-haul links.

This data is collected by Pegasus PCLF, aggregated by Pegasus PCIH, cross-checked for errors and inconsistencies, correlated, analyzed and presented in various meaningful charts, matrices and tables, providing radio engineers and network operations & maintenance staff an immediate and pervasive view of their network's health status.

In addition, NEAt allows operators to carry out what-if simulation scenarios to forecast the effect of introducing new services to specific or all parts of the network. This allows one to predict infrastructure usage for traffic channels, tie lines or microwave point-to-point links, and to find out evolution of spectrum usage classified by type of channel.

The unique ability of NEAt to correlate performance and utilization information, as well as its flexibility and vendor-independence, equip service providers with a single platform to more effectively manage their network and provide customer satisfaction during this evolutionary period.

With NEAt, carriers will gain clearer and more accurate visibility into the operation of their entire Trunked radio (MPT-1327, TETRA) or cellular (GSM, UMTS) networks, effectively turning raw data into meaningful and essential information.

Through the application of NEAt's industry-leading performance monitoring and capacity planning techniques, carriers are able to improve service levels, increase efficiency, and lower costs of their mobile and fixed networks.

Drilling down deeper into your CDRs

CDRs are the raw material that contain a meticulous trail of every activity in the network. Unfortunately, this data is typically coded in a proprietary binary format and thus inaccessible to network operators. And there's not just one type of CDR, but different ones depending on the type of call. For example, here are the CDR types for a currently and very popular TETRA network system:

TETRA originated call attempt records

These CDRs are created for each call attempt originated by a TETRA subscriber. The total size of a TOC record is 190 bytes. In individual calls, TOC records are generated in the exchange where the calling party is located in the beginning of the call. In group calls, they are formed in the home exchange of the group.

TETRA terminated call attempt records

A TETRA terminated call attempt (TTC) record is created for each call attempt

terminated to a TETRA subscriber. In a TETRA System these records are produced only for the called subscriber in a point-to-point call. The total size of a TTC record is 133 bytes. TTC records are generated in the exchange where the calling party is located in the beginning of the call.

Incoming gateway call attempt records

An incoming gateway record (InG) is created for each incoming call attempt received by a gateway from another network. These records can be used to settle accounts with other networks. The generation of gateway records is not affected by the production of TTC records. A gateway record is generated also in cases when the originating and terminating gatway are co-located. The total size of an InG record is 109 bytes.

Outgoing gateway call attempt record

An outgoing gateway record (OutG) is created for each outgoing call attempt from a gateway to another network. These records can be used to settle accounts with other networks. The generation of gateway records is not affected by the production of TOC records, a gateway record is generated also in cases when the terminating and originating digital exchange gateway are co-located. The total number of bytes in an OutG record is 95.

Short Data and Status -TETRA originated record

An SDS TETRA originated record (SDS-TO) is produced for each Short Data and Status message sent by a TETRA subscriber. The total size of an SDS-TO record is 140 bytes. Acknowledged SDS service involves sending an acknowledgement SDS back to the originating switch to confirm successful delivery of the SDS originally sent. No CDRs are produced for these acknowledgement SDS messages. SDS-TO records are generated in the originating (calling subscriber's) digital exchange.

Packet data records

If the generation of these records is enabled then a PD record is created for each packet data context activation attempt originated by a TETRA subscriber. Fields digital exchange ID, Location Area and Cell Identity report the location of the mobile subscriber.

As mentioned above, all this information usually lies hidden away, and most switch manufacturers have so far been extremely reluctant to provide third parties insight into their proprietary CDR coding schemes. However, Pegasus has managed to extract this information, and analyses and present the relevant facts to network operators in an easy to understand graphical format.

Not only can network operators now see their network's health with a bird eye's view, but if need be, they can drill down up to the details of a single call, extracting every bit of available data and squeezing out all relevant information. However, all subscriber-related information requires specific access permissions so as to comply with data privacy laws and policies.


In addition to network performance and CDR analysis, reporting is becoming a vital instrument in assisting in the continued success of a wireless operator business. Reporting provides the visual representation of data for trend comparisons and management models allowing empowered and critical decisions on both day-to-day and strategic levels.

Pegasus' reporting functionality, included in its data mining module, allows data collected by NEAT on the network traffic to be collated into an understandable and usable format. Statistics such as call outcome, inbound and outbound calls handled, calls types, success ratios, and grade of service, can be mined from a central repository using the integrated reporting module.

Through NEAt's APIs, information from other parts of the business such as sales or forecasts can also be included while graphical representation in a format appropriate to the data (such as linear, bar or scatter graphs) provides true data visualization.

Systems Architecture

The NEAt system architecturally integrates servers, storage and a relational database into a single powerful, carrier-class solution created from the outset to process queries faster and enable complex analysis that was not previously possible because of large and fast-growing data sizes.

For data storage purposes, NEAt uses an Oracle database, but is capable of being adapted to other database platforms if required. This enables operators to harness information located in tens, even hundreds, of gigabytes of data in order to lower costs, optimize the use of existing infrastructure, reduce risk and fraud, strengthen customer relationships and keep pace with ever-changing market trends.

NEAt itself is currently being re-written in Java and will therefore be platform independent in its next version. Supported standards such as XML, JDBC and CORBA will enable NEAT to be interoperable with a wide range of other applications.

OSS Integration

Pegasus has recognized that strength is in unity, and has consequently decided to combine its forces with that of other Operations Support System vendors adhering to the OSS through Java Initiative (OSS/J).

The OSS/J members aim to kick-start a marketplace of interchangeable, interoperable components that can be rapidly and cost effectively assembled into end-to-end telecommunications solutions that are easy to maintain and adapt to support new functionality.


NEAt is uniquely positioned to enable mobile operators to understand the inner workings of their networks. The system provides benefits such as:

• Compatibility with numerous Trunked radio and cellular systems

• Customization available for any other exchange that produces CDRs

• Carrier class stability with "five nines" availability

• Truly open APIs and standards-based architecture

• Customer-proven, mature platform

• Correlation of network usage and performance data

• Improvisation of network resources

• Optimization of network performance

• What-if analysis providing insight into repercussions of service changes

• Maximization of available capacity, both wireless and wireline

• Fostering lean operations


Google Analytics