This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom code for Iuh interface".

The branch, neels/ipa_nano3g has been updated discards 69e05da6049bbb3173de7592f9781aac36df111d (commit) discards a50f76af6b8ffc7f5a9bed1139474b6512ece621 (commit) discards e9d86b7a108e121328f3c50cba6ef5150f7a38af (commit) discards 4f014aa873bde7c1bcfb450fe412c408e9127afc (commit) discards 6148f344e2f55da59237616a90e53f44ca90d4ae (commit) via 5e21c59988f1d8067562c1dfab73536134b80087 (commit) via 33802daf23372019c92f49fa73fc5cf0038dc3ce (commit) via 75a61858d5bdee9afed1be059b45666702dfdda0 (commit) via bc03eeeee2dc9b330a7775e652d19b269530c5e9 (commit)

This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this:

* -- * -- B -- O -- O -- O (69e05da6049bbb3173de7592f9781aac36df111d) \ N -- N -- N (5e21c59988f1d8067562c1dfab73536134b80087)

When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B.

Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below.

- Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-iuh/commit/?id=5e21c59988f1d8067562c1dfab735361...

commit 5e21c59988f1d8067562c1dfab73536134b80087 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Fri Sep 9 01:25:22 2016 +0200

comment: note RAB assignment spec reference

Change-Id: Ifef8da82a01cd781ef560d1ec21cbfb23efb1495

http://cgit.osmocom.org/osmo-iuh/commit/?id=33802daf23372019c92f49fa73fc5cf0...

commit 33802daf23372019c92f49fa73fc5cf0038dc3ce Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Thu Sep 22 19:37:29 2016 +0200

log hnbap UE context allocation

Change-Id: I572095e6d3f2b48362bf8a88bc66f8438348d29a

http://cgit.osmocom.org/osmo-iuh/commit/?id=75a61858d5bdee9afed1be059b456667...

commit 75a61858d5bdee9afed1be059b45666702dfdda0 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Apr 25 15:05:32 2016 +0200

hnbap: accept UE Register Requests with TMSI and pTMSI

HNBGW so far keeps track of UEs that have registered, with their IMSI. When a UE registers with only a TMSI, we obviously can't store an IMSI. However, since we're so far never *using* the list of UEs in osmo-hnbgw, we might as well just accept the TMSI registration and carry on as usual. All that is needed for proper operation is a valid UE context.

This is particularly helpful with an ip.access nano3G femto cell, as it apparently feeds whichever identification the UE sends through to HNBAP (TMSI+LAI, pTMSI+RAI), instead of an IMSI as expected. So far this caused failures and the need to make the UE clear its TMSI (wait several minutes or attempt to subscribe to a different network), so that UE registration switched back to IMSI. When simply accepting the TMSI in osmo-hngw, no problems are apparent in our current code state.

For example, a Samsung Galaxy S4 seems to send a UE_Identity_PR_tMSILAI (CS identity), and a GT-I9100 seems to send a UE_Identity_PR_pTMSIRAI (PS identity) upon first registration to the network.

Recording the IMSI in hnbgw: we could use the subscriber list during paging, but on the other hand, it doesn't hurt to anyway always page to all HNBs connected to osmo-hnbgw. The paging procedure does include a page-to-all-HNBs in case the first HNB paging fails. However, since we're now failing to record UEs that register by TMSI, we must be aware that trying to page such UE on only its last seen HNB will fail; it is plainly missing in the list.

Patch-by: Harald Welte laforge@gnumonks.org, me Change-Id: I87bc1aa3e85815ded7ac1dbdca48f1680b468589

http://cgit.osmocom.org/osmo-iuh/commit/?id=bc03eeeee2dc9b330a7775e652d19b26...

commit bc03eeeee2dc9b330a7775e652d19b269530c5e9 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Thu Sep 22 18:06:59 2016 +0200

hnbgw: UE context: add handling by tmsi identification

To prepare for an upcoming commit that accepts TMSI identification upon UE Register Requests:

Add tmsi arg to ue_context_alloc(). Add ue_context_by_tmsi().

Change-Id: I138458443319cc4cbea5ee7906cf5dd72d582130

-----------------------------------------------------------------------

Summary of changes: include/osmocom/iuh/hnbgw.h | 7 ++++--- src/hnbgw.c | 23 +++++++++++++++++++-- src/hnbgw_hnbap.c | 49 +++++++++++++++++++++++++++++++++++---------- src/ranap_msg_factory.c | 24 +--------------------- src/tests/test-ranap.ok | 10 ++++----- 5 files changed, 69 insertions(+), 44 deletions(-)

hooks/post-receive