osmo-bts.git branch master updated. 0.7.0-147-g4e959b2

gitosis at osmocom.org gitosis at osmocom.org
Mon Mar 5 17:44:31 UTC 2018


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 BTS-side code (Abis, scheduling, ...)".

The branch, master has been updated
       via  4e959b2aa06c98a8b8cad953d7baac1271f87bf0 (commit)
       via  1ef544ea246a73ef4404cb9622ca41fbe8e0b76b (commit)
       via  4f14804f8a023eff0ce2ac1712dd65383d1e0b96 (commit)
       via  0dfe13700911eb3755628f78a1a9653a34dd2510 (commit)
       via  53bdf4d949433a5d69ff2bdd2f74746e93195b88 (commit)
       via  10aa1cd6f6e9a10741965991ecba2b0939e50542 (commit)
      from  8a28868b29b4480f248d64728ebb08af8274fda9 (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-bts/commit/?id=4e959b2aa06c98a8b8cad953d7baac1271f87bf0

commit 4e959b2aa06c98a8b8cad953d7baac1271f87bf0
Author: Philipp Maier <pmaier at sysmocom.de>
Date:   Thu Mar 1 15:46:59 2018 +0100

    l1_tch: remove dead code
    
    the file l1_tch.c in the octphy spcific code has its root in the
    tch.c file of sysmobts. It contains some sysmobts specific ifdefs
    which enclose dead code.
    
    - Remove the sysmobts specif ifdefs and the dead code
    
    Change-Id: I33f3e0fd293ca8387fddf5ed20f642621e9680de

http://cgit.osmocom.org/osmo-bts/commit/?id=1ef544ea246a73ef4404cb9622ca41fbe8e0b76b

commit 1ef544ea246a73ef4404cb9622ca41fbe8e0b76b
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Mon Mar 5 20:56:20 2018 +0700

    common/l1sap.c: limit the minimal ToA for RACH bursts
    
    In general, RACH bursts should not arrive with negative offset.
    Let's limit early signal arrival up to 2 symbols, otherwise it
    is most likely noise, interference or a ghost.
    
    TTCN-3 test case: Icccc88545ed3aabd6da28a40599a8a77d1de477d
    Change-Id: I662294fe3136cf7a259be13816a3e63f7db9a948

http://cgit.osmocom.org/osmo-bts/commit/?id=4f14804f8a023eff0ce2ac1712dd65383d1e0b96

commit 4f14804f8a023eff0ce2ac1712dd65383d1e0b96
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Mon Mar 5 20:43:02 2018 +0700

    common/l1sap.c: perform noise / ghost filtering for handover RACH
    
    For some reason, the noise / ghost filtering was performed for
    normal RACH requests, but not for handover RACH requests. There
    are also ghost RACH, interference and noise possible, so let's
    extend the filtering coverage.
    
    Change-Id: I94fc15835280d624780200dadc4418210bf565ff

http://cgit.osmocom.org/osmo-bts/commit/?id=0dfe13700911eb3755628f78a1a9653a34dd2510

commit 0dfe13700911eb3755628f78a1a9653a34dd2510
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Mon Mar 5 20:29:47 2018 +0700

    common/l1sap.c: clean up noise / ghost RACH filtering
    
    It makes sense to combine both existing BER (Bit Error Rate) and
    ToA (Timing of Arrival) checks into a separate funcition, so
    this code may be also used for handover RACH.
    
    Change-Id: I1ddda238d5212a88a3dd5c4fc5dfcfea018151bd

http://cgit.osmocom.org/osmo-bts/commit/?id=53bdf4d949433a5d69ff2bdd2f74746e93195b88

commit 53bdf4d949433a5d69ff2bdd2f74746e93195b88
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Mon Mar 5 20:03:06 2018 +0700

    common/l1sap.c: increment valid RACH counter after all checks
    
    Previously, the number of RACH slots with valid non-handover RACH
    burst was incremented between both BER (Bit Error Rate) and ToA
    (Timing of Arrival) checks. So, if a RACH burst passed the BER
    check, but was dropped by ToA check, the counter of valid RACH
    requests could be increased anyway.
    
    Change-Id: I31594a8c5dce1f42226ced5b2dc8778152b3d829

http://cgit.osmocom.org/osmo-bts/commit/?id=10aa1cd6f6e9a10741965991ecba2b0939e50542

commit 10aa1cd6f6e9a10741965991ecba2b0939e50542
Author: Vadim Yanitskiy <axilirator at gmail.com>
Date:   Mon Mar 5 19:40:55 2018 +0700

    common/l1sap.c: increase the BTS_CTR_RACH_DROP in RACH BER check
    
    The BTS_CTR_RACH_DROP counter is being increased in case if a RACH
    request is ignored due to exceeding ToA value, but remains untouched
    in case of exceeding BER (Bit Error Rate). Let's fix this.
    
    Change-Id: Ia02e781d6c47d9d8012a4c8846fe4b731aab74d7

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

Summary of changes:
 src/common/l1sap.c           | 87 ++++++++++++++++++++++++++------------------
 src/osmo-bts-octphy/l1_tch.c | 64 --------------------------------
 2 files changed, 52 insertions(+), 99 deletions(-)


hooks/post-receive
-- 
Osmocom BTS-side code (Abis, scheduling, ...)


More information about the osmocom-commitlog mailing list