diff options
author | Harald Welte <laforge@gnumonks.org> | 2009-10-26 20:38:37 +0100 |
---|---|---|
committer | Harald Welte <laforge@gnumonks.org> | 2009-10-26 20:38:37 +0100 |
commit | 143f1f56d94804fdfdd3302aa65cdc14f0b955e9 (patch) | |
tree | 469d19b15bd48651d215ebad93feaf8896ede104 /openbsc/doc/oml-interface.txt | |
parent | eb429b7b44f1c39548a1995cb93484b9cbe2996e (diff) |
add some random thoughts on hopping and the oml interface
Diffstat (limited to 'openbsc/doc/oml-interface.txt')
-rw-r--r-- | openbsc/doc/oml-interface.txt | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/openbsc/doc/oml-interface.txt b/openbsc/doc/oml-interface.txt new file mode 100644 index 000000000..8ddcfea5c --- /dev/null +++ b/openbsc/doc/oml-interface.txt @@ -0,0 +1,21 @@ +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 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 |