[doc] architecture: add process diagram
This commit is contained in:
parent
0c79e230b9
commit
191521751b
|
@ -62,7 +62,28 @@ Each step of this protocol corresponds to a different module:
|
|||
The positioning server, or computation server, takes as an input the
|
||||
data from the aggregation server, and outputs the computed positions,
|
||||
thanks to the //OwlPS Positioner// module, described in detail in
|
||||
owlps-positionerd.t2t.
|
||||
owlps-positionerd.t2t. These results can be sent to the mobile
|
||||
terminal or treated otherwise, for instance by a program such as OwlPS
|
||||
UDP-to-HTTP (cf. owlps-udp-to-http.t2t).
|
||||
|
||||
|
||||
The figure below summarises this process:
|
||||
|
||||
```
|
||||
+--------------+ positioning request +----------------+
|
||||
| OwlPS Client | ---------------------------> | OwlPS Listener |
|
||||
+--------------+ +----------------+
|
||||
^ |
|
||||
| |
|
||||
| | captured
|
||||
computed | | request
|
||||
position | |
|
||||
| |
|
||||
| V
|
||||
+------------------+ aggregated request +------------------+
|
||||
| OwlPS Positioner | <------------------------ | OwlPS Aggregator |
|
||||
+------------------+ +------------------+
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue