osmo-iuh.git branch sysmocom/ipa_nano3G updated. 75bfa56be9aa9fe98e88278e3a58ade29c2d69f0

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

gitosis at osmocom.org gitosis at osmocom.org
Wed Sep 7 13:11:12 UTC 2016


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, sysmocom/ipa_nano3G has been updated
  discards  575301ae326141af5745b60e286054448b6f1723 (commit)
  discards  ce605fab0a1d3b6eeb417bf31ceeed03dfe724c1 (commit)
  discards  544b76d6e2db765c57e35af0aa99f162a28685fe (commit)
       via  75bfa56be9aa9fe98e88278e3a58ade29c2d69f0 (commit)
       via  6ffacf5ea61308243cf2b0bb0b74e2f0923d19c0 (commit)
       via  8380eb2a01e6b5eb375adf1e570fa7293226fd47 (commit)
       via  e75a6297da9337db95e94c4eb1cebc1e72fb9d41 (commit)
       via  6dc074c9aa4eed9f6a69d2bc613f4852aaaa2fc7 (commit)
       via  01c71fc2dd3c3545a5a3f0d83391a28590dc9f69 (commit)
       via  4d91ab277b4acc1bc2bdb5edc81d8c09b2bd3e47 (commit)
       via  f495b2347bfc0c974e33988f8240be5cb7b2db3b (commit)
       via  926153b9af0659e8c214f40424e29cda0c821607 (commit)
       via  4d8eb4cbd7e7ecc1ad04e3b38ab5121dca2580b1 (commit)
       via  1d03f19e06ae5ca51e3f37fa01c6585df6d8ad26 (commit)
       via  085cd67672c9006be6e6f89abb80cff8926ef245 (commit)
       via  4d675a7df9fd9f3b435da4cbea8446a1e9df22b3 (commit)
       via  4c45d2b9fd364122f561239a7a8572f904effee6 (commit)
       via  a1bf4f330f50746a3ca7feff5464fe3e3cf17861 (commit)
       via  0a43722a488aa650ce0192a409734b9ddc093603 (commit)
       via  6458c30db459c666bce4a517c46b8dfdc1889f53 (commit)
       via  0961408e1bceb11586783a2c3484f92924429068 (commit)
       via  de0acd2ff2cde071d8d0c6818658107d97c24cd1 (commit)
       via  f706d6c06529c6c6fc2284ce9348a7058653b321 (commit)
       via  fef2e860030217b4a6edddc22b791a35ff224ed5 (commit)
       via  c23146e7f18b0f1bea67ba7b48ad4bc6cc76958b (commit)
       via  156fa393fc7472ba57683905c054adc6892b3cbd (commit)
       via  fd666890f7f1dc6fc8edc9f923ccf12461d5cbcc (commit)
       via  a9cf70f665c553e7d31ed3c7a68bca326db0d964 (commit)
       via  802acd0da459b4d74bf4a64d8c12aba0f2a6c09c (commit)
       via  75f8116132a452af9e2b9c95a9fe1d1142605567 (commit)
       via  95d0ba5f401db53d5ce3f296ec02bd33865a387b (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 (575301ae326141af5745b60e286054448b6f1723)
            \
             N -- N -- N (75bfa56be9aa9fe98e88278e3a58ade29c2d69f0)

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=75bfa56be9aa9fe98e88278e3a58ade29c2d69f0

commit 75bfa56be9aa9fe98e88278e3a58ade29c2d69f0
Author: Harald Welte <laforge at gnumonks.org>
Date:   Sat Apr 30 23:52:02 2016 +0200

    hack: Accept also UE_Identity_PR_pTMSIRAI in HNBAP from nano3G
    
    I have the feeling that the nano3G simply forwards whatever identity it
    receives from the MS in RRC via HNBAP, without sending any IDENTITY
    REQUESTS by itself.  That seems like a violation of the RANAP
    specification, but well.
    
    As opposed to Neels' earlier commit, the phone I was testing with
    (GT-I9100) is using the UE_Identity_PR_pTMSIRAI (PS identity) instead of
    UE_Identity_PR_tMSILAI (CS identity) when trying its first attempt to
    register to the network, so let's support that equally.

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

commit 6ffacf5ea61308243cf2b0bb0b74e2f0923d19c0
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date:   Mon Apr 25 15:05:32 2016 +0200

    hack: simply accept UE Register Requests with TMSI
    
    HNBGW would usually keep 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.
    
    This is particularly helpful with an ip.access nano3G femto cell, as it
    tends to send UE registrations with a TMSI+LAI identification instead of
    an IMSI when the subscriber is known. This causes timeouts of several
    minutes until a UE registration switches back to IMSI. When simply
    accepting the TMSI in osmo-hngw, no problems are apparent in our current
    code state.
    
    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.

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

commit 8380eb2a01e6b5eb375adf1e570fa7293226fd47
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date:   Mon Apr 25 14:55:35 2016 +0200

    UE Register with TMSI: reply with a Register Reject
    
    When receiving a UE Register Request with TMSI and no IMSI, compose a
    Register Reject with the same UE Identity and send.
    
    The accepting function expects a ue_context argument and composes the
    message from the IMSI found there. This new rejection message cannot rely
    on a ue_context struct and hence uses the asn1 uE_Identity directly.
    
    Change-Id: Ia47e398e50e316842cd260dc0d9a4e2d8a1c627c

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

Summary of changes:
 .gitignore                             |    2 +
 Makefile.am                            |    2 +-
 asn1/utils/asn1tostruct.py             |    2 +-
 configure.ac                           |    3 +
 contrib/jenkins.sh                     |  110 +-
 doc/Makefile.am                        |   12 +
 doc/examples/Makefile.am               |   23 +
 doc/examples/osmo-hnbgw.cfg            |   32 +
 include/osmocom/Makefile.am            |    2 +-
 include/osmocom/iuh/Makefile.am        |    2 +
 include/osmocom/iuh/vty.h              |    9 +
 include/osmocom/ranap/ranap_ies_defs.h | 2967 --------------------------------
 move-asn1-header-files.sh              |   25 +-
 src/Makefile.am                        |   12 +-
 src/hnbgw.c                            |  191 +-
 src/hnbgw.h                            |   17 +-
 src/hnbgw_cn.c                         |    3 +-
 src/hnbgw_vty.c                        |  153 ++
 src/ranap_msg_factory.c                |    7 +-
 src/tests/dummy_cn_sua.c               |   12 +-
 src/tests/test-ranap.c                 |    3 +-
 src/tests/test-ranap.ok                |    4 +-
 22 files changed, 485 insertions(+), 3108 deletions(-)
 create mode 100644 doc/Makefile.am
 create mode 100644 doc/examples/Makefile.am
 create mode 100644 doc/examples/osmo-hnbgw.cfg
 create mode 100644 include/osmocom/iuh/Makefile.am
 create mode 100644 include/osmocom/iuh/vty.h
 delete mode 100644 include/osmocom/ranap/ranap_ies_defs.h
 create mode 100644 src/hnbgw_vty.c


hooks/post-receive
-- 
Osmocom code for Iuh interface



More information about the osmocom-commitlog mailing list