Aricent Leaders in Communications Software - Aricent
 
HomeAbout UsProductsOutsourcing ServicesSolutionsSupport
Partners Partners  Careers Careers  Locations Locations  Contact Us Contact Us  
          
  Overview
  IMS
  GPRS/UMTS Stacks
  SIGTRAN & SS7
  Access Stacks
  VoP Stacks
  Datacom Stacks

Your Location : Home > Protocol Stacks > SS7 > SS7 Related Products


SS7 Overview | SS7 Features | SS7-Aricent Deliverables | SS7 Related Products
| Distributed SS7 | SS7 FAQ


Distributed SS7 stack

Distributed SS7 stack from Aricent provides a highly fault tolerant and scalable implementation of the SS7 protocol. Aricent DSS7 stack enables OEMs to meet stringent reliability and performance requirements demanded by Network Operators.

The SS7 stack instances can be run on distributed nodes in load sharing mode for handling heavy traffic. A new node can be added at run time to scale up the system without bringing down the rest of the nodes resulting in highly scaleable system.

The load is distributed across all the instances and in case one of the stack instance goes down, the system automatically redistributes the load across the remaining instances. When the failed instance recovers, it also becomes a part of the distributed system. Information amongst various instances is exchanged to ensure a consistent and updated database.

Distributed SS7 Stack
Distributed SS7 Stack

Various features of the distributed SS7 stack are:

  • Fault Resilient: In the event of failure of one instance, the other instances continue working, i.e., the impact of failure of an instance is minimal from the point of view of the stack users and the peer nodes on the network. However existing contexts with that instance will be lost.
  • Load balancing: The load from the user part and external world is distributed among multiple instances of stack evenly. If an instance fails or a new instance comes up, the load is redistributed and this redistribution is preformed without interrupting the ongoing operations.
  • Unified View: The stack provides a unified view to the network and user part. The network nodes are transparent to the distribution at the distributed node and view the distributed nodes as a single node only.
  • Minimum cross Traffic: The cross traffic is avoided between different instances of the stack as far as possible.
  • Highly Scalable: Provides capability of addition and deletion of stack instances dynamically at run time.

To know more about Aricent SS7 Stack, browse through the SS7 FAQ.

The distribution in the Aricent SS7 stack is achieved with the help of three entities –

  1. Downstream Message Router (DMR) library
  2. Upstream Message Router (UMR) library and
  3. Health Manager

The design is kept to have a minimum impact in the core functionality of individual layers.

Every stack layer is associated with two distribution libraries, known as Upstream Message Router (UMR) and a Downstream Message Router (DMR).

The DMR library functionality invoked by distributed stack instance user, is used to distribute traffic to the various lower stack instances.

The Upstream Message Router is used to distribute the messages coming from the network to various stack instances

The algorithm used in DMR and UMR libraries for distribution is configurable.

Health Manager takes care of monitoring the status of various stack instances and coordinating proper functioning of distributed stack. This Health Manager also keeps track of any new instances added in the system as well as instance failure and reports status change to all other stack instances.



Distributed SS7 Stack

In the figure above for the Nth Layer, UMR Library linked with Nth layer is the Message router library that will route the message to appropriate instance of n+1 layer. Similarly DMR Library linked with Nth layer will send the message to the appropriate N-1th instance.




Last updated : March 17, 2006

 

Customer Quote
  Case Studies
  Press Releases
  Whitepapers
  Partners