OpenBSC

openbsc@lists.osmocom.org

4317 discussions

[PATCH 0/1] Add bport0/1 support for bs11_config
by Daniel Willmann 09 Aug '09

09 Aug '09

Hello, this patch should add support to bs11_config for bport0/1 configuration. This should enable you to configure a BS11 to run in multidrop mode and so contol two BS11 from one E1 link. I only have one BS11 so I was only able to verify that the objects are indeed created/modified. If it's okay I can also directly push the patch. Regards, Daniel Willmann Daniel Willmann (1): Add {create,delete}-bport1 and bport0-{star,multidrop} to bs11-config openbsc/include/openbsc/abis_nm.h | 4 +++- openbsc/src/abis_nm.c | 31 +++++++++++++++++++++++++++++-- openbsc/src/bs11_config.c | 26 ++++++++++++++++++++++++++ 3 files changed, 58 insertions(+), 3 deletions(-)

2 2

Re: BS-11 order
by Harald Welte 08 Aug '09

08 Aug '09

On Sat, Aug 08, 2009 at 02:03:06PM +0400, Sergey V. Efimov wrote: > I've compiled mISDN module into kernel and it loads with > hfcmulti.dslot=1 parameter. > I think there is no difference between dynamically loadable module > and statically compiled in. > Also when I did not provide this parameter, nothing worked at all. > > Is there any issues regarding processor architecture? I use AMD64 > platform, though > the system (Debian) has i386 architecture working in compatibility mode. I'm using both debian on 32bit and 64bit. Your problem might be related to the actual cabling. I believe it is definitely a layer1 (cabling) or layer 2 (mISDN) problem. I don't really know any other advice but to double-check the cabling, the jumpers on the E1 board as well as the termination jumpers on the BS-11. Everything has to be set to 120 Ohms. -- - 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)

1 0

OpenBSC with configuration file
by Harald Welte 07 Aug '09

07 Aug '09

Hi! I've committed the first working version of OpenBSC with vty-based configuration file to the 'config_file' branch in git. Using this version, all parameters such as BTS E1 card / timeslot / sub-slot / TEI for OML and RSL, MNC, MCC, BSIC, TSC as well as the physical channel configuration of each Um timeslot can be configured in openbsc.cfg. As an example, I'm attaching a configuration for two bts with two trx each. You can change the configuration interactively by using the telnet interface by a sequence of commands like: ================ enable configure terminal network bts 0 trx 0 arfcn 111 write file ================ At this point you still need to restart OpenBSC, as we don't support changing configuration at runtime yet. -- - 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)

1 0

Re: BS-11 order
by Harald Welte 07 Aug '09

07 Aug '09

On Thu, Aug 06, 2009 at 09:22:17PM +0400, Sergey V. Efimov wrote: > This is a bs11_config log: Your BS-11 is lacking its firmware, please refer to http://bs11-abis.gnumonks.org/trac/wiki/BS11_Configuration and http://bs11-abis.gnumonks.org/trac/wiki/bs11_config Specifically, it seems the SMU Safety load is installed and the minimal configuration exists, but no actual Software is installed. Thus, the MBCCU0 and MBCCU1 remains in "No Load", i.e. no firmware running. 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)

3 4

Ericsson RBS 2308
by Harald Welte 04 Aug '09

04 Aug '09

Hi! JFYI: I've bought an Ericsson RBS 2308 a couple of days ago, this is a BTS with traditional E1 interface, but with GPRS + EDGE support. I've managed to find the manual online at http://rapidshare.com/files/178080402/RBS2308.rar I have not yet received the unit, but there are more availalbe by a seller based in Texas / USA (USD 750). I can't promise that OpenBSC will have good support anytime soon, but I'll definitely look into it. Regards, -- - 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)

1 0

BS-11 multidrop E1 status update
by Harald Welte 04 Aug '09

04 Aug '09

Hi! I've been experimenting for the last couple of hours with two BS-11 in a multi-drop configuration. The connection looks like this: HFC-E1 connects to BTS A Y01/Y02, just like normal. BTS-A Y03/Y04 connect to BTS-B Y01/Y02. BTS-A LI object is configured as multi-drop BTS-B LI object is configured normal (star) BTA-A is configured to use TEI 25 on TS 1 for OML (normal) BTS-B is configured to use TEI 26 on TS 10 for OML (differnt) If I put the MA-10 A-bis signal analyzer between BTS A and BTS, I can see * that the E1 physical layer is up and there are no alarms * BTS-B sends TEI requests on timeslot 10, as requested however, there is no response. Looking at TS 10 between BTS-A and BSC, I can see that there are no TEI requests or any other data. GSM 12.21 specifies a "CONNECT MULTI-DROP LINK" message, using which you can map two E1 timeslots on two interfaces to each other. I've done this (mapping port 0, TS 10 to port 1, TS 10) - but it seems the BS-11 does not support this message. The MA-10 also calls it an "unknown message". I'm Sending this message to object class 0xa5 (SiemensHW) and to the LI object in that class (object instance 7, 0, 0). The BS-11 does not respond with ACK and not with NACK. It seems it is simply ignored silently. Does anyone have an idea how to proceed? Or does anyone have an A-bis trace from a working multi-drop configuration? Thanks. -- - 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)

1 1

Re: HAR2009 TODO list (MS power, BS-11 calibration)
by Dieter Spaar 04 Aug '09

04 Aug '09

Hello Harald, On Tue, 4 Aug 2009 10:18:55 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote: > > Status update: I have now hard-coded a MS power limit of 20dBm (100mW) for all > activated channels. The BS-11 still doesn't use dynamic MS power control > yet, but that is optional anyway. At least we're sure the MS now get told to > use no more than 100mW to talk to the BTS. If you not already modified it, please don't forget to adjust the "Cell Selection Parameters" in System Information 3 and 4. The GIT version from a few days ago still sets MS-TXPWR-MAX-CCH to the maximum. This means that the power of the initial RACH burst is too high although the channel power gets properly adjusted later. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

HAR2009 TODO list
by Harald Welte 04 Aug '09

04 Aug '09

Hi again, I'm currently in the train, so forgive me posting the initial TODO list to the mailing list rather than the wiki. I'll put it in the wiki soon. If you want to take on of the items, just let me know! What I think we have to do before HAR is as follows: == Actual code == === absolutely required === * finish and test the SMS implementation [Harald] * make sure we enable MS power control and impose a global limit of 100mW for the uplink (MS->BSC) direction by means of the MS POWER IE's and the BCCH information. That sounds like something for Dieter to figure out, especially since he has measurement equipment ;) * test dual-BTS-on-single-E1-card config [Harald] ** up to now, we have only tested with two nanoBTS, not BS-11 ! * test dual-TRX operation of BS-11 on OpenBSC [Stefan/Daniel, can you do that?] ** channel allocator can be tweaked to give 2nd TRX a preference for debugging [I'll add those to trac, since they are really important] === optional === * implement a 'provisioning mode' to OpenBSC that ** acccepts every new IMSI the first time we see it ** sends a SMS with a auth token to that mobile ** disconnects that mobile immediately * implement a web site / cgi script ** once user enters correct tuple of ISMI + auth code, we *** assign him a number (user cannot choose, we assign) *** set authorized=1 in the sql table * implement a web site bug tracker for user bug reports ** the should include detailed information about the phone model, his phone number and the exact timestamp, so we can match it in the pcap's * add more introspection code for the VTY interface to explore the run-time data structures in OpenBSC * implement different TCH assignment schemes (early / very early / OCASU) * do we really want a SDCCH/8 or is SDCCH/4 for each BTS sufficient? * some more testing with two BTS * in case we call a user who is currently offline/busy, generate SMS about missed call and store it in the SMS table * web interface ideas ** SMS gateway where people can send SMS from the web site *** SMS spam function for us in case we want to inform users about something ** simplistic phone book * enhance vty interface with administrative functions such as ** ability to close arbitrary channels (i.e. terminate a call) ** ability to kick-ban a user out of the network *** set authorized=0 *** perform authentication procedure with reject at its end * make sure we store all the 'this phone was registerd before to MCC/MNC/LAC' from the LOC UPD REQ data * make sure we really store the classmark1/2/3 together with IMEI in SQL table == Things to bring to the event == * spectrum analyzer [from CCCB] * stable OCXO reference to calibrate BS-11 internal clock ** this could be done before the event, but Harald has no precision clock source * trace mobiles / monitor mode mobiles (if anyone has some) * some poles to which we can mount the BS-11 ? == Misc == * draft 'usage terms & conditions' to be put on the registration web site and the HAR2009 wiki, indicating ** all signalling and traffic data will be stored for R&D purpose ** we do not employ authentication and/or encryption ** we do not provide any service guarantee ** this is for evaluation+testing only ** no handover/roaming and/or external calls ** no warranty for any damage to MS, SIM, ... ** IMSI/IMEI information will not be disclosed by us, but people can sniff it Regards, -- - 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)

2 4

Re: UMA a possibility in the future?
by Dieter Spaar 03 Aug '09

03 Aug '09

Hello Johannes, On Mon, 03 Aug 2009 22:56:08 +0200, "Johannes Schmitz" <jsemail(a)gmx.de> wrote: > > At this point I have got one general question, maybe also towards > Dieter: > How can A3/A8 be proprietary by any operator? How does international > roaming work then if there is no standardized algorithm? As far as I know for roaming the foreign network receives a RAND-Kc-SRES Triple from the home network so there is no need to know A3/A8 used by the other operator. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

UMA a possibility in the future?
by Dakota C 03 Aug '09

03 Aug '09

Hi, I'm a long time lurker into this project and I've wondered something for a bit of time.Knowing that we can use an ip.access nanoBTS to work on OpenBSC, why not adapt OpenBSC for UMA (unlicensed mobile access) standards? I know over here in the US we currently use UMA with T-Mobile over WiFi to communicate back to the T-Mobile servers and eventually off to the GSM and regular ol' networks. http://www.umatechnology.org/specifications/index.htm is the UMA specification, and to my knowledge T-Mobile US's @Home service uses the 1.0.3 protocol revision. To me it seems like it'd be trivial to make a derived copy of OpenBSC with UMA support up and running, but I'd like some other thoughts into this matter. I'm not a programmer by any means here, so if this is impossible, well, then so be it. -DC

3 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC