summaryrefslogtreecommitdiffstats
path: root/openbsc/doc/oml-interface.txt
blob: 02bead77a3e891565ee899a240da00e51bd91b3d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
oml interface design notes

problems:

* there is no way how to tag a command sent to the BTS, with the response
  having the same tag to identify the originator of the command
* therefore, we can have e.g. both the BSC and the OML interface send a
  SET ATTRIBUTE message, where the responses would end up at the wrong
  query.
* The BTS has 10s to ACK/NACK a command. We do not run any timers.

the only possible solutions i can imagine:
* have some kind of exclusive locking, where the OML interface gets blocked
  from the BSC and is exclusively assigned to the OML console until all commands
  of the OML console have terminated.  This can either be done explicitly
  dynamically or on demand

* use the OML interface synchronously, i.e. always wait for the response from
  the BTS before

* unilateral / unsolicited messages need to be broadcasted to both the BSC and
  the OML console