A.2 RESUME Communication

24.6103GPPCommunication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystemProtocol specificationRelease 16TS

A.2.1 RESUME communication without announcement

The following diagram shows how a communication session is resumed using a re-INVITE request; The same can be achieved by sending an UPDATE request.

Figure A.2.1.1: RESUME communication without announcement to the held user

1. UE-A sends an INVITE to UE-B to resume the session – see example in table A.2.1.1-1. Resume is done by changing the SDP attribute. For each media stream that shall be resumed:

– "a=sendrecv", if the stream was previously a sendonly media stream, or the attribute can be omitted, since sendrecv is the default;

– "a=recvonly", if the stream was previously an inactive media stream.

Table A.2.1.1-1: re-INVITE request (UE to P-CSCF)

INVITE user2_public1@home2.net;gr=urn:uuid:2ad8950e-48a5-4a74-8d99-ad76cc7fc74 ;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP [5555::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-Preferred-Identity: "John Doe" <sip:user1_public1@home1.net>

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

Privacy: none

From: <sip:user1_public1@home1.net>; tag=171828

To: <tel:+1-212-555-2222>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 127 INVITE

Require: sec-agree

Proxy-Require: sec-agree

Supported: precondition, 100rel, gruu, 199

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_public1@home1.net; gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 ;comp=sigcomp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"

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

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=video 3400 RTP/AVPF 98 99

b=AS:75

a=curr:qos local sendrecv

a=curr:qos remote sendrecv

a=des:qos mandatory local sendrecv

a=des:qos optional remote sendrecv

a=sendrecv

a=rtpmap:98 H263

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

a=rtpmap:99:MPVMP4V-ES

m=audio 3456 RTP/AVPF 97 96

b=AS:25.4

a=curr:qos local sendrecv

a=curr:qos remote sendrecv

a=des:qos mandatory local sendrecv

a=des:qos optional remote sendrecv

a=sendrecv

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; maxframes=2

a=rtpmap:96 telephone-event

A.2.2 RESUME communication with announcement

The following diagram shows how a communication session is resumed using a re-INVITE request after it was held with an announcement being played by the AS to the held party. The same can be achieved by sending an UPDATE request.

Figure A.2.2.1: RESUME communication with announcement to the held user

1. UE-A sends a SIP INVITE request to UE-B to resume the session – see example in table A.2.2.1-1. Resume is done by changing the SDP attribute. For each media stream that shall be resumed:

– "a=sendrecv", if the stream was previously a sendonly media stream, or the attribute can be omitted, since sendrecv is the default;

Table A.2.2.1-1: re-INVITE request (UE to P-CSCF)

INVITE user2_public1@home2.net;gr=urn:uuid:2ad8950e-48a5-4a74-8d99-ad76cc7fc74 ;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP [5555::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-Preferred-Identity: "John Doe" <sip:user1_public1@home1.net>

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

Privacy: none

From: <sip:user1_public1@home1.net>; tag=171828

To: <tel:+1-212-555-2222>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 127 INVITE

Require: sec-agree

Proxy-Require: sec-agree

Supported: precondition, 100rel, gruu, 199

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_public1@home1.net; gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 ;comp=sigcomp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"

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

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=video 3400 RTP/AVPF 98 99

b=AS:75

a=curr:qos local sendrecv

a=curr:qos remote sendrecv

a=des:qos mandatory local sendrecv

a=des:qos optional remote sendrecv

a=sendrecv

a=rtpmap:98 H263

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

a=rtpmap:99:MPVMP4V-ES

m=audio 3456 RTP/AVPF 97 96

b=AS:25.4

a=curr:qos local sendrecv

a=curr:qos remote sendrecv

a=des:qos mandatory local sendrecv

a=des:qos optional remote sendrecv

a=sendrecv

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; maxframes=2

a=rtpmap:96 telephone-event

2. P-CSCF A forwards the SIP INVITE request towards S-CSCF.

3. S-CSCF forwards the SIP INVITE request towards the AS/MRF.

4. AS/MRF stops playing announcement to UE-B, following the procedures in 3GPP TS 24.628 [6].

5. AS/MRF forwards the SIP INVITE request towards UE-B, resulting in the removal of MRFP from the media path.

6. S-CSCF forwards the SIP INVITE request towards UE-B.

7. P-CSCF B forwards the SIP INVITE request to UE-B.

8. UE-B sends a SIP 200 (OK) response towards AS/MRF.

9. P-CSCF forwards the SIP 200 (OK) response towards AS/MRF.

10. S-CSCF forwards the SIP 200 (OK) response towards AS/MRF.

11. AS/MRF releases the resources allocated previously for the announcemnt

12. AS/MRF forwards the SIP 200 (OK) response towards UE-A.

13. S-CSCF forwards the SIP 200 (OK) response towards UE-A.

14. P-CSCF A forwards the SIP 200 (OK) response towards UE-A.

15. UE-A sends SIP ACK request towards AS/MRF.

16. P-CSCF forwards the SIP ACK request towards AS/MRF.

17. S-CSCF forwards SIP ACK request towards AS/MRF.

18. AS/MRF forwards the SIP ACK request towards UE-B.

19. S-CSCF forwards the SIP ACK request towards UE-B.

20. P-CSCF B forwards the SIP ACK request towards UE-B.

Annex B (informative):
Example of filter criteria

An example of an IFC Trigger Point configuration where the S-CSCF invokes the HOLD AS:

– Method="INVITE".

An example of an IFC Trigger Point configuration where the S-CSCF does not invoke the HOLD AS for a PSAP callback:

– Method="INVITE" and not Priority header field with a "psap-callback" header field value.

NOTE: Not invoking the HOLD AS assumes that the HOLD invocation request can be handled elsewhere in the network, e.g. in the PSAP itself.

Annex C (informative):
Change history

Change history

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Old

New

2005-08

Publication as ETSI TS 183 010

1.1.1

2006-04

Publication as ETSI TS 183 010

1.2.1

2007-04

Publication as ETSI TS 183 010

1.2.2

2007-12

Conversion to 3GPP TS 24.410

1.2.3

2008-01

Technically identical copy as 3GPP TS 24.610 as basis for further development.

1.2.4

2008-02

Implemented C1-080101

1.3.0

2008-04

Implemented C1-080886, C1-080887, C1-081090, C1-081091, C1-081113

1.4.0

2008-05

Implemented C1-081831, C1-081913

1.5.0

2008-05

Editorial changes done by MCC

1.5.0

1.5.1

2008-06

CT#40

CP-080330

CP-080330 was approved by CT#40 and version 8.0.0 is created by MCC for publishing

1.5.1

8.0.0

2008-09

CT#41

CP-080533

0001

Correction of Activation/deactivation of HOLD

8.0.0

8.1.0

2008-09

CT#41

CP-080533

0002

1

Miscellaneous clean-up corrections

8.0.0

8.1.0

2008-09

CT#41

CP-080533

0003

Applicability statement in scope

8.0.0

8.1.0

2008-09

CT#41

CP-080533

0004

Interaction of HOLD and CONF

8.0.0

8.1.0

2008-12

CT#42

CP-080865

0005

1

Holding or resuming all media streams

8.1.0

8.2.0

2008-12

CT#42

CP-080865

0006

2

Contents of SDP offer in HOLD

8.1.0

8.2.0

2008-12

CT#42

CP-080865

0007

1

Fixed the flows

8.1.0

8.2.0

2009-03

CT#43

CP-090121

0008

Correction of URN-value for Service Identifiers

8.2.0

8.3.0

2009-12

CT#46

CP-090923

0009

1

Correction of icsi-ref feature tag

8.3.0

9.0.0

2010-09

CT#49

CP-100526

0014

HOLD corrections

9.0.0

9.1.0

2011-03

CT#51

Upgrade to Rel-10

9.1.0

10.0.0

2012-03

CT#55

CP-120124

0015

1

HOLD-CONF interaction

10.0.0

11.0.0

2012-03

CT#55

CP-120197

0016

2

Clarification of HOLD procedures

10.0.0

11.0.0

2012-06

CT#56

CP-120307

0017

1

Usage of SDP direction attributes correction

11.0.0

11.1.0

2012-12

CT#58

CP-120778

0021

2

Emergency call HOLD suppression

11.1.0

11.2.0

2013-06

CT#60

CP-130414

0022

8

Prevent HOLD for PSAP callback

11.2.0

12.0.0

2013-09

CT#61

CP-130485

0027

2

Call Hold Bandwidth Management

12.0.0

12.1.0

2013-09

CT#61

CP-130507

0028

draft-ietf-ecrit-psap-callback reference update

12.0.0

12.1.0

2013-12

CT#62

CP-130758

0029

2

Reference update: draft-ietf-ecrit-psap-callback

12.1.0

12.2.0

2013-12

CT#62

CP-130763

0030

1

RTCP flow during hold with announcement

12.1.0

12.2.0

2014-03

CT#63

CP-140143

0032

Correction the direction attribute of media stream(s) in the Communication Hold supplementary service

12.2.0

12.3.0

2014-06

CT#64

CP-140330

0034

Clean-up of HOLD flows

12.3.0

12.4.0

2014-06

CT#64

CP-140330

0036

Minor corrections 24.610

12.3.0

12.4.0

2014-09

CT#65

CP-140665

0033

4

Media directionality when resuming a session established with one-way media

12.4.0

12.5.0

2014-12

CT#66

CP-140833

0037

1

Reference update: RFC 7090 (draft-ietf-ecrit-psap-callback)

12.5.0

12.6.0

2015-06

CT#67

CP-150322

0039

1

Media sharing and HOLD service

12.6.0

13.0.0

2015-12

CT#70

CP-150709

0042

1

Local held indication at UE

13.0.0

13.1.0

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2017-03

CT-75

Upgrade to Rel-14

14.0.0

2017-12

CT-78

CP-173071

0043

2

B

Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem

15.0.0

2018-03

CT-79

CP-180090

0044

4

F

Clarification of condition for providing announcement to the held UE

15.1.0

2019-12

CT-86

CP-193111

0045

B

Adding interactions with "Multi-Device" and "Multi-Identity" services

16.0.0