| |
| Figure 6.2.1-1 | MMTel Enabler architecture |
| Figure 6.2.2-1 | Option2: MMTel Enabler Server supports OMA OSE |
| Figure 8.2.2.2-1 | DC application and profile configuration |
| Table 8.2.2.3.1-1 | Information elements in DC application and profile configuration request |
| Table 8.2.2.3.1-2 | Information elements in DC application list |
| Table 8.2.2.3.2-1 | Information elements for DC application and profile configuration response |
| Table 8.2.2.3.2-2 | Information elements in DC application and profile configuration response list |
| Figure 8.2.3.2-1 | DC application and profile update |
| Table 8.2.3.3.1-1 | Information elements in DC application and profile update request |
| Table 8.2.3.3.2-1 | Information elements for DC application and profile update response |
| Table 8.2.3.3.2-2 | Information elements in DC application and profile update response list |
| Figure 8.2.4.2-1 | DC application deletion |
| Table 8.2.4.3.1-1 | Information elements in DC Application delete request |
| Table 8.2.4.3.2-1 | Information elements for DC Application delete response |
| Table 8.2.4.3.2-2 | Information elements in DC Application delete response list |
| Figure 8.2.5.2-1 | Getting DC application profile information |
| Table 8.2.5.3.1-1 | Information elements in Getting DC application profile information request |
| Table 8.2.5.3.2-1 | Information elements in Getting DC application profile information response |
| Figure 8.3.2.2-1 | MMTel Enabler Client in the UE requests the DC application profile list |
| Table 8.3.2.3.1-1 | Information elements in Get Root application request |
| Table 8.3.2.3.2-1 | Information elements for Get Root application response |
| Table 8.3.2.3.3-1 | Information elements in Get DC application profile List request |
| Table 8.3.2.3.4-1 | Information elements in Get DC application profile List response |
| Table 8.3.2.3.4-2 | Information elements in DC application profile |
| Figure 8.3.3.2.1-1 | MMTel Enabler Client request DC application profiles based on notification |
| Figure 8.3.3.2.2-1 | MMTel Enabler Server notifies the DC application profile list to UE |
| Table 8.3.3.3.1-1 | Information elements in Root application and profile update notification |
| Table 8.3.3.3.2-1 | Information elements for Root application notification |
| Table 8.3.3.3.3-1 | Information elements for MMTel Enabler Client subscribes to |
| Figure 8.4.2.2.1-1 | Establishing a Application Call with Data Channel capability between non-IMS applications and DCMTSI client |
| Figure 8.4.3.2.1-1 | Establishing a Third-Party Call with Data Channel capability |
| Table 8.4.3.3.1-1 | Third-Party Call with DC capability establishment request |
| Table 8.4.3.3.2-1 | Third-Party Call with DC capability establishment response |
| Figure 8.4.4-1 | Establishing an Application Call with Data Channel capability |
| Table 8.4.4.2.1-1 | Application Add Data Channel media to UE1 session (A2P) request |
| Table 8.4.4.2.2-1 | Application Add Data Channel media (A2P) response |
| Table 8.4.4.2.3-1 | Notify Application of DC media info (A2P) request |
| Table 8.4.4.2.4-1 | Notify Application of DC media info (A2P) response |
| Figure 8.4.5.1.1-1 | Establishing a Application Call with Data Channel capability (P2A) |
| Table 8.4.5.2.1-1 | Notify DC Application of MDC2 media (P2A) request |
| Table 8.4.5.2.2-1 | Notify DC Application of MDC2 media (P2A) response |
| Figure 8.5.2-1 | Multiple call control handling coordination among different Application Servers |
| Table 8.5.3.1-1 | Call control result notification request |
| Figure 9.2-1 | MMTel Enabler server deployed in PLMN operator domain |