32ROAM OPERATOR PARTNER DESCRIPTION

VERSION: 1.1

July 2023
Revision History
Version Date Revised By Description
1.0 10/08/22 MB First Draft
1.1 11/07/23 MB Updated for partner
1.2 11/07/23 MH Revised
Contents
Revision History 2
Contents 3
32Roam Overview 4
Uses Cases 5
BYOS 5
SMS vMSISDN 5
32RoamSIM 5
CaaS 5
Technical Requirements 6
Overview 6
SIGTRAN Specifics 6
Diameter Specifics 7
SMPP 8
Definitions 9
Security & Performance 10
Security 10
Message Flows 11
BYOS flow 11
vMSISDN SMS flow 11
CaaS flow 11
32Roam Overview
A cutting-edge provider of mobile network operator services serving niche markets.

32Roam offer three main services:

1. Bring Your Own Sim (BYOS) service – allowing any commercial SIM card to register on a
3G or 4G private network.

2. Virtual SMS Phone Numbers (vMSISDN) – providing a phone number for VIP SMS
applications and working in conjunction with the 32roam secure SIM.

3. 32RoamSIM – a multi-IMSI roaming SIM providing additional security features for

consumers roaming around the globe.

32Roam are working on adding a new service in the coming months:

Cellular as a Service (CaaS) – allowing 32Roam and partners to simply and speedily deploy a
private network allowing full in-roaming capabilities for roaming partner SIM cards to allow a
network extension service in hard to reach locations.
Uses Cases

BYOS
32Roam were approached in order to provide a solution for an off-shore wind farm challenge. The
off-shore wind farm deployed a private network to provide an LTE network for remote safety and
maintenance staff. It was quickly noticed that although the staff were issued with private SIM cards
provisioned on the private network, they often only carried their commercial SIM card in the
handset. 32Roam were tasked with solving this problem and deployed their BYOS service allowing
any commercial SIM card on to the network.

SMS vMSISDN
32Roam provide this service to a number of VIP banking clients. The vMSISDN allows secure SMS
communication with a secure banking app. Because the vMSISDN is not ever on a RAN network it
is comparably more secure.

32RoamSIM
32Roam are working with a US company supplying services to the Oil and Gas sector in the US.
Executives want SIM cards that can roam on to private networks as well as provide a cost-effective
solution when roaming in other countries.

CaaS
32Roam are working in conjunction with a UK neutral host vendor to deploy private 4G networks
for enterprise customers. The solution that 32Roam developed allows a full 4G network to be
deployed using just a Small Cell and an internet connection.
Technical Requirements

Overview
This document contains detailed requirements for implementation of mobile operator network
(MNO) connections to 32Roam’s infrastructure.

BYOS

Connectivity for signalling between the mobile network and the 32Roam network will be SS7
SIGTRAN, for GSM-MAP transport. For LTE, connectivity will be DIAMETER, carrying S6a signalling
only. For SMS an SMPP connection is required towards an MNO SMSC gateway.

SMS vMSISDN

32Roam connect to the MNO via SMPP. 32Roam expect the MNO to forward messages arriving at
their SMS gateway, or SMS router to the 32Roam SMSC. Messages sent from 32Roam should also
be terminated appropriately.

32RoamSIM

32Roam require several connections to each “IMSI/MSISDN” host sponsor network:

• 32Roam STP firewall towards MNO STP
• 32Roam DRA firewall towards MNO DRA for s6a and Gy for charging
• Home routing set up towards 32Roam SMS router with additional SMPP connection
• GMSC for voice routing and security

Currently 32Roam does not host a GGSN/PGW but would like to enable this option later, requiring
a dedicated APN or APN range in the future in addition to GTP-C and GTP-U connectivity to the IPX.

CaaS

An IP tunnel over GRE (GTP and GTPv2) is established from the 32Roam SGSN and SGW. BGP is
desirable in order to maintain routing tables and where possible; access to the MNO DNS server
that can be used for APN resolution for attaching subscribers.

For 3G, where voice is required, a SIP/RTP path is established from the 32Roam PBX towards the
MNO MGW or SBC. This is not required for 4G.

SIGTRAN Specifics
Connectivity between the server and the MNO will be SS7 SIGTRAN for GSM-MAP and CAMEL.

The MNO will provide public Global Titles (GT) and Point Codes dedicated for exclusive use of the
32Roam service over the supplied SS7 SIGTRAN signalling network.
The BYOS service prefers that two GTs are provisioned:
• one for MSC/VLR/SMSC
• another for HLR/GSMSCF

For 32Roam SIM, at least four GTs are provisioned:

• one for HLR
• another for SMSC
• another for GMSC
• another for GSMSCF

For redundancy (if available), it is requested that two VPN connections with routing to one or more
STPs is available to allow for fail over. Currently multi-homing is not supported on SCTP.

Signalling Operations

The possible signalling operations required are:

• Anytime Interrogation
• Anytime Subscriber Interrogation
• Cancel Location
• Insert Subscriber Data
• Mobile Originated Short Message
• Mobile Terminated Short Message
• Mobile Originated Forward SMS
• Mobile Terminated Forward SMS
• Provide Subscriber Info
• Provide Roaming Number
• Purge MS
• Send Authentication Information
• Send IMSI
• Send Routing Info
• Send Routing Info For SM
• Update Location

Routing

