Re: [Sigtran] Number of links towards a DPC (ITU)

"Brian F. G. Bidulock" <bidulock@openss7.org> Fri, 14 June 2013 21:55 UTC

Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0CB221F9ABA for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 14:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGsRABKF72Pz for <sigtran@ietfa.amsl.com>; Fri, 14 Jun 2013 14:55:09 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by ietfa.amsl.com (Postfix) with ESMTP id E343921F9A93 for <sigtran@ietf.org>; Fri, 14 Jun 2013 14:55:07 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5ELt4A0028622; Fri, 14 Jun 2013 15:55:04 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r5ELt4Ju002763; Fri, 14 Jun 2013 15:55:04 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id r5ELt4ff002762; Fri, 14 Jun 2013 15:55:04 -0600
Date: Fri, 14 Jun 2013 15:55:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Arvind Kumar <arvindverma77@gmail.com>
Message-ID: <20130614215503.GA966@openss7.org>
Mail-Followup-To: Arvind Kumar <arvindverma77@gmail.com>, sigtran@ietf.org
References: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAE4qXDFfy+7BycUNrWNGm=Lo4U=WMZH9FDjw1kqWy71nKNbEhw@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Number of links towards a DPC (ITU)
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 21:55:13 -0000

Arvind,

ITU has a 4-bit SLS and a 4 bit SLC.  The SLS and SLC is shared under
ITU and ITU does not do SLS rotation.  Therefore, because 1 bit is used
for link-set selection, there can only be 8 links in a linkset (16 links
in a combined linkset).

ANSI has an 8-bit SLS and a 5-bit SLC.  The SLS and SLC are not shared
and ANSI does SLS rotation.  Therefore, it is possible to have 32 links
in a linkset (64 links in a combined linkset).  Using the old 5-bit SLS
it was only possible to have 16 links in a linkset and 32 links in a
combined linkset because 1 of the 5 bits was used for linkset selection
within a combined linkset.

So, there are two considerations: SLS and SLC size.  The most links in a
link set is restricted by the size of the SLC (the number of signalling
links that can be identified between two signalling point  codes);
however, the combined linkset is also restricted by the SLS size (over
how many distinct signalling links can the traffic be distributed).

That said, signalling links are identified by the 3-tuple PC-PC-SLC.
Just because you have multiple PCs on a signalling point does not
necessarily increase the number of signalling links that it can support.
So, if you have 4 PCs, it does not necessarily mean that you can support
4 times as many signalling links.  It is common, for example on a class
5 switch, to provide 1 primary PC that is used in management messages on
signalling links and 3 additional ones (in our example) that are only
aliases (that is, messages can be routed to them but they do not
participate in signalling link management messages).

Some stacks; however, are also capable of supporting multiple signalling
points.  In which case, each primary PC can act as a completely
independent signalling point with its own set of signalling links.  SS7
network operators do no like connecting to systems where multiple
independent signalling points are implemented on the same hardware.

If you need a lot of signalling links for capacity, broadband (or
better, M2PA) signalling links can be used.  In the case of M2PA, the
signalling capacity is not dependent on the number of signalling links
and only a pair of signalling links is required (and recommended).

--brian

Arvind Kumar wrote:                        (Fri, 14 Jun 2013 14:09:27)
>    Hi All,
>    Would appreciate if somebody help me,
>    I have SS7 Stack with multiple OPC, I would like to create multiple
>    linksets towards a single destination (suppose 2000).
>    How many links are possible in all the link-sets. I know there is no
>    limitation of number of link-sets, but as I  understood, towards a
>    given destination the maximum number of links depends upon maximum
>    value of SLS.
>    For ITU it could be 16.
>    But my doubt is I have mutiple OPCs for my SS7 Stack, could number of
>    links  be possible
>    = number of OPCs * 16
>    Please comment.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/