A.7.2 Controller UE releases media

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

A.7.2.1 Controller UE releases media flow on controller UE

Figure A.7.2.1: Controller UE releases media flow on controller UE

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-1 (controller UE) removes the media A flow that is active on the remote UE.

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

UE-1 sends a SIP re-INVITE request towards the remote UE indicating Media A is to be removed in the SDP offer.

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

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

Via:SIP/2.0/UDP [3333::eee:fff:aaa:bbb]: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 Doe" <sip:user1_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>;+g.3gpp.iut-controller

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

s=-

t=0 0

m=audio 0 RTP/AVP 97

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

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

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

a=rtpmap:98 MPV/90000

2. SIP re-INVITE request

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.14.2.1-3

The SCC AS sends a SIP re-INVITE request with all the media information at the remote UE, sets the port number for media A to 0, and forwards it towards the remote UE through the intermediate IM CN subsystem entities.

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

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

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

Max-Forwards: 70

Route: <sip:orig@scscf1.home1.net;lr>

P-Asserted-Identity: "John Doe" <sip:user1_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:

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

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

Content-Length: (…)

v=0

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

s=-

t=0 0

m=audio 0 RTP/AVP 97

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

a=rtpmap:97 MPV/90000

m=video 8888 RTP/AVP 98

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

a=rtpmap:98 MPV/90000

4. SIP re-INVITE request

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

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

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

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

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=dahtadfz4radgs.12, SIP/2.0/UDP scscf2.home1.net;branch=hsdfldf343.12, SIP/2.0/UDP scscf1.home1.net;branch=hsdfldf56322cc.13, SIP/2.0/UDP sccas1.home1.net;branch=z9hG4bKnas34r2.21

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

a=rtpmap:97 MPV/90000

m=video 6666 RTP/AVP 98

a=rtpmap:98 MPV/90000

6. SIP 200 (OK) response

7. SIP ACK request (SCC AS to intermediate IM CN subsystem entities)

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

8. SIP ACK request (intermediate IM CN subsystem entities to remote UE)

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

The SCC AS sends a SIP 200 (OK) response with an SDP answer indicating that Media-A has been removed

11-12. SIP ACK request (controller UE to SCC AS)

A.7.2.2 Controller UE releases media flow on controllee UE

A.7.2.2.1 Controller UE removes media at the controllee UE

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

Figure A.7.2.2.1:Controller UE remove media at the controllee UE

1-2. SIP REFER request (controller UE to intermediate IM CN subsystem entities) – see example in table A.14.2.1-1

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 a voice (Media A) and UE-2(Controllee UE) with a video (Media B) media flows and a voice (Media C) media flow. The controller UE wants to remove the video media (Media B) component on the controllee UE.

Table A.7.2.2.1-1 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 =13579

Call-ID: cb03a0s09a2sdfglkj490333

CSeq: 93809824 REFER

Max-Forwards: 70

P-Preferred-Identity: "John Doe" <sip:user1_public1@home1.net>

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

Require: target-dialog

Target-dialog: cb03a0s09a2sdfglkj13579;to-tag=abcdef;from-tag=123456

Referred-By: sip:user1_public1@home1.net

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

Allow:

Accept: message/sipfrag

Content-Length: 0

3-4. 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.

5-6. SIP NOTIFY request (SCC AS to UE-1 through intermediate IM CN subsystem entities)-see example in table A.7.2.1-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.2.2.1-5 SIP NOTIFY request (SCC AS to UE-1)

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

Via:

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

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

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

Allow:

Event: refer

Subscription-State: active;expires=3600

Content-Type: message/sipfrag ;version=2.0

Content-Length: (…)

SIP/2.0 100 Trying

7-8. 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 the SCC AS.

9-10. SIP UPDATE request (SCC AS to remote UE through intermediate IM CN subsystem entities) – see example in table A.7.2.2.2-9.

The SCC AS prepares the removal of the media component received by the controllee UE-2 and sent by the remote UE.

Table A.7.2.2.2-9: SIP UPDATE request (SCC AS to remote UE through intermediate IM CN subsystem entities)

UPDATE sip:userR_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a762-00a0c91e6bf6 SIP/2.0

Via:

To:

From:

Call-ID:

Cseq:

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

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

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

s=-

t=0 0

m=audio 6666 RTP/AVP 97

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

a=rtpmap:97 PCMU/8000

m=video 6668 RTP/AVP 98

a=sendonly

b=RR:0

b=RS:0

c=145.23.77.88

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 profile-level-id=0

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

