Content for TR 24.837 Word version: 10.0.0
4 Procedures and issues
4.1 General
4.2 Inter-UE transfer and collaborative session procedures for UEs belonging to different IMS subscriptions under the same operator
4.3 Discovery of UEs of different IMS subscriptions which can participate in collaborative sessions
4.4 Establishment of collaborative session upon session setup
4.5 Assignment and transfer of control of a collaborative session
...
...
4 Procedures and issues p. 18
4.1 General p. 18
4.1.1 Subscription to dialog events filtering p. 18
4.1.2 Routing incoming session requests to a controller capable UE p. 18
4.2 Inter-UE transfer and collaborative session procedures for UEs belonging to different IMS subscriptions under the same operator p. 18
4.2.1 General p. 18
4.2.2 Procedures p. 19
4.2.2.1 Extension of existing Rel-9 procedures for inter-UE transfer and collaborative session for UEs belonging to different IMS subscriptions under the same operator p. 19
4.2.2.2 New Rel-10 procedures for inter-UE transfer and collaborative session for UEs belonging to different IMS subscriptions under the same operator p. 19
4.2.3 Identified issues p. 19
4.2.4 Call flows p. 20
4.3 Discovery of UEs of different IMS subscriptions which can participate in collaborative sessions p. 24
4.4 Establishment of collaborative session upon session setup p. 24
4.4.1 General p. 24
4.4.2 Procedures p. 24
4.4.2.1 Establishment of collaborative session upon originating IMS session setup p. 24
4.4.2.1.1 Alternative 1 - indicating collaborative session establishment by providing controllee UE SIP URI in SDP p. 24
4.4.2.1.1.1 Alternative 1a- media negotiation with remote party first p. 24
4.4.2.1.1.2 Alternative 1b- media negotiation with controllee UE first p. 25
4.4.2.1.2 Alternative 2 - indicating collaborative session establishment by multipart/related Content-Type parameter p. 27
4.4.2.1.3 Alternative 3 - indicating collaborative session establishment by providing controllee UE SIP URI in SDP attribute and using P-Asserted-Identity p. 28
4.4.2.1.3A Alternative 3A - indicating collaborative session establishment by providing controllee UE SIP URI in SDP connection line and using P-Asserted-Identity p. 29
4.4.2.1.4 Alternative 4 - indicating collaborative session establishment using multiple REFER p. 30
4.4.2.2 Establishment of collaborative session upon terminating IMS session setup p. 32
4.4.2.2.1 Alternative 1: Using SIP 183 (Session Progress) response p. 32
4.4.2.2.2 Alternative 2 - indicating collaborative session establishment bymultipart/related Content-Type parameter p. 33
4.4.2.2.3 Alternative 3 - indicating collaborative session establishment by SIP REFER request before SIP 200 (OK) response p. 34
4.4.2.2.4 Alternative 4 - Using SIP 300 (Multiple Choices) response p. 36
4.4.3 Identified issues p. 38
4.4.4 Call flows p. 38
4.4.4.1 Call flows for establishment of collaborative session upon originating IMS session setup without forked responses p. 38
4.4.4.1.1 Alternative 1 - indicating collaborative session establishment by providing controllee UE SIP URI in SDP p. 38
4.4.4.1.1.1 Alternative1a - Media negotiation with remote UE first p. 38
4.4.4.1.1.2 Alternative 1b - Media negotiation with controllee UE first p. 43
4.4.4.1.2 Alternative 2 - indicating collaborative session establishment by multipart/related Content-Type parameter p. 47
4.4.4.1.3 Alternative 3 - indicating collaborative session establishment by providing controllee UE SIP URI in SDP using P-Asserted-Identity p. 52
4.4.4.1.4 Alternative 4 - indicating collaborative session establishment using multiple REFER p. 56
5.4.1.4 Pros and cons of alternative 3 - indicating collaborative session establishment using multiple REFER p. 61
4.4.4.2 Call flows for establishment of collaborative session upon terminating IMS session setup p. 63
4.4.4.2.1 Alternative 1: Using SIP 183 (Session Progress) response p. 63
4.4.4.2.2 Alternative 2 - indicating collaborative session establishment by multipart/related Content-Type parameter p. 67
4.4.4.2.3 Alternative 3 - indicating collaborative session establishment by SIP REFER request before SIP 200 (OK) response p. 71
4.4.4.2.4 Alternative 4: Using SIP 300 (Multiple Choices) response p. 76
4.4.4.3 Call flows for establishment of collaborative session upon originating IMS session setup with forked responses p. 82
4.5 Assignment and transfer of control of a collaborative session p. 100
4.5.1 General p. 100
4.5.2 Procedures p. 101
4.5.2.1 Indicating whether controller UE wishes to be the controller of the collaborative session p. 101
4.5.2.1.0 General p. 101
4.5.2.1.1 Alternative 1 - Indicating whether controller UE wishes to be the controller of the collaborative session using the iut-controller media feature tag p. 101
4.5.2.1.2 Alternative 2 - Indicating whether Controller UE wishes to remain a controller of the collaborative Session using an XML body p. 102
4.5.2.1.2.1 General p. 102
4.5.2.1.2.2 Alternative 2A - Indicating whether Controller UE wishes to remain a controller of the collaborative Session using SIP INFO request p. 102
4.5.2.1.2.3 Alternative 2B - Indicating whether Controller UE wishes to remain a controller of the collaborative Session using an XML body in the transfer request p. 102
4.5.2.1.3 Alternative 3 - Indicating whether controller UE wishes to be the controller of the collaborative session using a new media feature tag p. 102
4.5.2.2 Identifying that another UE is requested to become a controller of the collaborative session p. 102
4.5.2.2.1 Alternative 1 - Identifying a new controller UE using SIP REFER with method= REFER p. 102
4.5.2.2.2 Alternative 2 - Identifying a new controller UE using an XML Body p. 103
4.5.2.2.2.1 General p. 103
4.5.2.2.2.2 Alternative 2A - Identifying a new controller UE using SIP INFO p. 103
4.5.2.2.2.3 Alternative 2B - Identifying a new controller UE using an Event Package p. 103
4.5.2.2.2.4 Alternative 2C - Identifying a new controller UE using XML embedded in Refer-To URI p. 103
4.5.2.2.3 Alternative 3 - Identifying a new controller UE using a SIP header field p. 103
4.5.2.2.4 Alternative 4 - Identifying a new controller UE using Accept-Contact in the Refer-To URI p. 104
4.5.2.3 Indicating to another UE that it is requested to become a controller of the collaborative Session p. 104
4.5.2.3.1 General p. 104
4.5.2.3.2 Alternative 1 - Requesting a UE to become a controller UE using an XML Body p. 104
4.5.2.3.2.1 General p. 104
4.5.2.3.2.2 Alternative 1A - Assigning a new controller UE using SIP INFO request p. 104
4.5.2.3.2.3 Alternative 1B - Assigning a new controller UE using an Event Package p. 104
4.5.2.3.2.4 Alternative 1C - Assigning a new controller UE using XML Body as a MIME type in the request p. 104
4.5.2.3.3 Alternative 2 - Requesting a UE to become a controller UE using a SIP header field p. 104
4.5.2.3.4 Alternative 3 - Requesting a UE to become a controller UE using a media feature tag in an Accept-Contact header field p. 105
4.5.2.4 Indicating acceptance of becoming a controller of the collaborative session p. 105
4.5.2.4.1 Alternative 1 - Indicating acceptance of becoming a controller using an XML Body p. 105
4.5.2.4.1.1 General p. 105
4.5.2.4.1.2 Alternative 1A - Indicating acceptance of becoming a controller using an XML Body in SIP 200 (OK) response p. 105
4.5.2.4.1.3 Alternative 1B - Indicating acceptance of becoming a controller using an XML Body in SIP INFO request p. 105
4.5.2.4.2 Alternative 2 - Indicating acceptance of becoming a controller using a SIP header field p. 105
4.5.2.4.3 Alternative 3 - Indicating acceptance of becoming a controller using a new feature tag p. 105
4.5.2.5 Informing that another UE has become a controller of the collaborative session p. 106
4.5.2.5.1 Alternative 1 - Informing that another UE has become a controller UE using an XML Body p. 106
4.5.2.5.1.1 General p. 106
4.5.2.5.1.2 Alternative 1A - Informing that another UE has become a controller UE using SIP INFO p. 106
4.5.2.5.1.3 Alternative 1B - Informing that another UE has become a controller UE using a new Event Package p. 106
4.5.2.5.2 Alternative 2 - Informing that another UE has become a controller UE using a SIP header field p. 106
4.5.2.5.3 Alternative 3 - Informing that another UE has become a controller UE using a SIPfrag in an events package p. 106
4.5.2.5.3.1 Alternative 3A - Informing that another UE has become a controller UE using a SIPfrag of the XML body in the response p. 106
4.5.2.5.3.2 Alternative 3B - Informing that another UE has become a controller UE using a SIPfrag of the new header field p. 107
4.5.2.5.3.3 Alternative 3C - Informing that another UE has become a controller UE using a SIPfrag of a feature tag in the Contact header field p. 107
4.5.3 Identified issues and advantages for each alternative p. 107
4.5.4 Call flows p. 107
4.5.4.1 Indicating whether Controller UE wishes to remain a controller of the collaborative Session p. 107
4.5.4.1.1 Alternative 1 - Indicating whether Controller UE wishes to remain a controller of the collaborative Session using the iut-controller media feature tag p. 107
4.5.4.1.2 Alternative 2 - Indicating whether Controller UE wishes to remain a controller of the collaborative Session using an XML body p. 110
4.5.4.2 Identifying that another UE is requested to become a controller of the collaborative session p. 110
4.5.4.2.1 Alternative 1 - controller UE transfer by SIP REFER with method=REFER p. 110
4.5.4.2.2 Alternative 2 - Identifying a new controller UE using an XML Body p. 114
4.5.4.2.2.1 General p. 114
4.5.4.2.2.2 Alternative 2A - Identifying a new controller UE transfer by using SIP INFO p. 114
4.5.4.2.2.3 Alternative 2B - Identifying a new controller UE using an Event Package p. 116
4.5.4.2.2.4 Alternative 2C - Identifying a new controller UE using XML embedded in Refer-To URI p. 116
4.5.4.2.3 Alternative 3 - Identifying a new controller UE using a SIP header field p. 119
4.5.4.2.4 Alternative 4 - Identifying a new controller UE using Accept-Contact in the Refer-To URI p. 119
4.5.4.3 Indicating to another UE that it is requested to become a controller of the collaborative Session p. 119
4.5.4.3.1 General p. 119
4.5.4.3.2 Alternative 1 - Requesting a UE to become a controller UE using an XML Body p. 119
4.5.4.3.2.1 General p. 119
4.5.4.3.2.2 Alternative 1A - Assigning a new controller UE using SIP INFO request p. 119
4.5.4.3.2.3 Alternative 1B - Assigning a new controller UE using an Event Package p. 119
4.5.4.3.2.4 Alternative 1C - Assigning a new controller UE using XML Body as a MIME type in the request p. 119
4.5.4.3.3 Alternative 2 - Requesting a UE to become a controller UE using a SIP header field p. 119
4.5.4.3.4 Alternative 3 - Requesting a UE to become a controller UE using a media feature tag in an Accept-Contact header field p. 119
4.5.4.4 Indicating acceptance of becoming a controller of the collaborative session p. 119
4.5.4.4.1 Alternative 1 - Indicating acceptance of becoming a controller using an XML Body p. 119
4.5.4.4.1.1 General p. 119
4.5.4.4.1.2 Alternative 1A - Indicating acceptance of becoming a controller using an XML Body in SIP 200 (OK) response p. 119
4.5.4.4.1.3 Alternative 1B - Indicating acceptance of becoming a controller using an XML Body in SIP INFO request p. 119
4.5.4.4.2 Alternative 2 - Indicating acceptance of becoming a controller using a SIP header field p. 120
4.5.4.4.3 Alternative 3 - Indicating acceptance of becoming a controller using a new feature tag p. 120
4.5.4.5 Informing that another UE has become a controller of the collaborative session p. 120
4.5.4.5.1 Alternative 1 - Informing that another UE has become a controller UE using an XML Body p. 120
4.5.4.5.1.1 General p. 120
4.5.4.5.1.2 Alternative 1A - Informing that another UE has become a controller UE using SIP INFO p. 120
4.5.4.5.1.3 Alternative 1B - Informing that another UE has become a controller UE using a new Event Package p. 120
4.5.4.5.2 Alternative 2 - Informing that another UE has become a controller UE using a SIP header field p. 120
4.5.4.5.3 Alternative 3 - Informing that another UE has become a controller UE using a SIPfrag in an events package p. 120
4.5.4.5.3.1 Alternative 3A - Informing that another UE has become a controller UE using a SIPfrag of the XML body in the response p. 120
4.5.4.5.3.2 Alternative 3B - Informing that another UE has become a controller UE using a SIPfrag of the new header field p. 120
4.5.4.5.3.3 Alternative 3C - Informing that another UE has become a controller UE using a SIPfrag of a feature tag in the Contact header field p. 120
