IPLOOK MVNO solution

MVNO Proposal by IPLOOK
The information in this document is proprietary to IPLOOK Co, Limited. The information shall not be used, copied, reproduced or
disclosed in whole or part without the written consent of IPLOOK Office of Technology Development.
MVNO solution for XXX
V 1.0
IPLOOK Network Technologies 2018-1-23

Contents
1 Background...................................................................................................................................4
2 Technical Requirements............................................................................................................ 4
3 General Solution......................................................................................................................... 5
3.1 Network Topology...........................................................................................................5
3.2 Functions of the network element............................................................................. 5
3.2.1 Network Dimension............................................................................................ 5
3.2.2 Network Features...................................................................................................7
4 The Services Model....................................................................................................................7
4.1 Technical configuration of Local services.................................................................7
4.1.1 Voice Service......................................................................................................... 7
4.1.2 SMS service............................................................................................................8
4.1.3 Data Service...........................................................................................................9
4.2 Technical Configuration of Roaming Services...................................................... 10
4.2.1 Roaming Voice Service.....................................................................................10
4.2.2 Roaming SMS Service.......................................................................................11
4.2.3 Roaming Data Service...................................................................................... 12
5 Necessary Resources of MNO.............................................................................................. 12
6 Redundancy and Network Expansion.................................................................................13
6.1 Redundancy.................................................................................................................... 13
6.1.1 2/3G domain....................................................................................................... 13
6.1.2 4G domain........................................................................................................... 13

6.2 Network expansion.......................................................................................................14
6.2.1 2G/3G domain.................................................................................................... 14
6.2.2 4G domain........................................................................................................... 15
7 Interface and Network Planning.......................................................................................... 15
8 Scope of Work........................................................................................................................... 16
9 Quotation....................................................................................................................................16

1 Background
With the increasing mobile connections, the efficiency use of limited
frequency band becomes one primary assignment for operators.
Correspondingly, new value added services are constantly emerging
widening the range and types of service offerings and pricing plans. The
introduction of Mobile Virtual Network Operator (MVNO) is seen as a
natural progression towards enhancing free market principles and
contributing to the efficient use of existing telecommunication
infrastructure.
IPLOOK is due to provide complex and diversified MVNO solution to
XXX.
2 Technical Requirements
1) Type 3 full MVNO model
2) Support 2G, 3G & 4G local and roaming voice, SMS, VMS, USSD and
data services.
3) 2/3G support prepaid and postpaid billing. 4G data service supports
prepaid.
4) MVNO will order/produce SIM by themselves after XXX allocates IMSI
block.
5) 100k subscribers for the first phase, and will expand to 1 million in the
future.
6) The long term user penetration rate is about 40%, so the overall
capacity of throughput is estimated as:
First phase: 100k/user X 100K X 40%=4Gbps
Final network model: 100k/user X 1M X 40%=40Gbps

3 General Solution
3.1 Network Topology
For the service requirements above, IPLOOK designed the following
scheme. GMSC, SMSC, VMS, SCP, PGW/GGSN, HSS/HLR, PCRF, BOSS, STP,
DRA will be deployed. All the interfaces between MNO and MVNO are
based on 3GPP standard. All the NEs are deployed in redundancy which
makes a high reliability. The business model of MVNO is whole MVNO
with CRM, billing and own brand for customers.
3.2 Functions of the network element
3.2.1 Network Dimension
Product
Name
NE Hardware
Platform
Qual
ity
License Capacity
R4S MSS VMSC/VLR/GMSC
Carrier class server
or VM machine
CPU: 2.0GHz+
RAM: 3G
Hard Disk: 100G+
2 GMSC : 2000 ERL
HLR/AUC HLR/AUC
or VM machine
2
Subs: 100K

CPU: 2.0GHz+
RAM: 3G
Hard Disk: 100G+
OCS SCP
or VM machine
CPU: 2.0GHz+
RAM: 3G
Hard Disk: 100G+
2
Subs: 100K
SMSC SMSC
or VM machine
CPU: 2.0GHz+
RAM: 2G
Hard Disk: 100G+
2
VMS SMSC
CPU: 2.0GHz+
RAM: 3G
Hard Disk: 200G+
2
Subs: 100K
OMC OMC
CPU: 2.0GHz+
RAM: 3G
Hard Disk: 300G+
Operation and
Maintenance Center.
Will collect all CDRs ,
CSTA and other
statistics.
PGW PGW/GGSN
CPU: 2*10 cores
RAM: 16G
Hard Disk: 500G*2
NIC: 1G*4 10G*1
2
BOSS
APP PC SERVER
CPU: 2*10 cores
RAM: 128G
Hard Disk: 300G
2
Subs: 100K
ORACAL PC SERVER
CPU: 1*10 cores
RAM: 64G
Hard Disk: 100G
2
Subs: 100K
ORACLE 11G
oracle 11g standard
edition
1
Subs: 100K
STORAGE Hard Disk: 20T 1 Subs: 100K

3.2.2 Network Features
See Annex Ⅰ
4 The Services Model
4.1 Technical configuration of Local services
4.1.1 Voice Service
When UE from XXX initiate a voice call request, a voice tunnel is provided
by MNO’s SBC to communicate with MVNO’s GMSC. If the called is
under the coverage of local MNO network or is PSTN users, the voice
will be routed back to MNO’s SBC. Then, the voice can be transmitted
between callee and caller. If the caller roams to other operators, then the
voice will be routed to GMSC of other operators by MVNO’s GMSC.

