A.11 Signalling flows for media flow transfer
24.3373GPPIP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transferRelease 17Stage 3TS
A.11.1 Introduction
This subclause describes signalling flows for media flow transfer. Four different scenarios are considered in the clause:
– subclause A.11.2 shows an example when Media flows transfer initiated by a UE not participating in the ongoing collaborative session;
– subclause A.11.3 shows an example when Media flows transfer initiated when no collaborative session has been established;
– subclause A.11.4 shows an example when Media flows transfer initiated by a controllee UE of an ongoing collaborative session; and
– subclause A.11.5 shows an example when Controllee UE initiated addition of media to another controllee UE.
A.11.2 Media flows transfer initiated by a UE not participating in the ongoing collaborative session
This subclause describes the scenario when the Media flow is transferred from UE-1 to UE-3 requested by UE-3 and the UE-3 becomes a new Controllee UE. The flow diagram shows when UE-1 and UE-3 belong to the different subscription. The SCC AS-1 is controlling the colloaborative session.
UE-1(123.45.67.89) and UE-2 (123.112.67.87) are included in a Collaborative Session with the remote UE (132.54.76.98), in which UE-1 is the Controller UE and UE-2 is the Controllee UE. Media paths exist between UE-1 and remote UE(video) and between UE-2 and remote UE(audio). The video component is bidirectional from the remote UE to the controller UE, UE-1. The UE-3(123.23.45.67) wants to pull the media flow between UE-1 and remote UE. After this procedure, the UE-3 will be in collaborative session.
Figure A.11.2-1: Signalling flow for Media flows transfer initiated by a UE not participating in the ongoing collaborative session
1. UE-3 discovers the sessions of UE-1.
2-6. SIP REFER request (from UE-3 to controller UE, UE-1)
The UE-3 sends SIP REFER request to the controller UE, UE-1 to request the media transfer. The SIP REFER request is finally routed to the SCC AS-1 serving UE-1.
Table A.11.2-2: SIP REFER request (UE-3 to UE-1)
REFER sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via: SIP/2.0/UDP [3333::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7dfdsdq
To: <sip:user1_public1@home1.net>
From: <sip:user2_public1@home2.net>;tag=294756
Call-ID: Asdasd23123366
Cseq: 4897924 REFER
Max-Forwards: 70
P-Preferred-Identity: <sip:user2_public1@home2.net>;
Refer-To: <sip:user2_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333?body= m%3Daudio%200%20RTP%2FAVP%97%0Dm%3Dvideo%203002%20RTP%2FAVP%2098%2099>
Require: target-dialog
Target-dialog: cb03a0s09a2sdfglkj11111;remote-tag=27364;local-tag=11928
Referred-By: sip:user2_public1@home2.net
Contact: sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333
Accept-Contact:* ;+g.3gpp.iut-focus;explicit;require
Accept: application/sdp, message/sipfrag
Content-Length: 0
7-11. SIP 200 (OK) response (from SCC AS-1 serving UE-1 to UE-3)
SCC AS-1 serving UE-1 sends a SIP 200 (OK) response to UE-3 as response to the SIP REFER request.
12-16. SIP NOTIFY request (from SCC AS-1 serving UE-1 to UE-3)
The SCC AS-1 serving UE-1 sends a SIP NOTIFY request to UE-3 to notify implicit subscription to the SIP REFER request results.
Table A.11.2-12: SIP NOTIFY request (SCC AS-1 to UE-3)
NOTIFY sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333 SIP/2.0
Via:
To:sip:user2_public2@home2.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net
Allow:
Event:refer
Subscription-State:active; expires=3600
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 100 Trying
17-21. SIP 200 (OK) response (from UE-3 to SCC AS-1 serving UE-1)
The UE-3 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS-1.
22-26. SIP INVITE request (from SCC AS-1 serving UE-1 to UE-3)
Since the message 2-6 contains a Refer-to header field addressed to UE-3 and the URI paramaters, listing an video line which is not currently supported by another UE than controller UE, the SCC AS-1 realizes the procedure is for transferring the media from that controller UE (UE-1) to UE-3. The SCC AS-1 sends a SIP INVITE request to the UE-3, to transfer the video media component.
Table A.11.2-22: SIP INVITE request (SCC AS-1 serving UE-1 to UE-3)
INVITE sip:user2_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333 SIP/2.0
Via: SIP/2.0/UDP sccas1.home1.net; branch=z9hG4bK332b33.3;
To: sip:user2_public1@home2.net;
From: sip:interUEtransfer@sccas1.home1.net; tag=12486
Call-ID: cb03a0s09a2sdfglkj33333
Cseq: 111 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net; +g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 3002 RTP/AVP 98 99
a=sendonly
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
27-31. SIP 200 (OK) response (from UE-3 to SCC AS-1 serving UE-1)
The target UE, UE-3, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCCAS-1.
Table A.11.2-27: SIP 200 (OK) response (UE-3 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To: sip:user2_public1@home2.net; tag = 24861
From: sip:interUEtransfer@sccas1.home1.net; tag = 12486
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.23.45.67
s=-
c=123.23.45.67
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
a=recvonly
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
32-36. SIP ACK request (from SCC AS-1 serving UE-1 to target UE; UE-3)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the UE-3.
37-38. SIP re-INVITE request (from SCC AS-1 serving UE-1 to controller UE; UE-1)
Table A.11.2-37: SIP INVITE request (SCC AS-1 serving UE-1 to UE-1)
INVITE sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via:
To: sip:user1_public1@home1.net;Tag=11928
From: sip:userR_public1@homeR.net; tag=27364
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
a=sendonly
39-40. SIP 200 (OK) response (from controller UE, UE-1 to SCC AS-1 serving UE-1)
The UE-1 sends a SIP 200 (OK) response with an SDP answer.
Table A.11.2-39: SIP 200 (OK) response (UE-1 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
a=inactive
41-42. SIP ACK request (from SCC AS-1 serving UE-1 to controller UE; UE-1)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the UE-1.
43-45. SIP re-INVITE request (from SCC AS-1 serving UE-1 to remote UE)
The SCC AS-1 serving UE-1 sends a SIP re-INVITE request to the remote UE.
Table A.11.2-43: SIP INVITE request (SCC AS-1 serving UE-1 to remote UE)
INVITE sip:userR_public1@homeR.net SIP/2.0
Via:
To: sip:userR_public1@homeR.net;tag=27364
From: sip:user1_public1@home1.net;tag=11928
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: <sip:interUEtransfer@sccas1.home1.net>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
t=0 0
m=audio 1300 RTP/AVP 96 97
c=IN IP4 123.112.67.87
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 1302 RTP/AVP 98 99
c=IN IP4 123.23.45.67
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
46-48. SIP 200 (OK) response (from remote UE to SCC AS-1 serving UE-1)
The remote UE acknowledges the SIP re-INVITE request by sending a SIP 200 (OK) response to the SCC AS-1.
Table A.11.2-46: SIP 200 (OK) response (remote UE to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Asserted-Identity:
Contact: sip:userR_public1@homeR.net
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
49-51. SIP ACK request (from SCC AS-1 serving UE-1 to remote UE)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the remote UE.
52-56. SIP re-INVITE request (from SCC AS-1 serving UE-1 to UE-3)
The SCC AS-1 serving UE-1 sends a SIP re-INVITE request to UE-3 to activate the video media component.
Table A.11.2-52: SIP INVITE request (SCC AS-1 serving UE-1 to UE-3)
INVITE sip:user2_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333 SIP/2.0
Via: SIP/2.0/UDP sccas1.home1.net; branch=z9hG4bK332b33.3;
To: sip:user2_public1@home2.net;
From: sip:interUEtransfer@sccas1.home1.net; tag=12486
Call-ID: cb03a0s09a2sdfglkj33333
Cseq: 111 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
57-61. SIP 200 (OK) response (from UE-3 to SCC AS-1 serving UE-1)
The target UE, UE-3, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCCAS-1 serving UE-1.
Table A.11.2-57: SIP 200 (OK) response (UE-3 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To: sip:user2_public1@home2.net; tag = 24861
From: sip:interUEtransfer@sccas1.home1.net; tag = 12486
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.23.45.67
s=-
c=123.23.45.67
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
62-66. SIP ACK request (from SCC AS-1 serving UE-1 to target UE; UE-3)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the UE-3.
67-68. SIP re-INVITE request (from SCC AS-1 serving UE-1 to controller UE; UE-1)
The SCC AS-1 sends a SIP re-INVITE request to the controller UE. Since UE-1 keep the collaborative session control, SCC AS-1 sends the re-INVITE instead of BYE in spite of no media flow at UE-1.
Table A.11.2-67: SIP INVITE request (SCC AS-1 serving UE-1 to UE-1)
INVITE sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via:
To: sip:user1_public1@home1.net;Tag=11928
From: sip:userR_public1@homeR.net; tag=27364
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 0 RTP/AVP 98 99
69-70. SIP 200 (OK) response (from controller UE, UE-1 to SCC AS-1 serving UE-1)
The UE-1 sends a SIP 200 (OK) response with an SDP answer.
Table A.11.2-69: SIP 200 (OK) response (UE-1 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 0 RTP/AVP 97
m=video 0 RTP/AVP 98 99
71-72. SIP ACK request (from SCC AS-1 serving UE-1 to controller UE; UE-1)
The SCC AS-1 sends a SIP ACK request to the UE-1.
73-77. SIP NOTIFY request (from SCC AS-1 serving UE-1 to UE-3)
The SCC AS-1 serving UE-1 sends a SIP NOTIFY request including the SIP final response as a sipfrag body to the UE-3 to inform about the success status of the inter-UE transfer.
Table A.11.2-73: SIP NOTIFY request (SCC AS-1 to UE-3)
NOTIFY sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333 SIP/2.0
Via:
To:sip:user2_public2@home2.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net
Allow:
Event:refer
Subscription-State:terminated; reason=noresource
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 200 OK
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 0 RTP/AVP 97
m=video 0 RTP/AVP 98 99
78-82. SIP 200 (OK) response (from UE-3 to SCC AS-1 serving UE-1)
The UE-3 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS-1.
A.11.3 Media flows transfer initiated when no collaborative session has been established
This subclause describes the scenario when the media flow is transferred from UE-1 to UE-2 requested by UE-2. The flow diagram shows when UE-1 and UE-2 belong to the same subscription.
Media path exist between UE-1(123.45.67.89) and Remote UE(132.54.76.98). UE-2(123.112.67.87) wants to pull the video media flow between UE-1 and Remote-UE. After this procedure, collaborative session will be established.
Figure A.11.3-1 Signalling flow for Media flow transfer initiated when no collaborative session has been established
1-2. UE-1 is in session with Remote UE
There is a multimedia session comprising audio and video media between the UE-1 and the Remote UE anchored at SCC AS.
3. UE-2 discovers the session of UE-1
4-5. SIP REFER request (from UE-2 to SCC AS)
The UE-2 sends SIP REFER request to the UE-1 to request the media transfer from UE-1 to UE-2. The SIP REFER request is routed to the SCC AS by filter criteria. The SCC AS does not route the SIP REFER request to the address set in the Request-URI if there is the g.3gpp.iut-focus media feature tag in the Accept-Contact header field.
Table A.11.3-4: SIP REFER request (UE-2 to SCC AS)
REFER sip:user1_public1@home1.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via: SIP/2.0/UDP [3333::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7dfdsdq
To: <sip: user1_public1@home1.net>
From: <sip:user1_public2@home1.net>;tag=294756
Call-ID: Asdasd23123366
Cseq: 4897924 REFER
Max-Forwards: 70
P-Preferred-Identity: <sip:user1_public2@home1.net>;
Refer-To: <sip:user1_public2@home1.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222?body= m%3Daudio%200%20RTP%2FAVP%97%0Dm%3Dvideo%203002%20RTP%2FAVP%2098%2099>
Require: target-dialog
Target-dialog: cb03a0s09a2sdfglkj11111;remote-tag=27364;local-tag=11928
Referred-By: sip:user1_public2@home1.net
Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222
Accept-Contact: +g.3gpp.iut-focus;explicit;require
Accept: application/sdp, message/sipfrag
Content-Length: 0
6-7. SIP 200 (OK) response (from SCC AS to UE-2)
SCC AS sends a SIP 200 (OK) response to UE-2 as response to the SIP REFER request.
8-9. SIP NOTIFY request (from SCC AS to UE-2)
The SCC AS sends a SIP NOTIFY request to UE-2 to notify implicit subscription to the SIP REFER request results.
Table A.11.3-8: SIP NOTIFY request (SCC AS to UE-2)
NOTIFY sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via:
To:sip:user1_public2@home1.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net
Allow:
Event:refer
Subscription-State:active; expires=3600
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 100 Trying
10-11. SIP 200 (OK) response (from UE-2 to SCC AS)
The UE-2 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS.
12-13. SIP INVITE request (from SCC AS to UE-2)
Since the 4-5 SIP REFER request contains a Refer-to header field addressed to UE-2 and the URI parameters, listing a video line which is transferred and an audio line with port number set to zero which is not transferred, The SCC-AS sends a SIP INVITE request to the UE-2, to transfer the video media component. In order to avoid to UE-2 to start sending video to the Remote UE, the SCC AS add an a line to sendonly in the SDP offer.
Table A.11.3-12: SIP INVITE request (SCC-AS to UE-2)
INVITE sip:user1_public2@home1.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via: SIP/2.0/UDP sccas.home1.net; branch=z9hG4bK332b33.3;
To: sip:user1_public2@home1.net;
From: sip:interUEtransfer@sccas1.home1.net; tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
Cseq: 111 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 3002 RTP/AVP 98 99
a=sendonly
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
14-15. SIP 200 (OK) response (from UE-2 to SCC-AS)
The target UE, UE-2, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC AS.
Table A.11.3-14: SIP 200 (OK) response (UE-2 to SCC AS)
SIP/2.0 200 OK
Via:
To: sip:user1_public2@home1.net; tag=36527
From: sip:interUEtransfer@sccas1.home1.net; tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.112.67.87
s=-
c=123.112.67.87
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
a=inactive
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
16-17. SIP ACK request (from SCC AS to UE-2)
The SCC AS sends a SIP ACK request to the UE-2.
18-19. SIP re-INVITE request (from SCC AS to UE-1)
The SCC-AS sends a SIP re-INVITE request to the UE-1 to hold the video media session to be transferred.
Table A.11.3-18: SIP INVITE request (SCC AS to UE-1)
INVITE sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via:
To: sip:user1_public1@home1.net;Tag=11928
From: sip:userR_public1@home2.net; tag=27364
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=video 3002 RTP/AVP 98 99
a=sendonly
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=audio 3000 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
20-21. SIP 200 (OK) response (from UE-1 to SCC AS)
The UE-1 sends a SIP 200 (OK) response with an SDP answer.
Table A.11.3-20: SIP 200 (OK) response (UE-1 to SCC AS)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 1300 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 1202 RTP/AVP 98 99
a=inactive
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
22-23. SIP ACK request (from SCC AS to UE-1)
The SCC AS sends a SIP ACK request to the UE-1.
24-26. SIP re-INVITE request (from SCC AS to remote UE)
The SCC AS sends a SIP re-INVITE request to the remote UE.
Table A.11.3-24: SIP INVITE request (SCC AS to remote UE)
INVITE sip:userR_public1@home2.net SIP/2.0
Via:
To: sip:userR_public1@home2.net;tag=27364
From: sip:user1_public1@home1.net;tag=11928
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: <sip:interUEtransfer@sccas1.home1.net>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
t=0 0
m=audio 1300 RTP/AVP 96 97
c=IN IP4 123.45.67.89
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 1302 RTP/AVP 98 99
c=IN IP4 123.112.67.87
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
27-29. SIP 200 (OK) response (from Remote UE to SCC AS)
The Remote UE acknowledges the SIP re-INVITE request by sending a SIP 200 (OK) response to the SCC AS.
Table A.11.3-27: SIP 200 (OK) response (Remote UE to SCC AS)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Asserted-Identity:
Contact: sip:userR_public1@home2.net
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
30-32. SIP ACK request (from SCC AS to Remote UE)
The SCC-AS sends a SIP ACK request to the Remote UE.
33-34. SIP re-INVITE request (from SCC AS to UE-2)
The SCC AS sends a SIP re-INVITE request to UE-2 to activate the video media component.
Table A.11.3-33: SIP INVITE request (SCC AS to UE-2)
INVITE sip:user1_public2@home1.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via: SIP/2.0/UDP sccas.home1.net; branch=z9hG4bK332b33.3;
To: sip:user1_public2@home1.net; tag=36527
From: sip:interUEtransfer@sccas1.home1.net; tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
Cseq: 112 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
35-36. SIP 200 (OK) response (from UE-2 to SCC AS)
The UE-2 sends a SIP 200 (OK) response to the SCC AS.
Table A.11.3-35: SIP 200 (OK) response (UE-2 to SCC AS)
SIP/2.0 200 OK
Via:
To: sip:user1_public2@home1.net; tag=36527
From: sip:interUEtransfer@sccas1.home1.net; tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.112.67.87
s=-
c=123.112.67.87
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
37-38. SIP ACK request (from SCC AS to UE-2)
The SCC AS sends a SIP ACK request to the UE-2.
40-41. SIP re-INVITE request (from SCC AS to UE-1)
The SCC-AS sends a SIP re-INVITE request to the UE-1 to release the video media component.
Table A.11.3-40: SIP INVITE request (SCC AS to UE-1)
INVITE sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via:
To: sip:user1_public1@home1.net;Tag=11928
From: sip:userR_public1@home2.net; tag=27364
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 0 RTP/AVP 98 99
41-42. SIP 200 (OK) response (from UE-1 to SCC AS)
The UE-1 sends a SIP 200 (OK) response with an SDP answer.
Table A.11.3-41: SIP 200 (OK) response (UE-1 to SCC AS)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 1300 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 0 RTP/AVP 98 99
43-44. SIP ACK request (from SCC AS to UE-1)
The SCC AS sends a SIP ACK request to the UE-1.
45-46. SIP NOTIFY request (from SCC AS to UE-2)
The SCC AS sends a SIP NOTIFY request including the SIP final response as a sipfrag body request to the UE-2.
Table A.11.3-45: SIP NOTIFY request (SCC AS to UE-2)
NOTIFY sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via:
To:sip:user2_public1@home1.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net
Allow:
Event:refer
Subscription-State:terminated; reason=noresource
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 200 OK
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>;+g.3gpp.iut-controller
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 1300 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 0 RTP/AVP 98 99
47-48. SIP 200 (OK) response (from UE-2 to SCC AS)
The UE-2 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS.
A.11.4 Media flows transfer initiated by a controllee UE of an ongoing collaborative session
This subclause describes the scenario when the Media flow is transferred from Controller UE, UE-1 to Controllee UE, UE-2 requested by UE-2. The flow diagram shows when UE-1 and UE-2 belong to the different subscription.
UE-1 (123.45.67.89) and UE-2 (123.112.67.87) are included in a Collaborative Session with the remote UE (132.54.76.98), in which UE-1 is the Controller UE and UE-2 is the Controllee UE. The call is anchored in the SCC AS-1 controlling the collaborative session. Prior to transfer the Media flow, UE-2 gets the dialog information such as the content type and port numbers on the remote end. This is done by UE-2 having subscribed to dialog event package between UE-1 and the SCC AS-1.
Figure A.11.4-1: Signalling flow for Media flows transfer initiated by a controllee UE of an ongoing collaborative session
1. UE-2 discovers the session of UE-1
2-6. SIP REFER request (from UE-2 to SCC AS serving UE-1)
The SIP REFER request contains a Refer-To header field containing a URI of Target UE, UE-2 and a body parameter containing an m line for audio to be pulled with the port number set to the non-zero port numbers use in the SDP parameter from the corresponding media descriptions as received during the last successful SDP offer-answer exchange from the Remote UE. The SIP REFER request also includes a Target-dialog header field containing the details of the dialog for the existing session between UE-1 and Remote-UE.
Table A.11.4-2 SIP REFER request (UE-2 to SCC AS-1 serving UE-1)
REFER sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via: SIP/2.0/UDP [2222::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7dfdsdq
To: <sip: user1_public1@home1.net >
From: <sip:user2_public1@home2.net>;tag=294756
Call-ID: Asdasd23123366
Cseq: 4897924 REFER
Max-Forwards: 70
P-Preferred-Identity: <sip:user2_public1@home2.net>;
Refer-To: <sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222? body=m%3Daudio%203000%20RTP%2FAVP%97%0Dm%3Dvideo%203002%20RTP%2FAVP%2098%2099>
Require: target-dialog
Target-dialog: cb03a0s09a2sdfglkj11111;remote-tag=27364;local-tag=11928
Referred-By: sip:user2_public1@home2.net
Contact: sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222
Accept-Contact:* ;+g.3gpp.iut-focus;explicit;require
Accept: application/sdp, message/sipfrag
Content-Length: 0
7-11. SIP 200 (OK) response (from SCC AS-1 serving UE-1 to UE-2)
The SCC AS-1 serving UE-1 sends a SIP 200 (OK) response to UE-2 as response to the SIP REFER request.
12-16. SIP NOTIFY request (from SCC AS-1 serving UE-1 to UE-2)
The SCC AS-1 serving UE-1 sends a SIP NOTIFY request to UE-2 to notify implicit subscription to the SIP REFER request results.
Table A.11.4-12: SIP NOTIFY request (SCC AS-1 serving UE-1 to UE-2)
NOTIFYsip:user2_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via:
To:sip:user2_public1@home2.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Event:refer
Subscription-State:active; expires=3600
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 100 Trying
17-21. SIP 200 (OK) response (from UE-2 to UE-1)
The UE-2 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the UE-1.
22-26. SIP re-INVITE request (from SCC AS-1 serving UE-1 to UE-2)
Since the 2-6 SIP REFER request contains a Refer-to header field addressed to UE-2 and the URI paramaters, listing an audio line which is not currently supported by UE-2, the SCC AS-1 realizes the procedure is for transferring the media from that controller UE (UE-1) to UE-2. The SCC-AS-1 sends a SIP re-INVITE request to the UE-2, to transfer the audio media component.
Table A.11.4-22 SIP INVITE request (SCC AS-1 serving UE-1 to UE-2)
INVITE sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via: SIP/2.0/UDP sccas1.home1.example.net;branch=z9hG4bK332b33.3;
To: sip:user2_public1@home2.net;
From: sip:interUEtransfer@example.net;tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
Cseq: 111 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@example.net;+g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
a=sendonly
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
27-31. SIP 200 (OK) response (from UE-2 to SCC-AS-1 serving UE-1)
The target UE, UE-2, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC AS serving UE-1.
Table A.11.4-27 SIP 200 (OK) response (UE-2 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To: sip:user2_public1@home2.net; tag=36527
From: sip:interUEtransfer@example.net; tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
CSeq:
P-Preferred-Identity:
Contact: <sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.23.45.87
s=-
c=123.23.45.87
t=0 0
m=audio 1300 RTP/AVP 97
a=inactive
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
32-36. SIP ACK request (from SCC AS-1 serving UE-1 to UE-2)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the UE-2.
37-38. SIP re-INVITE request (from SCC AS-1 serving UE-1 to UE-1)
The SCC AS-1 serving UE-1 sends a SIP re-INVITE request to the UE-1 to hold the video media session to be transferred.
Table A.11.4-37 SIP INVITE request (SCC AS-1 serving UE-1 to UE-1)
INVITE sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via:
To: sip:user1_public1@home1.net;Tag=11928
From: sip:userR_public1@homeR.net; tag=27364
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@example.net;+g.3gpp.iut-focus
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
a=sendonly
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 0 RTP/AVP 98 99
39-40. SIP 200 (OK) response (from UE-1 to SCC AS serving UE-1)
The UE-1 sends a SIP 200 (OK) response with an SDP answer.
Table A.11.4-39 SIP 200 (OK) response (UE-1 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 1200 RTP/AVP 97
a=inactive
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 0 RTP/AVP 98 99
41-42. SIP ACK request (from SCC AS-1 serving UE-1 to UE-1)
The SCC AS serving UE-1 sends a SIP ACK request to the UE-1.
43-45. SIP re-INVITE request (from SCC AS-1 serving UE-1 to remote UE)
The SCC AS-1 serving UE-1 sends a SIP re-INVITE request to the remote UE.
Table A.11.4-45 SIP INVITE request (SCC AS-1 serving UE-1 to remote UE)
INVITE sip:userR_public1@homeR.net SIP/2.0
Via:
To: sip:userR_public1@homeR.net;tag=27364
From: sip:user1_public1@home1.net;tag=11928
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: <sip:interUEtransfer@example.net>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
t=0 0
m=audio 1300 RTP/AVP 96 97
c=IN IP4 123.112.67.87
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 1302 RTP/AVP 98 99
c=IN IP4 123.112.67.87
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
46-48. SIP 200 (OK) response (from Remote UE to SCC AS-1 serving UE-1)
The Remote UE acknowledges the SIP re-INVITE request by sending a SIP 200 (OK) response to the SCC AS-1 serving UE-1.
Table A.11.4-46 SIP 200 (OK) response (Remote UE to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Asserted-Identity:
Contact: sip:userR_public1@homeR.net
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
49-51. SIP ACK request (from SCC AS serving UE-1 to Remote UE)
The SCC-AS serving UE-1 sends a SIP ACK request to the Remote UE.
52-56. SIP re-INVITE request (from SCC AS serving UE-1 to UE-2)
The SCC AS serving UE-1 sends a SIP re-INVITE request to UE-2 to activate the video media component.
Table A.11.4-52 SIP INVITE request (SCC AS-1 serving UE-1 to UE-2)
INVITE sip:user2_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via: SIP/2.0/UDP sccas1.home1.example.net; branch=z9hG4bK332b33.3;
To: sip:user2_public1@home2.net; tag=36527
From: sip:interUEtransfer@example.net; tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
Cseq: 112 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@example.net;+g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
57-61. SIP 200 (OK) response (from UE-2 to SCC AS-1 serving UE-1)
The UE-2 sends a SIP 200 (OK) response to the SCC AS serving UE-1.
Table A.11.4-57 SIP 200 (OK) response (UE-2 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To: sip:user2_public1@home2.net; tag=36527
From: sip:interUEtransfer@example.net; tag=27365
Call-ID: cb03a0s09a2sdfglkj22222
CSeq:
P-Preferred-Identity:
Contact: <sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.23.45.87
s=-
c=123.23.45.87
t=0 0
m=audio 1300 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
62-66. SIP ACK request (from SCC AS-1 serving UE-1 to UE-2)
The SCC AS serving UE-1 sends a SIP ACK request to the UE-2.
67-68. SIP re-INVITE request (from SCC AS-1 serving UE-1 to UE-1)
The SCC-AS serving UE-1 sends a SIP re-INVITE request to the UE-1 to release the video media component.
Table A.11.4-67 SIP INVITE request (SCC AS-1 serving UE-1 to UE-1)
INVITE sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via:
To: sip:user1_public1@home1.net;Tag=11928
From: sip:userR_public1@homeR.net; tag=27364
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@example.net
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 0 RTP/AVP 98 99
69-70. SIP 200 (OK) response (from UE-1 to SCC AS-1 serving UE-1)
The UE-1 sends a SIP 200 (OK) response with an SDP answer.
Table A.11.4-69 SIP 200 (OK) response (UE-1 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 0 RTP/AVP 97
m=video 0 RTP/AVP 98 99
71-72. SIP ACK request (from SCC AS-1 serving UE-1 to UE-1)
The SCC AS serving UE-1 sends a SIP ACK request to the UE-1.
73-77. SIP NOTIFY request (from SCC AS-1 serving UE-1 to UE-2)
The SCC AS serving UE-1 sends a SIP NOTIFY request including the SIP final response as a sipfrag body to the UE-2 to inform about success status of transferring the media from UE-1 to the UE-2.
Table A.11.4-73: SIP NOTIFY request (SCC AS-1 serving UE-1 to UE-2)
NOTIFY sip:user2_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via:
To:sip:user2_public1@home2.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Event:refer
Subscription-State:terminated; reason=noresource
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 200 OK
Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111>; +g.3gpp.iut-controller
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
c=123.45.67.89
t=0 0
m=audio 0 RTP/AVP 97
m=video 0 RTP/AVP 98 99
78-82. SIP 200 (OK) response (from UE-2 to SCC AS-1 serving UE-1)
The UE-2 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS-1 serving UE-1.
A.11.5 Controllee UE initiated addition of media to another controllee UE
This subclause describes the scenario when controllee UE, UE-2 initiate addition of a media to another controllee UE, UE-3. The flow diagram shows when UE-1and UE-2, UE-3 belong to the different subscription.
Note: When UE-1and UE-2, UE-3 belong to the same subscription, Serving SCC AS of UE-1, UE-2 and UE-3 are same.
UE-1(123.45.67.89), UE-2 (123.112.67.87) and UE-3(123.23.45.67) are included in a Collaborative Session with the remote UE (132.54.76.98), in which UE-1 is the controller UE and UE-2 and UE-3 are the controllee UEs. The Collaborative Session is controlled by SCC AS-1. Media paths exist between UE-2 and remote UE (audio) and between UE-3 and remote UE (video). The UE-2(123.23.45.67) wants to add another media flow between UE-3 and remote UE (video).
Figure A.11.5-1: Signalling flow for controllee UE initiated addition of media to another controllee UE
1. UE-2 discovers the information of the collaborative session.
2-6. SIP REFER request (from UE-2 to UE-1)
The UE-2 sends SIP REFER request to the controller UE, UE-1 to request addition of media to UE-3. The SIP REFER request is finally routed to the SCC AS-1 serving UE-1.
Table A.11.5-2: SIP REFER request (UE-2 to UE-1)
REFER sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-111111111111 SIP/2.0
Via: SIP/2.0/UDP [3333::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7dfdsdq
To: <sip:user1_public1@home1.net>
From: <sip:user2_public1@home2.net>;tag=294756
Call-ID: Asdasd23123366
Cseq: 4897924 REFER
Max-Forwards: 70
P-Preferred-Identity: <sip:user2_public1@home2.net>;
Refer-To: <sip:user1_public3@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333?body= m%3Daudio%200%20RTP%2FAVP%97%0Dm%3Dvideo%203002%20RTP%2FAVP%2098%2099%3E m%3Dvideo%209%20RTP%2FAVP%2098%2099>
Referred-By: sip:user2_public1@home2.net
Target-dialog: cb03a0s09a2sdfglkj11111;remote-tag=27364;local-tag=11928
Contact: sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222
Referred-By: sip:user2_public1@home2.net
Accept: application/sdp, message/sipfrag
Content-Length: 0
7-11. SIP 200 (OK) response (from SCC AS-1 serving UE-1 to UE-2)
SCC AS-1 serving UE-1 sends a SIP 200 (OK) response to UE-2 as response to the SIP REFER request.
12-16. SIP NOTIFY request (from SCC AS-1 serving UE-1 to UE-2)
The SCC AS-1 serving UE-1 sends a SIP NOTIFY request to UE-2 to notify implicit subscription to the SIP REFER request results.
Table A.11.5-12: SIP NOTIFY request (SCC AS-1 serving UE-1 to UE-2)
NOTIFY sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via:
To:sip:user2_public1@home2.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net
Allow:
Event:refer
Subscription-State:active; expires=3600
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 100 Trying
17-21. SIP 200 (OK) response (from UE-2 to SCC AS-1 serving UE-1)
The UE-2 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS-1 serving UE-1.
22-26. SIP re-INVITE request (from SCC AS-1 serving UE-1 to UE-3)
Since the message 2-6 contains a Refer-to header field addressed to UE-3 and the URI parameters, listing an audio line which is not currently supported by UE-3, the SCC AS realizes the procedure is for adding the media to UE-3. The SCC AS-1 serving UE-1 sends a SIP re-INVITE request to the UE-3, to add the video media component.
Table A.11.5-22: SIP INVITE request (SCC AS-1 serving UE-1 to UE-3)
INVITE sip:user3_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333 SIP/2.0
Via: SIP/2.0/UDP sccas1.home1.net; branch=z9hG4bK332b33.3;
To: sip:user3_public1@home2.net;
From: sip:interUEtransfer@home.net; tag=12486
Call-ID: cb03a0s09a2sdfglkj33333
Cseq: 115 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=video 9 RTP/AVP 98 99
a=sendonly
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
27-31. SIP 200 (OK) response (from UE-3 to SCC AS-1 serving UE-1)
The target UE, UE-3, acknowledges the SIP re-INVITE request by sending a SIP 200 (OK) response to the SCC AS-1 serving UE-1.
Table A.11.5-27: SIP 200 (OK) response (UE-3 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To: sip:user3_public1@home2.net; tag = 24861
From: sip:interUEtransfer@home.net; tag = 12486
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user3_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.23.45.67
s=-
c=123.23.45.67
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=video 1304 RTP/AVP 98 99
a=recvonly
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
32-36. SIP ACK request (from SCC AS-1 serving UE-1 to UE-3)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the UE-3.
37-39. SIP re-INVITE request (from SCC AS-1 serving UE-1 to remote UE)
The SCC AS-1 serving UE-1 sends a SIP re-INVITE request to the remote UE.
Table A.11.5-37 SIP INVITE request (SCC AS-1 serving UE-1 to remote UE)
INVITE sip:user4_public1@home2.net SIP/2.0
Via:
To: sip:user4_public1@home2.net;tag=27364
From: sip:user1_public1@home1.net;tag=11928
Call-ID: cb03a0s09a2sdfglkj11111
CSeq:
Max-Forwards:
P-Asserted-Identity:
Require:
Contact: <sip:interUEtransfer@sccas1.home1.net>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.45.67.89
s=-
t=0 0
m=audio 1300 RTP/AVP 96 97
c=IN IP4 123.112.67.87
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 1302 RTP/AVP 98 99
c=IN IP4 123.23.45.67
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=video 1304 RTP/AVP 98 99
c=IN IP4 123.23.45.67
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
40-42. SIP 200 (OK) response (from remote UE to SCC AS-1 serving UE-1)
The remote UE acknowledges the SIP re-INVITE request by sending a SIP 200 (OK) response to the SCC AS -1 serving UE-1.
Table A.11.5-40: SIP 200 (OK) response (remote UE to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To:
From:
Call-ID:
CSeq:
P-Asserted-Identity:
Contact: sip:user4_public1@home2.net
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 3000 RTP/AVP 97
b=AS:25.4
a=rtpmap:96 AMR
a=fmtp:96 mode-set=0,2,5,7; mode-change-period=2
a=rtpmap:97 telephone-event
a=maxptime:20
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=video 3004 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
43-45. SIP ACK request (from SCC AS-1 serving UE-1 to remote UE)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the remote UE.
46-50. SIP re-INVITE request (from SCC AS-1 serving UE-1 to UE-3)
The SCC AS-1 serving UE-1 sends a SIP re-INVITE request to the controllee UE.
Table A.11.5-46: SIP INVITE request (SCC AS-1 serving UE-1 to UE-3)
INVITE sip:user3_public1@home2.net; gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333 SIP/2.0
Via: SIP/2.0/UDP sccas.home1.net; branch=z9hG4bK332b33.3;
To: sip:user3_public1@home2.net;
From: sip:interUEtransfer@sccas1.home1.net; tag=12486
Call-ID: cb03a0s09a2sdfglkj33333
Cseq: 111 INVITE
Max-Forwards: 70
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Accept:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 132.54.76.98
s=-
c=IN IP4 132.54.76.98
t=0 0
m=audio 0 RTP/AVP 97
m=video 3002 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=video 3004 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
51-55. SIP 200 (OK) response (from UE-3 to SCC AS-1 serving UE-1)
The UE-3 sends a SIP 200 (OK) response with an SDP answer.
Table A.11.5-51: SIP 200 (OK) response (UE-3 to SCC AS-1 serving UE-1)
SIP/2.0 200 OK
Via:
To: sip:user3_public1@home3.net; tag = 24861
From: sip:interUEtransfer@home.net; tag = 12486
Call-ID:
CSeq:
P-Preferred-Identity:
Contact: <sip:user3_public1@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333>
Allow:
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.23.45.67
s=-
c=123.23.45.67
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=video 1304 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
56-60. SIP ACK request (from SCC AS-1 serving UE-1 to UE-3)
The SCC AS-1 serving UE-1 sends a SIP ACK request to the UE-3.
61-65. SIP NOTIFY request (from SCC AS-1 serving UE-1 to UE-2)
The SCC AS-1 sends a SIP NOTIFY request including the SIP final response as a sipfrag body to UE-2 to inform about the success status of adding media to UE-3.
Table A.11.5-61: SIP NOTIFY request (SCC AS-1 serving UE-1 to UE-2)
NOTIFY sip:user2_public1@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-222222222222 SIP/2.0
Via:
To:sip:user2_public1@home2.net;tag=1234
From:sip: sip:interUEtransfer@sccas1.home1.net;tag=3456
Call-ID:
CSeq:
P-Asserted-Identity:
Require:
Contact: sip:interUEtransfer@sccas1.home1.net;+g.3gpp.iut-focus
Allow:
Event:refer
Subscription-State:terminated; reason=noresource
Content-Type: message/sipfrag; version=2.0
Content-Length: (…)
SIP/2.0 200 OK
Contact: <sip:user3_public1@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-1111-333333333333>
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 1027933615 1027933615 IN IP4 123.23.45.67
s=-
c=123.23.45.67
t=0 0
m=audio 0 RTP/AVP 97
m=video 1302 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
m=video 1304 RTP/AVP 98 99
b=AS:75
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
a=rtpmap:99 MP4V-ES
66-70. SIP 200 (OK) response (from UE-2 to SCC AS-1 serving UE-1)
The UE-2 acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS-1 serving UE-1.