Our video tutorials are only available for viewing at our website with an internet connection (no offline option).
Public Course Schedule
June 21Technology Primer: Orchestration
June 21Technology Primer: 5G Radio Technologies and Deployments
June 22Technology Primer: DevOps
June 25Technology Primer: Licensed Assisted Access (LAA)
June 25Technology Primer: 5G Services and Network Architecture
June 26Technology Primer: LTE-M and NB-IoT
June 26Technology Primer: Artificial Intelligence (AI)
June 28Technology Primer: Cloud and Open RAN Architectures
July 2Technology Primer: Network Functions Virtualization
July 10Technology Primer: LTE-M and NB-IoT
July 11Technology Primer: 5G Services and Network Architecture
View full schedule
I would switch the Subscribers limitation with the Transactions one in the order. My logic is that based on my implementation and benchmarking experience, the HSS is in effect just a small layer of functionality which interfaces through Diameter to a back-end DBMS. I would even say that more than 90% of the resources are then spent in the DBMS then in the HSS delta. Then the capacity is in effect that of the DBMS, which rarely have a problem with the amounts of data required here (tens/hundreds millions of rows) vs. the DB transactions performance.
Then I would even eliminate entirely the Bearers from the list. Bearers are not saved or updated in the HSS, while also the subscriber profile data is supposed to be cached in the MME/PCRF/S-CSCF/etc, not pulled on bearer modifications, rather pushed down on updates.