diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2017-07-04 23:08:44 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2017-08-27 03:52:43 +0200 |
| commit | 218e4b4aa0fc6de842ff820dec8e97d1f083268a (patch) | |
| tree | 268a6e509270b1c80a36dd1a526da41a9b01a8e0 /doc/oml-interface.txt | |
| parent | 5ea6bfce56d6ae7be6d85e05b5e4eaebc94d1005 (diff) | |
move openbsc/* to repos root
This is the first step in creating this repository from the legacy openbsc.git.
Like all other Osmocom repositories, keep the autoconf and automake files in
the repository root. openbsc.git has been the sole exception, which ends now.
Change-Id: I9c6f2a448d9cb1cc088cf1cf6918b69d7e69b4e7
Diffstat (limited to 'doc/oml-interface.txt')
| -rw-r--r-- | doc/oml-interface.txt | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/oml-interface.txt b/doc/oml-interface.txt new file mode 100644 index 000000000..02bead77a --- /dev/null +++ b/doc/oml-interface.txt @@ -0,0 +1,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 |