Project

General

Profile

HSL Femto » History » Version 5

laforge, 02/19/2016 10:47 PM
add note about no hsl relationship

1 1 laforge
[[PageOutline]]
2
= The HSL 2.75G Femtocell =
3
4
The HSL 2.75G Femtocell is a relatively recent product implementing a single-ARFCN BTS with 23dBm maximum output power.
5
6 5 laforge
'''NOTE: All information on this website is gathered on our own, without any cooperation of the manufacturer.  There is no guarantee of correctness.  There is no relationship between HSL and the OpenBSC project developers!
7
8 1 laforge
== Hardware ==
9
10
The hardware seems to be a much more software radio approach than the nanoBTS, which are
11
built from telephone baseband processors.
12
13
 * Ti DaVinci TMS320DM6443A (ARM9 CPU + DSP)
14
 * Xilinx Spartan-3A FPGA (XC3SD1800A)
15
 * 128 MByte DDR-2 RAM
16
 * 128 MByte NAND flash
17
 * Realtek RTL8201 Ethernet MAC
18
 * Dual 12-bit 65Ms/sec ADC (ADS5232)
19
 * Dual 14-bit 275Ms/sec DAC (DAC5672)
20
21
As you can see, the hardware is _much_ more powerful than you would ever
22
need for a simple single-ARFCN femtocell.  Using the high-speed DAC/ADC,
23
the combined power of the FPGA (with DSP slices) and DSP, you can probably
24
expect that they will at least want to do multi-ARFCN (if not 3G) on the
25
same hardware at some later point.
26
27
There's a dedicated [wiki:HSL_Femto/Hardware] page with more details.
28
 
29
== Protocol ==
30
They use an odd down-sized minimalistic dialect of the ip.access Abis/IP.
31
32
=== ACS ===
33
Prior to connecting to the BSC, the cell downloads its current configuration
34
via https, using a HTTP POST of its serial number.
35
36
=== IPA layer ===
37
The IPA multiplex layer does not have PING/PONG keepalives, and it does
38
not do the ID_GET/ID_RESP/ID_CONF identification with the Unit ID.
39
Furthermore, both OML and RSL are encapsulated in the same TCP connection.
40
41
Stream identifier 0xDD is used for passing string debug messages from the
42
BTS to the BSC.
43
44
Neither OML nor RSL are implemented fully, as per 12.21 / 08.58
45
46
=== RSL ===
47
It seems to have a very 'creative' interpretation of the RSL specification.  Some
48
examples:
49
 * use of SACCH INFO MODIFY instead of SACCH FILLING for default SI5/SI6
50
 * it forgets to send RSL CHAN REL ACK on TS1...7
51
 * it does not implement RSL CHAN MODIFY
52
 * it seems to be unable to run without DTX
53
 * it often detects RACH requests where there are none (!)
54
55
=== OML ===
56
OML is almost not present at all.  Only software download and setting of
57
ARFCN + BSIC are supported.  No managed objects, no state transitions, no
58
software activation procedures/events at all.
59
60
The configuration of each timeslot seems to happen 'on demand', i.e.
61
there are no OML commands to configure the timeslots, but it depends on your
62
RSL CHAN ACT whether a timeslot will become a TCH/H or TCH/F.
63
64
I have not managed to use a SDCCH/8 anywhere, just TCH/F and TCH/H as well as
65
SDCCH/4.
66
67
The BCCH _claims_ to be a Combination 4, but in reality it is a Combination 5
68
(i.e. including the SDCCH/4)
69
70 4 laforge
=== RTP ===
71
There is a proprietary RSL message used to connect the BTS to the TRAU.
72
73
Codec data is exchanged by RTP packets exchanged between BTS UDP port 1000 and the
74
TRAU IP and UDP port.
75
76
The CellID is used as SSRC of all RTP packets, enabling the TRAU to distinguish frames
77
from different cells
78
79
If multiple TCH are active, the RTP payload contains the codec frames from all active TCH
80
channels.  The format is like a sequence of elements formatted like this:
81
 * byte 1: RSL Channel number (e.g. 0x09 = TCH/F on TS 1)
82
 * byte 2: length of codec frame (e.g. 0x22 hex for EFR)
83
 * byte 3..length: Codec Data
84
85 1 laforge
=== GPRS ===
86
GPRS is quiite odd, too.  The BSSGP is encapsulated in the RSL L3_INFO_IE,
87
this means we will have to run a NS link from the BSC to the SGSN, combining
88
all the BSSGP links from HSL Femtocells to the BSC.
89 2 laforge
90
== Software support ==
91
92
=== wireshark ===
93
94
We have some wireshark patches for adding HSL RSL/OML support:
95
 * http://cgit.osmocom.org/cgit/openbsc/plain/wireshark/0005-rsl-hsl.patch
96
 * http://cgit.osmocom.org/cgit/openbsc/plain/wireshark/0006-abis_oml-hsl.patch
97
98 3 laforge
=== OpenBSC ===
99 2 laforge
100
OpenBSC support is being worked on in the {{{laforge/hsl}}} branch of openbsc.git:
101
 * http://cgit.osmocom.org/cgit/openbsc/log/?h=laforge/hsl
Add picture from clipboard (Maximum size: 48.8 MB)