MDLCoverIPOverview.docVIP

Motorola-CGISS Alarm Control Product Group MDLC over IP Overview Page  PAGE 2 MDLC over IP Overview 3 August 99 Page  PAGE 1 With the MDLC Over IP option, MOSCAD RTUs and MCP-Ts (≥ V3.00) can use IP (Internet Protocol) interface to advanced radio infrastructure (e.g. digital ASTRO IP conventional systems) and to standard IP networks. Most benefits of the MDLC protocol are preserved. MDLC and IP networks can be integrated, as MDLC networking properties are unchanged. Most MOSCAD applications need not be modified when using IP networks. MDLC packets to be transmitted are enveloped inside IP datagrams and sent between remote RTUs or between an MDLC Gateway and RTUs. The MDLC Gateway acts between the field and the SCADA Central to extract the enveloped frames from the IP message. A ToolBox can be connected to one of the RTUs or to a serial port of the MCP-T or to Ethernet port. Each RTU/Gateway is assigned a Site ID. In addition each RTU/Gateway with an IP interface is assigned an IP address. An IP conversion table, which maps Site IDs to IP addresses, is created in the ToolBox and downloaded to the RTUs and MCP-T. Terminal Server RTUs can be connected to IP network via Terminal Servers. The Terminal Server interfaces between the RTU’s serial port (using SLIP -Serial Line IP) and the network. In the diagram below a typical configuration is shown, with RTUs attached via Terminal Server to an IP network. ASTRO IP RTUs can be connected to an ASTRO radio, which is a part of an IP network. The mapping of the radio ID to an IP address is done in the Wireless Network Gateway (WNG) connected via IP network to MDLC Gateway, SCADA Central, etc. In the diagram below, a typical configuration is shown, with RTUs attached with a serial port (using SLIP -Serial Line IP) to ASTRO radios that support IP data capability. The MDLC Gateway attached to the Ethernet LAN at the SCADA Central.