White Paper

Knowledge Management

nexGen SS7
The Ideal Platform for
Media Server Development

www.flextronicssoftware.com
 White Paper

Copyright information
© 2005 Flextronics Software Systems Ltd. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or otherwise, including photocopying, reprinting or
recording, for any purpose, without the express written permission of Flextronics Software Systems Ltd.

Disclaimer
Information in this document is subject to change without notice and should not be construed as a commitment on the part of Flextronics Software
Systems. Flextronics Software Systems does not assume any responsibility or make any warranty against errors that may appear in this document and
disclaims any implied warranty of merchantability or fitness for a particular purpose.

Trademarks
All other company, brand, product or service names mentioned herein are the trademarks or registered trademarks of their respective owners.

Flextronics Software Systems Ltd.

Plot 31, Electronic City, Sector 18,
Gurgaon - 122015
Haryana (INDIA)
Tel: +91-124-2346666/2455555
Fax: +91-124-2342415/2342810
e-mail: info@flextronicssoftware.com
Visit us at: http://www.flextronicssoftware.com

Tec h n o l o g y I n n ovat ion Pe ople

 White Paper

Contents

1. Introduction.....................................................................................................................................................................................4
1.1 Global trends...........................................................................................................................................................................................................................................................................4
1.2 ‘nexGen SS7’...........................................................................................................................................................................................................................................................................4

2. Media server......................................................................................................................................................................................5
2.1 Challenges faced by operators..........................................................................................................................................................................................................................................5
2.2 Media server - network positioning ...............................................................................................................................................................................................................................5
2.3 Media server - architecture ...............................................................................................................................................................................................................................................6
2.4 Typical requirements ...........................................................................................................................................................................................................................................................7

3. nexGen SS7 - an ideal platform for building media server.............................................................................................7

3.1 nexGen-resolving issues faced by media server developers..................................................................................................................................................................................7
3.2 ‘nexGen SS7’-value proposition......................................................................................................................................................................................................................................9
3.3 Conclusion ...........................................................................................................................................................................................................................................................................10

A. nexGen SS7........................................................................................................................................................................................11
A.1 ‘nexGen SS7’-components................................................................................................................................................................................................................................................11
A.2 ‘nexGen SS7’-features.........................................................................................................................................................................................................................................................11
A.2.1 Reliability and scalability...............................................................................................................................................................................................................................................11
A.2.2 High capacity.....................................................................................................................................................................................................................................................................11
A.2.3 Rich protocol features.....................................................................................................................................................................................................................................................11
A.2.4 Comprehensive APIs.......................................................................................................................................................................................................................................................11
A.2.5 Integrated management support..............................................................................................................................................................................................................................12
A.2.6 Diagnostics........................................................................................................................................................................................................................................................................12
A.3 ‘nexGen SS7’-standard compliance...............................................................................................................................................................................................................................12

Te chno l og y Innovat ion Pe op le

 White Paper

Introduction

1. Introduction
This whitepaper explores the role and positioning of media servers in a
network. It examines the architecture of the media server and the
components required to build a media server. It further describes
Flextronics Software Systems (FSS’) ‘nexGen SS7’ solution and outlines
how it is an effective and reliable platform to build media servers on.
1.1 Global trends
Voice continues to rule the world of wireless and wireline telephony, the
recent emergence of data services notwithstanding. Enhanced
voice-enabled services continue to be major revenue sources for
operators. These services act as service differentiators – a means to
provide customers with value-added, cost-effective, personalized services
– and at the same time help in keeping operational expenses under
control.
The demand for enhanced voice-enabled services is on the rise, especially
in the wireless world where innovative services such as customized
ring-tones and voice and video messaging have been introduced. These
value-added services are enabled in networks through media servers,
which provide media resources and functionality to the service platforms.
Media servers perform multimedia-processing tasks such as playing
announcements, audio/video recording and playback, interactive voice
response (IVR), fax reception and transmission, automatic speech
recognition (ASR), text-to-speech conversion (TTS), and multimedia
conferencing.
1.2 nexGen SS7
FSS’ ‘nexGen SS7’ is a ready-to-use, pre-integrated, scalable, reliable,
flexible and field deployable binary solution that provides the basic
building blocks for developing a media server. It is a carrier-grade
solution that resolves the typical challenges faced in media server
deployments. ‘nexGen SS7’ solution provides both SS7 and SIGTRAN
protocol functionalities and can therefore be positioned in existing SS7
networks, as well as in upcoming SS7-over-IP networks. It encapsulates
all SS7 related functionalities and allows media server developers to be
totally focused on the application. It makes media server investments
future proof by allowing easy modification to include value-added
services in the IN domain.
FSS has an outstanding track record of successful deployments in
multiple networks by multiple customers. It is a well-known name in the
signaling space and its signaling solutions stacks are field-proven and
stable.

