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 "UNNAMED PROJECT". The branch, jerlbeck/wip/ms-struct has been updated via dd1567812895ed5092d77db653be91c17cd7f5c3 (commit) via 547b8d09c439d4e73156ed414392cf8205cf2307 (commit) via 8ea626b89a82266d4cd5299a71f82638da11fc1c (commit) from 37e896dff112fda77c29de770a0d8b3fe8800a5a (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-pcu/commit/?id=dd1567812895ed5092d77db653be91c… commit dd1567812895ed5092d77db653be91c17cd7f5c3 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Tue Jun 9 09:44:36 2015 +0200 ms: Add UL CS selection based on L1 link quality Currently the UL CS values are set to the corresponding DL CS value, eventually limited by a maximum value. This approach does not reflect the general situation of the RF link between ME and BTS, which is rather asymmetric e.g. due to a lower degree of TX efficiency of the built-in antenna. This means, that UL and DL CS control should be decoupled for better results. This commit adds automatic UL CS selection based on the link quality measurement parameter. Each coding scheme is mapped to a link quality range. If the link quality value leaves that range, the current UL CS value is increased/decreased accordingly. This value will be copied when the next PACKET_UPLINK_ACK_NACK or PACKET_UPLINK_ASSIGMENT is sent to the MS. The following VTY command will be added to the config-pcu node: - cs link-quality-ranges cs1 <0-20> cs2 <0-20> <0-20> cs3 <0-20> <0-20> cs4 <0-20> which sets the ranges for the four coding schemes. For instance the example below reflects the current default values: cs link-quality-ranges cs1 5 cs2 4 8 cs3 7 12 cs4 10 set the following ranges, where the overlapping is used to configure a hysteresis: CS1: -inf .. 5 CS2: 4 .. 8 CS3: 7 .. 12 CS4: 10 .. inf Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=547b8d09c439d4e73156ed414392cf8… commit 547b8d09c439d4e73156ed414392cf8205cf2307 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Mon Jun 8 11:26:38 2015 +0200 ms: Store the L1 measurement values in the MS objects This commits adds the GprsMs::update_l1_meas() and GprsMs::l1_meas() methods to store and access the measurement values. The internal state is updated depending on which values are actually set. In addition, these values are shown in the output of the 'show ms imsi|tlli' command. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=8ea626b89a82266d4cd5299a71f8263… commit 8ea626b89a82266d4cd5299a71f82638da11fc1c Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Mon Jun 8 11:05:45 2015 +0200 l1: Pass all L1 measurements upwards (TODO) Currently only the RSSI value is passed to the upper layers. Other values like TA and BER which are needed for TA update respectively CS selection are not propagated. This commit introduces and passes a struct that contains a set of measurement values. TODO: - the struct is currently defined in pcu_l1_if.h. Consider to put it into a separate file. Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/bts.cpp | 10 ++++---- src/bts.h | 7 ++++-- src/gprs_ms.cpp | 60 ++++++++++++++++++++++++++++++++++++++++------- src/gprs_ms.h | 6 +++++ src/pcu_l1_if.cpp | 8 ++++--- src/pcu_l1_if.h | 34 ++++++++++++++++++++++++++- src/pcu_main.cpp | 9 +++++++ src/pcu_vty.c | 45 +++++++++++++++++++++++++++++++++++ src/pcu_vty_functions.cpp | 12 ++++++++++ src/sysmo_l1_if.c | 18 +++++++++++--- src/tbf.h | 4 +++- src/tbf_ul.cpp | 9 ++++++- tests/tbf/TbfTest.cpp | 9 ++++--- 13 files changed, 205 insertions(+), 26 deletions(-) hooks/post-receive -- UNNAMED PROJECT