G.15 Supplementary Services

34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

G.15.1 Originating Identification Presentation / WLAN

G.15.1.1 Definition

Test to verify that the UE activates and deactivates IMS Multimedia Telephony Originating Identification Presentation. This process is described in 3GPP TS 24.607 [102].

G.15.1.2 Conformance requirement

As described in clause 15.1.2.

G.15.1.3 Test purpose

As described in clause 15.1.3.

G.15.1.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC. UE is configured with the name of the XCAP root directory on the XCAP server and the user’s directory name. If needed the UE is also configured with the HTTP Digest password to be used for XCAP. UE has activated the IP-CAN to the Evolved Packet Core (EPC) via Wireless Local Access Network (WLAN) with SS.

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2.

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Originating Identification Presentation, at step 7 deactivation of Originating Identification Presentation is respectively triggered at the UE.

G.15.1.5 Test requirements

As described in clause 15.1.5.

G.15.2 Originating Identification Restriction / WLAN

G.15.2.1 Definition

Test to verify that the UE correctly invokes the IMS Multimedia Telephony Originating Identification Restriction. This process is described in 3GPP TS 24.607 [102].

G.15.2.2 Conformance requirement

As described in clause 15.2a.2.

G.15.2.3 Test purpose

As described in clause 15.2a.3.

G.15.2.4 Method of test

Initial conditions

Same as clause G.12.1 with the following addition:

The UE is configured for Originating Identification Restriction

Test procedure

As described in clause 15.2a.4, steps 1-14. Except, steps 2-13 replaced by steps 1-8 in C.21a.

G.15.2.5 Test requirements

As described in clause 15.2a.5.

G.15.3 Terminating Identification Presentation / WLAN

G.15.3.1 Definition

Test to verify that the UE activates and deactivates IMS Multimedia Telephony Terminating Identification Presentation. This process is described in 3GPP TS 24.608 [103].

G.15.3.2 Conformance requirement

As described in clause 15.3.2.

G.15.3.3 Test purpose

As described in clause 15.3.3.

G.15.3.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to annex C.29.2.

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Terminating Identification Presentation, at step 7 deactivation of Terminating Identification Presentation is respectively triggered at the UE.

G.15.3.5 Test requirements

As described in clause 15.3.5.

G.15.4 Terminating Identification Restriction / WLAN

G.15.4.1 Definition

Test to verify that the UE correctly invokes the IMS Multimedia Telephony Terminating Identification Restriction. This process is described in 3GPP TS 24.608 [103].

G.15.4.2 Conformance requirement

As described in clause 15.4a.2.

G.15.4.3 Test purpose

As described in clause 15.4a.3.

G.15.4.4 Method of test

Initial conditions

Same as clause G.12.2 with the following addition:

The UE is configured for Terminating Identification Restriction

Test procedure

NOTE: Only the IMS procedure relevant to the test purpose is described below.

Step	Direction		Message	Comment
	UE	SS
1-5			Steps 1-5 defined in annex C.11a	MTSI MT speech call.
6				Make UE accept the speech offer with Terminating Identification Restriction
7-8			Steps 6-7 defined in annex C.11a	MTSI MT speech call.

Specific Message Contents

183 Session Progress (Step 2A)

Use the default message "183 Session Progress" in annex A.2.3 with the following exceptions:

Header/param

Value/remark

Reference

Privacy

RFC 3323 [135]

RFC 3325 [89]

180 Ringing (Step 3)

Use the default message “180 Ringing for INVITE” in annex A.2.6 with the following exceptions:

Header/param

Value/remark

Reference

Privacy

RFC 3323 [135]

RFC 3325 [136]

200 Ok (Step 7)

Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1 with the following exceptions:

Header/param

Value/remark

Reference

Privacy

RFC 3323 [135]

RFC 3325 [136]

G.15.4.5 Test requirements

The UE shall send requests and responses as described in clause G.15.4.4.

G.15.5 Communication forwarding unconditional / WLAN

G.15.5.1 Definition

Test to verify that the UE activates and deactivates IMS Multimedia Telephony Communication Forwarding unconditional. This process is described in 3GPP TS 24.604 [106].

G.15.5.2 Conformance requirement

As described in clause 15.5.2.

G.15.5.3 Test purpose

As described in clause 15.5.3.

G.15.5.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2.

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Communication Forwarding unconditional, at step 7 deactivation of Communication Forwarding unconditional is respectively triggered at the UE.

G.15.5.5 Test requirements

As described in clause 15.5.5.

G.15.6 Communication forwarding on non Reply: activation / WLAN

G.15.6.1 Definition

Test to verify that the UE activates and deactivates IMS Multimedia Telephony Communication Forwarding for the case when user does not answer to the phone. This process is described in 3GPP TS 24.604 [106].

G.15.6.2 Conformance requirement

As described in clause 15.7.2.

G.15.6.3 Test purpose

As described in clause 15.7.3.

G.15.6.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2.

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Communication Forwarding on non Reply, at step 7 deactivation of Communication Forwarding on non Reply is respectively triggered at the UE.

