27 Sep
2016
27 Sep
'16
7:56 a.m.
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, master has been updated
via 39ee92606213a9fd36b10183bb461fa6e2d3a407 (commit)
via 0476e2854e89f6d30f3a7713e000657087e0fcaa (commit)
via 12181a937ff5658af49e12c57cb08ecba859e1f1 (commit)
via f33e8358cc2350e6fecb8653dc726770afa9fede (commit)
via c94ed09f50a124b962abb1f71f11c006db30e587 (commit)
from c83e49fc8ddb64fabf506ec3ed8cb622a4e4772c (commit)
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=39ee92606213a9fd36b10183bb461fa…
commit 39ee92606213a9fd36b10183bb461fa6e2d3a407
Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
Date: Mon Sep 26 01:07:19 2016 +0200
hnbgw: vty conformance: rename iuh 'bind' command to 'local-ip'
The standard osmo VTY terminology is 'remote-ip', 'remote-port',
'local-ip',
'local-port'. Conform to that. osmo-hnbgw is so far not rolled out widely, so
it makes sense to do this now.
Change-Id: Ifda2653bf58044552a5f1477cd7008dec3fb9100
http://cgit.osmocom.org/osmo-iuh/commit/?id=0476e2854e89f6d30f3a7713e000657…
commit 0476e2854e89f6d30f3a7713e000657087e0fcaa
Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
Date: Thu Sep 22 19:37:29 2016 +0200
log: hnbgw: add hnbap UE context allocation info log
Change-Id: Iac0ca948d6e699d984c6e424afe7106dcaf2ab1e
http://cgit.osmocom.org/osmo-iuh/commit/?id=12181a937ff5658af49e12c57cb08ec…
commit 12181a937ff5658af49e12c57cb08ecba859e1f1
Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
Date: Mon Apr 25 15:05:32 2016 +0200
hnbap: accept UE Register Requests with TMSI and pTMSI
Add the option to allow UE Register Requests with a TMSI identity.
Add VTY command to enable this option, 'hnbap-allow-tmsi'.
Add hnbgw_tx_ue_register_acc_tmsi().
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 aimed at the 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, to
page a UE on only its last seen HNB. 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. But we must
be aware that UEs that register by TMSI will simply not have an IMSI recorded
in the list of UE contexts, so a lookup based on IMSI may fail.
Patch-by: Harald Welte <laforge(a)gnumonks.org>rg>, me
Change-Id: I87bc1aa3e85815ded7ac1dbdca48f1680b468589
http://cgit.osmocom.org/osmo-iuh/commit/?id=f33e8358cc2350e6fecb8653dc72677…
commit f33e8358cc2350e6fecb8653dc726770afa9fede
Author: Neels Hofmeyr <nhofmeyr(a)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().
This is aimed at the 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.
See the upcoming commit that enables accepting TMSI identities for further
detail.
Change-Id: I138458443319cc4cbea5ee7906cf5dd72d582130
http://cgit.osmocom.org/osmo-iuh/commit/?id=c94ed09f50a124b962abb1f71f11c00…
commit c94ed09f50a124b962abb1f71f11c006db30e587
Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
Date: Mon Sep 26 01:27:55 2016 +0200
hnbap: add UE Register Reject for pTMSIRAI identity
This is aimed at the 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.
Sending a proper registration reject speeds up the response seen on the UE and
avoids needless waiting.
See the upcoming commit that enables accepting TMSI identities for further
detail.
Change-Id: I03b69613e6ddd8a08d9358ffc2f74954c231fd2c
-----------------------------------------------------------------------
Summary of changes:
include/osmocom/iuh/hnbgw.h | 10 +-
src/hnbgw.c | 25 ++++-
src/hnbgw_hnbap.c | 251 +++++++++++++++++++++++++++++++++++++-------
src/hnbgw_vty.c | 25 ++++-
4 files changed, 262 insertions(+), 49 deletions(-)
hooks/post-receive
--
Osmocom code for Iuh interface