RNC-Id and LAC both present in InitialUE msgs

Neels Hofmeyr nhofmeyr at sysmocom.de
Tue Apr 5 12:03:54 UTC 2016

More on the pairing of RNC-Id and LAC:

We've discussed that the CN should be manually configured for which RNC-Id
belongs to which LAC, in order to find the correct SUA link to page on
upon having the to-be-paged subscriber's LAC.

Turns out: even though only the RNC-Id is sent in the id-Reset message,
both the RNC-Id *and* the LAC are transmitted in an InitialUE message.

So we can actually record the LACs as well as the RNC<->LAC mappings from
the InitialUE messages (like Location Update Request) and don't need to
configure them manually.

Does that sound reasonable?

We can still keep the manual vty config of RNC<->LAC mappings to detect
errors in the field configuration from InitialUE messages.


- Neels Hofmeyr <nhofmeyr at sysmocom.de>          http://www.sysmocom.de/
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
-------------- 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/20160405/60aee899/attachment.bin>

More information about the OpenBSC mailing list