Content for TR 23.700-92 Word version: 19.0.0
4 Analysis of gaps
5 Architectural Assumptions and Principles
6 Key Issues
7 Architectural requirements
8 Solutions
9 Deployment Guideline
10 Overall evaluation
11 Conclusions
A Relationship between eMMTel Enabler architecture and the architectures specified in other specifications
$ Change history
4 Analysis of gaps p. 10
4.1 Introduction p. 10
4.2 Analysis of OMA OneAPI framework p. 10
5 Architectural Assumptions and Principles p. 11
6 Key Issues p. 11
6.1 Key Issue #1: Application calling service based on eMMTel service p. 11
6.1.1 Description p. 11
6.2 Key Issue #2: Download data channel application to UE p. 12
6.2.1 Description p. 12
6.3 Key Issue #3:support of eMMTel call between application with IMS capability and application without IMS capability p. 13
6.3.1 Description p. 13
6.4 Key Issue #4:support of providing application layer caller information to callee p. 13
6.4.1 Description p. 13
6.5 Key Issue #5: Support of virtual number p. 14
6.5.1 Description p. 14
6.6 Key Issue #6: Multiple call control handling coordination among different Application Servers p. 17
7 Architectural requirements p. 19
7.1 General p. 19
7.2 Service configuration requirements p. 19
7.2.1 Description p. 19
7.2.2 Requirements p. 19
7.3 Service enablement requirements p. 19
7.3.1 Description p. 19
7.3.2 Requirements p. 19
8 Solutions p. 19
8.1 Solution #1: eMMTel Enabler architecture p. 19
8.1.1 Description p. 19
8.1.2 eMMTel Enabler architecture model p. 20
8.1.2.1 General p. 20
8.1.2.2 Functional entities description p. 21
8.1.2.2.1 General p. 21
8.1.2.2.2 eMMTel Enabler Server p. 21
8.1.2.2.3 eMMTel Client p. 21
8.1.2.2.4 Application Server p. 22
8.2.2.2.5 Controlling Application Server p. 22
8.1.2.2.6 Application Client p. 22
8.1.2.3 Reference points p. 22
8.1.2.3.1 General p. 22
8.1.2.3.2 eMMTel-1 (between the eMMTel client and the eMMTel Enabler server) p. 22
8.1.2.3.3 eMMTel-2 (between the eMMTel Enabler server and the Application Server) p. 22
8.1.2.3.4 eMMTel-3 (between the eMMTel Enabler server and the Controlling Application Server) p. 22
8.1.2.3.5 App-1 (between the Application Client and the Application Server) p. 22
8.2 Solution #2: Application calling service between application and DCMTSI client p. 23
8.2.1 Description p. 23
8.2.2 Procedures p. 23
8.2.3 Impacts on Existing Nodes and Functionality p. 28
8.3 Solution #3: downloading of data channel application profiles to UE p. 28
8.3.1 Description p. 28
8.3.2 Procedures p. 29
8.3.3 Impacts on Existing Nodes and Functionality p. 33
8.4 Solution #4: configuration of DC application profile p. 33
8.4.1 Description p. 33
8.4.2 Procedures p. 33
8.4.3 Impacts on Existing Nodes and Functionality p. 36
8.5 Solution #5:updating of data channel application profiles to UE p. 36
8.5.1 Description p. 36
8.5.2 Procedures p. 37
8.5.3 Impacts on Existing Nodes and Functionality p. 39
8.8 Solution #8: Multiple call control handling coordination among different Application Servers p. 45
8.8.1 Description p. 45
8.8.2 Procedures p. 45
8.8.3 Impacts on Existing Nodes and Functionality p. 46
8.9.2 Procedures p. 47
8.10 Solution #10: providing application layer caller information to callee p. 51
8.10.1 Description p. 51
8.10.2 Procedures p. 51
8.10.3 Impacts on Existing Nodes and Functionality p. 52
8.11 Solution #11: configuration of application layer caller information on MMTel Enabler server p. 53
8.11.1 Description p. 53
8.11.2 Procedures p. 53
8.11.3 Impacts on Existing Nodes and Functionality p. 54
8.12 Solution #x: MMTel Enabler layer adaptation to CAPIF p. 54
9 Deployment Guideline p. 59
9.1 General p. 59
9.2 eMMTel Enabler server deployed in PLMN operator domain p. 59
9.3 eMMTel Enabler server deployed in trusted 3rd party call service provider domain p. 60
10 Overall evaluation p. 61
10.1 General p. 61
10.2 Mapping of Solutions to Key Issues p. 62
10.3 Solution evaluation p. 62
10.3.1 Key issue #1: Application calling service based on eMMTel service p. 62
10.3.2 Key issue #2: Download data channel application to UE p. 62
10.3.3 Key issue #3: support of eMMTel call between application with IMS capability and application without IMS capability p. 63
10.3.4 Key issue #4: support of providing application layer caller information to callee p. 64
10.3.5 Key issue #5: Support of virtual number p. 64
10.3.6 Key issue #6: Multiple call control handling coordination among different Application Servers p. 64
10.3.8 Key issue #8: Supporting the multiparty service with the data channel capability p. 65
11 Conclusions p. 66
11.1 Conclusion of KI#1 p. 66
11.2 Conclusion of KI#2 p. 66
11.3 Conclusion of KI#3 p. 66
11.4 Conclusion of KI#4 p. 67
11.5 Conclusion of KI#5 p. 67
11.6 Conclusion of KI#6 p. 67
11.8 Conclusion of KI#8 p. 68
A Relationship between eMMTel Enabler architecture and the architectures specified in other specifications p. 68
A.1 General p. 68
A.2 Relationship between eMMTel Enabler architecture and architectures specified in 3GPP TS 23.228 p. 68
A.3 Relationship between eMMTel Enabler architecture and architectures specified in GSMA NG.134 p. 69
A.4 Relationship between eMMTel Enabler architecture and architectures specified in GSMA TGY.02 p. 70
A.5 Relationship between eMMTel Enabler architecture and architectures specified in GSMA TS.66 p. 71
$ Change history p. 72
