Harald Welte
cb8f443399
SM's need to be transferred over their own RLL connection on SAPI3, rather than the default SAPI0 connection that we're using for signalling like 04.08 RR/MM/CC. This is not that much of a problem in the case of SMS SUBMIT from the MS to the netwrok. In that case, the MS will start its primary RLL connection with SAPI3, and we can just respond with SAPI3. However, in the case of SMS DELIVER to a MS, we first page the MS, it then establishes SAPI0. We then need to explicitly request the establishment of a SAPI3 RLL connection, before we can send CP-DATA with our RP-DATA and DELIVER RPDU Now that we have the bsc_rll.c code, we can actually wait for a paging response, and from the paging response request the establishment of the SAPI3 connection. We will be called back once that connection is open and can successively start transmission of the SM. |
||
---|---|---|
.. | ||
doc | ||
include | ||
src | ||
tests | ||
tools | ||
AUTHORS | ||
COPYING | ||
Makefile.am | ||
README | ||
configure.in | ||
openbsc.pc.in |
README
About OpenBSC ============= OpenBSC is a minimalistic implementation of the GSM Network, with particular emphasis on the functionality typically provided by the BSC, MSC, HLR, VLR. Its only current interface is a mISDN based E1 interface utilizing the A-bis protocol between BSC and BTS. In other words, you can connect an existing GSM Base Transceiver Station (BTS) through E1 to OpenBSC. So far, it has only been tested with the Siemens microBTS BS-11. Test reports with other BTS are appreciated! This project is still in its early days, and there are lots of areas where it doesn't behave as per GSM spec. December 29, 2008 Harald Welte <laforge@gnumonks.org>