osmocom-net-gprs

osmocom-net-gprs@lists.osmocom.org

482 discussions

by Harald Welte

Dear all, Deater has been investigating which issues currently prevent us from using GEA in OsmoSGSN. His mail has been sitting in my inbox too long, and hence I'm forwarding his results here to the mailing list for further discussion / follow-up. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

9 years, 2 months

MS behavior with dysfunctional GPRS

by Max

Hi. Imagine following configuration: - GSM network advertises GPRS capabilities in System Information messages - It's not actually available (SGSN crashed, all the timeslots are occupied by TCH etc) What would be expected behavior for MS in this scenario? Shall it switch to alternative network in hope of getting promised GPRS? Shall it hang on the currently camped network providing voice/sms only? Which spec(s) cover that? What could be decision factors for the MS? SIM entries, some data in SI, some timeout somewhere, smth else? -- Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte

9 years, 2 months

latest sysmobts-mgr failure on NURAN 1.0

by Prasad Kaup

Hi All, We are trying to cross compile and test latest osmo-pcu, osmo-bts, openbsc, osmo-sgsn , and ggsn. One issue we see with latest sysmobts-mgr (Commit ed494443cc1e9732b43ef99cccf187d17ac931ef) on Nuran 1.0 is as below. - PA is off - Signal is very low - No signal on slave. With sysmobts-mgr preloaded(older commit version) on board, the setup works fine. Please help us in resolving this issue seen in master branch of osmo-bts latest commit. Regards Prasad

9 years, 2 months

OpenBSC and related projects moved to Gerrit

by Holger Freyther

Hi, as discussed at OsmoDevCon and the mails from last week. The following list of projects have moved to use gerrit for codereview: * libosmocore.git * libosmo-abis.git * libosmo-netif.git * libosmo-sccp.git * libsmpp34.git * openbsc.git * osmo-bts.git * osmo-iuh.git * osmo-pcu.git * cellmgr-ng.git * osmo-sip-connector.git I have created this[1] page with the minimum to set-up gerrit as git-remote, register, configure the account and then hopefully the most frequently used comments. kind regards holger [1] http://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit

9 years, 2 months

PCU sends invalid block number to L1

by Minh-Quang Nguyen

Hi All, We have noticed that the PCU sends invalid block number to L1 in DSP leading to unexpected message warning in DSP "GsmL1_PhDataReq(1) : Unexpected burst (Invalid blockNumber) [2!=1, SAPI 21-21]]". After an investigation, we observe that the 'pcu_rx_rts_req' function in pcu_l1_if.cpp receives invalid block number from BTS. Looking at the BTS side, the calculation of L1SAP_FN2PTCCHBLOCK defined as '#define L1SAP_FN2PTCCHBLOCK(fn) ((fn / 52) & 7)' does not seem to be valid for expected PTCCH block numbers B0, B1,B2,B3 defined in Table 6 in TS 05.02 version 8.11.0. What do you think about re-define the calculation of the L1SAP_FN2PTCCHBLOCK? Regards, Minh-Quang Nguyen Concepteur logiciel | Software designer GSM/Network T. 418 914-7484 x2296 | 1 855 914-7484 | F. 418 914-9477 2150, Cyrille-Duquet, Québec (Québec) G1N 2G3 CANADA minh-quang.nguyen(a)nutaq.com <mailto:minh-quang.nguyen@nutaq.com> www.nutaq.com <http://www.nutaq.com/> QUEBEC MONTREAL NEW YORK <http://www.nutaq.com/signature/nutaq_q_m_ny.jpg> Facebook <http://www.facebook.com/pages/Nutaq-Innovation/351864938229900> Twitter <https://twitter.com/NutaqInnovation> LinkedIn <http://www.linkedin.com/company/Nutaq> YouTube <http://www.youtube.com/NutaqInnovation>

9 years, 3 months

[PATCH 1/5] Cleanup build leftovers

by msuraev＠sysmocom.de

From: Max <msuraev(a)sysmocom.de> --- .gitignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index d2713bf..959b09b 100644 --- a/.gitignore +++ b/.gitignore @@ -18,7 +18,7 @@ compile depcomp install-sh missing -libtool +*libtool ltmain.sh core -- 2.8.1

9 years, 3 months

