Our video tutorials are only available for viewing at our website with an internet connection (no offline option).
September 25*EMEA Timezone* Technology Primer: Orchestration
September 265G Radio Technologies and Deployments
September 27IoT in Wireless Networks: Part of Advances in LTE-RAN Series
October 3SON: Self Organizing Networks: Part of Advances in LTE-RAN Series
October 4*EMEA Timezone* Technology Primer: Cloud and Virtualization
October 4LTE-U and LAA
October 5IoT in Wireless Networks: Part of Advances in LTE-RAN Series
October 65G Services and Network Architecture
October 10*EMEA Timezone* Technology Primer: Network Functions Virtualization
October 10Technology Primer: Cloud and Virtualization
October 11*EMEA Timezone* 5G Services and Network Architecture
VIEW ALL PUBLIC COURSES
Overview of IMS
LTE SAE Evolved Packet Core (EPC) Overview
CONTACT US ABOUT BUNDLED PRICING
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.