M-Switch User Server

M-Switch for Constrained Networks is sold in two configurations:

1. M-Switch User Server. Usually deployed on a mobile unit (such as an aircraft or naval vessel), theUser Server supports local users and is used for communication with other Constrained Network Servers and/or the M-Switch Gateway.
2. M-Switch Gateway. Used to exchange messages between systems running on high quality links and those running over constrained networks. The M-Switch Constrained Network Gateway does not support any local clients, except those necessary for configuration and administration purposes.

A key feature of M-Switch for Constrained Networks is the ability to support and map between multiple protocols using a channel architecture, with different channels for different protocols. Multiple networks can be configured and a channel associated with each network, messages can then be routed between the various networks. Where a destination can be reached over multiple networks, route weighting can be used to select the preferred route taking into account factors such as message size and priority in the choice.

ACP 142 supports messaging over both IP and STANAG 5066. Whilst IP is suitable for most SatCom networks, Isode strongly recommends running ACP 142 over STANAG 5066 for HF networks and provides its own STANAG 5066 Server, Icon 5066, for this purpose.

As can be seen from the diagram above, Isode’s approach to constrained bandwidth networks is to use server/server communication over the constrained links, rather than client/server. This means that a server will always be used, even to support a single user. The advantage of this approach is that the client (and user) is isolated from performance problems of the underlying network, and that slow network performance does not slow down the user interface. This approach also means that special low-bandwidth clients are not needed; any standard familiar client can be used.

A consequence of this is that Isode’s optimized messaging protocols in M-Switch, and other messaging server products (in particular M-Box and M-Store), will always communicate through M-Switch and so do not need optimized protocol support.

The central protocol to Isode’s constrained communication solution is ACP 142, sometimes known as ‘P_Mul’. ACP 142 provides reliable multicast, which is an essential base service. ACP 142 is implemented as a channel in M-Switch products. M-Switch products use channels for each of the various protocols that it supports. The ACP 142 channel runs as a server, to process incoming requests.

M-Switch provides extended EMCON extensions to support broadcast only networks (e.g. NATO BRASS (Broadcast as Ship to Shore)) and extended outages. The two mode model of ACP 142 EMCON is extended to four modes, and the option is added to treat a message as delivered after a configurable number of transmissions.

Two network mappings are provided for ACP 142 protocols. The first is to use IP, which is widely supported and ideal for some underlying networks and in particular for Satcom. ACP 142 uses UDP to map onto IP, and CO ACP 142 uses TCP. ACP 142 utilizes IP multicast addressing.

The second mapping is to use the STANAG 5066 protocol. The ACP 142 channel accesses a STANAG 5066 server using the STANAG 5066 SIS (Subnet Interface Service) protocol. Isode’s own STANAG 5066 Server, Icon 5066, is a modem-independent STANAG 5066 server, enabling applications to work efficiently over HF Modems/Radios and allowing multiple applications to work simultaneously.