[PATCH 0/4] Support for Incremental redundency in EGPRS DL

by Aravind Sirsikar

This series of patches supports Incremental redundency for EGPRS DL case. These patches have been integration tested on Nuran 1.0 for EGPRS MCS 9 support in DL. And in UL only MCS4 has been tested. The EGPRS testing has been done with Browsing and Ping in DL with larger packet sizes(1500). Aravind Sirsikar (4): Add data structure for MCS change in Retx Add Accessor functions for MCS change in Retx Modify DL tbf flow for MCS change in Retx Add test cases to support MCS change during Retx src/gprs_coding_scheme.cpp | 36 ++++ src/gprs_coding_scheme.h | 27 ++- src/gprs_ms.cpp | 5 + src/gprs_ms.h | 1 + src/rlc.h | 10 ++ src/tbf_dl.cpp | 41 +++-- tests/tbf/TbfTest.cpp | 224 +++++++++++++++++++++++++ tests/tbf/TbfTest.err | 397 ++++++++++++++++++++++++++++++++++++++++++++ tests/tbf/TbfTest.ok | 9 + 9 files changed, 737 insertions(+), 13 deletions(-) -- 1.7.9.5

9 years, 3 months

Query for verified EGPRS osmo-pcu version on Nuran1.0

by Aravind Sirsikar

Hi Harald, Can you please let us know the commit version for osmo-pcu which has been verified for EGPRS functionality on Nuran 1.0 hardware. We have been trying the latest commit 1aa75273025b033d17c1068369a7ba145d5c9f06 which does not work( no uplink data received yet). Can you provide details of the hardware in which EGPRS functionality has been successfully verified. Thanks, Aravind Sirsikar

9 years, 3 months

[PATCH] Fix make distcheck

by msuraev＠sysmocom.de

From: Max <msuraev(a)sysmocom.de> Define automake variable for configure flags to be used while running 'make distcheck'. This should prevent additional vty tests from running in readonly distcheck environment. Note: user can still break the build by overriding this with DISTCHECK_CONFIGURE_FLAGS variable. --- src/Makefile.am | 1 + 1 file changed, 1 insertion(+) diff --git a/src/Makefile.am b/src/Makefile.am index 6428bef..487ef1d 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -19,6 +19,7 @@ # AM_CPPFLAGS = $(STD_DEFINES_AND_INCLUDES) $(LIBOSMOCORE_CFLAGS) $(LIBOSMOGB_CFLAGS) $(LIBOSMOGSM_CFLAGS) +AM_DISTCHECK_CONFIGURE_FLAGS="--enable-sysmocom-dsp=no" if ENABLE_SYSMODSP AM_CPPFLAGS += -DENABLE_SYSMODSP -- 2.8.1

9 years, 3 months

[PATCH 1/4] Add data structure for MCS change in Retx

by Aravind Sirsikar

