Re: RFC 4666 M3UA - Reg Request Message

Jitin,

Bhandari, Jitin (Jitin) wrote:                (Tue, 07 Nov 2006 11:20:39)
> Brian,
> 
> Here are some of the issues/questions I have with LOADSEL, NTFY procedure
> for handling CIC ranges:
> 
> 1. Brian in his previous emailed mentioned about defining Single AS for all
> ASPs handling CIC ranges for same DPC (from Routing Key). This would also
> mean that all ASPs in this AS are in loadshare mode. Is it true?

Yes and no.  Please read the summary in section 1.4.2 of the draft.

> Can the
> model of LOADSEL also further support Override mode for CIC ranges?

Yes, please read the summary in section 1.4.2 of the draft.

> It's very typical to have equipment redundancy in networks at ASPs level and
> one would need Override mode for redundant ASP pairs where as Loadshare mode
> is needed to support the LOADSEL scheme at different CIC level. A quick
> example would be ASP-1 and ASP-2(Override mode) supporting CIC range 1-100
> for DPC-X and ASP-3 and ASP-4 (Override mode) supporting CIC range 500-1000
> for DPC X.  Is this model supported? Please clarify.

Yes, this is an Override AS as described in summary section 1.4.2 of the
draft.

Because you seem to have not read the summary section that provides an
overview of the method, it appears that you have not read the draft.

> 
> 2. I see in the email exchange that we have been talking about either:
>     a) Sending ISUP messages destined for ASP (which is down) to a Default
>     ASP. What would default ASP do? Keep in mind, CICs are physical
>     resources and are usually mapped to One (or two in override mode) ASP.
>     How do you expect the default ASP to know the Status of CICs which is
>     not assigned to it during provisioning? Are we expecting all resources
>     (CICs) to be assigned to default ASP? Are we expecting General
>     procedures out of this default ASP? If yes, then why send it to this
>     default ASP instead handle it at SG?

This is not new for LOADSEL, I was speaking directly to section 1.4.2.4 of
RFC 4666 which says:

  "Normally, one or more ASPs are active (i.e., currently processing
   traffic) in the AS, but in certain failure and transition cases it is
   possible that there may be no active ASP available.  Broadcast,
   loadsharing, and backup scenarios are supported.

   When there is not matching Routing Key entry fro an incoming SS7
   message, a default treatment MAY be specified.  Possible solutions
   are to provide a default Application Server at the SGP that directs
   all unallocated traffic to a (set of) default ASPs, or to drop the
   message and provide a notification to layer management.  The
   treatment of unallocated traffic is implementation dependent."

The default ASP(s) can also be local (internal) to the SG.

--brian

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/