How to become an MVNO

The MVNO business depends mostly on the cost-efficiency of its core infrastructure and roaming agreements. This page comes with some preliminary information about our solutions for MVNOs, relevant in terms of market prospection.

How to enter a new market as an MVNO

A Mobile Virtual Network Operator (MVNO) provides services to its subscribers (roaming, voice & data, applications, customer care, handset management, etc.) by making agreements with Mobile Network Operators (MNOs) without owning a radio access network infrastructure.

MVNO video

Types of agreements that have to be signed

When entering a new market, MVNOs get an agreement that gives access to the radio network infrastructure of at least one MNO (Mobile Network Operator – owner of license), always including access to the radio network infrastructure and commercial terms.

The MVNO may or may not have acquired its own MCC (Mobile Country Code) and MNC (Mobile Network Code). In case it did, it has its own IMSI range (International Mobile Subscriber Identity, which identifies the SIM card). In case not, the MVNO also has to acquire an IMSI range from the MNO.

The SIM (Subscriber Identification Module)

MVNOs provide SIM cards to their subscribers for authentication and registration to the network. Each SIM card has an IMSI code with the following structure:

mvno_imsi_high.png
The IMSI code
  • MCC = Mobile Country Code
  • MNC = Mobile Network Code
  • MSIN = Mobile Subscription Identification Number.

The MVNO can have its own [MCC][MNC] codes from the legal authority of the country where the MVNO operates.

The core network infrastructure needed

MVNOs need some or all of the following network components for its business:

  • HSS/HLR (Home Location Register/ Home Subscriber Server) – for authentication, registration and authorization
  • GMSC (Gateway Mobile Switching Center) – for voice
  • GGSN (Gateway GPRS Support Node) – for data
  • SMSC (Short Message Service Center) – for SMSs
  • MMSC (Multimedia Messaging Service Center) – for MMSs.
mvno_solutions_high
The components of an MVNO network

The billing system

The billing system makes each MVNO’s business model different. Find some examples below:

  • offering low prices to subscribers for roaming all over the world
  • charging a monthly fee and providing international minutes for voice services and data
  • offering specific services such as Customer Care Services in a certain language, for the niche market of migrant population
  • providing only data services using the same tariffs all over a continent
  • offering specialized mobile apps for niche markets, such as kids niche market, seniors niche market, health and safety niche market, sports niche market, etc.
  • presence on the IoT market: fleet management, POS terminals.

The roaming agreement

MVNO users can roam using either the main MNO roaming agreement, or other roaming partners.

mvno_roaming_hub.png
MVNO roaming hub

A roaming hub is a type of carrier that provides a package of roaming agreements in a single contract. Roaming hub providers have roaming agreements with many operators and they allow smaller operators to use these agreements.

The Yate solutions for MVNOs

There are two types of approach in the MVNO business in terms of voice-data infrastructure, which give a classification of MVNOs:

  • Full MVNO: its own GMSC (voice), GGSN (data), HLR-AuC, HLR/HSS (subscribers management), billing system
  • Light MVNO: its own HLR, HSS, billing.

Subscriber management: YateHSS/HLR

To begin with the common subscribers management functionality, YateHSS/HLR is single product which includes both HSS (Home Subscriber Server – 4G/LTE) and HLR-Auc (Home Location Registry – Autentification Center – 2G/GSM):

  • supports both SS7 and Diameter protocols (the so-called signaling systems necessary to manage a mobile network)
  • is a software implemented product that uses commodity hardware, which results in a lightweight, multifunctional and reliable piece of equipment.

As an HLR, YateHSS/HLR supports the SS7 MAP protocol and connects to the radio network infrastructure through the STP routers:

mvno_yhlr.png
SS7/MAP support in YateHSS/HLR

As an HSS, YateHSS/HLR provides Diameter support and delivers signalling to the RAN  (Radio Access Network) through DRA routers.

mvno_yhss
Diameter support in YateHSS/HLR

For redundancy purposes (to provide back-up for equipment failure), the YateHSS/HLR can be configured in a cluster of equal nodes:

yhss_redund_yate_high.png
YateHSS/HLR configuration in cluster
  • each subscriber profile operations are replicated in all the other YateHSS/HLRs of the network
  • many to many relationships between the core network, SS7 STP/ Diameter routers, and the YateHSS/HLR nodes eliminate single points of failure from the network

The YateHSS/HLR supports the following profiles: Wifi, EPS, IMS, CS, PS. YateHSS/HLR supports both SS7 MAP and Diameter in a single product, so MVNO subscribers can roam from a 4G network to 2G/3G networks.

mvno_yhss-hlr_profiles.png
YateHSS/HLR supported profiles

For the YateHSS/HLR specifications click the following link.

The YateHSS/HLR is an affordable and scalable solution for any operator, please check our price offer. You can also contact us for personalized offers.

Core Network Components: YateUCN

YateUCN is a cost-efficient and easy to manage core network solution for MVNOs.

  • YateUCN implements in software the functions of GMSC and GGSN using Linux OS and Dell servers
  • supports both SS7 and Diameter protocols
  • uses Yate MMI, a web-based management interface for the core network
  • Yate core network components support JSON API for configuration.

YateUCN as a GMSC (voice in GSM)

YateUCN uses the HLR to localize the MSC/VLR of the called subscriber and routes the call to the designated MSC/VLR in the MNO network.

Yate UCN as a GGSN (GPRS data trafic)

When configured as a GGSN, YateUCN establishes and maintains the IP sessions of the subscriber and routes the IP packets to the SGSN in the MNO network.

The IP packets are routed to the SGSN over the GTP-c v1 protocol.

YateUCN is an affordable and scalable solution for any operator. Please check our price offer on our website and contact us for personalized solutions.

MVNO billing system solutions

YateUCN supports billing integration with any (OSS/BSS) charging system of an MVNO.

  • the YateUCN as a GMSC supports charging operations for prepaid and postpaid billing using CAMEL phase 2
  • the YateUCN as a GGSN supports RADIUS and 3GPP extensions for postpaid billing.

Note: our Yate network components can interconnect with other network components.

YateHSS/HLR and YateUCN specifications

YateHSS/HLR

Software Specifications
RoamingSS7 MAP (2G/3G) | Diameter (4G)
InterfacesS6a/S6d (MME/SGSN to and from YateHSS/HLR) | Cx/Dx (I-CSCF/S-CSCF to and from YateHSS/HLR)
Call forwarding servicesCFU, CFB, CFNRC, CFNRY
Standard services and bearerstelephony, emergency calls, SMS
Supplementary servicesBAOC, BAIC, CW, HOLD, CLIP, CLIR, COLP, COLR, MPTY
Hardware Specifications
Dell PowerEdge R4303.5″ Chassis with up to 4 Cabled Hard Drives
ProcessorIntel Xeon E5-2630 v3 2.4GHz,20M
Memory8GB RDIMM, 2133MT/s, Dual Rank, x8 Data
Hard drives1TB 7.2K RPM SATA 6Gbps 3.5in Cabled Hard
Hard drive configurationRAID 1 for H330/H730/H730P (2 HDDs) with Cabled Chassis
Internal controllerDVD ROM SATA Internal for 4HD Chassis ReadyRails Sliding Rails With Cable
Power supply550W
Network adapterIntel Ethernet I350 DP 1Gb Server Adapter, Low Profile

YateUCN

Software Specifications
SS7 connectivity– SIGTRAN, SCTP with CRC checksum
– M2UA, M2PA, M3UA
– ITU MTP, SCCP, TCAP
– ANSI MTP, SCCP
– ITU MAP v3
– CAMEL phase 2
Voice interconnect– SIP and RTP
– ISUP using external MGCP gateway
SCCP GTT– E.212 (ANSI)
– E.214 (ITU) translation table
– E.164
MSC/VLR– ETSI MAP v3
– Supported operations:
– MSC <-> AuC messages (authentication)
– MSC <-> EIR messages (equipment identification, optional)
– VLR <-> HLR messages (location management, roaming)
– MSC <-> SMSC messages (SMS)
SGSN/MME– ETSI MAP v3
– S1AP r11
– GTP v1, GTP v2
– Supported operations:
– SGSN <-> AuC messages (authentication)
– SGSN <-> EIR messages (equipment identification, optional)
– SGSN <-> HLR messages (data mobility management, roaming)
– SGSN <-> GGSN messages (data session)
– YateENB <-> SGSN messages (LTE control and user data)
– YateBTS <-> SGSN messages (GPRS control and user data)
SIP– Supported standards (RFC3261)
– Registrar function
– B2BUA for calls
– RTP (RFC3550) with sideband DTMF (RFC2833)
– SMS and USSD over IP
SMS– Format: SMS PDU (MO and MT)
– MAP/SS7 transport (T-PDU format)
– SIP MESSAGE transport (SMS over IP, R-PDU format)
CDR– File format
– Rotation interval
– File transfer: FTP
Interfaces– C Interface (MAP, HLR <-> GMSC)
– D Interface (MAP, HLR <-> VLR)
– E Interface (MAP, MSC <-> MSC)
– F Interface (MAP, MSC <-> EIR)
– G Interface (MAP, VLR <-> VLR)
– SIP, RTP (YateBTS <-> VLR)
– S1 Interface (S1AP & GTP, YateENB <-> EPC)
– Gi Interface (IP, connects to Public Data Network)
– Gn/Gp Interface (GTP, SGSN and GGSN)
– Gr Interface (MAP, SGSN <-> HSS)
– Gc Interface (GTP or SS7/MAP, interface to HLR) (optional)
CODECS and transcoders– G.711a, G.711u
– GSM-FR 06.10
– iSAC
– iLBC
Operating systemLinux based
 
Hardware Specifications
Dell PowerEdge R4303.5″ Chassis with up to 4 Cabled Hard Drives
ProcessorIntel Xeon E5-2630 v3 2.4GHz,20M
Memory8GB RDIMM, 2133MT/s, Dual Rank, x8 Data
Hard drives1TB 7.2K RPM SATA 6Gbps 3.5in Cabled Hard
Hard drive configurationRAID 1 for H330/H730/H730P (2 HDDs) with Cabled Chassis
Internal controllerDVD ROM SATA Internal for 4HD Chassis ReadyRails Sliding Rails With Cable
Power supply550W
Network adapterIntel Ethernet I350 DP 1Gb Server Adapter, Low Profile