Our video tutorials are only available for viewing at our website with an internet connection (no offline option).
Public Course Schedule
January 29Technology Primer: Artificial Intelligence (AI)
January 30Technology Primer: Blockchains
February 1Technology Primer: Containers and Microservices in Telecom
February 4Technology Primer: ONAP
February 6Technology Primer: LTE-M and NB-IoT
February 7Technology Primer: Overview of CBRS
February 13Technology Primer: OpenStack
February 14Technology Primer: Orchestration
February 15Technology Primer: Network Functions Virtualization
February 21Technology Primer: Artificial Intelligence (AI)
February 22Technology Primer: Blockchains
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.