G.15.6.5 Test requirements

As described in clause 15.7.5

G.15.7 Communication forwarding on non reply: MO call initiation / WLAN

G.15.7.1 Definition

Test to verify that the MTSI MO UE correctly handles session setup where call is being forwarded due to no reply. This process is described in 3GPP TS 24.604 [106], clauses 4.2.1, 4.5.2.1 and A.1.3 and 3GPP TS 24.229 [10], clause 9.2.3

G.15.7.2 Conformance requirement

As described in clause 15.8.2.

G.15.7.3 Test purpose

As described in clause 15.8.3.

G.15.7.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC. UE has activated the IP-CAN to the Evolved Packet Core (EPC) via Wireless Local Access Network (WLAN) with SS. The UE has registered to IMS according the procedure C.2c.

Test procedure

1-6) Steps 1-6, procedure C.21a.

7) SS responds to the INVITE with a valid 181 Call Is Being Forwarded response (simulate the UE to which call was forwarded)

8) SS responds to the INVITE request with 180 Ringing response.

9) As the 180 Ringing response was sent reliably, UE sends a PRACK request.

10) SS responds to PRACK with 200 OK.

11) SS responds to the INVITE request with a 200 OK response.

12) SS waits for the UE to send an ACK to acknowledge receipt of the 200 OK for INVITE.

13) Call is released on the UE. SS waits the UE to send a BYE request.

14) SS responds to the BYE request with a 200 OK response.

Expected sequence

NOTE: Only the IMS procedure relevant to the test purpose is described below.

Step	Direction		Message	Comment
	UE	SS
1-6			Steps 1-6 as defined in Annex C.21a
7	🡨		181 Call is being forwarded	SS sends 181 response to indicate that call forwarding has been started as the user did not answer to the phone
8	🡨		180 Ringing	The SS sends 180 Ringing response to the UE
9	🡪		PRACK	UE acknowledges the receipt of 180 response by sending PRACK.
10	🡨		200 OK	The SS responds PRACK with 200 OK.
11	🡨		200 OK	The SS responds INVITE with 200 OK to indicate that the virtual remote UE had answered the call
12	🡪		ACK	The UE acknowledges the receipt of 200 OK for INVITE
13	🡪		BYE	The UE releases the call with BYE
14	🡨		200 OK	The SS sends 200 OK for BYE

Specific Message Contents

180 Ringing (Step 8)

Use the default message “180 Ringing for INVITE” in annex A.2.6 applying condition A3 (Response sent reliably) and with the following exceptions:

Header/param	Value/remark
To
tag	different tag must be used than the one used in steps 3-9 as this response is now from another UE and belongs to another dialog instance. Note that this new tag must be used within the rest of the steps (10-17) in this test case instead of the tag used within steps 3-9.
Contact
addr-spec	different URI must be used than the one used in step 3 as this is supposed now to represent another UE to which the call is being forwarded.. Note that this new Contact must be used within the rest of the steps (13-14) in this test case.
History-Info
hi-targeted-to-uri	Same value as in the 181 response of step 7
hi-index	Same value as in the 181 response of step 7
Require
option-tag	precondition
Content-Type
media-type	application/sdp
Message-body	Same contents as specified in step 4 annex C.21a except for o-line: o=- 22222222 22222222 IN (addrtype) (unicast-address for new remote UE).

200 OK (Step 11)

Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1 with the following exceptions:

Header/param	Value/remark
Contact
addr-spec	Same value as in the 180 response of step 8
History-Info
hi-targeted-to-uri	Same value as in the 181 response of step 7
hi-index	Same value as in the 181 response of step 7

G.15.7.5 Test requirements

The UE shall send requests and responses as described in clause G.15.7.4.

G.15.8 Communication Forwarding on Busy / WLAN

G.15.8.1 Definition

Test to verify that the UE activates and deactivates IMS Multimedia Telephony Communication Forwarding for the case when user is busy. This process is described in 3GPP TS 24.604 [106].

G.15.8.2 Conformance requirement

As described in clause 15.9.2.

G.15.8.3 Test purpose

As described in clause 15.9.3.

G.15.8.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2.

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Communication Forwarding on Busy, at step 7 deactivation of Communication Forwarding on Busy is respectively triggered at the UE.

G.15.8.5 Test requirements

As described in clause 15.9.5

G.15.9 Communication Forwarding on Not logged-in / WLAN

G.15.9.1 Definition

Test to verify that the UE activates and deactivates IMS Multimedia Telephony Communication Forwarding for the case when user is not registered to IMS service. This process is described in 3GPP TS 24.604 [106].

G.15.9.2 Conformance requirement

As described in clause 15.10.2.

G.15.9.3 Test purpose

As described in clause 15.10.3.

G.15.9.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2.

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Communication Forwarding on not logged-in, at step 7 deactivation of Communication Forwarding on Not logged-in is respectively triggered at the UE.

G.15.9.5 Test requirements

As described in clause 15.10.5

G.15.10 Communication Forwarding on Not reachable / WLAN

