Project

General

Profile

Feature #3019

add config for number of auth tuples returned

Added by neels over 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
03/01/2018
Due date:
% Done:

0%


Description

by default osmo-hlr returns 5 auth tuples to any client requesting tuples (MSC, SGSN).
Allow configuring the number of tuples returned.

Rationale: the nr of tuples cached by the MSC / SGSN are a tuning detail allowing a tradeoff between HLR DB traffic and quick turnaround of the cached data in the MSC / SGSN.

History

#1 Updated by neels over 1 year ago

Related thought: should the HLR notify the connected clients of change in subscriber data?
i.e. entering a new Ki causes some GSUP message sent from the HLR to clear the auth cache?

#2 Updated by laforge over 1 year ago

Hi Neels,

On Thu, Mar 01, 2018 at 12:35:07PM +0000, neels [REDMINE] wrote:

Related thought: should the HLR notify the connected clients of change in subscriber data?

of course. This has always been the case in GSM, and I actually assumed we would be doing
this until I witnessed the issues at 34C3, where no InsertSubscriberData was performed when
the MSISDN is changed in the HLR.

There's a related task, #2785, assigned to you two months ago, very
recently re-assigned to stsp. So you should know about this :)

i.e. entering a new Ki causes some GSUP message sent from the HLR to clear the auth cache?

Key data is not supposed to change and is not part of "Subscriber Data"
stored in the HLR as per 3GPP specs. So there is no procedure in 3GPP
which covers that situation. I also don't think it's worth for us
spending time on desinging a non-standard mechanism for it.

#3 Updated by laforge about 1 year ago

  • Priority changed from Normal to Low

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)