A.3 FA model signalling flow
24.2393GPPFlexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystemProtocol specificationRelease 17TS
A.3.1 Introduction
The following flow shows the establishment of a session between UE#1 and UE#2. The following flow is included:
– clause A.3.2 shows FA, when UE#1 and UE#2 have resources available and UE#3 does not have required resources available.
A.3.2 FA when UE#1 and UE#2 have resources available and UE#3 does not have required resources available
Figure A.3.2-1 and figure A.3.2-2 show the FA service invoked when UE#1 sends an INVITE request to the Pilot Identity. UE#2 and UE#3 have registered public user identities that are included in the FA group. In this example, UE#1 and UE#2 have resources available prior to session initiation, whereas UE#3 does not have the required resources available before it receives the initial INVITE request. This example assumes that all the UEs involved in this session support the IMS Multimedia Telephony Communication Service.
Figure A.3.2-1: FA, UE#3 does not have required resources available
Figure A.3.2-2: FA, UE#3 does not have required resources available
1 INVITE request (UE#1 to S-CSCF) see example in table A.3.2-1
UE#1 sends a SIP INVITE request to the intermediate IM CN subsystem.
Table A.3.2-1: INVITE request (UE#1 to FA-AS)
INVITE tel:+1-212-555-2222 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:scscf1.home1.net;lr>
P-Preferred-Identity: "John Doe" <sip:user1_public1@home1.net>
P-Access-Network-Info: IEEE-802.11a
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"
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
Supported: precondition, 100rel, gruu, 199
Proxy-Require: sec-agree
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>;+g.3gpp.icsi-ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"
Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE
Accept:application/sdp,.application/3gpp-ims+xml
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 2987933615 2987933615 IN IP6 6666::aaa:bbb:ccc:ddd
s=-
c=IN IP6 6666::aaa:bbb:ccc:ddd
t=0 0
m=video 3400 RTP/AVP 98
a=tcap:1 RTP/AVPF
a=pcfg:1 t=1
b=AS:75
a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
m=audio 3456 RTP/AVP 97 96
a=tcap:1 RTP/AVPF
a=pcfg:1 t=1
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes=2
a=rtpmap:96 telephone-event
Request-URI: The request URI is set to the Pilot Identity of the FA group.
Supported: The UE indicates support for preconditions, reliable provisional responses, gruu and the 199 provisional response.
SDP: The SDP offer (SDP_O) contains a set of codecs supported by UE#1 and desired by the calling user for this session. The local preconditions are indicated as fulfilled.
2 INVITE request (S-CSCF to FA-AS)
The S-CSCF forwards the SIP INVITE request to the FA-AS.
3-4 INVITE request (FA-AS to UE#3)
The Pilot Identity included in the Request-URI in the received INVITE request is mapped to the public user identities of the individual FA members in the FA group. The FA-AS forwards the INVITE request to the individual FA members in the FA group. The FA-AS forwards the INVITE request to UE#3, with the Request-URI set the public user identity which is an identity included in the FA group and registered from UE#3.
5-6 180 (Ringing) provisional response (UE#3 to FA-AS) see example in table A.3.2-2
The called party is alerted. UE#3 sends a reliable SIP 180 (Ringing) provisional response for the INVITE request to the FA-AS.
Table A.3.4-2: 180 (Ringing) response (UE#3 to FA-AS)
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP pcscf2.visited2.net:5088;comp=sigcomp;branch=z9hG4bK361k21.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764XC12.1, SIP/2.0/UDP faas.home2.net;branch=z9hG4bK764Q32.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.1, SIP/2.0/UDP icscf2_s.home2.net;branch=z9hG4bK871y12.1, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7
Record-Route: <sip:pcscf2.visited2.net:5088;lr;comp=sigcomp>, <sip:scscf2.home2.net;lr>, <sip:scscf1.home1.net;lr>, <sip:pcscf1.visited1.net;lr>
From:
To: <tel:+1-212-555-1001>;tag=6322
Call-ID:
Cseq:
Require: 100rel, precondition
Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE
RSeq: 9021
Contact: <sip:user3_public1@visited1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91er2d2>;+g.3gpp.icsi-ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 2987933615 2987933615 IN IP6 6666::eee:fff:aaa:bbb
s=-
c=IN IP6 6666::eee:fff:aaa:bbb
t=0 0
m=video 3400 RTP/AVPF 98
a=acfg:1 t=1
b=AS:75
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
m=audio 3456 RTP/AVPF 97 96
a=acfg:1 t=1
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes
SDP: The SDP answer (SDP_A1) contains a set of codecs to be used for the session. The local preconditions are indicated as fulfilled.
7-8 PRACK request (FA-AS to UE#3)
FA-AS sends a SIP PRACK request, which acknowledges the SIP 180 (Ringing) provisional response, to UE##3.
9-10 200 (OK) response to PRACK (UE#3 to FA-AS)
UE#3 sends a SIP 200 (OK) response for the SIP PRACK request to FA-AS.
11-12 180 (Ringing) provisional response (FA-AS to UE#1)
The FA-AS sends a reliable SIP 180 (Ringing) provisional response to UE#1.
An early dialog (D2) is established between UE#1 and the FA-AS.
13-14 PRACK request (UE#1 to FA-AS)
UE#1 sends a SIP PRACK request, which acknowledges the SIP 180 (Ringing) provisional response, to the FA-AS.
15-16 200 (OK) response to PRACK (FA-AS to UE#1)
The FA-AS sends a SIP 200 (OK) response for the SIP PRACK request to UE#1.
17-18 INVITE request (FA-AS to UE#2)
The Pilot Identity included in the Request-URI in the received INVITE request is mapped to the public user identities of the individual FA members in the FA group. The FA-AS forwards the INVITE request to the individual FA members in the FA group. In parallel to forwarding the request to UE #3 (see step 3), the FA-AS forwards the request to UE#2, with the Request-URI set the public user identity which is an identity included in the FA group and registered from UE#2.
19-20 180 (Ringing) provisional response (UE#2 to FA-AS) see example in table A.3.2-2
The called party is alerted. UE#2 sends a reliable SIP 180 (Ringing) provisional response for the INVITE request to the FA-AS.
Table A.3.4-3: 180 (Ringing) response (UE#2 to FA-AS)
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP pcscf2.visited2.net:5088;comp=sigcomp;branch=z9hG4bK361k21.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764XC12.1, SIP/2.0/UDP faas.home2.net;branch=z9hG4bK764Q32.1, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK764z87.1, SIP/2.0/UDP icscf2_s.home2.net;branch=z9hG4bK871y12.1, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7
Record-Route: <sip:pcscf2.visited2.net:5088;lr;comp=sigcomp>, <sip:scscf2.home2.net;lr>, <sip:scscf1.home1.net;lr>, <sip:pcscf1.visited1.net;lr>
From:
To: <tel:+1-212-555-1002>;tag=4114
Call-ID:
Cseq:
Require: 100rel, precondition
Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE
RSeq: 7187
Contact: <sip:user2_public1@visited1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91ewxyz>;+g.3gpp.icsi-ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"
Content-Type: application/sdp
Content-Length: (…)
v=0
o=- 2987933615 2987933615 IN IP6 6666::eee:fff:aaa:ccc
s=-
c=IN IP6 6666::eee:fff:aaa:ccc
t=0 0
m=video 3400 RTP/AVPF 98
a=acfg:1 t=1
b=AS:75
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:98 H263
a=fmtp:98 profile-level-id=0
m=audio 3456 RTP/AVPF 97 96
a=acfg:1 t=1
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes
SDP: The SDP answer (SDP_A2) contains a set of codecs to be used for the session. The local preconditions are indicated as fulfilled.
21-22 PRACK request (FA-AS to UE#2)
FA-AS sends a SIP PRACK request, which acknowledges the SIP 180 (Ringing) provisional response, to UE#2.
23-24 200 (OK) response to PRACK (UE#2 to FA-AS)
UE#2 sends a SIP 200 (OK) response for the SIP PRACK request to FA-AS.
25-26 200 (OK) response to INVITE (UE#2 to FA-AS)
The called party answers the call. UE#2 sends a SIP 200 (OK) final response for the SIP INVITE request to the FA-AS.
27-28 CANCEL request (FA-AS to UE#3)
FA-AS sends a SIP CANCEL request, to cancel early dialog D1, to UE#3.
29-30 200 (OK) response to CANCEL (UE#3 to FA-AS)
UE#3 sends a SIP 200 (OK) response for the SIP PRACK request to FA-AS.
31-32 487 (Request Terminated) (UE#3 to FA-AS)
UE#3 sends a SIP 487 (Request Terminated), to cancel early dialog D1, to FA-AS.
33-34 ACK request to CANCEL (FA-AS to FA-UE#3)
FA-AS sends a SIP ACK request, which acknowledges the 200 (OK) to CANCEL, to UE#3.
35-36 200 (OK) response to INVITE (FA-AS to UE#1)
In parallel to sending the CANCEL request to UE#3 (see step 27), the FA-AS sends a SIP 200 (OK) response to UE#1. The response contains SDP answer (SDP_A2).
37-38 ACK request (UE#1 to FA-AS)
UE#1 sends a SIP ACK request, which acknowledges the SIP 200 (OK) final response, to FA-AS.
39-40 ACK request (FA-AS to UE#2)
FA-AS sends a SIP ACK request, which acknowledges the SIP 200 (OK) final response, to UE#2.
Annex B (informative):
Example of filter criteria
This annex provides an example of a filter criterion that triggers SIP requests that are subject to initial filter criteria evaluation.
When the initial request matches the conditions of the next unexecuted IFC rule for the served user which points to the FA service and the, the communication is forwarded to the AS.
An example of an Initial Filter Criteria (IFC) Trigger Point configurations under the assumption that the FA service is a standalone service that can be invoked by a very specific triggerpoint active at the destination S-CSCF:
– (Method="INVITE" AND Header="Request-URI").
NOTE 1: The coding of the Initial Filter Criteria is described in 3GPP TS 29.228 [7].
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2008-01 |
Rapporteurs input framework document |
0.0.0 |
0.0.1 |
||||
|
2008-04 |
Implementation of CRs agreed at CT1#52 as follows: C1-081362, C1-081363, C1-081364, C1-081365 |
0.0.1 |
0.1.0 |
||||
|
2008-04 |
Miscellaneous editorial corrections |
0.1.0 |
0.1.1 |
||||
|
2008-05 |
Implemented C1-082034, C1-082035 |
0.2.0 |
|||||
|
2008-07 |
Implemented C1-082448, C1-082662 from CT1#54 |
0.3.0 |
|||||
|
2008-08 |
Implemented C1-082959, C1-083207, C1-083371, C1-083372 from CT1#55 |
0.4.0 |
|||||
|
2008-09 |
Version 1.0.0 created for presentation to TSG CT#41 for information |
0.4.0 |
1.0.0 |
||||
|
2008-11 |
Implemented the following CRs after CT1#56: C1-085095, C1-085096, C1-085097, C1-085273, C1-085274, C1-085276, C1-085457 |
1.1.0 |
|||||
|
2008-11 |
Version 2.0.0 created for presentation to TSG CT#42 for approval |
1.1.0 |
2.0.0 |
||||
|
2008-12 |
CT-42 |
Version 8.0.0 created after approval in CT#42 |
2.0.0 |
8.0.0 |
|||
|
2009-03 |
CT-43 |
CP-090121 |
0001 |
Correction of URN-value for Service Identifiers |
8.0.0 |
8.1.0 |
|
|
2009-03 |
CT-43 |
CP-090143 |
0002 |
1 |
Service configuration XML schema for IMS Flexible Alerting |
8.0.0 |
8.1.0 |
|
2009-03 |
CT-43 |
CP-090143 |
0003 |
Flow updates |
8.0.0 |
8.1.0 |
|
|
2009-12 |
CT-46 |
CP-090910 |
0004 |
1 |
Correction of FA XML schema – activation |
8.1.0 |
8.2.0 |
|
2009-12 |
CT-46 |
CP-090910 |
0005 |
1 |
Removal of editor’s notes from 24.239 |
8.1.0 |
8.2.0 |
|
2009-12 |
CT-46 |
Upgrade to Rel-9 |
8.2.0 |
9.0.0 |
|||
|
2011-03 |
CT-51 |
Upgrade to Rel-10 |
9.0.0 |
10.0.0 |
|||
|
2012-09 |
CT-57 |
Upgrade to Rel-11 |
10.0.0 |
11.0.0 |
|||
|
2013-06 |
CT-60 |
CP-130265 |
0006 |
3 |
Flexible Alerting-Sequential mode |
11.0.0 |
12.0.0 |
|
2015-12 |
CT-70 |
Upgrade to Rel-13 |
12.0.0 |
13.0.0 |
|||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
CT75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2017-12 |
CT-78 |
CP-173071 |
0008 |
3 |
B |
Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem |
15.0.0 |
|
2019-12 |
CT-86 |
CP-193111 |
0009 |
1 |
B |
Adding interactions with "Multi-Device" and "Multi-Identity" services |
16.0.0 |
|
2022-03 |
CT-86- |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |