| Figure 4.2.1-1 | MBMS Client - Application and Network reference Points an APIs |
| Listing 4.2.1-1 | Example usage of the Android APIs to support accessing MBMS services through Mission Critical functions |
| Listing 4.2.1-2 | Reception of data from an MBMS bearer using Android APIs |
| Listing 4.2.1-3 | Multicast packet data access using Android APIs |
| Figure 4.2.2-1 | Media Session Handler- Application and Network reference Points an APIs |
| Figure 4.2.3-1 | Media Playback in 5G Media Downlink Streaming Architecture |
| Figure 4.2.5-1 | Generic on-network functional model for SEAL (see TS 23.434, Figure 6.2-1) |
| Figure 5.2.1-1 | Media Service Enablers Framework |
| Table 5.2.3-1 | Summary of MSE features for various components of Figure 5.2.3-1 |
| Figure 5.2.4-1 | Media Session Handler as defined in26.501 |
| Figure 5.2.4-2 | Media Session Handler as MSE SDK abstraction, MSE SDK instantiations, and MSE service |
| Figure 5.3.2-1 | Third-party application on top of 5G System - 5G System Architecture |
| Figure 5.3.2-2 | Third-party application on top of 5G System - Interfaces |
| Figure 5.3.2-3 | Addition of MSE to 5G-based media delivery |
| Figure 5.3.5-1 | Test Framework for MSE Client Implementation |
| Table 5.3.7.1-1 | Mapping of MBMS Client to MSE concept |
| Table 5.3.7.2-1 | Mapping of DASH Player to MSE concept |
| Figure 6.2.2-1 | Media Service Enablers in 5G Systems |
| Figure 6.4-1 | MSE Reference Implementation |
| Figure 6.4-2 | Test/Conformance Framework for MSE Client Implementation |