OVERVIEW INDEX DEPRECATED HELP CORRESPONDENCES

provided by TTworkbench

Module Parameters Data Types Component Types Port Types Constants Templates Signatures Functions Altsteps Test Cases

Group g_Mobile_Originated_1_to_1_Chat

Declared in module RCS_Testcases

Test Cases Summary
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.

Details

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