catch ~Next ~Previous ~Home! See also ~Patrol and ~Business networks!
Epsilon series Military Sensor Sensor4Xi Networks:
[001]~ MILITARY NET
[002]~ NCOIC
[003]~ IP Network
[004]~ Mobile Ad Hoc Networks
[005]~ Challenges
[006]~ Link 16 Protocol
[007]~ JDAM
[008]~ FADEC
[009]~ Wireless
[010]~ GPS
[011]~ Galileo
[012]~ Glonass
[013]~ LAN
[014]~ SCA
[015]~ Virtual Design
[016]~ Semantic Web
[017]~ Reconfigurable_Computing
[018]~ Fighter
[019]~ Carrier
[020]~ Operating System
[021]~ PATROL NET AND BUSINESS NET































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[001] Sensor4Xi Network ~ Military Sensor: MILITARY NET

Sensor4Xi has been designed for MILITARY NET.


catch: ~[content] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[002] Sensor4Xi Network ~ Military Sensor NCOIC

S&S takes into account Network Centric Operations Industry Consortium's standards.
~ same is true also with other network standards developed by standard organizations
~ Sensors4Xi around Base4Xi collaborate closely with Base4Xi which may embed a base stations based on OBSAI standard
~ Xi, which drops Sensor4Xi, acts as a ad-hoc network master to a Sensor4Xi



catch: ~[content] ~[previous] ~[organization] ~[wireless] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[003] Sensor4Xi Network ~ Military Sensor IP Network

IP Network
~ Sensor4Xi is capable to use IP protocol to communicate with Base4Xi
~ Base4Xi embeds OBSAI standard base station
~ (Sensor4Xi---Xi) and (Base4Xi---Sensor4Xi aroundBase4Xi) communication is IP-based



catch: ~[content] ~[previous] ~[ip_network] ~[organization] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[004] Sensor4Xi Network ~ Military Sensor Mobile Ad Hoc Networks

Xi creates mobile Ad Hoc Sensor4Xi Networks
~ Xi drops Sensors4Xi in the beginning of it's mission to reprogrammed locations
~ Xi may also drop Sensors4Xi around Base4Xi
~ Base4Xi analyzes sensor data collected by Xis sheltering inside it and orders them to drop more Sensors4Xi, if necessary
~ mobile ad-hoc Sensor4Xi networks can also be setup by manned helicopter, SOF with ground vehicles, for example
~ (Base4Xi-Sensors4Xi) and (Xi-dropped Sensors4Xi around a target) are typical networks created


catch: ~[content] ~[previous] ~[mobile_ad_hoc_network] ~[wireless] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[005] Sensor4Xi Network ~ Military Sensor Challenges

Challenges:
~ power at remote theaters
~ limited processing capability
~ networking
~ invisibility
~ durability

Solutions in MILITARY NET:
~ Sensors4Xi are programmed to sensor in specified time intervals
~ it is the Base4Xi, which filters and processes sensored data; not sensors not Xi
~ although Sensors4Xi are capable to form a ad-hoc network with themselves, they typically communicate only with Xi
~ uploading and downloading happens only when Xi requests it
~ Sensor4Xi has been designed to be droppable and last in challenging remote environments



catch: ~[content] ~[previous] ~[uav_control_strategy] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[006] Sensor4Xi Network ~ Military Sensor Link 16 Protocol

Link 16 protocol is not used by Sensors4Xi
~ Link 16 is used by Base4Xi which already has processed, filteres and analyzed sensor data collected from Sensors4Xi
~ with data collected from sensors and with it's own sensor data Xi provides valuable information to network and command and control center
~ Sensor4Xi's role in this concept is to focus on programmed sensoring in specified time intervals and tp upload sensored data, when requested



catch: ~[content] ~[previous] ~[link_16] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[007] Sensor4Xi Network ~ Military Sensor JDAM

Pod4Xi embedding Xi has been designed for JDAM.
~ Xi itself contains a number of Sensor4Xi to be dropped to target area
~ one can think Pod4Xi/Xi/Sensor4Xi package as a JDAM


catch: ~[content] ~[previous] ~[jdam] ~[pod] ~[targeting_pod] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[008] Sensor4Xi Network ~ Military Sensor FADEC

Network-centric Xi's engine can be analysed and tuned using Xi's remotely controllable FADEC.
~ analysis and control of Xi's engine can be done in real-time while Xi is flying
~ a mobile Freedom Device can be plugged into Xi and connected to network when Xi is not flying
~ autonomous and network-centric Base4Xi is capable to communicate with Xi's FADEC when Xi is sheltering at Base4Xi
~ typically FADEC sensor is embedded inside Xi or Base4Xi
~ however, it would be possible for a Sensor4Xi carried by Xi to be a FADEC sensor, which Xi would not drop


catch: ~[content] ~[previous] ~[fadec] ~[engine_control] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[009] Sensor4Xi Network ~ Military Sensor Wireless

