Project

General

Profile

Ericsson RBS » History » Version 10

dexter, 10/14/2016 03:43 PM

1 6 laforge
{{>toc}}
2 1 laforge
3 6 laforge
h1. Ericsson RBS 2000
4 1 laforge
5 6 laforge
6
There is some initial/experimental code in [[OpenBSC]] to support the Ericsson RBS 2000 family of BTS.
7
8 1 laforge
As opposed to Siemens/ip.access, Ericsson A-bis is much farther away from the specs, particularly
9
since their Organization and Maintenance Layer (OML) is a proprietary protocol called OM2000.
10
11
Nonetheless, we have been making quite a bit of progress in getting the RBS 2000 series supported.
12
Right now it is still not complete.  Don't expect anything to work at this stage.
13
14 6 laforge
We are collecting links to documents describing the Ericsson RBS architecture at [[RBS_Links]]
15 1 laforge
16 6 laforge
h2. Requirements
17 1 laforge
18
19 6 laforge
* Ericsson RBS 2000 series BTS
20
* E1 or T1 interface card, supported by the [[DAHDI]] driver. WE DO NOT SUPPORT RBS with mISDN drivers!
21
* RBS with software + IDB in default configuration, especially OML TEI set to 62
22
* /etc/dahdi/system.conf with "dslot=1,4" in it
23 1 laforge
24
25 6 laforge
h2. Setup
26
27
28
* Check that dahdi_tool is showing the link as OK, otherwise you have some wiring/polarity issues
29
* Create an openbsc.cfg that lists your BTS as 'rbs2000' type (see attached example)
30
** do not try to be clever and use non-standard E1 timeslot assignments, the code is hard-coded and assumes certain values
31
* start [[osmo-nitb]] as usual
32 9 dexter
* OM2000 messages can be decoded with Wireshark, set the following options:
33 10 dexter
** Right-Click on Link Access Procedure, Channel D (LAPD) ==> Protocol Preferences ==> Use GSM SAPI values
34
** Right-Click on GSM A-bis OML ==> Protocol Preferences ==> A-bis dialect to be used ==> Ericsson OM2000
35 6 laforge
36
h2. Status
37
38
39 1 laforge
So far, you should get
40 6 laforge
* A-bis link initialization, i.e. BSC telling the BTS to use TS1 as signalling for IXU/DXU OML
41
* [[OpenBSC]] configuring and starting the CF (central function)
42
* You can manually connect, configure and enable the IS via the VTY
43
* With some luck, the OML SAPI to the RRU/TRU's can then be established
44
* Using the '-p foo.pcap' option, you can write a PCAP protocol trace to be used with wireshark and our OM2000 wireshark dissector
45 1 laforge
46
What is NOT supported yet:
47 6 laforge
* Actually initializing the transceivers and Um timeslots
48
* Any actual communication with phones
49 7 laforge
* Any form of GPRS.  This requires us to implement a PCU compatible with the Ericsson PCU-CCU A-bis protocol. See [[Ericsson_RBS2000_GPRS]] for some collected information on this topic.
Add picture from clipboard (Maximum size: 48.8 MB)