When the caller is local user, international carrier user or the user from
other operators in Turkey, the voice will begin through MNO’s SBC and
switch in MVNO’s GMSC. The MVNO customer can receive the phone
call in this way.
4.1.2 SMS service
The opening of short message service requires us to deploy the SMSC
(Short Message Service Center) and SMGW (Short Message Gateway)
network elements. The originator sends the short message to SMC which
will deliver it to terminator’s SMC, and the terminator gets the message
from its own SMC.

4.1.3 Data Service
When UE is located in 4G coverage, UE will attach on 4G core network
automatically. MME selects SGW and PGW based on TAI FQDN and APN
FQDN. User traffic will be routed to MVNO’s PGW.
When UE goes out of E-UTRAN coverage areas, then UE can fall back to
UTRAN through S3 and S4 interfaces. Data path hand over to SGSN and
GGSN. In this case PGW and GGSN are integrated in one box by IPLOOK
to insure the consistency of user traffic.

4.2 Technical Configuration of Roaming Services
4.2.1 Roaming Voice Service
When UE travels to MVNO partner’s network and initiates a phone call,
the VLR will directly route the voice request to GMSC of called party. So
the voice service can be provided with visited operator’s network.
However, the prepaid service is not supported in this case.
When UE is called by others, the calling party will find MNO’s SBC
through subscriber’s registration information, and the voice packages
are routed back to MVNO’s GMSC which transmit these packages to
GMSC of visited place.

4.2.2 Roaming SMS Service
When UE initiates SMS request while roaming to partner’s network, the
VLR of visited place will transmit the packages to MNO’s SBC. Then, SBC
forward the packages to MVNO’s GSMC and SMSC. The SMSC is
responsible for finding the short message center of the other party, and
the sender's message center sends the message to the receiver. The SMS
path of MT is just the same with MO.

4.2.3 Roaming Data Service
The SGW of visited place connects to MVNO’s PGW through S8
interface. When UE falls back to UMRAN, the SGSN can connect to SGSN
through Gn interface. So, when UE travels outside, data services can still
be provided. In this case, the S6a interface on HSS should be opened to
the visited PLMN MME for the roamer UE.
5 Necessary Resources of MNO
1) Services required
 2G, 3G &4G Local Voice, SMS & Data
 2G, 3G &4G Roaming Voice, SMS & Data
2) Network Element/routing
 RAN, GMSC, SGSN, SMS via SMPP
 Existing MNO interconnect with PSTN
 MVNO apply MVNO license, MSISDN and other relevant resources
(e.g. ISPC, PC, etc.)

6 Redundancy and Network
Expansion
6.1 Redundancy
6.1.1 2/3G domain
All 3G Core Network nodes (MSC/GMSC, SSF, VLR，HLR/AUC) and Value
Added System (SMSC, SCF) support hot-hot redundancy and
load-sharing. VMS supports active-standby redundancy. The typical
deployment of the 3G system can be as following:
*All servers/machines can be deployed in one office or divided into 2 groups and deployed in 2 offices
6.1.2 4G domain
Two suits of xGW should be deployed at the same time and they can
work as load sharing or active and standby model, which depends on the
configuration of GW selection strategy on MME.
If xGW A is crashed, MME will detach the event and changed the weight
during the GW selection procedure. After the xGW is restored, MME will
adopt the weight again.(MME can choose active GW automatically)

6.2 Network expansion
6.2.1 2G/3G domain
Phase Capacity Hardware
layout
Hardware
details
Note
Ⅰ
VMSC/VLR/GM
SC
1M
2 Servers
CPU:
2.0GHz+
RAM: 3G
Hard Disk:
100G+
The equipment
in GW pool are
deployed in
redundancy by
load-sharing
mode
SMSC 1M
SCP 200K 2 Servers
VMS 200K 2 Servers
HLR/AUC 100K 2 Servers
Ⅱ
SCP 1M
Add servers
or database
to support
1MVMS 1M
HLR/AUC 1M

6.2.2 4G domain
Phase Capacity Hardware
layout
Hardware
details
Note
Ⅰ
Subscribers 100k
2 Servers
CPU: 2*10
cores
RAM: 16G
Hard Disk:
500G*2
NIC: 1G*4
10G*1
The equipment
in GW pool are
deployed in
redundancy by
load-sharing
mode
Throughput 4Gbps
Ⅱ
Subscribers 1M
Add 9
servers in
GW pool
Throughput 40Gbps
7 Interface and Network Planning
The interface and nodes are showed in following diagram.
The right part is providing the MVNO functions. It provides MAP/Camel,
SIP/ISUP interfaces for voice call and short message and voice mail
service. The network structure also provides roaming inbound and
roaming outbound service for mobile subscribers.

8 Scope of Work
See Annex Ⅱ
9 Quotation
See Annex Ⅲ

IPLOOK MVNO solution

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to IPLOOK MVNO solution

Similar to IPLOOK MVNO solution (20)

More from IPLOOK Networks

More from IPLOOK Networks (20)

Recently uploaded

Recently uploaded (20)

IPLOOK MVNO solution