Remote UE send a SIP 200 (OK) response with SDP answer.

Table A.7.2.2.2-11 SIP 200 (OK) response (remote UE to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via:

To:

From:

Call-ID:

Cseq:

Contact: <sip:userR_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a762-00a0c91e6bf6>

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

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

s=-

t=0 0

m=audio 4444 RTP/AVP 97

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

a=rtpmap:9777 PCMU/8000

m=video 6666 RTP/AVP 98

a=recvonly

b=RR:0

b=RS:0

c=145.23.77.88

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 profile-level-id=0

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

The SCC AS sends a SIP re-INVITE request towards the Controllee UE (UE-2).

Table A.7.2.2.1-13 SIP re-INVITE request (SCC-AS to IM CN subsystem entities)

INVITE sip:user2_public1@home1.net;gr=urn:uuid:f 81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

Route:

To: sip:user2_public1@home1.net;abcdef

From: sip:user3_public3@home3.net;tag=123456

Call-ID:

CSeq:

Max-Forwards:

Require:

Referred-By: sip:user1_public1@home1.net

Contact: sip:user3_public3@home3.net;gr=urn:uuid:f81d4fae-17oct-11a1-a678-0054c91eabcd

Allow:

Content-Type: application/sdp

Content-Length:(…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

m=audio 0 RTP/AVP 97

m=audio 4568 RTP/AVP 97

c=123.112.67.87

b=AS:75

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

a=rtpmap:98 MPV/90000

a=sendonly

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

15-16. SIP 200 (OK) response (UE-2 to SCC AS through intermediate IM CN subsystem entities)

17-18. SIP ACK request (from SCC-AS to UE-2)

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

The SCC AS sends a SIP re-INVITE request with all the media information at the remote UE, set the port number for media B to 0, and forwards it to the remote UE through the intermediate IM CN subsystem entities.

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

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

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

Max-Forwards: 70

Route: <sip:orig@scscf1.home1.net;lr>

P-Asserted-Identity: "John Doe" <sip:user1_public1@home1.net>

Privacy: none

From:

To:

Call-ID:

Cseq: 127 INVITE

Supported: 100rel, precondition

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

Content-Length:(..)

v=0

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

s=-

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

t=0 0

m=audio 6666 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=audio 4567 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

a=rtpmap:98 MPV/90000

20. SIP re-INVITE request (intermediate IM CN subsystem entities to remote UE)

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

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

Table A.7.2.2.1-21 SIP 200 (OK) (remote UE to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=343asdfaredfatz.12, SIP/2.0/UDP scscf2.home1.net;branch=fsc35avhthaz4.22, SIP/2.0/UDP scscf1.home1.net;branch=fsc35avhthaz4.12, SIP/2.0/UDP sccas1.home1.net;branch=z9hG4bKnas34r2.14

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:9777 PCMU/8000

m=audio 4545 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

a=rtpmap:98 MPV/90000

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

23-24. SIP ACK request (SCC AS to remote UE)

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

SCC AS sends a SIP re-INVITE request towards Controllee UE (UE-2).

NOTE: The SIP re-INVITE request is triggered by the SIP REFER request. The previous SIP INVITE request was generated by the SCC AS due to third party call cotrol to allow sending this SIP re-INVITE request.

Table A.7.2.2.1-25 SIP re-INVITE request (SCC-AS to UE-2)

INVITE sip:user2_public1@home1.net;gr=urn:uuid:f 81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

Route:

To: sip:user2_public1@home1.net;abcdef

From: sip:user3_public3@home3.net;tag=123456

Call-ID:

CSeq:

Max-Forwards:

Contact: sip:user3_public3@home3.net;gr=urn:uuid:f81d4fae-17oct-11a1-a678-0054c91eabcd

Allow:

Referred-By: sip:user1_public1@home1.net

Content-Type: application/sdp

Content-Length:(…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

m=audio 0 RTP/AVP 97

m=audio 4568 RTP/AVP 97

c=123.112.67.87

b=AS:75

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

27-28. SIP 200 (OK) response (UE-2 to SCC AS through intermediate IM CN subsystem entities)

29-30. SIP NOTIFY request (SCC-AS to UE-1)-see example table A.7.2.2.1-21

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

Table A.7.2-2.1-29 SIP NOTIFY request (SCC AS to UE-1)

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

Via:

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

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

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

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

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

a=rtpmap:98 MPV/90000

a=sendonly

31-32. SIP 200 OK response (UE-1 to SCC AS)

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

A.7.2.2.2 Controller UE remove the controllee UE from the collaborative session

Figure A.7.2.2.2:Controller UE remove the controllee UE from the collaborative session

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

1-2. SIP REFER request (controller UE to intermediate IM CN subsystem entities) – see example in table A.14.2.2.2-1

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 a voice (Media A) and UE-2(Controllee UE) with a video (Media B) media flow. The controller UE wants to remove the controllee UE from the collaborative session.

Table A.7.2.2.2-1 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 = 13579

Call-ID: cb03a0s09a2sdfglkj490333

CSeq: 93809824 REFER

Max-Forwards: 70

P-Preferred-Identity:

Refer-To: <sip:user2_public2@home2.net;gr=urn:uuid:f81d4fae-7dec-11d0-a762-00a0c91e6bf6;method=BYE>

Require: target-dialog

Target-dialog: cb03a0s09a2sdfglkj13579; to-tag=abcdef; from-tag=123456

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

Allow:

Referred-By: sip:user1_public1@home1.net

Accept:

Content-Type:

Content-Length:

3-4. 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.

5-6. SIP NOTIFY request (SCC AS to UE-1 through intermediate IM CN subsystem entities) – see example in table A.7.2.2.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.2.2.2-5 SIP NOTIFY request (SCC AS to UE-1)

NOTIFY

Via:

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

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

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

Allow:

Event: refer

Subscription-State: active;expires=3600

Content-Type: message/sipfrag ;version=2.0

Content-Length: (…)

SIP/2.0 100 Trying

7-8. 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) to the SCC AS.

9-10. SIP UPDATE request (SCC AS to remote UE through intermediate IM CN subsystem entities) – see example in table A.7.2.2.2-9.

The SCC AS prepares the removal of the controllee UE-2 from the collaborative session by stopping the media received by the controllee UE-2 and sent by the remote UE.

Table A.7.2.2.2-9: SIP UPDATE request (SCC AS to Remote UE through intermediate IM CN subsystem entities)

UPDATE sip:userR_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a762-00a0c91e6bf6 SIP/2.0

Via:

To:

From:

Call-ID:

Cseq:

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

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

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

s=-

t=0 0

m=audio 6666 RTP/AVP 97

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

a=rtpmap:97 PCMU/8000

m=video 6668 RTP/AVP 98

a=sendonly

b=RR:0

b=RS:0

c=145.23.77.88

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 profile-level-id=0

11-12. SIP 200 (OK) response (Remote UE to intermediate IM CN subsystem entities) – see example in table A.14.2.2.2-11.

Remote UE sends a SIP 200 (OK) response with SDP answer.

Table A.7.2.2.2-11 SIP 200 (OK) response (Remote UE to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

Via:

To:

From:

Call-ID:

Cseq:

Contact: <sip:userR_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a762-00a0c91e6bf6>

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

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

s=-

t=0 0

m=audio 4444 RTP/AVP 97

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

a=rtpmap:9777 PCMU/8000

m=video 6666 RTP/AVP 98

a=recvonly

b=RR:0

b=RS:0

c=145.23.77.88

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 profile-level-id=0

13-14. SIP BYE request (SCC AS to UE-2 through intermediate IM CN subsystem entities)

The SCC AS sends a SIP BYE request towards the controllee UE (UE-2).

15-16. SIP 200 (OK) response (UE-2 to SCC AS through intermediate IM CN subsystem entities)

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

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

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

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

Max-Forwards: 70

Route: <sip:orig@scscf1.home1.net;lr>

P-Asserted-Identity: "John Doe" <sip:user1_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-Length:0

v=0

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

s=-

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

t=0 0

m=audio 6666 RTP/AVP 97

a=rtpmap:97 PCMU/8000

m=video 0 RTP/AVP 98

a=rtpmap:98 MPV/90000

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

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

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

Table A.7.2.2.2-19 SIP 200 (OK) response (remote UE to intermediate IM CN subsystem entities)

SIP/2.0 200 OK

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:9777 PCMU/8000

m=video 0 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 request (SCC AS to remote party)

23-24. SIP NOTIFY request (SCC-AS to UE-1)-see example in table A.7.2.2.2-25

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

Table A.7.2.2.2-23 SIP NOTIFY request (SCC-AS to UE-1)

NOTIFY

Via:

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

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

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

Allow:

Event: refer

Subscription-State:terminated; reason=noresource

Content-Type: message/sipfrag ;version=2.0

Content-Length: (…)

SIP/2.0 200 OK

25-26. SIP 200 OK response (UE-1 to SCC-AS)

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