A.7.6 Remote UE adds new media on controllee UE

24.3373GPPIP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transferRelease 17Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

It is assumed that UE-1 is the controller UE having collaborative session control. A user has a multimedia session on his device UE‑1 with voice (Media A) and video (Media B) media flows. Subsequently, the remote UE adds the media B flow. In this scenario it is assumed that the controller UE, UE-1 automatically initiates the addition of the new media on UE-2 (Controllee) without first alerting the user and sends a SIP REFER request prior to sending back a SIP 200 (OK) response to the SIP re-INVITE request.

Figure A.7.6: Remote UE add new media on Controllee UE

NOTE 1: For clarity, the SIP 100 (Trying) responses are not shown in the signalling flow.

1. SIP re-INVITE request (remote UE to intermediate IM CN subsystem entities) – see example in table A.14.6-1

The remote UE sends a SIP re-INVITE request towards the controller UE (UE-1) indicating media B is to be added in SDP offer.

Table A.7.6-1: SIP re-INVITE request (remote UE to intermediate IM CN subsystem entities)

INVITE <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6> SIP/2.0

Via: SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7

Max-Forwards: 70

Route: <sip:pcscf2.visited2.net:7531;lr;comp=sigcomp>, <sip:orig@scscf2.home1.net;lr>

P-Asserted-Identity: "David Fan" <sip:user3_public3@home3.net>

P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11

Privacy: none

From:

To:

Call-ID:

Cseq: 127 INVITE

Require: sec-agree

Proxy-Require: sec-agree

Supported: 100rel, precondition

Security-Verify: ipsec-3gpp; q=0.1; alg=hmac-sha-1-96; spi-c=98765432; spi-s=87654321; port-c=8642; port-s=7531

Contact: <sip:user3_public3@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c67t6br4>

Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY

Accept: application/sdp, application/3gpp-ims+xml

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 2987933615 2987933615 IN IP6 5555::aaa:bbb:ccc:ddd

s=-

c=IN IP6 5555::aaa:bbb:ccc:ddd

t=0 0

m=audio 6666 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 4444 RTP/AVP 98

a=rtpmap:98 MPV/90000

2-4. SIP re-INVITE request

Intermediate IM CN subsystem entities forward the SIP re-INVITE request to UE-1 via the SCC AS according to standard IMS procedure.

5-6. SIP REFER request (UE-1 to SCC AS through intermediate IM CN subsystem entities) – see example in table A.7.6-5

The controller UE determines to add the new media (Media B) on the controllee UE. The controller UE, UE-1 sends a SIP REFER request to the SCC AS containing a Refer-To header field containing the GRUU of controllee UE, UE-2 and a body parameter containing an m line for audio set to 0 and an m line for video with the port number set to the port number of the video media line from the SDP offer in the SIP re-INVITE request 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 the controller UE, UE-1 and the remote UE.

Table A.7.6-5 SIP REFER request (UE-1 to SCC AS)

REFER sip:interUEtransfer@sccas1.home1.net SIP/2.0

Via:

To: sip:interUEtransfer@sccas1.home1.net

From: sip:user1_public1@home1.net;tag=34719

Call-ID: cb03a0s09a2sdfglkj490333

CSeq: 93809824 REFER

Max-Forwards: 70

P-Preferred-Identity:

Refer-To: <sip:user1_public2@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6?body=m%3Daudio%200%20RTP%2FAVP%2097%0Dm%3Dvideo%204444%20RTP%2FAVP%2098>

Require: target-dialog

Target-dialog: cb03a0s09a2sdfglkj490333;remote-tag=13579;local-tag=24680

Referred-By: sip:user1_public1@home1.net

Contact: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>;+g.3gpp.iut-controller

Allow:

Accept:message/sipfrag

Content-Length:0

7-8. SIP 200 (OK) response

The SCC-AS sends a SIP 200 (OK) response to the controller UE-1 as response to the SIP REFER request.

9-10. SIP NOTIFY request (SCC AS to UE-1 through intermediate IM CN subsystem entities)-see example in table A.7.3.2-5

The SCC AS sends a SIP NOTIFY request to UE-1 to notify implicit subscription to the SIP REFER request results.

Table A.7.3.2-5 SIP NOTIFY request (SCC-AS to UE-1)

NOTIFY sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

To: sip:user1_public1@home1.net;tag=34719

From: sip:interUEtransfer@sccas1.home1.net;tag=2255

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: <sip:user3_public3@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c67t6br4>

Allow:

Event: refer

Subscription-State: active;expires=3600

Content-Type: message/sipfrag;version=2.0

Content-Length: (…)

SIP/2.0 100 Trying

11-12. SIP 200 (OK) response (UE-1 to SCC-AS through intermediate IM CN subsystem entities)

The controller UE, UE-1, acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to SCC AS.

13-14. SIP 200 (OK) response (UE-1 to SCC-AS through intermediate IM CN subsystem entities)-see example in table A.7.6-13

The controller UE responds to the SIP re-INVITE request in step 4.

