Professional Documents
Culture Documents
4.0 Monetization
4.0 Monetization
Agenda
Introduction
Monetization Configuration
3
Capabilities Of Monetization
Location
Revenue Smart
Analytics Based
Generator Connectivity
Services
Subscriber Push Notification,
Analytics SMS, Broadcast
Captive Portal Messages
(dashboard)
Notifications sent
Advertisement based on hotspot
location
Revenue Statistics Mobile App Location Based
Advertisement
4
Call Flows & Test Cases
5
Hotspot Finder for Mobile Users
Mobile User Opens the Monetization Client and Existing
User can click network
on the infrastructure
hotspot to view thecomponents
details and get
can see “Hotspot Finder” option. navigation.
Monetization Client has a list of all the hotspot locations. So, it
Internet Cloud User can search
proactively shows Wi-fI Hotspot. Wi-Fi hotspots.
WAG all the nearby
AP / WLC VoMSAL
SMSC IN / SDP
1
Access Middleware Payment Gateway
Controller
User
Monetization Solution for
STL components existing
network
in network
4
2 Monetization 3
Client
Elitecore
Monetization
Server Wi-Fi
SMP
Ad Server
Push Notification to Mobile User in WI-FI Range
SMSC IN / SDP
1
Access Middleware Payment Gateway
Controller
User
Monetization Solution for STL components existing
network in network
5 2
Monetization 3
Client
Monetization
STL
Server Wi-Fi
4
SMP
Ad Server
Monetization Configuration
SNMP Alert Configuration
Community Strings
• Community Strings are same as passwords. They are used to allow authorized users to access the
SNMP agent on a device.
9
SNMP Alert Configuration
• Many administrators never change community strings from the defaults “Public” for read-only, and
“Private” for read-write.
• Read-only (RO): Read-only strings only allow information to be pulled from the agent.
• Read-write (RW): Read-write strings are much more powerful, and can allow re-configuration of
many of a device’s properties
10
SNMP Alert Configuration
• SNMP Alert Configuration is a SNMP Alert notification service offered by monetization server to
send different alerts/warnings. When a Particular Event (Server Up/down, Caching Data, etc) takes
place, monetization server sends a SNMP Alert to Configured SNMP Server. SNMP Trap Listener can
be configured in such a way that alarms will be generated for particular trap.
Following Alerts can be configured in Monetization server manager for various misbehaviors:
1) Monetization Server
• Monetization Server Shutdown: This trap is generated when monetization server is down or
shutdown.
• Monetization Server Startup: This trap is generated when monetization server is started or
restarted. 11
SNMP Alert Configuration
• Caching Data: This trap is generated when Tomcat starts up and all the required data is cached
successfully.
• Voucher Limit Over: This trap is generated when voucher limit of a particular voucher has been
reached.
12
SNMP Alert Configuration
4) Monetization DB
Database Up: This trap is generated when database pointing to monetization server is up.
Database Down: This trap is generated when database pointing to monetization server is down.
No Database Connection: This trap is generated when connection between database pointing to
monetization server and monetization server has been lost.
Query Timeout: This trap is generated when database pointing to monetization server is does not
respond in time for any particular action.
13
SNMP Alert Configuration
License Generic: This trap is generated for some common activities related to license as mentioned
below.
Invalid License Validation: This trap is generated when license validation is invalid.
Invalid Secret key: This trap is generated when secret key generated is invalid.
14
SNMP Alert Configuration
OTP initialize failure: This trap is generated when OTP service startup for sent OTP service fails.
7) Monetization Thread
Thread Pool Size Increased: This trap is generated when no. of threads for handling requests has
been increased. If a request cannot be queued, a new thread is created unless this would exceed
maximum Pool Size, in which case, the task will be rejected.
15
SNMP Alert Configuration
8) Services
Notification Services
1. WPNS connectivity down: This trap is generated when window’s WPNS is down.
2. GCM connectivity down: This trap is generated when google’s GCM is down.
5. APNS connectivity down: This trap is generated when apple’s APNS is down
16
SNMP Alert Configuration
17
SNMP Alert Configuration
18
SNMP Alert Configuration
19
Android Wi-Fi Setting
Wi-Fi offload is a cost-effective access method for mobile broadband. As both subscribers and devices tend to
connect to Wi-Fi whenever it is in reach, mobile operators need to follow their subscribers into the Wi-Fi
environment. The automatic network selection mechanism often exists common in android operating system.
Android Wi-Fi settings being done on the server side will help the subscriber to auto offload the 3G data traffic
over the preferred Wi-Fi network through eliteconnect mobile app, whenever it is in range. Once the device has
selected the Wi-Fi network, the subscriber will be authenticated to be admitted to the network. The
authentication will be as seamless as possible in order to maximize the business case for offloading.
20
Android Wi-Fi Setting
This configuration is required to bind the connection specific details with the respective Wi-Fi profile
setting. The connection specific detail governs the configuration w.r.t. default/preferable connection,
addition of SSID along with security concerns and auto join feature.
21
Android Wi-Fi Setting
22
iOS Wi-Fi Setting
• The automatic network selection and thus eventually Wi-Fi offload mechanism is different when it comes to
IOS operating system. In case of Elite connect mobile application; few IOS settings needs to be configured in
order to auto offload the 3G data traffic over the Wi-Fi network through mobile app, whenever it is in range.
• During installation of profile setting in the elite connect
mobile application in IOS device, the mobile application
sends IMEI, IMSI and other details to the monetization
server. The monetization server responds with a URL to be
launched in to the mobile application. Thereafter, the URL is
launched in the mobile application. The subscriber can view
the IOS profile being created in the monetization server
which could be EAP SIM based or profile based
authentication created in the monetization server. The
subscriber installs the profile in the mobile device.
23
iOS Wi-Fi Setting
24
beyond tomorrow
25