From: Aravind Sirsikar <arvind.sirsikar(a)radisys.com> Modify the existing data structure to support MCS change during retransmission in EGPRS DL --- src/gprs_coding_scheme.cpp | 36 ++++++++++++++++++++++++++++++++++++ src/gprs_coding_scheme.h | 8 ++++++++ src/rlc.h | 11 +++++++++++ 3 files changed, 55 insertions(+) diff --git a/src/gprs_coding_scheme.cpp b/src/gprs_coding_scheme.cpp index 8601d4f..436b2d9 100644 --- a/src/gprs_coding_scheme.cpp +++ b/src/gprs_coding_scheme.cpp @@ -21,6 +21,42 @@ #include "gprs_coding_scheme.h" +/* + * 44.060 Table 8.1.1.1 and Table 8.1.1.2 + * It has 3 level indexing. 0th level is ARQ type + * 1st level is Original MCS (index 0 corresponds to MCS1 and so on) + * 2nd level is MS MCS (index 0 corresponds to MCS1 and so on) + * in 0th level indexing only ARQ type 2 is supported i.e index 1 for + * incremental redundancy + */ + +/* TODO: Need to support ARQ type 1 */ +enum GprsCodingScheme::Scheme GprsCodingScheme::egprs_mcs_retx_tbl[MAX_NUM_ARQ] + [MAX_NUM_MCS][MAX_NUM_MCS] = { + { + {MCS1, MCS1, MCS1, MCS1, MCS1, MCS1, MCS1, MCS1, MCS1}, + {MCS2, MCS2, MCS2, MCS2, MCS2, MCS2, MCS2, MCS2, MCS2}, + {MCS3, MCS3, MCS3, MCS3, MCS3, MCS3, MCS3, MCS3, MCS3}, + {MCS1, MCS1, MCS1, MCS4, MCS4, MCS4, MCS4, MCS4, MCS4}, + {MCS2, MCS2, MCS2, MCS2, MCS5, MCS5, MCS7, MCS7, MCS7}, + {MCS3, MCS3, MCS3, MCS3, MCS3, MCS6, MCS6, MCS6, MCS9}, + {MCS2, MCS2, MCS2, MCS2, MCS5, MCS5, MCS7, MCS7, MCS7}, + {MCS3, MCS3, MCS3, MCS3, MCS3, MCS6, MCS6, MCS8, MCS8}, + {MCS3, MCS3, MCS3, MCS3, MCS3, MCS6, MCS6, MCS6, MCS9} + }, + { + {MCS1, MCS1, MCS1, MCS1, MCS1, MCS1, MCS1, MCS1, MCS1}, + {MCS2, MCS2, MCS2, MCS2, MCS2, MCS2, MCS2, MCS2, MCS2}, + {MCS3, MCS3, MCS3, MCS3, MCS3, MCS3, MCS3, MCS3, MCS3}, + {MCS4, MCS4, MCS4, MCS4, MCS4, MCS4, MCS4, MCS4, MCS4}, + {MCS5, MCS5, MCS5, MCS5, MCS5, MCS5, MCS7, MCS7, MCS7}, + {MCS6, MCS6, MCS6, MCS6, MCS6, MCS6, MCS6, MCS6, MCS9}, + {MCS5, MCS5, MCS5, MCS5, MCS5, MCS5, MCS7, MCS7, MCS7}, + {MCS6, MCS6, MCS6, MCS6, MCS6, MCS6, MCS6, MCS8, MCS8}, + {MCS6, MCS6, MCS6, MCS6, MCS6, MCS6, MCS6, MCS8, MCS9} + } + }; + static struct { struct { unsigned int bytes; diff --git a/src/gprs_coding_scheme.h b/src/gprs_coding_scheme.h index aec3762..06e90fc 100644 --- a/src/gprs_coding_scheme.h +++ b/src/gprs_coding_scheme.h @@ -26,6 +26,12 @@ class GprsCodingScheme { public: + +#define MAX_NUM_ARQ 2 /* max. number of ARQ */ +#define MAX_NUM_MCS 9 /* max. number of MCS */ +#define EGPRS_ARQ1 0x0 +#define EGPRS_ARQ2 0x1 + enum Scheme { UNKNOWN, CS1, CS2, CS3, CS4, @@ -105,6 +111,8 @@ public: static GprsCodingScheme getEgprsByNum(unsigned num); static const char *modeName(Mode mode); + static Scheme egprs_mcs_retx_tbl[MAX_NUM_ARQ] + [MAX_NUM_MCS][MAX_NUM_MCS]; private: GprsCodingScheme(int s); /* fail on use */ GprsCodingScheme& operator =(int s); /* fail on use */ diff --git a/src/rlc.h b/src/rlc.h index 8f75588..f5429c2 100644 --- a/src/rlc.h +++ b/src/rlc.h @@ -120,6 +120,17 @@ struct gprs_rlc_data { uint8_t len; struct gprs_rlc_data_block_info block_info; + + /* + * cs2 is variable to hold the cs value for + * current transmission. cs2 is same as cs during + * transmission case. During retransmission cs2 is + * fetched from egprs_mcs_retx_tbl table based on + * cs and demanded cs. Once the data has been sent successfully, + * cs2 will be copied to cs. Reference is 44.060 Table + * 8.1.1.1 and Table 8.1.1.2 + */ + GprsCodingScheme cs2; GprsCodingScheme cs; /* puncturing scheme value to be used for next transmission*/ -- 1.7.9.5

9 years, 3 months

← Newer
1
...
31
32
33
34
35
36
37
...
49
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

osmocom-net-gprs