Browse Prior Art Database

Virtual call server to determine the correct entity in a cluster when all cluster members have the same signaling point code

IP.com Disclosure Number: IPCOM000131673D
Original Publication Date: 2005-Dec-10
Included in the Prior Art Database: 2005-Dec-10
Document File: 2 page(s) / 136K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

In SS7 network environments (SS7, Signalling System number 7), each signalling node is expected to have its own signalling point code (OPC). These point codes are used as addresses when SS7 signalling message units are exchanged between such signalling nodes. These signalling point codes, used for message routing, have to be administered as destinations in static routing databases. Changing the addresses requires significant administration effort to update the static routing databases in the network. Because of several reasons (e.g. redundancy issues, capacity increase issues, etc.), a new signalling node is introduced for the SS7 network which has the same OPC as an existing network node. In this configuration both nodes have the same signalling point code and they form a cluster or pair. The benefit of this approach is that the new node can be introduced in the network without the need to change the static routing databases in the rest of the network. A problem that goes along with this concept is that SS7 signalling message units may end up at the "wrong node" within the cluster / pair since all members have the same OPC.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

S

Virtual call server to determine the correct entity in a cluster when all cluster members have the same signaling point code

Idea: Michel Van Craenendonck, BE-Herentals

In SS7 network environments (SS7, Signalling System number 7), each signalling node is expected to have its own signalling point code (OPC). These point codes are used as addresses when SS7 signalling message units are exchanged between such signalling nodes. These signalling point codes, used for message routing, have to be administered as destinations in static routing databases. Changing the addresses requires significant administration effort to update the static routing databases in the network.

Because of several reasons (e.g. redundancy issues, capacity increase issues, etc.), a new signalling node is introduced for the SS7 network which has the same OPC as an existing network node. In this configuration both nodes have the same signalling point code and they form a cluster or pair. The benefit of this approach is that the new node can be introduced in the network without the need to change the static routing databases in the rest of the network.

A problem that goes along with this concept is that SS7 signalling message units may end up at the "wrong node" within the cluster / pair since all members have the same OPC.

For bearer-unrelated SS7 messages that are routed to a called party number, an alternative method can be applied: The solution is to pass these messages to a special routing function before they become handed off to the local SS7 application. This special routing function, a virtual call server, pe...