The increasing adoption of voice-enabled services in the wireless domain

demands a continuous scaling up of existing platforms. The demand for
such services has grown beyond expectations and the media servers
deployed in networks around the world are not designed to handle such
high traffic. As a result, operators are looking towards next generation
platforms that are scalable enough to meet the growing traffic demands
for voice services.

Although there is a global migration towards IP-based networks, the

existing SS7-based networks continue to be the major revenue sources for
operators. As such, there is a growing demand for next generation
SS7-based media servers, which can enable operators to provide
value-added voice services on their existing networks.

Tec h n o l o g y I n n ovat ion Pe ople

 White Paper
Media Server
2. Media server
2.1 Challenges faced by operators
Some of the challenges faced by operators in deploying media servers
include
- Providing scalability
The biggest challenge that any media server deployment faces is that of
scalability. Media servers have a limit on the number of connections, the
bit rate, and the disk space available to house streaming content. A media
server may work fine initially when it is serving the subscriber base for
which it was built. However, as subscriber traffic increases with time, it
will face multiple problems like loss of service, reduced quality,
unavailability of value-added services etc. All this leads to loss of revenue
for the operator and directly impacts customer goodwill.
This issue can be resolved in three ways –
- build a new solution after a few years, catering to the new demand
- build a massive solution initially so that it will be adequate even after a
number of years
- build the solution on a flexible platform that can be scaled up or down
depending on subscriber traffic
The first option will lead to a loss of all initial investment and require a
recursive high investment, drastically reducing the operator’s roIe. The
second option will demand massive investments from year 0. The
revenues obtained will be much less in the initial years. This could result
in a stretched break-even period and a delay in real profits, so much so
that the business case becomes unviable. The third option is the most
suitable one; it will reduce the initial investment, accelerate profits and
require a smaller investment in the future, since the media servers will
need to be upgraded, not replaced altogether.
- Providing reliability
Reliability is another major challenge for carrier-grade media servers. Lack
of service availability or downtime in case of system crashes directly
impacts operator revenue. Media servers have to be built on platforms
that provide inherent reliability.
- Providing flexibility
A media server deployment has to be flexible enough to adapt itself to
network requirements. Requirements for media servers change with time.
A media server may be purely SS7-based in the beginning, but would in all
probability need to provide IP connectivity later on. It may be acting as a
service node initially, but could be required to take care of IN connectivity
down the line. All these issues require the base platform of the media
server to be flexible.
Techno l og y Innovat io n Pe op le
- Providing high performance
The performance requirement of a media server is directly proportional
to the number of subscribers as well as the extent of usage by
subscribers. Handling peak hour traffic is one of the major performance
challenges confronting any media server. This requires a high
performance base platform controlling the signaling, in addition to an
optimized media processing application running on top.
2.2 Media server - network positioning
A media server is a service node that provides media functionality and
resources to the network. Media servers enable basic voice operations
such as playing and recording voice files, DTMF detection, IVR, automatic
speech recognition and Text to Speech. These operations can be
combined in a call to create different value-added services. Depending
on their functional capabilities and interfaces, media servers can be
broadly classified as:
- Service node
A service node is a complete application server in itself. Besides providing
media resources and operations, it also contains service logic to provide
different services. It interfaces with the switching nodes in the network
through a control interface (for example, ISUP over MTP3 in the case of
SS7). This is depicted in Illustration 1-1.
Wireline
network
SS7
Wireline switch
SS7
Radio Access
network SS7
Switch
MSC
Media Server
Illustration 1-1. Service node
- Intelligent network media server
This media server provides media operations to the network. It is service
agnostic and not contain logic for implementing any service. This media
server is controlled by the control points that host the services. The
media server exposes two types of interfaces – the Control Interface and
the User Data Interface.
 White Paper

2.3 Media server – architecture

A media server consists of the following logical functional blocks:

- Control signaling functionality (SF)

Service control
point INAP / CAP / MAP The switch uses the signaling functionality to control the voice
(Over SS7) trunks terminating on the media server. It typically consists of
Wireline
network
SS7 Signaling cards and SS7 protocol stacks ( ISUP over MTP3 and MTP2
Wireline switch
protocol layers ). It also involves managing signaling cards , E1 / T1
SS7
trunks , and SS7 / SIGTRAN connection. It could also consist of
Radio Access
TCAP / MAP / CAP functionality, which provides signaling for IN based
Switch
network SS7 applications.

MSC Media Server

- Media functionality (MF)
Illustration 1-2: Intelligent network media server This consists of media cards that contain DSPs for voice processing
and DTMF detection/generation.

The Control interface is used by the media server controller (typically a - Controlling applications functionality
class 5 switch) to establish and prepare the media server for handling user This consists of controlling applications such as ISUP application /
data (typically voice, video or multimedia). The user data interface is the IP IN applications, which control the setup / termination of voice trunks
interface over which the voice, video or multimedia information is and provides media enriched service functionality like playing or
transferred between the media server and the network. This is depicted in recording of announcements.
Figure 1-2.
Other network
node (Switch) Signaling
Controlling
Media servers typically terminate: functionality
applications
Signaling links
- media bearers for transporting encoded media such as E1/T1/IP. functionality
- signaling links for controlling the media trunks. Media
functionality
Media server
The role of signaling protocol between the media server and the switch is
to allocate and manage resources within the media server to handle user Illustration 1-3: Media server architecture
data. SS7 signaling (ISUP over MTP3/M3UA) is one of the most common There can be a wide variety of media server architectures depending on
and widely used signaling protocols for signaling between media servers the hardware and application requirements. The various architectures
and other network nodes. ISUP provides means of setting up and can be broadly classified as chassis-based or desktop server-based
releasing the voice trunks for media services. (PC-based) solutions.

The media server application can use the additional services of the Mobile - Chassis-based architecture
Application Part (MAP) and CAMEL Application Part (CAP) protocol stacks A chassis-based solution consists of a CPCI/ CPSB/ ATCA chassis hosting
for intelligent network and mobility related applications. These protocols media and signaling cards.
are typically used for media-unrelated signaling between various nodes to
provide value-added services.

- IP-based media server

This media server can be in both wireline as well as wireless domains. In
the wireline world, IP-based media server delivers services to PSTN
subscribers as well as IP terminals. In the wireless world, where the
demand for enhanced voice and video services is even higher, it is used for SBC card SS7 solution
innovative new services like ringback tones, Push-To-Talk or media
messaging. IP-based media server is relatively new in the market but their
demand is expected to grow in the future.
Media card Signaling card running MTP2

6
Illustration 1-4: Chassis-based structure

Tec h n o l o g y I n n ovat ion Pe ople

 White Paper

The chassis-based solution has: For SIGTRAN connectivity, the software architecture for the signaling
- one or more signaling cards hosting MTP2 , on which E1 / T1 signaling functionality of the media server will be as depicted in Figure 1-6.
links are terminated.
- one or more media cards for voice processing, on which voice trunks
are terminated.
- single board computing (SBC) cards hosting the SS7 solution.
APPLICATION User
- controlling applications, which have the flexibility of running either Application
on the SBC cards or on a separate high processing back - end server
as per the system requirements. TCAP Stack
ISUP layers
This type of solution is generally used for high capacity and scalable SCCP
PLATFORM
solutions. The solution can be scaled up by adding more voice or signaling M3UA Signaling
cards SCTP card
IP
- PC-based architecture
This architecture is PC-based and provides a low-cost, low-capacity Illustration 1-6: Media server software architecture for signaling in SIGTRAN
solution. There can be one PC dedicated to signaling only – containing
signaling cards for physical termination as well as the MTP2 protocol stack
along with the applications. Another PC can be used for terminating voice 2.4 Typical requirements
links and would contain media cards for voice processing. As discussed earlier in this chapter, a typical media server needs to be
able to:
Alternatively, the PC-based architecture could consist of one PC containing - cope up with the challenges of scalability, reliability, flexibility and
both signaling cards and media cards along with the applications. The high performance
exact architecture depends on the system requirements and capacity. - keep the overlying media application independent of the base platform
used. Any change in the platform should not require a corresponding
- Software decomposition change in the user application.
A media server consists of two parts – the platform and the application. - migrate seamlessly from SS7 to IP and from IP to SS7. A mediaserver
The platform takes care of the SS7 signaling functionality while the should ideally be built over a platform that offers simultaneous
overlying application processes media. The platform may consist of one of signaling support for both SS7 and SIGTRAN.
more of the following signaling stacks - MTP2, MTP3, ISUP, SCCP, TCAP,
M3UA, SCTP etc

3. nexGen SS7 - an ideal platform for building

For SS7 connectivity, the software architecture for the signaling
media servers
functionality of the media server will be as depicted in Figure 1-5
‘nexGen SS7’ is a carrier-grade platform solution that can provide SS7
signaling functionality over traditional E1/T1 or SIGTRAN networks. It
comes pre-integrated with an easy to use management and
configuration interface and a comprehensive set of APIs. FSS’ ‘nexGen
APPLICATION User SS7’ accelerates the development of network elements by providing
Application
ready to use components that encapsulate all complex signaling
protocol details. It provides ISUP, TCAP, CAP and MAP interfaces for
TCAP Stack
ISUP layers building service node solutions like media servers for intelligent
SCCP networks. Unlike individual protocol stack offerings where a lot of time is
PLATFORM
MTP3 Signaling spent understanding and integrating the various protocol stack
MTP2 card interfaces, ‘nexGen SS7’ provides a fast and cost-effective approach to
building network nodes.
Illustration 1-5: Media server software architecture for signaling in SS7

Te chno l og y Innovat ion Pe op le

 White Paper

nexGen SS7

3.1 nexGen SS7 – resolving issues faced by media

server developers
‘nexGen SS7’ is an advanced SS7 platform that offers solutions to all the
major challenges faced by media server deployments.
- Scalability
Scalability is ensured in the ‘nexGen SS7’ solution by distributing the
functionality of the protocol stacks over multiple nodes. All the SS7 stacks
have been designed so that protocol functionality can be distributed over
multiple instances; the instances co-ordinate with one another and share
network information to project a unified view and single point code to the
network and stack users. Thus, one can initially build a media server with
just one instance of ‘nexGen SS7’, catering to a small subscriber base. The
same system can be scaled up to accommodate millions of subscribers by
using multiple instances of ‘nexGen SS7’. All scalability aspects are
handled by the solution transparently, allowing users to be completely
focused on the media server application.
Controller card running
MTP3 & ISUP running
- Reliability
The ‘nexGen SS7’ platform ensures reliability through its unique
distributed architecture, with multiple active physical nodes
coordinating with one another to process SS7 traffic in load sharing
mode. An active standby architecture ensures system recovery without
loss of stable transactions. The standby node works in a passive mode
where it keeps updating information about the call, without actually
allocating any resources for call processing. N-way redundancy, where
each node is active and at the same time acts as a standby for the others,
optimally utilizes resources but is complex to implement. FSS’ ‘nexGen
SS7’ adopts an intermediate distributed approach where the system
takes care of node failures and ensures optimal utilization of resources.
MTP3 and SCCP are the network layer protocols. Critical information such
as the connection and routing table information is distributed across
multiple nodes to ensure that high availability is achieved. Multiple links
in the linkset terminate on different distributed nodes. Any node failure,
therefore, is reduced to a link failure for the platform. The other active
nodes handle the node failure as they would handle a link failure
according to the SS7 protocol specifications. The architecture therefore
logically takes care of link and node failures. This approach provides
optimal utilization of resources while ensuring system reliability.

Signaling card (8-16 links)

Media card running MTP2 Application Application
(Active) (Standby)

Illustration 2-1: Small media server built over nexGen SS7

TCAP TCAP
(Active) (Standby)

SCCP SCCP
(Active) (Active)

MTP3 MTP3
(Active) (Active)

MTP1 & MTP 2 MTP1 & MTP 2

(Active) (Active)
Controller card running
MTP3 & ISUP running

Signaling card (32-64 links)

Media card running MTP2

STP STP
Illustration 2-2: Large media server built over nexGen SS7

Illustration 2-3: SS7 node with two physical machines

Tec h n o l o g y I n n ovation Pe ople

 White Paper
The below figure shows an SS7 node consisting of two physical machines,
each with one SS7 link, sharing a single point code. The SS7 signaling
layers – MTP3 and SCCP (connectionless mode) – are active on both the
machines and function as a single protocol stack distributed across
multiple physical nodes.
A distributed version of ‘nexGen SS7’ , consisting of multiple instances,
should thus be running on the media server chassis, with each instance
running on one controller card. The multiple instances appear as a single
point code to the network and each of the instances has a complete view
of the network. This architecture takes care of SS7 link failures as well as
physical termination card or node failures (processor failure or software
failure). Whenever one instance fails, the other is still active and can
process signaling traffic, thus ensuring signaling service availability.
Visible as single point code to
the external network
Two instances of ‘nexGen SS7’
running in distributed mode. Service
remains available even if one fails
Illustration 2-4: Carrier-grade reliability in media servers through nexGen SS7
- Flexibility
‘nexGen SS7’ is a flexible solution and ensures that media server
investments are future proof. It provides a rich set of value-added features
that give developers enough flexibility to customize the solution
according to their needs.
Card running One card running
MTP3 and ISUP MTP3 and SCCP
Illustrations 2-5: Different media server configurations with nexGen SS7: service
node and IN applications
Te chno l og y Innovat ion Pe op le
- Flexibility in choosing specific SS7 stack layers
‘nexGen SS7’ contains the whole set of SS7 stack layers, built in such a
way that the user can initially use just a few of them and add the rest
depending on the additional functionality required. Thus, a media server
can be initially built using the MTP3 and ISUP layers for a service code
configuration. Such a configuration includes complete functionality in
the node itself, including media resources, operations and embedded
service logic. IN functionality can be added to the media server later by
using additional layers – SCCP, TCAP, MAP etc. This can be done in a
seamless manner without affecting the overlying application in any
way.
- Integrated SIGTRAN support
With ‘nexGenSS7’, media server developers can seamlessly migrate from
legacy SS7 to IP networks. While the media server can be built for SS7
networks initially, it can be modified to talk to IP networks as and when
required. The FSS solution comes with integrated SIGTRAN support and
makes the application totally transparent to the underlying transport.
- Support for load sharing across combined linksets
A normal SS7 solution offers load sharing across a maximum of
only 16 links. However, the ‘nexGen SS7’ solution’s innovative design
increases the load sharing to as many as 256 links. This makes it suitable
for large media servers handling a vast number of subscribers. The
solution’s load sharing capability also enables media servers to perform
better during peak hours of operation.
- Support for high capacity
‘nexGen SS7’ is ideal for large solutions. It handles the requirements of
large media servers by providing support for upto 1024 destination point
codes, 256 self point codes, 1024 links and 4096 routes.
3.2 nexGen SS7 – value proposition
‘nexGen SS7’ is the ideal platform for building a network deployable
media server.
- it encapsulates all complex protocol functionality, allowing the user
to be focus on the overlying application.
Moreover, the application needs to be built over the platform only once;
no changes are required even if the transport mechanism is changed
from SS7 to IP or vice versa.
- since it is a pre-integrated binary solution, no time needs to be spent
in integrating the various stacks. Also, FSS’ highly interoped and
stable stacks guarantee seamless interoperability with other network
devices.
- it can be scaled up to handle more than 10000 transactions per second.
It offers an excellent price performance ratio.
 White Paper

- it comes with pre-integrated management support in the form of an

element manager. It provides multiple configuration options–for file
based, CLI based and third party based systems. The element manager
is redundant and ensures service availability even in case of failure.
- its scalability helps in reducing capex requirements over time, since
it can be scaled up with minimal overheads and the overlying
application does not need to be rebuilt.
- it is a future proof investment, since it supports easy migration to next
generation technologies like SIGTRAN.
- its highly flexible architecture allows the introduction of new services
as it supports MAP / CAP / TCAP functionality for IN and mobility
management related services.

3.3 Conclusion
FSS’ ‘nexGen SS7’ Signaling platform is a pre-integrated, scalable and
highly reliable solution that can be used to build media server solutions
for legacy as well as next generation networks. It is a truly carrier-grade
offering, based on FSS’ field proven protocol stacks. With features like
SIGTRAN support, multiple network appearance, and high capacity with
support for multiple self point codes, the platform is flexible enough to
cater to varied media server requirements and configurations.

10

Tec h n o l o g y I n n ovation Pe ople

 White Paper
nexGen SS7
‘nexGen SS7’ perfectly meets the present and evolving needs of media
server equipment manufacturers.
This appendix briefly describes the FSS ‘nexGen SS7’ offering and explains
its specific components, functionality and standards compliance.
A.1 nexGen SS7 - components
‘nexGen SS7’ resides on high performance SUN or Linux platforms using
FSS’ distributed SS7 stack. It is a collection of telecommunications
software building blocks as depicted in the figure.
Illustration 7: nexGen SS7 architecture
The various components of ‘nexGen SS7’are:
- SS7 stack layers including MTP3, SCCP and TCAP – TCAP and MTP3
services can be accessed through the API interfaces provided for the
same
- SIGTRAN – M2UA, M3UA and SCTP
- application layer protocols including ISUP, MAP, CAP etc, required for
various applications pertaining to call control, mobility and intelligent
networks
- element manager – This entity provides a management interface to the
‘nexGen SS7’ platform for provisioning / configuration of protocol layers.
The platform can be provisioned in any of the following ways:
- configuration file based management
- command line interface
- a client library interface for development of third party
element manager
11
Te chno l og y Innovat io n Pe op le
A.2 nexGen SS7 - features
‘nexGen SS7’ provides the following rich set of features:
A.2.1 Reliability and scalability
‘nexGen SS7’ is a reliable and scalable solution:
- innovative distribution mechanism to provide high calability and
reliability for node failures
- designed to run multiple copies of SS7 - Sigtran solution software and
handle signaling traffic sharing the same point code. The multiple
copies present a unified network view to the peer SS7 nodes. This
unique architectural approach creates unique advantages in terms of
load distribution, scalability and reliability.
- high power back - end servers run user applications whereas front -
end servers carry all the SS7 signaling traffic.
- both the front-end and back-end servers can be further distributed to
achieve scalability, high availability and increased capacity and
performance. The SS7 - Sigtran solution is able to distribute traffic
among several instances of the application running on back-end nodes.
A.2.2 High capacity
‘nexGenSS7’ can be used to build high capacity signaling nodes.
It provides support for:
- 128 self point codes
- 1024 destination point codes
- 2048 links
- 256 link-sets
- 4096 route sets
A.2.3 Rich protocol features
‘nexGen SS7’ provides support for:
- multiple self point codes
- combined linksets for load sharing on links across linksets
- Multiple Network Appearance (MNA) based on multiple Network
Indicators (NI) (national / international) and variants (ITU, CHINESE,
and ANSI)
- multiple SS7 variants ( ANSI, ITU and Chinese ) simultaneously
- hybrid stack combinations, comprising ANSI TCAP over Chinese SCCP /
MTP and Chinese TCAP over ANSI SCCP/MTP
- support for High Speed links (HSL)
- SIGTRAN ( M3UA / M2UA / SCTP ) connectivity (ASP or IPSP) with its
network peers
A.2.4 Comprehensive APIs
‘nexGen SS7’ provides an easy to use set of APIs:
- APIs are available at MTP3, SCCP and TCAP levels of the SS7 protocol
stack. These APIs provide SS7 Services to the Service User.
 White Paper

