Module Parameters
Data Types
Component Types
Port Types
Constants
Templates
Signatures
Functions
Altsteps
Test Cases
Module RCS_Testcases
Import Declarations:
Groups:
| Test Cases Summary |
| RCS_1_2_con_001 |
First-time unsuccessful configuration: Subscriber unauthorized.
|
| RCS_1_2_con_004 |
Successful re-configuration: RCS configuration enableRcseSwitch first set to ‘true’ and then set to ‘false’.
|
| RCS_1_2_con_020 |
Keep-alive for SIPoUDP (STUN).
|
| RCS_1_2_con_030 |
Mobile Originated Capability Discovery - Successful.
|
| RCS_1_2_con_031 |
Mobile Originated Capability Discovery – Unsuccessful – 480 Temporarily Unavailable.
|
| RCS_1_2_con_032 |
Mobile Originated Capability Discovery – Unsuccessful –408 Request Timeout.
|
| RCS_1_2_con_033 |
Mobile Originated Capability discovery – Unsuccessful – 404 Not Found.
|
| RCS_1_2_con_034 |
Mobile Originated Capability Discovery – Successful – Multiple Identities.
|
| RCS_1_2_con_035 |
Mobile Originated Capability Discovery - Successful.
|
| RCS_1_2_con_040 |
Mobile Terminated Capability Discovery – Correct Presentation of Remote Capabilities.
|
| RCS_1_2_con_041 |
Mobile Terminated Capability Discovery – Learning Unknown New Users RCS Capabilitie.
|
| RCS_1_2_con_050 |
Capability update during a MO call for video /image sharing (Includes Optional Features).
|
| RCS_1_2_con_051 |
Capability update during a MT call for video /image sharing.
|
| RCS_1_2_con_052 |
Capability update during initiation of an MO voice call - fails as other end has no capability (Includes Optional Features).
|
| RCS_1_2_con_053 |
Capability exchange optimization during a call.
|
| RCS_1_2_con_100 |
Verifies Mobile Originated 1-to-1 Chat session establishment with Mobile Originated session termination.
|
| RCS_1_2_con_101 |
Verifies Mobile Originated 1-to-1 Chat session establishment with Mobile Terminated session termination.
|
| RCS_1_2_con_102 |
Verifies display notification in Mobile Originated 1-to-1 Chat session.
|
| RCS_1_2_con_103 |
Verifies a duplicate session in a Mobile Originated 1-to-1 Chat session.
|
| RCS_1_2_con_104 |
Verifies Mobile Originated 1-to-1 Chat session race condition with two simultaneous invites.
|
| RCS_1_2_con_105 |
Verifies 1-to-1 Chat inactivity timeout.
|
| RCS_1_2_con_106 |
Verifies Mobile Originated 1-to-1 Chat session with store and forward when the sender is still in active IM session (with MSRP session still active) when the recipient comes back online.
|
| RCS_1_2_con_107 |
Verifies Mobile Originated 1-to-1 Chat session with store and forward when the sender is still online when the recipient comes back online.
|
| RCS_1_2_con_120 |
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Terminated session termination.
|
| RCS_1_2_con_121 |
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Originated session termination.
|
| RCS_1_2_con_122 |
Verifies Mobile Terminated 1-to-1 Chat session establishment when the sender is on the spam/blacklist.
|
| RCS_1_2_con_123 |
Verifies display notification in Mobile Terminated 1-to-1 Chat session.
|
| RCS_1_2_con_124 |
Verifies a duplicate session in a Mobile Terminated 1-to-1 Chat session
1.
|
| RCS_1_2_con_125 |
Verifies Mobile Terminated 1-to-1 Chat session race condition with new invite received after previous invite has been accepted
1.
|
| RCS_1_2_con_126 |
Verifies delivery of deferred messages in a Mobile Terminated 1-to-1 Chat session.
|
| RCS_1_2_con_130 |
Verifies Mobile Originated Group Chat session establishment and Originating User leaves the session
1.
|
| RCS_1_2_con_131 |
Verifies Mobile Originated Group Chat session when non-originating Users leave the session and the session is closed
1.
|
| RCS_1_2_con_132 |
Verifies Group Chat when a new User is added to the session
1.
|
| RCS_1_2_con_140 |
Verifies Mobile Terminated Group Chat session establishment and Terminating User leaves the session
1.
|
| RCS_1_2_con_145 |
Verifies Group Chat automatic re-join when a participant leaves the session due to loss of connectivity.
|
| RCS_1_2_con_146 |
|
| RCS_1_2_con_147 |
Verifies correct behaviour after a Group Chat times out and a participant attempts to re-start the session but receives a 403 Forbidden response from the IM server.
|
| RCS_1_2_con_148 |
Verifies correct behaviour after a Group Chat is re-started more than once leading to two concurrent sessions.
|
| RCS_1_2_con_200 |
Mobile Originated File Transfer
1.
|
| RCS_1_2_con_201 |
Mobile originated file transfer – Rejected
1.
|
| RCS_1_2_con_210 |
Mobile Terminated File Transfer
1.
|
| RCS_1_2_con_211 |
Mobile terminated file transfer – Rejected
1.
|
| RCS_1_2_con_212 |
File size limit
1.
|
| RCS_1_2_con_213 |
File size warning
1.
|
| RCS_1_2_con_250 |
Mobile Originated Image sharing session – Mobile originated Session termination
1.
|
| RCS_1_2_con_251 |
Mobile originated image sharing session establishment – Rejected
1.
|
| RCS_1_2_con_270 |
Mobile Terminated Image sharing session – Mobile Terminated session termination
1.
|
| RCS_1_2_con_271 |
Mobile terminated Image sharing session establishment – Rejected
1.
|
| RCS_1_2_con_300 |
Mobile Originated Video sharing session – Mobile originated termination
1.
|
| RCS_1_2_con_301 |
Mobile Terminated Video sharing session – Mobile Terminated Session termination
1.
|
| RCS_1_2_con_302 |
Unsuccessful mobile originated video sharing session establishment
1.
|
| RCS_1_2_con_320 |
Mobile Terminated Video sharing session – Mobile Terminated Session termination
1.
|
| RCS_1_2_con_321 |
Mobile Terminated Video sharing session – Mobile Originated session termination
1.
|
| RCS_1_2_con_322 |
Unsuccessful mobile terminated video sharing session establishment
1.
|
Details
RCS_1_2_con_001
testcase RCS_1_2_con_001() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Configuration
First-time unsuccessful configuration: Subscriber unauthorized.
1. Handset is powered on.
2. Execute "Successful autoconfiguration" (C.6.1.1). In step 4 set the version in the XML body to "0".
3. Reboot the handset.
4. Execute "Successful autoconfiguration" (C.6.1.1).
Requirements: User A NOT IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - After step 2 service is not enabled on the handset.
2. At step 4 of the test procedure in step 3 of C.6.1.1 "vers" parameter SHALL be 0.
3. After step 4 service is enabled on the handset.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.2.2.1.2
RCS_1_2_con_004
testcase RCS_1_2_con_004() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Configuration
Successful re-configuration: RCS configuration enableRcseSwitch first set to ‘true’ and then set to ‘false’.
1. User A’s handset is powered on.
2. Execute "Successful autoconfiguration" (C.6.1.1).
In step 4 set the enableRcseSwitch to true in the XML body.
3. User A’s RCS client performs IMS registration.
4. User A’s handset is power cycled.
5. Execute “Successful autoconfiguration” (C.6.1.1).
In step 4 set the enableRcseSwitch to false in the XML body.
6. User A’s RCS client performs IMS registration.
Requirements: RCS services previously configured on the phone/(U)SIM pair
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - After step 3 User A’s handset, RCS UX provides the following control elements:
‘RCS Service while roaming’ enabled/disabled switch; and
‘RCS Service’ enabled/disabled switch.
2. After step 6 User A’s handset, RCS UX does not provide the following control element:
‘RCS Service’ enabled/disabled switch.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.10 (and A.2.6)
RCS_1_2_con_020
testcase RCS_1_2_con_020() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Keep_Alive
Keep-alive for SIPoUDP (STUN).
1. The client A exchanges initial STUN message.
2. The client A’s handset registers for the RCS service.
3. The client A’s constantly sends keep-alive message.
Requirements: The client A is a registered RCS user.
The client A’s handset coverage is Wi-Fi.
Applicability: ics_stun_udp
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- During - the step 3, the test tool receives STUN keep-alive messages from the client A.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.8
RCS_1_2_con_030
testcase RCS_1_2_con_030() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Capability_Discovery
Mobile Originated Capability Discovery - Successful.
1. User A triggers a capability discovery procedure towards User B at User A’s device.
This can be done by one of the following:
a. Adding new User B entry (RCS user) to User A’s address book; or
b. Refreshing User B’s status (RCS user) manually
2. Execute "Mobile Originated Capability Exchange" (C.1.1)
3. Check that User B is shown as available for RCS on User A’s RCS client
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 3 User A’s RCS client shows User B as available.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_031
testcase RCS_1_2_con_031() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Capability_Discovery
Mobile Originated Capability Discovery – Unsuccessful – 480 Temporarily Unavailable.
1. User A triggers a capability discovery procedure towards User B on User A’s device.
This can be done by one of the following:
a. Adding new User B entry (RCS user) to User A’s address book; or
b. Refreshing User B’s (RCS user) status manually
2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1).
3. The test tool responds with a 480 TEMPORARILY UNAVAILABLE towards User A’s RCS client. 4. Check that User B is shown as not available for RCS on User A’s RCS client
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 4 User A’s RCS client shows User B as not available.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_032
testcase RCS_1_2_con_032() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Capability_Discovery
Mobile Originated Capability Discovery – Unsuccessful –408 Request Timeout.
1. User A triggers a capability discovery procedure towards User B on User A’s device.
This can be done by one of the following:
a. Adding new User B entry (RCS user) to User A’s address book; or
b. Refreshing User B’s (RCS user) status manually
2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1).
3. The test tool responds with a 408 REQUEST TIMEOUT towards the RCS client.
4. Check that User B is shown as not available for RCS on User A’s RCS client
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 4 User A’s RCS client shows User B as not available.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_033
testcase RCS_1_2_con_033() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Capability_Discovery
Mobile Originated Capability discovery – Unsuccessful – 404 Not Found.
1. User A triggers a capability discovery procedure towards User B on User A’s device.
This can be done by one of the following:
a. Adding new User B entry (RCS user) to User A’s address book; or
b. Refreshing User B’s (RCS user) status manually
2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1).
3. The test tool responds with a 404 NOT FOUND towards User A’s RCS client.
4. Check that User B is shown as not available for RCS on User A’s RCS client
Requirements: User A is IMS registered for RCS, User A’s RCS device is provisioned for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 4 User A’s RCS client shows User B as not available.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_034
testcase RCS_1_2_con_034() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Capability_Discovery
Mobile Originated Capability Discovery – Successful – Multiple Identities.
1. User A creates a new contact (User C) in address book with the following four unique entries
1. MSISDN number 1 (RCS capable)
2. MSISDN number 2 (without RCS capabilities)
3. MSISDN number 3 (RCS capable, different from 1)
4. SIP-URI (RCS capable, if supported by the UI, independent from 1, 2 or 3).
2. Execute step 1 of "Mobile Originated Capability Exchange" (C.1.1) for all four entries (three if SIP-URI was not supported).
3. The test tool responds with 200 OK towards User A’s RCS client for each OPTIONS message.
4. Check that User C’s identities 1, 3 and 4 (if supported) are shown as available for RCS on User A’s RCS client
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 4 User A’s RCS client shows User C’s identities 1, 3 and 4 (if supported) as available.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_035
testcase RCS_1_2_con_035() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Capability_Discovery
Mobile Originated Capability Discovery - Successful.
1. User A triggers a capability discovery procedure towards User B at User A’s device.
This can be done by one of the following:
a. Adding new User B entry (RCS user) to User A’s address book; or
b. Refreshing User B’s (RCS user) status manually
2. Execute "Mobile Originated Capability Exchange" (C.1.1) with exception to not sending feature param tag in the contact header of 200 OK.
3. Check that User B is shown as unavailable for RCS on User A’s RCS client
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS , User B is IMS registered, but does not support RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 3 User A’s RCS client shows User B as unavailable.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.3.1
RCS_1_2_con_040
testcase RCS_1_2_con_040() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Capability_Discovery
Mobile Terminated Capability Discovery – Correct Presentation of Remote Capabilities.
1. Execute "Mobile Terminated Capability Exchange" (C.1.2)
2. Check that User B is shown as available for RCS on User A’s RCS client.
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS , User B is stored in User A’s address book
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 2 User A’s RCS client shows User B as available for RCS.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.4.1
RCS_1_2_con_041
testcase RCS_1_2_con_041() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Capability_Discovery
Mobile Terminated Capability Discovery – Learning Unknown New Users RCS Capabilitie.
1. Execute "Mobile Terminated Capability Exchange" (C.1.2) with User X as sender and condition B4 in D.1.4.
Note: User A’s RCS device temporarily stores capabilities of User X.
2. User A adds User X to their address book shortly after completing the SIP OPTIONS exchange (which was done in step 1).
Requirements: User A’s and User X’s RCS devices are provisioned for RCS , User A and User X are IMS registered for RCS , User X is not currently stored in User A’s address book
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 2 on User A’s RCS client; User X is shown as an RCS user.
See also: RCS-e – Advanced Communications: Services and Client Specification 2.4.1
RCS_1_2_con_050
testcase RCS_1_2_con_050() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Capability_Update
Capability update during a MO call for video /image sharing (Includes Optional Features).
When a voice call is established the participants have to update their capabilities
1. User A initiates a voice call to User B at User A’s device.
2. Execute "Mobile Originated Capability Exchange" (C.1.1).
3. Check that User B is shown as available for video and/or image sharing on User A’s RCS client as supported by User A’s RCS client.
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS , User A’s RCS device as 3G, HSPA or Wi-Fi connectivity Applicability: ics_imageShare OR ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 3 User A’s RCS client shows User B as available for video / image sharing as matching User A’s RCS client's capabilities.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.1
RCS_1_2_con_051
testcase RCS_1_2_con_051() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Capability_Update
Capability update during a MT call for video /image sharing.
When a voice call is established the participants have to update their capabilities
1. User A accepts a voice call from User B at User A’s device.
2. Execute "Mobile Terminated Capability Exchange" (C.1.2).
3. Check that User B's capabilities for video and image sharing are shown as available on User A’s RCS client matching User A's RCS client's capabilities according to ICS.
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS , User A’s RCS device as 3G, HSPA or Wi-Fi connectivity
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 3 User B's capabilities for video and image sharing are shown as available on User A’s RCS client matching User A's RCS client's capabilities according to ICS.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.1
RCS_1_2_con_052
testcase RCS_1_2_con_052() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Capability_Update
Capability update during initiation of an MO voice call - fails as other end has no capability (Includes Optional Features).
When a voice call is initiated the call participants have to update their capabilities.
The recipient should not be shown as available for video / image share if the corresponding tags are not included in the 200 OK response
1. User A initiates a voice call to User B at User A’s device.
2. Execute "Mobile Originated Capability Exchange" (C.1.1) and do not use condition B1 and B2 in step 2 (D.1.4).
3. Check that User B is shown as not available for video and image sharing on User A’s RCS client.
Requirements: User A is IMS registered for RCS , User A’s RCS device is provisioned for RCS , User A’s RCS device as 3G, HSPA or Wi-Fi connectivity Applicability: ics_imageShare OR ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 3 User A’s RCS client shows User B as not available for video and image sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.1
RCS_1_2_con_053
testcase RCS_1_2_con_053() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Capability_Update
Capability exchange optimization during a call.
1. The client A’s handset’s coverage is changed to HSPA.
2. Wait for 15 seconds.
3. The client A’s handset’s coverage is changed to 3G.
4. Wait for 15 seconds.
Requirements: The client A is RCS registered user.
The client A’s handset is in an on-going voice call with a test tool (simulating an RCS user) and the test tool delivers its RCS capabilities to the client A.
The client A’s handset is under 3G coverage.
The displayed capabilities on the client A’s handset for the current call include both image and video share.
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- Client - A is not sending SIP OPTIONS message at the step #2 and the step #4.
See also: GSMA RCS IOT RCS-e Implementation Guidelines 2.3.1, RCS-e – Advanced Communications: Services and Client Specification 1.2.2
RCS_1_2_con_100
testcase RCS_1_2_con_100() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies Mobile Originated 1-to-1 Chat session establishment with Mobile Originated session termination.
1. User A initiates a 1-to-1 Chat session with User B on his device with the message “Hello B”.
2. Execute “Mobile Originated Session Establishment” (C.2.1) with the message “Hello B”
3. User A receives an indication that the message “Hello B” has been delivered.
4. If the session invitation in step 2 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Hello B”.
5. Execute “MSRP Session Message” (C.7.2) with the message “Hello A” from the Test Tool
6. User A receives an “Is Composing” indication from User B.
7. User A receives “Hello A” from User B.
8. User A sends the message “Bye B” to User B.
9. Execute “MSRP Session Message” (C.7.2) with the message “Bye B” from client A.
10. User A receives an indication that the message “Bye B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
11. User A terminates the session. 11. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s device is provisioned for RCS.
User A is IMS registered for RCS.
In case of User A’s device support UI for switching display notifications on/off then display notification are to be switched on
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives an indication that the message “Hello B” has been delivered.
2. At step 4 User A receives an indication that message “Hello B” has been displayed.
3. At step 6 User A receives an “Is Composing” indication from User B.
4. At step 7 User A receives “Hello A” from User B.
5. At step 10 User A receives an indication that the message “Bye B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4
RCS_1_2_con_101
testcase RCS_1_2_con_101() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies Mobile Originated 1-to-1 Chat session establishment with Mobile Terminated session termination.
1. User A initiates a 1-to-1 Chat session with User B on his device with the message “Hello B”.
2. Execute “Mobile Originated Session Establishment” (C.2.1) with the message “Hello B”
3. User A receives an indication that the message “Hello B” has been delivered.
4. If the session invitation in step 2 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Hello B”.
5. Execute “MSRP Session Message” (C.7.1) with the message “Hello A” from the Test Tool
6. User A receives an “Is Composing” indication from User B.
7. User A receives “Hello A” from User B.
8. User A sends the message “Bye B” to User B.
9. Execute “MSRP Session Message” (C.7.1) with the message “Bye B” from client A.
10. User A receives an indication that the message “Bye B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
11. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s device is provisioned for RCS.
User A is IMS registered for RCS
In case of User A’s device support UI for switching display notifications on/off then display notification are to be switched on
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives an indication that the message “Hello B” has been delivered.
2. At step 4 User A receives an indication that message “Hello B” has been displayed.
3. At step 6 User A receives an “Is Composing” indication from User B.
4. At step 7 User A receives “Hello A” from User B.
5. At step 10 User A receives an indication that the message “Bye B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4
RCS_1_2_con_102
testcase RCS_1_2_con_102() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies display notification in Mobile Originated 1-to-1 Chat session.
1. User A initiates a 1-to-1 Chat session with User B on his device with the message “Hello B”.
2. Execute “Mobile Originated Session: 1-to-1 Chat with display notification” (C.2.3) with the message “Hello B”
3. User A receives an indication that the message “Hello B” has been delivered.
4. User A receives an indication that the message “Hello B” has been displayed.
5. Execute “MSRP Session Message” (C.7.1) with the message “Hello A” from the Test Tool
6. User A receives “Hello A” from User B.
7. User A sends the message “Bye B” to User B.
8. Execute “MSRP Session Message with Display Notification” (C.7.2) with the message “Bye B” from client A.
9. User A receives an indication that the message “Bye B” has been delivered.
10. User A receives an indication that the message “Bye B” has been displayed.
11. User A terminates the session. 12. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s device is provisioned for RCS.
User A is IMS registered for RCS.
User A’s device is configured to request display notifications.
Applicability: ics_request_displayNotifications
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives an indication that the message “Hello B” has been delivered.
2. At step 4 User A receives an indication that the message “Hello B” has been displayed.
3. At step 9 User A receives an indication that the message “Bye B” has been delivered.
4. At step 10 User A receives an indication that the message “Bye B” has been displayed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.2.4
RCS_1_2_con_103
testcase RCS_1_2_con_103() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies a duplicate session in a Mobile Originated 1-to-1 Chat session.
1. User A initiates a 1-to-1 Chat session with User B on his device with the first message “Hello B”.
2. Execute “Mobile Originated Session Establishment - 1-to-1 Chat with two messages” (C.2.5) with the first message “Hello B”
3. User A receives an indication that the message “Hello B” has been delivered.
4. User A sends the second message “Wake up B” to User B.
5. Continue to execute “Mobile Originated Session Establishment - 1-to-1 Chat with two messages” (C.2.5) with the second message “Wake up B”
7. If the session invitation in step 2 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Hello B”.
8. If the session invitation in step 5 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Wake up B”.
9. Execute “MSRP Session Message” (C.7.2) with the message “Hello A” from the Test Tool
10. User A receives “Hello A” from User B.
11. User A terminates the session.
12. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s device is provisioned for RCS.
User A is IMS registered for RCS.
In case of User A’s device support UI for switching display notifications on/off then display notification are to be switched on
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives an indication that the message “Hello B” has been delivered.
2. At step 6 User A receives an indication that the message “Wake up B” has been delivered.
3. At step 7 User A receives an indication that message “Hello B” has been displayed.
4. At step 8 User A receives an indication that message “Wake up B” has been displayed.
5. At step 10 User A receives “Hello A” from User B
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.1
RCS_1_2_con_104
testcase RCS_1_2_con_104() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies Mobile Originated 1-to-1 Chat session race condition with two simultaneous invites.
1. User A initiates a 1-to-1 Chat session with User B on his device with the message “Hello B”.
2. Execute “Mobile Originated Session Establishment: simultaneous INVITEs” (C.2.8) with the messages “Hello B” from User A and “Hello A” from User B
3. User A receives “Hello A” from User B.
4. User A receives an indication that the message “Hello B” has been delivered.
5. If the session invitation in step 2 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Hello B”.
6. User A sends the message “Quick B” to User B.
7. Execute “MSRP Session Message” (C.7.2) with the message “Quick B” from client A.
8. Execute “MSRP Session Message” (C.7.2) with the message “Yes A” from the Test Tool
9. User A receives “Yes A” from User B.
10. User A receives an indication that the message “Quick B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
11. User A terminates the session. 12. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s device is provisioned for RCS
User A is IMS registered for RCS
In case of User A’s device support UI for switching display notifications on/off then display notification are to be switched on
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives “Hello A” from User B.
2. At step 4 User A receives an indication that the message “Hello B” has been delivered.
3. At step 5 User A receives an indication that message “Hello B” has been displayed.
4. At step 9 User A receives “Yes A” from User B.
5. At step 10 User A receives an indication that the message “Quick B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.18.1
RCS_1_2_con_105
testcase RCS_1_2_con_105() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies 1-to-1 Chat inactivity timeout.
1. User A initiates a 1-to-1 Chat session with User B on his device with the message “Hello B”.
2. Execute “Mobile Originated Session Establishment” (C.2.1) with the message “Hello B”
3. User A receives an indication that the message “Hello B” has been delivered.
4. If the session invitation in step 2 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Hello B”.
5. Execute “MSRP Session Message” (C.7.2) with the message “Hello A” from the Test Tool
6. User A receives “Hello A” from User B.
7. User A waits until the chat inactivity timeout occurs (TBD) and Client A then terminates the session
8. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s device is provisioned for RCS
User A is IMS registered for RCS
In case of User A’s device support UI for switching display notifications on/off then display notification are to be switched on
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 8 Client A terminates the session.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.8
RCS_1_2_con_106
testcase RCS_1_2_con_106() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies Mobile Originated 1-to-1 Chat session with store and forward when the sender is still in active IM session (with MSRP session still active) when the recipient comes back online.
1. User A initiates a 1-to-1 Chat session with User B on his device with the message “Hello B”. (User B is offline)
2. Execute “Mobile Originated Session: Store and Forward - Receiver offline” (C.2.10) with the message “Hello B”
3. User A sends the message “Again B” to User B. (User B is offline)
4. Execute “MSRP Session Store and Forward” (C.7.3) with the message “Again B” from Client A.
5. (User A keeps chat session open and User B comes back online)
6. Execute “MSRP Session Store and Forward Message Delivered” (C.7.4) for the message “Hello B” from Client A.
7. User A receives an indication that the message “Hello B” has been delivered.
8. If the session invitation in step 2 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Hello B”.
9. Execute “MSRP Session Store and Forward Final Message Delivered” (C.7.5) for the message “Again B” from Client A.
10. User A receives an indication that the message “Again B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
Requirements: User A’s device is provisioned for RCS
User A is IMS registered for RCS
In case of User A’s device support UI for switching display notifications on/off then display notification are to be switched on.
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 7 User A receives an indication that the message “Hello B” has been delivered.
2. At step 8 User A receives an indication that message “Hello B” has been displayed.
3. At step 10 User A receives an indication that the message “Again B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.11
RCS_1_2_con_107
testcase RCS_1_2_con_107() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_1_to_1_Chat
Verifies Mobile Originated 1-to-1 Chat session with store and forward when the sender is still online when the recipient comes back online.
The same call-flow is also used for delivery of deferred notifications when the sender goes offline and then comes back on line later.
1. User A initiates a 1-to-1 Chat session with User B on his device with the message “Hello B”. (User B is offline)
2. Execute “Mobile Originated Session Store and Forward - Receiver offline” (C.2.10) with the message “Hello B”
3. User A sends the message “Again B” to User B. (User B is offline)
4. Execute “MSRP Session Store and Forward” (C.7.3) with the message “Again B” from Client A.
5. User A terminates the session.
6. Execute “Mobile Originated Session Termination” (C.3.1)
7. (User A stays online and User B comes back online)
8. Execute “Mobile Originated Session Store and Forward - deferred delivery” (C.2.11)
9. Execute “MSRP Session Store and Forward Message Delivered” (C.7.4) for the message “Hello B” from Client A.
10. Client A auto-accepts and User A receives an indication that the message “Hello B” has been delivered.
11. If the session invitation in step 2 contained a request for display notification, then execute MSRP SEND request towards A that contains display status for message “Hello B”.
12. Execute “MSRP Session Store and Forward Final Message Delivered” (C.7.5) for the message “Again B” from Client A.
13. User A receives an indication that the message “Again B” has been delivered and if display notifications were
Requirements: User A’s device is provisioned for RCS
User A is IMS registered for RCS
In case of User A’s device support UI for switching display notifications on/off then display notification are to be switched on
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 10 User A receives an indication that the message “Hello B” has been delivered.
2. At step 11 User A receives an indication that message “Hello B” has been displayed.
3. At step 13 User A receives an indication that the message “Again B” has been delivered and if display notifications were requested, then an indication that the message has been displayed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.11
RCS_1_2_con_120
testcase RCS_1_2_con_120() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Terminated session termination.
1. Execute “Mobile Terminated Session Establishment” (C.2.2) with the message “Hello A” from User B
2. User A receives “Hello A” from User B.
3. User A sends the message “Hello B” to User B before the session times out.
4. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
5. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
6. User A receives an “Is Composing” indication from User B.
7. User A receives “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 6 User A receives an “Is Composing” indication from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4
RCS_1_2_con_121
testcase RCS_1_2_con_121() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session establishment with Mobile Originated session termination.
1. Execute “Mobile Terminated Session Establishment” (C.2.2) with the message “Hello A” from User B
2. User A receives “Hello A” from User B.
3. User A sends the message “Hello B” to User B before the session times out.
4. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
5. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
6. User A receives an “Is Composing” indication from User B.
7. User A receives “Bye A” from User B.
8. User A terminates the session.
9. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 6 User A receives an “Is Composing” indication from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4
RCS_1_2_con_122
testcase RCS_1_2_con_122() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session establishment when the sender is on the spam/blacklist.
1. Execute “Mobile Terminated Session Establishment: Spam” (C.2.7) with the message “Spam for A” from User S
2. User A does not receive the message from User S.
3. The message “Spam for A” is available in the spam filter.
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
User A has User S listed in the spam/blacklist
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - During step 1 Client A sends a delivery notification with status “delivered” to Client S.
2. At step 2 User A does not receive the message from User S.
3. At step 3 the message “Spam for A” is available in the spam filter.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.15
RCS_1_2_con_123
testcase RCS_1_2_con_123() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies display notification in Mobile Terminated 1-to-1 Chat session.
1. Execute “Mobile Terminated Session Establishment: 1-to-1 Chat with display notification” (C.2.4) with the message “Hello A” from User B
2. User A receives “Hello A” from User B.
3. User A sends the message “Hello B” to User B before the session times out.
4. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
5. Execute “MSRP Session with Display Notification” (C.7.2) with the message “Bye A” from the Test Tool
6. User A receives “Bye A” from User B.
7. User A displays “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
User A’s device is configured to respond to display notification requests
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- The - pass-criteria are completely contained in the message flows in Appendix C.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.2.4
RCS_1_2_con_124
testcase RCS_1_2_con_124() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies a duplicate session in a Mobile Terminated 1-to-1 Chat session
1. Execute “Mobile Terminated Session Establishment: 1-to-1 Chat with two messages” (C.2.6) with the first message “Hello A” from User B and the second message “Wake up A” from User B.
2. User A receives “Hello A” from User B (but performs no action).
3. User A receives “Wake up A” from User B.
4. User A sends the message “Hello B” to User B before the session times out.
5. Execute “MSRP Session Message” (C.7.1) with the message “Hello B” from client A.
6. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
7. User A receives “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 3 User A receives “Wake up A” from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.1
RCS_1_2_con_125
testcase RCS_1_2_con_125() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies Mobile Terminated 1-to-1 Chat session race condition with new invite received after previous invite has been accepted
1. Execute “Mobile Terminated Session Establishment: new INVITE race” (C.2.9) with the first message “Hello A” from User B and the
second message “Again A” from User B
2. User A receives “Hello A” from User B.
3. User A receives “Again A” from User B.
4. User A sends the message “Two B” to User B before the session times out.
5. Execute “MSRP Session Message” (C.7.1) with the message “Two B” from client A.
6. Execute “MSRP Session Message” (C.7.1) with the message “Bye A” from the Test Tool
7. User A receives “Bye A” from User B.
8. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives “Hello A” from User B.
2. At step 3 User A receives “Again A” from User B.
3. At step 7 User A receives “Bye A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.18.2
RCS_1_2_con_126
testcase RCS_1_2_con_126() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_1_to_1_Chat
Verifies delivery of deferred messages in a Mobile Terminated 1-to-1 Chat session.
1. User A comes online.
2. Execute “Mobile Terminated Session Store and Forward - deferred delivery” (C.2.12) with the first stored message “Hello A”
from User B and the second stored message “Again A” from User B.
3. User A receives an indication of the stored message “Hello A” from User B and may optionally receive an indication of the
stored message “Again A” from User B. User A opens the chat window.
4. Execute “MSRP Session Store and Forward Final Message Delivered” (C.7.5) with the stored message “Yet again A” from User B.
5. User A receives the stored message “Again A” from User B if not already received and then the message “Yet again A” from User B
and the session is closed.
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
User A is offline
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives an indication of the stored message “Hello A” from User B and optionally receives an indication
of the stored message “Again A” from User B.
2. At step 5 User A receives the stored message “Again A” from User B if not already received and then receives the stored message
“Yet again A” from User B and the session is closed.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.4.11, 3.2.4.19
RCS_1_2_con_130
testcase RCS_1_2_con_130() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Group_Chat
Verifies Mobile Originated Group Chat session establishment and Originating User leaves the session
1. User A initiates a Group Chat session with User B, User C and User D on his device with the subject “Test”.
2. Execute “Mobile Originated Session Establishment: Group Chat” (C.2.13) with the subject “Test” and participants list with User B and User C as accepted (User D does not accept).
3. User A receives the participant list and the status for each one
4. User A sends the message “Hello group” to the group.
5. Execute “MSRP Group Session Message” (C.7.6) with the message “Hello group” from Client A.
6. Execute “MSRP Group Session Message” (C.7.6) with the message “Hello A” from the Test Tool from User B
7. User A receives “Hello A” from User B.
8. User A leaves the Group Chat session.
9. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 User A receives the participant list and the status for each one
2. At step 7 User A receives “Hello A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5
RCS_1_2_con_131
testcase RCS_1_2_con_131() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Group_Chat
Verifies Mobile Originated Group Chat session when non-originating Users leave the session and the session is closed
1. User A initiates a Group Chat session with User B, User C and User D on his device with the subject “Test”.
2. Execute “Mobile Originated Session Establishment: Group Chat” (C.2.13) with the subject “Test” and participants list with User B and User C as accepted (User D does not accept).
3. Execute “MSRP Group Session Message” (C.7.6) with the message “B going” from the Test Tool from User B
4. User A receives the message “B going” from User B.
5. Execute “Participant List Update” (C.5.1) with User B as offline (and User C as accepted).
6. User A receives the participant list and the status for each one (User B as offline and User C as accepted).
7. Execute “MSRP Group Session Message” (C.7.6) with the message “C going” from the Test Tool from User C
8. User A receives the message “C going” from User C.
9. Execute “Participant List Update” (C.5.1) with User C as offline.
10. User A receives the participant list and the status for each one (User C as offline).
11. Execute “Mobile Terminated Session Termination” (C.3.2).
Requirements: User A’s device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 4 User A receives the message “B going” from User B.
2. At step 6 User A receives the participant list and the status for each one (User B as offline and User C as accepted).
3. At step 8 User A receives the message “C going” from User C.
4. At step 10 User A receives the participant list and the status for each one (User C as offline).
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5
RCS_1_2_con_132
testcase RCS_1_2_con_132() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Group_Chat
Verifies Group Chat when a new User is added to the session
1. User A initiates a Group Chat session with User B and User C on his device with the subject “Test”.
2. Execute “Mobile Originated Session Establishment: Group Chat” (C.2.13) with the subject “Test” and participants list with User B and User C as accepted.
3. User A selects User D to add to the session
4. Execute “Inviting new User to Group Chat” (C.5.2) with new User D added to the Group Chat
5. User A receives the participant list and the status for each one (User D as added/accepted and User B and User C as accepted).
6. User A leaves the Group Chat session.
7. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 5 User A receives the participant list and the status for each one (User D as added/accepted and User B and User C as accepted).
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5.5.4
RCS_1_2_con_140
testcase RCS_1_2_con_140() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Group_Chat
Verifies Mobile Terminated Group Chat session establishment and Terminating User leaves the session
1. Execute “Mobile Terminated Session Establishment: Group Chat” (C.2.14) with User B as the initiator and User C also invited
2. User A receives the invitation and the participant list.
3. User A accepts the invitation.
4. Continue to execute “Mobile Terminated Session Establishment: Group Chat” (C.2.14) (TBD: Does this include a “get participants” session?)
5. Execute “MSRP Group Session Message” (C.7.6) with the message “Hello group” from the Test Tool from Client B.
6. User A receives the message “Hello group” from User B.
7. User A sends the message “Hello BC” to the Group.
8. Execute “MSRP Group Session Message” (C.7.6) with the message “Hello BC” from User A to the Group
9. User A leaves the Group Chat session.
10. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives the invitation and the participant list (User B and User C).
2. At step 6 User A receives the message “Hello group” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5
RCS_1_2_con_145
testcase RCS_1_2_con_145() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Group_Chat
Verifies Group Chat automatic re-join when a participant leaves the session due to loss of connectivity.
1. User A, User B and User C are in an established Group Chat session initiated by User B.
( Execute “Mobile Terminated Session Establishment: Group Chat” (C.2.14) with User B as the initiator and User A and User C also invited).
2. User A leaves the Group Chat involuntarily. Simulate by e.g. severely attenuating the cellular signal from the Test Tool
to the device under test and waiting XX ixit_RF_loss_recognition_timer seconds.
3. Connectivity with the device under test is restored by re-establishing the cellular signal from the Test Tool.
4. Client A re-registers with the IMS core (Test Tool).
5. Client A automatically re-joins the original Group Chat session using the original Contribution ID. Execute: “Group Chat automatic re-join”
(C.2.15) with User A as the initiator.
6. Execute “MSRP Group Session Message” (C.7.6) with the message “Hello again A” from User B to the Group.
7. User A receives the message “Hello again A” from User B.
8. User A leaves the Group Chat session.
9. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 5 Client A automatically re-joins the original Group Chat
2. At step 7 User A receives the message “Hello again A” from User B.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.5.5.6, RCS Implementation Guidelines ID_4_21_2
RCS_1_2_con_146
testcase RCS_1_2_con_146() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Group_Chat
Requirements:
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- The - pass-criteria are completely contained in the message flows in Appendix C.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.2.2.4
RCS_1_2_con_147
testcase RCS_1_2_con_147() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Group_Chat
Verifies correct behaviour after a Group Chat times out and a participant attempts to re-start the session but receives a 403 Forbidden response from the IM server.
1. User A, User B and User C are in an established Group Chat session initiated by User B. ( Execute “Mobile Terminated Session Establishment: Group Chat” (C.2.14) with
User B as the initiator and User A and User C also invited). Set the XX FFS timer to YY FFS value.
2. Wait ZZ FFS until the Group Chat session times out.
3. User A sends the message “Restart” to the original Group.
4. Client A attempts to automatically re-join the original Group Chat using the original Contribution ID. This fails as the session has expired and the IM server (Test Tool)
sends 403 Forbidden. Execute: “Group Chat re-start: 403 Forbidden” (C.2.17) with User A as the initiator.
5. Client A either:
a) Abandons the attempt to start a Group Chat and sends no new messages.
Or
b) Starts a new Group Chat in which case execute “Mobile Originated Session Establishment: Group Chat” (C.2.13) with User A as the initiator, with the subject
“Restart” and participants list with User B and User C. Then User A leaves the Group Chat session. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 4 Client A attempts to automatically re-join the original Group Chat.
2. At step 5 Client A either:
a) Sends no messages.
Or
b) Starts a new Group Chat.
See also: RCS Implementation Guidelines ID_4_21_3
RCS_1_2_con_148
testcase RCS_1_2_con_148() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Group_Chat
Verifies correct behaviour after a Group Chat is re-started more than once leading to two concurrent sessions.
1. User A, User B, User C and User D are in a re-started Group Chat session (session 1), re-started by User B.
( Execute “Mobile Terminated Session Establishment: Group Chat” (C.2.14) with User B as the initiator and User A and
User C and User D also invited). User C does not re-join (as is offline).
2. Wait XX 5 seconds (??).
3. User C (the Test Tool) re-starts the same Group Chat using the same Contribution ID (session 2). (User C was offline at
step 1 and also was not aware that User D was a member of the Group Chat). Execute: “Group Chat re-start: Mobile Terminated” (C.2.19)
with User C as the initiator and User A and User B (only) as the other members of the participants list.
4. Client A auto-accepts the group session request from step 3. Execute: “Auto-accept Group Chat” (C.2.20).
5. Client A auto-invites Client D to the Group Chat (session 2). Execute: “Auto-invite Group Chat” (C.2.21).
6. User A sends the message “Hello again” to the group using session 2.
7. Execute “MSRP Group Session Message” (C.7.6) (session 2) with the message “Hello again” from Client A.
8. (User B (the Test Tool) did not receive the second re-start (session 2) at step 3 and so when he sends a message Client B uses session 1).
Execute “MSRP Group Session Message” (C.7.6) with the message “Back again” from the Test Tool from Client B using session 1.
9. User A receives the message “Back again” from User B.
10. Client A auto-invites Client B to the Group Chat (session 2). Execute: “Auto-invite Group Chat” (C.2.21).
11. User A leaves the Group Chat session.
12. Execute “Mobile Originated Session Termination” (C.3.1).
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- Pass-Criteria - 1. At step 4 Client A auto-accepts the group session request.
2. At step 5 Client A auto-invites Client D to the Group Chat session 2.
3. At step 7 the MSRP Group Session uses session 2.
4. At step 9 User A receives the message “Back again” from User B.
5. At step 10 Client A auto-invites Client B to the Group Chat session 2.
See also: RCS Implementation Guidelines ID_4_21_3
RCS_1_2_con_200
testcase RCS_1_2_con_200() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_File_Transfer
Mobile Originated File Transfer
1. User A initiates a File Transfer towards User B on his device.
2. Execute “Mobile Originated Session Establishment” (C.2.1)
3. User A’s RCS client sends a file in an MSRP session.
4. Execute “Mobile Originated Session Termination” (C.3.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_fileTransfer
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 3 the MSRP session is setup correctly and a file is transferred successfully
See also: RCS-e – Advanced Communications: Services and Client Specification 3.4.1
RCS_1_2_con_201
testcase RCS_1_2_con_201() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_File_Transfer
Mobile originated file transfer – Rejected
1. User A initiates a File Transfer towards User B on his device.
2. Execute “Mobile Originated Session – Reject” (C.4.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_fileTransfer
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 2 User A’s RCS client shows User B rejected the file sharing session.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.4.3
RCS_1_2_con_210
testcase RCS_1_2_con_210() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_File_Transfer
Mobile Terminated File Transfer
1. Execute “Mobile Terminated Session Establishment” (C.2.2)
2. The test tool sends a file in an MSRP session to User A’s RCS client.
3. Execute “Mobile Terminated Session Termination” (C.3.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_fileTransfer
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 2 User A’s RCS client receives the file.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.4.1
RCS_1_2_con_211
testcase RCS_1_2_con_211() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_File_Transfer
Mobile terminated file transfer – Rejected
1. Execute “Mobile Terminated Session – Reject” (C.4.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
User A’s RCS device is configured with File Transfer Auto-accept set to “off” (ftAutAccept set to 0)
Applicability:
ics_fileTransfer
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 1 on User A’s RCS client shows no ongoing file transfer.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.4.3
RCS_1_2_con_212
testcase RCS_1_2_con_212() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_File_Transfer
File size limit
1. Execute steps 1 to 3 of “Mobile Terminated Session Establishment: File Transfer” (C.2.2) from User B,
for a file of size larger than FT MAX SIZE (i.e. maximum file size User A’s RCS client is allowed to receive,
given by ixit_FTMAXSIZE).
2. User A’s RCS client auto-rejects the file transfer invitation request with a 603 DECLINE towards User B
(and User A receives a warning message).
3. The test tool sends a SIP ACK message to User A’s RCS client
Requirements: User A is IMS registered for RCS
User A’s RCS device is provisioned for RCS
User A’s RCS device is configured with a non-zero value of FT MAX SIZE
User A’s RCS device as 3G, HSPA or Wi-Fi connectivity
Applicability:
ics_fileTransfer
ixit:
ixit_FTMAXSIZE
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A’s RCS client auto-rejects the file transfer invitation request.
2. At step 2 User A receives a warning message indicating file size too large.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.4.6
RCS_1_2_con_213
testcase RCS_1_2_con_213() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_File_Transfer
File size warning
1. Execute steps 1 to 3 of “Mobile Terminated Session Establishment: File Transfer” (C.2.2) from User B,
for a file of size larger than FT WARN SIZE (i.e. maximum file size User A’s RCS client is allowed to receive,
given by ixit_FTMAXSIZE, before a warning requesting confirmation is required).
2. User A’s RCS client determines file is of size larger than FT WARN SIZE and User A receives a
warning message requesting confirmation.
3. User A accepts the confirmation request.
4. Continue to execute steps 6 to 8 of “Mobile Terminated Session Establishment: File Transfer” (C.2.2).
Requirements: User A is IMS registered for RCS
User A’s RCS device is provisioned for RCS
User A’s RCS device is configured with a non-zero value of FT WARN SIZE
User A’s RCS device as 3G, HSPA or Wi-Fi connectivity
Applicability:
ics_fileTransfer
ixit:
ixit_FTWARNSIZE
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 2 User A receives a warning message requesting confirmation.
2. At step 4 the file is transferred successfully.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.4.6
RCS_1_2_con_250
testcase RCS_1_2_con_250() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_originated_Image_Sharing
Mobile Originated Image sharing session – Mobile originated Session termination
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. User A initiates an Image Share session towards User B on his device.
4. Execute “Mobile Originated Session Establishment” (C.2.1)
5. User A’s RCS client sends an image in an MSRP session.
6. Execute “Mobile Originated Session Termination” (C.4.1)
7. Execute “Mobile Terminated Capability Exchange” (C.1.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_imageShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 5 the MSRP session is setup correctly and an image is transferred successfully.
2. At step 7 on User A’s RCS client shows User B still as available for image sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.8
RCS_1_2_con_251
testcase RCS_1_2_con_251() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_originated_Image_Sharing
Mobile originated image sharing session establishment – Rejected
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. User A initiates an Image Share session towards User B on his device.
4. Execute “Mobile Originated Call – Reject” (C.4.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_imageShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 4 User A’s RCS client shows User B rejected the image sharing session.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.11
RCS_1_2_con_270
testcase RCS_1_2_con_270() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Image_Sharing
Mobile Terminated Image sharing session – Mobile Terminated session termination
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. Execute “Mobile Terminated Session Establishment” (C.2.2)
4. The test tool sends an image in an MSRP session to User A’s RCS client.
5. Execute “Mobile Terminated Session Termination” (C.3.2)
6. Execute “Mobile Originated Capability Exchange” (C.1.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_imageShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 4 User A’s RCS client receives the image.
2. At step 6 User A’s RCS client shows User B still as available for image sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.8
RCS_1_2_con_271
testcase RCS_1_2_con_271() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Image_Sharing
Mobile terminated Image sharing session establishment – Rejected
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. Execute “Mobile Terminated Session – Reject” (C.4.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_imageShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- At - step 3 on User A’s RCS client shows no ongoing image share session.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.11
RCS_1_2_con_300
testcase RCS_1_2_con_300() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Video_Sharing
Mobile Originated Video sharing session – Mobile originated termination
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. User A initiates a Video Share session towards User B on his device.
4. Execute “Mobile Originated Session Establishment” (C.2.1)
5. User A terminates the Video Share session.
6. Execute “Mobile Originated Session Termination” (C.4.1)
7. Execute “Mobile Terminated Capability Exchange” (C.1.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 4 the test tool receives an RTP video stream from User a’s RCS device.
2. At step 7 User A’s RCS client shows User B still as available for video sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.4
RCS_1_2_con_301
testcase RCS_1_2_con_301() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Video_Sharing
Mobile Terminated Video sharing session – Mobile Terminated Session termination
1. User A establishes a CS Voice call to User B.
2 Execute “Mobile Originated Capability Exchange” (C.1.1)
3. User A initiates a Video Share session towards User B on his device.
4. Execute “Mobile Originated Session Establishment” (C.2.1)
5. Execute “Mobile Terminated Session Termination” (C.3.2)
6. Execute “Mobile Originated Capability Exchange” (C.1.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 3 the test tool receives an RTP video stream from User a’s RCS device.
2. At step 5 User A’s RCS client shows User B still as available for video sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.5
RCS_1_2_con_302
testcase RCS_1_2_con_302() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Originated_Video_Sharing
Unsuccessful mobile originated video sharing session establishment
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. User A initiates a Video Share session towards User B on his device.
4. Execute “Mobile Originated Session – Reject” (C.4.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 4 User A’s RCS client shows User B rejected the video sharing session.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.11
RCS_1_2_con_320
testcase RCS_1_2_con_320() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Video_Sharing
Mobile Terminated Video sharing session – Mobile Terminated Session termination
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. Execute “Mobile Terminated Session Establishment” (C.2.2)
4. The test tool sends a video stream to User A’s RCS client.
5. Execute “Mobile Terminated Session Termination” (C.3.2)
6. Execute “Mobile Originated Capability Exchange” (C.1.1)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 4 on User A’s RCS client the video stream received from User B can be seen.
2. At step 6 User A’s RCS client shows User B still as available for video sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.4
RCS_1_2_con_321
testcase RCS_1_2_con_321() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Video_Sharing
Mobile Terminated Video sharing session – Mobile Originated session termination
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. Execute “Mobile Terminated Session Establishment” (C.2.2)
4. The test tool sends a video stream to User A’s RCS client.
5. User A terminates the Video Share session.
6. Execute “Mobile Originated Session Termination” (C.4.1)
7. Execute “Mobile Terminated Capability Exchange” (C.1.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- 1. - At step 4 on User A’s RCS client the video stream received from User B can be seen.
2. At step 7 User A’s RCS client shows User B still as available for video sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.5
RCS_1_2_con_322
testcase RCS_1_2_con_322() runs on MTC_IMS system SYSTEM_IMS
Declared in group g_Mobile_Terminated_Video_Sharing
Unsuccessful mobile terminated video sharing session establishment
1. User A establishes a CS Voice call to User B.
2. Execute “Mobile Originated Capability Exchange” (C.1.1)
3. Execute “Mobile Terminated Session – Reject” (C.4.2)
Requirements: User A’s RCS device is provisioned for RCS
User A is IMS registered for RCS
Applicability:
ics_videoShare
Runs On: MTC_IMS
System: SYSTEM_IMS
Verdicts:
- . - At step 3 User A’s RCS client shows User B as still available for video sharing.
See also: RCS-e – Advanced Communications: Services and Client Specification 3.3.11
© Copyright Testing Technologies IST GmbH 2013
provided by TTworkbench