Content for TR 23.700-87 Word version: 18.0.0
6 Solutions p. 15
6.0 Mapping of Solutions to Key Issues p. 15
6.1 Solution #1: Data Channel Usage for A2P/P2A Scenario p. 15
6.1.1 Description p. 15
6.1.2 Procedures p. 16
6.1.3 Impacts on existing nodes and functionality p. 18
6.2 Solution #2: Solution of Data Channel usage in IMS network p. 18
6.2.1 Description p. 18
6.2.2 Procedures p. 20
6.2.3 Impacts on existing nodes and functionality p. 20
6.3 Solution #3: Data Channel Architecture p. 21
6.3.1 Description p. 21
6.3.1.1 Architecture Description p. 21
6.3.1.2 Network Function Description p. 22
6.3.1.2.1 Control Function of Data Channel Server (DCS-C) p. 22
6.3.1.2.2 Media Function of Data Channel Server (DCS-M) p. 22
6.3.1.3 Network Function Service Description p. 22
6.3.1.4 Lawful Intercept of IMS Data Channel p. 24
6.3.1.5 Interactions with IMS Supplementary Services p. 24
6.3.2 Procedures p. 24
6.3.2.1 NF service registration p. 24
6.3.2.2 Data channel SDP media description model p. 24
6.3.2.3 Establishing bootstrap data channels p. 25
6.3.2.3.1 UE-initiated bootstrap data channel establishment p. 25
6.3.2.3.2 Network-initiated bootstrap data channel establishment p. 26
6.3.2.4 Establishing application data channels p. 26
6.3.2.4.1 Establishing application data channel between UEs p. 26
6.3.2.4.2 Establishing application data channel between the UE and the network p. 27
6.3.2.5 Terminating data channels p. 28
6.3.2.6 Exception handling of data channels p. 28
6.3.3 Impacts on existing nodes and functionality p. 28
6.4 Solution #4: IMS Data Channel Capabilities Discovery p. 29
6.4.1 Description p. 29
6.4.1.1 Network discovers the data channel capability of the UE p. 29
6.4.1.1.1 Home network discovers the data channel capability of its UE p. 29
6.4.1.1.2 Remote network discovers the data channel capability of the local UE p. 30
6.4.1.2 UE discovers the data channel capability of the network p. 30
6.4.1.2.1 UE discovers the data channel capability of its home network p. 30
6.4.1.2.2 Local UE discovers the data channel capability of the remote end p. 30
6.4.1.3 Avoid impact on IMS basic audio/video call p. 30
6.4.2 Procedures p. 30
6.4.3 Impacts on existing nodes and functionality p. 31
6.5 Solution #5: Negotiation and report of IMS Data Channel capabilities p. 31
6.5.1 Description p. 31
6.5.1.1 General p. 31
6.5.1.2 IMS Data Channel capability discovery and negotiation p. 32
6.5.1.3 Option 1 of report of IMS Data Channel capabilities to Data Channel Server: via IMS registration procedure p. 32
6.5.1.4 Option 2 of report of IMS Data Channel capabilities to Data Channel Server: when the UE requests Data Channel applications p. 32
6.5.1.5 Option 3 of report of IMS Data Channel capabilities to Data Channel Server: when the UE establishment the bootstrap data channel p. 32
6.5.1.6 IMS Data Channel capabilities p. 33
6.5.2 Procedures p. 33
6.5.3 Impacts on existing nodes and functionality p. 34
6.6 Solution #6: Enhancement to support Data Channel usage in IMS network p. 35
6.6.1 Description p. 35
6.6.2 Network Architecture and Functionalities of IMS Data Channel p. 35
6.6.3 Procedure p. 36
6.6.3.1 UE Initiated Bootstrap Data Channel Establishment p. 37
6.6.3.2 UE Initiated Application Data Channel Establishment p. 39
6.6.4 Impacts on Existing Functions and Services p. 40
6.7 Solution #7: Reference architecture to support Data Channel usage in IMS p. 41
6.7.1 Description p. 41
6.7.2 Procedures p. 43
6.7.2.1 UE Initiated Bootstrap Data Channel establishment p. 43
6.7.2.2 Application Data Channel establishment between UEs (P2P) p. 45
6.7.2.3 Application Data Channel establishment between UE and DCS (P2A) p. 46
6.7.3 Impacts on existing nodes and functionality p. 47
6.8 Solution #8: AR Telephony Communication Based on Data Channel p. 47
6.8.1 Description p. 47
6.8.2 Procedures p. 48
6.8.3 Impacts on existing nodes and functionality p. 49
6.9 Solution #9: Supporting AR communication p. 49
6.9.1 Description p. 49
6.9.2 Procedures p. 51
6.9.3 Impacts on existing nodes and functionality p. 55
6.10 Solution #10: Support of Third Party specific User Identities in IMS re-using the Ms reference point and STIR/SHAKEN p. 55
6.10.1 Description p. 55
6.10.2 Procedures p. 57
6.10.3 Impacts on existing nodes and functionality p. 57
6.11 Solution #11: Verification of calling party when using third party specific identity p. 58
6.11.1 Description p. 58
6.11.2 Procedures p. 59
6.11.3 Impacts on existing nodes and functionality p. 60
6.12 Solution #12: Solution of SHAKEN based third-party specific user identities p. 60
6.12.1 Description p. 60
6.12.2 Procedures p. 61
6.12.3 Impacts on Existing Nodes and Functionality p. 62
6.13 Solution #13: third party specific user identities p. 63
6.13.1 Description p. 63
6.13.1.1 Assumptions p. 63
6.13.1.2 Definitions p. 63
6.13.1.3 Architecture p. 64
6.13.1.4 Subscription model and data processing principle p. 65
6.13.2 Procedures p. 65
6.13.2.1 third party ID Access via SIP Trunk p. 66
6.13.2.2 third party ID Access via Single SIP Registration p. 68
6.13.2.3 SIP Trunk third party User as the called party p. 70
6.13.2.4 Single SIP Registration third party User as the called party p. 71
6.13.2.5 Terminating IMS network verifying third party specific identities and name card p. 71
6.13.3 Impacts on Existing Nodes and Functionality p. 73
6.14 Solution #14: IMS MRF Discovery and Selection using 5G-SBA NRF p. 74
6.14.1 Description p. 74
6.14.1.1 Introduction p. 74
6.14.1.2 Summary p. 74
6.14.1.3 Networks using SCP p. 75
6.14.1.4 Distributed MRFC/MRFP p. 75
6.14.2 Procedures p. 76
6.14.3 Impacts on Existing Nodes and Functionality p. 77
6.15 Solution #15: Applying service based principles to IMS media control interfaces for supporting new capbilities Efficiently p. 78
6.15.1 Description p. 78
6.15.1.1 Scope p. 78
6.15.1.2 Definitions p. 78
6.15.1.3 Principle p. 78
6.15.1.4 Architecture p. 79
6.15.1.5 Co-existence of 5G service based and legacy IMS media control interfaces p. 79
6.15.2 Procedures p. 79
6.15.2.1 Registration of media plane NF p. 80
6.15.2.2 Discovery of media plane NF p. 80
6.15.2.3 Coordination between new media capabilities and existing media capabilities p. 80
6.15.3 Impacts on existing nodes and functionality p. 82
6.16 Solution #16: Solution for IMS Media Support for DC Server p. 83
6.16.1 Description p. 83
6.16.2 Procedures p. 84
6.16.2.1 IMS Session Procedures p. 84
6.16.2.2 IMS AS - DC Server Interaction for Media control p. 86
6.16.3 Impacts on existing nodes and functionality p. 86
6.17 Solution #17: Service registration, discovery and selection for distributed DC server p. 87
6.17.1 Description p. 87
6.17.2 DCSF Registration and Discovery p. 87
6.17.3 DCMF Registration and Discovery p. 88
6.17.4 Impacts on existing nodes and functionality p. 89
6.18 Solution #18: Negotiation the data channel application(s) used in the call p. 89
6.18.1 Description p. 89
6.18.1.1 General p. 89
6.18.2 Procedures p. 90
6.18.3 Impacts on Existing Nodes and Functionality p. 90
6.19 Solution #19: Light weight solution of third party specific ID using existing mechanisms p. 91
6.19.1 Description p. 91
6.19.2 Procedures p. 91
6.19.3 Impacts on existing nodes and functionality p. 91
6.20 Solution #20: Merged solution to support Data Channel usage in IMS network p. 92
6.20.1 Description p. 92
6.20.1.1 General p. 92
6.20.1.2 Architecture p. 92
6.20.2 Procedures p. 96
6.20.2.1 NF service registration and discovery p. 96
6.20.2.2 Session event notification p. 97
6.20.2.3 UE initiated bootstrap data channel establishment p. 97
6.20.2.4 UE initiated P2P application data channel establishment p. 101
6.20.2.5 UE initiated P2A/A2P application data channel establishment p. 103
6.20.2.6 Replacing Root-URL in HTTP GET request from the UE p. 104
6.20.3 Network Function Services p. 104
6.21 Solution #21: Interworking between a DCMTSI client in terminal and an MTSI client in terminal p. 106
6.21.1 Description p. 106
6.21.2 Procedures p. 107
6.21.3 Impacts on Existing Nodes and Functionality p. 110
6.22 Solution #22: Application Data Channel establishment based on application ID p. 110
6.22.1 Description p. 110
6.22.1.1 Application Data Channel route selection p. 110
6.22.1.2 Trigger of DC application downloading in the peer UE p. 111
6.22.1.3 Usage of DC Application ID p. 111
6.22.2 Procedures p. 112
6.22.3 Impacts on Existing Nodes and Functionality p. 113
6.23 Solution #23: UE capabilities detection for IMS DC applications p. 113
6.23.1 Description p. 113
6.23.2 Procedures p. 115
