| Harald Welte | 143f1f5 | 2009-10-26 20:38:37 +0100 | [diff] [blame^] | 1 | oml interface design notes |
| 2 | |
| 3 | problems: |
| 4 | |
| 5 | * there is no way how to tag a command sent to the BTS, with the response |
| 6 | having the same tag to identify the originator of the command |
| 7 | * therefore, we can have e.g. both the BSC and the OML interface send a |
| 8 | SET ATTRIBUTE message, where the responses would end up at the wrong |
| 9 | query. |
| 10 | |
| 11 | the only possible solutions i can imagine: |
| 12 | * have some kind of exclusive locking, where the OML interface gets blocked |
| 13 | from the BSC and is exclusively assigned to the OML console until all commands |
| 14 | of the OML console have terminated. This can either be done explicitly |
| 15 | dynamically or on demand |
| 16 | |
| 17 | * use the OML interface synchronously, i.e. always wait for the response from |
| 18 | the BTS before |
| 19 | |
| 20 | * unilateral / unsolicited messages need to be broadcasted to both the BSC and |
| 21 | the OML console |