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_Group_Chat

Declared in module RCS_Testcases

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

Details

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