📱Telco
Overview
The objective of this project is provide a set of examples that demonstrates some of the core Joule platform capabilities. Each use case builds upon the previous to represent how use cases can be built and tested incrementally with the final use case combining all functionality to demonstrate a simple direct telco marketing campaign using simulated streaming mobile events and geospatial analytics.
A set of use case examples have been defined as a sequence to gain how incremental functionality is developed for a target use case. We start from the basic filtering of user events to direct marketing using real-time geospatial triggers. All use cases source event data from a basic mobile event simulator described further in the document.
IMSI Opt-out filtering
Enrich events with device information
Anonymise IMSI field
Trigger location tracking using predefined geofences
Generate geospatial marketing messages based on location
Good to know: depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
Setting up
Clone the project repository is hosted on Gitlab
Components
The following Joule platform components are used
Processors
Filtering
Anonymisation
Geospatial
Joule SDK for custom plugins
Integrations
Geode, caching layer to provide low latency data to processing clients, integrated to Postgres
Postgres, database holding reference data and hosted with in a Docker container
InfluxDB, time series database for processed events
Joule Image
The latest Joule image can be pulled from the following docker hub link
Event Simulator
Events for these examples are generated using a simulator, events are modelled on simple mobile events. The simulator has been developed using the Joule SDK by extending the AbstractConsumerTransport
class.
Events are generated for five IMSIs to simulate entities moving through London streets. The default journey provided has IMSIs travelling from Waterloo station to St Pauls and back until the example process is stopped Each IMSI speed and direction is dynamically set on each movement iteration to simulate the general movement of entities in the system. Along with entity movement, the algorithm sets the corresponding connected cell tower, geospatial coordinates, data usage and dropped calls.
Event Structure
The following fields are available on each event
Note
You can provide your own journey path, see the below example, and geofences, see further down in the document
Support
Creating examples and a platform takes a significant amount of work. Joule is independently developed, funded and maintained by Fractalworks Ltd. If you would like to support please contact Fractalworks enquiries
Last updated