M3UA needs a chapter on its own.
A new section on M3UA
Route :
Before Payload Data from M3UA-user can be transfered to peer, user has to
define the route based on Destination Point Code (DPC), Originating Point Code
(OPC) and Service Indicator (SI). Look at section 5.5.2.11 to understand how to
add route. While DPC is mandatory and should be actual value, OPC and SI can be
-1 indicating wild card. Below table shows an example of a routeset table. The
routeset table contains routesets for all of the possible destinations that can
be reached. The table is searched to find a match for the DPC:OPC:SI to be
routed. If a match is found in the list of As, a As is chosen from the
available routes associated with the routeset. If As is not found SI is
substitued with -1 (DPC:OPC:-1) and match is found. Still if As is not found
OPC is substituted with -1 (DPC:-1:-1) and match is found. If no As is found,
MSU is dropped and no routing takes place.
DPC | OPC | SI | AsName
2 | 3 | 2 | AS1, AS2
2 | 3 | -1 | AS1, AS2
4 | -1 | -1 | AS3
Load Sharing
The SLS field of Protocol Data carried in Payload Data Message is used for M3UA
load-balancing.
M3UA can be configured to
1) load-balance between Application Servers (AS) for given route. For any given
route there can be maximum 16 AS defined.
2) within AS load-balancing between Application Server Process (ASP). Maximum
128 ASP's can be defined within AS for loadshare.
For even distribution of messages on the network its suggeted to define the
even number of As for a route for load sharing. Proper care should be taken to
decide on number of As's for route and number of Asp's in As depending on
routing lable format of MSU.
M3UA can be configured to use highest or lowest bits of SLS for AS selection.
The number of SLS bits used for As selection depends on number of maximum As
defined for a route. The remaining bits are used for Asp selection
Max As for route | Number of SLS bits used for As | Max Asp's that can be used
within As
1 or 2 | 1 | 128
3 or 4 | 2 | 64
5 to 8 | 3 | 32
9 to 16 | 4 | 16
Original issue reported on code.google.com by amit.bha...@gmail.com on 10 Jan 2013 at 3:02
Original issue reported on code.google.com by
amit.bha...@gmail.com
on 10 Jan 2013 at 3:02