A.7.5 Controllee UE modifies media on itself

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

Figure A.7.5: Controllee UE modifies media on itself

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

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 UE-2 with video (Media B) media flows. Subsequently, the UE-2 (Controllee UE) modifies the media B flow that is active on the remote UE.

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

UE-2 sends a SIP re-INVITE request towards the remote UE containing Media B using SDP offer.

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

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

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

Max-Forwards: 70

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

P-Asserted-Identity: "John Doe2" <sip:user1_public2@home1.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: user1_public@home1.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 4444::aaa:bbb:ccc:ddd

s=-

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

t=0 0

m=video 4444 RTP/AVP 98

a=rtpmap:98 MPV/90000

2. SIP re-INVITE request (intermediate IM CN subsystem entities to SCC AS)

The intermediate IM CN subsystem entities forward the SIP re-INVITE request to the SCC AS according to standard IMS procedure.

3. SIP re-INVITE request (SCC AS to intermediate IM CN subsystem entities) – see example in table A.7.5-3

The SCC AS sends a SIP re-INVITE request to the remote UE through the intermediate IM CN subsystem entities containing Media A and Media B information in SDP offer.

Table A.7.5-3: SIP re-INVITE request (SCC AS to intermediate IM CN subsystem entities)

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

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

Max-Forwards: 70

Route:

P-Asserted-Identity:

P-Access-Network-Info:

Privacy:

From:

To:

Call-ID:

Cseq:

Require:

Proxy-Require:

Supported:

Security-Verify:

Contact:

Allow:

Accept:

Content-Type:

Content-Length: (…)

v=0

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

s=-

t=0 0

m=audio 2222 RTP/AVP 97

c=IN IP6 3333::aaa:bbb:ccc:ddda=rtpmap:97 MPV/90000

m=video 4444 RTP/AVP 98

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

a=rtpmap:98 MPV/90000

4. SIP re-INVITE request (intermedia IM CN subsystem entities to remote UE)

5. SIP 200 (OK) response (remote UE to intermediate IM CN subsystem entities) – see example in table A.14.5-5

The remote EU sends a an SIP 200 (OK) response with SDP answer.

Table A.7.5-5: SIP 200 (OK) response (remote UE to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK240f26.3, SIP/2.0/UDP scscf2.home1.net;branch=z9hG4bK332d25.1, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332d25.2, SIP/2.0/UDP sccas1.home1.net;branch=z9hG4bK240a48.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 5555::aaa:bbb:ccc:ddd

s=-

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

t=0 0

m=audio 4444 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 6666 RTP/AVP 98

a=rtpmap:98 MPV/90000

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

7-8. SIP ACK request (SCC AS to the remote UE through intermediate IM CN subsystem entities)

The SCC AS sends an SIP ACK request to the remote UE through the intermediate IM CN subsystem entities.

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

The SCC AS sends a SIP 200 (OK) response containing Media B information and send it to UE-2 through the intermediate IM CN subsystem entities.

Table A.7.5-9 SIP 200 (OK) response (SCC AS to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via: SIP/2.0/UDP sccas1.home1.net;branch=z9hG4bK240f42.22,

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 5555::aaa:bbb:ccc:ddd

s=-

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

t=0 0

m=video 6666 RTP/AVP 98

a=rtpmap:98 MPV/90000

10. SIP 200 (OK) response (intermediate IM CN subsystem entities to UE-2)

11-12. SIP ACK request (UE-2 to SCC AS through intermediate IM CN subsystem entities)

UE-2 sends a SIP ACK request to the intermediate IM CN subsystem entities which is terminated by the SCC AS.