Our video tutorials are only available for viewing at our website with an internet connection (no offline option).
November 27*EMEA Time Zone* Technology Primer: OpenStack
November 29*EMEA Time Zone* 5G Services and Network Architecture
November 30*EMEA Time Zone* 5G Radio Technologies and Deployments
December 5IoT in Wireless Networks: Part of Advances in LTE-RAN Series
December 6*EMEA Time Zone* Voice over Wi-Fi (VoWiFi): Part of Advances in LTE-RAN Series
December 65G Services and Network Architecture
December 7*EMEA Time Zone* C-RAN: Part of Advances in LTE-RAN Series
December 75G Radio Technologies and Deployments
December 11*EMEA Time Zone* Technology Primer: DevOps
December 12*EMEA Time Zone* Technology Primer: Orchestration
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.