Xis build wireless ad-hoc networks
~ after having hatched in the air Xi connects itself to network with a trusteed Base4Xi
~ Xi drops Sensors4Xi and created wireless sensor networks around targets
~ around Base4Xi wireless Sensors4Xi dropped by Xi create a wireless network with Base4Xi
~ wireless networking capability of Sensor4Xi offers possibility to drop Sensors4Xi, where requested
~ Freedom Devices (Base4Xi/Xi/Sensor4Xi/FD1/FD2/PRD) communication is wireless and they can communicate with each others and with other systems



catch: ~[content] ~[previous] ~[wireless] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[010] Sensor4Xi Network ~ Military Sensor GPS

Sensor4Xi does not use GPS.
~ instead, Xi and Base4Xi use GPS; this solutions saves power in Sensor4Xi
~ when Sensor4Xi is dropped, Xi registers Sensors4Xi location
~ Xi downloads to Base4Xi locations of dropped Sensors4Xi



catch: ~[content] ~[previous] ~[gps] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[011] Sensor4Xi Network ~ Military Sensor Galileo

Sensor4Xi does not use Galileo.
~ instead, Xi will be able to use Galileo for joint operations
~ Base4Xi and Xi will Galileo and they are the ones, which know Sensor4Xi location



catch: ~[content] ~[previous] ~[galileo] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[012] Sensor4Xi Network ~ Military Sensor Glonass

Glonass is explored for network-centric operations.
~ Sensor4Xi will not use Glonass
~ instead, Xi and Base4Xi might use Glonass
~ Base4Xi and Xi would use Glonass and they are the ones, which know Sensor4Xi location


catch: ~[content] ~[previous] ~[glonass] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[013] Sensor4Xi Network ~ Military Sensor LAN

Sensor4Xi uses wireless LAN
~ Sensors4Xi of sheltering Xi can connect themselves to Base4Xi's LAN nodes
~ Sensors4Xi around Base4Xi can communicate with Base4Xi's LAN nodes


catch: ~[content] ~[previous] ~[lan] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[014] Sensor4Xi Network ~ Military Sensor SCA

Xi both embeds and uses SCA with other networked systems
~ Sensor4Xi does not embed SCA
~ this solutions is due to limited power and processing capacities of Sensor4Xi



catch: ~[content] ~[previous] ~[sca] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[015] Sensor4Xi Network ~ Military Sensor Virtual_Design

Sensor4Xi's development processes use Virtual Design.



catch: ~[content] ~[previous] ~[virtual_design] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[016] Sensor4Xi Network ~ Military Sensor Semantic Web

Network-centric Sensor4Xi is based on the Semantic Web concept.
~ networked Sensor4Xi has been modelled using OWL/RDF/XML
~ Sensor4Xi's machine readable OWL/RDF/XML data can be read and interpreted by other networked machines such as Xi
~ artificial intelligence systems are used by Xi and Base4Xi, not Sensor4Xi




catch: ~[content] ~[previous] ~[ontology] ~[owl] ~[rdf] ~[xml] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[017] Sensor4Xi Network ~ Military Sensor Reconfigurable Computing

Sensor4Xi's architecure is based on Reconfigurable Computing.
~ designed for network-centric operations Sensor4Xi utilizes Reconfigurable Computing
~ Sensor4Xi can be modified & updated via Xi and Base4Xi
~ tailoring to a mission and target theater can be done in real-time, if required



catch: ~[content] ~[previous] ~[reconfigurable_computing] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[018] Sensor4Xi Network ~ Military Sensor Fighter

Xi is capable to operate in the same network as the Fighter which deploys it.
~ typically Sensor4Xi communicates only with Base4Xi and Xi
~ mobile Freedom Device inside fighter can wirelessly communicate with Sensor4Xi
~ fighter's computer system can wirelessly communicate with Sensor4Xi



catch: ~[content] ~[previous] ~[fighter_related_hardware] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[019] Sensor4Xi Network ~ Military Sensor Carrier

Xi is capable to operate in the same network as the carrier, which deploys the fighter with Pod4Xi (Xi inside).
~ typically Sensor4Xi communicates only with Base4Xi and Xi
~ mobile Freedom Device inside carrier can wirelessly communicate with Sensor4Xi
~ carrier's computer system can wirelessly communicate with Sensor4Xi



catch: ~[content] ~[previous] ~[carrier_related_hardware] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[020] Sensor4Xi Network ~ Military Sensor Operating System

Sensor4Xi uses network-centric operating system and is capable to communicate with other network-centric operating systems.
~ OS is a sensor operating system, embedded and real-time



catch: ~[content] ~[previous] ~[operating_system] ~[next]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[021] Sensor4Xi Network ~ Military Sensor PATROL NET AND BUSINESS NET

Sensor4Xi may also be part of PATROL NET and BUSINESS NET.
~ Sensors4Xi dropped by Xi typically communicate with Xi only
~ those Sensors4Xi dropped around Base4Xi, communicate with Base4Xi
~ Sensor4Xi is also an independent wireless ad-hoc mobile sensor programmable to other networks



catch: ~[content] ~[previous]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Small & Smart Inc reserves rights to change this specification
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~