M.3 Application usage of SIP
24.1733GPPIMS Multimedia telephony communication service and supplementary servicesRelease 18Stage 3TS
M.3.1 Procedures at the UE
M.3.1.1 3GPP PS data off
M.3.1.1.1 General
The requirements in clause J.3.1.1.1 apply.
Additionally, the following requirements apply.
In case of SNPN, if the UE supports the 3GPP PS data off:
a) the UE can be configured with:
1) up to two indications of whether the MMTEL voice is a 3GPP PS data off exempt service for each subscribed SNPN whose entry exists in the "list of subscriber data", one indication is valid for the UE camping in the subscribed SNPN, and the other indication is valid for any non-subscribed SNPN the UE is camping in using the subscribed SNPN’s credentials;
2) up to two indications of whether the MMTEL video is a 3GPP PS data off exempt service for each subscribed SNPN whose entry exists in the "list of subscriber data", one indication is valid for the UE camping in the subscribed SNPN, and the other indication is valid for any non-subscribed SNPN the UE is camping in using the subscribed SNPN’s credentials;
3) an indication of whether the MMTEL voice is a 3GPP PS data off exempt service for PLMN subscription, valid for any non-subscribed SNPN the UE is camping in using the PLMN subscription; and
4) an indication of whether the MMTEL video is a 3GPP PS data off exempt service for PLMN subscription, valid for any non-subscribed SNPN the UE is camping in using the PLMN subscription;
b) for a subscribed SNPN whose entry exists in the "list of subscriber data", the UE may support being configured with the indication of whether the MMTEL voice is a 3GPP PS data off exempt service using one or more of the following methods:
1) the MMTEL_voice_exempt node of 3GPP TS 24.275 [36], if the UE is in the subscribed SNPN; and
2) the MMTEL_voice_exempt_non_subscribed_SNPN node of 3GPP TS 24.275 [36], if the UE is in the non-subscribed SNPN.
For PLMN subscription, the UE may support being configured with the indication of whether the MMTEL voice is a 3GPP PS data off exempt service using the following method:
1) the MMTEL_voice_exempt_non_subscribed_SNPN node of 3GPP TS 24.275 [36], if the UE is in the non-subscribed SNPN; and
c) for a subscribed SNPN whose entry exists in the "list of subscriber data", the UE may support being configured with the indication of whether the MMTEL video is a 3GPP PS data off exempt service using one or more of the following methods:
1) the MMTEL_video_exempt node of 3GPP TS 24.275 [36], if the UE is in the subscribed SNPN; and
2) the MMTEL_video_exempt_non_subscribed_SNPN node of 3GPP TS 24.275 [36], if the UE is in the non-subscribed SNPN.
For PLMN subscription, the UE may support being configured with the indication of whether the MMTEL video is a 3GPP PS data off exempt service using the following method:
1) the MMTEL_video_exempt_non_subscribed_SNPN node of 3GPP TS 24.275 [36], if the UE is in the non-subscribed SNPN.
When the UE is only configured with the indication valid for the UE camping in the subscribed SNPN, the UE shall use this indication also when the UE is in the non-subscribed SNPN.
M.3.1.1.2 Enforcement
If the 3GPP PS data off status is "active":
a) the UE shall release according to 3GPP TS 24.229 [13] any multimedia telephony communication session as described in clause 5.2, which is not an IMS emergency call, established with a UE’s contact address containing an IP address associated with a 5GS QoS flow using NG-RAN, with media streams:
1) other than only audio;
2) other than only real-time text;
3) other than only audio and real-time text; and
4) not including video;
NOTE 1: When the 3GPP PS data off status is "active", an MMTEL session which is not MMTEL voice and which is not MMTEL video (e.g. MMTEL session with only fax) is released.
b) the UE shall not send according to 3GPP TS 24.229 [13] a SIP message related to a multimedia telephony communication session as described in clause 5.2, which is not an IMS emergency call, from a UE’s contact address containing an IP address associated with a 5GS QoS flow using NG-RAN, and with:
1) an SDP offer; or
2) an SDP answer;
with media streams:
1) other than only audio;
2) other than only real-time text;
3) other than only audio and real-time text; and
4) not including video;
NOTE 2: When the 3GPP PS data off status is "active", an MMTEL session which is not MMTEL voice and which is not MMTEL video (e.g. MMTEL session with only fax) cannot be initiated.
c) if the UE is not configured with indication that MMTEL voice is a 3GPP PS data off exempt service:
1) the UE shall release according to 3GPP TS 24.229 [13] any multimedia telephony communication session as described in clause 5.2, which is not an IMS emergency call, established with a UE’s contact address containing an IP address associated with an 5GS QoS flow using NG-RAN, with only audio, only real-time text or only audio and real-time text; and
2) the UE shall not send according to 3GPP TS 24.229 [13] a SIP message related to a multimedia telephony communication session as described in clause 5.2, which is not an IMS emergency call, from a UE’s contact address containing an IP address associated with a 5GS QoS flow using NG-RAN and with:
A) an SDP offer; or
B) an SDP answer;
with only audio, only real-time text or only audio and real-time text;
NOTE 3: If the UE doesn’t send an intitial SIP INVITE due to conditions as described in bullet c.2, the UE can attempt a request for a service equivalent to MMTel voice via the CS domain – if supported and available – and, otherwise, the UE can attempt the service according to 3GPP TS 24.229 [13] and as described in clause 5.2 via non-3GPP access.
d) if the UE is not configured with indication that MMTEL video is a 3GPP PS data off exempt service:
1) the UE shall release according to 3GPP TS 24.229 [13] any multimedia telephony communication session as described in clause 5.2, which is not an IMS emergency call, established with a UE’s contact address containing an IP address associated with a 5GS QoS flow using NG-RAN, and with video;
2) the UE shall not send according to 3GPP TS 24.229 [13] a SIP message related to a multimedia telephony communication session as described in clause 5.2, which is not an IMS emergency call, from a UE’s contact address containing an IP address associated with a 5GS QoS flow using NG-RAN and with:
A) an SDP offer; or
B) an SDP answer;
with video; and
e) if the UE is not configured with indication that MMTEL voice is a 3GPP PS data off exempt service and the UE is not configured with indication that MMTEL video is a 3GPP PS data off exempt service:
1) the UE shall de-register the binding of a UE’s contact address containing an IP address associated with an 5GS QoS flow using NG-RAN from IM CN subsystem according to 3GPP TS 24.229 [13];
2) the UE shall re-register the binding of a UE’s contact address containing an IP address associated with an 5GS QoS flow using NG-RAN with IM CN subsystem with a Contact header field without the g.3gpp.icsi-ref media feature tag; or
3) the UE shall re-register the binding of a UE’s contact address containing an IP address associated with an 5GS QoS flow with IM CN subsystem with a Contact header field with the g.3gpp.icsi-ref media feature tag not including the urn:urn-7:3gpp-service.ims.icsi.mmtel ICSI according to 3GPP TS 24.229 [13].
NOTE 4: Which of the bullets 1), 2), and 3) the UE performs is influenced by other 3GPP PS data off exempt services.
M.3.1.2 Establishing an MMTEL session
If the UE is establishing an MMTEL session offering audio and if the IP-CAN of 5GS indicated that interworking without N26 is supported as specified in 3GPP TS 24.501 [42], the UE should transmit the SIP INVITE request using TCP as transport protocol.
NOTE: The use of TCP is to ensure the reception of transmitted SIP messages in case fallback to EPS for voice is used and the IP-CAN of 5GS supports interworking without N26.
M.3.2 Procedures at the multimedia telephony application server
M.3.2.1 3GPP PS data off
The requirements in clause J.3.2.1 apply.
Additionally, the following requirements apply.
When serving a UE in an SNPN using an entry of "list of subscriber data", a multimedia telephony application server supporting the 3GPP PS data off can be configured with:
1) up to two indications of whether the MMTEL voice is a 3GPP PS data off exempt service, one indication is valid for the UE camping in the subscribed SNPN, and the other indication is valid for any non-subscribed SNPN the UE is camping in using the subscribed SNPN’s credentials; and
2) up to two indications of whether the MMTEL video is a 3GPP PS data off exempt service, one indication is valid for the UE camping in the subscribed SNPN, and the other indication is valid for any non-subscribed SNPN the UE is camping in using the subscribed SNPN’s credentials.
When the multimedia telephony application server is only configured with the indication valid for the UE camping in the subscribed SNPN, the multimedia telephony application server shall use this indication also when the UE is in the non-subscribed SNPN.
When serving a UE in an SNPN using PLMN subscription, a multimedia telephony application server supporting the 3GPP PS data off can be configured with:
1) an indication of whether the MMTEL voice is a 3GPP PS data off exempt service, valid for any non-subscribed SNPN the UE is camping in using the PLMN subscription; and
2) an indication of whether the MMTEL video is a 3GPP PS data off exempt service, valid for any non-subscribed SNPN the UE is camping in using the PLMN subscription.
Annex N (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2006-05 |
CT1#42 |
First draft |
0.0.0 |
0.1.0 |
|||
|
2006-07 |
CT1#42-bis |
The following Tdocs included are in this version of the TS: Some corrections to the formatting as well as editorial alignments also done by the rapporteur. |
0.1.0 |
0.2.0 |
|||
|
2006-09 |
CT1#43 |
The following Tdocs have been included in this version of the TS: C1-061464, C1-061721, C1-061722, C1-0611723 Some formatting cleanups performed in chapters: Annex E (4.5.2.6.2 and 4.7.1.1) and Annex H (4.5.2.4.1.2.3, 4.5.2.4.2.1, 4.5.2.7.2 and 4.5.2.7.3). |
0.2.0 |
0.3.0 |
|||
|
2006-11 |
CT1#44 |
The following Tdoc has been included in this version of the TS: C1-062452 |
0.3.0 |
0.4.0 |
|||
|
2006-11 |
3GPP/TISPAN Supplementary Serv |
The following Tdoc has been included in this version of the TS: SS-060052 |
0.4.0 |
0.5.0 |
|||
|
2006-11 |
V 1.0.0 created by MCC |
0.5.0 |
1.0.0 |
||||
|
2007-02 |
CT1#45 |
The text in the annexes A, B, C, D, E, F, G, H and I split out as separate word-files with ETSI-logo and headers. The following contributions, including TISPAN#12 plenary approved CRs, have been incorporated: C1-070032 C1-070163 (12TD062 TISPAN#12 plenary CR pack) C1-070164 (12TD066r1 TISPAN#12 plenary CR pack) C1-070165 (12TD060 TISPAN#12 plenary CR pack) C1-070166 (12TD068 TISPAN#12 plenary CR pack) C1-070167 (12TD061 TISPAN#12 plenary CR pack) C1-070436 C1-070437 C1-070555 C1-070557 C1-070631 C1-061464 (CT1#43) change to Annex E/4.6.4 incorporated |
1.0.0 |
1.1.0 |
|||
|
2007-02 |
V 2.0.0 created by MCC |
1.1.0 |
2.0.0 |
||||
|
2007-02 |
CT#35 |
The following Tdoc approved in CT#35: CP-070230 |
2.0.0 |
2.1.0 |
|||
|
2007-03 |
CT#35 |
Version 7.0.0 was created by MCC |
2.1.0 |
7.0.0 |
|||
|
2007-06 |
CT-36 |
CP-070430 |
0006 |
1 |
24.173: Alignment with TISPAN#13 approved CDIV CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0013 |
– |
24.173: Alignment with TISPAN#13 approved XCAP CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0011 |
– |
24.173: Alignment with TISPAN#13 approved OIP/OIR CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0010 |
– |
24.173: Alignment with TISPAN#13 approved MWI CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0009 |
– |
24.173: Alignment with TISPAN#13 approved HOLD CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0008 |
– |
24.173: Alignment with TISPAN#13 approved ECT CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0007 |
– |
24.173: Alignment with TISPAN#13 approved CONF CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0005 |
– |
24.173: Alignment with TISPAN#13 approved CB CRs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070430 |
0003 |
– |
Correction of file names for the SS-TSs |
7.0.0 |
7.1.0 |
|
2007-06 |
CT-36 |
CP-070490 |
0012 |
1 |
Alignment with TISPAN#13 approved TIP/TIR CRs |
7.0.0 |
7.1.0 |
|
2007-09 |
CT-37 |
CP-070668 |
0024 |
3 |
Service identification alignment |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0025 |
2 |
24.173: Alignment with TISPAN#14 approved CDIV CRs |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0026 |
2 |
24.173: Alignment with TISPAN#14 approved ECT CRs |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0027 |
2 |
24.173: Replacing CB text with text from the published ETSI specification |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0028 |
2 |
24.173: Replacing CONF text with text from the published ETSI specification |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0029 |
2 |
24.173: Replacing HOLD text with text from the published ETSI specification |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0030 |
2 |
24.173: Replacing MWI text with text from the published ETSI specification |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0031 |
2 |
24.173: Replacing OIP-OIR text with text from the published ETSI specification |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0032 |
2 |
24.173: Replacing TIP-TIR text with text from the published ETSI specification |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070669 |
0033 |
2 |
24.173: Replacing XCAP text with text from the published ETSI specification |
7.1.0 |
7.2.0 |
|
2007-09 |
CT-37 |
CP-070699 |
0023 |
7 |
IMS Multimedia Telephony Communication Service ICSI in Accept-Contact |
7.1.0 |
7.2.0 |
|
2007-12 |
CT-38 |
CP-070797 |
0036 |
2 |
Specification of ICSI for Multimedia Telephony in Accept-Contact |
7.2.0 |
7.3.0 |
|
2007-12 |
CT-38 |
CP-070796 |
0037 |
Use of the ICSI in the Contact Header for mmtel |
7.2.0 |
7.3.0 |
|
|
2008-03 |
CT-39 |
CP-080127 |
0045 |
3 |
Interworking with terminals not supporting Multimedia Telephony Service Identifier |
7.3.0 |
7.4.0 |
|
2008-03 |
CT-39 |
CP-080205 |
0046 |
1 |
Addition of 3GPP supplementary service specification |
7.3.0 |
7.4.0 |
|
2008-03 |
CT-39 |
CP-080139 |
0047 |
1 |
Addition of 3GPP supplementary service specification |
7.4.0 |
8.0.0 |
|
2008-06 |
CT-40 |
CP-080345 |
0049 |
1 |
Correction of feature tag format |
8.0.0 |
8.1.0 |
|
2008-06 |
CT-40 |
CP-080346 |
0052 |
– |
Reference replacement table removal |
8.0.0 |
8.1.0 |
|
2008-06 |
CT-40 |
CP-080360 |
0050 |
1 |
Reference naming correction |
8.0.0 |
8.1.0 |
|
2008-09 |
CT-41 |
CP-080518 |
0054 |
1 |
Introduction of terms "multimedia telephony participant" and "multimedia telephony application server" |
8.1.0 |
8.2.0 |
|
2008-09 |
CT-41 |
CP-080518 |
0055 |
2 |
Allow SIP based user configuration mechanism for configuring supplementary services |
8.1.0 |
8.2.0 |
|
2008-09 |
CT-41 |
CP-080536 |
0056 |
2 |
Addition of new supplementary services |
8.1.0 |
8.2.0 |
|
2008-12 |
CT-42 |
CP-080864 |
0058 |
3 |
Make common IMS specification codec-neutral |
8.2.0 |
8.3.0 |
|
2008-12 |
CT-42 |
CP-080869 |
0060 |
Correction of ICSI and IARI feature tag name |
8.2.0 |
8.3.0 |
|
|
2008-12 |
CT-42 |
CP-080864 |
0063 |
2 |
Interaction between SIP and Ut based service configuration |
8.2.0 |
8.3.0 |
|
2008-12 |
CT-42 |
CP-080852 |
0064 |
1 |
Codec formats for fixed-broadband accesses |
8.2.0 |
8.3.0 |
|
2008-12 |
CT-42 |
CP-080873 |
0065 |
Adding CC and CW |
8.2.0 |
8.3.0 |
|
|
2008-12 |
CT-42 |
Editorial cleanup by MCC |
8.2.0 |
8.3.0 |
|||
|
2009-03 |
CT-43 |
CP-090121 |
0067 |
Correction of URN-value for Service Identifiers |
8.3.0 |
8.4.0 |
|
|
2009-06 |
CT-44 |
CP-090416 |
0068 |
Correction of clause heading |
8.4.0 |
8.5.0 |
|
|
2009-06 |
CT-44 |
CP-090403 |
0070 |
Correction of 3GPP URN link |
8.4.0 |
8.5.0 |
|
|
2009-12 |
CT-46 |
CP-090904 |
0073 |
1 |
Addition of Customized alterting tones (CAT) service |
8.5.0 |
8.6.0 |
|
2009-12 |
CT-46 |
CP-090920 |
0075 |
Removal of editor’s note on Reverse Charging |
8.5.0 |
8.6.0 |
|
|
2009-12 |
CT-46 |
CP-090931 |
0072 |
5 |
Service Specific Access Control enforcement |
8.6.0 |
9.0.0 |
|
2009-12 |
CT-46 |
CP-090932 |
0074 |
Addition of Customized ringing signal (CRS) service |
8.6.0 |
9.0.0 |
|
|
2010-03 |
CT-47 |
CP-100145 |
0076 |
1 |
Alignment with RAN2 specification regarding SSAC |
9.0.0 |
9.1.0 |
|
2010-09 |
CT-49 |
CP-100519 |
0080 |
2 |
CS data and fax |
9.1.0 |
10.0.0 |
|
2011-09 |
CT-53 |
CP-110695 |
0083 |
2 |
Adding missing PNM feature to TS 24.173 |
10.0.0 |
11.0.0 |
|
2011-09 |
CT-53 |
CP-110696 |
0084 |
2 |
Addition of USSD into TS 24.173 |
10.0.0 |
11.0.0 |
|
2011-12 |
CT-54 |
CP-110881 |
0086 |
2 |
Multimedia Telephony Application Server indicating it is on the route |
11.0.0 |
11.1.0 |
|
2012-03 |
CT-55 |
CP-120124 |
0087 |
2 |
Multimedia Telephony Application Server indicating it is on the route |
11.1.0 |
11.2.0 |
|
2012-09 |
CT-57 |
CP-120583 |
0089 |
1 |
Reference update and technical changes: draft-ietf-sipcore-proxy-feature |
11.2.0 |
11.3.0 |
|
2012-12 |
CT-58 |
CP-120793 |
0090 |
2 |
Reference update: draft-ietf-sipcore-proxy-feature |
11.3.0 |
11.4.0 |
|
2012-12 |
CT-58 |
CP-120793 |
0091 |
1 |
Feature-Caps header field clarification |
11.3.0 |
11.4.0 |
|
2013-03 |
CT-59 |
CP-130116 |
0092 |
Reference update: RFC 6809 |
11.4.0 |
11.5.0 |
|
|
2013-12 |
CT-62 |
CP-130763 |
0097 |
4 |
Provide linkage to Supplementary Services Configuration in TS 24.167 |
11.5.0 |
12.0.0 |
|
2014-06 |
CT-64 |
CP-140330 |
0098 |
1 |
Extended scope of TS 26.114 |
12.0.0 |
12.1.0 |
|
2014-06 |
CT-64 |
CP-140334 |
0103 |
2 |
USSD method selection |
12.0.0 |
12.1.0 |
|
2014-09 |
CT-65 |
CP-140662 |
0104 |
3 |
MMTEL voice/video call indications for SCM |
12.1.0 |
12.2.0 |
|
2014-12 |
CT-66 |
CP-140855 |
0106 |
1 |
Correcting incorrect reference |
12.2.0 |
12.3.0 |
|
2014-12 |
CT-66 |
CP-140855 |
0107 |
Correcting details of originating multimedia telephony communication session end |
12.2.0 |
12.3.0 |
|
|
2014-12 |
CT-66 |
CP-140855 |
0108 |
Solving Editor’s Note on handling addition and removal of media from a session for SCM – alt 1 |
12.2.0 |
12.3.0 |
|
|
2014-12 |
CT-66 |
CP-140855 |
0109 |
Correcting conditions for sending START and STOP for MMTEL |
12.2.0 |
12.3.0 |
|
|
2014-12 |
CT-66 |
CP-140837 |
0110 |
5 |
clarification of the text on service configuration |
12.2.0 |
12.3.0 |
|
2015-06 |
CT-68 |
CP-150328 |
0112 |
1 |
Service Specific Access Control Exemption for MPS |
12.3.0 |
13.0.0 |
|
2016-06 |
CT-72 |
CP-160307 |
0113 |
3 |
Correction of MMTEL voice/video call indications for ACDC |
13.0.0 |
13.1.0 |
|
2016-06 |
CT-72 |
CP-160332 |
0115 |
Default call progress indication provided by the UE |
13.1.0 |
14.0.0 |
|
|
2016-06 |
CT-72 |
CP-160332 |
0116 |
2 |
MMTEL session timeouts |
13.1.0 |
14.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2016-09 |
CT#73 |
CP-160518 |
0118 |
F |
Note in Annex L |
14.1.0 |
|
|
2017-03 |
CT#75 |
CP-170130 |
0119 |
6 |
B |
3GPP PS Data Off and MMTEL voice and MMTEL video |
14.2.0 |
|
2017-03 |
CT#75 |
CP-170124 |
0120 |
2 |
B |
Adding a reference to the RequestTimeout timer MO |
14.2.0 |
|
2017-12 |
CT#78 |
CP-173080 |
0121 |
3 |
B |
Response-Source header field handling completion |
15.0.0 |
|
2017-12 |
CT#78 |
CP-173071 |
0122 |
4 |
B |
IMS multimedia telephony communication service and supplementary services |
15.0.0 |
|
2017-12 |
CT#78 |
CP-173080 |
0123 |
2 |
B |
UE behaviour for MO MMTel voice call when service request failure |
15.0.0 |
|
2018-06 |
CT#80 |
CP-181060 |
0125 |
1 |
B |
MMTel -PS Data Off for 5GS |
15.1.0 |
|
2018-06 |
CT#80 |
CP-181060 |
0126 |
2 |
B |
Unified Access Control for MMTel |
15.1.0 |
|
2018-06 |
CT#80 |
CP-181074 |
0127 |
2 |
B |
3GPP PS Data Off2 and MMTEL voice and MMTEL video |
15.1.0 |
|
2018-09 |
CT#81 |
CP-182177 |
0129 |
2 |
F |
T3325 notification in Annex M |
15.2.0 |
|
2018-09 |
CT#81 |
CP-182145 |
0130 |
1 |
F |
No unified access control check when adding or removing media during MMTEL session |
15.2.0 |
|
2018-09 |
CT#81 |
CP-182145 |
0131 |
2 |
B |
Use TCP for SIP signaling in case of voice fallback to EPS without N26 interface |
15.2.0 |
|
2018-12 |
CT#82 |
CP-183056 |
0133 |
A |
Removal of EN on RequestTimeout timer |
15.3.0 |
|
|
2018-12 |
CT#82 |
CP-183044 |
0134 |
3 |
F |
Correct PS Data Off requirements for other accesses |
15.3.0 |
|
2019-06 |
CT#84 |
CP-191143 |
0137 |
1 |
B |
Multi-Device and Multi-Identity services |
16.0.0 |
|
2019-09 |
CT#85 |
CP-192046 |
0139 |
1 |
A |
Removing leftover EN |
16.1.0 |
|
2019-09 |
CT#85 |
CP-192046 |
0141 |
1 |
A |
Correction on PS data off |
16.1.0 |
|
2019-12 |
CT#86 |
CP-193092 |
0142 |
1 |
F |
Provide handover of ongoing MMTEL voice or MMTEL video from non-3GPP access indication to NAS |
16.2.0 |
|
2020-12 |
CT#90e |
CP-203214 |
0145 |
1 |
B |
Handling of lower layer congestion notification for MMTEL video |
17.0.0 |
|
2021-06 |
CT#92e |
CP-211148 |
0146 |
4 |
F |
MMTEL Voice and MMTEL Video in non-3GPP |
17.1.0 |
|
2021-06 |
CT#92e |
CP-211156 |
0147 |
1 |
B |
IMS data channel media feature tag in Accept-Contact header |
17.1.0 |
|
2022-03 |
CT#95e |
0148 |
1 |
B |
3GPP PS data off and UE in SNPN |
17.2.0 |
|
|
2022-12 |
CT#98e |
CP-223134 |
0150 |
2 |
B |
General MPS for Supplementary Services |
18.0.0 |
|
2022-12 |
CT#98e |
CP-223157 |
0151 |
1 |
F |
Indication to the NAS layer for an MT call |
18.0.0 |