11.6 3GPP PS Data Off
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
11.6.1 Data Off / MO Voice Call
11.6.1.1 Test Purpose (TP)
(1)
with { UE in PDU SESSION ACTIVE state and in 5GMM-CONNECTED mode and PS Data Off configured to “inactive” }
ensure that {
when { UE PS Data Off status is changed to “active” }
then { UE performs a PDU session modification procedure providing the PS Data Off status set to “active” }
}
(2)
with { UE being registered to IMS and with PS Data Off configured to “inactive” }
ensure that {
when { UE PS Data Off status is changed to “active” }
then { UE sends REGISTER with PS Data Off configured to “active” }
}
(3)
with { UE being registered to IMS and with PS Data Off configured to “active” }
ensure that {
when { UE is being made to initiate a voice call }
then { UE sends INVITE for voice call }
}
11.6.1.2 Conformance Requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 6.2.10. TS 24.229 clause 4.17, Rel-15. Unless otherwise stated these are Rel-16 requirements.
[TS 24.501, clause 6.2.10]
In case of PLMN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501 [8]), can be configured with up to two lists of 3GPP PS data off exempt services as specified in 3GPP TS 24.368 [17] or in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102 [22]:
a) a list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN; and
b) a list of 3GPP PS data off exempt services to be used in the VPLMN.
If only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is configured at the UE, this list shall be also used in the VPLMN.
In case of SNPN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501 [8]), can be configured with a list of 3GPP PS data off exempt services as specified in 3GPP TS 24.368 [17] for each SNPN whose entry exists in the "list of subscriber data":
a) a list of 3GPP PS data off exempt services to be used in the SNPN.
If the UE supports 3GPP PS data off, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE during UE-requested PDU session establishment procedure except for the transfer of a PDU session from non-3GPP access to 3GPP access and except for the establishment of user plane resources on the other access for the MA PDU session(see subclause 6.4.1), and during UE-requested PDU session modification procedure (see subclause 6.4.2), regardless of associated access type of the PDU session. If the UE requests a PDU session establishment procedure in order to transfer a PDU session from non-3GPP access to 3GPP access, or in order to establish user plane resources on the other access for the MA PDU session over 3GPP access or non-3GPP access, and:
a) if the 3GPP PS data off UE status has changed since the last providing to the network, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE; or
b) if the 3GPP PS data off UE status has not changed since the last providing to the network, the UE need not provide the 3GPP PS data off UE status.
The network shall support of 3GPP PS data off.
The UE shall indicate change of the 3GPP PS data off UE status for the PDU session by using the UE-requested PDU session modification procedure as specified in subclause 6.4.2.
When the 3GPP PS data off UE status is "activated":
a) the UE does not send uplink IP packets via 3GPP access except:
1) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN as specified in 3GPP TS 24.368 [17] when the UE is in its HPLMN or EHPLMN or for those services indicated in the list of 3GPP PS data off exempt services to be used in the SNPN as specified in 3GPP TS 24.368 [17] when the UE is in an SNPN;
2) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN when the UE is in the VPLMN, if only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is configured to the UE as specified in 3GPP TS 24.368 [17];
3) for those services indicated in the list of 3GPP PS data off exempt services to be used in the VPLMN when the UE is in the VPLMN, if the list of 3GPP PS data off exempt services to be used in the VPLMN is configured to the UE as specified in 3GPP TS 24.368 [17];
4) for those services indicated in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102 [22];
5) any uplink traffic due to procedures specified in 3GPP TS 24.229 [14]; and
6) any uplink traffic due to procedures specified in 3GPP TS 24.623 [20];
b) the UE does not send uplink Ethernet user data packets via 3GPP access; and
c) the UE does not send uplink Unstructured user data packets via 3GPP access.
Otherwise the UE sends uplink user data packets without restriction.
NOTE: If the UE supports 3GPP PS data off, uplink IP packets are filtered as specified in 3GPP TS 24.229 [14] in U.3.1.5.
3GPP PS data off does not restrict sending of uplink user data packets via non-3GPP access of a single access PDU session or an MA PDU session.
[TS 24.229, Rel-15, clause 4.17]
The UE and the network can support the 3GPP PS data off.
When 3GPP PS data off is supported and active, IP packets that are associated with services that are not a 3GPP PS data off exempt service are prevented from transport over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN as specified in 3GPP TS 23.228 [7]. The UE may be configured by the HPLMN or the EHPLMN with up to two indications whether a 3GPP IMS service is a 3GPP PS Data Off exempt service, one indication is valid for the UE is in the HPLMN or the EHPLMN and the other indication is valid for the UE is in the VPLMN. 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.
When 3GPP PS data off is supported and active and the UE is configured, either as specified in 3GPP TS 24.167 [8G] or in 3GPP TS 31.102 [15C], with services that are 3GPP PS data off exempt, then the UE will not send uplink IP packets related to any services that are not 3GPP PS data off exempt over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN. The UE informs the network about its 3GPP PS data off status by including a g.3gpp.ps-data-off media feature tag specified in subclause 7.9.8 in all REGISTER requests sent over GPRS IP-CAN, EPS IP-CAN or 5GS IP-CAN. The UE reregisters over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN every time the 3GPP PS data off status is changed or the UE is provided by the network with a new list of 3GPP PS data off exempt services while the 3GPP PS data off status is "active".
An AS handling a service is configured with information whether the service is a 3GPP PS data off exempt service. If the 3GPP PS data off status is active and the service is not a 3GPP PS data off exempt service, the AS prevents downlink IP packets of the service from reaching the UE over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN. The AS shall be configured with up to two indications whether a 3GPP IMS service is a 3GPP PS Data Off exempt service, one indication is valid for non-roaming users, and the other indication is valid for users roaming in the various VPLMNs with whom roaming agreements exist. When the AS is only configured with the indication valid for the UE camping in the HPLMN or the EHPLMN, the AS shall use this indication also when the UE is in the VPLMN.
[TS 24.229, Rel-15, clause U.3.1.0]
If the UE supports the 3GPP PS data off, then the UE shall in all REGISTER requests include the "+g.3gpp.ps-data-off" header field parameter defined in subclause 7.9.8 set to a value indicating the 3GPP PS data off status.
When the UE sends a REGISTER request, if the 3GPP PS data off status is "active", then the UE shall only include media feature tags associated with services that are 3GPP PS data off exempt services in the g.3gpp.icsi-ref media feature tag, as defined in subclause 7.9.2 and RFC 3840 [62], for the IMS communication services it intends to use.
If the UE is registered, and the 3GPP PS data off status is changed, then the UE shall perform a reregistration of the previously registered public user identity.
11.6.1.3 Test description
11.6.1.3.1 Pre-test conditions
System Simulator:
– 1 NR Cell connected to 5GC, default parameters.
UE:
– None.
Preamble:
– UE is in state 3N-A with IMS registered on NR cell 1 according to TS 38.508-1 [4] Table 4.4A.2-3.
11.6.1.3.2 Test procedure sequence
Table 11.6.1.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
UE is made to activate Data Off, see NOTE 1 |
– |
– |
– |
– |
|
2 |
Check: Does the UE transmit a PDU SESSION MODIFICATION REQUEST message with Data Off status set to activated? |
–> |
5GSM: PDU SESSION MODIFICATION REQUEST |
1 |
P |
|
3 |
The SS transmits an PDU SESSION MODIFICATION COMMAND message. |
<– |
5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
|
– |
EXCEPTION: Steps 4 and 5 can occur in any order |
– |
– |
– |
– |
|
4 |
the UE transmit an PDU SESSION MODIFICATION COMPLETE message. |
–> |
5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
– |
|
5 |
Check: does the UE re-register with "+g.3gpp.ps-data-off" header field parameter set to “active”? |
–> |
IMS: REGISTER |
2 |
P |
|
6 |
SS responds with 200 OK |
<– |
IMS: 200 OK |
||
|
7 |
UE is made to attempt an IMS voice call. |
– |
– |
||
|
8-12 |
Check: is the MTSI MO Voice call / 5GS procedure, steps 1-5, of Annex A.4.1a in TS 34.229-5 [41] performed? |
3 |
P |
||
|
13-15 |
Steps 10-12 of generic procedure specified in Table 4.9.15.2.2-1 of TS 38.508-1 [21] are performed. |
– |
– |
– |
– |
|
16-22 |
Check: is the MTSI MO Voice call / 5GS procedure, steps 6-12, of Annex A.4.1a in TS 34.229-5 [41] performed? |
– |
– |
3 |
P |
|
23-24 |
SS releases the call. (Steps 1-2 of Annex A.8 in TS 34.229-5 [41]) |
– |
– |
– |
– |
|
NOTE 1: This could be done by e.g. MMI or AT command. |
|||||
11.6.1.3.3 Specific message contents
Table 11.6.1.3.3-1: PDU SESSION MODIFICATION REQUEST (step 2, Table 11.6.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Extended protocol configuration options |
||||
|
Container ID n |
‘0017’H |
n assigned to next available number |
||
|
Length of container ID n contents |
1 octet |
|||
|
Container ID n contents |
‘02’H |
3GPP PS data off UE status activated |
||
Table 11.6.1.3.3-2: PDU SESSION MODIFICATION COMMAND (step 3, Table 11.6.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Extended protocol configuration options |
||||
|
Container ID n |
‘0017’H |
n assigned to next available number |
||
|
Length of container ID n contents |
0 octets |
|||
|
Container ID n contents |
empty |
3GPP PS data off support indication |
||
Table 11.6.1.3.3-3: REGISTER (step 5, Table 11.6.1.3.2-1)
|
Derivation Path: TS 34.229-1 [2], Annex A.1.1, Conditions A2, A4, A17, A32 |
||||
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|
Contact |
||||
|
feature-param |
+g.3gpp.ps-data-off=”active” |
TS 24.229 [7] |
||
11.6.2 Data Off / MO Video Call
11.6.2.1 Test Purpose (TP)
(1)
with { UE in PDU SESSION ACTIVE state and in 5GMM-CONNECTED mode and PS Data Off configured to “inactive” }
ensure that {
when { UE PS Data Off status is changed to “active” }
then { UE performs a PDU session modification procedure providing the PS Data Off status set to “active” }
}
(2)
with { UE being registered to IMS and with PS Data Off configured to “inactive” }
ensure that {
when { UE PS Data Off status is changed to “active” }
then { UE sends REGISTER with PS Data Off configured to “active” }
}
(3)
with { UE being registered to IMS and with PS Data Off configured to “active” }
ensure that {
when { UE is being made to initiate a video call }
then { UE does not send INVITE for video call }
}
11.6.2.2 Conformance Requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 6.2.10. TS 24.229 clause 4.17, Rel-15. Unless otherwise stated these are Rel-16 requirements.
[TS 24.501, clause 6.2.10]
In case of PLMN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501 [8]), can be configured with up to two lists of 3GPP PS data off exempt services as specified in 3GPP TS 24.368 [17] or in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102 [22]:
a) a list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN; and
b) a list of 3GPP PS data off exempt services to be used in the VPLMN.
If only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is configured at the UE, this list shall be also used in the VPLMN.
In case of SNPN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501 [8]), can be configured with a list of 3GPP PS data off exempt services as specified in 3GPP TS 24.368 [17] for each SNPN whose entry exists in the "list of subscriber data":
a) a list of 3GPP PS data off exempt services to be used in the SNPN.
If the UE supports 3GPP PS data off, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE during UE-requested PDU session establishment procedure except for the transfer of a PDU session from non-3GPP access to 3GPP access and except for the establishment of user plane resources on the other access for the MA PDU session(see subclause 6.4.1), and during UE-requested PDU session modification procedure (see subclause 6.4.2), regardless of associated access type of the PDU session. If the UE requests a PDU session establishment procedure in order to transfer a PDU session from non-3GPP access to 3GPP access, or in order to establish user plane resources on the other access for the MA PDU session over 3GPP access or non-3GPP access, and:
a) if the 3GPP PS data off UE status has changed since the last providing to the network, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE; or
b) if the 3GPP PS data off UE status has not changed since the last providing to the network, the UE need not provide the 3GPP PS data off UE status.
The network shall support of 3GPP PS data off.
The UE shall indicate change of the 3GPP PS data off UE status for the PDU session by using the UE-requested PDU session modification procedure as specified in subclause 6.4.2.
When the 3GPP PS data off UE status is "activated":
a) the UE does not send uplink IP packets via 3GPP access except:
1) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN as specified in 3GPP TS 24.368 [17] when the UE is in its HPLMN or EHPLMN or for those services indicated in the list of 3GPP PS data off exempt services to be used in the SNPN as specified in 3GPP TS 24.368 [17] when the UE is in an SNPN;
2) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN when the UE is in the VPLMN, if only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is configured to the UE as specified in 3GPP TS 24.368 [17];
3) for those services indicated in the list of 3GPP PS data off exempt services to be used in the VPLMN when the UE is in the VPLMN, if the list of 3GPP PS data off exempt services to be used in the VPLMN is configured to the UE as specified in 3GPP TS 24.368 [17];
4) for those services indicated in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102 [22];
5) any uplink traffic due to procedures specified in 3GPP TS 24.229 [14]; and
6) any uplink traffic due to procedures specified in 3GPP TS 24.623 [20];
b) the UE does not send uplink Ethernet user data packets via 3GPP access; and
c) the UE does not send uplink Unstructured user data packets via 3GPP access.
Otherwise the UE sends uplink user data packets without restriction.
NOTE: If the UE supports 3GPP PS data off, uplink IP packets are filtered as specified in 3GPP TS 24.229 [14] in U.3.1.5.
3GPP PS data off does not restrict sending of uplink user data packets via non-3GPP access of a single access PDU session or an MA PDU session.
[TS 24.229, Rel-15, clause 4.17]
The UE and the network can support the 3GPP PS data off.
When 3GPP PS data off is supported and active, IP packets that are associated with services that are not a 3GPP PS data off exempt service are prevented from transport over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN as specified in 3GPP TS 23.228 [7]. The UE may be configured by the HPLMN or the EHPLMN with up to two indications whether a 3GPP IMS service is a 3GPP PS Data Off exempt service, one indication is valid for the UE is in the HPLMN or the EHPLMN and the other indication is valid for the UE is in the VPLMN. 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.
When 3GPP PS data off is supported and active and the UE is configured, either as specified in 3GPP TS 24.167 [8G] or in 3GPP TS 31.102 [15C], with services that are 3GPP PS data off exempt, then the UE will not send uplink IP packets related to any services that are not 3GPP PS data off exempt over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN. The UE informs the network about its 3GPP PS data off status by including a g.3gpp.ps-data-off media feature tag specified in subclause 7.9.8 in all REGISTER requests sent over GPRS IP-CAN, EPS IP-CAN or 5GS IP-CAN. The UE reregisters over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN every time the 3GPP PS data off status is changed or the UE is provided by the network with a new list of 3GPP PS data off exempt services while the 3GPP PS data off status is "active".
An AS handling a service is configured with information whether the service is a 3GPP PS data off exempt service. If the 3GPP PS data off status is active and the service is not a 3GPP PS data off exempt service, the AS prevents downlink IP packets of the service from reaching the UE over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN. The AS shall be configured with up to two indications whether a 3GPP IMS service is a 3GPP PS Data Off exempt service, one indication is valid for non-roaming users, and the other indication is valid for users roaming in the various VPLMNs with whom roaming agreements exist. When the AS is only configured with the indication valid for the UE camping in the HPLMN or the EHPLMN, the AS shall use this indication also when the UE is in the VPLMN.
[TS 24.229, Rel-15, clause U.3.1.0]
If the UE supports the 3GPP PS data off, then the UE shall in all REGISTER requests include the "+g.3gpp.ps-data-off" header field parameter defined in subclause 7.9.8 set to a value indicating the 3GPP PS data off status.
When the UE sends a REGISTER request, if the 3GPP PS data off status is "active", then the UE shall only include media feature tags associated with services that are 3GPP PS data off exempt services in the g.3gpp.icsi-ref media feature tag, as defined in subclause 7.9.2 and RFC 3840 [62], for the IMS communication services it intends to use.
If the UE is registered, and the 3GPP PS data off status is changed, then the UE shall perform a reregistration of the previously registered public user identity.
11.6.2.3 Test description
11.6.2.3.1 Pre-test conditions
System Simulator:
– 1 NR Cell connected to 5GC, default parameters.
UE:
– None.
Preamble:
– UE is in state 3N-A with IMS registered on NR cell 1 according to TS 38.508-1 [4] Table 4.4A.2-3.
11.6.2.3.2 Test procedure sequence
Table 11.6.2.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
UE is made to activate Data Off, see NOTE 1. |
– |
– |
– |
– |
|
2 |
Check: Does the UE transmit a PDU SESSION MODIFICATION REQUEST message with Data Off status set to activated? |
–> |
5GSM: PDU SESSION MODIFICATION REQUEST |
1 |
P |
|
3 |
The SS transmits an PDU SESSION MODIFICATION COMMAND message. |
<– |
5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
|
– |
EXCEPTION: Steps 4 and 5 can occur in any order |
– |
– |
– |
– |
|
4 |
the UE transmit an PDU SESSION MODIFICATION COMPLETE message. |
–> |
5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
– |
|
5 |
Check: does the UE re-register with "+g.3gpp.ps-data-off" header field parameter set to “active”? |
–> |
IMS: REGISTER |
2 |
P |
|
6 |
SS responds with 200 OK |
<– |
IMS: 200 OK |
||
|
7 |
UE is made to attempt an IMS video call. |
– |
– |
||
|
8 |
Check: Does the UE send a SIP INVITE within 30 seconds? |
– |
– |
3 |
F |
|
NOTE 1: This could be done by e.g. MMI or AT command. |
|||||
11.6.2.3.3 Specific message contents
Table 11.6.2.3.3-1: PDU SESSION MODIFICATION REQUEST (step 2, Table 11.6.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Extended protocol configuration options |
||||
|
Container ID n |
‘0017’H |
n assigned to next available number |
||
|
Length of container ID n contents |
1 octet |
|||
|
Container ID n contents |
‘02’H |
3GPP PS data off UE status activated |
||
Table 11.6.2.3.3-2: PDU SESSION MODIFICATION COMMAND (step 3, Table 11.6.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-9 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Extended protocol configuration options |
||||
|
Container ID n |
‘0017’H |
n assigned to next available number |
||
|
Length of container ID n contents |
0 octets |
|||
|
Container ID n contents |
empty |
3GPP PS data off support indication |
||
Table 11.6.2.3.3-3: REGISTER (step 5, Table 11.6.2.3.2-1)
|
Derivation Path: TS 34.229-1 [2], Annex A.1.1, Conditions A2, A4, A17, A32 |
||||
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|
Contact |
||||
|
feature-param |
+g.3gpp.ps-data-off=”active” |
TS 24.229 [7] |
||
11.6.3 Data Off / SMSoIP
11.6.3.1 Test Purpose (TP)
(1)
with { UE in PDU SESSION ACTIVE state and in 5GMM-CONNECTED mode and PS Data Off configured to “inactive” }
ensure that {
when { UE PS Data Off status is changed to “active” }
then { UE performs a PDU session modification procedure providing the PS Data Off status set to “active” }
}
(2)
with { UE being registered to IMS and with PS Data Off configured to “inactive” }
ensure that {
when { UE PS Data Off status is changed to “active” }
then { UE sends REGISTER with PS Data Off configured to “active” }
}
(3)
with { UE being registered to IMS and with PS Data Off configured to “active” }
ensure that {
when { UE is being made to send an SMS over IP }
then { UE sends a SIP MESSAGE request containing a short message }
}
11.6.3.2 Conformance Requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 6.2.10. TS 24.341, clause 5.3.1.2, 5.3.1.3 and TS 24.229 clause 4.17, Rel-15. Unless otherwise stated these are Rel-16 requirements.
[TS 24.341, clause 5.3.1.2]:
When an SM-over-IP sender wants to submit an SM over IP, the SM-over-IP sender shall send a SIP MESSAGE request with the following information:
a) the Request-URI, which shall contain the PSI of the SC of the SM-over-IP sender;
NOTE 1: The PSI of the SC can be SIP URI or tel URI based on operator policy. The PSI of the SC can be obtained using one of the following methods in the priority order listed below:
1) provided by the user;
2) if UICC is used, then:
– if present in the ISIM, then the PSI of the SC is obtained from the EFPSISMSC in DF_TELECOM of the ISIM as per 3GPP TS 31.103 [18];
– if not present on the ISIM, then the PSI of the SC is obtained from the EFPSISMSC in DF_TELECOM of the USIM as per 3GPP TS 31.102 [19]; or
– if neither present on the ISIM nor on the USIM, then the PSI of the SC contains the TS‑Service-Centre-Address stored in the EFSMSP in DF_TELECOM as per 3GPP TS 31.102 [19]. If the PSI of the SC is based on the E.164 number from the TS‑Service-Centre-Address stored in the EFSMSP in DF_TELECOM then the URI constructed can be either a tel URI or a SIP URI (using the "user=phone" SIP URI parameter format).
3) if SIM is used instead of UICC, then the PSI of the SC contains the TS‑Service Centre Address stored in the EFSMSP in DF_TELECOM as per 3GPP TS 51.011 [20]. If the PSI of the SC is based on the E.164 number from the TS‑Service-Centre-Address stored in the EFSMSP in DF_TELECOM then the URI constructed can be either a tel URI or a SIP URI (using the "user=phone" SIP URI parameter format); or
4) if neither the UICC nor SIM is used, then how the PSI of the SC is configured and obtained is through means outside the scope of this specification.
b) the From header, which shall contain a public user identity of the SM-over-IP sender;
NOTE 2: The IP-SM-GW will have to use an address of the SM-over-IP sender that the SC can process (i.e. an E.164 number). This address will come from a tel URI in a P-Asserted-Identity header (as defined in RFC 3325 [13]) placed in the SIP MESSAGE request by the P-CSCF or S-CSCF.
NOTE 3: The SM-over-IP sender has to store the Call-ID of the SIP MESSAGE request, so it can associate the appropriate SIP MESSAGE request including a submit report with it.
c) the To header, which shall contain the SC of the SM-over-IP sender;
d) the Content-Type header, which shall contain "application/vnd.3gpp.sms"; and
e) the body of the request shall contain an RP-DATA message as defined in 3GPP TS 24.011 [8], including the SMS headers and the SMS user information encoded as specified in 3GPP TS 23.040 [3].
NOTE 4: The address of the SC is included in the RP-DATA message content. The address of the SC included in the RP-DATA message content is stored in the EFSMSP in DF_TELECOM of the (U)SIM of the SM-over-IP sender.
NOTE 5: The SM-over-IP sender will use content transfer encoding of type "binary" for the encoding of the SM in the body of the SIP MESSAGE request.
NOTE 6: Both the address of the SC and the PSI of the SC can be configured in the EFPSISMSC in DF_TELECOM of the USIM and ISIM respectively using the USAT as per 3GPP TS 31.111 [21].
The SM-over-IP sender may request the SC to return the status of the submitted message. The support of status report capabilities is optional for the SC.
When a SIP MESSAGE request including a submit report in the "vnd.3gpp.sms" payload is received, the SM-over-IP sender shall:
– if SM-over-IP sender supports In-Reply-To header usage and the In-Reply-To header indicates that the request corresponds to a short message submitted by the SM-over-IP sender, generate a 200 (OK) SIP response according to RFC 3428 [14].
if SM-over-IP sender supports In-Reply-To header usage and the In-Reply-To header indicates that the request does not correspond to a short message submitted by the SM-over-IP sender, a 488 (Not Acceptable here) SIP response according to RFC 3428 [14].
– if SM-over-IP sender does not support In-Reply-To header usage, generate a 200 (OK) SIP response according to RFC 3428 [14]; and extract the payload encoded according to 3GPP TS 24.011 [8] for RP-ACK or RP-ERROR.
[TS 24.341 clause 5.3.1.3]:
When a SIP MESSAGE request including a status report in the "vnd.3gpp.sms" payload is delivered, the SM-over-IP sender shall:
– generate a SIP response according to RFC 3428 [14];
– extract the payload encoded according to 3GPP TS 24.011 [8] for RP-DATA; and
– create a delivery report for the status report as described in subclause 5.3.2.4. The content of the delivery report is defined in 3GPP TS 24.011 [8].
[TS 24.341 clause 5.3.2.4]:
When an SM-over-IP receiver wants to send an SM delivery report over IP, the SM-over-IP receiver shall send a SIP MESSAGE request with the following information:
a) the Request-URI, which shall contain the IP-SM-GW;
NOTE 1: The address of the IP-SM-GW is received in the P-Asserted-Identity header in the SIP MESSAGE request including the delivered short message.
b) the From header, which shall contain a public user identity of the SM-over-IP receiver.
c) the To header, which shall contain the IP-SM-GW;
b) the Content-Type header shall contain "application/vnd.3gpp.sms"; and
c) the body of the request shall contain the RP-ACK or RP-ERROR message for the SM delivery report, as defined in 3GPP TS 24.011 [8].
NOTE 2: The SM-over-IP sender will use content transfer encoding of type "binary" for the encoding of the SM in the body of the SIP MESSAGE request.
[TS 24.501, clause 6.2.10]
In case of PLMN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501 [8]), can be configured with up to two lists of 3GPP PS data off exempt services as specified in 3GPP TS 24.368 [17] or in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102 [22]:
a) a list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN; and
b) a list of 3GPP PS data off exempt services to be used in the VPLMN.
If only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is configured at the UE, this list shall be also used in the VPLMN.
In case of SNPN, a UE, which supports 3GPP PS data off (see 3GPP TS 23.501 [8]), can be configured with a list of 3GPP PS data off exempt services as specified in 3GPP TS 24.368 [17] for each SNPN whose entry exists in the "list of subscriber data":
a) a list of 3GPP PS data off exempt services to be used in the SNPN.
If the UE supports 3GPP PS data off, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE during UE-requested PDU session establishment procedure except for the transfer of a PDU session from non-3GPP access to 3GPP access and except for the establishment of user plane resources on the other access for the MA PDU session(see subclause 6.4.1), and during UE-requested PDU session modification procedure (see subclause 6.4.2), regardless of associated access type of the PDU session. If the UE requests a PDU session establishment procedure in order to transfer a PDU session from non-3GPP access to 3GPP access, or in order to establish user plane resources on the other access for the MA PDU session over 3GPP access or non-3GPP access, and:
a) if the 3GPP PS data off UE status has changed since the last providing to the network, the UE shall provide the 3GPP PS data off UE status in the Extended protocol configuration options IE; or
b) if the 3GPP PS data off UE status has not changed since the last providing to the network, the UE need not provide the 3GPP PS data off UE status.
The network shall support of 3GPP PS data off.
The UE shall indicate change of the 3GPP PS data off UE status for the PDU session by using the UE-requested PDU session modification procedure as specified in subclause 6.4.2.
When the 3GPP PS data off UE status is "activated":
a) the UE does not send uplink IP packets via 3GPP access except:
1) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN as specified in 3GPP TS 24.368 [17] when the UE is in its HPLMN or EHPLMN or for those services indicated in the list of 3GPP PS data off exempt services to be used in the SNPN as specified in 3GPP TS 24.368 [17] when the UE is in an SNPN;
2) for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN when the UE is in the VPLMN, if only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is configured to the UE as specified in 3GPP TS 24.368 [17];
3) for those services indicated in the list of 3GPP PS data off exempt services to be used in the VPLMN when the UE is in the VPLMN, if the list of 3GPP PS data off exempt services to be used in the VPLMN is configured to the UE as specified in 3GPP TS 24.368 [17];
4) for those services indicated in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102 [22];
5) any uplink traffic due to procedures specified in 3GPP TS 24.229 [14]; and
6) any uplink traffic due to procedures specified in 3GPP TS 24.623 [20];
b) the UE does not send uplink Ethernet user data packets via 3GPP access; and
c) the UE does not send uplink Unstructured user data packets via 3GPP access.
Otherwise the UE sends uplink user data packets without restriction.
NOTE: If the UE supports 3GPP PS data off, uplink IP packets are filtered as specified in 3GPP TS 24.229 [14] in U.3.1.5.
3GPP PS data off does not restrict sending of uplink user data packets via non-3GPP access of a single access PDU session or an MA PDU session.
[TS 24.229, Rel-15, clause 4.17]
The UE and the network can support the 3GPP PS data off.
When 3GPP PS data off is supported and active, IP packets that are associated with services that are not a 3GPP PS data off exempt service are prevented from transport over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN as specified in 3GPP TS 23.228 [7]. The UE may be configured by the HPLMN or the EHPLMN with up to two indications whether a 3GPP IMS service is a 3GPP PS Data Off exempt service, one indication is valid for the UE is in the HPLMN or the EHPLMN and the other indication is valid for the UE is in the VPLMN. 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.
When 3GPP PS data off is supported and active and the UE is configured, either as specified in 3GPP TS 24.167 [8G] or in 3GPP TS 31.102 [15C], with services that are 3GPP PS data off exempt, then the UE will not send uplink IP packets related to any services that are not 3GPP PS data off exempt over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN. The UE informs the network about its 3GPP PS data off status by including a g.3gpp.ps-data-off media feature tag specified in subclause 7.9.8 in all REGISTER requests sent over GPRS IP-CAN, EPS IP-CAN or 5GS IP-CAN. The UE reregisters over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN every time the 3GPP PS data off status is changed or the UE is provided by the network with a new list of 3GPP PS data off exempt services while the 3GPP PS data off status is "active".
An AS handling a service is configured with information whether the service is a 3GPP PS data off exempt service. If the 3GPP PS data off status is active and the service is not a 3GPP PS data off exempt service, the AS prevents downlink IP packets of the service from reaching the UE over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN. The AS shall be configured with up to two indications whether a 3GPP IMS service is a 3GPP PS Data Off exempt service, one indication is valid for non-roaming users, and the other indication is valid for users roaming in the various VPLMNs with whom roaming agreements exist. When the AS is only configured with the indication valid for the UE camping in the HPLMN or the EHPLMN, the AS shall use this indication also when the UE is in the VPLMN.
[TS 24.229, Rel-15, clause U.3.1.0]
If the UE supports the 3GPP PS data off, then the UE shall in all REGISTER requests include the "+g.3gpp.ps-data-off" header field parameter defined in subclause 7.9.8 set to a value indicating the 3GPP PS data off status.
When the UE sends a REGISTER request, if the 3GPP PS data off status is "active", then the UE shall only include media feature tags associated with services that are 3GPP PS data off exempt services in the g.3gpp.icsi-ref media feature tag, as defined in subclause 7.9.2 and RFC 3840 [62], for the IMS communication services it intends to use.
If the UE is registered, and the 3GPP PS data off status is changed, then the UE shall perform a reregistration of the previously registered public user identity.
11.6.3.3 Test description
11.6.3.3.1 Pre-test conditions
System Simulator:
– 1 NR Cell connected to 5GC, default parameters.
UE:
– None.
Preamble:
– UE is in state 3N-A with IMS registered on NR cell 1 according to TS 38.508-1 [4] Table 4.4A.2-3.
11.6.3.3.2 Test procedure sequence
Table 11.6.3.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
UE is made to activate Data Off, see NOTE 1. |
– |
– |
– |
– |
|
2 |
Check: Does the UE transmit a PDU SESSION MODIFICATION REQUEST message with Data Off status set to activated? |
–> |
5GSM: PDU SESSION MODIFICATION REQUEST |
1 |
P |
|
3 |
The SS transmits an PDU SESSION MODIFICATION COMMAND message. |
<– |
5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
|
– |
EXCEPTION: Steps 4 and 5 can occur in any order |
– |
– |
– |
– |
|
4 |
the UE transmit an PDU SESSION MODIFICATION COMPLETE message. |
–> |
5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
– |
|
5 |
Check: does the UE re-register with "+g.3gpp.ps-data-off" header field parameter set to “active”? |
–> |
IMS: REGISTER |
2 |
P |
|
6 |
SS responds with 200 OK |
<– |
IMS: 200 OK |
– |
– |
|
7 |
UE is made to attempt to send an SMSoIP message. |
– |
– |
||
|
8 |
Check: Is the IMS MO SMS / 5GS procedure performed according to steps 1-8 of annex A.13 in TS 34.229-5? |
– |
– |
3 |
P |
|
NOTE 1: This could be done by e.g. MMI or AT command. |
|||||
11.6.3.3.3 Specific message contents
Table 11.6.3.3.3-1: PDU SESSION MODIFICATION REQUEST (step 2, Table 11.6.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Extended protocol configuration options |
||||
|
Container ID n |
‘0017’H |
n assigned to next available number |
||
|
Length of container ID n contents |
1 octet |
|||
|
Container ID n contents |
‘02’H |
3GPP PS data off UE status activated |
||
Table 11.6.3.3.3-2: PDU SESSION MODIFICATION COMMAND (step 3, Table 11.6.3.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-9 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Extended protocol configuration options |
||||
|
Container ID n |
‘0017’H |
n assigned to next available number |
||
|
Length of container ID n contents |
0 octets |
|||
|
Container ID n contents |
empty |
3GPP PS data off support indication |
||
Table 11.6.3.3.3-3: REGISTER (step 5, Table 11.6.3.3.2-1)
|
Derivation Path: TS 34.229-1 [2], Annex A.1.1, Conditions A2, A4, A17, A32 |
||||
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|
Contact |
||||
|
feature-param |
+g.3gpp.ps-data-off=”active” |
TS 24.229 [7] |
||