Table A.7.6-13: SIP 200 (OK) response (SCC AS to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.3, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP sccas1.home1.net;branch=z9hG4bKnas34r4.12

From:

To:

Call-ID:

Cseq: 127 INVITE

Supported: 100rel; precondition

Contact:

Allow:

Accept: application/sdp;

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 2987933300 2987933300 IN IP6 3333::aaa:bbb:ccc:ddd

s=-

c=IN IP6 3333::ccc:ddd:aaa:bbb

t=0 0

m=audio 8888 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

15-16. SIP ACK (SCC AS to UE-1 through intermediate IM CN subsystem entities)

17. SIP INVITE request (SCC AS to intermediate IM CN subsystem entities)-see example in table A.7.6-15

NOTE 2: This SIP INVITE request can be sent as soon as the SIP REFER request is received.

The SCC AS sends a SIP INVITE request towards UE-2 through the intermediate IM CN subsystem entities indicating Media B information in SDP offer.

Table A.7.6-17: SIP INVITE request (SCC AS to intermediate IM CN subsystem entities)

INVITE sip:user1_public2@home1.net;gr=urn:uuid:2ad8920e-48a5-4a74-8d99-ad76cc7fc74 SIP/2.0

Via: SIP/2.0/UDP sccas1.home1.net;branch=z9hG4bKnas34r2.12

Max-Forwards: 70

Route: <sip:term@scscf1.home1.net;lr>, <sip:pcscf1.visited1.net:7538;lr;comp=sigcomp>

P-Asserted-Identity: "John Doe" <sip:user3_public3@home3.net>

Privacy: none

From: <sip:user3_public3@home3.net>;tag=171828

To: <sip:user1_public2@home1.net>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 127 INVITE

Supported: 100rel, precondition

Referred-By: sip:user1_public1@home1.net

Contact: <sip:user3_public3@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c67t6br4>

Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY

Accept: application/sdp

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 2987933615 2987933615 IN IP6 5555::aaa:bbb:ccc:ddd

s=-

c=IN IP6 4444::bbb:aaa:ccc:ddd

t=0 0

m=audio 0 RTP/AVP 97

m=video 4444 RTP/AVP 98

a=rtpmap:98 MPV/90000

18. SIP INVITE request (intermediate IM CN subsystem entities to UE-2)

19. SIP 200 (OK) response (UE-2 to intermediate IM CN subsystem entities) – see example in table A.7.6-19

UE-2 responds with a SIP 200 (OK) response containing the SDP answer.

Table A.7.6-19: SIP 200 (OK) response (UE-2 to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.3, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP sccas1.home1.net;branch=z9hG4bKnas34r2.12

From:

To: <sip:user1_public2@home1.net>;tag=237674

Call-ID:

Cseq: 127 INVITE

Supported: 100rel; precondition

Contact: <sip:user1_public2@home1.net;gr=urn:uuid:2ad8920e-48a5-4a74-8d99-ad76cc7fc74>;+g.3gpp.icsi-ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"

Allow:

Accept: application/sdp;

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 2987933300 2987933300 IN IP6 4444::aaa:bbb:ccc:ddd

s=-

c=IN IP6 4444::aaa:bbb:ccc:ddd

t=0 0

m=audio 0 RTP/AVP 97

m=video 6666 RTP/AVP 98

a=rtpmap:98 MPV/90000

20. SIP 200 (OK) response (intermediate IM CN subsystem entities to SCC AS)

21-22. SIP ACK (SCC AS to UE-2 through intermediate IM CN subsystem entities)

23. SIP 200 (OK) response (SCC AS to intermediate IM CN subsystem entities) – see example in table A.7.6-23

In response to the SIP re-INVITE from the remote UE, the SCC AS sends a SIP 200 (OK) response containing the SDP answer towards the remote UE through IM CN subsystem entities, which includes Media A and Media B information.

Table A.7.6-23: SIP 200 (OK) response (SCC AS to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG6bKnas34r4, SIP/2.0/UDP scscf2.visited2.net;branch=34qtrada3333.22, SIP/2.0/UDP pcscf2.visited2.net;branch=34qtrada5454.12, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7

From:

To:

Call-ID:

Cseq: 127 INVITE

Supported: 100rel; precondition

Contact:

Allow:

Accept: application/sdp;

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 2987933300 2987933300 IN IP6 3333::aaa:bbb:ccc:ddd

s=-

t=0 0

m=audio 8888 RTP/AVP 97

c=IN IP6 3333::ccc:ddd:aaa:bbb

a=rtpmap:97 PCMU/8000

m=video 6666 RTP/AVP 98

c=IN IP6 4444::bbb:aaa:ccc:ddd

a=rtpmap:98 MPV/90000

24. SIP 200 (OK) response (intermediate IM CN subsystem entities to remote UE)

25-26. SIP ACK (remote UE to SCC AS through intermediate IM CN subsystem entities)

The remote UEsends a SIP ACK request to the intermediate IM CN subsystem entities which terminated by the SCC AS.

27-28. SIP NOTIFY request (from SCC AS to controller UE, UE-1)

The SCC AS sends a SIP NOTIFY request to the controller UE, UE-1 to inform about the success status if the inter-UE transfer.

Table A.7.6-27: SIP NOTIFY request (SCC AS to UE-1)

NOTIFY sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

To: sip:user1_public1@home1.net;tag=34719

From: sip:interUEtransfer@sccas1.home1.net;tag=2255

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: <sip:user3_public3@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c67t6br4>

Allow:

Event: refer

Subscription-State:terminated;reason=noresource

Content-Type: message/sipfrag;version=2.0

Content-Length: (…)

SIP/2.0 200 OK

Content-Type: application/sdp

v=0

s=-

m=audio 0 RTP/AVP 97

m=video 6666 RTP/AVP 98

29-30. SIP 200 (OK) response (from controller UE to SCC AS)

The controller UE acknowledges the SIP NOTIFY request by sending a SIP 200 (OK) response to the SCC AS.