Eagle: G-Flex MLR Feature - Loadsharing Behavior

Asset ID:	1-72-2388420.1
Update Date:	2018-04-24
Keywords:

Solution Type Problem Resolution Sure

Solution 2388420.1 : Eagle: G-Flex MLR Feature - Loadsharing Behavior

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.5 and later
Information in this document applies to any platform.

Symptoms

Messages which are defined to be routed to a specific HLR point code, as part of G-Flex MAP Layer Routing and RTDB definition, are being load shared across multiple destinations.

Changes

Cause

HLR point code returned as part of G-Flex service invoke (s-01111) is part of a MAP set with equal RC.

MAPSET ID=DFLT MRNSET ID=---- MRNPC=-----------
  PCN Mate PCN SSN RC MULT SRM MRC GRP NAME SSO WT %WT THR
  s-01111 6 10 SHR *N *N -------- OFF 8 8 1
  s-02222 6 10 SHR *N *N -------- OFF 8 8 1
  s-03333 6 10 SHR *N *N -------- OFF 7 7 1
  s-04444 6 10 SHR *N *N -------- OFF 7 7 1
  s-05555 6 10 SHR *N *N -------- OFF 12 12 1
  s-06666 6 10 SHR *N *N -------- OFF 13 13 1
  s-07777 6 10 SHR *N *N -------- OFF 12 12 1
  s-08888 6 10 SHR *N *N -------- OFF 13 13 1

Solution

As part of G-Flex MAP Layer Routing feature, if RI=SSN and the translated Point Code is part of a MAP set, traffic will be load-shared with the other SPs in that set (if same RC is configured).
If RI=GT and the translated Point Code is part of a MRN set, traffic will be load-shared with the other SPs in that set (if same RC is configured).

In below configuration, the first scenario applies, the entry that is found in the RTDB as a result of G-Flex service selection for a specific IMSI has PC=1111 (part of a MAP set with the same RC) and RI=SSN. As a result, messages are routed to the other PC as well (s-02222,s-03333,...)

IMSI EntIdx IMEI Index
xxxxxxxxxxxxxxx H'00000330 H'ffffffff

  Entity Address Type PC(NATL-aa) RI SSN TT NP NAI DA
1111 SP s-01111 SSN 000 000 00 000 none

  SRFIMSI NSSN CCGT NTT NNP NNAI
  no no no no no

Attachments

This solution has no attachment