Our video tutorials are only available for viewing at our website with an internet connection (no offline option).
Public Course Schedule
February 27LTE RF Optimization: Part 1 - Coverage and Accessibility
March 5*EMEA Time Zone* Technology Primer: Licensed Assisted Access (LAA)
March 5OpenStack Heat Workshop
March 12*EMEA Time Zone* Technology Primer: Orchestration
March 19NFV Application Planning and Design Workshop
March 21Advanced LPWA for IoT
March 27RF Design Workshop: Part 2 - VoLTE and Small Cells
April 35G Services and Network Architecture
April 3LTE RF Optimization: Part 2 - Downlink and Uplink Throughput
April 45G Radio Technologies and Deployments
April 5Technology Primer: LTE-M and NB-IoT
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.