Getting Started with MCL-Net V4 > MCL-Net V4 Workflow

Overview

As a communications tool, MCL-Net V4 has an important role on the overall communication architecture of the MCL project implementation.

MCL-Net V4 is used to synchronize data between concurrent mobile devices and one or more servers.

If it becomes necessary for your mobile devices to access your own databases, MCL-Net V4, alongside MCL-Bridge, ensures a secure and reliable connection between your mobile device and those external systems.

When implementing your MCL-Net V4 network, consider your business needs and what the desired workflow should be.

Below are MCL-Net V4 workflow examples:

Mobile Device Data Synchronization with one Local Server

MCL-Net V4 is installed in one location.

MCL-Net V4 ensures file exchange with the host (send file/receive file).

Concurrent mobile devices communicate with the MCL-Net Server via Ethernet, USB, WiFi and/or LAN/WAN (GPRS/UMTS/4G). The type of communication is interchangeable. For instance, an operator may communicate with an MCL-Net server via WiFi and, then, switch to a GPRS communication.

Mobile Device Data Synchronization with more than one server and between servers

More than one MCL-Net Server, each installed in a different location, ensure file exchange with the host (send file/receive file).

This setup is useful when customer sites/locations are isolated from each other.

MCL-Net Server communication with External Databases

The MCL-Net server uses MCL-Bridge to communicate with the customer's databases and/or ensure file exchange (send file/receive file).