Use cases #1
Description
For the "static": I am not sure whether Web pages is the best example here. In most pages nowadays, resources (images, js files, ads, etc.) are fetched from various places and unless the last-mile link for the browser is the bottleneck, the assumption of a "static" network would not apply. The simplest example would be an object download from a single server and the download duration is rather short. If it is a big file (so it takes a long time to download), then conditions will likely change.
For the "dynamic": In addition to mobility, network switching is another scenario (from wifi to LTE for example).
I also argue that the line between static and dynamic is how much the Web app/service is actually sensitive to variations in throughput (or download time). For conferencing apps, the latency budget is a few 100 ms, so if source->destination delay increases by 10s of ms, it may or may not be important. That kind of increase would not even be noticed in media streaming but would certainly be important for cloud gaming.