Our video tutorials are only available for viewing at our website with an internet connection (no offline option).
Public Course Schedule
April 195G Services and Network Architecture
April 24LTE RF Optimization: Part 3 - Mobility and Inter-RAT
May 7Technology Primer: LTE-M and NB-IoT
May 85G Services and Network Architecture
May 10Technology Primer: Software-Defined Networking (SDN)
May 11Technology Primer: Orchestration
May 14OpenStack Workshop for SDN and NFV
May 295G Radio Technologies and Deployments
May 305G Services and Network Architecture
June 5Technology Primer: Cloud and Virtualization
June 6Technology Primer: OpenStack
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.