On Building An IPX
On Building An IPX
and 5G Networks
Objective:
The goal of this project is to design and implement an IPX (IP Exchange) for interconnecting
2G, 4G, and 5G networks. This IPX will facilitate experimentation, learning, and testing, while
maintaining a decentralized network architecture. It will allow for multiple independent IPXs to
peer or operate under a regional services model, with a few centrally managed items.
A. Connectivity
For interconnecting networks, we will use a VPN overlay network connected over the internet.
After researching several options, WireGuard was selected as the VPN protocol due to its
flexibility and security. Here's why WireGuard was chosen:
A Diameter Routing Agent (DRA) will be deployed to manage Diameter-based routing for
LTE (4G) roaming. The IPX will maintain routing tables for Diameter messages to ensure proper
LTE roaming functionality.
For 5G roaming, a SEPP will be deployed, and the IPX will manage the SEPP routing tables.
SEPP ensures secure communication between roaming partners in 5G networks, maintaining
data privacy and security.
• BGP Looking Glass: A tool to view BGP routes and inspect network health.
• Active Network Map: A visual representation of the interconnected networks.
• SIP/RTP Proxy: To manage VoIP signaling and media streams.
• Certificate Authority: To issue certificates for securing communications.
• Voice Test Services: Including echo tests and calling number read-back for VoIP.
D. Voice Services
1. Voice Transport
Voice communication will be transported using VoIP (SIP for signaling and RTP for media
transport).
2. Voice Routing
We will use E.164 ENUM for voice routing. ENUM maps E.164 telephone numbers to domain
names in DNS, allowing IP-based systems to route calls using domain names instead of
traditional phone number routing.
E. Roaming
LTE Roaming will use S8HR
simplified-volte-roaming-white-paper.pdf (metaswitch.com)
Best Practices for SGW & PGW Deployment Architectures for Roaming
F. SMS Transport
SMS transport is still under discussion. Several options are being considered, including SIP
SIMPLE, MSRP, SMPP, Diameter, HTTP, and SS7. At this point, MSRP (Message Session
Relay Protocol) seems like the most suitable option for its ability to support SIP
SIMPLE/MESSAGE and RCS (Rich Communication Services).
• IPv4: The RFC 1918 private address space, specifically 10.0.0.0/8 and 172.16.0.0/12,
will be used to minimize IP overlap. Portions of this space will be allocated to each
network.
• IPv6: The private IPv6 address space fd00::/8 will be used.
• IP Allocation: Networks can request IP allocations from the IPX. These requests will be
processed on a first-come, first-served basis and must be approved by the IPX. In some
cases, the IPX may assign IP space directly.
2. PLMN
• Each network will use a unique PLMN. These must be globally unique within the IPX.
PLMN allocations will be assigned or approved by the IPX.
3. ASN
• The private ASN range (4200000000 to 4294967294) will be used for BGP peering.
ASNs will be assigned by the IPX to ensure no conflicts arise.
4. Telephone Numbers
• Telephone numbers will use the E.164 format and be managed by the IPX. The specifics
of number assignment and allocation are yet to be determined and will be discussed
further.
Conclusion:
This design aims to create a flexible, decentralized IPX network that fosters experimentation
with interconnecting 2G, 4G, and 5G networks. While the core services and routing will be
centrally managed, individual networks will maintain control over their own networks and DNS.
Future work will focus on finalizing SMS transport protocols and refining the management of
telephone number allocations.
IR.38-v3.0-1.pdf (gsma.com)
IR.34-v14.0.pdf (gsma.com)
IR.65-v31.0-1.pdf (gsma.com)
IR.67-v10.0.pdf (gsma.com)
IR.40-v8.0.pdf (gsma.com)
NG.105-v2.0.pdf (gsma.com)
NG.113-v6.0.pdf (gsma.com)
OpenIPX.NET