osmo-iuh[master]: fix osmo-hnbgw HNBAP: different RNC Id for each hNodeB

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/gerrit-log@lists.osmocom.org/.

Neels Hofmeyr gerrit-no-reply at lists.osmocom.org
Mon Dec 11 12:35:55 UTC 2017


Patch Set 1:

> I think qthis is just a hack that clutters around the assumption
 > that there is always only one lac per RNC :/

ok hold on, the RNC ID identifies the HNB-GW, not the RNC inside the hNodeB, right? Looking at 25.469 9.2.26

  RNC-ID Uniquely identifies the HNB-GW towards the CN on a particular Iu interface.

I was pretty sure that each hNodeB has its own RNC Id and was a bit confused why the hnbgw has to deal one out.

So the real solution then is in the iu client code to be able to manage several LACs per RNC Id, i.e. being able to connect multiple HNBGW each having one RNC Id, each in turn being able to serve multiple hNodeBs with a different LAC each...

-- 
To view, visit https://gerrit.osmocom.org/5264
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I5ea89ebe60b2afc31d87fc1e2145e46f83c34f07
Gerrit-PatchSet: 1
Gerrit-Project: osmo-iuh
Gerrit-Branch: master
Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-HasComments: No



More information about the gerrit-log mailing list