Routing from 32Roam is required to be configured to ‘route on GT’ with the destination being
either a network node GT (E164), MGT (E214) or MSISDN (E164).

The following source SSNs must be allowed from 32Roam: 6, 7, 8, 145, 147, 149. The following
destination SSNs must be allowed from 32Roam: 6, 7, 8, 148, 252.

Diameter Specifics
32Roam requires a dedicated hostname for exclusive use of MNO over the supplied DIAMETER
signalling network. It is 32Roam’s preference that a realm specific to 32Roam is created and used
for inbound communications to 32Roam’s network. This helps to route traffic within the 32Roam
extension as to not confuse destinations.

For redundancy (if available), it is requested that parallel VPN connections are requested to allow
reliable routing to one or two DRA nodes.

Signalling Operations

The required signalling operations required are:

• AIR/AIA
• CCR-[I/U/T]/CCA-[I/U/T]
• CLR/CLA
• IDR/IDA
• NOR/NOA
• PUR/PUA
• ULR/ULA

For BYOS only:

• When the DIAMETER client acts as an HSS, it should not be configured to route inbound
subscriber authentication and attachment requests – it is a client role within the network
only and should not be added to any active HSS pools within the network.
• The system will send a signalling to an MME which needs to be routed by the DRA – an
example destination MME is MMEXYZ.epc.3gppnetwork.org. In the case of MME
operations, the system will send signalling from the MME to a destination HSS routed by
destination realm. The DRA should route traffic accordingly.

SMPP
32Roam connects to the MNO SMSC gateway with a configured system ID and password. There
will be heartbeats as per SMPP specification, in addition to two message types;

• SM_SUBMIT
• SM_DELIVER

In the case of sending an SMS from 32Roam towards a third party network subscriber, 32Roam
prefer to set DLR parameters to notify upon delivery towards the network and receipt of the SMS
by the end user handset.
Definitions
In this Document the following words have the following meanings:

● “Global Title” (GT) means an address used in the protocol for routing signalling
messages on telecommunications networks
● “GSM” means Global System for Mobile Communications
● “HLR” means Home Location Register
● “IP” refers to the communications protocol on the Internet Layer of the TCP/IP Model
● “ITP” means IP Transfer Point used by telecom providers either as an SS7 Signalling
Gateway or as an “STP/SCP”
● “MAP” or “GSM-MAP” means Mobile Application part, the SS& protocol which provides
the application layer in mobile telecommunications networks
● “MSC/VLR” means Mobile Switching Centre/Visitor Location Register
● “MSU” means Message Signalling Unit and as further defined in ITU/SS7 signalling
standards
● “SIGTRAN” means Signalling Transport, the name given to SS7 over IP
● “SMSC” means Short Message Service Centre
● “STP” means Signal Transfer Point which relays SS7 messages to other STPs
● “VPN” means virtual private network.
• “HSS” means the LTE Home Subscriber Server
• “DIAMETER” refers to the signalling protocol used for authentication and signalling
messages
• “S6” is a suite of protocols for network elements in an LTE core network
• “REALM” refers to a domain name used for traffic routing
• “HOSTNAME” is name (typically) an FQDN identifying a host
• “HOST” is a physical or virtual server
• “FQDN” means Fully Qualified Domain Name and forms e.g., X.Y.Z
• “SCTP” is a transport protocol running on IP with guaranteed payload delivery typically
used to carry other telecommunications protocols
• “IP” refers to the communications protocol on the Internet Layer of the TCP/IP Model
• “VPN” means virtual private network.
Security & Performance
Security
Security is the highest priority and concern within the solution. There are multiple levels of security
in place within the solution to protect from abuse.

IP level security

The solution DIAMETER agent includes an inbound/outbound firewall which only allows traffic to
flow (SCTP) out to a specific port and IP address matching the DRA. All inbound requests are denied
since traffic is initiated by the solution agent. The solution is also installed within a protected
private network which is not accessible from outside or public users.

Signalling layer

The messaging agent (DIAMETER agent or ASP agent) for DIAMETER and SIGTRAN respectively, can
only send commands for very specific interfaces and very specific messages. For DIAMETER, only
s6a is supported. No other commands are supported and should not be used.

Intelligence layer

The solution includes an intelligence middleware solution that instructs the DIAMETER agent to
send IDR messages and the ASP agent to send SS7 MAP messages. It includes a number of
safeguards for protection of the MNO.
Message Flows
BYOS flow
The 3G message flow for the Bring Your Own SIM service is as follows. For LTE, the messages are
identical except they are from MME à HSS and are the DIAMETER equivalents:

vMSISDN SMS flow

Sending an SMS from the 32Roam platform as a vMSISDN relies on the MNO SMSC to handle
delivery of the SMS via interconnects (i.e. AA19 or SRI-SM/MO-FORWARD):

32Roam SMSC MNO SMSC Interconnect Handset

SUBMIT_SM à MT_FORWARD à DELIVER_SM à

Reception of an SMS to a 32Roam vMSISDN requires the MNO to forward inbound traffic to
32Roam’s SMSC:

32Roam SMSC MNO SMSC Interconnect Sender

ß DELIVER_SM ß MO_FORWARD ß SUBMIT_SM

CaaS flow
The 3G message flow for the Cellular as a Service is as follows. For LTE, the flow is identical except
they are from MME à HSS and are the DIAMETER equivalents: