A.5 Signalling flows for media transfer within collaborative session for inter-UE transfer

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.5.1 Introduction

This subclause describes signalling flows for media transfer within collaborative sessions. Two different scenarios are considered in the clause:

– subclause A.5.2 shows an example where a media component is transferred from the controller UE to the controllee UE; and

– subclause A.5.3 shows an example where a media component is transferred from one controllee UE to another controllee UE.

A.5.2 Controller UE initiated media transfer from controller UE to controllee UE

Figure A.5.2: Controller UE transfers a media on controllee UE

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

1-2. SIP REFER request (SIP REFER request from UE-1 to SCC-AS)

There is an existing session with audio1 and video between the controller UE, UE-1 (123.45.67.89), and the remote UE (132.54.76.98). There is another audio2 component between the controllee UE, UE-2 (145.23.77.88), and the remote UE. The video component is bidirectional from the remote UE to the controller UE, UE-1. The Controller UE attempts to transfer the video portion of this session to the controllee UE, UE-2.

Table A.5.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:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6?body= m%3Daudio%200%20RTP%2FAVP%2097%0Dm%3Daudio%203004%20RTP%2FAVP%2097%0Dm%3Dvideo%203002%20RTP%2FAVP%2098%2099>

Require: target-dialog

Target-dialog: cb03a0s09a2sdfglkj321576;remote-tag=abcdef;local-tag=123456

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

Referred-By: sip:user1_public1@home1.net

Accept: application/sdp, message/sipfrag

Content-Length: 0

3-4. SIP 200 (OK) response (from SCC AS to UE-1)

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 (from SCC AS to UE-1)

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

Table A.5.2-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=24680

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

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 (from UE-1 AS to SCC-AS)

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

9-10. SIP re-INVITE request (from SCC-AS to UE-2)

The SCC-AS sends a SIP re-INVITE request to the controllee UE, UE-2, to transfer video media. In order to avoid UE-2 to start sending video to the remote UE, the SCC-AS adds an a-line set to sendonly and b-lines to set the bandwidth to 0 in the SDP offer.

Table A.5.2-9 SIP INVITE request (SCC-AS to UE-2)

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

Via:

To: sip:user1_public2@home1.net;

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

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Referred-By: sip:user1_public1@home1.net

Contact:

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=audio 3004 RTP/AVP 96 97

a=rtpmap :0 PCMU/8000

b=RR :0

b=RS :0

m=video 3002 RTP/AVP 98 99

a=sendonly

b=RR:0

b=RS:0

b=AS:75

a=rtpmap:98 H263

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

a=rtpmap:99 MP4V-ES

11-12. SIP 200 (OK) response (from UE-2 to SCC-AS)

The controllee UE, UE-2, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.2-11 SIP 200 OK response (UE-2 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public2@home1.net; tag = xyzwv

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

Call-ID:

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 145.23.77.88

s=-

c=145.23.77.88

t=0 0

m=audio 0 RTP/AVP 97

m=audio 1304 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

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

13-14. SIP ACK request (from SCC-AS to UE-2)

The SCC-AS sends a SIP ACK request to the controllee UE, UE-2.

15-16. SIP re-INVITE request (from SCC-AS to UE-1)

The SCC-AS sends a SIP re-INVITE request to the controller UE, UE-1.

Table A.5.2-15 SIP INVITE request (SCC-AS to UE-1)

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

Via:

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

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

Call-ID: cb03a0s09a2sdfglkj11111

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

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 96 97

m=audio 3000 RTP/AVP 96 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

a=sendonly

a=rtpmap:98 H263

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

a=rtpmap:99 MP4V-ES

17-18. SIP 200 (OK) response (from UE-1 to SCC-AS)

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

Table A.5.2-17 SIP 200 (OK) response (UE-1 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user3_public3@home3.net;tag = 27364

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

Call-ID: cb03a0s09a2sdfglkj11111

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 145.23.77.88

s=-

c=145.23.77.88

t=0 0

m=audio 0 RTP/AVP 96 97

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

a=recvonly

19-20. SIP ACK request (from SCC-AS to UE-1)

The SCC-AS sends a SIP ACK request to the controller UE, UE-1, in response to the SIP 200 (OK) response.

21-22. 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.5.2-21 SIP INVITE request (SCC-AS to remote UE)

INVITE sip:user3_public3@home3.net SIP/2.0

Via:

To: sip:user3_public3@home3.net;tag = 66666

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

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

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

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=audio 1304 RTP/AVP 96 97

c=IN IP4 145.23.77.88

b=AS:25.4

a=rtpmap:94 AMR

a=fmtp:94 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:95 telephone-event

a=maxptime:20

m=video 1302 RTP/AVP 98 99

c=IN IP4 145.23.77.88

b=AS:75

a=rtpmap:98 H263

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

a=rtpmap:99 MP4V-ES

23-24. 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.5.2-23 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:user3_public3@home3.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 96 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=audio 3004 RTP/AVP 96 97

b=AS:25.4

a=rtpmap:94 AMR

a=fmtp:94 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:95 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

25-26. SIP ACK request (from SCC-AS to remote UE)

The SCC-AS sends a SIP ACK request to the remote UE.

27-28. SIP re-INVITE request (from SCC-AS to UE-1)

The SCC-AS sends a SIP re-INVITE request to the controller UE, UE-1.

Table A.5.2-27 SIP INVITE request (SCC-AS to UE-1)

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

Via:

To:

From:

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

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

m=video 0 RTP/AVP 98 99

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

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

31-32. SIP ACK request (from SCC-AS to UE-1)

The SCC-AS sends a SIP ACK request to the controller UE, UE-1, in response to the SIP 200 (OK) response.

33-34. SIP re-INVITE request (from SCC-AS to UE-2)

The SCC-AS sends a SIP re-INVITE request to the controllee UE, UE-2, to activate the video media components.

Table A.5.2-33 SIP INVITE request (SCC-AS to UE-2)

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

Via:

To: sip:user1_public2@home1.net;

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

Call-ID: cb03a0s09a2sdfglkj22222

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Referred-By: sip:user1_public1@home1.net

Contact:

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=audio 3004 RTP/AVP 96 97

b=AS:25.4

a=rtpmap:94 AMR

a=fmtp:94 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:95 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

a=sendrecv

35-36. SIP 200 (OK) response (from UE-2 to SCC-AS)

The controllee UE, UE-2, acknowledges the SIP re-INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.2-35 SIP 200 (OK) response (UE-2 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public2@home1.net; tag = 27365

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

Call-ID: cb03a0s09a2sdfglkj22222

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 145.23.77.88

s=-

c=145.23.77.88

t=0 0

m=audio 0 RTP/AVP 97

m=audio 1304 RTP/AVP 96 97

c=IN IP4 145.23.77.88

b=AS:25.4

a=rtpmap:94 AMR

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

a=rtpmap:95 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

37-38. SIP ACK request (from SCC-AS to UE-2)

The SCC-AS sends a SIP ACK request to the controllee UE, UE-2, in response to the SIP 200 (OK) response.

39-40. SIP NOTIFY request (from SCC-AS to conroller UE, UE-1)

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.5.2-39 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=24680

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

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

o=- 1027933615 1027933615 IN IP4 145.23.77.88

s=-

c=145.23.77.88

t=0 0

m=audio 0 RTP/AVP 97

m=audio 1304 RTP/AVP 96 97

c=IN IP4 145.23.77.88

b=AS:25.4

a=rtpmap:94 AMR

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

a=rtpmap:95 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

41-42. SIP 200 (OK) response (from – 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.5.3 Controller UE initiated media transfer from controllee UE to another controllee UE with subscription to dialog events

The signalling flow in figure A.5.3 describes the procedures for media transfer from one controllee UE to another controllee UE with persistent subscription to dialog events.

NOTE 1: For brevity not all SIP NOTIFY requests sent as a result of the subscription to the dialog event package are shown.

Figure A.5.3: Controller UE transfers a media from one controllee UE to another controllee UE

1-2. SIP SUBSCRIBE request (from controller UE to SCC-AS) – see example in table A.5.3-1

In order that the controller UE fetches the information about the session descriptions of the UEs within the collaborative session, the controller UE subscribes to the existing dialog between the controller UE and the SCC AS.

Table A.5.3-1 SIP SUBSCRIBE request (controller UE to SCC-AS)

SUBSCRIBE sip:scc-as@home1.net SIP/2.0

Via:

To: sip:scc-as@home1.net; tag= 24680

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

Event: dialog; call-id=" cb03a0s09a2sdfglkj321576"; from-tag="54321"; to-tag="123456"; include-session-description

Call-ID: cb03a0s09a2sdfglkj490333

CSeq: 1 SUBSCRIBE

Max-Forwards: 70

P-Preferred-Identity:

Require: target-dialog

Expires: 3600

Target-dialog: cb03a0s09a2sdfglkj321576;remote-tag=abcdef;local-tag=123456

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

CSeq:

Allow:

Accept: application/dialog-info+xml

Content-Length: 0

3-4. SIP 200 (OK) response (from SCC-AS to controller UE)

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

5-6. SIP NOTIFY request (from SCC-AS to controller UE) – see example in table A.5.3-5

The SCC AS sends a SIP NOTIFY request containing SDP for the remote UE so that the controller UE has the current state of the media for the collaborative session.

Table A.5.3-5 SIP NOTIFY request (SCC-AS to controller UE)

NOTIFY sip:user1_public1@home1.net SIP/2.0

Via:

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

From: sip:scc-as@home1.net; tag= 24680

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

Allow:

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: (…)

<?xml version="1.0"?>

<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"

version="0"

state="full"

entity="sip:scc-as@home1.net">

<state>confirmed</state>

<local>

<identity display="controllee UE">sip:user2_public1@home1.net</identity>

<target>sip:user2_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6</target>

<session-description type="application/sdp">

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

m=audio 49174 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=audio 44552 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 1009 RTP/AVP 98 99

c=IN IP4 123.112.67.87

a=sendonly

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 H263

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

a=rtpmap:99 MP4V-ES

</session-description>

</local>

<target>sip:user2_public1@home2.net;gr=urn:uuid:2ad8950e-48a5-4a74-8d99-ad76cc7fc74</target>

<session-description type="application/sdp">

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

m=audio 49174 RTP/AVP 96 97

c= IN IP4 132.54.76.98

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

m=audio 44552 RTP/AVP 96 97

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

c= IN IP4 132.54.76.98

m=video 1009 RTP/AVP 98 99

c= IN IP4 132.54.76.98

a=sendonly

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 H263

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

a=rtpmap:99 MP4V-ES

</session-description>

</remote>

</dialog>

</dialog-info>

7-8. SIP 200 (OK) response (from controller UE-1 to SCC-AS)

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

9-10. SIP REFER request (from controller UE-1 to SCC-AS) – see example in table A.5.3-9

There is an existing session with audio 1 and audio 2 between UE-2 (123.45.67.89) and the remote UE (132.54.76.98). The video component is unidirectional from the remote UE to the controllee UE, UE-3 (123.112.67.87). The controller UE-1 attempts to transfer the audio 1 portion of this session to the controllee UE, UE-3.

Table A.5.3-9 SIP REFER request (UE-1 to SCC-AS)

REFER sip:scc-as@home1.net SIP/2.0

Via:

To: sip:scc-as@home1.net; tag= 24680

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

Call-ID: cb03a0s09a2sdfglkj490333

CSeq: 93809824 REFER

Max-Forwards: 70

P-Preferred-Identity: sip:user1_public1@home1.net

Refer-To: <sip:user1_public3@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6body=m%3Daudio%200%20RTP%2FAVP%200%0Dm%3Daudio%20 49174%20RTP%2FAVP%2096%0Dm%3Dvideo%201009%20RTP%2FAVP%2098%2099>

Require: target-dialog

Target-dialog: cb03a0s09a2sdfglkj321576;remote-tag=abcdef;local-tag=123456

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

Referred-By: sip:user1_public1@home1.net

Accept: message/sipfrag

Content-Length: 0

11-12. SIP 200 (OK) response (from SCC AS to UE-1)

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

13-14. SIP NOTIFY request (from SCC AS to UE-1) – see example in table A.6.3-13

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

Table A.5.3-13 SIP NOTIFY request (SCC-AS to UE-1)

NOTIFY

Via:

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

From: sip:scc-as@home1.net;tag=13579

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

15-16. SIP 200 (OK) response (from UE-1 AS to SCC-AS)

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

17-18. SIP INVITE request (from SCC-AS to UE-3) – see example in table A.5.3-17

Since the message 9-10 contains a Refer-to header field addressed to UE-3 and the URI paramaters, listing an audio line which is not currently supported by another controllee UE than UE-2, the SCC AS realizes the procedure is for transferring the media from that controllee UE (UE-2) to controllee UE (UE-3). The SCC-AS sends a SIP INVITE request to the controllee UE, UE-3, to transfer the audio media component. The SDP in the SIP INVITE request lists the media lines within the collaborative session. In order to avoid UE-3 to start sending audio to the remote UE, the SCC-AS adds an a-line set to sendonly in the SDP offer.

Table A.5.3-17 SIP INVITE request (SCC-AS to UE-3)

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

Via:

To: sip:user1_public3@home1.net;

From: sip:scc-as@home1.net; tag=12486

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

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

a=rtpmap:0 PCMU/8000

a= sendonly

b=RR:0

b=RS:0m=audio 0 RTP/AVP 0

m=video 1009 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

19-20. SIP 200 (OK) response (from UE-3 to SCC-AS) – see example in table A.5.3-19

The controllee UE, UE-3, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.3-19 SIP 200 (OK) response (UE-3 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public3@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public3@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

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

a=rtpmap:0 PCMU/8000

a=recvonly

m=audio 0 RTP/AVP 0

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

21-22. SIP ACK request (from SCC-AS to UE-3)

The SCC-AS sends a SIP ACK request to UE-3 to acknowlege.

23-24. SIP re-INVITE request (from SCC-AS to controllee UE, UE-2) – see example in table A.5.3-23

The SCC AS sends a SIP re-INVITE request to controllee UE, UE-2 to put Audio 1 on hold.

Table A.5.3-23 SIP INVITE request (SCC-AS to UE-2)

INVITE sip:user1_public2@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

To: sip:user1_public2@home1.net;

From: sip:scc-as@home1.net; tag=12386

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

c=IN IP4 123.112.67.87

t=0 0

m=audio 49174 RTP/AVP 96 97

a=sendonly

b=RR:0

b=RS:0

m=audio 44552 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

a=sendonly

b=RR:0

25-26. SIP 200 (OK) response (from UE-2 to SCC-AS) – see example in table A.5.3-25

The controllee UE, UE-2, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.3-25 SIP 200 (OK) response (UE-2 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public2@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.45.67.89

s=-

c=IN IP4 123.45.67.89

t=0 0

m=audio 32324 RTP/AVP 96 97

a=recvonly

m=audio 34002 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

a=recvonly

27-28. SIP ACK request (from SCC-AS to UE-2 )

The SCC –AS sends a SIP ACK request to UE-2 to acknowlege.

29-30 SIP re-INVITE request (from SCC-AS to remote UE) – see example in table A.5.3-29

The SCC-AS sends a SIP re-INVITE request to the remote UE.

Table A.5.3-29 SIP INVITE request (SCC-AS to remote UE)

INVITE sip:user2_public1@home3.net;SIP/2.0

Via:

To: sip:user2_public1@home2.net;tag=66666

From: sip:scc-as@home1.net; tag=33333

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

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

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

m=audio 3002 RTP/AVP 96 97

c= IN IP4 123.112.67.87

a=rtpmap:0 PCMU/8000

m=audio 34002 RTP/AVP 96 97

C=IN IP4 123.45.67.89

A=rtpmap:0 PCMU/8000

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

a=recvonly

31-32. SIP 200 (OK) response (from remote UE to SCC-AS) – see example in table A.5.3-31

The remote UE acknowledges the SIP re-INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.3-31 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:user2_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 49174 RTP/AVP 96 97

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

m=audio 44552 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

m=video 1009 RTP/AVP 98 99

a=sendonly

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 H263

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

a=rtpmap:99 MP4V-ES

a=sendonly

33-34. SIP ACK request (from SCC-AS to remote UE)

The SCC-AS sends a SIP ACK request to the remote UE.

35-36. SIP NOTIFY request (from SCC-AS to controller UE) – see example in table A.5.3-35

The SCC AS sends a SIP NOTIFY request containing SDP for the remote UE so that the controller UE can be aware about the change of state of the media for the collaborative session.

Table A.5.3-35 SIP NOTIFY request (SCC-AS to controller UE)

NOTIFY sip:user1_public1@home1.net;

Via:

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

From: sip:scc-as@home1.net; tag= 24680

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

Allow:

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: (…)

<?xml version="1.0"?>

<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"

version="1"

state="full"

entity="sip:scc-as@home1.net">

<state>confirmed</state>

<local>

<identity display="controllee UE">sip:user2_public1@home1.net</identity>

<target>sip:user2_public1@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6</target>

<session-description type="application/sdp">

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

m=audio 49174 RTP/AVP 96 97

c=IN IP4 123.45.67.89

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

m=audio 44552 RTP/AVP 96 97

c=IN IP4 123.45.67.89

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

m=video 1009 RTP/AVP 98 99

c=IN IP4 123.112.67.87

a=sendonly

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 H263

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

a=rtpmap:99 MP4V-ES

</session-description>

</local>

<target>sip:user2_public1@home2.net;gr=urn:uuid:2ad8950e-48a5-4a74-8d99-ad76cc7fc74</target>

<session-description type="application/sdp">

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

c= IN IP4 132.54.76.98

m=audio 49174 RTP/AVP 96 97

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

m=audio 44552 RTP/AVP 96 97

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

m=video 1009 RTP/AVP 98 99

a=sendonly

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 H263

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

a=rtpmap:99 MP4V-ES

</session-description>

</remote>

</dialog>

</dialog-info>

37-38. SIP 200 (OK) response (from controller UE-1 to SCC-AS)

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

39-40. SIP re-INVITE request (from SCC-AS to controllee UE, UE-2) – see example in table A.5.3-39

The SCC-AS sends a SIP re-INVITE request to UE-2 to remove the audio 1 media component.

Table A.5.3-39 SIP INVITE request (SCC-AS to UE-2)

INVITE sip:user1_public2@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

To: sip:user1_public2@home1.net;

From: sip:scc-as@home1.net; tag=12386

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

c=IN IP4 123.112.67.87

t=0 0

m=audio 0 RTP/AVP 0

m=audio 44552 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

41-42. SIP 200 (OK) response (from UE-2 to SCC-AS) – see example in table A.5.3-41

The controllee UE, UE-2, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.3-41 SIP 200 (OK) response (UE-2 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public2@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.45.67.89

s=-

c=IN IP4 123.45.67.89

t=0 0

m=audio 0 RTP/AVP 0

m=audio 34002 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

43-44. SIP ACK request (from SCC-AS to UE-2)

The SCC –AS sends a SIP ACK request to UE-2 to acknowlege.

45-46. SIP re_INVITE request (from SCC-AS to controllee UE; UE-3) – see example in table A.5.3-45

The SCC-AS sends a SIP re_INVITE request to UE-3 to activate the audio 1 media component.

Table A.5.3-45 SIP re-INVITE request (SCC-AS to UE-3)

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

Via:

To: sip:user1_public3@home1.net;

From: sip:scc-as@home1.net; tag=12486

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Referred-By: sip:user1_public1@home1.net

Contact:

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

c=IN IP4 123.112.67.87

t=0 0

m=audio 49174 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

a= sendrecv

m=audio 0 RTP/AVP 0

m=video 1009 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

NOTE 2: This 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 control to allow sending this SIP re-INVITE request.

47-48. SIP 200 (OK) response (from controllee UE; UE-3 to SCC AS)

Controllee UE, UE-3 sends a SIP 200 (OK) response to the SCC AS.

49-50. SIP ACK request (from SCC-AS to UE-3)

The SCC-AS sends a SIP ACK request to the controllee UE, UE-3.

51-52. SIP NOTIFY request (from SCC-AS to controller UE) – see example in table A.5.3-51

The SCC AS sends a SIP NOTIFY request containing SDP of the SIP 200 (OK) response received from the controllee UE, UE-3.

Table A.5.3-51 SIP NOTIFY request (SCC-AS to controller UE)

NOTIFY sip:user1_public1@home1.net;

Via:

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

From: sip:scc-as@home1.net; tag= 24680

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

Allow:

Event: refer

Content-Type: message/sipfrag ;version=2.0 ;

Content-Length: (…)

SIP/2.0 200 OK

To: sip:user1_public3@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

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

a=rtpmap:0 PCMU/8000

m=audio 0 RTP/AVP 0

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

53-54. 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.

A.5.4 Controller UE initiated media transfer from controllee UE to another controllee UE

The signalling flow in figure A.5.4 describes the procedures for media transfer from one controllee UE to another controllee UE.

Figure A.5.3A: Controller UE transfers a media from one controllee UE to another controllee UE.

1-2. SIP REFER request (SIP REFER request from UE-1 to SCC-AS)

There is an existing session with audio 1 and audio 2 between UE-2 (123.45.67.89) and the remote UE (132.54.76.98). The video component is unidirectional from the remote UE to the controllee UE, UE-3 (123.112.67.87). The Controller UE attempts to transfer the audio 1 portion of this session to the controllee UE, UE-3.

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

REFER sip:scc-as@home1.net SIP/2.0

Via:

To: sip:scc-as@home1.net; tag= 24680

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

Call-ID: cb03a0s09a2sdfglkj490333

CSeq: 93809824 REFER

Max-Forwards: 70

P-Preferred-Identity: sip:user1_public1@home1.net

Require: target-dialog

Target-dialog: cb03a0s09a2sdfglkj321576;remote-tag=abcdef;local-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

Accept: message/sipfrag

Content-Length: 0

3-4. SIP 200 (OK) response (from SCC AS to UE-1)

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

5-6. SIP NOTIFY request (from SCC AS to UE-1)

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

Table A.5.3A-2 SIP NOTIFY request (SCC-AS to UE-1)

NOTIFY

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

From: sip:scc-as@home1.net;tag=13579

Call-ID: cb03a0s09a2sdfglkj12345

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 (from controller 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.

9-10. SIP INVITE request (from SCC-AS to UE-3)

Since the message 1-2 contains a Refer-to header field addressed to UE-3 and the URI paramaters, listing an audio line which is not currently supported by another controllee UE than UE-2, the SCC AS realizes the procedure is for transferring the media from that controllee UE (UE-2) to controllee UE (UE-3). The SCC-AS sends a SIP INVITE request to the controllee UE, UE-3, to transfer the audio media component. The SDP in the SIP INVITE request lists the media lines within the collaborative session. In order to avoid UE-3 to start sending audio to the remote UE, the SCC-AS adds an a-line set to sendonly in the SDP offer.

Table A.5.3A-3 SIP INVITE request (SCC-AS to UE-3)

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

Via:

To: sip:user1_public3@home1.net;

From: sip:scc-as@home1.net; tag=12486

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

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

a=rtpmap:0 PCMU/8000

a= sendonly

b=RR:0

b=RS:0m=audio 0 RTP/AVP 0

m=video 1009 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

11-12. SIP 200 (OK) response (from UE-3 to SCC-AS)

The controllee UE, UE-3, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.3A-4 SIP 200 (OK) request (UE-3 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public3@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public3@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

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

a=rtpmap:0 PCMU/8000

a=recvonly

m=audio 0 RTP/AVP 0

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

13-14. SIP ACK request(from SCC-AS to UE-3)

The SCC-AS sends a SIP ACK request to UE-3 to acknowledge.

15-16. SIP re-INVITE request (from SCC-AS to controllee UE, UE-2)

The SCC AS sends a SIP re-INVITE request to controllee UE, UE-2 to put Audio 1 on hold.

Table A.5.3A-5 SIP INVITE request (SCC-AS to controllee UE, UE-2)

INVITE sip:user1_public2@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

To: sip:user1_public2@home1.net;

From: sip:scc-as@home1.net; tag=12386

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

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

a=sendonly

b=RR:0

b=RS:0

m=audio 44552 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

a=sendonly

b=RR:0

17-18. SIP 200 (OK) response (from UE-2 to SCC-AS)

The controllee UE, UE-2 acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.3A-6 SIP 200 (OK) response (UE-2 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public2@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.45.67.89

s=-

c=IN IP4 123.45.67.89

t=0 0

m=audio 32324 RTP/AVP 96 97

a=recvonly

m=audio 34002 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

a=recvonly

19-20. SIP ACK request (from SCC-AS to UE-2)

The SCC-AS sends a SIP ACK request to UE-2 to acknowledge.

21-22. SIP re-INVITE request (from SCC-AS to remote UE)

The SCC-AS sends a SIP re-INVITE request to the remote UE, UE-4.

Table A.5.3A-7 SIP INVITE request (SCC-AS to remote UE, UE-4)

INVITE sip:user2_public1@home3.net;SIP/2.0

Via:

To: sip:user2_public1@home2.net;tag=66666

From: sip:scc-as@home1.net; tag=33333

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

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

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

t=0 0

m=audio 3002 RTP/AVP 96 97

c= IN IP4 123.112.67.87

a=rtpmap:0 PCMU/8000

m=audio 34002 RTP/AVP 96 97

C=IN IP4 123.45.67.89

A=rtpmap:0 PCMU/8000

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

a=recvonly

23-24. SIP 200 (OK) response (from remote UE, UE-4 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.5.3A-8 SIP 200 (OK) request (UE-4 to SCC-AS)

SIP/2.0 200 OK

Via:

To:

From:

Call-ID:

CSeq:

P-Asserted-Identity:

Contact: sip:user2_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 49174 RTP/AVP 96 97

b=AS:25.4

a=rtpmap:96 AMR

a=fmtp:96mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime:20

m=audio 44552 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

m=video 1009 RTP/AVP 98 99

a=sendonly

b=AS:75

a=rtpmap:98 H263

a=fmtp:98 H263

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

a=rtpmap:99 MP4V-ES

a=sendonly

25-26. SIP ACK request (from SCC-AS to remote UE)

The SCC-AS sends a SIP ACK request to the remote UE.

27-28. SIP re-INVITE request (from SCC-AS to controllee UE, UE-2)

The SCC-AS sends a SIP re-INVITE request to UE-2 to remove the audio 1 media component.

Table A.5.3A-9 SIP re-INVITE request (SCC-AS to UE-2)

INVITE sip:user1_public2@home3.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 SIP/2.0

Via:

To: sip:user1_public2@home1.net;

From: sip:scc-as@home1.net; tag=12386

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact:

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 0

m=audio 44552 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

29-30, SIP 200 (OK) response (from UE-2 to SCC-AS)

The controllee UE, UE-2, acknowledges the SIP INVITE request by sending a SIP 200 (OK) response to the SCC-AS.

Table A.5.3A-10 SIP 200 (OK) response (UE-2 to SCC-AS)

SIP/2.0 200 OK

Via:

To: sip:user1_public2@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

CSeq:

P-Preferred-Identity:

Contact: sip:user1_public2@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.45.67.89

s=-

c=IN IP4 123.45.67.89

t=0 0

m=audio 0 RTP/AVP 0

m=audio 34002 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

31-32. SIP ACK request (from SCC-AS to UE-2)

The SCC-AS sends a SIP ACK request to UE-2 to acknowledge.

33-34. SIP re-INVITE request (from SCC-AS to controllee UE, UE-3)

The SCC-AS sends a SIP re-INVITE request to UE-3 to activate the audio 1 media component.

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.5.3A-11 SIP re-INVITE request (SCC-AS to UE-3)

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

Via:

To: sip:user1_public3@home1.net;

From: sip:scc-as@home1.net; tag=12486

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Referred-By: sip:user1_public1@home1.net

Contact:

Allow:

Content-Type: application/sdp

Content-Length: (…)

v=0

o=- 1027933615 1027933615 IN IP4 123.112.67.87

s=-

c=IN IP4 123.112.67.87

t=0 0

m=audio 49174 RTP/AVP 96 97

a=rtpmap:0 PCMU/8000

a= sendrecv

m=audio 0 RTP/AVP 0

m=video 1009 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

35-36. SIP 200 (OK) response (from controllee UE, UE-3 to SCC-AS)

Controllee UE, UE-3 sends a SIP 200 (OK) response to the SCC AS.

37-38. SIP ACK request (from SCC-AS to UE-3)

The SCC-AS sends a SIP ACK request to the controllee UE, UE-3.

39-40. SIP NOTIFY request (from SCC-AS to controller UE, UE-1)

The SCC AS sends a SIP NOTIFY request containing SDP of the SIP 200 (OK) response received from the controllee UE, UE-3.

Table A.5.3A-12 SIP NOTIFY request (SCC-AS to UE-1)

NOTIFY sip:user1_public1@home1.net;

Via:

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

From: sip:scc-as@home1.net; tag= 24680

Call-ID:

CSeq:

Max-Forwards:

P-Asserted-Identity:

Require:

Contact: sip: scc-as@home1.net

Allow:

Event: refer

Content-Type: message/sipfrag ;version=2.0 ;

Content-Length: (…)

SIP/2.0 200 OK

To: sip:user1_public3@home1.net; tag = xyzwv

From: sip:scc-as@home1.net; tag = 12486

Call-ID:

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

a=rtpmap:0 PCMU/8000

m=audio 0 RTP/AVP 0

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

41-42. 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.