Content for TR 23.700-77 Word version: 19.0.0
5 Key Issues p. 14
5.1 Key Issue #1: Extensible IMS mechanism supporting IMS events in the context of DC communication p. 14
5.1.1 Description p. 14
5.2 Key issue #2: Impact on IMS architecture, interfaces and procedures to support IMS capability exposure in the context of IMS data channel session p. 14
5.2.1 Description p. 14
5.3 Key Issue #3: Data channel interworking with MTSI UE p. 14
5.3.1 Description p. 14
5.4 Key Issue #4: Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions p. 15
5.4.1 Description p. 15
5.5 Key Issue #5: Handling of PS data off exemption for services over IMS DC p. 15
5.5.1 Description p. 15
5.6 Key Issue #6: Support of Standalone IMS Data Channel Sessions p. 15
5.6.1 Description p. 15
5.7 Key issue #7: Support multiplexing multiple DC applications over single SCTP connection p. 16
5.7.1 Description p. 16
5.8 Key Issue #8: Support of IMS Avatar Communication p. 16
5.8.1 Description p. 16
6 Solutions p. 17
6.0 Mapping of Solutions to Key Issues p. 17
6.1 Solution #1: Architectural Enhancements in Support of exposure of IMS events using HSS Subscription p. 17
6.1.1 Description p. 17
6.1.2 Procedures p. 20
6.1.2.1 DCSF Subscription to IMS Events Via HSS p. 20
6.1.2.2 Subscription to IMS events via NEF p. 21
6.1.2.3 Additional Services and Operations in Support of IMS Event subscription p. 22
6.1.3 Impacts on existing services, entities and interfaces p. 23
6.2 Solution #2: Event subscription and notification enhancements for DC applications p. 23
6.2.1 Description p. 23
6.2.1.1 General p. 23
6.2.1.2 Report of registration events p. 24
6.2.1.3 Determination the interaction mode between DC application server and IMS network p. 25
6.2.1.4 Discovery and selection of NFs p. 25
6.2.1.5 Definition of group of IMS subscriber p. 25
6.2.1.6 Subscription and notification of IMS events p. 25
6.2.2 Services p. 25
6.2.3 Procedures p. 28
6.2.4 Impacts on Existing Nodes and Functionality p. 29
6.3 Solution #3: Subscription and Notification for DC Events p. 29
6.3.1 Description p. 29
6.3.1.1 Nimsas_SessionEventControl_Subscribe service operation p. 30
6.3.1.2 Nimsas_SessionEventControl_Notify service operation p. 30
6.3.1.3 Nimsas_SessionEventControl_Unsubscribe service operation p. 30
6.3.2 Procedures p. 31
6.3.2.1 Subscription procedure for a specific IMS Subscriber p. 31
6.3.2.2 Subscription procedure for a list of IMS Subscribers p. 31
6.3.3 Impacts on Existing Nodes and Functionality p. 32
6.4 Solution #4: Event subscription and notification of IMS DC for related subscribers p. 32
6.4.1 Description p. 32
6.4.2 Procedures p. 33
6.4.3 Impacts on Existing Nodes and Functionality p. 34
6.5 Solution #5: IMS event subscription mechanism p. 34
6.5.1 Description p. 34
6.5.2 Procedures p. 35
6.5.2.1 Event subscription mechanism of DCSF p. 35
6.5.2.2 Event subscription mechanism of IMS AS p. 36
6.5.3 Impacts on Existing Nodes and Functionality p. 39
6.6 Solution #6: IMS capability exposure architecture p. 40
6.6.1 Description p. 40
6.6.1.1 Architecture Description p. 40
6.6.1.2 Network Function Description p. 41
6.6.1.3 Network Function Service Description p. 42
6.6.2 Procedures p. 43
6.6.2.1 General Description p. 43
6.6.2.2 Establishing an IMS session with data channel media p. 44
6.6.2.3 Terminating an IMS session with data channel media p. 46
6.6.2.4 Modifying an IMS session to add data channel media p. 47
6.6.3 Impacts on Existing Nodes and Functionality p. 48
6.7 Solution #7: Solution for IMS capability exposure via DC3/DC4 p. 48
6.7.1 Description p. 48
6.7.1.1 Events to be exposed over DC3/DC4 p. 49
6.7.1.2 DC AS requesting a service over DC3/DC4 p. 49
6.7.1.3 Information to be exposed to the DCAS via DC3/DC4 p. 50
6.7.2 Procedures p. 50
6.7.2.1 Event Subscription and Notification p. 50
6.7.2.2 Person-to-Person (P2P) Application Data Channel Setup p. 53
6.7.2.3 Person-to-Application (P2A) Application Data Channel Setup p. 55
6.7.3 Service definition p. 58
6.7.3.1 Enhancements to DCSF services p. 58
6.7.3.2 Enhancements to IMS AS services p. 59
6.7.3.3 Enhancements to HSS services p. 60
6.7.4 Enhancements to Sc interface p. 61
6.7.5 Impacts on existing nodes and functionality p. 61
6.8 Solution #8: Interworking between a DCMTSI UE and an MTSI UE by using messaging p. 61
6.8.1 Description p. 61
6.8.2 Procedures p. 62
6.8.3 Impacts on Existing Nodes and Functionality p. 63
6.9 Solution #9: Data Channel Interworking mechanism between DCMTSI UE and MTSI UE p. 63
6.9.1 Description p. 63
6.9.2 Procedures p. 64
6.9.2.1 Interworking between a DCMTSI client and an MTSI client p. 64
6.9.2.1.1 General p. 64
6.9.2.1.2 Interworking between a DCMTSI client in terminal and an MTSI client in terminal during BootstrapData Channel establishment p. 64
6.9.2.1.3 Interworking between a DCMTSI client in terminal and an MTSI client in terminal during Application Data Channel establishment p. 65
6.10 Solution #10: Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions p. 66
6.10.1 Description p. 66
6.10.2 Procedures p. 68
6.10.2.1 How Originating IMS network invokes the signing on behalf of 3rd party (PBX Scenario) p. 68
6.10.2.2 How Originating IMS network invokes the signing on behalf of 3rd party (Single SIP registration) p. 70
6.10.3 Impacts on services, entities and interfaces p. 71
6.11 Solution #11: Enhancement of STIR/SHAKEN framework to support delivery of third party ID p. 71
6.11.1 Description p. 71
6.11.2 Procedures p. 73
6.11.3 Impacts on Existing Nodes and Functionality p. 73
6.12 Solution #12: Verification of calling party when using third party specific identity p. 74
6.12.1 Description p. 74
6.12.2 Procedures p. 75
6.12.3 Impacts on Existing Nodes and Functionality p. 76
6.13 Solution #13: Support of Third Party User Identities in IMS using STIR/SHAKEN p. 76
6.13.1 Description p. 76
6.13.2 Procedures p. 78
6.13.3 Impacts on existing nodes and functionality p. 78
6.14 Solution #14: Standalone IMS data channel without extra subscription p. 79
6.14.1 Description p. 79
6.14.1.1 General p. 79
6.14.1.2 Subscription of standalone data channel p. 79
6.14.1.3 Capability negotiation of standalone data channel p. 80
6.14.2 Procedures p. 80
6.15 Solution #15: Solution to support standalone bootstrap data channel p. 82
6.15.1 Description p. 82
6.15.2 Procedures p. 82
6.15.3 Impacts on Existing Nodes and Functionality p. 84
6.16 Solution #16: Supporting of standalone IMS DC sessions p. 84
6.16.1 Description p. 84
6.16.1.1 General p. 84
6.16.1.2 The existing clarification on the restriction of standalone IMS DC p. 84
6.16.1.3 Analysis on the impact of standalone IMS DC to existing NFs p. 84
6.16.1.4 Proposal p. 85
6.16.2 Procedures p. 85
6.16.3 Impacts on existing services, entities and interfaces p. 86
6.17 Solution #17: Solution for support of IMS avatar communication using data channel p. 86
6.17.1 Description p. 86
6.17.2 Procedures p. 87
6.17.2.1 Network centric IMS avatar call flow using data channel p. 87
6.17.2.2 UE-A centric IMS avatar call flow using data channel p. 89
6.17.2.3 UE-B centric IMS avatar call flow using data channel p. 90
6.17.3 Impacts on existing nodes and functionality p. 91
6.18 Solution #18: Supporting of network initiated IMS Data Channels p. 91
6.18.1 Description p. 91
6.18.2 Procedures p. 91
6.18.2.1 Network initiated IMS DC establishment p. 91
6.18.2.2 Additional Services and Operations p. 93
6.18.3 Impacts on existing services, entities and interfaces p. 94
6.19 Solution #19: Standalone IMS Data Channel decoupled from Multimedia Telephony p. 95
6.19.1 Description p. 95
6.19.2 Procedures p. 96
6.19.3 Impacts on existing nodes and functionality p. 97
6.20 Solution #20: Support Standalone Bootstrap Data Channel and Standalone Application Data Channel without Subscription and Media Negotiation. p. 98
6.20.1 Description p. 98
6.20.1.1 Subscription of Standalone Data Channel p. 98
6.20.1.2 Standalone Data Channel Capability Negotiation p. 98
6.20.1.3 Support of Standalone Bootstrap Data Channel p. 98
6.20.1.4 Support of Standalone Application Data Channel p. 98
6.20.1.5 Adding Audio/Video/Messaging Media to Established Standalone Data Channel p. 99
6.20.1.6 Removing Audio/Video/Messaging Media from an IMS Session that Contains IMS Data Channel Media p. 99
6.20.2 Procedures p. 99
6.20.2.1 Standalone Application Data Channel Establishment when Both Ends have Version Compatible DC App p. 100
6.20.2.2 Standalone Application Data Channel Establishment when Originating UE does not have Version Compatible DC App p. 101
6.20.2.3 Standalone Application Data Channel Establishment when Terminating UE does not have Version Compatible DC App p. 102
6.20.3 Impacts on Existing Nodes and Functionality p. 103
6.21 Solution #21: Standalone DC setup with backward compatibility p. 103
6.21.1 Description p. 103
6.21.2 Procedures p. 104
6.21.3 Impacts on Existing Nodes and Functionality p. 105
6.22 Solution #22: Multiplexing multiple DC streams over single SCTP connection p. 106
6.22.1 Description p. 106
6.22.1.1 General p. 106
6.22.1.2 Example scenarios for multiplexing and de-multiplexing p. 106
6.22.1.3 Capability negotiation p. 108
6.22.1.3.1 Capability negotiation between UE and network p. 108
6.22.1.3.2 Capability negotiation between originating and terminating network p. 108
6.22.1.4 Determination of multiplexing and de-multiplexing p. 109
6.22.1.5 media management for multiplexing and de-multiplexing p. 109
6.22.1.6 MF/MRF selection p. 109
6.22.2 Procedures p. 110
6.22.2.1 Bootstrap data channel establishment p. 110
6.22.2.1.1 Bootstrap data channels multiplexing in originating network p. 110
6.22.2.1.2 Bootstrap data channel multiplexing in terminating network p. 111
6.22.2.2 Application data channel establishment p. 112
6.22.2.2.1 Application data channel multiplexing when both originating and terminating networks support data channel multiplexing p. 112
6.22.2.2.2 Application data channel multiplexing when terminating network does not support data channel multiplexing p. 114
6.22.2.3 Option of capability discovery between the originating IMS network and terminating IMS network p. 115
6.22.3 Impacts on existing nodes and functionality p. 116
6.23 Solution #23: Download avatar representation in bootstrap data channel from avatar repository p. 116
6.23.1 Description p. 116
6.23.2 Procedures p. 118
6.23.3 Impacts on Existing Nodes and Functionality p. 119
6.24 Solution #24: Transition Between Avatar and Audio/Video Communication p. 119
6.24.1 Description p. 119
6.24.2 Architecture for Avatar Communication p. 119
6.24.3 Procedures p. 121
6.24.3.1 Transition from audio/video communication to Avatar communication p. 121
6.24.3.2 Transition from Avatar communication to audio/video communication p. 122
6.24.4 Impacts on Existing Nodes and Functionality p. 123
6.25 Solution #25: Supporting network-based avatar communication by media capability invocation p. 123
6.25.1 Description p. 123
6.25.2 Procedures p. 125
6.25.2.1 Network-based procedure for avatar communication p. 125
6.25.2.2 Transcoding between speech and gesture (or text) in communication p. 126
6.25.3 Impacts on Existing Nodes and Functionality p. 127
6.26 Solution #26: Support for Avatars in AR Calls p. 128
6.26.1 Description p. 128
6.26.1.1 Function Mapping p. 128
6.26.1.2 Architecture Enhancements p. 129
6.26.2 Procedures p. 130
6.26.3 Impacts on existing services, entities and interfaces p. 133
6.27 Solution #27: Early capability negotiation for IMS Avatar Communication p. 133
6.27.1 Description p. 133
6.27.1.1 General p. 133
6.27.1.2 Architecture p. 133
6.27.1.3 Capability negotiation p. 134
6.27.1.3.1 Definition of Avatar type and Required UE avatar capability p. 134
6.27.1.3.2 Negotiation steps p. 134
6.27.1.4 Avatar objects storage and access p. 134
6.27.1.5 Transcoding of Avatar p. 134
6.27.2 Procedures p. 135
6.27.2.1 Storing Avatar objects into DAC p. 135
6.27.2.2 Early capability negotiation and transcoding p. 136
6.27.3 Impacts on services, entities and interfaces p. 138
6.28 Solution #28: Configuration of PS Data Off exemption on IMS DC p. 138
6.28.1 Description p. 138
6.28.2 Procedures p. 139
6.28.2.1 PS Data Off activation with existing IMS Session with DCs p. 139
6.28.2.2 PS Data Off activation without existing IMS session with DCs p. 140
6.28.3 Impacts on services, entities and interfaces p. 141
6.29 Solution #29: Handling of PS data off exemption for services over IMS DC p. 141
6.29.1 Description p. 141
6.29.2 Procedures p. 141
6.29.3 Impacts on Existing Nodes and Functionality p. 143
6.30 Solution #30: DC interworking with DC service data provision to MTSI UE p. 143
6.30.1 Description p. 143
6.30.2 Procedures p. 143
6.30.3 Impacts on Existing Nodes and Functionality p. 145
6.31 Solution #31: Support of IMS DC based avatar communication p. 146
6.31.1 Description p. 146
6.31.1.1 General p. 146
6.31.2 Procedures p. 147
6.31.2.1 Authorization of the UE to access avatar data stored in the network p. 147
6.31.2.2 Bootstrap data channel establishment for retrieval of identities of avatar data stored in the network p. 147
6.31.3 Impacts on Existing Nodes and Functionality p. 149
6.32 Solution #32: Solution for support of IMS avatar communication without using data channel p. 150
6.32.1 Description p. 150
6.32.2 Procedures p. 152
6.32.2.1 Scenario 1: Network centric IMS avatar call flow using SIP/SDP p. 152
6.32.2.2 Scenario 2: UE-A centric IMS avatar call flow using SIP/SDP p. 154
6.32.2.3 Scenario 3: UE-B centric IMS avatar call flow using SIP/SDP p. 155
6.32.3 Impacts on existing nodes and functionality p. 156
7 Overall Evaluation p. 157
8 Conclusions p. 157
8.1 Conclusions of KI #1 p. 157
8.2 Conclusions of KI #2 p. 158
8.3 Conclusions of KI #3 p. 158
8.4 Conclusions of KI #4 p. 158
8.5 Conclusions of KI #5 p. 159
8.6 Conclusions of KI #6 p. 160
8.7 Conclusions of KI #7 p. 161
8.8 Conclusions of KI #8 p. 163
$ Change history p. 165
