Project

General

Profile

Bug #1951

Location update is hard to be performed using osmo-bts-trx and USRP B200

Added by wirelesss 2 months ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
02/15/2017
Due date:
% Done:

0%

Spec Reference:

Description

Two different time-slots configuration has been used while attempts for Location update have been done.
It is not possible to perform LU, while using Osmocom style dynamic time-slots.
Just one of the test phones (BlackBerry) has attached successfully to NITB, but just for a few moment after this phone has been disconnected from the network. In this case I have used 3 TCH/F, 3 PDCH timeslots configuration for NITB.

I have run B200 with external 10Mhz ref. clock source from GPS Disciplined Oscilator (BG7TBL), but there was no difference to be seen.

Described issue has not been seen with sysmoBTS,nanoBTS and OCTBTS.

hashes:
libosmo-abis: 254745880bb2ff7f17fe158fb7bfb5e1dc530906
libosmo-netif: 5fd93e02f818aecfc73db66e8064858442122959
libosmo-sccp: 0c72c1c0d313321f65fd272840ed8e8ae69a04cd
libosmocore: 96c8bc6e76ba1200c96085ecce2ce80ee257a6aa
libsmpp34: 63d562c099f11c4d11a952a03bc54659f8b82319
openbsc: b726c2c72b5e94d6723fefd04daf21be61eab5a5
openggsn: 68d244d3022d41a170f83ddec5050d659aef0bcd
osmo-bts-oct: b390dfb90dfd0b38d17cea931ec0d0e194e2a4a1
osmo-bts: b390dfb90dfd0b38d17cea931ec0d0e194e2a4a1
osmo-pcu: 78ce59137fa0bd0e6b11bfc9ea24c93e6b2a8d2a
osmo-trx: 2dee3e996e777b67aa3185f7456c041765f0d71f

no_lu_nitb.log Magnifier (13.7 KB) wirelesss, 02/15/2017 01:34 PM

trx_bts_lo_pacap.tar.gz (3.37 MB) wirelesss, 02/15/2017 01:36 PM

openbsc_B200.cfg - osmocom dynamic ts nitb configuration (5.3 KB) wirelesss, 02/17/2017 11:51 AM

osmo-bts_B200.cfg - bts configuration (374 Bytes) wirelesss, 02/17/2017 11:51 AM

History

#1 Updated by laforge 2 months ago

  • Subject changed from Location update is hard to be performed using ettus B200 to Location update is hard to be performed using osmo-bts-trx and USRP B200

#2 Updated by ipse 2 months ago

Just want to clarify - is the issue happening when non-dynamic channel types are used?

#3 Updated by wirelesss 2 months ago

ipse wrote:

Just want to clarify - is the issue happening when non-dynamic channel types are used?

When non-dynamic time-slots (i.e. 3 TCH/F, 3 PDCH) configuration is used then there was successful Location Update, but after a few seconds Mobile phone has start searching for the network again. Second test phone have not performed Location update at all.

#4 Updated by msuraev 2 months ago

Could you please attach config files used for testing?

#5 Updated by wirelesss 2 months ago

Also available in: Atom PDF