cncto/kəˈnɛkto/ = conecto @cnc iot/ir21, sbc and ggsn locally bau roaming between operator and...
TRANSCRIPT
ScalableandcostefficientsolutionsforMobileVirtualNetworkOperatorslookingtode-risktheMVNOset-upprocessandcreateasimple,honestandcompleteservicefortheircustomersandbeasuccessfulMVNO
cncto /kəˈnɛkto/[email protected]
Why is Conecto talking about this:Conecto rolled out the largest single SIM order to the most MVNO brands of any
MVNE, MVNA or MVNx in history in 2017…While also rolling out its US IMSIs on other
Partner SIMs and other IoT services…… with a noticeably higher ARPU than
expected – why?
cncto/kəˈnɛkto/[email protected]
The Agenda:How new platforms are allowing new business models / higher ARPU in mobile and IoT by:1) reatime reporting and data for pushing apps, links, relevant geo information2) multi IMSI, multi number3) Apps as a service differentiator4) handset trends5) IoT on the same cloud platform benefits
An MVNO or IoT player needs to be
Niche, Differentiate (especially from MNO)
Why does multi IMSI matter?
Conecto is the first MVNx to:1) Be truly multi-brand, multi-SKU, multi IMSI
from the core up: This means its MVNOs can have three levels of resellers which can migrate between prepay, postpay as well as across resellers.
2) The first MVNx to allow MVNOs to grow from small MVNA type brand with little investment through MVNE, full MVNO, to buying out the full system and running themselves, with a single set of API, single billing system across as many countries
3) Be fully cloud, software defined and virtual for all services: when we say it can be anywhere, we mean anywhere
The world is becoming more international by the day, both in IoT and the consumer space:
Ax
By.
CzReduced roaming prices great for travel and travellers, however it just does not
work for the huge growing base of people who live in another country. This however is a growing market for MNOs globally that we are allowing MNO and
MVNOs to tap: winning back the SIM of people who have moved to another country and their main SIM is now from that country. These are typically high
ARPU customers
Only around 30% of smartphone users download and update their own apps to their smartphone. The rest need help… or a simple, relevant, timely link from their mobile operator / MVNO
Sometimes you have to
Keep it Simpler Sir!
Sending a direct link to the user to whichever device they have:1. Much bigger uptake of apps2. Easier to keep apps up to date3. Automatically sends a new link if they
use a different Operating System with the same SIM
Conecto has 400 pages of APIs but its not all about 4G, APPs, and tech, sometimes USSD and SMS is quicker, easier and drives higher ARPU
Sometimes you have to
Keep it Simpler Still
Sometimes to grow / get data you need data, but don’t always have coverage:1. With low coverage in some travel
environments, such as approaching a border or a port; a phone trying to update via an app or a mobile web page will go into high power mode, use 5-10% of battery…. And still not do what you wanted to do
2. Or you can use USSD to capture a request, the sending CLID and call and API before the customer gets distracted by emails, messages, updates, etc. in data range… you are welcome!
Handset usage in MVNOs. These vary by MVNO, but you need to adjust Pricing to all these users – while keeping simple.
Conecto can map handsets to users and push apps to them
Create bundles and measure their take
up
Analyse their take-up against devices, value add Apps
Make sure you have the bundles /
services for low end and target high-end
better
• How many MVNO offerings cater for this many generations of devices (consumer types / demo / spend profile)?
• How many MVNOs are underselling to high end phone customers?
Handset usage can vary by customers, so are all iPhone, some iOS/Android v.Xupwards, the latter can be complicated
Conecto can put apps on the SIM top ensure even the newer androids with no OMA compliance can be configured
What percentage of your ARPU assurance
tools work across 100% of base
What can you do to address this
The answer usually ends up with deeper
access to location, SIM profile, Wholesale up
CDRS
• How much data revenue is lost from not being able to configure the newer devices via a simpleOTA method if at all
• How much ARPU is lot from a 10 min customer care call to configure a handset
IMSI donation takes 6 to 18 Months for an MNO with an end to end solution in place and fully tested and signed off.
Conecto can demo to launch via Cloud, deploy local hybrid, migrate local service on same SIM, System, APIs, etc.
Local MSISDNs + Roaming
Immediate reservation / allocation of local
numbers (and IMSIs) added to service
No technical Integration needed, demo in a
week, 10,000+ SIMs in a month, MNO owns customers, show first success: start win-win
Local Roaming Exclusive
Add Locals IMSIs to new SIMs, OTA existing
SIMs, Implement discounted roaming, via Clearing IOT/IR21, SBC
and GGSN locally
BAU Roaming between operator and Conecto US IMSI, local traffic locked to local MNO,
start testing LIVE / Real SIMs from Month 3
Local IMSITurn on Local IMSI
service, as light or as full a service can be
implemented as required by chosen
MNO
Full service with Local IMSI in country / any roaming agreements
MNO has, Travel IMSI elsewhere.
Local Number allocated on Conecto Cloud Service,
customer owned by MNO
Local SBC and GGSN keeps local traffic local,
Roaming exclusive keeps full revenue / service
control
Full local system, ss7 signaling switched
overnight when fully built, tested and signed-off, MNO roaming footprint
used where wished
The Conecto group has multiple full US IMSI ranges, has its own US sites, and is a full GSMA Member
A unique regional group
With key Global USPs
The Group access to full IMSI ranges ran by our GSMA member group company, and own networks, plus the way we are set-up and run has numerous benefits that are unique:1. Conecto, and its customers can have their own
agreements on 1M, 10M, 100M, etc. IMSIs routed in multiple ways as we own and fully control our own ranges
2. Settling these bills is BaU through industry standard DCH, FCH, GRX, IPX
3. Routing the traffic is standard over IPX, cross connect, leased line
4. Agreements can be bilateral with a full GSMA member, that is also US – which is a rare and
5. Fully cloud based, flexible ITU, ANSI, M3x, M2x, etc, etc.6. Our IMSI ranges are not limited in use for M2M, etc.
Previous platform / market avg. ARPU
Customer ARPU on Conecto
it is important for certain types of IoT to be
Multi-IMSI, Voice and SMS
What does that mean for IoT I hear?
While present MNOs have single IMSI covered :1) Multi IMSI can save a man visit to swap
out a SIM / move a machine and that saves companies $1000’s that they are prepared to pay for in higher revenue and usage.
2) Multi IMSI means more coverage, which means more devices, more use cases and more usage of the service.
3) Voice and Text, easily manageable on a fully cloud, NFV, SDN service without increasing cost to serve, drives wider, higher and more usage.
A fully cloud platform allows for multiple IoT configurations on the same platform, including voice and SMS :
Just because most IoT is data first, it does not mean Voice and Text is not sometimes needed.
Signalling request for Cell ID can use up to 1000% less battery than data channel and GPRS, that’s days vs. hours or weeks/months vs. days and makes more possibleLike with the mobile customers, sometimes voice and SMS/USSD commands are just easier, quicker, more successful and use fewer resources than a data channel which may not be even strong enough after using all that data and battery…