J.3 Application usage of SIP
24.1733GPPIMS Multimedia telephony communication service and supplementary servicesRelease 18Stage 3TS
J.3.1 Procedures at the UE
J.3.1.1 3GPP PS data off
J.3.1.1.1 General
The UE may support the 3GPP PS data off.
If the UE supports the 3GPP PS data off:
a) the UE can be configured with:
1) up to two indications whether the MMTEL voice is a 3GPP PS data off exempt service, one indication is valid for the UE camping in the HPLMN or the EHPLMN, and the other indication is valid for any VPLMN the UE is roaming in; and
2) up to two indications whether the MMTEL video is a 3GPP PS data off exempt service, one indication is valid for the UE camping in the HPLMN or the EHPLMN, and the other indication is valid for any VPLMN the UE is roaming in;
b) the UE may support being configured with the indication whether the MMTEL voice is a 3GPP PS data off exempt service using one or more of the following methods:
1) the EF3GPPPSDATAOFF described in 3GPP TS 31.102 [38];
2) the MMTEL_voice_exempt node of 3GPP TS 24.275 [36], if the UE is in the HPLMN or the EHPLMN; and
3) the MMTEL_voice_roaming_exempt node of 3GPP TS 24.275 [36], if the UE is in the VPLMN.
If the UE is configured with both the MMTEL_voice_exempt node of 3GPP TS 24.275 [36] and the EF3GPPPSDATAOFF described in 3GPP TS 31.102 [38], then the EF3GPPPSDATAOFF shall take precedence;
If the UE is configured with both the MMTEL_voice_roaming_exempt node of 3GPP TS 24.275 [36] and the EF3GPPPSDATAOFF described in 3GPP TS 31.102 [38], then the EF3GPPPSDATAOFF shall take precedence; and
c) the UE may support being configured with the indication whether the MMTEL video is a 3GPP PS data off exempt service using one or more of the following methods:
1) the EF3GPPPSDATAOFF described in 3GPP TS 31.102 [38];
2) the MMTEL_video_exempt node of 3GPP TS 24.275 [36], if the UE is in the HPLMN or the EHPLMN; and
3) the MMTEL_video_roaming_exempt node of 3GPP TS 24.275 [36], if the UE is in the VPLMN.
If the UE is configured with both the MMTEL_video_exempt node of 3GPP TS 24.275 [36] and the EF3GPPPSDATAOFF described in 3GPP TS 31.102 [38], then the EF3GPPPSDATAOFF shall take precedence;
If the UE is configured with both the MMTEL_video_roaming_exempt node of 3GPP TS 24.275 [36] and the EF3GPPPSDATAOFF described in 3GPP TS 31.102 [38], then the EF3GPPPSDATAOFF shall take precedence.
When the UE is only configured with the indication valid for the UE camping in the HPLMN or the EHPLMN, the UE shall use this indication also when the UE is in the VPLMN.
J.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 an EPS IP-CAN bearer, 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 an EPS IP-CAN bearer, 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 EPS IP-CAN bearer, 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 an EPS IP-CAN bearer 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 an EPS IP-CAN bearer, 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 an EPS IP-CAN bearer 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 EPS IP-CAN bearer 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 EPS IP-CAN bearer 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 EPS IP-CAN bearer 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.
J.3.2 Procedures at the multimedia telephony application server
J.3.2.1 3GPP PS data off
A multimedia telephony application server supporting the 3GPP PS data off can be configured with:
1) up to two indications whether the MMTEL voice is a 3GPP PS data off exempt service, one indication is valid for the UE camping in the HPLMN or the EHPLMN, and the other indication is valid for any VPLMN the UE is roaming in; and
2) up to two indications whether the MMTEL video is a 3GPP PS data off exempt service, one indication is valid for the UE camping in the HPLMN or the EHPLMN, and the other indication is valid for any VPLMN the UE is roaming in.
When the multimedia telephony application server is only configured with the indication valid for the UE camping in the HPLMN or the EHPLMN, the multimedia telephony application server shall use this indication also when the UE is in the VPLMN.
If the multimedia telephony application server supports the 3GPP PS data off, the multimedia telephony application server shall support obtaining registration state information from a received third-party SIP REGISTER request including information contained in the body of the third-party SIP REGISTER request as specified in 3GPP TS 24.229 [13], of the served UE.
If a received registration state information of the served UE indicates a Contact header field with the g.3gpp.ps-data-off media feature tag with the "active" value:
a) the multimedia telephony application server 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 with:
1) an SDP offer; or
2) an SDP answer;
containing 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;
towards a contact address (or via a registration flow) of the served UE such that the contact address (or the registration flow) was registered or re-registered by a SIP REGISTER request with a P-Access-Network-Info header field with "3GPP-GERAN", "3GPP-UTRAN", "3GPP-E-UTRAN" or "3GPP-NR" access class, and with the "network-provided" header field parameter;
b) if the multimedia telephony application server is not configured with indication that MMTEL voice is a 3GPP PS data off exempt service for the served UE, the multimedia telephony application server shall not send according to 3GPP TS 24.229 [13] a SIP message related to the IMS multimedia telephony communication service with:
1) an SDP offer; or
2) an SDP answer;
containing media streams:
1) with only audio;
2) with only real-time text; or
3) with only audio and real-time text;
towards a contact address (or via a registration flow) of the served UE such that the contact address (or the registration flow) was registered or re-registered by a SIP REGISTER request with a P-Access-Network-Info header field with "3GPP-GERAN", "3GPP-UTRAN", "3GPP-E-UTRAN" or "3GPP-NR" access class, and with the "network-provided" header field parameter; and
c) if the multimedia telephony application server is not configured with indication that MMTEL video is a 3GPP PS data off exempt service for the served UE, the multimedia telephony application server 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, with:
1) an SDP offer; or
2) an SDP answer;
containing media streams with video towards a contact address (or via a registration flow) of the served UE such that the contact address (or the registration flow) was registered or re-registered by a SIP REGISTER request with a P-Access-Network-Info header field with "3GPP-GERAN", "3GPP-UTRAN", "3GPP-E-UTRAN" or "3GPP-NR" access class, and with the "network-provided" header field parameter.
Annex K (normative):
IP-Connectivity Access Network specific concepts when using GPRS to access IM CN subsystem