The Aricent SIGTRAN (Signaling Transport) Suite is a
set of protocol stacks for transporting signaling information over
packet-based networks. The IETF SIGTRAN-defined SCTP is the key transport
component in the distributed Voice over Packet (VoP) architecture, and the
FSS SCTP implementation can be integrated into signaling gateways, media
gateway controllers, and IP-based service control points to develop
convergent voice and data solutions.
The SIGTRAN Suite from Aricent includes the Stream
Control Transmission Protocol (SCTP) and user adaptations SUA (SCCP user
adaptation layer), M3UA (MTP3 user adaptation layer), M2UA (MTP2 user
adaptation layer), M2PA (MTP2 Peer-to-Peer adaptation layer), IUA (ISDN
Q.921 user adaptation layer) and Voice over Packet software. These products
provide a complete set of building blocks for quickly developing
next-generation solutions that meet the strictest requirements for
redundancy, scalability and reliability.
Aricent’s Companion Lifecycle Services
The majority of Aricent’s products are delivered with
tailored combinations of our Lifecycle Services, including Global Innovation
and Design, Product Development, Testing and Certification, Network
Engineering, Maintenance and Support, and Business Operations and Systems
Integration. Aricent’s engineers and consultants have successfully completed
thousands of services engagements globally using flexible delivery models
ranging from on-site to off-shore. Aricent’s services offer deep
communications domain expertise, cost and time efficiencies, quick ramp up
and contemporary commercial engagement models including end-to-end
commitments.
Architecture
The SIGTRAN suite’s functions can be divided into SCTP
stacks and protocol stacks for Adaptation Layers.
SCTP is responsible for reliable signaling transport,
streaming, congestion avoidance and control, bundling and un-bundling,
multi-homing and association management, security and user-transparent fault
management. The adaptation layers (M3UA, M2UA, M2PA, IUA and SUA) transport
the signaling information from the corresponding signaling layers (MTP3,
MTP2, Q.921 and SCCP) using SCTP services.
SCTP
- Based on RFC 2960
- Conformance to SCTP implementer's guide
draft-ietf-sigtran-tsgwg-sctpimpguide-08.txt
- Ordered and un-ordered delivery
- Includes user-data segmentation and bundling
- Offers protection against masquerade, fraud and
repudiation
- Supports TCP congestion control (for delayed
acknowledgement) as per RFC 2581
- Supports multi-homing and multi-streaming features
- Path MTU discovery - ECN capable
- Provides generic interface to support
non-signaling applications
- Simultaneous IPv6 and IPv4 support
- Socket Interface support as per draft
draft-ietf-tsvwg-sctpsocket-07.txt
- SCTP MIB supported as per
draft-ietf-sigtran-sctp-mib-10.txt
- Dynamic addition of IP address supported as per
draft-ietf-tsvwg-addip-sctp-07.txt
- CRC32C checksum as per RFC 3309 and Adler32
checksum as per RFC 2960 are supported
- Stream Control Transmission Protocol Applicability
Statement draft-ietf-sigtran-sctp-applicability-08.txt
- Next release to be based on following:
- SCTP Sockets mapping
draft-ietf-tsvwg-sctpsocket-08.txt
- SCTP Management Information Base using SMIv2
draft-ietf-sigtran-sctp-mib-10.txt
- draft-ietf-tsvwg-sctpimpguide-10.txt
- Draft draft-ietf-tsvwg-addip-sctp-09.txt
- IPSec support in the SCTP protocol.
- Implementation of the partial reliability
draft
User Adaptations
·
Supports ASP, SGP level redundancy
·
Can be configured for ASP, SG or IPSP
elements
·
Provide status indications to management
·
SCTP association and stream management
·
IPSP-IPSP communication supported
·
Based on RFC 3332 and implementation guide
version 4 draft-ietf-sigtran-m3ua-implementors-guide-04.txt>
·
Supports transfer of SS7 MTP3 user part
messages for ISUP, SCCP,TUP
·
Supports Dynamic Routing Key registration
procedure
·
Highly versatile message distribution based
on DPC/OPC/CIC/SIO
·
Interworking and compatibility with ANSI, ITU
and Chinese variants of MTP3
·
Congestion Control Mechanism per MTP3 Q.704
procedures
·
Default AS & ASP routing
·
Coexistence of SGP, ASP, IPSP in the same
M3UA Instance (FlexiServer)
·
Indication queue mechanism
·
Multiple SCTP support
·
Next release to be based on RFC 3332 and
draft-ietf-sigtran-m3ua-v02-00.txt >
·
Based on RFC 3331
·
Maintains interface ID to SCTP
association/stream mapping
·
Support for congestion control
·
Support for Dynamic Routing Key registration
procedures
·
Support for Override, Loadshare and Broadcast
mode of ASP
·
Based on RFC 3057 and implementation guide 01
·
Supports Q.931/Q.921 interface
·
Configurable to function as both SG and ASP
·
Supports dynamic configuration of stack
parameters like times etc
·
Support for handling congestion indications
from SCTP
·
Maintains interface ID to an SCTP
association/stream mapping
·
Based on draft-ietf-sigtran-m2pa-06.txt
·
Supports MTP3-MTP2 interface
·
Support for each link to be configurable as
either SCTP client or SCTP server
·
Maintains signaling link to SCTP association
mapping
·
Support for handling congestion indications
from SCTP and also M2Pa’s own congestion handling
·
Next Release to be based on
draft-ietf-sigtran-m2pa-12.txt
·
Based on draft-ietf-sigtran-sua-016.txt
·
Supports S7AP-SCCP interface
·
Supports transfer of SCCP User Part Messages
for TCAP, RANAP and RNSAP
·
Support for SCCP protocol classes 0, 1, 2 , 3
·
Support for Dynamic Routing Key registration
procedures
·
Relay functionality is supported
·
Congestion handling
·
Multithreading is supported
·
Statistics are maintained as Per Q.752
·
Flexible API invocation mechanisms, either
function based (stack as library) or message based (stack as task)
·
Portable, modular, easy to customize, MT safe
and run-time configurable
·
Well-defined and documented interfaces to the
stack (APIs)
·
Integrated, tested and verified with
Aricent’s SS7 stack layers
·
Supports all features needed by 3G networks
·
ASP, SG and IPSP configurations
·
Client and server support
·
Single/Multi-threaded support for higher
performance
·
Redundancy support
·
Complete Suite; SCTP, M3UA, M2UA, M2PA, IUA
and SUA
The Aricent SIGTRAN suite has highly configurable
run-time and compile-time capacity related options. Moreover, the SIGTRAN
suite can be used either as a library with a client application or as an
independent module communicating with multiple applications.
·
Aricent successfully participated in the ETSI
2nd SIGTRAN interop held in France in September 2002 and 2003, with all UAs
(i.e. M3UA, M2UA, M2PA, IUA, SUA). Aricent also authored the
interoperability test plans for M3UA, SUA and IUA.
·
Aricent successfully participated in the ETSI
M3UA interop based on draft version10 in February 2002. FSS authored the
test cases for this event
·
Aricent successfully participated in the 1st
SUA v08 interop held in Belgium in November 2001 organized by Siemens.
Aricent participated with both SG and ASP sides of the implementation
·
Aricent’s M2PA stack was represented in the
1st M2PA v03 interop held in November 2001
·
Aricent successfully participated in the 3rd
SCTP Bake-off (for RFC 2960), which was held at European Telecommunications
Standards Institute (ETSI) facilities at Sophia Antipolis, France from 23-27
April, 2001. Aricent participated with both the ASP and SG sides of the
implementation
·
Aricent successfully participated in the SCTP
ver 13 interop in October, 2000
·
Aricent successfully participated in the 1st
M3UA bake-off, held in Madrid, Spain, organized by Ericsson (Spain) from May
7-11, 2000. We participated with both SG, ASP sides of the implementation
·
Source Code for SCTP, M3UA, M2UA, IUA, M2PA
and SUA containing:
o
Core Stack Build
o
Client Library
o
OS Wrappers for Solaris, VxWorks, Linux,
WinNT
·
Implementer's guide (User manual and porting
guide)
·
API documents
·
Protocol Implementation Conformance Statement
(PICS)
·
Warranty and annual support plans
·
Training and on-site consultancy
·
Turnkey integration and porting service