The Meridian Editor is the content management system (CMS) providing the content that powers the Meridian-powered apps. This document provides an overview of the way that data flows in and out of the Meridian Editor.
Meridian Editor Data Flows
Click the image to see an enlarged version.
Meridian Editor data flows to and from four different resources. These resources are: the Meridian SDK, Aruba hardware, Google Cloud Services, and other third-party services.
The Meridian SDK provides the functions that send and receive data from Google Cloud Services, Aruba Hardware, and other third-party services.
It’s helpful to think of the Meridian SDK as running on iOS and Android devices in terms of where data is moving.
In order for the Meridian SDK to send and receive data, both Wi-Fi and Bluetooth need to be enabled on a device with a Meridian-powered SDK app.
Aruba hardware is made up of Aruba controllers, Internet Access Points (IAP), and Sensors for connecting to the Internet and monitoring Beacon deployments.
Beacon hardware sends out Bluetooth Low Energy (BLE) signals that support location and notification services in a Meridian-powered app. Aruba Sensors can also function as Beacons.
As a user with a Meridian-powered SDK app walks through a location with a Beacon deployment, the app uses Location Beacon Bluetooth signals to calculate the user’s blue dot location on a map in real time.
When the app hears a Bluetooth signal from a proximity Beacon, the app contacts the Meridian API over HTTPS to check if a campaign has been assigned to that Beacon. If one has been assigned to the Beacon, the device will show a notification or notify a third-party endpoint.
Aruba controllers and IAPs can be configured to monitor a Beacon network and report the Beacon network status to the Meridian API over HTTPS. Aruba Sensors, when connected to a Wi-Fi network, can also report the Beacon network status.
The Aruba controllers and IAPs are also used to track the location of Aruba Tags for asset tracking. This data is sent to the Meridian API over HTTPS.
The Meridian Editor and the Meridian APIs are hosted on Google Cloud Services. A Meridian-powered SDK app sends and receives data via Meridian APIs over HTTPS.
The Meridian SDK requests are tied to a specific location ID in the Meridian Editor.
For European customers concerned with General Data Protection Regulation (GDPR) requirements, Meridian offers Google Cloud servers hosted entirely within the European Union. For more information about this, please email us at: email@example.com.
Meridian API gets data from the Google Cloud Services datastore. This data includes map images, placemarks, events, pages, and routing.
When changes are made to the Meridian Editor, the Meridian-powered apps are updated with this new information.
On Google Cloud Services, Asset Tracking is used to track the location of Aruba Tags in close to realtime. This data is sent and received through the Meridian API.
As users use a Meridian-powered SDK app in a location, data about that usage is sent to the Meridian API. This data is then passed along to Google Cloud Services for the purposes of gathering that analytics. This analytics data is then collected by the Meridian API’s reports endpoint.