Gateways provide the wireless network access for the End Devices, relaying data to and from the Senet Network Server via IP backhaul (Ethernet, Wi-Fi, 3 or 4 G cellular or satellite). As part of relaying data from End Devices, Gateways include RF meta-data about the data’s reception characteristics. The Network Server in turn leverages this information in real time to optimize the End Device.
Gateways are deployed to meet application, geographical, and End Device density coverage requirements. Coverage depends on topology characteristics and varies among rural, suburban, and urban environments. To meet these various needs, Gateways are available in a variety of sizes and may be deployed to provide indoor and outdoor coverage.
In order to integrate your Gateway with Senet's Network, it must be on-boarded. This process involves:
Registration and subsequent approval from Senet.
Installation & configuration of a supported packet forwarder.
Once approval is received your Gateway's packet forwarder will communicate with Senet's network. The level of security depends on the packet forwarder implementation. Currently Senet supports the following options:
Senet Packet Forwarder
This integration option is typically used by customers requiring additional deployment flexibility and security beyond that offered by the Semtech Packet Forwarder. Senet's Packet Forwarder is firewall friendly and secure.
Senet Packet Forwarder for RAN providers
This integration option is applicable to Radio Access Network (RAN) Providers deploying Gateways at scale. This option increases security over the standard Senet Packet forwarder, which includes restricting local user accounts and preventing remote access.
This integration option is typically used by developers during early stage product creation. Most Gateway manufacturers have pre-installed the Semtech Packet Forwarder. Onboarding these Gateways requires simple configuration and registration.
This integration option is typically used by developers during early stage product creation. Onboarding these Gateways requires simple configuration and registration.
Gateway Registration and Software Installation is only required for devices that are new to the Senet Network. If Senet provided the Gateway, no further action is necessary.
Semtech Packet Forwarder
|Tektelic KONA Micro||2.1.3, 2.3.4, 3.0.2||US915, EU868, IN865|
|Tektelic KONA 16 Macro||3.1.3, 3.3.0, 4.0.3||US915, EU868, AS923, AU915|
|Tektelic KONA 64 Mega||3.2.6, 3.3.0, 4.0.2||US915|
|MultiTech Conduit - mLinux||3.1.x, 4.x.x, 5.x.x||US915, EU868, IN865, AU915, AS923|
|MultiTech Conduit AP - mLinux||3.1.x, 4.x.x, 5.x.x||US915, EU868, IN865, AU915, AS923|
|MultiTech Conduit IP67 - mLinux||3.1.x, 4.x.x, 5.x.x||US915, EU868, IN865, AU915, AS923|
|MultiTech Conduit IP67 16 Channel - mLinux||4.x.x, 5.x.x||US915, EU868|
|MultiTech Conduit - mPower (AEP)||3.1.x, 4.x.x, 5.x.x||US915, EU868, IN865, AU915, AS923|
|MultiTech Conduit AP - mPower (AEP)||3.1.x, 4.x.x, 5.x.x||US915, EU868, IN865, AU915, AS923|
|MultiTech Conduit IP67 - mPower (AEP)||4.x.x, 5.x.x||US915, EU868, IN865, AU915, AS923|
|RAK Wireless||US915, AU915, AS923|
|Laird Sentrius||184.108.40.206+||US915, EU868, AS923|
|Kerlink Wirnet iBTS Compact||3.1.16||US915|
|Kerlink Wirnet iBTS 64||3.1.16||US915|
|Kerlink Wirnet Station||OS 2.x||US915, IN865|
Gateway Communication Ports in Use
Below is a table of ports used by the gateway to communicate with the Senet Network.