A.7.7 Remote UE releases media on the controller UE

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

Figure A.7.7: Remote UE releases media on the controller UE

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

1. SIP re-INVITE request (Remote Party to intermediate IM CN subsystem entities) – see example in table A.14.7-1

The remote UE sends a SIP re-INVITE request towards the controller UE (UE-1) indicating Media A is to be removed using SDP offer. If Media B is to be removed, the SIP re-INVITE request will send to controllee UE (UE-2).

Table A.7.7-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:userR_public1@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 5555::aaa:bbb:ccc:ddd

s=-

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

t=0 0

m=audio 0 RTP/AVP 97

a=rtpmap:97 PCMU/8000

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 re-INVITE request to the SCC AS according to standard IMS procedures.

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

The media B is not removed, but the SCC AS set the port of the media B to 0, and forwards it towards intermediate IM CN subsystem entities.

Table A.7.7-3: SIP INVITE request (SCC AS 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 sccas1.home1.net;branch=z9hG4bKnas34r4.12

Max-Forwards: 70

Route: <sip:term@scscf2.home1.net;lr>

P-Asserted-Identity:

P-Access-Network-Info:

Privacy:

From:

To:

Call-ID:

Cseq:

Supported:

Require:

Proxy-Require:

Security-Verify:

Contact:

Allow:

Accept:

Content-Type:

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 0 RTP/AVP 97

a=rtpmap: 97 PCMU/8000

m=video 0 RTP/AVP 98

a=rtpmap:98 MPV/90000

4. SIP re-INVITE request (intermediate IM CN subsystem entities to UE-1)

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

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

UE-1 sends a SIP 200 (OK) response with an SDP answer.

Table A.7.7-5: SIP 200 (OK) response (UE-1 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: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>;+g.3gpp.iut-controller

Allow:

Accept: application/sdp;

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 2987933300 2987933300 IN IP6 3333::eee:fff:aaa:bbb

s=-

c=IN IP6 3333::eee:fff:aaa:bbb

t=0 0

m=audio 0 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 0 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 (SCC AS to UE-1 through intermediate IM CN subsystem entities)

The SCC AS sends a SIP ACK request to the controller 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.7-9

The SCC AS sends a SIP 200 (OK) response with an SDP answer indicating Media A is removed to the intermediate IM CN subsystem entities

Table A.7.7-9: 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 scsf2.visited2.net;branch=3q5qefsdr62233.22, SIP/2.0/UDP pcscf2.visited2.net;branch=3q5qefsdr62245.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: <sip:user1_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>;+g.3gpp.iut-controller

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

t=0 0

m=audio 0 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 6666 RTP/AVP 98

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

a=rtpmap:98 MPV/90000

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

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

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