# Device connection topology
The OpenGate platform supports different device connection strategies:
# Direct connection strategy
Most common scenario used by endpoint or gateway devices.
# Indirect connection strategy
Used in scenarios that monitorized devices are behind a device (called gateway) or in most complex scenarios that implement non transparent Mesh Networks. To support this kind of scenarios the platform uses the concept of path that associated to the device Identifier (deviceId) allows to know which devices has to be traversed in order to reach the destination:
The endpoint device in case of operations, diagnostics sent by the plaftorm.
The platform in case of events, responses, etc. sent by the endpoint device.
# Indirect connection scenarios
Taking an indirect connection scenario we have:
- A gateway device with the id:
- An intermediate device connected to the Gateway with the id: "Device_1"
- Two Endpoint devices connected to the intermediate device with the ids: "Device_1_1" and "Device_1_2" respectively.
From a platform point of view, the
deviceId parameter values are:
- To reach the Gateway:
- "deviceId": "GatewayA"
- "path": 
- To reach the intermediate device:
- "deviceId": "Device_1"
- "path": ["GatewayA"]
- To reach an endpoint device:
- "deviceId": "Device_1_1"
- "path": ["GatewayA", "Device_1"]