Robust Web Services in Heterogenous Military Networks
Lund et al
soa services service oriented tactical edge networking
@article{lund:ieee-comm2010,
title={Robust Web Services in Heterogenous Military Networks},
author={Ketil Lund and Espen Skjervold and Frank T. Johnsen and
Trude Hafs\OE e and Anders Eggen},
journal={{IEEE} Communications},
year={2010},
month={October},
volume={48},
number={10},
pages={78--83},
}
[ Overview slides ]
NATO standardizing on service oriented architectures
- Enable interoperability, competition
- Loose coupling of applications
- Not reasonable to expect everyone to use same software
- Must define the interfaces
SOA most commonly realized through XML, SOAP, HTTP based protocols
In appling to disadvantaged tactical networks, must
- Reduce amount and size of traffic generated
- Eliminate end-to-end connectivity dependence
- Manage network heterogeneity, render transparent
Compression alone cannot control volume enough, must also
- Cache, reuse matching messages
- Switch to pub/sub rather than request based paradigm
- Support group dissemination, sharing messages
- Filter, possibly transform content
Introduce store-and-forward proxy to mitigate end-to-end connectivity
- Minor increase in computational cost
- Requires higher level corruption and error control at endpoints
Heterogenous networks
- Must manage differences in transmission & processing rates, buffers
- Have to store-and-forward at application layer to manage underlying protocols
Proxy core functionality does not rely on inspecting message content
Additional functionality may read, manipulate messages at content level
- Caching, reuse
- Publish/subscribe
- Proxy near service continually polls service
- Proxy near client responds to polls with most recent response
- Proxy near service only propagates changes
- Diff propagation
Of note:
- STANAG 4406 Annex C and E
- WS-Notification, WS-Eventing
- TACOMS tactical communications standard