Python Home Subscriber Server implementing Diameter / 3GPP S6a Interfaces.
PyHSS is a Diameter Home Subscriber Server (HSS) and Subscriber Data Management solution, used for LTE (4G) Evolved Packet Core (EPC) networks, written in Python3.
This includes support for acting as:
- Standard HSS
- VoLTE HSS
- Equipment Identity Register (EIR)
- PCRF
- Generate BSF Credentials
- Gateway Mobile Location Centre
The underlying library - diameter.py provided here can be easily worked with to add support other Diameter based interfaces / protocols as required, for example to impliment a DRA or PCRF.
Basic configuration is set in the config.yaml file,
You will need to set the IP address to bind to (IPv4 or IPv6), the Diameter hostname, realm, your PLMN and transport type to use (SCTP or TCP).
Once the configuration is done you can run the HSS by running hss.py and the server will run using whichever transport (TCP/SCTP) you have selected.
The service runs in a trusting mode allowing Diameter connections from any other Diameter hosts.
- Diameter Base Protocol (Ie Device-Watchdog-Request, Capabilities-Exchange-Request)
- S6a - MME / HSS Authentication of Subscribers (Ie Authentication-Information-Request, Update-Location-Request)
- S13 - MME to EIR verification of devices (Ie ME-Identity-Check-Request)
- Cx - For P/S/I/E-CSCF Authentication and Routing (Ie User-Authentication-Request, Location-Information-Request)
- SLh - For Location of Subscriber MME from GMLC (Ie LCS-Routing-Info-Answer Request)
- Sh - For Application Servers to IMS & XCAP Data
- Zh/Zn - For generating GBA Credentials
- Gx Credit Control Answer / Re-Auth Request including installing Charging Rules on demand
The file hss.py runs a threaded Sockets based listener (SCTP or TCP) to receive Diameter requests, process them and send back Diameter responses.
Most of the heavy lifting in this is managed by the Diameter class, in diameter.py. This:
- Decodes incoming packets (Requests)(Returns AVPs as an array, called avp, and a Dict containing the packet variables (called packet_vars)
- Generates responses (Answer messages) to Requests (when provided with the AVP and packet_vars of the original Request)
- Generates Requests to send to other peers
Subscriber data (IMSI, APN Profiles & Crypto values for each subscriber) are stored in a SQL backend, (See databases for more info) which can be interfaced with a number of different ways.
The RESTful API allows for easy, safe CRUD operations on the subscriber data.
If REST isn't your jam and you instead want to interact directly with Python, database.py can be imported into your project and contains all the same hooks as the API.
Dependencies can be installed using Pip3:
pip3 install -r requirements.txt
Then after setting up the config, you can fire up the HSS itself by running:
python3 hss.py
All going well you'll have a functioning HSS at this point.
To get everything more production ready checkout Monit with PyHSS for more info.
Historically stats were collected through Redis counters and exposed via an SNMP service.
Support for Prometheus has now been added and this is the way that stats generation will be handled going forward.
More info about the legacy monitoring the system is available in SNMP Readme.
This software was written to address the limited options of free or lightweight HSS platforms out there, particularly those implementing IMS HSS functionality.
It is now deployed by several mid-tier operators, private LTE networks and lab networks worldwide.
Any contributions are welcome, just submit a PR or contact me.
You can contact me at nick (at) nickvsnetworking.com or via my blog at nickvsnetworking.com