The VergeSense L208 wireless battery-powered sensor has flexible network configuration options, all of which are designed to meet the highest privacy and security standards. See the table below for a comparison of the available options.
VergeSense recommends using the Customer WiFi + Cloud Gateway option where possible for optimal network stability and ease of deployment.
Option |
Totally Isolated |
WiFi + Wired Hardware Gateway |
Customer WiFi + Cloud Gateway |
Overview |
Sensors send data to a gateway over a VergeSense-created WiFi network. The gateway processes data and sends data to the VergeSense cloud over an IOT cellular connection. |
Sensors send data to a gateway over a VergeSense-created WiFi network. The gateway processes data and sends data to the VergeSense cloud over an ethernet connection. |
Sensors connect to an existing guest, IOT, or standard WiFi network and send data to a cloud gateway. The cloud gateway processes data and sends data to the VergeSense Cloud. |
# of Hardware Gateways Required |
1 gateway per ~50 sensors, sensors must be within 125 ft. of a gateway |
1 gateway per ~50 sensors, sensors must be within 125 ft. of a gateway |
None |
Network Stability |
Good |
Better |
Best |
Advantages |
No corporate IT infrastructure is required. |
Increased network stability. No cellular data plan costs. |
Optimal network stability. No hardware gateways to procure, install, or maintain. No cellular data plan costs. |
Great for... |
Small, short-term pilots |
Large or long-term deployments |
Large or long-term deployments |
Frequently Asked Questions
The following answers apply to the wireless L208 sensor.
-
What protocols are used to send data from sensors to gateway and from gateway to cloud? VergeSense Sensors send data to VergeSense Gateways over an 802.11n WiFi network, using WPA2 authentication and HTTPS (for application-layer security). VergeSense AI on the VergeSense Gateway processes raw data into JSON. Processed data (anonymous person counts) is then sent to the VergeSense cloud over MQTT.
-
How is data encrypted? Data-in-motion is encrypted using TLS 1.2. All cloud-hosted databases are encrypted using AES-256.
-
What is the volume of network traffic? Do the sensors cause network interference? Data is sent in small packets and in staggered intervals, thus preventing spikes in network traffic and network interference. Each sensor sends ~30 KB of data to the gateway every 10 minutes. After gateway processing, another ~0.6 KB of data per sensor is transferred from the gateway to the VergeSense Cloud.
-
How do sensors receive firmware updates? The sensors automatically deploy device updates when available. As the sensors or gateways send data to the cloud, they also check for available device updates. If an update is available, it is downloaded and installed. For security purposes, all communication is initiated outbound from the sensor or gateway to the cloud; there is no cloud-to-sensor or gateway-initiated communication inbound.
-
Do we use 802.1x? Yes, sensors can connect to a WPA2 Enterprise network with 802.1x authentication.
-
What type of data is collected? Where is data processed? The sensor wakes and captures a raw data point using its wide-angle (170 degrees) fisheye lens every 10 minutes. The raw data point is a 352x288 array of pixels, which is transmitted to the gateway using a WPA2 80211n network. The VergeSense Gateway processes the data, running the raw sensor data through a processing engine. After completing processing, the raw sensor data is discarded (it is only temporarily stored in RAM). Processed data (anonymous person counts in JSON format) is transmitted to VergeSense’s cloud analytics portal over MQTT using TLS 1.2 encryption.
-
How long is raw sensor data stored? Raw sensor data is processed and discarded within seconds.
Updated
Comments
0 comments
Please sign in to leave a comment.