G.15.10.1 Definition

Test to verify that the UE activates and deactivates IMS Multimedia Telephony Communication Forwarding for the case when user is not reachable. This process is described in 3GPP TS 24.604 [106].

G.15.10.2 Conformance requirement

As described in clause 15.10a.1.

G.15.10.3 Test purpose

As described in clause 15.10a.3.

G.15.10.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2.

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Communication Forwarding on Not reachable;

At step 5b, SS delivers a simservs document as specified in TS 24.604 [106] cl 4.9, including a non-empty rule set. Specifically, the SS includes the following:

<?xml version="1.0" encoding="UTF-8"?>

<simservs

xmlns="http://uri.etsi.org/ngn/params/xml/simservs/xcap"

xmlns:cp="urn:ietf:params:xml:ns:common-policy"

xmlns:ocp="urn:oma:xml:xdm:common-policy">

<communication-diversion active="true">

<cp:ruleset>

<cp:rule id="rule1">

<cp:conditions>

<not-reachable/>

<rule-deactivated/>

</cp:conditions>

<cp:actions>

<forward-to>

px_XCAP_TargetUri

</target>

<notify-caller>true</notify-caller>

</forward-to>

</cp:actions>

As described in clause 15.14a.3.

G.15.15.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Incoming Communication Barring, at step 7 deactivation of Incoming Communication Barring is respectively triggered at the UE.

G.15.15.5 Test requirements

As described in clause 15.14a.5

G.15.16 Outgoing Communication Barring while roaming / WLAN

G.15.16.1 Definition

Test to verify that the UE activates and deactivates the "IMS Multimedia Telephony Communication Barring for outgoing calls while the user is roaming" supplementary service while camping on HPLMN. This process is described in 3GPP TS 24.611 [101].

G.15.16.2 Conformance requirement

As described in clause 15.14b.2.

G.15.16.3 Test purpose

As described in clause 15.14b.3.

G.15.16.4 Method of test

Initial conditions

SS is configured with the HTTP Digest password for XCAP or shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE.

If the UE uses GAA as XCAP authentication scheme, GAA bootstrapping exchange has been performed according to Annex C.29.2

Test procedure

The generic test procedure according to annex C.29.1 is applied: At step 1 activation of Outgoing Communication Barring, at step 7 deactivation of Outgoing Communication Barring is respectively triggered at the UE.

G.15.16.5 Test requirements

As described in clause 15.14b.5

G.15.17 Subscription to the MWI event package / WLAN

G.15.17.1 Definition

Test to verify that the UE is able to subscribe to MTSI message waiting notification and handle such notifications received after subscription. This process is described in 3GPP TS 24.229 [10] and TS 24.606 [107].

G.15.17.2 Conformance requirement

As described in clause 15.15.2.

G.15.17.3 Test purpose

As described in clause 15.15.3.

G.15.17.4 Method of test

Initial conditions

The UE is pre-configured to autonomously subscribe to the Message Waiting Indication package. The UE is configured with the public service identity of the message account. Otherwise the phone is expected to use the public identity of the user when subscribing to the Message Waiting Indication package.

Test procedure

As described in clause 15.15.4.

G.15.17.5 Test requirements

As described in clause 15.15.5.

G.15.18 Inviting user to conference by sending a REFER request to the conference focus / WLAN

G.15.18.1 Definition

Test to verify that the UE is able to invite a user to a conference by sending a REFER request to the conference focus. This process is described in 3GPP TS 24.147 [84].

G.15.18.2 Conformance requirement

As described in clause 15.19.2.

G.15.18.3 Test purpose

As described in clause 15.19.3.

G.15.18.4 Method of test

Initial conditions

Test procedure

As described in clause 15.19.4.

G.15.18.5 Test requirements

As described in clause 15.19.5.

G.15.19 Void

G.15.20 Three way session creation / WLAN

G.15.20.1 Definition

Test to verify that the UE support Three Way Session creation. This process is described in Section 5.3.1.3.3 of 3GPP TS 24.147 [84].

G.15.20.2 Conformance requirement

As described in clause 15.21a.2.

G.15.20.3 Test purpose

As described in clause 15.21a.3.

G.15.20.4 Method of test

Initial conditions

Test procedure

As described in clause 15.21a.4, but, steps 5-17 replaced by steps 1-8 in C.21a, steps 19-30 are replaced by steps 2-9 in C.10a.

G.15.20.5 Test requirements

As described in clause 15.21a.5.

G.15.21 Inviting user to conference by sending a REFER request to the conference focus for video / WLAN

G.15.21.1 Definition

Test to verify that the UE is able to invite a user to a conference by sending a REFER request to the conference focus. This process is described in 3GPP TS 24.147 [84].

G.15.21.2 Conformance requirement

As described in clause 15.19a.2.

G.15.21.3 Test purpose

As described in clause 15.19a.3.

G.15.21.4 Method of test

Initial conditions

Test procedure

As described in clause 15.19a.4.

G.15.21.5 Test requirements

As described in clause 15.19a.5.

As described in clause 15.28.5.