Attention is currently required from: neels, pespin, fixeria. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/31085 )
Change subject: hnbgw: add HNBAP port to ConnHdlr ......................................................................
Patch Set 1:
(1 comment)
File hnbgw/HNBGW_Tests.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/31085/comment/7590b215_194ee... PS1, Line 414: /* disconnect test_CT HNBAP[i], instead connect ConnHdlr.HNBAP to HNBAP[i] */
When I want to send HNBAP in-between some RUA-SCCP conn activities, it is cumbersome to have to go b […]
conceptually it just feels wrong. A ConnHdlr relates to a Subscriber. HNBAP UE register relates to a subscriber. But HNB register relates to a HNB.
Architecturally, IMHO, this means the clean approach is to have some kind of "HNBAP_Emulation" component which separates the per-hnb and the per-UE messages. The per-ue related messages then get dispatched to the respective ConnHdlr component. For the per-hnb signals, they might need to be broadcast to all ConnHdlr serving UEs of that HNB.
-
laforge