vlr+hlr: Insert Data

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Mon Feb 27 12:56:57 UTC 2017


On Mon, Feb 27, 2017 at 10:47:43AM +0100, Tobias Engel wrote:
> On 13.02.17 08:13, Jacob Erlbeck wrote:
> > On 02/09/2017 02:53 PM, Neels Hofmeyr wrote:
> >>
> >> What should we do if the HLR sends no Insert Data?
> > 
> > I did not find much in 29.002 that tells otherwise. There is only figure
> > 19.1.1/3 which states that the insert messages are not optional by not
> > using italics. The automatons in 19.1.1/6 and 19.1.1/13 do not impose
> > such a restriction.
> 
> By the way: Both updateLocation and updateGprsLocation have a
> skipSubscriberDataUpdate flag, which tells the HLR to skip the
> insertSubscriberData procedure.
> 
> From 29.002 8.1.2.3:
> 
> Skip Subscriber Data Update
> The presence of the parameter is optional and if present it indicates
> that subscriber data download during the updateGprsLocation procedure
> may be skipped by the HLR e.g. because the service is solely used to
> inform the HLR about change of IMEISV. The parameter is used to optimise
> signalling load during Location Update procedure.

Interesting, thanks!

It seems the VLR should have an intention of whether it wants to receive
subscriber data or not. I guess for now our VLR's intention is to always
receive subscriber data, i.e. so far we can reject LU if missing.

~N

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170227/fb3ef89f/attachment.bin>


More information about the OpenBSC mailing list