- APIs are available at the application level for MAP and ISUP.
- Function - based Management APIs (client library) that can be integrated
with Client Applications such as CLI, client database or SNMP agent are
available. The Client library provides an easy - to - use ‘C’ structure-based
interface.

A.2.5 Integrated management support

‘nexGen SS7’ includes:
- extensive support for configuration, provisioning and management
information to all the stack instances
- support to be configured/provisioned in the following ways:
- configuration/provisioning file
- command Line Interface (provided with ‘nexGen SS7’)
- open APIs to dispatch Alarm/events to the User Management
Application
- centralized, system-wide configuration manager for
configuring all the subsystems of the distributed system. This
enables simpler and faster system configuration
- open management interface to enable users to develop their
own customized management front-end

A.2.6 Diagnostics
‘nexGen SS7’ supports extensive diagnostics in the form of traces, alarms,
events and a logger entity that makes it an ideal environment for
application programming.

A.3 nexGen SS7 - standards compliance

‘nexGen SS7’ conforms to the following standards:

- SS7
- ITU Recommendation for TCAP Q.771 to Q.774(1996)
- ANSI Recommendations for TCAP T1.114.1 to T1.114.4(1996)
- ITU Recommendation for SCCP Q.711 to Q.714 (1996)
- ANSI Recommendation for SCCP T1.112(1996)
- ITU-T Recommendations for MTP3 Q.701 to Q.704(1993)
- ANSI Recommendation for MTP3 T1.111.4 (1996)
- Chinese Variant supports 24 - bit point code over ITU
procedures
- ITU-T Recommendations for ISUP Q.761 to Q.764
- ANSI Recommendation for ISUP T1.113

- SIGTRAN
- RFC 3332 for MTP3 User Adaptation Layer (M3UA)
- RFC 3331 for MTP2 User Adaptation Layer (M2UA)
- RFC 2960 for Stream Control Transmission Protocol (SCTP)

12

Tec h n o l o g y I n n ovation Pe ople

 White Paper

Flextronics Software Systems (formerly Hughes Software

Systems-HSS ) is a global end-to-end communications
solutions provider with over 250 customers worldwide, in
the telecom infrastructure and handsets, c ommunication
service providers, systems integrators and independent
software vendors space. It is a part of Flextronics, which
has engineering, manufacturing and logistics operations
in 32 countries spread over five continents. Flextronics
Software Systems has development centers across India
and Germany and associate companies in the Ukraine
and South Africa. It also has sales offices in more than 10
locations worldwide.

United States United Kingdom

1-866- 477-0247 +44-208-6223859
(301)-212-7988

Germany Japan
© 2005 Flextronics Software Systems

+49-160-972-18125 +81-90-9370-9579
+49-911-2527-414 +81-33-5160091

India
+91-124-2455151

w w w. f l ex t ro n i c s s o ft wa re . co m