Datasets:

OrganizedProgrammers
/

ETSISpecContent

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 194k rows

hash stringlengths 32 32	doc_id stringlengths 7 13	section stringlengths 3 121	content stringlengths 0 3.82M
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.4.3.4.1 UC_RCS_6_I: SIP message flow for 1-to-many chat with CF_INT_AS	Following there are the expected common call flow sequences for normal procedure of 1-to-many chat. It is assumed that in 1-to-many chat there should be additional user C, but for the clarity in the call flow sequences only two users presented since the message flow for UE_C is the same as for the other users. NOTE 1: In this Use Case AS/IM_A server assumes to be a Controlling IM server for 1-to-many Chat sessions and UE_A should have configured IM CONFERENCE FACTORY URI. NOTE 2: According to RCS-e specification [11] delivery and display notifications in 1-to-many Chat are not required and therefore not presented in this Use Case CFW. The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_INT_AS 1 User A initiates a 1-to-many Chat with User B and User C by sending initial message Step 1 2 User A is informed that the 1-to-many Chat is established Step 8 3 User B is informed of incoming invitation from User A to join the 1-to-many Chat Step 25 4 User B reads the initial message and accepts the 1-to-many Chat invitation Step 26 5 User A is notified with list of 1-to-many Chat participants Step 47 6 User B is notified with list of 1-to-many Chat participants Step 71 7 Users perform messaging in the 1-to-many Chat Step 79 8A User B leaves the 1-to-many Chat Step 80A 8B User A leaves the 1-to-many Chat Step 80B 9A User B is informed that he has left the 1-to-many Chat Step 95A 9B User A is informed that he has left the 1-to-many Chat Step 85B 10A User A is notified that all other users have left the 1-to-many Chat Step 98A 10B User B is notified that all other users have left the 1-to-many Chat Step 93B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 39 Step Action CF_INT_AS 11A User A leaves the 1-to-many Chat Step 101A 11B User B leaves the 1-to-many Chat Step 101B 12A User A is informed that the 1-to-many Chat has ended Step 106A 12B User B is informed that the 1-to-many Chat has ended Step 116B Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User A initiates a 1-to-many Chat with User B and User C by sending initial message 2 INVITE UE_A sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users and the first SDP offer indicating all specific data for MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to AS/IM_A 5 100 Trying AS/IM_A responds with a 100 Trying provisional response 6 200 OK AS/IM_A responds INVITE with 200 OK response with IM session Identity allocated for the current 1-to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up 7 200 OK IMS_A forwards 200 OK response to AS/IM_A 8 User A is informed that the 1-to- many Chat is established 9 ACK UE_A acknowledges the receipt of 200 OK for INVITE 10 ACK IMS_A forwards ACK to AS/IM_A 11 INVITE AS/IM_A sends INVITE to UE_B with IM session identity (allocated for the current 1-to-many Chat) and IM address of the Inviting IM UE (UE_A) 12 100 Trying IMS_A responds with a 100 Trying provisional response 13 INVITE IMS_A forwards INVITE to IBCF_A 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IBCF_B 16 100 Trying IBCF_B responds with a 100 Trying provisional response 17 INVITE IBCF_B forwards INVITE to IMS_B 18 100 Trying IMS_B responds with a 100 Trying provisional response 19 INVITE IMS_B forwards INVITE to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 40 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 20 100 Trying AS/IM_B responds with a 100 Trying provisional response 21 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 22 100 Trying IMS_B responds with a 100 Trying provisional response 23 INVITE IMS_B forwards INVITE to UE_B 24 100 Trying UE_B optionally responds with a 100 Trying provisional response 25 User B is informed of incoming invitation from User A to join the 1-to-many Chat 26 User B reads the initial message and accepts the 1-to-many Chat invitation 27 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 28 200 OK IMS_B forwards 200 OK response to AS/IM_B 29 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 30 200 OK IMS_B forwards 200 OK response to IBCF_B 31 200 OK IBCF_B forwards 200 OK response to IBCF_A 32 200 OK IBCF_A forwards 200 OK response to IMS_A 33 200 OK IMS_A forwards 200 OK response to AS/IM_A 34 ACK AS/IM_A acknowledges the receipt of 200 OK for INVITE 35 ACK IMS_A forwards ACK to IBCF_A 36 ACK IBCF_A forwards ACK to IBCF_B 37 ACK IBCF_B forwards ACK to IMS_B 38 ACK IMS_B forwards ACK to AS/IM_B 39 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 40 ACK IMS_B forwards ACK to UE_B 41 SUBSCRIBE UE_A subscribes to the conference event package 42 SUBSCRIBE IMS_A forwards SUBCRIBE to AS/IM_A 43 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 44 200 OK IMS_A forwards 200 OK response to UE_A 45 NOTIFY AS/IM_A sends NOTIFY to UE_A with list of 1-to-many Chat participants ETSI ETSI TS 102 901 V4.1.1 (2012-05) 41 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 46 NOTIFY IMS_A forwards the NOTIFY to UE_A 47 User A is notified with list of 1-to- many Chat participants 48 200 OK UE_A responds with 200 OK to IMS_A 49 200 OK IMS_A forwards the 200 OK response to AS/IM_A 50 SUBSCRIBE UE_B subscribes to the conference event package 51 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 52 SUBSCRIBE AS/IM_B returns, possibly modified, SUBSCRIBE to IMS_B 53 SUBSCRIBE IMS_B forwards SUBSCRIBE to IBCF_B 54 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IBCF_A 55 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IMS_A 56 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 57 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 58 200 OK IMS_A forwards 200 OK response to IBCF_A 59 200 OK IBCF_A forwards 200 OK response to IBCF_B 60 200 OK IBCF_B forwards 200 OK response to IMS_B 61 200 OK IMS_B forwards 200 OK response to AS/IM_B 62 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 63 200 OK IMS_B forwards 200 OK response to UE_B 64 NOTIFY AS/IM_A sends NOTIFY to UE_B with list of 1-to-many Chat participants 65 NOTIFY IMS_A forwards BYE to IBCF_A 66 NOTIFY IBCF_A forwards BYE to IBCF_B 67 NOTIFY IBCF_B forwards BYE to IMS_B 68 NOTIFY IMS_B forwards BYE to AS/IM_B 69 NOTIFY AS/IM_B returns, possibly modified, BYE to IMS_B 70 NOTIFY IMS_B forwards BYE to UE_B 71 User B is notified with list of 1-to- many Chat participants 72 200 OK UE_B sends 200 OK for NOTIFY 73 200 OK IMS_B forwards 200 OK response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 42 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 74 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 75 200 OK IMS_B forwards 200 OK response to IBCF_B 76 200 OK IBCF_B forwards 200 OK response to IBCF_A 77 200 OK IBCF_A forwards 200 OK response to IMS_A 78 200 OK IMS_A forwards 200 OK response to AS/IM_A 79 Users perform messaging in the 1-to-many Chat (see clause 5.3.2.1 Chat 1 to many via MSRP - Interworking and use 5.4.2 test description) 80A User B leaves the 1-to-many Chat 81A BYE UE_B sends BYE to IMS_B to leave the 1-to-many Chat 82A BYE IMS_B forwards BYE to AS/IM_B 83A BYE AS/IM_B returns, possibly modified, BYE to IMS_B 84A BYE IMS_B forwards BYE to IBCF_B 85A BYE IBCF_B forwards BYE to IBCF_A 86A BYE IBCF_A forwards BYE to IMS_A 87A BYE IMS_A forwards BYE to AS/IM_A 88A 200 OK AS/IM_A sends 200 OK for BYE 89A 200 OK IMS_A forwards 200 OK response to IBCF_A 90A 200 OK IBCF_A forwards 200 OK response to IBCF_B 91A 200 OK IBCF_B forwards 200 OK response to IMS_B 92A 200 OK IMS_B forwards 200 OK response to AS/IM_B 93A 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 94A 200 OK IMS_B forwards 200 OK response to UE_B 95A User B is informed that he has left the 1-to-many Chat 96A NOTIFY AS/IM_A sends NOTIFY to IMS _A to inform UE_A that User B has left the 1-to-many Chat 97A NOTIFY IMS_A forwards the NOTIFY to UE_A 98A User A is notified that all other users have left the 1-to-many Chat 99A 200 OK UE_A responds with 200 OK to IMS_A 100A 200 OK IMS_A forwards the 200 OK response to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 43 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 101A User A leaves the 1-to-many Chat 102A BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 103A BYE IMS_A forwards BYE to AS/IM_A 104A 200 OK AS/IM_A sends 200 OK for BYE 105A 200 OK IMS_A forwards 200 OK response to UE_A 106A User A is informed that the 1-to- many Chat has ended 80B User A leaves the 1-to-many Chat 81B BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 82B BYE IMS_A forwards BYE to AS/IM_A 83B 200 OK AS/IM_A sends 200 OK for BYE 84B 200 OK IMS_A forwards 200 OK response to UE_A 85B User A is informed that he has left the 1-to-many Chat 86B NOTIFY AS/IM_A sends NOTIFY to IMS_A to inform UE_B that User A has left the 1-to-many Chat 87B NOTIFY IMS_A forwards BYE to IBCF_A 88B NOTIFY IBCF_A forwards BYE to IBCF_B 89B NOTIFY IBCF_B forwards BYE to IMS_B 90B NOTIFY IMS_B forwards BYE to AS/IM_B 91B NOTIFY AS/IM_B returns, possibly modified, BYE to IMS_B 92B NOTIFY IMS_B forwards BYE to UE_B 93B User B is notified that all other users have left the 1-to-many Chat 94B 200 OK UE_B sends 200 OK for NOTIFY 95B 200 OK IMS_B forwards 200 OK response to AS/IM_B 96B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 97B 200 OK IMS_B forwards 200 OK response to IBCF_B 98B 200 OK IBCF_B forwards 200 OK response to IBCF_A 99B 200 OK IBCF_A forwards 200 OK response to IMS_A 100B 200 OK IMS_A forwards 200 OK response to AS/IM_A 101B User B leaves the 1-to-many Chat 102B BYE UE_B sends BYE to IMS_B to leave the 1-to-many Chat ETSI ETSI TS 102 901 V4.1.1 (2012-05) 44 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 103B BYE IMS_B forwards BYE to AS/IM_B 104B BYE AS/IM_B returns, possibly modified, BYE to IMS_B 105B BYE IMS_B forwards BYE to IBCF_B 106B BYE IBCF_B forwards BYE to IBCF_A 107B BYE IBCF_A forwards BYE to IMS_A 108B BYE IMS_A forwards BYE to AS/IM_A 109B 200 OK AS/IM_A sends 200 OK for BYE 110B 200 OK IMS_A forwards 200 OK response to IBCF_A 111B 200 OK IBCF_A forwards 200 OK response to IBCF_B 112B 200 OK IBCF_B forwards 200 OK response to IMS_B 113B 200 OK IMS_B forwards 200 OK response to AS/IM_B 114B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 115B 200 OK IMS_B forwards 200 OK response to UE_B 116B User B is informed that the 1-to- many Chat has ended 4.4.3.4.2 UC_RCS_6_R: SIP message flow 1-to-many chat with CF_ROAM_AS (OPTIONAL) NOTE 1: In this Use Case AS/IM_B server assumes to be a Controlling IM server for 1-to-many Chat sessions and UE_B should have configured IM CONFERENCE FACTORY URI. NOTE 2: According to RCS-e specification [11] delivery and display notifications in 1-to-many Chat are not required and therefore not presented in this Use Case CFW. The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_ROAM_AS 1 User B initiates a 1-to-many Chat with User A and User C by sending initial message Step 1 2 User B is informed that the 1-to-many Chat is established Step 17 3 User A is informed of incoming invitation from User B to join the 1-to-many Chat Step 37 4 User A reads the initial message and accepts the 1-to-many Chat invitation Step 38 5 User B is notified with list of 1-to-many Chat participants Step 68 6 User A is notified with list of 1-to-many Chat participants Step 95 7 Users perform messaging in the 1-to-many Chat Step 103 8A User A leaves the 1-to-many Chat Step 104A 8B User B leaves the 1-to-many Chat Step 104B 9A User A is informed that he has left the 1-to-many Chat Step 119A 9B User B is informed that he has left the 1-to-many Chat Step 115B 10A User B is notified that all other users have left the 1-to-many Chat Step 125A 10B User A is notified that all other users have left the 1-to-many Chat Step 123B 11A User B leaves the 1-to-many Chat Step 131A 11B User A leaves the 1-to-many Chat Step 131B 12A User B is informed that the 1-to-many Chat has ended Step 142A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 45 Step Action CF_ROAM_AS 12B User A is informed that the 1-to-many Chat has ended Step 146B Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User B initiates a 1-to-many Chat with User A and User C by sending initial message 2 INVITE UE_B sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users and the first SDP offer indicating all specific data for MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to AS/IM_B 11 100 Trying AS/IM_B responds with a 100 Trying provisional response 12 200 OK AS/IM_B responds INVITE with 200 OK response with IM session Identity allocated for the current 1- to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up 13 200 OK IMS_B forwards 200 OK response to IBCF_B 14 200 OK IBCF_B forwards 200 OK response to IBCF_A 15 200 OK IBCF_A forwards 200 OK response to IMS_A 16 200 OK IMS_A forwards 200 OK response to UE_B 17 User B is informed that the 1-to- many Chat is established 18 ACK UE_B acknowledges the receipt of 200 OK for INVITE 19 ACK IMS_A forwards ACK to IBCF_A 20 ACK IBCF_A forwards ACK to IBCF_B 21 ACK IBCF_B forwards ACK to IMS_B 22 ACK IMS_B forwards ACK to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 46 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 23 INVITE AS/IM_B sends INVITE to UE_A with IM session identity (allocated for the current 1-to-many Chat) and IM address of the Inviting IM UE (UE_B) 24 100 Trying IMS_B responds with a 100 Trying provisional response 25 INVITE IMS_B forwards INVITE to IBCF_B 26 100 Trying IBCF_B responds with a 100 Trying provisional response 27 INVITE IBCF_B forwards INVITE to IBCF_A 28 100 Trying IBCF_A responds with a 100 Trying provisional response 29 INVITE IBCF_A forwards INVITE to IMS_A 30 100 Trying IMS_A responds with a 100 Trying provisional response 31 INVITE IMS_A forwards INVITE to AS/IM_A 32 100 Trying AS/IM_A responds with a 100 Trying provisional response 33 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 34 100 Trying IMS_A responds with a 100 Trying provisional response 35 INVITE IMS_A forwards INVITE to UE_A 36 100 Trying UE_A optionally responds with a 100 Trying provisional response 37 User A is informed of incoming invitation from User B to join the 1- to-many Chat 38 User A reads the initial message and accepts the 1-to-many Chat invitation 39 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 40 200 OK IMS_A forwards 200 OK response to AS/IM_A 41 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 42 200 OK IMS_A forwards 200 OK response to IBCF_A 43 200 OK IBCF_A forwards 200 OK response to IBCF_B 44 200 OK IBCF_B forwards 200 OK response to IMS_B 45 200 OK IMS_B forwards 200 OK response to AS/IM_B 46 ACK AS/IM_B acknowledges the receipt of 200 OK for INVITE 47 ACK IMS_B forwards ACK to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 47 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 48 ACK IBCF_B forwards ACK to IBCF_A 49 ACK IBCF_A forwards ACK to IMS_A 50 ACK IMS_A forwards ACK to AS/IM_A 51 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 52 ACK IMS_A forwards ACK to UE_A 53 SUBSCRIBE UE_B subscribes to the conference event package 54 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 55 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 56 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 57 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 58 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 59 200 OK IMS_B forwards 200 OK response to IBCF_B 60 200 OK IBCF_B forwards 200 OK response to IBCF_A 61 200 OK IBCF_A forwards 200 OK response to IMS_A 62 200 OK IMS_A forwards 200 OK response to UE_B 63 NOTIFY AS/IM_B sends NOTIFY to UE_B with list of 1-to-many Chat participants 64 NOTIFY IMS_B forwards NOTIFY to IBCF_B 65 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 66 NOTIFY IBCF_A forwards NOTIFY to IMS_A 67 NOTIFY IMS_A forwards NOTIFY to UE_B 68 User B is notified with list of 1-to- many Chat participants 69 200 OK UE_B responds with 200 OK to IMS_A 70 200 OK IMS_A forwards 200 OK response to IBCF_A 71 200 OK IBCF_A forwards 200 OK response to IBCF_B 72 200 OK IBCF_B forwards 200 OK response to IMS_B 73 200 OK IMS_B forwards 200 OK response to AS/IM_B 74 SUBSCRIBE UE_A subscribes to the conference event package 75 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 76 SUBSCRIBE AS/IM_A returns, possibly modified, SUBSCRIBE to IMS_A 77 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 48 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 78 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 79 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 80 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 81 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 82 200 OK IMS_B forwards 200 OK response to IBCF_B 83 200 OK IBCF_B forwards 200 OK response to IBCF_A 84 200 OK IBCF_A forwards 200 OK response to IMS_A 85 200 OK IMS_A forwards 200 OK response to AS/IM_A 86 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 87 200 OK IMS_A forwards 200 OK response to UE_A 88 NOTIFY AS/IM_B sends NOTIFY to UE_A with list of 1-to-many Chat participants 89 NOTIFY IMS_B forwards BYE to IBCF_B 90 NOTIFY IBCF_B forwards BYE to IBCF_A 91 NOTIFY IBCF_A forwards BYE to IMS_A 92 NOTIFY IMS_A forwards BYE to AS/IM_A 93 NOTIFY AS/IM_A returns, possibly modified, BYE to IMS_A 94 NOTIFY IMS_A forwards BYE to UE_A 95 User A is notified with list of 1-to- many Chat participants 96 200 OK UE_A sends 200 OK for NOTIFY 97 200 OK IMS_A forwards 200 OK response to AS/IM_A 98 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 99 200 OK IMS_A forwards 200 OK response to IBCF_A 100 200 OK IBCF_A forwards 200 OK response to IBCF_B 101 200 OK IBCF_B forwards 200 OK response to IMS_B 102 200 OK IMS_B forwards 200 OK response to AS/IM_B 103 Users perform messaging in the 1- to-many Chat (see clause 5.3.2.2 Chat 1 to many via MSRP - Roaming and use 5.4.2 test description) 104A User A leaves the 1-to-many Chat ETSI ETSI TS 102 901 V4.1.1 (2012-05) 49 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 105A BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 106A BYE IMS_A forwards BYE to AS/IM_A 107A BYE AS/IM_A returns, possibly modified, BYE to IMS_A 108A BYE IMS_A forwards BYE to IBCF_A 109A BYE IBCF_A forwards BYE to IBCF_B 110A BYE IBCF_B forwards BYE to IMS_B 111A BYE IMS_B forwards BYE to AS/IM_B 112A 200 OK AS/IM_B sends 200 OK for BYE 113A 200 OK IMS_B forwards 200 OK response to IBCF_B 114A 200 OK IBCF_B forwards 200 OK response to IBCF_A 115A 200 OK IBCF_A forwards 200 OK response to IMS_A 116A 200 OK IMS_A forwards 200 OK response to AS/IM_A 117A 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 118A 200 OK IMS_A forwards 200 OK response to UE_A 119A User A is informed that he has left the 1-to-many Chat 120A NOTIFY AS/IM_B sends NOTIFY to IMS _B to inform UE_B that User A has left the 1-to-many Chat 121A NOTIFY IMS_B forwards NOTIFY to IBCF_B 122A NOTIFY IBCF_B forwards NOTIFY to IBCF_A 123A NOTIFY IBCF_A forwards NOTIFY to IMS_A 124A NOTIFY IMS_A forwards NOTIFY to UE_B 125A User B is notified that all other users have left the 1-to-many Chat 126A 200 OK UE_B responds with 200 OK to IMS_A 127A 200 OK IMS_A forwards 200 OK response to IBCF_A 128A 200 OK IBCF_A forwards 200 OK response to IBCF_B 129A 200 OK IBCF_B forwards 200 OK response to IMS_B 130A 200 OK IMS_B forwards 200 OK response to AS/IM_B 131A User B leaves the 1-to-many Chat 132A BYE UE_B sends BYE to IMS_A to leave the 1-to-many Chat 133A BYE IMS_A forwards BYE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 50 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 134A BYE IBCF_A forwards BYE to IBCF_B 135A BYE IBCF_B forwards BYE to IMS_B 136A BYE IMS_B forwards BYE to AS/IM_B 137A 200 OK AS/IM_B sends 200 OK for BYE 138A 200 OK IMS_B forwards 200 OK response to IBCF_B 139A 200 OK IBCF_B forwards 200 OK response to IBCF_A 140A 200 OK IBCF_A forwards 200 OK response to IMS_A 141A 200 OK IMS_A forwards 200 OK response to UE_B 142A User B is informed that the 1-to- many Chat has ended 104B User B leaves the 1-to-many Chat 105B BYE UE_B sends BYE to IMS_A to leave the 1-to-many Chat 106B BYE IMS_A forwards BYE to IBCF_A 107B BYE IBCF_A forwards BYE to IBCF_B 108B BYE IBCF_B forwards BYE to IMS_B 109B BYE IMS_B forwards BYE to AS/IM_B 110B 200 OK AS/IM_B sends 200 OK for BYE 111B 200 OK IMS_B forwards 200 OK response to IBCF_B 112B 200 OK IBCF_B forwards 200 OK response to IBCF_A 113B 200 OK IBCF_A forwards 200 OK response to IMS_A 114B 200 OK IMS_A forwards 200 OK response to UE_B 115B User B is informed that he has left the 1-to-many Chat 116B NOTIFY AS/IM_B sends NOTIFY to IMS_B to inform UE_A that User B has left the 1-to-many Chat 117B NOTIFY IMS_B forwards NOTIFY to IBCF_B 118B NOTIFY IBCF_B forwards NOTIFY to IBCF_A 119B NOTIFY IBCF_A forwards NOTIFY to IMS_A 120B NOTIFY IMS_A forwards NOTIFY to AS/IM_A 121B NOTIFY AS/IM_A returns, possibly modified, NOTIFY to IMS_A 122B BYE IMS_A forwards NOTIFY to UE_A 123B User A is informed that User B has left the 1-to-many Chat 124B 200 OK UE_A sends 200 OK for NOTIFY ETSI ETSI TS 102 901 V4.1.1 (2012-05) 51 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 125B 200 OK IMS_A forwards 200 OK response to AS/IM_A 126B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 127B 200 OK IMS_A forwards 200 OK response to IBCF_A 128B 200 OK IBCF_A forwards 200 OK response to IBCF_B 129B 200 OK IBCF_B forwards 200 OK response to IMS_B 130B 200 OK IMS_B forwards 200 OK response to AS/IM_B 131B User A leaves the 1-to-many Chat 132B BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 133B BYE IMS_A forwards BYE to AS/IM_A 134B BYE AS/IM_A returns, possibly modified, BYE to IMS_A 135B BYE IMS_A forwards BYE to IBCF_A 136B BYE IBCF_A forwards BYE to IBCF_B 137B BYE IBCF_B forwards BYE to IMS_B 138B BYE IMS_B forwards BYE to AS/IM_B 139B 200 OK AS/IM_B sends 200 OK for BYE 140B 200 OK IMS_B forwards 200 OK response to IBCF_B 141B 200 OK IBCF_B forwards 200 OK response to IBCF_A 142B 200 OK IBCF_A forwards 200 OK response to IMS_A 143B 200 OK IMS_A forwards 200 OK response to AS/IM_A 144B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 145B 200 OK IMS_A forwards 200 OK response to UE_A 146B User A is informed that the 1-to- many Chat has ended
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.4.3.5 Switching to 1-to-many chat	Following there are the expected common call flow sequences for switching from 1-to-1 chat to 1-to-many chat. It is assumed that in 1-to-many chat there should be additional user C, but for the clarity in the call flow sequences only two users presented since the message flow for UE_C is the same as for the other users. 4.4.3.5.1 UC_RCS_7_I: SIP message flow for switching to 1-to-many chat with CF_INT_AS NOTE 1: In this Use Case AS/IM_A server assumes to be a Controlling IM server for 1-to-many Chat sessions and UE_A should have configured IM CONFERENCE FACTORY URI. ETSI ETSI TS 102 901 V4.1.1 (2012-05) 52 NOTE 2: According to RCS-e specification [11] delivery and display notifications in 1-to-many Chat are not required and therefore not presented in this Use Case CFW. The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_INT_AS 1 User A selects User B in the phone address book and sends him an initial message UC_RCS_4_I Step 1 2 User B is informed of incoming message UC_RCS_4_I Step 20 3 User A is informed that initial message was delivered to user B UC_RCS_4_I Step 39 4 User B reads the initial message from user A and opens the 1-to-1 chat UC_RCS_4_I Step 49 5 Users perform 1-to-1 chatting UC_RCS_4_I Step 68 6 User A initiates a 1-to-many Chat with User B and User C by sending initial message Step 2 7 User A is informed that the 1-to-many Chat is established Step 9 8 User B is informed of incoming invitation from User A to join the 1-to-many Chat Step 26 9 User B reads the initial message and accepts the 1-to-many Chat invitation Step 27 10 User A is notified with list of 1-to-many Chat participants Step 66 11 User B is notified with list of 1-to-many Chat participants Step 90 12 Users perform messaging in the 1-to-many Chat Step 98 13A User B leaves the 1-to-many Chat UC_RCS_6_I Step 80A 13B User A leaves the 1-to-many Chat UC_RCS_6_I Step 80B 14A User B is informed that he has left the 1-to-many Chat UC_RCS_6_I Step 95A 14B User A is informed that he has left the 1-to-many Chat UC_RCS_6_I Step 85B 15A User A is notified that all other users have left the 1-to-many Chat UC_RCS_6_I Step 98A 15B User B is notified that all other users have left the 1-to-many Chat UC_RCS_6_I Step 93B 16A User A leaves the 1-to-many Chat UC_RCS_6_I Step 101A 16B User B leaves the 1-to-many Chat UC_RCS_6_I Step 101B 17A User A is informed that the 1-to-many Chat has ended UC_RCS_6_I Step 106A 17B User B is informed that the 1-to-many Chat has ended UC_RCS_6_I Step 116B Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_I (1-68) 2 User A initiates a 1-to-many Chat with User B and User C by sending initial message 3 INVITE UE_A sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users, the first SDP offer indicating all specific data for MSRP connection set up and the identity of User B with Session- Replaces header 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to AS/IM_A 6 100 Trying AS/IM_A responds with a 100 Trying provisional response 7 200 OK AS/IM_A responds INVITE with 200 OK response with IM session Identity allocated for the current 1- to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up ETSI ETSI TS 102 901 V4.1.1 (2012-05) 53 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 8 200 OK IMS_A forwards 200 OK response to AS/IM_A 9 User A is informed that the 1-to- many Chat is established 10 ACK UE_A acknowledges the receipt of 200 OK for INVITE 11 ACK IMS_A forwards ACK to AS/IM_A 12 INVITE AS/IM_A sends INVITE to UE_B with IM session identity (allocated for the current 1-to-many Chat), IM address of the Inviting IM UE (UE_A) and Session-Replaces header with the original 1-to-1 session identity 13 100 Trying IMS_A responds with a 100 Trying provisional response 14 INVITE IMS_A forwards INVITE to IBCF_A 15 100 Trying IBCF_A responds with a 100 Trying provisional response 16 INVITE IBCF_A forwards INVITE to IBCF_B 17 100 Trying IBCF_B responds with a 100 Trying provisional response 18 INVITE IBCF_B forwards INVITE to IMS_B 19 100 Trying IMS_B responds with a 100 Trying provisional response 20 INVITE IMS_B forwards INVITE to AS/IM_B 21 100 Trying AS/IM_B responds with a 100 Trying provisional response 22 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 23 100 Trying IMS_B responds with a 100 Trying provisional response 24 INVITE IMS_B forwards INVITE to UE_B 25 100 Trying UE_B optionally responds with a 100 Trying provisional response 26 User B is informed of incoming invitation from User A to join the 1- to-many Chat 27 User B reads the initial message and accepts the 1-to-many Chat invitation 28 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 29 200 OK IMS_B forwards 200 OK response to AS/IM_B 30 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 31 200 OK IMS_B forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 54 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 33 200 OK IBCF_A forwards 200 OK response to IMS_A 34 200 OK IMS_A forwards 200 OK response to AS/IM_A 35 ACK AS/IM_A acknowledges the receipt of 200 OK for INVITE 36 ACK IMS_A forwards ACK to IBCF_A 37 ACK IBCF_A forwards ACK to IBCF_B 38 ACK IBCF_B forwards ACK to IMS_B 39 ACK IMS_B forwards ACK to AS/IM_B 40 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 41 ACK IMS_B forwards ACK to UE_B 42 BYE UE_B releases the 1-to-1 IM session with BYE 43 BYE IMS_B forwards BYE to AS/IM_B 44 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 45 BYE IMS_B forwards BYE to IBCF_B 46 BYE IBCF_B forwards BYE to IBCF_A 47 BYE IBCF_A forwards BYE to IMS_A 48 BYE IMS_A forwards BYE to AS/IM_A 49 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 50 BYE IMS_A forwards BYE to UE_A 51 200 OK UE_A sends 200 OK for BYE 52 200 OK IMS_A forwards 200 OK response to AS/IM_A 53 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 54 200 OK IMS_A forwards 200 OK response to IBCF_A 55 200 OK IBCF_A forwards 200 OK response to IBCF_B 56 200 OK IBCF_B forwards 200 OK response to IMS_B 57 200 OK IMS_B forwards 200 OK response to AS/IM_B 58 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 59 200 OK IMS_B forwards 200 OK response to UE_B 60 SUBSCRIBE UE_A subscribes to the conference event package 61 SUBSCRIBE IMS_A forwards SUBCRIBE to AS/IM_A 62 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 63 200 OK IMS_A forwards 200 OK response to UE_A 64 NOTIFY AS/IM_A sends NOTIFY to UE_A with list of 1-to-many Chat participants 65 NOTIFY IMS_A forwards the NOTIFY to UE_A 66 User A is notified with list of 1-to- many Chat participants ETSI ETSI TS 102 901 V4.1.1 (2012-05) 55 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 67 200 OK UE_A responds with 200 OK to IMS_A 68 200 OK IMS_A forwards the 200 OK response to AS/IM_A 69 SUBSCRIBE UE_B subscribes to the conference event package 70 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 71 SUBSCRIBE AS/IM_B returns, possibly modified, SUBSCRIBE to IMS_B 72 SUBSCRIBE IMS_B forwards SUBSCRIBE to IBCF_B 73 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IBCF_A 74 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IMS_A 75 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 76 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 77 200 OK IMS_A forwards 200 OK response to IBCF_A 78 200 OK IBCF_A forwards 200 OK response to IBCF_B 79 200 OK IBCF_B forwards 200 OK response to IMS_B 80 200 OK IMS_B forwards 200 OK response to AS/IM_B 81 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 82 200 OK IMS_B forwards 200 OK response to UE_B 83 NOTIFY AS/IM_A sends NOTIFY to UE_B with list of 1-to-many Chat participants 84 NOTIFY IMS_A forwards BYE to IBCF_A 85 NOTIFY IBCF_A forwards BYE to IBCF_B 86 NOTIFY IBCF_B forwards BYE to IMS_B 87 NOTIFY IMS_B forwards BYE to AS/IM_B 88 NOTIFY AS/IM_B returns, possibly modified, BYE to IMS_B 89 NOTIFY IMS_B forwards BYE to UE_B 90 User B is notified with list of 1-to- many Chat participants 91 200 OK UE_B sends 200 OK for NOTIFY 92 200 OK IMS_B forwards 200 OK response to AS/IM_B 93 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 94 200 OK IMS_B forwards 200 OK response to IBCF_B 95 200 OK IBCF_B forwards 200 OK response to IBCF_A 96 200 OK IBCF_A forwards 200 OK response to IMS_A 97 200 OK IMS_A forwards 200 OK response to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 56 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 98 Users perform messaging in the 1- to-many Chat(see clause 5.3.2.1 Chat 1 to many via MSRP - Interworking and use 5.4.2 test description) 99 Continue UC_RCS_6_I (80A-116B) 4.4.3.5.2 UC_RCS_7_R: SIP message flow for switching to 1-to-many chat with CF_ROAM_AS (OPTIONAL) NOTE 1: In this Use Case AS/IM_B server assumes to be a Controlling IM server for 1-to-many Chat sessions and UE_B should have configured IM CONFERENCE FACTORY URI. NOTE 2: According to RCS-e specification [11] delivery and display notifications in 1-to-many Chat are not required and therefore not presented in this Use Case CFW. The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_ROAM_AS 1 User B selects User A in the phone address book and sends him an initial message UC_RCS_4_R Step 1 2 User A is informed of incoming message UC_RCS_4_R Step 26 3 User B is informed that initial message was delivered to user A UC_RCS_4_R Step 51 4 User A reads the initial message from user B and opens the 1-to-1 chat UC_RCS_4_R Step 64 5 Users perform 1-to-1 chatting UC_RCS_4_R Step 89 6 User B initiates a 1-to-many Chat with User A and User C by sending initial message Step 2 7 User B is informed that the 1-to-many Chat is established Step 18 8 User A is informed of incoming invitation from User B to join the 1-to-many Chat Step 38 9 User A reads the initial message and accepts the 1-to-many Chat invitation Step 39 10 User B is notified with list of 1-to-many Chat participants Step 93 11 User A is notified with list of 1-to-many Chat participants Step 120 12 Users perform messaging in the 1-to-many Chat Step 128 13A User A leaves the 1-to-many Chat UC_RCS_6_R Step 104A 13B User B leaves the 1-to-many Chat UC_RCS_6_R Step 104B 14A User A is informed that he has left the 1-to-many Chat UC_RCS_6_R Step 119A 14B User B is informed that he has left the 1-to-many Chat UC_RCS_6_R Step 115B 15A User B is notified that all other users have left the 1-to-many Chat UC_RCS_6_R Step 125A 15B User A is notified that all other users have left the 1-to-many Chat UC_RCS_6_R Step 123B 16A User B leaves the 1-to-many Chat UC_RCS_6_R Step 131A 16B User A leaves the 1-to-many Chat UC_RCS_6_R Step 131B 17A User B is informed that the 1-to-many Chat has ended UC_RCS_6_R Step 142A 17B User A is informed that the 1-to-many Chat has ended UC_RCS_6_R Step 146B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 57 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_R (1-89) 2 User B initiates a 1-to-many Chat with User A and User C by sending initial message 3 INVITE UE_B sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users, the first SDP offer indicating all specific data for MSRP connection set up and the identity of User A with Session- Replaces header 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to AS/IM_B 12 100 Trying AS/IM_B responds with a 100 Trying provisional response 13 200 OK AS/IM_B responds INVITE with 200 OK response with IM session Identity allocated for the current 1- to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up 14 200 OK IMS_B forwards 200 OK response to IBCF_B 15 200 OK IBCF_B forwards 200 OK response to IBCF_A 16 200 OK IBCF_A forwards 200 OK response to IMS_A 17 200 OK IMS_A forwards 200 OK response to UE_B 18 User B is informed that the 1-to- many Chat is established 19 ACK UE_B acknowledges the receipt of 200 OK for INVITE 20 ACK IMS_A forwards ACK to IBCF_A 21 ACK IBCF_A forwards ACK to IBCF_B 22 ACK IBCF_B forwards ACK to IMS_B 23 ACK IMS_B forwards ACK to AS/IM_B 24 INVITE AS/IM_B sends INVITE to UE_A with IM session identity (allocated for the current 1-to-many Chat), IM address of the Inviting IM UE (UE_B) and Session-Replaces header with the original 1-to-1 session identity ETSI ETSI TS 102 901 V4.1.1 (2012-05) 58 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 25 100 Trying IMS_B responds with a 100 Trying provisional response 26 INVITE IMS_B forwards INVITE to IBCF_B 27 100 Trying IBCF_B responds with a 100 Trying provisional response 28 INVITE IBCF_B forwards INVITE to IBCF_A 29 100 Trying IBCF_A responds with a 100 Trying provisional response 30 INVITE IBCF_A forwards INVITE to IMS_A 31 100 Trying IMS_A responds with a 100 Trying provisional response 32 INVITE IMS_A forwards INVITE to AS/IM_A 33 100 Trying AS/IM_A responds with a 100 Trying provisional response 34 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 35 100 Trying IMS_A responds with a 100 Trying provisional response 36 INVITE IMS_A forwards INVITE to UE_A 37 100 Trying UE_A optionally responds with a 100 Trying provisional response 38 User A is informed of incoming invitation from user B to join the 1- to-many Chat 39 User A reads the initial message and accepts the 1-to-many Chat invitation 40 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 41 200 OK IMS_A forwards 200 OK response to AS/IM_A 42 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 43 200 OK IMS_A forwards 200 OK response to IBCF_A 44 200 OK IBCF_A forwards 200 OK response to IBCF_B 45 200 OK IBCF_B forwards 200 OK response to IMS_B 46 200 OK IMS_B forwards 200 OK response to AS/IM_B 47 ACK AS/IM_B acknowledges the receipt of 200 OK for INVITE 48 ACK IMS_B forwards ACK to IBCF_B 49 ACK IBCF_B forwards ACK to IBCF_A 50 ACK IBCF_A forwards ACK to IMS_A 51 ACK IMS_A forwards ACK to AS/IM_A 52 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 53 ACK IMS_A forwards ACK to UE_A 54 BYE UE_A releases the 1-to-1 IM session with BYE 55 BYE IMS_A forwards BYE to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 59 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 56 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 57 BYE IMS_A forwards BYE to IBCF_A 58 BYE IBCF_A forwards BYE to IBCF_B 59 BYE IBCF_B forwards BYE to IMS_B 60 BYE IMS_B forwards BYE to AS/IM_B 61 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 62 BYE IMS_B forwards BYE to IBCF_B 63 BYE IBCF_B forwards BYE to IBCF_A 64 BYE IBCF_A forwards BYE to IMS_A 65 BYE IMS_A forwards BYE to UE_B 66 200 OK UE_B sends 200 OK for BYE 67 200 OK IMS_A forwards 200 OK response to IBCF_A 68 200 OK IBCF_A forwards 200 OK response to IBCF_B 69 200 OK IBCF_B forwards 200 OK response to IMS_B 70 200 OK IMS_B forwards 200 OK response to AS/IM_B 71 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 72 200 OK IMS_B forwards 200 OK response to IBCF_B 73 200 OK IBCF_B forwards 200 OK response to IBCF_A 74 200 OK IBCF_A forwards 200 OK response to IMS_A 75 200 OK IMS_A forwards 200 OK response to AS/IM_A 76 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 77 200 OK IMS_A forwards 200 OK response to UE_A 78 SUBSCRIBE UE_B subscribes to the conference event package 79 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 80 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 81 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 82 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 83 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 84 200 OK IMS_B forwards 200 OK response to IBCF_B 85 200 OK IBCF_B forwards 200 OK response to IBCF_A 86 200 OK IBCF_A forwards 200 OK response to IMS_A 87 200 OK IMS_A forwards 200 OK response to UE_B 88 NOTIFY AS/IM_B sends NOTIFY to UE_B with list of 1-to-many Chat participants ETSI ETSI TS 102 901 V4.1.1 (2012-05) 60 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 89 NOTIFY IMS_B forwards NOTIFY to IBCF_B 90 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 91 NOTIFY IBCF_A forwards NOTIFY to IMS_A 92 NOTIFY IMS_A forwards NOTIFY to UE_B 93 User B is notified with list of 1-to- many Chat participants 94 200 OK UE_B responds with 200 OK to IMS_A 95 200 OK IMS_A forwards 200 OK response to IBCF_A 96 200 OK IBCF_A forwards 200 OK response to IBCF_B 97 200 OK IBCF_B forwards 200 OK response to IMS_B 98 200 OK IMS_B forwards 200 OK response to AS/IM_B 99 SUBSCRIBE UE_A subscribes to the conference event package 100 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 101 SUBSCRIBE AS/IM_A returns, possibly modified, SUBSCRIBE to IMS_A 102 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 103 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 104 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 105 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 106 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 107 200 OK IMS_B forwards 200 OK response to IBCF_B 108 200 OK IBCF_B forwards 200 OK response to IBCF_A 109 200 OK IBCF_A forwards 200 OK response to IMS_A 110 200 OK IMS_A forwards 200 OK response to AS/IM_A 111 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 112 200 OK IMS_A forwards 200 OK response to UE_A 113 NOTIFY AS/IM_B sends NOTIFY to UE_A with list of 1-to-many Chat participants 114 NOTIFY IMS_B forwards BYE to IBCF_B 115 NOTIFY IBCF_B forwards BYE to IBCF_A 116 NOTIFY IBCF_A forwards BYE to IMS_A 117 NOTIFY IMS_A forwards BYE to AS/IM_A 118 NOTIFY AS/IM_A returns, possibly modified, BYE to IMS_A 119 NOTIFY IMS_A forwards BYE to UE_A 120 User A is notified with list of 1-to- many Chat participants ETSI ETSI TS 102 901 V4.1.1 (2012-05) 61 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 121 200 OK UE_A sends 200 OK for NOTIFY 122 200 OK IMS_A forwards 200 OK response to AS/IM_A 123 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 124 200 OK IMS_A forwards 200 OK response to IBCF_A 125 200 OK IBCF_A forwards 200 OK response to IBCF_B 126 200 OK IBCF_B forwards 200 OK response to IMS_B 127 200 OK IMS_B forwards 200 OK response to AS/IM_B 128 Users perform messaging in the 1- to-many Chat (see clause 5.3.2.2 Chat 1 to many via MSRP - Roaming and use 5.4.2 test description) 129 Continue UC_RCS_6_R (104A- 146B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.4.4 RCS-e services during a call	RCS-e services during a call include two main types of Content sharing: • Video sharing; • Pictures sharing. The main difference between these types of Content sharing is in the media session protocol. In case of Video sharing users establish RTP media session and for the Pictures sharing purposes MSRP connection is used. Since the call flow sequences for Pictures and Video sharing are similar in the Use Cases below there is only a common procedure of Content sharing described. In the case of sharing a file (picture) during a call follow Use Cases provided in the File transfer service clause 4.4.5. For Use Cases of Content sharing during a call it is assumed that UEs registered on the corresponding IMS networks and they have already performed capability discovery procedures. In particular, users subscribed to RCS-e services during a call such as video and pictures sharing.
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.4.4.1 Content sharing
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.4.4.1.1 UC_RCS_8_I: SIP message flow for Content sharing with CF_INT_CALL	The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering). Step Action CF_INT_CALL 1A User A establishes voice call with user B Step 1A 1B User B establishes voice call with user A Step 1B 2 User A requests to share content with user B Step 2 3 User B is requested to accept to share content Step 13 4 User B accepts to share content with user A Step 19 5 User A is informed that request has been answered Step 25 6 Content sharing starts Step 31 7A User A ends content sharing Step 32A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 62 Step Action CF_INT_CALL 8A User B is informed that content sharing has terminated Step 38A 9A User A is informed that content sharing has terminated Step 44A 10A User A initiates voice call termination Step 55A 7B User B ends content sharing Step 32B 8B User A is informed that content sharing has terminated Step 38B 9B User B is informed that content sharing has terminated Step 44B 10B User B initiates voice call termination Step 55B The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share content with user B 3 INVITE UE_A sends INVITE to share content with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to UE_B 12 100 Trying UE_B responds with a 100 Trying provisional response 13 User B is requested to accept to share content 14 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 15 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 16 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 17 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User B accepts to share content 20 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 21 200 OK IMS_B forwards 200 OK response to IBCF_B 22 200 OK IBCF_B forwards 200 OK response to IBCF_A 23 200 OK IBCF_A forwards 200 OK response to IMS_A 24 200 OK IMS_A forwards 200 OK response to UE_A 25 User A is informed that request has been answered 26 ACK UE_A acknowledges the receipt of 200 OK for INVITE 27 ACK IMS_A forwards ACK to IBCF_A 28 ACK IBCF_A forwards ACK to IBCF_B 29 ACK IBCF_B forwards ACK to IMS_B 30 ACK IMS_B forwards ACK to UE_B 31 Content sharing starts (see clause 5.3.3 Image data via MSRP and use 5.4.3 test description) ETSI ETSI TS 102 901 V4.1.1 (2012-05) 63 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 32A User A ends content sharing 33A BYE UE_A releases the call with BYE 34A BYE IMS_A forwards BYE to IBCF_A 35A BYE IBCF_A forwards BYE to IBCF_B 36A BYE IBCF_B forwards BYE to IMS_B 37A BYE IMS_B forwards BYE to UE_B 38A User B is informed that content sharing has ended 39A 200 OK UE_B sends 200 OK for BYE 40A 200 OK IMS_B forwards 200 OK response to IBCF_B 41A 200 OK IBCF_B forwards 200 OK response to IBCF_A 42A 200 OK IBCF_A forwards 200 OK response to IMS_A 43A 200 OK IMS_A forwards the 200 OK response to UE_A 44A User A is informed that content sharing has ended 45A OPTIONS UE_B sends OPTIONS to IMS_B to verify availability of video sharing capability of the UE_A 46A OPTIONS IMS_B forwards OPTIONS to IBCF_B 47A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 48A OPTIONS IBCF_A forwards OPTIONS to IMS_A 49A OPTIONS IMS_A forwards OPTIONS to UE_A 50A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 51A 200 OK IMS_A forwards 200 OK to IBCF_A 52A 200 OK IBCF_A forwards 200 OK to IBCF_B 53A 200 OK IBCF_B forwards 200 OK to IMS_B 54A 200 OK IMS_B forwards 200 OK to UE_B 55A Voice call termination initiated by user A 32B User B ends content sharing 33B BYE UE_B releases the call with BYE 34B BYE IMS_B forwards BYE to IBCF_B 35B BYE IBCF_B forwards BYE to IBCF_A 36B BYE IBCF_A forwards BYE to IMS_A 37B BYE IMS_A forwards BYE to UE_A 38B User A is informed that content sharing has ended 39B 200 OK UE_A sends 200 OK for BYE 40B 200 OK IMS_A forwards 200 OK response to IBCF_A 41B 200 OK IBCF_A forwards 200 OK response to IBCF_B 42B 200 OK IBCF_B forwards 200 OK response to IMS_B 43B 200 OK IMS_B forwards the 200 OK response to UE_B 44B User B is informed that content sharing has ended 45 OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_B 46 OPTIONS IMS_A forwards OPTIONS to IBCF_A 47 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 48 OPTIONS IBCF_B forwards OPTIONS to IMS_B 49 OPTIONS IMS_B forwards OPTIONS to UE_B 50 200 OK UE_B responds with 200 OK to IMS_B with updated capabilities 51 200 OK IMS_B forwards 200 OK to IBCF_B 52 200 OK IBCF_B forwards 200 OK to IBCF_A 53 200 OK IBCF_A forwards 200 OK to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 64 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 54 200 OK IMS_A forwards 200 OK to UE_A 55B Voice call termination initiated by user B 4.4.4.1.2 UC_RCS_8_R: SIP message flow for Content sharing with CF_ROAM_CALL (OPTIONAL) The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering). Step Action CF_ROAM_CALL 1A User A establishes voice call with user B Step 1A 1B User B establishes voice call with user A Step 1B 2 User A requests to share content with user B Step 2 3 User B is requested to accept to share content Step 19 4 User B accepts to share content with user A Step 28 5 User A is informed that request has been answered Step 37 6 Content sharing starts Step 46 7A User A ends content sharing Step 47A 8A User B is informed that content sharing has terminated Step 56A 9A User A is informed that content sharing has terminated Step 65A 10A User A initiates voice call termination Step 82A 7B User B ends content sharing Step 47B 8B User A is informed that content sharing has terminated Step 56B 9B User B is informed that content sharing has terminated Step 65B 10B User B initiates voice call termination Step 82B The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share content with user B 3 INVITE UE_A sends INVITE to share content with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IBCF_A 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 65 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 16 100 Trying IMS_A responds with a 100 Trying provisional response 17 INVITE IMS_A forwards INVITE to UE_B 18 100 Trying UE_B responds with a 100 Trying provisional response 19 User B is requested to accept to share content 20 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 21 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 22 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 23 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 24 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 27 180 Ringing IMS_A forwards 180 Ringing response to UE_A 28 User B accepts to share content 29 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 30 200 OK IMS_A forwards 200 OK response to IBCF_A 31 200 OK IBCF_A forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IMS_B 33 200 OK IMS_B forwards 200 OK response to IBCF_B 34 200 OK IBCF_B forwards 200 OK response to IBCF_A 35 200 OK IBCF_A forwards 200 OK response to IMS_A 36 IMS_A forwards 200 OK response to UE_A 37 User A is informed that request has been answered 38 ACK UE_A acknowledges the receipt of 200 OK for INVITE 39 ACK IMS_A forwards ACK to IBCF_A 40 ACK IBCF_A forwards ACK to IBCF_B 41 ACK IBCF_B forwards ACK to IMS_B 42 ACK IMS_B forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IBCF_A 44 ACK IBCF_A forwards ACK to IMS_A 45 ACK IMS_A forwards ACK to UE_B 46 Content sharing starts (see clause 5.3.3 Image data via MSRP and use 5.4.3 test description) 47A User A ends content sharing 48A BYE UE_A releases the call with BYE 49A BYE IMS_A forwards BYE to IBCF_A 50A BYE IBCF_A forwards BYE to IBCF_B 51A BYE IBCF_B forwards BYE to IMS_B 52A BYE IMS_B forwards BYE to IBCF_B 53A BYE IBCF_B forwards BYE to IBCF_A 54A BYE IBCF_A forwards BYE to IMS_A 55A BYE IMS_A forwards BYE to UE_B 56A User B is informed that content sharing has ended 57A 200 OK UE_B sends 200 OK for BYE 58A 200 OK IMS_A forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 66 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 59A 200 OK IBCF_A forwards 200 OK response to IBCF_B 60A 200 OK IBCF_B forwards 200 OK response to IMS_B 61A 200 OK IMS_B forwards the 200 OK response to IBCF_B 62A 200 OK IBCF_B forwards 200 OK response to IBCF_A 63A 200 OK IBCF_A forwards 200 OK response to IMS_A 64A 200 OK IMS_A forwards the 200 OK response to UE_A 65A Content sharing terminates 66A OPTIONS UE_B sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_A 67A OPTIONS IMS_A forwards OPTIONS to IBCF_A 68A OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69A OPTIONS IBCF_B forwards OPTIONS to IMS_B 70A OPTIONS IMS_B forwards OPTIONS to IBCF_B 71A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 72A OPTIONS IBCF_A forwards OPTIONS to IMS_A 73A OPTIONS IMS_A forwards OPTIONS to UE_A 74A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 75A 200 OK IMS_A forwards 200 OK to IBCF_A 76A 200 OK IBCF_A forwards 200 OK to IBCF_B 77A 200 OK IBCF_B forwards 200 OK to IMS_B 78A 200 OK IMS_B forwards 200 OK to IBCF_B 79A 200 OK IBCF_B forwards 200 OK to IBCF_A 80A 200 OK IBCF_A forwards 200 OK to IMS_A 81A 200 OK IMS_A forwards 200 OK to UE_B 82A User A terminates voice call 47B User B ends content sharing 48B BYE UE_B releases the call with BYE 49B BYE IMS_A forwards BYE to IBCF_A 50B BYE IBCF_A forwards BYE to IBCF_B 51B BYE IBCF_B forwards BYE to IMS_B 52B BYE IMS_B forwards BYE to IBCF_B 53B BYE IBCF_B forwards BYE to IBCF_A 54B BYE IBCF_A forwards BYE to IMS_A 55B BYE IMS_A forwards BYE to UE_A 56B User A is informed that content sharing has ended 57B 200 OK UE_A sends 200 OK for BYE 58B 200 OK IMS_A forwards 200 OK response to IBCF_A 59B 200 OK IBCF_A forwards 200 OK response to IBCF_B 60B 200 OK IBCF_B forwards 200 OK response to IMS_B 61B 200 OK IMS_B forwards 200 OK response to IBCF_B 62B 200 OK IBCF_B forwards 200 OK response to IBCF_A 63B 200 OK IBCF_A forwards 200 OK response to IMS_A 64B 200 OK IMS_A forwards the 200 OK response to UE_B 65B Content sharing terminates 66B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_B 67B OPTIONS IMS_A forwards OPTIONS to IBCF_A 68B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69B OPTIONS IBCF_B forwards OPTIONS to IMS_B 70B OPTIONS IMS_B forwards OPTIONS to IBCF_B 71B OPTIONS IBCF_B forwards OPTIONS to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 67 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 72B OPTIONS IBCF_A forwards OPTIONS to IMS_A 73B OPTIONS IMS_A forwards OPTIONS to UE_B 74B 200 OK UE_B responds with 200 OK to IMS_A with updated capabilities 75B 200 OK IMS_A forwards 200 OK to IBCF_A 76B 200 OK IBCF_A forwards 200 OK to IBCF_B 77B 200 OK IBCF_B forwards 200 OK to IMS_B 78B 200 OK IMS_B forwards 200 OK to IBCF_B 79B 200 OK IBCF_B forwards 200 OK to IBCF_A 80B 200 OK IBCF_A forwards 200 OK to IMS_A 81B 200 OK IMS_A forwards 200 OK to UE_A 82B User B terminates voice call
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.4.5 File transfer service	Following there are the expected common call flow sequences for a standalone File transfer service. For all Use Cases it is assumed that UEs registered on the corresponding IMS networks and they have already performed capability discovery procedures. In particular, users subscribed to standalone File transfer service. NOTE: According to RCS-e specification [11] File Transfer is a standalone service. In the mean time sharing picture during a call from the ‘Media gallery’ of the user terminal or file transfer during 1-to-1 chat ultimately equals to File transfer service procedures from a call flow sequences point of view.
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.4.5.1 UC_RCS_9_I: SIP message flow for File transfer with CF_INT_AS	The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_INT_AS 1 User A initiates a file transfer to user B Step 1 2 User B is informed of incoming file and accepts the transfer Step 20 3 User A is informed that file transfer has been accepted by user B Step 30 4 File transfer starts Step 40 5 File transfer completed (size checked) Step 41 6 User B is informed that file transfer completed Step 51 7 User A is informed that file transfer completed Step 61 The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User A initiates a file transfer to user B 2 INVITE UE_A sends INVITE to IMS_A to establish a session with the SDP offer indicating all specific data for a MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 68 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 5 100 Trying AS/IM_A responds with a 100 Trying provisional response 6 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 7 100 Trying IMS_A responds with a 100 Trying provisional response 8 INVITE IMS_A forwards INVITE to IBCF_A 9 100 Trying IBCF_A responds with a 100 Trying provisional response 10 INVITE IBCF_A forwards INVITE to IBCF_B 11 100 Trying IBCF_B responds with a 100 Trying provisional response 12 INVITE IBCF_B forwards INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to AS/IM_B 15 100 Trying AS/IM_B responds with a 100 Trying provisional response 16 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 17 100 Trying IMS_B responds with a 100 Trying provisional response 18 INVITE IMS_B forwards INVITE to UE_B 19 100 Trying UE_B optionally responds with a 100 Trying provisional response 20 User B is informed of incoming file and accepts the transfer 21 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform A-side with specific data for a MSRP connection set up 22 200 OK IMS_B forwards 200 OK response to AS/IM_B 23 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 24 200 OK IMS_B forwards 200 OK response to IBCF_B 25 200 OK IBCF_B forwards 200 OK response to IBCF_A 26 200 OK IBCF_A forwards 200 OK response to IMS_A 27 200 OK IMS_A forwards 200 OK response to AS/IM_A 28 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 29 200 OK IMS_A forwards 200 OK response to UE_A 30 User A is informed that file transfer has been accepted by user B 31 ACK UE_A acknowledges the receipt of 200 OK for INVITE 32 ACK IMS_A forwards ACK to AS/IM_A 33 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 34 ACK IMS_A forwards ACK to IBCF_A 35 ACK IBCF_A forwards ACK to IBCF_B 36 ACK IBCF_B forwards ACK to IMS_B 37 ACK IMS_B forwards ACK to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 69 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 38 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 39 ACK IMS_B forwards ACK to UE_B 40 File transfer starts (see clause 5.3.3 Image data via MSRP and use 5.4.3 test description) 41 File transfer completed (size checked) 42 BYE UE_A releases the file transfer session with BYE 43 BYE IMS_A forwards BYE to AS/IM_A 44 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 45 BYE IMS_A forwards BYE to IBCF_A 46 BYE IBCF_A forwards BYE to IBCF_B 47 BYE IBCF_B forwards BYE to IMS_B 48 BYE IMS_B forwards BYE to AS/IM_B 49 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 50 BYE IMS_B forwards BYE to UE_B 51 User B is informed that file transfer completed 52 200 OK UE_B sends 200 OK for BYE 53 200 OK IMS_B forwards 200 OK response to AS/IM_B 54 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 55 200 OK IMS_B forwards 200 OK response to IBCF_B 56 200 OK IBCF_B forwards 200 OK response to IBCF_A 57 200 OK IBCF_A forwards 200 OK response to IMS_A 58 200 OK IMS_A forwards 200 OK response to AS/IM_A 59 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 60 200 OK IMS_A forwards 200 OK response to UE_A 61 User A is informed that file transfer completed 4.4.5.2 UC_RCS_9_R: SIP message flow for File transfer with CF_ROAM_AS (OPTIONAL) The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_ROAM_AS 1 User B initiates a file transfer to user A Step 1 2 User A is informed of incoming file and accepts the transfer Step 26 3 User B is informed that file transfer has been accepted by user A Step 39 4 File transfer starts Step 52 5 File transfer completed (size checked) Step 53 6 User A is informed that file transfer completed Step 66 7 User B is informed that file transfer completed Step 79 ETSI ETSI TS 102 901 V4.1.1 (2012-05) 70 The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User B initiates a file transfer to user A 2 INVITE UE_B sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to AS/IM_B 11 100 Trying AS/IM_B responds with a 100 Trying provisional response 12 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to IBCF_B 15 100 Trying IBCF_B responds with a 100 Trying provisional response 16 INVITE IBCF_B forwards INVITE to IBCF_A 17 100 Trying IBCF_A responds with a 100 Trying provisional response 18 INVITE IBCF_A forwards INVITE to IMS_A 19 100 Trying IMS_A responds with a 100 Trying provisional response 20 INVITE IMS_A forwards INVITE to AS/IM_A 21 100 Trying AS/IM_A responds with a 100 Trying provisional response 22 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 23 100 Trying IMS_A responds with a 100 Trying provisional response 24 INVITE IMS_A forwards INVITE to UE_A 25 100 Trying UE_A optionally responds with a 100 Trying provisional response 26 User A is informed of incoming file and accepts the transfer 27 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform B-side with specific data for a new MSRP connection set up 28 200 OK IMS_A forwards 200 OK response to AS/IM_A 29 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 30 200 OK IMS_A forwards 200 OK response to IBCF_A 31 200 OK IBCF_A forwards 200 OK response to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 71 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 32 200 OK IBCF_B forwards 200 OK response to IMS_B 33 200 OK IMS_B forwards 200 OK response to AS/IM_B 34 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 35 200 OK IMS_B forwards 200 OK response to IBCF_B 36 200 OK IBCF_B forwards 200 OK response to IBCF_A 37 200 OK IBCF_A forwards 200 OK response to IMS_A 38 200 OK IMS_A forwards 200 OK response to UE_B 39 User B is informed that file transfer has been accepted by user B 40 ACK UE_B acknowledges the receipt of 200 OK for INVITE 41 ACK IMS_A forwards ACK to IBCF_A 42 ACK IBCF_A forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IMS_B 44 ACK IMS_B forwards ACK to AS/IM_B 45 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 46 ACK IMS_B forwards ACK to IBCF_B 47 ACK IBCF_B forwards ACK to IBCF_A 48 ACK IBCF_A forwards ACK to IMS_A 49 ACK IMS_A forwards ACK to AS/IM_A 50 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 51 ACK IMS_A forwards ACK to UE_A 52 File transfer starts (see clause 5.3.3 Image data via MSRP and use 5.4.3 test description) 53 File transfer completed (size checked) 54 BYE UE_B releases the file transfer session with BYE 55 BYE IMS_A forwards BYE to IBCF_A 56 BYE IBCF_A forwards BYE to IBCF_B 57 BYE IBCF_B forwards BYE to IMS_B 58 BYE IMS_B forwards BYE to AS/IM_B 59 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 60 BYE IMS_B forwards BYE to IBCF_B 61 BYE IBCF_B forwards BYE to IBCF_A 62 BYE IBCF_A forwards BYE to IMS_A 63 BYE IMS_A forwards BYE to AS/IM_A 64 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 65 BYE IMS_A forwards BYE to UE_A 66 User A is informed that file transfer completed 67 200 OK UE_A sends 200 OK for BYE 68 200 OK IMS_A forwards 200 OK response to AS/IM_A 69 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 72 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 70 200 OK IMS_A forwards 200 OK response to IBCF_A 71 200 OK IBCF_A forwards 200 OK response to IBCF_B 72 200 OK IBCF_B forwards 200 OK response to IMS_B 73 200 OK IMS_B forwards 200 OK response to AS/IM_B 74 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 75 200 OK IMS_B forwards 200 OK response to IBCF_B 76 200 OK IBCF_B forwards 200 OK response to IBCF_A 77 200 OK IBCF_A forwards 200 OK response to IMS_A 78 200 OK IMS_A forwards 200 OK response to UE_B 79 User B is informed that file transfer completed
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5 Test Descriptions	This clause introduces interoperability test descriptions (TDs) which realize one or more IMS NNI test purposes of TS 186 011-1 [2]. Each TD is defined on the basis of one of the generic use cases forms presented in the previous clause and in TS 186 011-2 [9], clause 4.4. Each test sequence step in a TD includes also a reference to a specific call flow step of the generic use case. Call flow steps which are associated with the test body are repeated after each TD and include any modifications necessary to adapt the generic use case. In the adapted call flow steps that are associated with user interactions are shown shaded and steps which have pass criteria are associated with are shown in bold. Note that the expected test sequence may only show the Call Flow that affects the test. In the tabulations which follow, all references are to TS 124 229 [1].
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.1 Capability discovery
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.1.1 Capability discover through OPTIONS - User B is Registered - interworking	Interoperability Test Description Identifier: TD_IMS_CAP_0001 Summary: IMS network supports capability discovery and OPTIONS messages exchange between two users in their home network can be performed. User B must be Registered. Configuration: CF_INT_AS SUT IMS_B References Test Purpose Specification Reference TP_IMS_5097_13 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶65 Use Case ref.: UC_RCS_1_I ETSI ETSI TS 102 901 V4.1.1 (2012-05) 73 Interoperability Test Description Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding Test Sequence: Step 1 User A selects a contact of user B in the phone address book 2 User B is informed about user A capabilities 3 User A is informed about user B capabilities Conformance Criteria: Check 1 TP_IMS_5097_13 in CFW step 6 (PUBLISH): ensure that { when {IMS_B receives a PUBLISH from IMS_A } then { IMS_B sends the PUBLISH to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter and containing access-network-charging-info } } 2 TP_IMS_5108_07 in CFW step 18 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 3 TP_IMS_5115_08 in CFW step 19 (200 OK): ensure that { when { AS_B sends a 200 response to UE_A } then { IMS_B receives the 200 response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating IMS_A and containing a term-ioi_parameter indicating IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1 User A selects a contact of user B in the phone address book 2 OPTIONS UE_A sends OPTIONS to IMS_A with Accept- contact header containing user A capabilities (RCS-e services Tags) 3 OPTIONS IMS_A forwards OPTIONS to IBCF_A 4 OPTIONS IBCF_A forwards OPTIONS to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 74 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 5 OPTIONS IBCF_B forwards OPTIONS to IMS_B 6 OPTIONS IMS_B forwards OPTIONS to UE_B 7 User B is informed about user A capabilities 8 200 OK UE_B responds with 200 OK to IMS_B with Contact header containing user B capabilities (RCS-e services Tags) 9 200 OK IMS_B forwards 200 OK to IBCF_B 10 200 OK IBCF_B forwards 200 OK to IBCF_A 11 200 OK IBCF_A forwards 200 OK to IMS_A 12 200 OK IMS_A forwards 200 OK to UE_A 13 User A is informed about user B capabilities
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.1.2 Capability discover through OPTIONS - User B is Registered - roaming	Interoperability Test Description Identifier: TD_IMS_CAP_0002 Summary: IMS network supports capability discovery and OPTIONS messages exchange between one user in its home network and another in visited network can be performed. User B must be Registered. Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_B References Test Purpose Specification Reference TP_IMS_5097_13 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶65 Use Case ref.: UC_RCS_1_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding Test Sequence: Step 1 User A selects a contact of user B in the phone address book 2 User B is informed about user A capabilities 3 User A is informed about user B capabilities Conformance Criteria: Check 1 TP_IMS_5097_13 in CFW step 6 (PUBLISH): ensure that { when {IMS_B receives a PUBLISH from IMS_A } then { IMS_B sends the PUBLISH to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter and containing access-network-charging-info } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 75 Interoperability Test Description 2 TP_IMS_5108_07 in CFW step 18 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 3 TP_IMS_5115_08 in CFW step 19 (200 OK): ensure that { when { AS_B sends a 200 response to UE_A } then { IMS_B receives the 200 response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating IMS_A and containing a term-ioi_parameter indicating IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1 User A selects a contact of user B in the phone address book 2 OPTIONS UE_A sends OPTIONS to IMS_A with Accept- contact header containing user A capabilities (RCS-e services Tags) 3 OPTIONS IMS_A forwards OPTIONS to IBCF_A 4 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 5 OPTIONS IBCF_B forwards OPTIONS to IMS_B 6 OPTIONS IMS_B forwards OPTIONS to IBCF_B 7 OPTIONS IBCF_B forwards OPTIONS to IBCF_A 8 OPTIONS IBCF_A forwards OPTIONS to IMS_A 9 OPTIONS IMS_A forwards OPTIONS to UE_B 10 User B is informed about user A capabilities 11 200 OK UE_B responds with 200 OK to IMS_A with Contact header containing user B capabilities (RCS-e services Tags) 12 200 OK IMS_A forwards 200 OK to IBCF_A 13 200 OK IBCF_A forwards 200 OK to IBCF_B 14 200 OK IBCF_B forwards 200 OK to IMS_B 15 200 OK IMS_B forwards 200 OK to IBCF_B 16 200 OK IBCF_B forwards 200 OK to IBCF_A 17 200 OK IBCF_A forwards 200 OK to IMS_A 18 200 OK IMS_A forwards 200 OK to UE_A 19 User A is informed about user B capabilities ETSI ETSI TS 102 901 V4.1.1 (2012-05) 76 4.5.1.3 Capability discover through OPTIONS- User B is not Registered - interworking Interoperability Test Description Identifier: TD_IMS_CAP_0003 Summary: IMS network supports capability discovery and OPTIONS messages exchange between two users in their home network can be performed. User B must be not Registered. Configuration: CF_INT_AS SUT IMS_B References Test Purpose Specification Reference TP_IMS_5097_13 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶65 Use Case ref.: UC_RCS_1_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is not registered in IMS_B • UE_A is optionally configured to receive notifications with watcher information • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding Test Sequence: Step 1 User A selects a contact of user B in the phone address book 2 User A is informed that user B is offline (not registered) Conformance Criteria: Check 1 TP_IMS_5097_13 in CFW step 6 (PUBLISH): ensure that { when {IMS_B receives a PUBLISH from IMS_A } then { IMS_B sends the PUBLISH to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter and containing access-network-charging-info } } 2 TP_IMS_5108_07 in CFW step 18 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 3 TP_IMS_5115_08 in CFW step 19 (200 OK): ensure that { when { AS_B sends a 200 response to UE_A } then { IMS_B receives the 200 response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating IMS_A and containing a term-ioi_parameter indicating IMS_B } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 77 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1 User A selects a contact of user B in the phone address book 2 OPTIONS UE_A sends OPTIONS to IMS_A with Accept- contact header containing user A capabilities (RCS-e services Tags) 3 OPTIONS IMS_A forwards OPTIONS to IBCF_A 4 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 5 OPTIONS IBCF_B forwards OPTIONS to IMS_B 6 480 Not Registered/ 408 Request Timeout IMS_B responds OPTIONS with 480 Not Registered/408 Request Timeout to IBCF_B 7 480 Not Registered/ 408 Request Timeout IBCF_B forwards 480 Not Registered/408 Request Timeout response to IBCF_A 8 480 Not Registered/ 408 Request Timeout IBCF_A forwards 480 Not Registered/408 Request Timeout response to IMS_A 9 480 Not Registered/ 408 Request Timeout IMS_A forwards 480 Not Registered/408 Request Timeout response to UE_A 10 User A is informed that user B is offline (not registered) 4.5.1.4 Capability discover through OPTIONS - User B is not provisioned for RCS-e - interworking Interoperability Test Description Identifier: TD_IMS_CAP_0004 Summary: IMS network supports capability discovery and OPTIONS messages exchange between two users in their home network can be performed. User B must be not provisioned for RCS-e services. Configuration: CF_INT_AS SUT IMS_B References Test Purpose Specification Reference TP_IMS_5097_13 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶65 Use Case ref.: UC_RCS_1_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B without RCS-e capabilities • UE_A is optionally configured to receive notifications with watcher information • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding ETSI ETSI TS 102 901 V4.1.1 (2012-05) 78 Interoperability Test Description Test Sequence: Step 1 User A selects a contact of user B in the phone address book 2 User A is informed that user B is not provisioned for RCS-e Conformance Criteria: Check 1 TP_IMS_5097_13 in CFW step 6 (PUBLISH): ensure that { when {IMS_B receives a PUBLISH from IMS_A } then { IMS_B sends the PUBLISH to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter and containing access-network-charging-info } } 2 TP_IMS_5108_07 in CFW step 18 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 3 TP_IMS_5115_08 in CFW step 19 (200 OK): ensure that { when { AS_B sends a 200 response to UE_A } then { IMS_B receives the 200 response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating IMS_A and containing a term-ioi_parameter indicating IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1 User A selects a contact of user B in the phone address book 2 OPTIONS UE_A sends OPTIONS to IMS_A with Accept- contact header containing user A capabilities (RCS-e services Tags) 3 OPTIONS IMS_A forwards OPTIONS to IBCF_A 4 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 5 OPTIONS IBCF_B forwards OPTIONS to IMS_B 6 404 Not Found IMS_B responds OPTIONS with 404 Not Found to IBCF_B 7 404 Not Found IBCF_B forwards 404 Not Found response to IBCF_A 8 404 Not Found IBCF_A forwards 404 Not Found response to IMS_A 9 404 Not Found IMS_A forwards 404 Not Found response to UE_A 10 User A is informed that user B is not provisioned for RCS-e ETSI ETSI TS 102 901 V4.1.1 (2012-05) 79
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.2 Social Presence
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.2.1 Watcher subscription for presence event notification in visited network	Interoperability Test Description Identifier: TD_IMS_PRES_0001 Summary: IMS network supports properly presence service when a watcher subscribes to presence information for a presentity that it’s located in a different network. Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_B References Test Purpose Specification Reference TP_IMS_5097_13 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶65 Use Case ref.: UC_RCS_2_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding Test Sequence: Step 1 User B publishes presence and capability information 2 User B is informed of its presence status update 3 User A selects a contact of user B in the phone address book 4 User B is informed about user A capabilities 5 User A is informed about user B capabilities 6 User A subscribes to presence and capability information from User B 7 SUBSCRIPTION triggers the AS to send a NOTIFY to UE_B indicating the change to the watcher information subscriber 8 User B receives an authorization request from User A to see its own presence and capability information 9 User B authorizes user A to be informed of its own presence and capability information 10 User A is informed of user B presence and capability information 11 User A sees user B presence and capability information Conformance Criteria: Check 1 TP_IMS_5097_13 in CFW step 6 (PUBLISH): ensure that { when {IMS_B receives a PUBLISH from IMS_A } then { IMS_B sends the PUBLISH to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter and containing access-network-charging-info } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 80 Interoperability Test Description 2 TP_IMS_5108_07 in CFW step 18 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 3 TP_IMS_5115_08 in CFW step 19 (200 OK): ensure that { when { AS_B sends a 200 response to UE_A } then { IMS_B receives the 200 response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating IMS_A and containing a term-ioi_parameter indicating IMS_B } } Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence elements 3 PUBLISH IMS_A forwards the PUBLISH to IBCF_A 4 PUBLISH IBCF_A forwards the PUBLISH to IBCF_B 5 PUBLISH IBCF_B forwards the PUBLISH to IMS_B 6 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 7 200 OK IMS_B AS responds with a 200 OK to IMS_B 8 200 OK IMS_B forwards the 200 OK response to IBCF_B 9 200 OK IBCF_B forwards the 200 OK response to IBCF_A 10 200 OK IBCF_A forwards the 200 OK response to IMS_A 11 200 OK IMS_A forwards the 200 OK response to UE_B 12 User B is informed of its presence status update 13 User A selects a contact of user B in the phone address book 14 OPTIONS UE_A sends OPTIONS to IMS_A with Accept-contact header containing user A capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 15 OPTIONS IMS_A forwards OPTIONS to IBCF_A 16 OPTIONS IBCF_A forwards OPTIONS to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 81 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 17 OPTIONS IBCF_B forwards OPTIONS to IMS_B 18 OPTIONS IMS_B forwards OPTIONS to IBCF_B 19 OPTIONS IBCF_B forwards OPTIONS to IBCF_A 20 OPTIONS IBCF_A forwards OPTIONS to IMS_A 21 OPTIONS IMS_A forwards OPTIONS to UE_B 22 User B is informed about user A capabilities 23 200 OK UE_B responds with 200 OK to IMS_A with Contact header containing user B capabilities (RCS-e services Tags and the Tag indicating support via presence) 24 200 OK IMS_A forwards 200 OK to IBCF_A 25 200 OK IBCF_A forwards 200 OK to IBCF_B 26 200 OK IBCF_B forwards 200 OK to IMS_B 27 200 OK IMS_B forwards 200 OK to IBCF_B 28 200 OK IBCF_B forwards 200 OK to IBCF_A 29 200 OK IBCF_A forwards 200 OK to IMS_A 30 200 OK IMS_A forwards 200 OK to UE_A 31 User A is informed about user B capabilities 32 User A subscribes to presence and capability information from User B 33 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "User B presence" event with expiry time of 0 to IMS_A 34 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 35 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 36 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 37 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 38 200 OK IMS_B AS responds with a 200 OK to IMS_B 39 200 OK IMS_B forwards the 200 OK response to IBCF_B 40 200 OK IBCF_B forwards the 200 OK response to IBCF_A 41 200 OK IBCF_A forwards the 200 OK response to IMS_A 42 200 OK IMS_A forwards the 200 OK response to UE_A 43 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 44 NOTIFY IBCF_B forwards NOTIFY to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 82 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 45 NOTIFY IBCF_A forwards NOTIFY to IMS_A 46 NOTIFY IMS_A forwards the NOTIFY to UE_A 47 200 OK UE_A responds with a 200 OK to IMS_A 48 200 OK IMS_A forwards the 200 OK to IBCF_A 49 200 OK IBCF_A forwards the 200 OK to IBCF_B 50 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 51 SUBSCRIPTION triggers the AS to send a NOTIFY to UE_B indicating the change to the watcher information subscriber 52 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B the change to the watcher information subscriber 53 NOTIFY IMS_B forwards the NOTIFY to IBCF_B 54 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 55 NOTIFY IBCF_A forwards the NOTIFY to IMS_A 56 NOTIFY IMS_A forwards the NOTIFY to UE_B 57 200 OK UE_B responds with a 200 OK to IMS_A 58 200 OK IMS_A forwards the 200 OK response to IBCF_A 59 200 OK IBCF_A forwards the 200 OK response to IBCF_B 60 IBCF_B forwards the 200 OK response to IMS_B 61 200 OK IMS_B forwards the 200 OK response to IMS_B AS 62 User B receives an authorization request from User A to see its own presence and capability information 63 User B authorizes user A to be informed of its own presence and capability information 64 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 65 NOTIFY IBCF_B sends NOTIFY to IBCF_A 66 NOTIFY IBCF_A forwards NOTIFY to IMS_A 67 NOTIFY IMS_A forwards the NOTIFY to UE_A 68 200 OK UE_A responds with a 200 OK to IMS_A 69 200 OK IMS_A forwards the 200 OK response to IBCF_A 70 200 OK IBCF_A forwards the 200 OK response to IBCF_B 71 200 OK IBCF_B forwards the 200 OK response to IMS_B AS ETSI ETSI TS 102 901 V4.1.1 (2012-05) 83 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 72 User A is informed of user B presence and capability information 73 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B that subscription has been authorized 74 NOTIFY IMS_B forwards the NOTIFY to IBCF_B 75 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 76 NOTIFY IBCF_A forwards the NOTIFY to IMS_A 77 NOTIFY IMS_A forwards the NOTIFY to UE_B 78 200 OK UE_B responds with a 200 OK to IMS_A 79 200 OK IMS_A forwards the 200 OK response to IBCF_A 80 200 OK IBCF_A forwards the 200 OK response to IBCF_B 81 200 OK IBCF_B forwards the 200 OK response to IMS_B 82 200 OK IMS_B forwards the 200 OK response to IMS_B AS 83 User A sees user B presence and capability information
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.2.2 Watcher subscription to presence event notification in home network	Interoperability Test Description Identifier: TD_IMS_PRES_0002 Summary: IMS network supports properly presence service when a watcher subscribes to presence information for a presentity that it’s located in a home network. Configuration: CF_INT_AS SUT IMS_A References Test Purpose Specification Reference TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶65 Use Case ref.: UC_RCS_2_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding ETSI ETSI TS 102 901 V4.1.1 (2012-05) 84 Interoperability Test Description Test Sequence: Step 1 User B publishes presence and capability information including capabilities 2 User B is informed of its presence status update 3 User A selects a contact of user B in the phone address book 4 User B is informed about user A capabilities 5 User A is informed about user B capabilities 6 User A subscribes to presence and capability information from User B 7 SUBSCRIPTION triggers the AS to send a NOTIFY to UE_B indicating the change to the watcher information subscriber 8 User B receives an authorization request from User A to see its own presence and capability information 9 User B authorizes user A to be informed of its own presence and capability information 10 User A is informed of user B presence and capability information 11 User A sees user B presence and capability information Conformance Criteria: Check 1 TP_IMS_5108_07 in CFW step 12 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 2 TP_IMS_5115_08 in CFW step 13 (200 OK): ensure that { when { AS_B sends a 200 response to UE_A } then { IMS_B receives the 200 response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating IMS_A and containing a term-ioi_parameter indicating IMS_B } } Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information including capabilities 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence elements and capabilities 3 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 4 200 OK IMS_B AS responds with a 200 OK to IMS_B 5 200 OK IMS_B forwards the 200 OK response to IBCF_B 6 User B is informed of its presence status update 7 User A selects a contact of user B in the phone address book ETSI ETSI TS 102 901 V4.1.1 (2012-05) 85 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 8 OPTIONS UE_A sends OPTIONS to IMS_A with Accept-contact header containing user A capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 9 OPTIONS IMS_A forwards OPTIONS to IBCF_A 10 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 11 OPTIONS IBCF_B forwards OPTIONS to IMS_B 12 OPTIONS IMS_B forwards OPTIONS to UE_B 13 User B is informed about user A capabilities 14 200 OK UE_B responds with 200 OK to IMS_B with Contact header containing user B capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 15 200 OK IMS_B forwards 200 OK to IBCF_B 16 200 OK IBCF_B forwards 200 OK to IBCF_A 17 200 OK IBCF_A forwards 200 OK to IMS_A 18 200 OK IMS_A forwards 200 OK to UE_A 19 User A is informed about user B capabilities 20 User A subscribes to presence and capability information from User B 21 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "User B presence" event with expiry time of 0 to IMS_A 22 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 23 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 24 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 25 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 26 200 OK IMS_B AS responds with a 200 OK to IMS_B 27 200 OK IMS_B forwards the 200 OK response to IBCF_B 28 200 OK IBCF_B forwards the 200 OK response to IBCF_A 29 200 OK IBCF_A forwards the 200 OK response to IMS_A 30 200 OK IMS_A forwards the 200 OK response to UE_A 31 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 32 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 33 NOTIFY IBCF_A forwards NOTIFY to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 86 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 34 NOTIFY IMS_A forwards the NOTIFY to UE_A 35 200 OK UE_A responds with a 200 OK to IMS_A 36 200 OK IMS_A forwards the 200 OK to IBCF_A 37 200 OK IBCF_A forwards the 200 OK to IBCF_B 38 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 39 SUBSCRIPTION triggers the AS to send a NOTIFY to UE_B indicating the change to the watcher information subscriber 40 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B the change to the watcher information subscriber 41 NOTIFY IMS_B forwards the NOTIFY to UE_B 42 200 OK UE_B responds with a 200 OK to IMS_B 43 200 OK IMS_B forwards the 200 OK response to IMS_B AS 44 User B receives an authorization request from User A to see its own presence and capability information 45 User B authorizes user A to be informed of its own presence and capability information 46 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 47 NOTIFY IBCF_B sends NOTIFY to IBCF_A 48 NOTIFY IBCF_A forwards NOTIFY to IMS_A 49 NOTIFY IMS_A forwards the NOTIFY to UE_A 50 200 OK UE_A responds with a 200 OK to IMS_A 51 200 OK IMS_A forwards the 200 OK response to IBCF_A 52 200 OK IBCF_A forwards the 200 OK response to IBCF_B 53 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 54 User A is informed of user B presence and capability information 55 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B that subscription has been authorized 56 NOTIFY IMS_B forwards the NOTIFY to UE_B 57 200 OK UE_B responds with a 200 OK to IMS_B 58 200 OK IMS_B forwards the 200 OK response to IMS_B AS 59 User A sees user B presence and capability information ETSI ETSI TS 102 901 V4.1.1 (2012-05) 87 4.5.2.3 Unsuccessful watcher subscription to presence event notification in home network Interoperability Test Description Identifier: TD_IMS_PRES_0003 Summary: IMS network supports properly presence service when a watcher subscribes to presence information for a presentity that it’s located in a different network and does not authorize the watcher to be informed of his presence information. Configuration: CF_INT_AS SUT IMS_B References Test Purpose Specification Reference TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 Use Case ref.: UC_RCS_2_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • User A is not authorized to see presence information of User B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding Test Sequence: Step 1 User B publishes presence and capability information including capabilities 2 User B is informed of its presence status update 3 User A selects a contact of user B in the phone address book 4 User B is informed about user A capabilities 5 User A is informed about user B capabilities 6 User A subscribes to presence and capability information from User B 7 User A is not informed of user B presence information Conformance Criteria: Check 1 TP_IMS_5108_07 in CFW step 6 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 88 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information including capabilities 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence elements and capabilities 3 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 4 200 OK IMS_B AS responds with a 200 OK to IMS_B 5 200 OK IMS_B forwards the 200 OK response to IBCF_B 6 User B is informed of its presence status update 7 User A selects a contact of user B in the phone address book 8 OPTIONS UE_A sends OPTIONS to IMS_A with Accept-contact header containing user A capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 9 OPTIONS IMS_A forwards OPTIONS to IBCF_A 10 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 11 OPTIONS IBCF_B forwards OPTIONS to IMS_B 12 OPTIONS IMS_B forwards OPTIONS to UE_B 13 User B is informed about user A capabilities 14 200 OK UE_B responds with 200 OK to IMS_B with Contact header containing user B capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 15 200 OK IMS_B forwards 200 OK to IBCF_B 16 200 OK IBCF_B forwards 200 OK to IBCF_A 17 200 OK IBCF_A forwards 200 OK to IMS_A 18 200 OK IMS_A forwards 200 OK to UE_A 19 User A is informed about user B capabilities 20 User A subscribes to presence and capability information from User B 21 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "User B presence" event with expiry time of 0 to IMS_A 22 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 23 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 24 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 89 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 25 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 26 2xx or 4xx response IMS_B AS responds with a 2xx or 4xx response to IMS_B 27 2xx or 4xx response IMS_B forwards the 2xx or 4xx response to IBCF_B 28 2xx or 4xx response IBCF_B forwards the 2xx or 4xx response to IBCF_A 29 2xx or 4xx response IBCF_A forwards the 2xx or 4xx response to IMS_A 30 2xx or 4xx response IMS_A forwards the 2xx or 4xx response to UE_A 31 User A is not informed of user B presence information Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information including capabilities 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence elements and capabilities 3 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 4 200 OK IMS_B AS responds with a 200 OK to IMS_B 5 200 OK IMS_B forwards the 200 OK response to IBCF_B 6 User B is informed of its presence status update 7 User A selects a contact of user B in the phone address book 8 OPTIONS UE_A sends OPTIONS to IMS_A with Accept-contact header containing user A capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 9 OPTIONS IMS_A forwards OPTIONS to IBCF_A 10 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 11 OPTIONS IBCF_B forwards OPTIONS to IMS_B 12 OPTIONS IMS_B forwards OPTIONS to UE_B 13 User B is informed about user A capabilities 14 200 OK UE_B responds with 200 OK to IMS_B with Contact header containing user B capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) ETSI ETSI TS 102 901 V4.1.1 (2012-05) 90 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 15 200 OK IMS_B forwards 200 OK to IBCF_B 16 200 OK IBCF_B forwards 200 OK to IBCF_A 17 200 OK IBCF_A forwards 200 OK to IMS_A 18 200 OK IMS_A forwards 200 OK to UE_A 19 User A is informed about user B capabilities 20 User A subscribes to presence and capability information from User B 21 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "User B presence" event with expiry time of 0 to IMS_A 22 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 23 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 24 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 25 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 26 2xx or 4xx response IMS_B AS responds with a 2xx or 4xx response to IMS_B 27 2xx or 4xx response IMS_B forwards the 2xx or 4xx response to IBCF_B 28 2xx or 4xx response IBCF_B forwards the 2xx or 4xx response to IBCF_A 29 2xx or 4xx response IBCF_A forwards the 2xx or 4xx response to IMS_A 30 2xx or 4xx response IMS_A forwards the 2xx or 4xx response to UE_A 31 User A is not informed of user B presence information
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.2.4 Watcher subscription to resource list in visited network	Interoperability Test Description Identifier: TD_IMS_PRES_0004 Summary: IMS network supports properly presence service when a watcher subscribes to a resource list containing one or more presentities located in different networks. Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_B References Test Purpose Specification Reference TP_IMS_5097_13 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5313_01 TS 124 229 [1], clause 5.4.6.1.3 ¶2 Use Case ref.: UC_RCS_3_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 91 Interoperability Test Description • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding • UE_A is authorized to use the resource list userPRES_list Test Sequence: Step 1 User B publishes presence and capability information 2 User B is informed of its presence status update 3 User A subscribes to resource list previously stored in the User A client as XDMS list of contacts 4 RLS performs authorization checks to ensure that User A is authorized to use resource lists 5 RLS resolves watcher resource´s address and subscribes for presence event notification for all the presentities represented by the resource list SIP URI 6 PS performs authorization checks on the originator to ensure it is allowed to watch the presentity 7 RLS notifies with presence and capability information for all the presentities represented by the resource list SIP URI 8 User A sees user B presence and capability information Conformance Criteria: Check 1 TP_IMS_5097_13 in CFW step 6 (PUBLISH): ensure that { when {IMS_B receives a PUBLISH from IMS_A } then { IMS_B sends the PUBLISH to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter and containing access-network-charging-info} } 2 TP_IMS_5108_07 in CFW step 28 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 3 TP_IMS_5313_01 in CFW step 34 (200 OK) ensure that { when { IMS_A receives a response from IMS_B containing a P-Charging-Vector_header including an access-network-charging-info_parameter } then { IMS_A sends the response to AS_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter }} ETSI ETSI TS 102 901 V4.1.1 (2012-05) 92 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence and capability elements 3 PUBLISH IMS_A forwards the PUBLISH to IBCF_A 4 PUBLISH IBCF_A forwards the PUBLISH to IBCF_B 5 PUBLISH IBCF_B forwards the PUBLISH to IMS_B 6 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 7 200 OK IMS_B AS responds with a 200 OK to IMS_B 8 200 OK IMS_B forwards the 200 OK response to IBCF_B 9 200 OK IBCF_B forwards the 200 OK response to IBCF_A 10 200 OK IBCF_A forwards the 200 OK response to IMS_A 11 200 OK IMS_A forwards the 200 OK response to UE_B 12 User B is informed of its presence status update 13 User A subscribes to resource list previously stored in the User A client as XDMS list of contacts 14 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "presence" event with expiry time of 0 to IMS_A indicating support to "eventlist" to a resource list SIP URI 15 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IMS_A AS (RLS) 16 RLS performs authorization checks to ensure that User A is authorized to use resource lists 17 200 OK IMS_A AS responds with a 200 OK to IMS_A 18 200 OK IMS_A forwards the 200 OK response to UE_A 19 NOTIFY IMS_A AS sends NOTIFY to IMS_A 20 NOTIFY IMS_A forwards the NOTIFY to UE_A 21 200 OK UE_A responds with a 200 OK to IMS_A 22 200 OK IMS_A forwards the 200 OK response to IMS_A AS 23 RLS resolves watcher resource´s address and subscribes for presence event notification for all the presentities represented by the resource list SIP URI 24 SUBSCRIBE IMS_A AS (RLS) sends SUBSCRIBE for "presence" event to IMS_A 25 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 93 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 26 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 27 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 28 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 29 PS performs authorization checks on the originator to ensure it is allowed to watch the presentity 30 200 OK IMS_B AS (PS) responds with a 200 OK to IMS_B 31 200 OK IMS_B forwards the 200 OK response to IBCF_B 32 200 OK IBCF_B forwards the 200 OK response to IBCF_A 33 200 OK IBCF_A forwards the 200 OK response to IMS_A 34 200 OK IMS_A forwards the 200 OK response to IMS_A AS (RLS) 35 NOTIFY IMS_B AS sends a NOTIFY to IBCF_B with the presence and capability information of UE_B 36 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 37 IBCF_A forwards the NOTIFY to IMS_A 38 NOTIFY IMS_A forwards the NOTIFY to IMS_A AS (RLS) 39 200 OK IMS_A AS responds with a 200 OK to IMS_A 40 200 OK IMS_A forwards the 200 OK response to IBCF_A 41 200 OK IBCF_A forwards the 200 OK response to IBCF_B 42 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 43 RLS notifies with presence and capability information for all the presentities represented by the resource list SIP URI 44 NOTIFY IMS_A AS sends NOTIFY to IMS_A 45 NOTIFY IMS_A forwards the NOTIFY to UE_A 46 200 OK UE_A responds with a 200 OK to IMS_A 47 200 OK IMS_A forwards the 200 OK response to IMS_A AS 48 User A sees user B presence and capability information
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.2.5 Watcher subscription to resource list in home network	Interoperability Test Description Identifier: TD_IMS_PRES_0005 Summary: IMS network supports properly presence service when a watcher subscribes to a resource list containing one or more presentities located in different networks. Configuration: CF_INT_AS SUT IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 94 Interoperability Test Description References Test Purpose Specification Reference TP_IMS_5108_07 TS 124 229 [1], clause 5.4.3.3 ¶1 TP_IMS_5313_01 TS 124 229 [1], clause 5.4.6.1.3 ¶2 Use Case ref.: UC_RCS_3_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • IMS_A not configured for topology hiding • UE_A is authorized to use the resource list userPRES_list Test Sequence: Step 1 User B publishes presence and capability information 2 User B is informed of its presence status update 3 User A subscribes to resource list previously stored in the User A client as XDMS list of contacts 4 RLS performs authorization checks to ensure that User A is authorized to use resource lists 5 RLS resolves watcher resource´s address and subscribes for presence event notification for all the presentities represented by the resource list SIP URI 6 PS performs authorization checks on the originator to ensure it is allowed to watch the presentity 7 RLS notifies with presence and capability information for all the presentities represented by the resource list SIP URI 8 User A sees user B presence and capability information Conformance Criteria: Check 1 TP_IMS_5108_07 in CFW step 22 (SUBSCRIBE): ensure that { when { IMS_A receives a SUBSCRIBE addressed to UE_B } then { IMS_B sends the SUBSCRIBE to AS_B containing a topmost Route header indicating the SIP URI of AS_B containing a Route header indicating the S-CSCF_SIP URI of IMS_B containing a P-Charging-Vector_header containing an orig-ioi parameter indicating IMS_A and not containing a term-ioi parameter} } } 2 TP_IMS_5313_01 in CFW step 28 (200 OK) ensure that { when { IMS_A receives a response from IMS_B containing a P-Charging-Vector_header including an access-network-charging-info_parameter } then { IMS_A sends the response to AS_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 95 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence and capability elements 3 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 4 200 OK IMS_B AS responds with a 200 OK to IMS_B 5 200 OK IMS_B forwards the 200 OK response to UE_B 6 User B is informed of its presence status update 7 User A subscribes to resource list previously stored in the User A client as XDMS list of contacts 8 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "presence" event with expiry time of 0 to IMS_A indicating support to "eventlist" to a resource list SIP URI 9 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IMS_A AS (RLS) 10 RLS performs authorization checks to ensure that User A is authorized to use resource lists 11 200 OK IMS_A AS responds with a 200 OK to IMS_A 12 200 OK IMS_A forwards the 200 OK response to UE_A 13 NOTIFY IMS_A AS sends NOTIFY to IMS_A 14 NOTIFY IMS_A forwards the NOTIFY to UE_A 15 200 OK UE_A responds with a 200 OK to IMS_A 16 200 OK IMS_A forwards the 200 OK response to IMS_A AS 17 RLS resolves watcher resource´s address and subscribes for presence event notification for all the presentities represented by the resource list SIP URI 18 SUBSCRIBE IMS_A AS (RLS) sends SUBSCRIBE for "presence" event to IMS_A 19 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 20 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 21 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 22 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 23 PS performs authorization checks on the originator to ensure it is allowed to watch the presentity 24 200 OK IMS_B AS (PS) responds with a 200 OK to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 96 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 25 200 OK IMS_B forwards the 200 OK response to IBCF_B 26 200 OK IBCF_B forwards the 200 OK response to IBCF_A 27 200 OK IBCF_A forwards the 200 OK response to IMS_A 28 200 OK IMS_A forwards the 200 OK response to IMS_A AS (RLS) 29 NOTIFY IMS_B AS sends a NOTIFY to IBCF_B with the presence and capability information of UE_B 30 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 31 IBCF_A forwards the NOTIFY to IMS_A 32 NOTIFY IMS_A forwards the NOTIFY to IMS_A AS (RLS) 33 200 OK IMS_A AS responds with a 200 OK to IMS_A 34 200 OK IMS_A forwards the 200 OK response to IBCF_A 35 200 OK IBCF_A forwards the 200 OK response to IBCF_B 36 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 37 RLS notifies with presence and capability information for all the presentities represented by the resource list SIP URI 38 NOTIFY IMS_A AS sends NOTIFY to IMS_A 39 NOTIFY IMS_A forwards the NOTIFY to UE_A 40 200 OK UE_A responds with a 200 OK to IMS_A 41 200 OK IMS_A forwards the 200 OK response to IMS_A AS 42 User A sees user B presence and capability information
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3 IM/Chat service
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.1 1-to-1 chat standard procedure
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.1.1 1-to-1 chat standard procedure - interworking	Interoperability Test Description Identifier: TD_IMS_CHAT_0001 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users in their home network can be performed. Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (1st numbered list) ETSI ETSI TS 102 901 V4.1.1 (2012-05) 97 Interoperability Test Description TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶89 (4th numbered list) TD_MSRP_CHAT_0001 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 Use Case ref.: UC_RCS_4_I & UC_MSRP_01 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A and UE_B shall support MSRP • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A selects User B in the phone address book and sends him an initial message with MSRP indication 2 User B is informed of incoming message 3 User A is informed that initial message was delivered to user B 4 User B reads the initial message from user A and opens the 1-to-1 chat 5 Users perform chatting (MSRP session) 6A User A closes the 1-to-1 chat 6B User B closes the 1-to-1 chat 7A User A is informed that 1-to-1 chat with user B is closed 7B User B is informed that 1-to-1 chat with user A is closed Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 10 (INVITE): ensure that { when { UE_A sends an initial INVITE to UE_B } then { IMS_B receives the initial INVITE not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A containing a P-Charging-Vector_header (containing an icid-value_parameter and containing a orig-ioi_parameter indicating IMS_A and not containing an access-network-charging-info_parameter and not containing a term-ioi_parameter) and containing a Record-Route_header indicating the originating S-CSCF_SIP_URI } } 2 TP_IMS_5108_03 in CFW step 14 (INVITE) ensure that { when {IMS_B receives an initial INVITE from IMS_A addressed_to UE_B} then {IMS_B sends the INVITE to AS_B containing a topmost Route_header indicating the SIP_URI of AS_B and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 98 Interoperability Test Description 3 TP_IMS_5115_08 in CFW step 35 (200 OK) ensure that { when { IMS_B receives 200_response from AS_B addressed to UE_A } then { IMS_B sends the 200_response to IMS_A containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and including a term-ioi_parameter indicating operator_identifier of IMS_B } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User A selects User B in the phone address book and sends him an initial message 2 INVITE UE_A sends INVITE to IMS_A with user A initial message in the Subject header, CPIM/IMND headers and the first SDP offer indicating all specific data for MSRP connection set up (CheckMSRP1) 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to AS/IM_A 5 100 Trying AS/IM_A responds with a 100 Trying provisional response 6 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 7 100 Trying IMS_A responds with a 100 Trying provisional response 8 INVITE IMS_A forwards INVITE to IBCF_A 9 100 Trying IBCF_A responds with a 100 Trying provisional response 10 INVITE IBCF_A forwards INVITE to IBCF_B 11 100 Trying IBCF_B responds with a 100 Trying provisional response 12 INVITE IBCF_B forwards INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to AS/IM_B 15 100 Trying AS/IM_B responds with a 100 Trying provisional response 16 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 17 100 Trying IMS_B responds with a 100 Trying provisional response 18 INVITE IMS_B forwards INVITE to UE_B 19 100 Trying UE_B optionally responds with a 100 Trying provisional response 20 User B is informed of incoming message 21 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that invitation to a 1-to-1 chat session has reached the invited user 22 180 Ringing IMS_B forwards 180 Ringing response to AS/IM_B 23 180 Ringing AS/IM_B returns, possibly modified, 180 Ringing response to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 99 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 24 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 27 180 Ringing IMS_A forwards 180 Ringing response to AS/IM_A 28 180 Ringing AS/IM_A returns, possibly modified, 180 Ringing response to IMS_A 29 180 Ringing IMS_A forwards 180 Ringing response to UE_A 30 MESSAGE UE_B sends MESSAGE to IMS_B with delivery notification of initial message from user A 31 MESSAGE IMS_B forwards MESSAGE to AS/IM_B 32 MESSAGE AS/IM_B returns, possibly modified, MESSAGE to IMS_B 33 MESSAGE IMS_B forwards MESSAGE to IBCF_B 34 MESSAGE IBCF_B forwards MESSAGE to IBCF_A 35 MESSAGE IBCF_A forwards MESSAGE to IMS_A 36 MESSAGE IMS_A forwards MESSAGE to AS/IM_A 37 MESSAGE AS/IM_A returns, possibly modified, MESSAGE to IMS_A 38 MESSAGE IMS_A forwards MESSAGE to UE_A 39 User A is informed that initial message was delivered to user B 40 200 OK UE_A responds MESSAGE with 200 OK response 41 200 OK IMS_A forwards 200 OK response to AS/IM_A 42 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 43 200 OK IMS_A forwards 200 OK response to IBCF_A 44 200 OK IBCF_A forwards 200 OK response to IBCF_B 45 200 OK IBCF_B forwards 200 OK response to IMS_B 46 200 OK IMS_B forwards 200 OK response to AS/IM_B 47 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 48 200 OK IMS_B forwards 200 OK response to UE_B 49 User B reads the initial message from user A and opens the 1-to-1 chat 50 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform A-side with specific data for MSRP connection set up 51 200 OK IMS_B forwards 200 OK response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 100 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 52 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 53 200 OK IMS_B forwards 200 OK response to IBCF_B 54 200 OK IBCF_B forwards 200 OK response to IBCF_A 55 200 OK IBCF_A forwards 200 OK response to IMS_A 56 200 OK IMS_A forwards 200 OK response to AS/IM_A 57 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 58 200 OK IMS_A forwards 200 OK response to UE_A (CheckMSRP2) 59 ACK UE_A acknowledges the receipt of 200 OK for INVITE 60 ACK IMS_A forwards ACK to AS/IM_A 61 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 62 ACK IMS_A forwards ACK to IBCF_A 63 ACK IBCF_A forwards ACK to IBCF_B 64 ACK IBCF_B forwards ACK to IMS_B 65 ACK IMS_B forwards ACK to AS/IM_B 66 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 67 ACK IMS_B forwards ACK to UE_B 68 Users perform chatting (see clause 5.3.1 Chat 1 to 1 via MSRP and use 5.4.1 test description) - CheckMSRP2 69A User A closes the 1-to-1 chat 70A BYE UE_A releases the 1-to-1 chat session with BYE 71A BYE IMS_A forwards BYE to AS/IM_A 72A BYE AS/IM_A returns, possibly modified, BYE to IMS_A 73A BYE IMS_A forwards BYE to IBCF_A 74A BYE IBCF_A forwards BYE to IBCF_B 75A BYE IBCF_B forwards BYE to IMS_B 76A BYE IMS_B forwards BYE to AS/IM_B 77A BYE AS/IM_B returns, possibly modified, BYE to IMS_B 78A BYE IMS_B forwards BYE to UE_B 79A 200 OK UE_B sends 200 OK for BYE 80A 200 OK IMS_B forwards 200 OK response to AS/IM_B 81A 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 82A 200 OK IMS_B forwards 200 OK response to IBCF_B 83A 200 OK IBCF_B forwards 200 OK response to IBCF_A 84A 200 OK IBCF_A forwards 200 OK response to IMS_A 85A 200 OK IMS_A forwards 200 OK response to AS/IM_A 86A 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 101 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 87A 200 OK IMS_A forwards 200 OK response to UE_A 88A User A is informed that 1-to-1 chat with user B is closed 69B User B close the 1-to-1 chat 70B BYE UE_B releases the 1-to-1 chat session with BYE 71B BYE IMS_B forwards BYE to AS/IM_B 72B BYE AS/IM_B returns, possibly modified, BYE to IMS_B 73B BYE IMS_B forwards BYE to IBCF_B 74B BYE IBCF_B forwards BYE to IBCF_A 75B BYE IBCF_A forwards BYE to IMS_A 76B BYE IMS_A forwards BYE to AS/IM_A 77B BYE AS/IM_A returns, possibly modified, BYE to IMS_A 78B BYE IMS_A forwards BYE to UE_A 79B 200 OK UE_A sends 200 OK for BYE 80B 200 OK IMS_A forwards 200 OK response to AS/IM_A 81B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 82B 200 OK IMS_A forwards 200 OK response to IBCF_A 83B 200 OK IBCF_A forwards 200 OK response to IBCF_B 84B 200 OK IBCF_B forwards 200 OK response to IMS_B 85B 200 OK IMS_B forwards 200 OK response to AS/IM_B 86B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 87B 200 OK IMS_B forwards 200 OK response to UE_B 88B User B is informed that that 1-to-1 chat with user A is closed
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.1.2 1-to-1 chat standard procedure - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_CHAT_0002 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users, one user in its home network and one user roaming can be performed. Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ¶1 (1st numbered list) TP_IMS_5067_01 TS 124 229 [1], clause 5.2.7.2 ¶5 TP_IMS_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) TD_MSRP_CHAT_0001 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 Use Case ref.: UC_RCS_4_R & UC_MSRP_01 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as ETSI ETSI TS 102 901 V4.1.1 (2012-05) 102 Interoperability Test Description per TS 186 011-2 [9], clause 4.2.1 • UE_A and UE_B shall support MSRP • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B selects User A in the phone address book and sends him an initial message with MSRP indication 2 User A is informed of incoming message 3 User B is informed that initial message was delivered to user A 4 User A reads the initial message from user B and opens the 1-to-1 chat 5 Users perform chatting (MSRP session) 6A User B closes the 1-to-1 chat 6B User A closes the 1-to-1 chat 7A User B is informed that that 1-to-1 chat with user A is closed 7B User A is informed that that 1-to-1 chat with user B is closed Conformance Criteria: Check 1 TP_IMS_5046_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a Route_header not indicating the P-CSCF_SIP_URI of IMS_A and containing a Route_header indicating the "list of Service Route header URIs from the registration" and containing an additional Via_header containing ( the P-CSCF_via_port_number and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and containing an additional topmost Record-Route_header indicating (the P-CSCF_port_number 'where it awaits subsequent requests' from UE_A and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and not containing P-Preferred-Identity_header and containing a P-Asserted-Identity_header containing an address of UE_B and containing a P-Charging-Vector_header containing an icid-value_parameter } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 103 Interoperability Test Description 2 TP_IMS_5067_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a P-Charging-Vector_header } } 3 TP_IMS_5097_09 in CFW step 10 (INVITE) ensure that { when { IMS_B receives an initial INVITE from IMS_A addressed to UE_A } then { IMS_B sends the initial INVITE to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header (including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter and including access-network-charging-info) } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User B selects User A in the phone address book and sends him an initial message 2 INVITE UE_B sends INVITE to IMS_A with user B initial message in the Subject header, CPIM/IMND headers and the first SDP offer indicating all specific data for MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to AS/IM_B 11 100 Trying AS/IM_B responds with a 100 Trying provisional response 12 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to IBCF_B 15 100 Trying IBCF_B responds with a 100 Trying provisional response 16 INVITE IBCF_B forwards INVITE to IBCF_A 17 100 Trying IBCF_A responds with a 100 Trying provisional response 18 INVITE IBCF_A forwards INVITE to IMS_A 19 100 Trying IMS_A responds with a 100 Trying provisional response 20 INVITE IMS_A forwards INVITE to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 104 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 21 100 Trying AS/IM_A responds with a 100 Trying provisional response 22 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 23 100 Trying IMS_A responds with a 100 Trying provisional response 24 INVITE IMS_A forwards INVITE to UE_A 25 100 Trying UE_A optionally responds with a 100 Trying provisional response 26 User A is informed of incoming message 27 180 Ringing UE_A responds to initial INVITE with 180 Ringing to indicate that invitation to a 1-to-1 chat session has reached the invited user 28 180 Ringing IMS_A forwards 180 Ringing response to AS/IM_A 29 180 Ringing AS/IM_A returns, possibly modified, 180 Ringing response to IMS_A 30 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 31 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 32 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 33 180 Ringing IMS_B forwards 180 Ringing response to AS/IM_B 34 180 Ringing AS/IM_B returns, possibly modified, 180 Ringing response to IMS_B 35 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 36 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 37 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 38 180 Ringing IMS_A forwards 180 Ringing response to UE_B 39 MESSAGE UE_A sends MESSAGE to IMS_A with delivery notification of initial message from user B 40 MESSAGE IMS_A forwards MESSAGE to AS/IM_A 41 MESSAGE AS/IM_A returns, possibly modified, MESSAGE to IMS_A 42 MESSAGE IMS_A forwards MESSAGE to IBCF_A 43 MESSAGE IBCF_A forwards MESSAGE to IBCF_B 44 MESSAGE IBCF_B forwards MESSAGE to IMS_B 45 MESSAGE IMS_B forwards MESSAGE to AS/IM_B 46 MESSAGE AS/IM_B returns, possibly modified, MESSAGE to IMS_B 47 MESSAGE IMS_B forwards MESSAGE to IBCF_B 48 MESSAGE IBCF_B forwards MESSAGE to IBCF_A 49 MESSAGE IBCF_A forwards MESSAGE to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 105 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 50 MESSAGE IMS_A forwards MESSAGE to UE_B 51 User B is informed that initial message was delivered to user A 52 200 OK UE_B responds MESSAGE with 200 OK response 53 200 OK IMS_A forwards 200 OK response to IBCF_A 54 200 OK IBCF_A forwards 200 OK response to IBCF_B 55 200 OK IBCF_B forwards 200 OK response to IMS_B 56 200 OK IMS_B forwards 200 OK response to AS/IM_B 57 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 58 200 OK IMS_B forwards 200 OK response to IBCF_B 59 200 OK IBCF_B forwards 200 OK response to IBCF_A 60 200 OK IBCF_A forwards 200 OK response to IMS_A 61 200 OK IMS_A forwards 200 OK response to AS/IM_A 62 200 OK AS/IM_A returns, possibly modified, ACK to IMS_A 63 200 OK IMS_A forwards ACK to UE_A (CheckMSRP2) 64 User A reads the initial message from user B and opens the 1-to-1 chat 65 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform B-side with specific data for MSRP connection set up 66 200 OK IMS_A forwards 200 OK response to AS/IM_A 67 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 68 200 OK IMS_A forwards 200 OK response to IBCF_A 69 200 OK IBCF_A forwards 200 OK response to IBCF_B 70 200 OK IBCF_B forwards 200 OK response to IMS_B 71 200 OK IMS_B forwards 200 OK response to AS/IM_B 72 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 73 200 OK IMS_B forwards 200 OK response to IBCF_B 74 200 OK IBCF_B forwards 200 OK response to IBCF_A 75 200 OK IBCF_A forwards 200 OK response to IMS_A 76 200 OK IMS_A forwards 200 OK response to UE_B 77 ACK UE_B acknowledges the receipt of 200 OK for INVITE 78 ACK IMS_A forwards ACK to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 106 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 79 ACK IBCF_A forwards ACK to IBCF_B 80 ACK IBCF_B forwards ACK to IMS_B 81 ACK IMS_B forwards ACK to AS/IM_B 82 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 83 ACK IMS_B forwards ACK to IBCF_B 84 ACK IBCF_B forwards ACK to IBCF_A 85 ACK IBCF_A forwards ACK to IMS_A 86 ACK IMS_A forwards ACK to AS/IM_A 87 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 88 ACK IMS_A forwards ACK to UE_A 89 Users perform chatting (see clause 5.3.1 Chat 1 to 1 via MSRP and use 5.4.1 test description) - CheckMSRP2 90A User B closes the 1-to-1 chat 91A BYE UE_B releases the 1-to-1 chat session with BYE 92A BYE IMS_A forwards BYE to IBCF_A 93A BYE IBCF_A forwards BYE to IBCF_B 94A BYE IBCF_B forwards BYE to IMS_B 95A BYE IMS_B forwards BYE to AS/IM_B 96A BYE AS/IM_B returns, possibly modified, BYE to IMS_B 97A BYE IMS_B forwards BYE to IBCF_B 98A BYE IBCF_B forwards BYE to IBCF_A 99A BYE IBCF_A forwards BYE to IMS_A 100A BYE IMS_A forwards BYE to AS/IM_A 101A BYE AS/IM_A returns, possibly modified, BYE to IMS_A 102A BYE IMS_A forwards BYE to UE_A 103A 200 OK UE_A sends 200 OK for BYE 104A 200 OK IMS_A forwards 200 OK response to AS/IM_A 105A 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 106A 200 OK IMS_A forwards 200 OK response to IBCF_A 107A 200 OK IBCF_A forwards 200 OK response to IBCF_B 108A 200 OK IBCF_B forwards 200 OK response to IMS_B 109A 200 OK IMS_B forwards 200 OK response to AS/IM_B 110A 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 111A 200 OK IMS_B forwards 200 OK response to IBCF_B 112A 200 OK IBCF_B forwards 200 OK response to IBCF_A 113A 200 OK IBCF_A forwards 200 OK response to IMS_A 114A 200 OK IMS_A forwards 200 OK response to UE_B 115A User B is informed that that 1-to-1 chat with user A is closed 90B User A closes the 1-to-1 chat ETSI ETSI TS 102 901 V4.1.1 (2012-05) 107 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 91B BYE UE_A releases the 1-to-1 chat session with BYE 92B BYE IMS_A forwards BYE to AS/IM_A 93B BYE AS/IM_A returns, possibly modified, BYE to IMS_A 94B BYE IMS_A forwards BYE to IBCF_A 95B BYE IBCF_A forwards BYE to IBCF_B 96B BYE IBCF_B forwards BYE to IMS_B 97B BYE IMS_B forwards BYE to AS/IM_B 98B BYE AS/IM_B returns, possibly modified, BYE to IMS_B 99B BYE IMS_B forwards BYE to IBCF_B 100B BYE IBCF_B forwards BYE to IBCF_A 101B BYE IBCF_A forwards BYE to IMS_A 102B BYE IMS_A forwards BYE to UE_B 103B 200 OK UE_B sends 200 OK for BYE 104B 200 OK IMS_A forwards 200 OK response to IBCF_A 105B 200 OK IBCF_A forwards 200 OK response to IBCF_B 106B 200 OK IBCF_B forwards 200 OK response to IMS_B 107B 200 OK IMS_B forwards 200 OK response to AS/IM_B 108B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 109B 200 OK IMS_B forwards 200 OK response to IBCF_B 110B 200 OK IBCF_B forwards 200 OK response to IBCF_A 111B 200 OK IBCF_A forwards 200 OK response to IMS_A 112B 200 OK IMS_A forwards 200 OK response to AS/IM_A 113B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 114B 200 OK IMS_A forwards 200 OK response to UE_A 115B User A is informed that that 1-to-1 chat with user B is closed
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.2 Several messages prior to establishment of 1-to-1 chat
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.2.1 Several messages prior to establishment of 1-to-1 chat - interworking	Interoperability Test Description Identifier: TD_IMS_CHAT_0003 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users in their home network can be performed. User B must wait until receiving several messages from User A before accepting the chat invitation Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (1st numbered list) TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.3 ¶5 ETSI ETSI TS 102 901 V4.1.1 (2012-05) 108 Interoperability Test Description (item 4 in 1st numbered list) TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶89 (4th numbered list) TD_MSRP_CHAT_0001 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 Use Case ref.: UC_RCS_4_I & UC_MSRP_01 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A and UE_B shall support MSRP • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A selects User B in the phone address book and sends him an initial message with MSRP indication 2 User B is informed of incoming message 3 User A is informed that initial message was delivered to user B 4 User A sends to User B a second message 5 User B is informed of incoming two messages 6 User A is informed that second message was delivered to user B 7 User B reads the incoming messages from user A and opens the 1-to-1 chat 8 Users perform chatting (MSRP session) 9A User A closes the 1-to-1 chat 9B User B closes the 1-to-1 chat 10A User A is informed that 1-to-1 chat with user B is closed 10B User B is informed that 1-to-1 chat with user A is closed Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 10 (INVITE): ensure that { when { UE_A sends an initial INVITE to UE_B } then { IMS_B receives the initial INVITE not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A containing a P-Charging-Vector_header (containing an icid-value_parameter and containing a orig-ioi_parameter indicating IMS_A and not containing an access-network-charging-info_parameter and not containing a term-ioi_parameter) and containing a Record-Route_header indicating the originating S-CSCF_SIP_URI } } 2 TP_IMS_5108_03 in CFW step 14 (INVITE) ensure that { when {IMS_B receives an initial INVITE from IMS_A addressed_to UE_B} then {IMS_B sends the INVITE to AS_B containing a topmost Route_header indicating the SIP_URI of AS_B and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 109 Interoperability Test Description } 3 TP_IMS_5115_08 in CFW step 35 (200 OK) ensure that { when { IMS_B receives 200_response from AS_B addressed to UE_A } then { IMS_B sends the 200_response to IMS_A containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and including a term-ioi_parameter indicating operator_identifier of IMS_B } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_I (1-48) 2 User A sends to User B a second message 3 INVITE UE_A sends second INVITE to IMS_A with user A second message in the Subject header, CPIM/IMND headers and the first SDP offer indicating all specific data for MSRP connection set up 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to AS/IM_A 6 100 Trying AS/IM_A responds with a 100 Trying provisional response 7 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 8 100 Trying IMS_A responds with a 100 Trying provisional response 9 INVITE IMS_A forwards INVITE to IBCF_A 10 100 Trying IBCF_A responds with a 100 Trying provisional response 11 INVITE IBCF_A forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to AS/IM_B 16 100 Trying AS/IM_B responds with a 100 Trying provisional response 17 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 18 100 Trying IMS_B responds with a 100 Trying provisional response 19 INVITE IMS_B forwards INVITE to UE_B 20 100 Trying UE_B optionally responds with a 100 Trying provisional response 21 User B is informed of incoming two messages 22 180 Ringing UE_B responds to additional INVITE with 180 Ringing to indicate that invitation to an enhanced messaging session has reached the invited user 23 180 Ringing IMS_B forwards 180 Ringing response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 110 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 24 180 Ringing AS/IM_B returns, possibly modified, 180 Ringing response to IMS_B 25 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 26 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 27 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 28 180 Ringing IMS_A forwards 180 Ringing response to AS/IM_A 29 180 Ringing AS/IM_A returns, possibly modified, 180 Ringing response to IMS_A 30 180 Ringing IMS_A forwards 180 Ringing response to UE_A 31 MESSAGE UE_B sends MESSAGE to IMS_B with delivery notification of second message from user A 32 MESSAGE IMS_B forwards MESSAGE to AS/IM_B 33 MESSAGE AS/IM_B returns, possibly modified, MESSAGE to IMS_B 34 MESSAGE IMS_B forwards MESSAGE to IBCF_B 35 MESSAGE IBCF_B forwards MESSAGE to IBCF_A 36 MESSAGE IBCF_A forwards MESSAGE to IMS_A 37 MESSAGE IMS_A forwards MESSAGE to AS/IM_A 38 MESSAGE AS/IM_A returns, possibly modified, MESSAGE to IMS_A 39 MESSAGE IMS_A forwards MESSAGE to UE_A 40 User A is informed that second message was delivered to user B 41 200 OK UE_A responds MESSAGE with 200 OK response 42 200 OK IMS_A forwards 200 OK response to AS/IM_A 43 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 44 200 OK IMS_A forwards 200 OK response to IBCF_A 45 200 OK IBCF_A forwards 200 OK response to IBCF_B 46 200 OK IBCF_B forwards 200 OK response to IMS_B 47 200 OK IMS_B forwards 200 OK response to AS/IM_B 48 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 49 200 OK IMS_B forwards 200 OK response to UE_B 50 User B reads the incoming messages from user A and opens the 1-to-1 chat 51 603 DECLINE UE_B responds INVITE 603 DECLINE to indicate that the initial session has been declined 52 603 DECLINE IMS_B forwards 603 DECLINE response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 111 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 53 603 DECLINE AS/IM_B returns, possibly modified, 603 DECLINE response to IMS_B 54 603 DECLINE IMS_B forwards 603 DECLINE response to IBCF_B 55 603 DECLINE IBCF_B forwards 603 DECLINE response to IBCF_A 56 603 DECLINE IBCF_A forwards 603 DECLINE response to IMS_A 57 603 DECLINE IMS_A forwards 603 DECLINE response to AS/IM_A 58 603 DECLINE AS/IM_A returns, possibly modified, 603 DECLINE response to IMS_A 59 603 DECLINE IMS_A forwards 603 DECLINE response to UE_A 60 ACK UE_A acknowledges the receipt of 603 DECLINE for INVITE 61 ACK IMS_A forwards ACK to AS/IM_A 62 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 63 ACK IMS_A forwards ACK to IBCF_A 64 ACK IBCF_A forwards ACK to IBCF_B 65 ACK IBCF_B forwards ACK to IMS_B 66 ACK IMS_B forwards ACK to AS/IM_B 67 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 68 ACK IMS_B forwards ACK to UE_B 69 200 OK UE_B responds second INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform A-side with specific data for MSRP connection set up 70 200 OK IMS_B forwards 200 OK response to AS/IM_B 71 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 72 200 OK IMS_B forwards 200 OK response to IBCF_B 73 200 OK IBCF_B forwards 200 OK response to IBCF_A 74 200 OK IBCF_A forwards 200 OK response to IMS_A 75 200 OK IMS_A forwards 200 OK response to AS/IM_A 76 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 77 200 OK IMS_A forwards 200 OK response to UE_A 78 ACK UE_A acknowledges the receipt of 200 OK for the second INVITE 79 ACK IMS_A forwards ACK to AS/IM_A 80 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 81 ACK IMS_A forwards ACK to IBCF_A 82 ACK IBCF_A forwards ACK to IBCF_B 83 ACK IBCF_B forwards ACK to IMS_B 84 ACK IMS_B forwards ACK to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 112 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 85 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 86 ACK IMS_B forwards ACK to UE_B 87 Users perform chatting (see clause 5.3.1 Chat 1 to 1 via MSRP CheckMSRP3) 88 Continue UC_RCS_4_I (69A-88B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.2.2 Several messages prior to establishment of 1-to-1 chat - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_CHAT_0004 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users, one user in its home network and one user roaming can be performed. User B must wait until receiving several messages from User A before accepting the chat invitation Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ¶1 (1st numbered list) TP_IMS_5067_01 TS 124 229 [1], clause 5.2.7.2 ¶5 TP_IMS_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Use Case ref.: UC_RCS_4_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B selects User A in the phone address book and sends him an initial message with MSRP indication 2 User A is informed of incoming message 3 User B is informed that initial message was delivered to user A 4 User B sends to User A a second message 5 User A is informed of incoming two messages 6 User B is informed that second message was delivered to user A 7 User A reads the incoming messages from user B and opens the 1-to-1 chat 8 Users perform chatting (MSRP session) 9A User B closes the 1-to-1 chat 9B User A closes the 1-to-1 chat 10A User B is informed that 1-to-1 chat with user A is closed 10B User A is informed that 1-to-1 chat with user B is closed ETSI ETSI TS 102 901 V4.1.1 (2012-05) 113 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5046_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a Route_header not indicating the P-CSCF_SIP_URI of IMS_A and containing a Route_header indicating the "list of Service Route header URIs from the registration" and containing an additional Via_header containing ( the P-CSCF_via_port_number and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and containing an additional topmost Record-Route_header indicating (the P-CSCF_port_number 'where it awaits subsequent requests' from UE_A and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and not containing P-Preferred-Identity_header and containing a P-Asserted-Identity_header containing an address of UE_B and containing a P-Charging-Vector_header containing an icid-value_parameter } } 2 TP_IMS_5067_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a P-Charging-Vector_header } } 3 TP_IMS_5097_09 in CFW step 10 (INVITE) ensure that { when { IMS_B receives an initial INVITE from IMS_A addressed to UE_A } then { IMS_B sends the initial INVITE to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header (including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter and including access-network-charging-info) } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_R (1-63) 2 User B sends to User A a second message 3 INVITE UE_B sends second INVITE to IMS_A with user A second message in the Subject header, CPIM/IMND headers and the first SDP offer indicating all specific data for MSRP connection set up 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 114 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to AS/IM_B 12 100 Trying AS/IM_B responds with a 100 Trying provisional response 13 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to IBCF_B 16 100 Trying IBCF_B responds with a 100 Trying provisional response 17 INVITE IBCF_B forwards INVITE to IBCF_A 18 100 Trying IBCF_A responds with a 100 Trying provisional response 19 INVITE IBCF_A forwards INVITE to IMS_A 20 100 Trying IMS_A responds with a 100 Trying provisional response 21 INVITE IMS_A forwards INVITE to AS/IM_A 22 100 Trying AS/IM_A responds with a 100 Trying provisional response 23 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 24 100 Trying IMS_A responds with a 100 Trying provisional response 25 INVITE IMS_A forwards INVITE to UE_A 26 100 Trying UE_A optionally responds with a 100 Trying provisional response 27 User A is informed of incoming two messages 28 180 Ringing UE_A responds second INVITE with 180 Ringing to indicate that invitation to an enhanced messaging session has reached the invited user 29 180 Ringing IMS_A forwards 180 Ringing response to AS/IM_A 30 180 Ringing AS/IM_A returns, possibly modified, 180 Ringing response to IMS_A 31 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 32 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 33 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 34 180 Ringing IMS_B forwards 180 Ringing response to AS/IM_B 35 180 Ringing AS/IM_B returns, possibly modified, 180 Ringing response to IMS_B 36 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 37 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 38 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 115 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 39 180 Ringing IMS_A forwards 180 Ringing response to UE_B 40 MESSAGE UE_A sends MESSAGE to IMS_A with delivery notification of initial message from user B 41 MESSAGE IMS_A forwards MESSAGE to AS/IM_A 42 MESSAGE AS/IM_A returns, possibly modified, MESSAGE to IMS_A 43 MESSAGE IMS_A forwards MESSAGE to IBCF_A 44 MESSAGE IBCF_A forwards MESSAGE to IBCF_B 45 MESSAGE IBCF_B forwards MESSAGE to IMS_B 46 MESSAGE IMS_B forwards MESSAGE to AS/IM_B 47 MESSAGE AS/IM_B returns, possibly modified, MESSAGE to IMS_B 48 MESSAGE IMS_B forwards MESSAGE to IBCF_B 49 MESSAGE IBCF_B forwards MESSAGE to IBCF_A 50 MESSAGE IBCF_A forwards MESSAGE to IMS_A 51 MESSAGE IMS_A forwards MESSAGE to UE_B 52 User B is informed that second message was delivered to user A 53 200 OK UE_B responds MESSAGE with 200 OK response 54 200 OK IMS_A forwards 200 OK response to IBCF_A 55 200 OK IBCF_A forwards 200 OK response to IBCF_B 56 200 OK IBCF_B forwards 200 OK response to IMS_B 57 200 OK IMS_B forwards 200 OK response to AS/IM_B 58 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 59 200 OK IMS_B forwards 200 OK response to IBCF_B 60 200 OK IBCF_B forwards 200 OK response to IBCF_A 61 200 OK IBCF_A forwards 200 OK response to IMS_A 62 200 OK IMS_A forwards 200 OK response to AS/IM_A 63 200 OK AS/IM_A returns, possibly modified, ACK to IMS_A 64 200 OK IMS_A forwards ACK to UE_A 65 User A reads the incoming messages from user B and opens the 1-to-1 chat 66 603 DECLINE UE_A responds initial INVITE with 603 DECLINE response with SDP to indicate that the session has been declined ETSI ETSI TS 102 901 V4.1.1 (2012-05) 116 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 67 603 DECLINE IMS_A forwards 603 DECLINE response to AS/IM_A 68 603 DECLINE AS/IM_A returns, possibly modified, 603 DECLINE response to IMS_A 69 603 DECLINE IMS_A forwards 603 DECLINE response to IBCF_A 70 603 DECLINE IBCF_A forwards 603 DECLINE response to IBCF_B 71 603 DECLINE IBCF_B forwards 603 DECLINE response to IMS_B 72 603 DECLINE IMS_B forwards 603 DECLINE response to AS/IM_B 73 603 DECLINE AS/IM_B returns, possibly modified, 603 DECLINE response to IMS_B 74 603 DECLINE IMS_B forwards 603 DECLINE response to IBCF_B 75 603 DECLINE IBCF_B forwards 603 DECLINE response to IBCF_A 76 603 DECLINE IBCF_A forwards 603 DECLINE response to IMS_A 77 603 DECLINE IMS_A forwards 603 DECLINE response to UE_B 78 ACK UE_B acknowledges the receipt of 603 DECLINE for the initial INVITE 79 ACK IMS_A forwards ACK to IBCF_A 80 ACK IBCF_A forwards ACK to IBCF_B 81 ACK IBCF_B forwards ACK to IMS_B 82 ACK IMS_B forwards ACK to AS/IM_B 83 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 84 ACK IMS_B forwards ACK to IBCF_B 85 ACK IBCF_B forwards ACK to IBCF_A 86 ACK IBCF_A forwards ACK to IMS_A 87 ACK IMS_A forwards ACK to AS/IM_A 88 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 89 ACK IMS_A forwards ACK to UE_A 90 200 OK UE_A responds second INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform B-side with specific data for MSRP connection set up 91 200 OK IMS_A forwards 200 OK response to AS/IM_A 92 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 93 200 OK IMS_A forwards 200 OK response to IBCF_A 94 200 OK IBCF_A forwards 200 OK response to IBCF_B 95 200 OK IBCF_B forwards 200 OK response to IMS_B 96 200 OK IMS_B forwards 200 OK response to AS/IM_B 97 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 98 200 OK IMS_B forwards 200 OK response to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 117 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 99 200 OK IBCF_B forwards 200 OK response to IBCF_A 100 200 OK IBCF_A forwards 200 OK response to IMS_A 101 200 OK IMS_A forwards 200 OK response to UE_B 102 ACK UE_B acknowledges the receipt of 200 OK for INVITE 103 ACK IMS_A forwards ACK to IBCF_A 104 ACK IBCF_A forwards ACK to IBCF_B 105 ACK IBCF_B forwards ACK to IMS_B 106 ACK IMS_B forwards ACK to AS/IM_B 107 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 108 ACK IMS_B forwards ACK to IBCF_B 109 ACK IBCF_B forwards ACK to IBCF_A 110 ACK IBCF_A forwards ACK to IMS_A 111 ACK IMS_A forwards ACK to AS/IM_A 112 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 113 ACK IMS_A forwards ACK to UE_A 114 Users perform chatting (see clause 5.3.1 Chat 1 to 1 via MSRP) 115 Continue UC_RCS_4_R (90A-115B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.3 Switching to 1-to-many chat
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.3.1 Switching to 1-to-many chat - interworking	Interoperability Test Description Identifier: TD_IMS_CHAT_0007 Summary: IMS network supports 1-to-many IM/Chat service and messages exchange between two users in their home network can be performed. User A switching 1-to-1 chat to 1- to-many chat by inviting User C Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) TD_MSRP_CHAT_0002 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 Use Case ref.: UC_RCS_7_I & UC_MSRP_02 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A, UE_C and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B and UE_C are registered in IMS_B optionally using userPRES according to table 1 • UE_A, UE_B and UE_C shall support MSRP • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B and UE_C • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization ETSI ETSI TS 102 901 V4.1.1 (2012-05) 118 Interoperability Test Description • IMS_A is within the trust domain of IMS_B • UE_A, UE_C and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A selects User B in the phone address book and sends him an initial message with MSRP indication 2 User B is informed of incoming message 3 User A is informed that initial message was delivered to user B 4 User B reads the initial message from user A and opens the 1-to-1 chat 5 Users perform 1-to-1 chatting 6 User A initiates a 1-to-many Chat with User B and User C by sending initial message 7 User A is informed that the 1-to-many Chat is established 8 User B is informed of incoming invitation from User A to join the 1-to-many Chat 9 User B reads the initial message and accepts the 1-to-many Chat invitation 10 User A is notified with list of 1-to-many Chat participants 11 User B is notified with list of 1-to-many Chat participants 12 Users perform messaging in the 1-to-many Chat (MSRP session) 13 User B leaves the 1-to-many Chat 14 User B is informed that he has left the 1-to-many Chat 15 User A is notified that User B has left the 1-to-many Chat 16A User A leaves the 1-to-many Chat 16B User C leaves the 1-to-many Chat 17A User A is informed that the 1-to-many Chat has ended 17B User B is informed that the 1-to-many Chat has ended 17C User C is informed that the 1-to-many Chat has ended Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 41 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 119 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_I (1-68) 2 User A initiates a 1-to-many Chat with User B and User C by sending initial message 3 INVITE UE_A sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users, the first SDP offer indicating all specific data for MSRP connection set up and the identity of User B with Session- Replaces header (CheckMSR1) 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to AS/IM_A 6 100 Trying AS/IM_A responds with a 100 Trying provisional response 7 200 OK AS/IM_A responds INVITE with 200 OK response with IM session Identity allocated for the current 1- to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up 8 200 OK IMS_A forwards 200 OK response to AS/IM_A 9 User A is informed that the 1-to- many Chat is accepted 10 ACK UE_A acknowledges the receipt of 200 OK for INVITE 11 ACK IMS_A forwards ACK to AS/IM_A 12 INVITE AS/IM_A sends INVITE to UE_B with IM session identity (allocated for the current 1-to-many Chat), IM address of the Inviting IM UE (UE_A) and Session-Replaces header with the original 1-to-1 session identity 13 100 Trying IMS_A responds with a 100 Trying provisional response 14 INVITE IMS_A forwards INVITE to IBCF_A 15 100 Trying IBCF_A responds with a 100 Trying provisional response 16 INVITE IBCF_A forwards INVITE to IBCF_B 17 100 Trying IBCF_B responds with a 100 Trying provisional response 18 INVITE IBCF_B forwards INVITE to IMS_B 19 100 Trying IMS_B responds with a 100 Trying provisional response 20 INVITE IMS_B forwards INVITE to AS/IM_B 21 100 Trying AS/IM_B responds with a 100 Trying provisional response 22 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 23 100 Trying IMS_B responds with a 100 Trying provisional response 24 INVITE IMS_B forwards INVITE to UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 120 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 25 100 Trying UE_B optionally responds with a 100 Trying provisional response 26 User B is informed of incoming invitation from User A to join the 1- to-many Chat 27 User B reads the initial message and accepts the 1-to-many Chat invitation 28 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 29 200 OK IMS_B forwards 200 OK response to AS/IM_B 30 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 31 200 OK IMS_B forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IBCF_A 33 200 OK IBCF_A forwards 200 OK response to IMS_A 34 200 OK IMS_A forwards 200 OK response to AS/IM_A 35 ACK AS/IM_A acknowledges the receipt of 200 OK for INVITE 36 ACK IMS_A forwards ACK to IBCF_A 37 ACK IBCF_A forwards ACK to IBCF_B 38 ACK IBCF_B forwards ACK to IMS_B 39 ACK IMS_B forwards ACK to AS/IM_B 40 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 41 ACK IMS_B forwards ACK to UE_B 42 Users perform messaging in the 1- to-many Chat (see clause 5.3.2.1 Chat 1 to many via MSRP - Interworking) 43 BYE UE_B releases the 1-to-1 IM session with BYE 43A BYE IMS_B forwards BYE to AS/IM_B 44 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 45 BYE IMS_B forwards BYE to IBCF_B 46 BYE IBCF_B forwards BYE to IBCF_A 47 BYE IBCF_A forwards BYE to IMS_A 48 BYE IMS_A forwards BYE to AS/IM_A 49 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 50 BYE IMS_A forwards BYE to UE_A 51 200 OK UE_A sends 200 OK for BYE 52 200 OK IMS_A forwards 200 OK response to AS/IM_A 53 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 54 200 OK IMS_A forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 121 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 55 200 OK IBCF_A forwards 200 OK response to IBCF_B 56 200 OK IBCF_B forwards 200 OK response to IMS_B 57 200 OK IMS_B forwards 200 OK response to AS/IM_B 58 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 59 200 OK IMS_B forwards 200 OK response to UE_B 60 SUBSCRIBE UE_A subscribes to the conference event package 61 SUBSCRIBE IMS_A forwards SUBCRIBE to AS/IM_A 62 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 63 200 OK IMS_A forwards 200 OK response to UE_A 64 NOTIFY AS/IM_A sends NOTIFY to UE_A with list of 1-to-many Chat participants 65 NOTIFY IMS_A forwards the NOTIFY to UE_A 66 User A is notified with list of 1-to- many Chat participants 67 200 OK UE_A responds with 200 OK to IMS_A 68 200 OK IMS_A forwards the 200 OK response to AS/IM_A 69 SUBSCRIBE UE_B subscribes to the conference event package 70 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 71 SUBSCRIBE AS/IM_B returns, possibly modified, SUBSCRIBE to IMS_B 72 SUBSCRIBE IMS_B forwards SUBSCRIBE to IBCF_B 73 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IBCF_A 74 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IMS_A 75 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 76 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 77 200 OK IMS_A forwards 200 OK response to IBCF_A 78 200 OK IBCF_A forwards 200 OK response to IBCF_B 79 200 OK IBCF_B forwards 200 OK response to IMS_B 80 200 OK IMS_B forwards 200 OK response to AS/IM_B 81 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 82 200 OK IMS_B forwards 200 OK response to UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 122 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 83 NOTIFY AS/IM_A sends NOTIFY to UE_B with list of 1-to-many Chat participants 84 NOTIFY IMS_A forwards BYE to IBCF_A 85 NOTIFY IBCF_A forwards BYE to IBCF_B 86 NOTIFY IBCF_B forwards BYE to IMS_B 87 NOTIFY IMS_B forwards BYE to AS/IM_B 88 NOTIFY AS/IM_B returns, possibly modified, BYE to IMS_B 89 NOTIFY IMS_B forwards BYE to UE_B 90 User B is notified with list of 1-to- many Chat participants 91 200 OK UE_B sends 200 OK for NOTIFY 92 200 OK IMS_B forwards 200 OK response to AS/IM_B 93 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 94 200 OK IMS_B forwards 200 OK response to IBCF_B 95 200 OK IBCF_B forwards 200 OK response to IBCF_A 96 200 OK IBCF_A forwards 200 OK response to IMS_A 97 200 OK IMS_A forwards 200 OK response to AS/IM_A 98 Users perform messaging in the 1- to-many Chat (see clause 5.3.2.1 Chat 1 to many via MSRP - Interworking) 99 Continue UC_RCS_6_I (80A-116B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.3.2 Switching to 1-to-many chat - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_CHAT_0008 Summary: IMS network supports 1-to-many IM/Chat service and messages exchange between two users, one user in its home network and one user roaming can be performed. User B switching 1-to-1 chat to 1-to-many chat by inviting User C Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) TD_MSRP_CHAT_0002 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 Use Case ref.: UC_RCS_7_R & UC_MSRP_02_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A, UE_C and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B and UE_C are registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A, UE_B and UE_C shall support MSRP • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B and UE_C ETSI ETSI TS 102 901 V4.1.1 (2012-05) 123 Interoperability Test Description • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A, UE_C and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B selects User A in the phone address book and sends him an initial message with MSRP indication 2 User A is informed of incoming message 3 User B is informed that initial message was delivered to user A 4 User A reads the initial message from user B and opens the 1-to-1 chat 5 Users perform 1-to-1 chatting (MSRP session) 6 User B initiates a 1-to-many Chat with User A and User C by sending initial message 7 User B is informed that the 1-to-many Chat is established 8 User A is informed of incoming invitation from User B to join the 1-to-many Chat 9 User A reads the initial message and accepts the 1-to-many Chat invitation 10 User B is notified with list of 1-to-many Chat participants 11 User A is notified with list of 1-to-many Chat participants 12 Users perform messaging in the 1-to-many Chat (MSRP session) 13A User A leaves the 1-to-many Chat 13B User B leaves the 1-to-many Chat 14A User A is informed that he has left the 1-to-many Chat 14B User B is informed that he has left the 1-to-many Chat 15A User B is notified that all other users have left the 1-to-many Chat 15B User A is notified that all other users have left the 1-to-many Chat 16A User B leaves the 1-to-many Chat 16B User A leaves the 1-to-many Chat 17A User B is informed that the 1-to-many Chat has ended 17B User A is informed that the 1-to-many Chat has ended Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 56 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_R (1-89) 2 User B initiates a 1-to-many Chat with User A and User C by sending initial message 3 INVITE UE_B sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users, the first SDP offer indicating all specific data for MSRP connection set up and the identity of User A with Session- Replaces header ETSI ETSI TS 102 901 V4.1.1 (2012-05) 124 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to AS/IM_B 12 100 Trying AS/IM_B responds with a 100 Trying provisional response 13 200 OK AS/IM_B responds INVITE with 200 OK response with IM session Identity allocated for the current 1- to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up 14 200 OK IMS_B forwards 200 OK response to IBCF_B 15 200 OK IBCF_B forwards 200 OK response to IBCF_A 16 200 OK IBCF_A forwards 200 OK response to IMS_A 17 200 OK IMS_A forwards 200 OK response to UE_B 18 User B is informed that the 1-to- many Chat is established 19 ACK UE_B acknowledges the receipt of 200 OK for INVITE 20 ACK IMS_A forwards ACK to IBCF_A 21 ACK IBCF_A forwards ACK to IBCF_B 22 ACK IBCF_B forwards ACK to IMS_B 23 ACK IMS_B forwards ACK to AS/IM_B 24 INVITE AS/IM_B sends INVITE to UE_A with IM session identity (allocated for the current 1-to-many Chat), IM address of the Inviting IM UE (UE_B) and Session-Replaces header with the original 1-to-1 session identity 25 100 Trying IMS_B responds with a 100 Trying provisional response 26 INVITE IMS_B forwards INVITE to IBCF_B 27 100 Trying IBCF_B responds with a 100 Trying provisional response 28 INVITE IBCF_B forwards INVITE to IBCF_A 29 100 Trying IBCF_A responds with a 100 Trying provisional response 30 INVITE IBCF_A forwards INVITE to IMS_A 31 100 Trying IMS_A responds with a 100 Trying provisional response 32 INVITE IMS_A forwards INVITE to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 125 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 33 100 Trying AS/IM_A responds with a 100 Trying provisional response 34 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 35 100 Trying IMS_A responds with a 100 Trying provisional response 36 INVITE IMS_A forwards INVITE to UE_A 37 100 Trying UE_A optionally responds with a 100 Trying provisional response 38 User A is informed of incoming invitation from user B to join the 1- to-many Chat 39 User A reads the initial message and accepts the 1-to-many Chat invitation 40 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 41 200 OK IMS_A forwards 200 OK response to AS/IM_A 42 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 43 200 OK IMS_A forwards 200 OK response to IBCF_A 44 200 OK IBCF_A forwards 200 OK response to IBCF_B 45 200 OK IBCF_B forwards 200 OK response to IMS_B 46 200 OK IMS_B forwards 200 OK response to AS/IM_B 47 ACK AS/IM_B acknowledges the receipt of 200 OK for INVITE 48 ACK IMS_B forwards ACK to IBCF_B 49 ACK IBCF_B forwards ACK to IBCF_A 50 ACK IBCF_A forwards ACK to IMS_A 51 ACK IMS_A forwards ACK to AS/IM_A 52 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 53 ACK IMS_A forwards ACK to UE_A 54 BYE UE_A releases the 1-to-1 IM session with BYE 55 BYE IMS_A forwards BYE to AS/IM_A 56 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 57 BYE IMS_A forwards BYE to IBCF_A 58 BYE IBCF_A forwards BYE to IBCF_B 59 BYE IBCF_B forwards BYE to IMS_B 60 BYE IMS_B forwards BYE to AS/IM_B 61 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 62 BYE IMS_B forwards BYE to IBCF_B 63 BYE IBCF_B forwards BYE to IBCF_A 64 BYE IBCF_A forwards BYE to IMS_A 65 BYE IMS_A forwards BYE to UE_B 66 200 OK UE_B sends 200 OK for BYE ETSI ETSI TS 102 901 V4.1.1 (2012-05) 126 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 67 200 OK IMS_A forwards 200 OK response to IBCF_A 68 200 OK IBCF_A forwards 200 OK response to IBCF_B 69 200 OK IBCF_B forwards 200 OK response to IMS_B 70 200 OK IMS_B forwards 200 OK response to AS/IM_B 71 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 72 200 OK IMS_B forwards 200 OK response to IBCF_B 73 200 OK IBCF_B forwards 200 OK response to IBCF_A 74 200 OK IBCF_A forwards 200 OK response to IMS_A 75 200 OK IMS_A forwards 200 OK response to AS/IM_A 76 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 77 200 OK IMS_A forwards 200 OK response to UE_A 78 SUBSCRIBE UE_B subscribes to the conference event package 79 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 80 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 81 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 82 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 83 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 84 200 OK IMS_B forwards 200 OK response to IBCF_B 85 200 OK IBCF_B forwards 200 OK response to IBCF_A 86 200 OK IBCF_A forwards 200 OK response to IMS_A 87 200 OK IMS_A forwards 200 OK response to UE_B 88 NOTIFY AS/IM_B sends NOTIFY to UE_B with list of 1-to-many Chat participants 89 NOTIFY IMS_B forwards NOTIFY to IBCF_B 90 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 91 NOTIFY IBCF_A forwards NOTIFY to IMS_A 92 NOTIFY IMS_A forwards NOTIFY to UE_B 93 User B is notified with list of 1-to- many Chat participants 94 200 OK UE_B responds with 200 OK to IMS_A 95 200 OK IMS_A forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 127 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 96 200 OK IBCF_A forwards 200 OK response to IBCF_B 97 200 OK IBCF_B forwards 200 OK response to IMS_B 98 200 OK IMS_B forwards 200 OK response to AS/IM_B 99 SUBSCRIBE UE_A subscribes to the conference event package 100 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 101 SUBSCRIBE AS/IM_A returns, possibly modified, SUBSCRIBE to IMS_A 102 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 103 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 104 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 105 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 106 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 107 200 OK IMS_B forwards 200 OK response to IBCF_B 108 200 OK IBCF_B forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 128 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 109 200 OK IBCF_A forwards 200 OK response to IMS_A 110 200 OK IMS_A forwards 200 OK response to AS/IM_A 111 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 112 200 OK IMS_A forwards 200 OK response to UE_A 113 NOTIFY AS/IM_B sends NOTIFY to UE_A with list of 1-to-many Chat participants 114 NOTIFY IMS_B forwards BYE to IBCF_B 115 NOTIFY IBCF_B forwards BYE to IBCF_A 116 NOTIFY IBCF_A forwards BYE to IMS_A 117 NOTIFY IMS_A forwards BYE to AS/IM_A 118 NOTIFY AS/IM_A returns, possibly modified, BYE to IMS_A 119 NOTIFY IMS_A forwards BYE to UE_A 120 User A is notified with list of 1-to- many Chat participants 121 200 OK UE_A sends 200 OK for NOTIFY 122 200 OK IMS_A forwards 200 OK response to AS/IM_A 123 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 124 200 OK IMS_A forwards 200 OK response to IBCF_A 125 200 OK IBCF_A forwards 200 OK response to IBCF_B 126 200 OK IBCF_B forwards 200 OK response to IMS_B 127 200 OK IMS_B forwards 200 OK response to AS/IM_B 128 Users perform messaging in the 1- to-many Chat (see clause 5.3.2.2 Chat 1 to many via MSRP - Roaming) 129 Continue UC_RCS_6_R (104A- 146B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.4 File transfer within 1-to-1 chat
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.4.1 File transfer within 1-to-1 chat - interworking	Interoperability Test Description Identifier: TD_IMS_CHAT_0009 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users in their home network can be performed. User A starts file transfer with User B Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) TD_MSRP_FILE_0001 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 ETSI ETSI TS 102 901 V4.1.1 (2012-05) 129 Interoperability Test Description RFC 5547 [13] Use Case ref.: UC_RCS_5_I & UC_MSRP_04 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • UE_A, UE_B and UE_C shall support MSRP • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A selects User B in the phone address book and sends him an initial message with MSRP indication 2 User B is informed of incoming message 3 User A is informed that initial message was delivered to user B 4 User B reads the initial message from user A and opens the 1-to-1 chat 5 Users perform chatting 6 User A initiates a file transfer to user B 7 User B is informed of incoming file and accepts the transfer 8 User A is informed that file transfer has been accepted by user B 9 File transfer starts (MSRP session) 10 File transfer completed (size checked) 11 User B is informed that file transfer completed 12 User A is informed that file transfer completed 13 Users continue chatting (MSRP session) 14A User A closes the 1-to-1 chat 14B User B closes the 1-to-1 chat 15A User A is informed that 1-to-1 chat with user B is closed 15B User B is informed that 1-to-1 chat with user A is closed Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 41 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_I (1-68) 2 User A initiates a file transfer to user B (MSRP session) 3 INVITE UE_A sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 4 100 Trying IMS_A responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 130 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 5 INVITE IMS_A forwards INVITE to AS/IM_A 6 100 Trying AS/IM_A responds with a 100 Trying provisional response 7 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 8 100 Trying IMS_A responds with a 100 Trying provisional response 9 INVITE IMS_A forwards INVITE to IBCF_A 10 100 Trying IBCF_A responds with a 100 Trying provisional response 11 INVITE IBCF_A forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to AS/IM_B 16 100 Trying AS/IM_B responds with a 100 Trying provisional response 17 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 18 100 Trying IMS_B responds with a 100 Trying provisional response 19 INVITE IMS_B forwards INVITE to UE_B 20 100 Trying UE_B optionally responds with a 100 Trying provisional response 21 User B is informed of incoming file and accepts the transfer 22 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform A-side with specific data for a new MSRP connection set up 23 200 OK IMS_B forwards 200 OK response to AS/IM_B 24 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 25 200 OK IMS_B forwards 200 OK response to IBCF_B 26 200 OK IBCF_B forwards 200 OK response to IBCF_A 27 200 OK IBCF_A forwards 200 OK response to IMS_A 28 200 OK IMS_A forwards 200 OK response to AS/IM_A 29 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 30 200 OK IMS_A forwards 200 OK response to UE_A 31 User A is informed that file transfer has been accepted by user B 32 ACK UE_A acknowledges the receipt of 200 OK for INVITE 33 ACK IMS_A forwards ACK to AS/IM_A 34 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 35 ACK IMS_A forwards ACK to IBCF_A 36 ACK IBCF_A forwards ACK to IBCF_B 37 ACK IBCF_B forwards ACK to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 131 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 38 ACK IMS_B forwards ACK to AS/IM_B 39 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 40 ACK IMS_B forwards ACK to UE_B 41 File transfer starts (see clause 5.3.3 Image data via MSRP - CheckMSRP3) 42 File transfer completed (size checked) and users can continue with 1 to 1 chat (see clause 5.3.1 Chat 1 to 1 via MSRP- CheckMSRP3) 43 BYE UE_A releases the file transfer session with BYE 44 BYE IMS_A forwards BYE to AS/IM_A 45 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 46 BYE IMS_A forwards BYE to IBCF_A 47 BYE IBCF_A forwards BYE to IBCF_B 48 BYE IBCF_B forwards BYE to IMS_B 49 BYE IMS_B forwards BYE to AS/IM_B 50 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 51 BYE IMS_B forwards BYE to UE_B 52 User B is informed that file transfer completed 53 200 OK UE_B sends 200 OK for BYE 54 200 OK IMS_B forwards 200 OK response to AS/IM_B 55 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 56 200 OK IMS_B forwards 200 OK response to IBCF_B 57 200 OK IBCF_B forwards 200 OK response to IBCF_A 58 200 OK IBCF_A forwards 200 OK response to IMS_A 59 200 OK IMS_A forwards 200 OK response to AS/IM_A 60 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 61 200 OK IMS_A forwards 200 OK response to UE_A 62 User A is informed that file transfer completed 63 Users continue chatting 64 Continue UC_RCS_4_I (69A-88B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.4.2 File transfer within 1-to-1 chat - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_CHAT_0010 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users, one user in its home network and one user roaming can be performed. User B starts file transfer with User A Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 132 Interoperability Test Description References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) TD_MSRP_FILE_0001 RFC 4975 [10], clauses 5.4, 7.1 & 7.2 RFC 5547 [13] Use Case ref.: UC_RCS_5_R & UC_MSRP_04 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A, UE_B and UE_C shall support MSRP • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B selects User A in the phone address book and sends him an initial message 2 User A is informed of incoming message 3 User B is informed that initial message was delivered to user A 4 User A reads the initial message from user B and opens the 1-to-1 chat 5 Users perform chatting 6 User B initiates a file transfer to user A 7 User A is informed of incoming file and accepts the transfer 8 User B is informed that file transfer has been accepted by user B 9 File transfer starts 10 File transfer completed (size checked) 11 User A is informed that file transfer completed 12 User B is informed that file transfer completed 13 Users continue chatting 14A User B closes the 1-to-1 chat 14B User A closes the 1-to-1 chat 15A User B is informed that that 1-to-1 chat with user A is closed 15B User A is informed that that 1-to-1 chat with user B is closed Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 56 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 133 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_R (1-89) 2 User B initiates a file transfer to user A (MSRP session) 3 INVITE UE_B sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to AS/IM_B 12 100 Trying AS/IM_B responds with a 100 Trying provisional response 13 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to IBCF_B 16 100 Trying IBCF_B responds with a 100 Trying provisional response 17 INVITE IBCF_B forwards INVITE to IBCF_A 18 100 Trying IBCF_A responds with a 100 Trying provisional response 19 INVITE IBCF_A forwards INVITE to IMS_A 20 100 Trying IMS_A responds with a 100 Trying provisional response 21 INVITE IMS_A forwards INVITE to AS/IM_A 22 100 Trying AS/IM_A responds with a 100 Trying provisional response 23 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 24 100 Trying IMS_A responds with a 100 Trying provisional response 25 INVITE IMS_A forwards INVITE to UE_A 26 100 Trying UE_A optionally responds with a 100 Trying provisional response 27 User A is informed of incoming file and accepts the transfer 28 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform B-side with specific data for a new MSRP connection set up 29 200 OK IMS_A forwards 200 OK response to AS/IM_A 30 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 31 200 OK IMS_A forwards 200 OK response to IBCF_A 32 200 OK IBCF_A forwards 200 OK response to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 134 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 33 200 OK IBCF_B forwards 200 OK response to IMS_B 34 200 OK IMS_B forwards 200 OK response to AS/IM_B 35 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 36 200 OK IMS_B forwards 200 OK response to IBCF_B 37 200 OK IBCF_B forwards 200 OK response to IBCF_A 38 200 OK IBCF_A forwards 200 OK response to IMS_A 39 200 OK IMS_A forwards 200 OK response to UE_B 40 User B is informed that file transfer has been accepted by user B 41 ACK UE_B acknowledges the receipt of 200 OK for INVITE 42 ACK IMS_A forwards ACK to IBCF_A 43 ACK IBCF_A forwards ACK to IBCF_B 44 ACK IBCF_B forwards ACK to IMS_B 45 ACK IMS_B forwards ACK to AS/IM_B 46 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 47 ACK IMS_B forwards ACK to IBCF_B 48 ACK IBCF_B forwards ACK to IBCF_A 49 ACK IBCF_A forwards ACK to IMS_A 50 ACK IMS_A forwards ACK to AS/IM_A 51 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 52 ACK IMS_A forwards ACK to UE_A 53 File transfer starts (see clause 5.3.3 Image data via MSRP ) 54 File transfer completed (size checked) and users can continue with 1 to 1 chat (see clause 5.3.1 Chat 1 to 1 via MSRP) 55 BYE UE_B releases the file transfer session with BYE 56 BYE IMS_A forwards BYE to IBCF_A 57 BYE IBCF_A forwards BYE to IBCF_B 58 BYE IBCF_B forwards BYE to IMS_B 59 BYE IMS_B forwards BYE to AS/IM_B 60 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 61 BYE IMS_B forwards BYE to IBCF_B 62 BYE IBCF_B forwards BYE to IBCF_A 63 BYE IBCF_A forwards BYE to IMS_A 64 BYE IMS_A forwards BYE to AS/IM_A 65 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 66 BYE IMS_A forwards BYE to UE_A 67 User A is informed that file transfer completed 68 200 OK UE_A sends 200 OK for BYE 69 200 OK IMS_A forwards 200 OK response to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 135 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 70 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 71 200 OK IMS_A forwards 200 OK response to IBCF_A 72 200 OK IBCF_A forwards 200 OK response to IBCF_B 73 200 OK IBCF_B forwards 200 OK response to IMS_B 74 200 OK IMS_B forwards 200 OK response to AS/IM_B 75 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 76 200 OK IMS_B forwards 200 OK response to IBCF_B 77 200 OK IBCF_B forwards 200 OK response to IBCF_A 78 200 OK IBCF_A forwards 200 OK response to IMS_A 79 200 OK IMS_A forwards 200 OK response to UE_B 80 User B is informed that file transfer completed 81 Users continue chatting 82 Continue UC_RCS_4_R (90A-115B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.5 File transfer rejection within 1-to-1 chat
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.5.1 File transfer rejection within 1-to-1 chat - interworking	Interoperability Test Description Identifier: TD_IMS_CHAT_0011 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users in their home network can be performed. User A starts file transfer with User B, but User B rejects invitation Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Use Case ref.: UC_RCS_5_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding ETSI ETSI TS 102 901 V4.1.1 (2012-05) 136 Interoperability Test Description Test Sequence: Step 1 User A selects User B in the phone address book and sends him an initial message 2 User B is informed of incoming message 3 User A is informed that initial message was delivered to user B 4 User B reads the initial message from user A and opens the 1-to-1 chat 5 Users perform chatting 6 User A initiates a file transfer to user B 7 User B is informed of incoming file and rejects the transfer 8 User A is informed that file transfer has been rejected by user B 9 Users continue chatting 10A User A closes the 1-to-1 chat 10B User B closes the 1-to-1 chat 11A User A is informed that 1-to-1 chat with user B is closed 11B User B is informed that 1-to-1 chat with user A is closed Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 41 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_I (1-68) 2 User A initiates a file transfer to user B 3 INVITE UE_A sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to AS/IM_A 6 100 Trying AS/IM_A responds with a 100 Trying provisional response 7 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 8 100 Trying IMS_A responds with a 100 Trying provisional response 9 INVITE IMS_A forwards INVITE to IBCF_A 10 100 Trying IBCF_A responds with a 100 Trying provisional response 11 INVITE IBCF_A forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to AS/IM_B 16 100 Trying AS/IM_B responds with a 100 Trying provisional response 17 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 137 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 18 100 Trying IMS_B responds with a 100 Trying provisional response 19 INVITE IMS_B forwards INVITE to UE_B 20 100 Trying UE_B optionally responds with a 100 Trying provisional response 21 User B is informed of incoming file and rejects the transfer 22 603 Decline UE_B responds INVITE with 603 Decline response to indicate that the session has been rejected 23 603 Decline IMS_B forwards 603 Decline response to AS/IM_B 24 603 Decline AS/IM_B returns, possibly modified, 603 Decline response to IMS_B 25 603 Decline IMS_B forwards 603 Decline response to IBCF_B 26 603 Decline IBCF_B forwards 603 Decline response to IBCF_A 27 603 Decline IBCF_A forwards 603 Decline response to IMS_A 28 603 Decline IMS_A forwards 603 Decline response to AS/IM_A 29 603 Decline AS/IM_A returns, possibly modified, 603 Decline response to IMS_A 30 603 Decline IMS_A forwards 603 Decline response to UE_A 31 User A is informed that file transfer has been rejected by user B 32 ACK UE_A acknowledges the receipt of 603 Decline response for INVITE 33 ACK IMS_A forwards ACK to AS/IM_A 34 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 35 ACK IMS_A forwards ACK to IBCF_A 36 ACK IBCF_A forwards ACK to IBCF_B 37 ACK IBCF_B forwards ACK to IMS_B 38 ACK IMS_B forwards ACK to AS/IM_B 39 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 40 ACK IMS_B forwards ACK to UE_B 41 Users continue chatting (see clause 5.3.1 Chat 1 to 1 via MSRP - CheckMSRP3) 42 Continue UC_RCS_4_I (69A-88B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.5.2 File transfer rejection within 1-to-1 chat - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_CHAT_0012 Summary: IMS network supports 1-to-1 IM/Chat service and messages exchange between two users, one user in its home network and one user roaming can be performed. User B starts file transfer with User A, but User A rejects invitation Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) ETSI ETSI TS 102 901 V4.1.1 (2012-05) 138 Interoperability Test Description TD_MSRP_FILE_0001 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 RFC 5547 [13] Use Case ref.: UC_RCS_5_R & UC_MSRP_02 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A, UE_B and UE_C shall support MSRP • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B selects User A in the phone address book and sends him an initial message with MSRP indication 2 User A is informed of incoming message 3 User B is informed that initial message was delivered to user A 4 User A reads the initial message from user B and opens the 1-to-1 chat 5 Users perform chatting (MSRP session) 6 User B initiates a file transfer to user A 7 User A is informed of incoming file and rejects the transfer 8 User B is informed that file transfer has been rejected by user B 9 Users continue chatting (MSRP session) 10A User B closes the 1-to-1 chat 10B User A closes the 1-to-1 chat 11A User B is informed that that 1-to-1 chat with user A is closed 11B User A is informed that that 1-to-1 chat with user B is closed Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 56 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_R (1-89) 2 User B initiates a file transfer to user A 3 INVITE UE_B sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up (MSRP session) 4 100 Trying IMS_A responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 139 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to AS/IM_B 12 100 Trying AS/IM_B responds with a 100 Trying provisional response 13 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to IBCF_B 16 100 Trying IBCF_B responds with a 100 Trying provisional response 17 INVITE IBCF_B forwards INVITE to IBCF_A 18 100 Trying IBCF_A responds with a 100 Trying provisional response 19 INVITE IBCF_A forwards INVITE to IMS_A 20 100 Trying IMS_A responds with a 100 Trying provisional response 21 INVITE IMS_A forwards INVITE to AS/IM_A 22 100 Trying AS/IM_A responds with a 100 Trying provisional response 23 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 24 100 Trying IMS_A responds with a 100 Trying provisional response 25 INVITE IMS_A forwards INVITE to UE_A 26 100 Trying UE_A optionally responds with a 100 Trying provisional response 27 User A is informed of incoming file and rejects the transfer 28 603 Decline UE_A responds INVITE with 603 Decline response to indicate that the session has been rejected 29 603 Decline IMS_A forwards 603 Decline response to AS/IM_A 30 603 Decline AS/IM_A returns, possibly modified, 603 Decline response to IMS_A 31 603 Decline IMS_A forwards 603 Decline response to IBCF_A 32 603 Decline IBCF_A forwards 603 Decline response to IBCF_B 33 603 Decline IBCF_B forwards 603 Decline response to IMS_B 34 603 Decline IMS_B forwards 603 Decline response to AS/IM_B 35 603 Decline AS/IM_B returns, possibly modified, 603 Decline response to IMS_B 36 603 Decline IMS_B forwards 603 Decline response to IBCF_B 37 603 Decline IBCF_B forwards 603 Decline response to IBCF_A 38 603 Decline IBCF_A forwards 603 Decline response to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 140 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 39 603 Decline IMS_A forwards 603 Decline response to UE_B 40 User B is informed that file transfer has been rejected by user B 41 ACK UE_B acknowledges the receipt of 603 Decline response for INVITE 42 ACK IMS_A forwards ACK to IBCF_A 43 ACK IBCF_A forwards ACK to IBCF_B 44 ACK IBCF_B forwards ACK to IMS_B 45 ACK IMS_B forwards ACK to AS/IM_B 46 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 47 ACK IMS_B forwards ACK to IBCF_B 48 ACK IBCF_B forwards ACK to IBCF_A 49 ACK IBCF_A forwards ACK to IMS_A 50 ACK IMS_A forwards ACK to AS/IM_A 51 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 52 ACK IMS_A forwards ACK to UE_A 53 Users continue chatting (see clause 5.3.1 Chat 1 to 1 via MSRP - CheckMSRP3) 54 Continue UC_RCS_4_R (90A-115B)
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.6 1-to-many chat
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.6.1 1-to-many chat - interworking	Interoperability Test Description Identifier: TD_IMS_CHAT_0013 Summary: IMS network supports 1-to-many IM/Chat service and messages exchange between two users in their home network can be performed. User A starts 1-to-many chat with users B and C Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) TD_MSRP_FILE_0001 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 RFC 5547 [13] Use Case ref.: UC_RCS_6_I & UC_MSRP_02 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A, UE_C and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B and UE_C are registered in IMS_B optionally using userPRES according to table 1 • UE_A, UE_B and UE_C shall support MSRP • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B and UE_C • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization ETSI ETSI TS 102 901 V4.1.1 (2012-05) 141 Interoperability Test Description • IMS_A is within the trust domain of IMS_B • UE_A, UE_C and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A initiates a 1-to-many Chat with User B and User C by sending initial message 2 User A is informed that the 1-to-many Chat is established 3 User B is informed of incoming invitation from User A to join the 1-to-many Chat 4 User B reads the initial message and accepts the 1-to-many Chat invitation 5 User A is notified with list of 1-to-many Chat participants 6 User B is notified with list of 1-to-many Chat participants 7 Users perform messaging in the 1-to-many Chat 8A User B leaves the 1-to-many Chat 8B User A leaves the 1-to-many Chat 9A User B is informed that he has left the 1-to-many Chat 9B User A is informed that he has left the 1-to-many Chat 10A User A is notified that all other users have left the 1-to-many Chat 10B User B is notified that all other users have left the 1-to-many Chat 11A User A leaves the 1-to-many Chat 11B User B leaves the 1-to-many Chat 12A User A is informed that the 1-to-many Chat has ended 12B User B is informed that the 1-to-many Chat has ended Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 41 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User A initiates a 1-to-many Chat with User B and User C by sending initial message 2 INVITE UE_A sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users and the first SDP offer indicating all specific data for MSRP connection set up (CheckMSRP1) 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to AS/IM_A 5 100 Trying AS/IM_A responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 142 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 6 200 OK AS/IM_A responds INVITE with 200 OK response with IM session Identity allocated for the current 1-to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up 7 200 OK IMS_A forwards 200 OK response to AS/IM_A 8 User A is informed that the 1-to- many Chat is established 9 ACK UE_A acknowledges the receipt of 200 OK for INVITE 10 ACK IMS_A forwards ACK to AS/IM_A 11 INVITE AS/IM_A sends INVITE to UE_B with IM session identity (allocated for the current 1-to-many Chat) and IM address of the Inviting IM UE (UE_A) 12 100 Trying IMS_A responds with a 100 Trying provisional response 13 INVITE IMS_A forwards INVITE to IBCF_A 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IBCF_B 16 100 Trying IBCF_B responds with a 100 Trying provisional response 17 INVITE IBCF_B forwards INVITE to IMS_B 18 100 Trying IMS_B responds with a 100 Trying provisional response 19 INVITE IMS_B forwards INVITE to AS/IM_B 20 100 Trying AS/IM_B responds with a 100 Trying provisional response 21 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 22 100 Trying IMS_B responds with a 100 Trying provisional response 23 INVITE IMS_B forwards INVITE to UE_B 24 100 Trying UE_B optionally responds with a 100 Trying provisional response 25 User B is informed of incoming invitation from User A to join the 1-to-many Chat 26 User B reads the initial message and accepts the 1-to-many Chat invitation 27 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 28 200 OK IMS_B forwards 200 OK response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 143 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 29 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 30 200 OK IMS_B forwards 200 OK response to IBCF_B 31 200 OK IBCF_B forwards 200 OK response to IBCF_A 32 200 OK IBCF_A forwards 200 OK response to IMS_A 33 200 OK IMS_A forwards 200 OK response to AS/IM_A 34 ACK AS/IM_A acknowledges the receipt of 200 OK for INVITE 35 ACK IMS_A forwards ACK to IBCF_A 36 ACK IBCF_A forwards ACK to IBCF_B 37 ACK IBCF_B forwards ACK to IMS_B 38 ACK IMS_B forwards ACK to AS/IM_B 39 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 40 ACK IMS_B forwards ACK to UE_B 41 SUBSCRIBE UE_A subscribes to the conference event package 42 SUBSCRIBE IMS_A forwards SUBCRIBE to AS/IM_A 43 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 44 200 OK IMS_A forwards 200 OK response to UE_A 45 NOTIFY AS/IM_A sends NOTIFY to UE_A with list of 1-to-many Chat participants 46 NOTIFY IMS_A forwards the NOTIFY to UE_A 47 User A is notified with list of 1-to- many Chat participants 48 200 OK UE_A responds with 200 OK to IMS_A 49 200 OK IMS_A forwards the 200 OK response to AS/IM_A 50 SUBSCRIBE UE_B subscribes to the conference event package 51 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 52 SUBSCRIBE AS/IM_B returns, possibly modified, SUBSCRIBE to IMS_B 53 SUBSCRIBE IMS_B forwards SUBSCRIBE to IBCF_B 54 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IBCF_A 55 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IMS_A 56 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 57 200 OK AS/IM_A sends 200 OK for SUBSCRIBE ETSI ETSI TS 102 901 V4.1.1 (2012-05) 144 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 58 200 OK IMS_A forwards 200 OK response to IBCF_A 59 200 OK IBCF_A forwards 200 OK response to IBCF_B 60 200 OK IBCF_B forwards 200 OK response to IMS_B 61 200 OK IMS_B forwards 200 OK response to AS/IM_B 62 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 63 200 OK IMS_B forwards 200 OK response to UE_B 64 NOTIFY AS/IM_A sends NOTIFY to UE_B with list of 1-to-many Chat participants 65 NOTIFY IMS_A forwards BYE to IBCF_A 66 NOTIFY IBCF_A forwards BYE to IBCF_B 67 NOTIFY IBCF_B forwards BYE to IMS_B 68 NOTIFY IMS_B forwards BYE to AS/IM_B 69 NOTIFY AS/IM_B returns, possibly modified, BYE to IMS_B 70 NOTIFY IMS_B forwards BYE to UE_B 71 User B is notified with list of 1-to- many Chat participants 72 200 OK UE_B sends 200 OK for NOTIFY 73 200 OK IMS_B forwards 200 OK response to AS/IM_B 74 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 75 200 OK IMS_B forwards 200 OK response to IBCF_B 76 200 OK IBCF_B forwards 200 OK response to IBCF_A 77 200 OK IBCF_A forwards 200 OK response to IMS_A 78 200 OK IMS_A forwards 200 OK response to AS/IM_A 79 Users perform messaging in the 1-to-many Chat (see clause 5.3.2.1 Chat 1 to many via MSRP - Interworking) 80A User B leaves the 1-to-many Chat 81A BYE UE_B sends BYE to IMS_B to leave the 1-to-many Chat 82A BYE IMS_B forwards BYE to AS/IM_B 83A BYE AS/IM_B returns, possibly modified, BYE to IMS_B 84A BYE IMS_B forwards BYE to IBCF_B 85A BYE IBCF_B forwards BYE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 145 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 86A BYE IBCF_A forwards BYE to IMS_A 87A BYE IMS_A forwards BYE to AS/IM_A 88A 200 OK AS/IM_A sends 200 OK for BYE 89A 200 OK IMS_A forwards 200 OK response to IBCF_A 90A 200 OK IBCF_A forwards 200 OK response to IBCF_B 91A 200 OK IBCF_B forwards 200 OK response to IMS_B 92A 200 OK IMS_B forwards 200 OK response to AS/IM_B 93A 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 94A 200 OK IMS_B forwards 200 OK response to UE_B 95A User B is informed that he has left the 1-to-many Chat 96A NOTIFY AS/IM_A sends NOTIFY to IMS _A to inform UE_A that User B has left the 1-to-many Chat 97A NOTIFY IMS_A forwards the NOTIFY to UE_A 98A User A is notified that all other users have left the 1-to-many Chat 99A 200 OK UE_A responds with 200 OK to IMS_A 100A 200 OK IMS_A forwards the 200 OK response to AS/IM_A 101A User A leaves the 1-to-many Chat 102A BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 103A BYE IMS_A forwards BYE to AS/IM_A 104A 200 OK AS/IM_A sends 200 OK for BYE 105A 200 OK IMS_A forwards 200 OK response to UE_A 106A User A is informed that the 1-to- many Chat has ended 80B User A leaves the 1-to-many Chat 81B BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 82B BYE IMS_A forwards BYE to AS/IM_A 83B 200 OK AS/IM_A sends 200 OK for BYE 84B 200 OK IMS_A forwards 200 OK response to UE_A 85B User A is informed that he has left the 1-to-many Chat 86B NOTIFY AS/IM_A sends NOTIFY to IMS_A to inform UE_B that User A has left the 1-to-many Chat ETSI ETSI TS 102 901 V4.1.1 (2012-05) 146 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 87B NOTIFY IMS_A forwards BYE to IBCF_A 88B NOTIFY IBCF_A forwards BYE to IBCF_B 89B NOTIFY IBCF_B forwards BYE to IMS_B 90B NOTIFY IMS_B forwards BYE to AS/IM_B 91B NOTIFY AS/IM_B returns, possibly modified, BYE to IMS_B 92B NOTIFY IMS_B forwards BYE to UE_B 93B User B is notified that all other users have left the 1-to-many Chat 94B 200 OK UE_B sends 200 OK for NOTIFY 95B 200 OK IMS_B forwards 200 OK response to AS/IM_B 96B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 97B 200 OK IMS_B forwards 200 OK response to IBCF_B 98B 200 OK IBCF_B forwards 200 OK response to IBCF_A 99B 200 OK IBCF_A forwards 200 OK response to IMS_A 100B 200 OK IMS_A forwards 200 OK response to AS/IM_A 101B User B leaves the 1-to-many Chat 102B BYE UE_B sends BYE to IMS_B to leave the 1-to-many Chat 103B BYE IMS_B forwards BYE to AS/IM_B 104B BYE AS/IM_B returns, possibly modified, BYE to IMS_B 105B BYE IMS_B forwards BYE to IBCF_B 106B BYE IBCF_B forwards BYE to IBCF_A 107B BYE IBCF_A forwards BYE to IMS_A 108B BYE IMS_A forwards BYE to AS/IM_A 109B 200 OK AS/IM_A sends 200 OK for BYE 110B 200 OK IMS_A forwards 200 OK response to IBCF_A 111B 200 OK IBCF_A forwards 200 OK response to IBCF_B 112B 200 OK IBCF_B forwards 200 OK response to IMS_B 113B 200 OK IMS_B forwards 200 OK response to AS/IM_B 114B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 115B 200 OK IMS_B forwards 200 OK response to UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 147 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 116B User B is informed that the 1-to- many Chat has ended
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.6.2 1-to-many chat - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_CHAT_0014 Summary: IMS network supports 1-to-many IM/Chat service and messages exchange between two users, one user in its home network and one user roaming can be performed. User B starts 1-to-many chat with user A and C Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Use Case ref.: UC_RCS_6_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A, UE_C and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B and UE_C are registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B and UE_C • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A, UE_C and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B initiates a 1-to-many Chat with User A and User C by sending initial message 2 User B is informed that the 1-to-many Chat is established 3 User A is informed of incoming invitation from User B to join the 1-to-many Chat 4 User A reads the initial message and accepts the 1-to-many Chat invitation 5 User B is notified with list of 1-to-many Chat participants 6 User A is notified with list of 1-to-many Chat participants 7 Users perform messaging in the 1-to-many Chat 8A User A leaves the 1-to-many Chat 8B User B leaves the 1-to-many Chat 9A User A is informed that he has left the 1-to-many Chat 9B User B is informed that he has left the 1-to-many Chat 10A User B is notified that all other users have left the 1-to-many Chat 10B User A is notified that all other users have left the 1-to-many Chat 11A User B leaves the 1-to-many Chat 11B User A leaves the 1-to-many Chat 12A User B is informed that the 1-to-many Chat has ended 12B User A is informed that the 1-to-many Chat has ended ETSI ETSI TS 102 901 V4.1.1 (2012-05) 148 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 56 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 149 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User B initiates a 1-to-many Chat with User A and User C by sending initial message 2 INVITE UE_B sends INVITE to IMS_A with Request-URI set to IM CONFERENCE FACTORY URI, MIME resource-list body including invited IM Users and the first SDP offer indicating all specific data for MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to AS/IM_B 11 100 Trying AS/IM_B responds with a 100 Trying provisional response 12 200 OK AS/IM_B responds INVITE with 200 OK response with IM session Identity allocated for the current 1- to-many Chat to indicate that the session has been accepted and SDP to inform A-side with specific data for MSRP connection set up 13 200 OK IMS_B forwards 200 OK response to IBCF_B 14 200 OK IBCF_B forwards 200 OK response to IBCF_A 15 200 OK IBCF_A forwards 200 OK response to IMS_A 16 200 OK IMS_A forwards 200 OK response to UE_B 17 User B is informed that the 1-to- many Chat is established 18 ACK UE_B acknowledges the receipt of 200 OK for INVITE 19 ACK IMS_A forwards ACK to IBCF_A 20 ACK IBCF_A forwards ACK to IBCF_B 21 ACK IBCF_B forwards ACK to IMS_B 22 ACK IMS_B forwards ACK to AS/IM_B 23 INVITE AS/IM_B sends INVITE to UE_A with IM session identity (allocated for the current 1-to-many Chat) and IM address of the Inviting IM UE (UE_B) 24 100 Trying IMS_B responds with a 100 Trying provisional response 25 INVITE IMS_B forwards INVITE to IBCF_B 26 100 Trying IBCF_B responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 150 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 27 INVITE IBCF_B forwards INVITE to IBCF_A 28 100 Trying IBCF_A responds with a 100 Trying provisional response 29 INVITE IBCF_A forwards INVITE to IMS_A 30 100 Trying IMS_A responds with a 100 Trying provisional response 31 INVITE IMS_A forwards INVITE to AS/IM_A 32 100 Trying AS/IM_A responds with a 100 Trying provisional response 33 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 34 100 Trying IMS_A responds with a 100 Trying provisional response 35 INVITE IMS_A forwards INVITE to UE_A 36 100 Trying UE_A optionally responds with a 100 Trying provisional response 37 User A is informed of incoming invitation from User B to join the 1- to-many Chat 38 User A reads the initial message and accepts the 1-to-many Chat invitation 39 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 40 200 OK IMS_A forwards 200 OK response to AS/IM_A 41 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 42 200 OK IMS_A forwards 200 OK response to IBCF_A 43 200 OK IBCF_A forwards 200 OK response to IBCF_B 44 200 OK IBCF_B forwards 200 OK response to IMS_B 45 200 OK IMS_B forwards 200 OK response to AS/IM_B 46 ACK AS/IM_B acknowledges the receipt of 200 OK for INVITE 47 ACK IMS_B forwards ACK to IBCF_B 48 ACK IBCF_B forwards ACK to IBCF_A 49 ACK IBCF_A forwards ACK to IMS_A 50 ACK IMS_A forwards ACK to AS/IM_A 51 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 52 ACK IMS_A forwards ACK to UE_A 53 SUBSCRIBE UE_B subscribes to the conference event package 54 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 55 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 56 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 151 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 57 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 58 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 59 200 OK IMS_B forwards 200 OK response to IBCF_B 60 200 OK IBCF_B forwards 200 OK response to IBCF_A 61 200 OK IBCF_A forwards 200 OK response to IMS_A 62 200 OK IMS_A forwards 200 OK response to UE_B 63 NOTIFY AS/IM_B sends NOTIFY to UE_B with list of 1-to-many Chat participants 64 NOTIFY IMS_B forwards NOTIFY to IBCF_B 65 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 66 NOTIFY IBCF_A forwards NOTIFY to IMS_A 67 NOTIFY IMS_A forwards NOTIFY to UE_B 68 User B is notified with list of 1-to- many Chat participants 69 200 OK UE_B responds with 200 OK to IMS_A 70 200 OK IMS_A forwards 200 OK response to IBCF_A 71 200 OK IBCF_A forwards 200 OK response to IBCF_B 72 200 OK IBCF_B forwards 200 OK response to IMS_B 73 200 OK IMS_B forwards 200 OK response to AS/IM_B 74 SUBSCRIBE UE_A subscribes to the conference event package 75 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 76 SUBSCRIBE AS/IM_A returns, possibly modified, SUBSCRIBE to IMS_A 77 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 78 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B 79 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 80 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 81 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 82 200 OK IMS_B forwards 200 OK response to IBCF_B 83 200 OK IBCF_B forwards 200 OK response to IBCF_A 84 200 OK IBCF_A forwards 200 OK response to IMS_A 85 200 OK IMS_A forwards 200 OK response to AS/IM_A 86 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 152 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 87 200 OK IMS_A forwards 200 OK response to UE_A 88 NOTIFY AS/IM_B sends NOTIFY to UE_A with list of 1-to-many Chat participants 89 NOTIFY IMS_B forwards NOTIFY to IBCF_B 90 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 91 NOTIFY IBCF_A forwards NOTIFY to IMS_A 92 NOTIFY IMS_A forwards NOTIFY to AS/IM_A 93 NOTIFY AS/IM_A returns, possibly modified, NOTIFY to IMS_A 94 NOTIFY IMS_A forwards NOTIFY to UE_A 95 User A is notified with list of 1-to- many Chat participants 96 200 OK UE_A sends 200 OK for NOTIFY 97 200 OK IMS_A forwards 200 OK response to AS/IM_A 98 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 99 200 OK IMS_A forwards 200 OK response to IBCF_A 100 200 OK IBCF_A forwards 200 OK response to IBCF_B 101 200 OK IBCF_B forwards 200 OK response to IMS_B 102 200 OK IMS_B forwards 200 OK response to AS/IM_B 103 Users perform messaging in the 1- to-many Chat (see clause 5.3.2.2 Chat 1 to many via MSRP - Roaming) 104A User A leaves the 1-to-many Chat 105A BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 106A BYE IMS_A forwards BYE to AS/IM_A 107A BYE AS/IM_A returns, possibly modified, BYE to IMS_A 108A BYE IMS_A forwards BYE to IBCF_A 109A BYE IBCF_A forwards BYE to IBCF_B 110A BYE IBCF_B forwards BYE to IMS_B 111A BYE IMS_B forwards BYE to AS/IM_B 112A 200 OK AS/IM_B sends 200 OK for BYE 113A 200 OK IMS_B forwards 200 OK response to IBCF_B 114A 200 OK IBCF_B forwards 200 OK response to IBCF_A 115A 200 OK IBCF_A forwards 200 OK response to IMS_A 116A 200 OK IMS_A forwards 200 OK response to AS/IM_A 117A 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 118A 200 OK IMS_A forwards 200 OK response to UE_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 153 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 119A User A is informed that he has left the 1-to-many Chat 120A NOTIFY AS/IM_B sends NOTIFY to IMS _B to inform UE_B that User A has left the 1-to-many Chat 121A NOTIFY IMS_B forwards NOTIFY to IBCF_B 122A NOTIFY IBCF_B forwards NOTIFY to IBCF_A 123A NOTIFY IBCF_A forwards NOTIFY to IMS_A 124A NOTIFY IMS_A forwards NOTIFY to UE_B 125A User B is notified that all other users have left the 1-to-many Chat 126A 200 OK UE_B responds with 200 OK to IMS_A 127A 200 OK IMS_A forwards 200 OK response to IBCF_A 128A 200 OK IBCF_A forwards 200 OK response to IBCF_B 129A 200 OK IBCF_B forwards 200 OK response to IMS_B 130A 200 OK IMS_B forwards 200 OK response to AS/IM_B 131A User B leaves the 1-to-many Chat 132A BYE UE_B sends BYE to IMS_A to leave the 1-to-many Chat 133A BYE IMS_A forwards BYE to IBCF_A 134A BYE IBCF_A forwards BYE to IBCF_B 135A BYE IBCF_B forwards BYE to IMS_B 136A BYE IMS_B forwards BYE to AS/IM_B 137A 200 OK AS/IM_B sends 200 OK for BYE 138A 200 OK IMS_B forwards 200 OK response to IBCF_B 139A 200 OK IBCF_B forwards 200 OK response to IBCF_A 140A 200 OK IBCF_A forwards 200 OK response to IMS_A 141A 200 OK IMS_A forwards 200 OK response to UE_B 142A User B is informed that the 1-to- many Chat has ended 104B User B leaves the 1-to-many Chat 105B BYE UE_B sends BYE to IMS_A to leave the 1-to-many Chat 106B BYE IMS_A forwards BYE to IBCF_A 107B BYE IBCF_A forwards BYE to IBCF_B 108B BYE IBCF_B forwards BYE to IMS_B 109B BYE IMS_B forwards BYE to AS/IM_B 110B 200 OK AS/IM_B sends 200 OK for BYE 111B 200 OK IMS_B forwards 200 OK response to IBCF_B 112B 200 OK IBCF_B forwards 200 OK response to IBCF_A 113B 200 OK IBCF_A forwards 200 OK response to IMS_A 114B 200 OK IMS_A forwards 200 OK response to UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 154 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 115B User B is informed that he has left the 1-to-many Chat 116B NOTIFY AS/IM_B sends NOTIFY to IMS_B to inform UE_A that User B has left the 1-to-many Chat 117B NOTIFY IMS_B forwards NOTIFY to IBCF_B 118B NOTIFY IBCF_B forwards NOTIFY to IBCF_A 119B NOTIFY IBCF_A forwards NOTIFY to IMS_A 120B NOTIFY IMS_A forwards NOTIFY to AS/IM_A 121B NOTIFY AS/IM_A returns, possibly modified, NOTIFY to IMS_A 122B BYE IMS_A forwards NOTIFY to UE_A 123B User A is informed that User B has left the 1-to-many Chat 124B 200 OK UE_A sends 200 OK for NOTIFY 125B 200 OK IMS_A forwards 200 OK response to AS/IM_A 126B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 127B 200 OK IMS_A forwards 200 OK response to IBCF_A 128B 200 OK IBCF_A forwards 200 OK response to IBCF_B 129B 200 OK IBCF_B forwards 200 OK response to IMS_B 130B 200 OK IMS_B forwards 200 OK response to AS/IM_B 131B User A leaves the 1-to-many Chat 132B BYE UE_A sends BYE to IMS_A to leave the 1-to-many Chat 133B BYE IMS_A forwards BYE to AS/IM_A 134B BYE AS/IM_A returns, possibly modified, BYE to IMS_A 135B BYE IMS_A forwards BYE to IBCF_A 136B BYE IBCF_A forwards BYE to IBCF_B 137B BYE IBCF_B forwards BYE to IMS_B 138B BYE IMS_B forwards BYE to AS/IM_B 139B 200 OK AS/IM_B sends 200 OK for BYE 140B 200 OK IMS_B forwards 200 OK response to IBCF_B 141B 200 OK IBCF_B forwards 200 OK response to IBCF_A 142B 200 OK IBCF_A forwards 200 OK response to IMS_A 143B 200 OK IMS_A forwards 200 OK response to AS/IM_A 144B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 145B 200 OK IMS_A forwards 200 OK response to UE_A 146B User A is informed that the 1-to- many Chat has ended ETSI ETSI TS 102 901 V4.1.1 (2012-05) 155
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.3.7 Adding participants to an already established 1-to-many chat session	4.5.3.7.1 Adding participants to an already established 1-to-many chat session - interworking Interoperability Test Description Identifier: TD_IMS_CHAT_0015 Summary: IMS network supports 1-to-many IM/Chat service and messages exchange between two users in their network can be performed. User A invites User D to an already established 1-to-many Chat Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) TD_MSRP_CHAT_0002 RFC 4975 [10], clauses 5.4, 7.1 and 7.2 RFC 5547 [13] Use Case ref.: UC_RCS_6_I & UC_MSRP_02 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A, UE_C, UE_D and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B, UE_D and UE_C are registered in IMS_B optionally using userPRES according to table 1 • UE_A, UE_B and UE_C shall support MSRP • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B, UE_D and UE_C • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A, UE_C, UE_D and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A initiates a 1-to-many Chat with User B and User C by sending initial message 2 User A is informed that the 1-to-many Chat is established 3 User B is informed of incoming invitation from User A to join the 1-to-many Chat 4 User B reads the initial message and accepts the 1-to-many Chat invitation 5 User A is notified with list of 1-to-many Chat participants 6 User B is notified with list of 1-to-many Chat participants 7 Users perform messaging in the 1-to-many Chat 8 User A invites User D to join 1-to-many Chat 9 User D is informed of incoming invitation from User A to join the 1-to-many Chat 10 User D accepts the 1-to-many Chat invitation 11 User A is notified with list of 1-to-many Chat participants 12 User D is notified with list of 1-to-many Chat participants 13 Users perform messaging in the 1-to-many Chat 14 User D leaves the 1-to-many Chat 15 User D is informed that he has left the 1-to-many Chat 16 User A is notified that User D has left the 1-to-many Chat 17A User B leaves the 1-to-many Chat 17B User A leaves the 1-to-many Chat 18A User B is informed that he has left the 1-to-many Chat 18B User A is informed that he has left the 1-to-many Chat 19A User A is notified that all other users have left the 1-to-many Chat 19B User B is notified that all other users have left the 1-to-many Chat ETSI ETSI TS 102 901 V4.1.1 (2012-05) 156 Interoperability Test Description 20A User A leaves the 1-to-many Chat 20B User B leaves the 1-to-many Chat 20A User A is informed that the 1-to-many Chat has ended 20B User B is informed that the 1-to-many Chat has ended Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 41 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E D U s e r D 1 Follow UC_RCS_6_I (1-79) 2 User A invites User D to join 1-to- many Chat 3 REFER UE_A sends REFER message to IMS_A, with IM session identity (allocated for the current 1-to- many chat), Refer-To header value equals to UE_D URI and Refer-Sub header value set to "false" 4 REFER IMS_A forwards REFER to AS/IM_A 5 200 OK AS/IM_A responds with 200 OK to IMS_A 6 200 OK IMS_A forwards the 200 OK response to UE_A 7 INVITE AS/IM_A sends INVITE to UE_D with IM session identity (allocated for the current 1-to-many Chat) and IM address of the Inviting IM UE (UE_A) 8 100 Trying IMS_A responds with a 100 Trying provisional response 9 INVITE IMS_A forwards INVITE to IBCF_A 10 100 Trying IBCF_A responds with a 100 Trying provisional response 11 INVITE IBCF_A forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to AS/IM_B 16 100 Trying AS/IM_B responds with a 100 Trying provisional response 17 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 18 100 Trying IMS_B responds with a 100 Trying provisional response 19 INVITE IMS_B forwards INVITE to UE_D ETSI ETSI TS 102 901 V4.1.1 (2012-05) 157 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E D U s e r D 20 100 Trying UE_D optionally responds with a 100 Trying provisional response 21 User D is informed of incoming invitation from User A to join the 1-to-many Chat 22 User D accepts the 1-to-many Chat invitation 23 200 OK UE_D responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 24 200 OK IMS_B forwards 200 OK response to AS/IM_B 25 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 26 200 OK IMS_B forwards 200 OK response to IBCF_B 27 200 OK IBCF_B forwards 200 OK response to IBCF_A 28 200 OK IBCF_A forwards 200 OK response to IMS_A 29 200 OK IMS_A forwards 200 OK response to AS/IM_A 30 ACK AS/IM_A acknowledges the receipt of 200 OK for INVITE 31 ACK IMS_A forwards ACK to IBCF_A 32 ACK IBCF_A forwards ACK to IBCF_B 33 ACK IBCF_B forwards ACK to IMS_B 34 ACK IMS_B forwards ACK to AS/IM_B 35 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 36 ACK IMS_B forwards ACK to UE_D 37 NOTIFY AS/IM_A sends NOTIFY to UE_A with list of 1-to-many Chat participants 38 NOTIFY IMS_A forwards the NOTIFY to UE_A 39 User A is notified with list of 1-to- many Chat participants 40 200 OK UE_A responds with 200 OK to IMS_A 41 200 OK IMS_A forwards the 200 OK response to AS/IM_A 42 SUBSCRIBE UE_D subscribes to the conference event package 43 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 44 SUBSCRIBE AS/IM_B returns, possibly modified, SUBSCRIBE to IMS_B 45 SUBSCRIBE IMS_B forwards SUBSCRIBE to IBCF_B 46 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IBCF_A 47 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IMS_A 48 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 158 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E D U s e r D 49 200 OK AS/IM_A sends 200 OK for SUBSCRIBE 50 200 OK IMS_A forwards 200 OK response to IBCF_A 51 200 OK IBCF_A forwards 200 OK response to IBCF_B 52 200 OK IBCF_B forwards 200 OK response to IMS_B 53 200 OK IMS_B forwards 200 OK response to AS/IM_B 54 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 55 200 OK IMS_B forwards 200 OK response to UE_D 56 NOTIFY AS/IM_A sends NOTIFY to UE_D with list of 1-to-many Chat participants 57 NOTIFY IMS_A forwards BYE to IBCF_A 58 NOTIFY IBCF_A forwards BYE to IBCF_B 59 NOTIFY IBCF_B forwards BYE to IMS_B 60 NOTIFY IMS_B forwards BYE to AS/IM_B 61 NOTIFY AS/IM_B returns, possibly modified, BYE to IMS_B 62 NOTIFY IMS_B forwards BYE to UE_D 63 User D is notified with list of 1-to- many Chat participants 64 200 OK UE_D sends 200 OK for NOTIFY 65 200 OK IMS_B forwards 200 OK response to AS/IM_B 66 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 67 200 OK IMS_B forwards 200 OK response to IBCF_B 68 200 OK IBCF_B forwards 200 OK response to IBCF_A 69 200 OK IBCF_A forwards 200 OK response to IMS_A 70 200 OK IMS_A forwards 200 OK response to AS/IM_A 71 Users perform messaging in the 1-to-many Chat (see clause 5.3.2.3 Chat 1 to many via MSRP to additional user - Interworking - CheckMSRP3) 72 User D leaves the 1-to-many Chat 73 BYE UE_D sends BYE to IMS_B to leave the 1-to-many Chat 74 BYE IMS_B forwards BYE to AS/IM_B 75 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 76 BYE IMS_B forwards BYE to IBCF_B 77 BYE IBCF_B forwards BYE to IBCF_A 78 BYE IBCF_A forwards BYE to IMS_A 79 BYE IMS_A forwards BYE to AS/IM_A 80 200 OK AS/IM_A sends 200 OK for BYE ETSI ETSI TS 102 901 V4.1.1 (2012-05) 159 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E D U s e r D 81 200 OK IMS_A forwards 200 OK response to IBCF_A 82 200 OK IBCF_A forwards 200 OK response to IBCF_B 83 200 OK IBCF_B forwards 200 OK response to IMS_B 84 200 OK IMS_B forwards 200 OK response to AS/IM_B 85 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 86 200 OK IMS_B forwards 200 OK response to UE_B 87 User D is informed that he has left the 1-to-many Chat 88 NOTIFY AS/IM_A sends NOTIFY to IMS _A to inform UE_A that User B has left the 1-to-many Chat 89 NOTIFY IMS_A forwards the NOTIFY to UE_A 90 User A is notified that User D has left the 1-to-many Chat 91 200 OK UE_A responds with 200 OK to IMS_A 92 200 OK IMS_A forwards the 200 OK response to AS/IM_A 93 Continue UC_RCS_6_I (80A- 116B) 4.5.3.7.2 Adding participants to an already established 1-to-many chat session - roaming (optional) Interoperability Test Description Identifier: TD_IMS_CHAT_0016 Summary: IMS network supports 1-to-many IM/Chat service and messages exchange between two users, one user in its home network and one user roaming can be performed. User A invites User D to an already established 1-to-many Chat Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Use Case ref.: UC_RCS_6_R & UC_MSRP_04 Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A, UE_C, UE_D and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A and UE_D are registered in IMS_A optionally using userPRES according to table 1 • UE_A, UE_B and UE_C shall support MSRP • UE_B and UE_C are registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B and UE_C • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 160 Interoperability Test Description • UE_A, UE_C, UE_D and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B initiates a 1-to-many Chat with User A and User C by sending initial message 2 User B is informed that the 1-to-many Chat is established 3 User A is informed of incoming invitation from User B to join the 1-to-many Chat 4 User A reads the initial message and accepts the 1-to-many Chat invitation 5 User B is notified with list of 1-to-many Chat participants 6 User A is notified with list of 1-to-many Chat participants 7 Users perform messaging in the 1-to-many Chat 8 User B invites User D to join 1-to-many Chat 9 User D is informed of incoming invitation from User B to join the 1-to-many Chat 10 User D reads the initial message and accepts the 1-to-many Chat invitation 11 User B is notified with list of 1-to-many Chat participants 12 User D is notified with list of 1-to-many Chat participants 13 Users perform messaging in the 1-to-many Chat 14 User D leaves the 1-to-many Chat 15 User D is informed that he has left the 1-to-many Chat 16 User B is notified that user D has left the 1-to-many Chat 17A User A leaves the 1-to-many Chat 17B User B leaves the 1-to-many Chat 18A User A is informed that he has left the 1-to-many Chat 18B User B is informed that he has left the 1-to-many Chat 19A User B is notified that all other users have left the 1-to-many Chat 19B User A is notified that all other users have left the 1-to-many Chat 20A User B leaves the 1-to-many Chat 20B User A leaves the 1-to-many Chat 21A User B is informed that the 1-to-many Chat has ended 21B User A is informed that the 1-to-many Chat has ended Conformance Criteria: Check 1 TP_IMS_5107_03 in CFW step 56 (CANCEL): ensure that { when { UE_A sends CANCEL to UE_B } then { IMS_B receives the CANCEL not containing Route_header indicating the S-CSCF_SIP_URI of IMS_A } } Step Direction Message Comment U s e r D U E D A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_6_R (1- 2 User B invites User D to join 1-to- many Chat 3 REFER UE_B sends REFER message to IMS_A, with IM session identity (allocated for the current 1-to-many chat), Refer-To header value equals to UE_D URI and Refer-Sub header value set to "false" 4 INVITE IMS_A forwards INVITE to IBCF_A 5 INVITE IBCF_A forwards INVITE to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 161 Step Direction Message Comment U s e r D U E D A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 6 INVITE IBCF_B forwards INVITE to IMS_B 7 INVITE IMS_B forwards INVITE to AS/IM_B 8 200 OK AS/IM_B responds with 200 OK to IMS_B 9 200 OK IMS_B forwards 200 OK response to IBCF_B 10 200 OK IBCF_B forwards 200 OK response to IBCF_A 11 200 OK IBCF_A forwards 200 OK response to IMS_A 12 200 OK IMS_A forwards 200 OK response to UE_B 13 INVITE AS/IM_B sends INVITE to UE_D with IM session identity (allocated for the current 1-to-many Chat) and IM address of the Inviting IM UE (UE_D) 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to IBCF_B 16 100 Trying IBCF_B responds with a 100 Trying provisional response 17 INVITE IBCF_B forwards INVITE to IBCF_A 18 100 Trying IBCF_A responds with a 100 Trying provisional response 19 INVITE IBCF_A forwards INVITE to IMS_A 20 100 Trying IMS_A responds with a 100 Trying provisional response 21 INVITE IMS_A forwards INVITE to AS/IM_A 22 100 Trying AS/IM_A responds with a 100 Trying provisional response 23 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 24 100 Trying IMS_A responds with a 100 Trying provisional response 25 INVITE IMS_A forwards INVITE to UE_D 26 100 Trying UE_D optionally responds with a 100 Trying provisional response 27 User D is informed of incoming invitation from User B to join the 1- to-many Chat 28 User D reads the initial message and accepts the 1-to-many Chat invitation 29 200 OK UE_D responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform AS/IM_A with specific data for MSRP connection set up 30 200 OK IMS_A forwards 200 OK response to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 162 Step Direction Message Comment U s e r D U E D A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 31 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 32 200 OK IMS_A forwards 200 OK response to IBCF_A 33 200 OK IBCF_A forwards 200 OK response to IBCF_B 34 200 OK IBCF_B forwards 200 OK response to IMS_B 35 200 OK IMS_B forwards 200 OK response to AS/IM_B 36 ACK AS/IM_B acknowledges the receipt of 200 OK for INVITE 37 ACK IMS_B forwards ACK to IBCF_B 38 ACK IBCF_B forwards ACK to IBCF_A 39 ACK IBCF_A forwards ACK to IMS_A 40 ACK IMS_A forwards ACK to AS/IM_A 41 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 42 ACK IMS_A forwards ACK to UE_D 43 NOTIFY AS/IM_B sends NOTIFY to UE_B with list of 1-to-many Chat participants 44 NOTIFY IMS_B forwards NOTIFY to IBCF_B 45 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 46 NOTIFY IBCF_A forwards NOTIFY to IMS_A 47 NOTIFY IMS_A forwards NOTIFY to UE_B 48 User B is notified with list of 1-to- many Chat participants 49 200 OK UE_B responds with 200 OK to IMS_A 50 200 OK IMS_A forwards 200 OK response to IBCF_A 51 200 OK IBCF_A forwards 200 OK response to IBCF_B 52 200 OK IBCF_B forwards 200 OK response to IMS_B 53 200 OK IMS_B forwards 200 OK response to AS/IM_B 54 SUBSCRIBE UE_D subscribes to the conference event package 55 SUBSCRIBE IMS_A forwards SUBSCRIBE to AS/IM_A 56 SUBSCRIBE AS/IM_A returns, possibly modified, SUBSCRIBE to IMS_A 57 SUBSCRIBE IMS_A forwards SUBSCRIBE to IBCF_A 58 SUBSCRIBE IBCF_A forwards SUBSCRIBE to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 163 Step Direction Message Comment U s e r D U E D A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 59 SUBSCRIBE IBCF_B forwards SUBSCRIBE to IMS_B 60 SUBSCRIBE IMS_B forwards SUBSCRIBE to AS/IM_B 61 200 OK AS/IM_B sends 200 OK for SUBSCRIBE 62 200 OK IMS_B forwards 200 OK response to IBCF_B 63 200 OK IBCF_B forwards 200 OK response to IBCF_A 64 200 OK IBCF_A forwards 200 OK response to IMS_A 65 200 OK IMS_A forwards 200 OK response to AS/IM_A 66 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 67 200 OK IMS_A forwards 200 OK response to UE_D 68 NOTIFY AS/IM_B sends NOTIFY to UE_D with list of 1-to-many Chat participants 69 NOTIFY IMS_B forwards BYE to IBCF_B 70 NOTIFY IBCF_B forwards BYE to IBCF_A 71 NOTIFY IBCF_A forwards BYE to IMS_A 72 NOTIFY IMS_A forwards BYE to AS/IM_A 73 NOTIFY AS/IM_A returns, possibly modified, BYE to IMS_A 74 NOTIFY IMS_A forwards BYE to UE_D 75 User D is notified with list of 1-to- many Chat participants 76 200 OK UE_D sends 200 OK for NOTIFY 77 200 OK IMS_A forwards 200 OK response to AS/IM_A 78 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 79 200 OK IMS_A forwards 200 OK response to IBCF_A 80 200 OK IBCF_A forwards 200 OK response to IBCF_B 81 200 OK IBCF_B forwards 200 OK response to IMS_B 82 200 OK IMS_B forwards 200 OK response to AS/IM_B 83 Users perform messaging in the 1- to-many Chat (see clause 5.3.2.4 Chat 1 to many via MSRP to additional user - Roaming) 84 User D leaves the 1-to-many Chat ETSI ETSI TS 102 901 V4.1.1 (2012-05) 164 Step Direction Message Comment U s e r D U E D A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 85 BYE UE_D sends BYE to IMS_A to leave the 1-to-many Chat 86 BYE IMS_A forwards BYE to AS/IM_A 87 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 88 BYE IMS_A forwards BYE to IBCF_A 89 BYE IBCF_A forwards BYE to IBCF_B 90 BYE IBCF_B forwards BYE to IMS_B 91 BYE IMS_B forwards BYE to AS/IM_B 92 200 OK AS/IM_B sends 200 OK for BYE 93 200 OK IMS_B forwards 200 OK response to IBCF_B 94 200 OK IBCF_B forwards 200 OK response to IBCF_A 95 200 OK IBCF_A forwards 200 OK response to IMS_A 96 200 OK IMS_A forwards 200 OK response to AS/IM_A 97 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 98 200 OK IMS_A forwards 200 OK response to UE_D 99 User D is informed that he has left the 1-to-many Chat 100 NOTIFY AS/IM_B sends NOTIFY to IMS _B to inform UE_B that User D has left the 1-to-many Chat 101 NOTIFY IMS_B forwards NOTIFY to IBCF_B 102 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 103 NOTIFY IBCF_A forwards NOTIFY to IMS_A 104 NOTIFY IMS_A forwards NOTIFY to UE_B 105 User B is notified that user D has left the 1-to-many Chat 106 200 OK UE_B responds with 200 OK to IMS_A 107 200 OK IMS_A forwards 200 OK response to IBCF_A 108 200 OK IBCF_A forwards 200 OK response to IBCF_B 109 200 OK IBCF_B forwards 200 OK response to IMS_B 110 200 OK IMS_B forwards 200 OK response to AS/IM_B 111 Continue UC_RCS_6_R (104A- 146B) ETSI ETSI TS 102 901 V4.1.1 (2012-05) 165
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4 RCS-e services during a call
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.1 Video sharing
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.1.1 Video sharing- interworking	Interoperability Test Description Identifier: TD_IMS_SHARE_0001 Summary: IMS network supports Video sharing service and messages exchange between two users in their networks can be performed. User A starts video sharing with User B during a voice call Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (1st numbered list) TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶89 (4th numbered list) Use Case ref.: UC_RCS_8_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A establishes voice call with user B 1B User B establishes voice call with user A 2 User A requests to share video with user B 3 User B is requested to accept to share video 4 User B accepts to share video with user A 5 User A is informed that request has been answered 6 Video sharing starts 7A User A ends video sharing 8A User B is informed that video sharing has terminated 9A User A is informed that video sharing has terminated 10A User A initiates voice call termination 7B User B ends video sharing 8B User A is informed that video sharing has terminated 9B User B is informed that video sharing has terminated 10B User B initiates voice call termination ETSI ETSI TS 102 901 V4.1.1 (2012-05) 166 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 15 (INVITE): ensure that { when { UE_A sends an initial INVITE to UE_B } then { IMS_B receives the initial INVITE not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A containing a P-Charging-Vector_header (containing an icid-value_parameter and containing a orig-ioi_parameter indicating IMS_A and not containing an access-network-charging-info_parameter and not containing a term-ioi_parameter) and containing a Record-Route_header indicating the originating S-CSCF_SIP_URI } } 2 TP_IMS_5108_03 in CFW step 19 (INVITE) ensure that { when { IMS_B receives an initial INVITE from IMS_A addressed_to UE_B } then { IMS_B sends the initial INVITE to AS_B containing a topmost Route_header indicating the SIP_URI of AS_B and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter } } 3 TP_IMS_5115_08 in CFW step 31 (200 OK) ensure that { when { IMS_B receives 200_response from AS_B addressed_to UE_A } then { IMS_B sends the 200_response to IMS_A containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and including a term-ioi_parameter indicating operator_identifier of IMS_BIUT_ } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share video with user B 3 INVITE UE_A sends INVITE to share video with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to UE_B 12 100 Trying UE_B responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 167 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 13 User B is requested to accept to share video 14 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 15 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 16 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 17 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User B accepts to share video 20 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 21 200 OK IMS_B forwards 200 OK response to IBCF_B 22 200 OK IBCF_B forwards 200 OK response to IBCF_A 23 200 OK IBCF_A forwards 200 OK response to IMS_A 24 200 OK IMS_A forwards 200 OK response to UE_A 25 User A is informed that request has been answered 26 ACK UE_A acknowledges the receipt of 200 OK for INVITE 27 ACK IMS_A forwards ACK to IBCF_A 28 ACK IBCF_A forwards ACK to IBCF_B 29 ACK IBCF_B forwards ACK to IMS_B 30 ACK IMS_B forwards ACK to UE_B 31 Video sharing starts 32A User A ends video sharing 33A BYE UE_A releases the call with BYE 34A BYE IMS_A forwards BYE to IBCF_A 35A BYE IBCF_A forwards BYE to IBCF_B 36A BYE IBCF_B forwards BYE to IMS_B 37A BYE IMS_B forwards BYE to UE_B 38A User B is informed that video sharing has ended 39A 200 OK UE_B sends 200 OK for BYE 40A 200 OK IMS_B forwards 200 OK response to IBCF_B 41A 200 OK IBCF_B forwards 200 OK response to IBCF_A 42A 200 OK IBCF_A forwards 200 OK response to IMS_A 43A 200 OK IMS_A forwards the 200 OK response to UE_A 44A User A is informed that video sharing has ended 45A OPTIONS UE_B sends OPTIONS to IMS_B to verify availability of video sharing capability of the UE_A 46A OPTIONS IMS_B forwards OPTIONS to IBCF_B 47A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 48A OPTIONS IBCF_A forwards OPTIONS to IMS_A 49A OPTIONS IMS_A forwards OPTIONS to UE_A 50A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 51A 200 OK IMS_A forwards 200 OK to IBCF_A 52A 200 OK IBCF_A forwards 200 OK to IBCF_B 53A 200 OK IBCF_B forwards 200 OK to IMS_B 54A 200 OK IMS_B forwards 200 OK to UE_B 55A Voice call termination initiated by user A 32B User B ends video sharing ETSI ETSI TS 102 901 V4.1.1 (2012-05) 168 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 33B BYE UE_B releases the call with BYE 34B BYE IMS_B forwards BYE to IBCF_B 35B BYE IBCF_B forwards BYE to IBCF_A 36B BYE IBCF_A forwards BYE to IMS_A 37B BYE IMS_A forwards BYE to UE_A 38B User A is informed that video sharing has ended 39B 200 OK UE_A sends 200 OK for BYE 40B 200 OK IMS_A forwards 200 OK response to IBCF_A 41B 200 OK IBCF_A forwards 200 OK response to IBCF_B 42B 200 OK IBCF_B forwards 200 OK response to IMS_B 43B 200 OK IMS_B forwards the 200 OK response to UE_B 44B User B is informed that video sharing has ended 45B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_B 46B OPTIONS IMS_A forwards OPTIONS to IBCF_A 47B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 48B OPTIONS IBCF_B forwards OPTIONS to IMS_B 49B OPTIONS IMS_B forwards OPTIONS to UE_B 50B 200 OK UE_B responds with 200 OK to IMS_B with updated capabilities 51B 200 OK IMS_B forwards 200 OK to IBCF_B 52B 200 OK IBCF_B forwards 200 OK to IBCF_A 53B 200 OK IBCF_A forwards 200 OK to IMS_A 54B 200 OK IMS_A forwards 200 OK to UE_A 55B Voice call termination initiated by user B
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.1.2 Video sharing- roaming (optional)	Interoperability Test Description Identifier: TD_IMS_SHARE_0002 Summary: IMS network supports Video sharing service and messages exchange between two users, one user in its home network and one user roaming can be performed. User A starts video sharing with User B during a voice call Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ¶1 (1st numbered list) TP_IMS_5110_01 TS 124 229 [1], clause 5.4.3.3 ¶79 (after 6th dashed list) Use Case ref.: UC_RCS_8_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization ETSI ETSI TS 102 901 V4.1.1 (2012-05) 169 Interoperability Test Description • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A establishes voice call with user B 1B User B establishes voice call with user A 2 User A requests to share video with user B 3 User B is requested to accept to share video 4 User B accepts to share video with user A 5 User A is informed that request has been answered 6 Video sharing starts 7A User A ends video sharing 8A User B is informed that video sharing has terminated 9A User A is informed that video sharing has terminated 10A User A initiates voice call termination 7B User B ends video sharing 8B User A is informed that video sharing has terminated 9B User B is informed that video sharing has terminated 10B User B initiates voice call termination Conformance Criteria: Check 1 TP_IMS_5046_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a Route_header not indicating the P-CSCF_SIP_URI of IMS_A and containing a Route_header indicating the "list of Service Route header URIs from the registration" and containing an additional Via_header containing ( the P-CSCF_via_port_number and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and containing an additional topmost Record-Route_header indicating (the P-CSCF_port_number 'where it awaits subsequent requests' from UE_A and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and not containing P-Preferred-Identity_header and containing a P-Asserted-Identity_header containing an address of UE_B and containing a P-Charging-Vector_header containing an icid-value_parameter } } 2 TP_IMS_5110_01 in CFW step 43 (200 OK) ensure that { when { IMS_A receives a 200_response from AS_A addressed_to UE_B } then { IMS_A sends the 200_response to IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share video with user B 3 INVITE UE_A sends INVITE to share video with user B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 170 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IBCF_A 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IMS_A 16 100 Trying IMS_A responds with a 100 Trying provisional response 17 INVITE IMS_A forwards INVITE to UE_B 18 100 Trying UE_B responds with a 100 Trying provisional response 19 User B is requested to accept to share video 20 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 21 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 22 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 23 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 24 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 27 180 Ringing IMS_A forwards 180 Ringing response to UE_A 28 User B accepts to share video 29 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 30 200 OK IMS_A forwards 200 OK response to IBCF_A 31 200 OK IBCF_A forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IMS_B 33 200 OK IMS_B forwards 200 OK response to IBCF_B 34 200 OK IBCF_B forwards 200 OK response to IBCF_A 35 200 OK IBCF_A forwards 200 OK response to IMS_A 36 IMS_A forwards 200 OK response to UE_A 37 User A is informed that request has been answered 38 ACK UE_A acknowledges the receipt of 200 OK for INVITE 39 ACK IMS_A forwards ACK to IBCF_A 40 ACK IBCF_A forwards ACK to IBCF_B 41 ACK IBCF_B forwards ACK to IMS_B 42 ACK IMS_B forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 171 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 44 ACK IBCF_A forwards ACK to IMS_A 45 ACK IMS_A forwards ACK to UE_B 46 Video sharing starts 47A User A ends video sharing 48A BYE UE_A releases the call with BYE 49A BYE IMS_A forwards BYE to IBCF_A 50A BYE IBCF_A forwards BYE to IBCF_B 51A BYE IBCF_B forwards BYE to IMS_B 52A BYE IMS_B forwards BYE to IBCF_B 53A BYE IBCF_B forwards BYE to IBCF_A 54A BYE IBCF_A forwards BYE to IMS_A 55A BYE IMS_A forwards BYE to UE_B 56A User B is informed that video sharing has ended 57A 200 OK UE_B sends 200 OK for BYE 58A 200 OK IMS_A forwards 200 OK response to IBCF_A 59A 200 OK IBCF_A forwards 200 OK response to IBCF_B 60A 200 OK IBCF_B forwards 200 OK response to IMS_B 61A 200 OK IMS_B forwards the 200 OK response to IBCF_B 62A 200 OK IBCF_B forwards 200 OK response to IBCF_A 63A 200 OK IBCF_A forwards 200 OK response to IMS_A 64A 200 OK IMS_A forwards the 200 OK response to UE_A 65A Video sharing terminates 66A OPTIONS UE_B sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_A 67A OPTIONS IMS_A forwards OPTIONS to IBCF_A 68A OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69A OPTIONS IBCF_B forwards OPTIONS to IMS_B 70A OPTIONS IMS_B forwards OPTIONS to IBCF_B 71A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 72A OPTIONS IBCF_A forwards OPTIONS to IMS_A 73A OPTIONS IMS_A forwards OPTIONS to UE_A 74A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 75A 200 OK IMS_A forwards 200 OK to IBCF_A 76A 200 OK IBCF_A forwards 200 OK to IBCF_B 77A 200 OK IBCF_B forwards 200 OK to IMS_B 78A 200 OK IMS_B forwards 200 OK to IBCF_B 79A 200 OK IBCF_B forwards 200 OK to IBCF_A 80A 200 OK IBCF_A forwards 200 OK to IMS_A 81A 200 OK IMS_A forwards 200 OK to UE_B 82A User A terminates voice call 47B User B ends video sharing 48B BYE UE_B releases the call with BYE 49B BYE IMS_A forwards BYE to IBCF_A 50B BYE IBCF_A forwards BYE to IBCF_B 51B BYE IBCF_B forwards BYE to IMS_B 52B BYE IMS_B forwards BYE to IBCF_B 53B BYE IBCF_B forwards BYE to IBCF_A 54B BYE IBCF_A forwards BYE to IMS_A 55B BYE IMS_A forwards BYE to UE_A 56B User A is informed that video sharing has ended 57B 200 OK UE_A sends 200 OK for BYE 58B 200 OK IMS_A forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 172 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 59B 200 OK IBCF_A forwards 200 OK response to IBCF_B 60B 200 OK IBCF_B forwards 200 OK response to IMS_B 61B 200 OK IMS_B forwards 200 OK response to IBCF_B 62B 200 OK IBCF_B forwards 200 OK response to IBCF_A 63B 200 OK IBCF_A forwards 200 OK response to IMS_A 64B 200 OK IMS_A forwards the 200 OK response to UE_B 65B Video sharing terminates 66B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_B 67B OPTIONS IMS_A forwards OPTIONS to IBCF_A 68B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69B OPTIONS IBCF_B forwards OPTIONS to IMS_B 70B OPTIONS IMS_B forwards OPTIONS to IBCF_B 71B OPTIONS IBCF_B forwards OPTIONS to IBCF_A 72B OPTIONS IBCF_A forwards OPTIONS to IMS_A 73B OPTIONS IMS_A forwards OPTIONS to UE_B 74B 200 OK UE_B responds with 200 OK to IMS_A with updated capabilities 75B 200 OK IMS_A forwards 200 OK to IBCF_A 76B 200 OK IBCF_A forwards 200 OK to IBCF_B 77B 200 OK IBCF_B forwards 200 OK to IMS_B 78B 200 OK IMS_B forwards 200 OK to IBCF_B 79B 200 OK IBCF_B forwards 200 OK to IBCF_A 80B 200 OK IBCF_A forwards 200 OK to IMS_A 81B 200 OK IMS_A forwards 200 OK to UE_A 82B User B terminates voice call
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.2 Video sharing rejection
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.2.1 Video sharing rejection - interworking	Interoperability Test Description Identifier: TD_IMS_SHARE_0003 Summary: IMS network supports Video sharing service and messages exchange between two users in their networks can be performed. User A starts video sharing with User B during a voice call, but user B rejects the invitation Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) Use Case ref.: UC_RCS_8_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization ETSI ETSI TS 102 901 V4.1.1 (2012-05) 173 Interoperability Test Description • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A invites user B to 1-to-1 chat session 2 User B automatically accepts 1-to-1 chat invitation 3 Verify that Users perform chatting 4 User A initiates an Ad-hoc IM conference with user B 5 Verify that User A is informed that the Ad Hoc IM Conference is established 6 Verify that User B is informed of incoming invitation from User A to join the Ad-hoc IM Conference 7 User B joins the Ad-hoc IM Conference (automatically) 8 Verify that User A is notified that User B has joined the Ad-hoc IM Conference 9 Verify that User A informed that 1-to-1 chat session with user B has ended 10 Verify that User B informed that 1-to-1 chat session with user A has ended 11 Verify that Users perform IM/chat service in the Ad-hoc IM Conference 12 User B leaves the Ad-hoc IM Conference 13 Verify that User B is informed that the Ad-hoc IM Conference has ended 14 Verify that User A is notified that user B has left the Ad-hoc IM Conference 15 User A leaves the Ad-hoc IM Conference 16 Verify that User A is informed that the Ad-hoc IM Conference has ended Conformance Criteria: Check 1 TP_IMS_5108_03 in CFW step 58 (INVITE) ensure that { when { IMS_B receives an initial INVITE from IMS_A addressed_to UE_B } then { IMS_B sends the initial INVITE to AS_B containing a topmost Route_header indicating the SIP_URI of AS_B and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share video with user B 3 INVITE UE_A sends INVITE to share video with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 174 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 12 100 Trying UE_B responds with a 100 Trying provisional response 13 User B is requested to accept to share video 14 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 15 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 16 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 17 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User B accepts to share video 20 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 21 200 OK IMS_B forwards 200 OK response to IBCF_B 22 200 OK IBCF_B forwards 200 OK response to IBCF_A 23 200 OK IBCF_A forwards 200 OK response to IMS_A 24 200 OK IMS_A forwards 200 OK response to UE_A 25 User A is informed that request has been answered 26 ACK UE_A acknowledges the receipt of 200 OK for INVITE 27 ACK IMS_A forwards ACK to IBCF_A 28 ACK IBCF_A forwards ACK to IBCF_B 29 ACK IBCF_B forwards ACK to IMS_B 30 ACK IMS_B forwards ACK to UE_B 31 Video sharing starts 32A User A ends video sharing 33A BYE UE_A releases the call with BYE 34A BYE IMS_A forwards BYE to IBCF_A 35A BYE IBCF_A forwards BYE to IBCF_B 36A BYE IBCF_B forwards BYE to IMS_B 37A BYE IMS_B forwards BYE to UE_B 38A User B is informed that video sharing has ended 39A 200 OK UE_B sends 200 OK for BYE 40A 200 OK IMS_B forwards 200 OK response to IBCF_B 41A 200 OK IBCF_B forwards 200 OK response to IBCF_A 42A 200 OK IBCF_A forwards 200 OK response to IMS_A 43A 200 OK IMS_A forwards the 200 OK response to UE_A 44A User A is informed that video sharing has ended 45A OPTIONS UE_B sends OPTIONS to IMS_B to verify availability of video sharing capability of the UE_A 46A OPTIONS IMS_B forwards OPTIONS to IBCF_B 47A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 48A OPTIONS IBCF_A forwards OPTIONS to IMS_A 49A OPTIONS IMS_A forwards OPTIONS to UE_A 50A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 51A 200 OK IMS_A forwards 200 OK to IBCF_A 52A 200 OK IBCF_A forwards 200 OK to IBCF_B 53A 200 OK IBCF_B forwards 200 OK to IMS_B 54A 200 OK IMS_B forwards 200 OK to UE_B 55A Voice call termination initiated by user A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 175 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 32B User B ends video sharing 33B BYE UE_B releases the call with BYE 34B BYE IMS_B forwards BYE to IBCF_B 35B BYE IBCF_B forwards BYE to IBCF_A 36B BYE IBCF_A forwards BYE to IMS_A 37B BYE IMS_A forwards BYE to UE_A 38B User A is informed that video sharing has ended 39B 200 OK UE_A sends 200 OK for BYE 40B 200 OK IMS_A forwards 200 OK response to IBCF_A 41B 200 OK IBCF_A forwards 200 OK response to IBCF_B 42B 200 OK IBCF_B forwards 200 OK response to IMS_B 43B 200 OK IMS_B forwards the 200 OK response to UE_B 44B User B is informed that video sharing has ended 45B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_B 46B OPTIONS IMS_A forwards OPTIONS to IBCF_A 47B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 48B OPTIONS IBCF_B forwards OPTIONS to IMS_B 49B OPTIONS IMS_B forwards OPTIONS to UE_B 50B 200 OK UE_B responds with 200 OK to IMS_B with updated capabilities 51B 200 OK IMS_B forwards 200 OK to IBCF_B 52B 200 OK IBCF_B forwards 200 OK to IBCF_A 53B 200 OK IBCF_A forwards 200 OK to IMS_A 54B 200 OK IMS_A forwards 200 OK to UE_A 55B Voice call termination initiated by user B
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.2.2 Video sharing rejection - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_SHARE_0004 Summary: IMS network supports Video sharing service and messages exchange between two users, one user in its home network and one user roaming can be performed. User A starts video sharing with User B during a voice call, but user B rejects the invitation Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5070_01 TS 124 229 [1], clause 5.2.7.3 ¶3 Use Case ref.: UC_RCS_8_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding ETSI ETSI TS 102 901 V4.1.1 (2012-05) 176 Interoperability Test Description Test Sequence: Step 1 User B invites user A to 1-to-1 chat session 2 User A automatically accepts 1-to-1 chat invitation 3 Verify that Users perform chatting 4 User B initiates an Ad-hoc IM conference with user A 5 Verify that User B is informed that the Ad Hoc IM Conference is established 6 Verify that User A is informed of incoming invitation from User B to join the Ad-hoc IM Conference 7 User A joins the Ad-hoc IM Conference (automatically) 8 Verify that User B is notified that User A has joined the Ad-hoc IM Conference 9 Verify that User B informed that 1-to-1 chat session with user A has ended 10 Verify that User A informed that 1-to-1 chat session with user B has ended 11 Verify that Users perform IM/chat service in the Ad-hoc IM Conference 12 User A leaves the Ad-hoc IM Conference 13 Verify that User A is informed that the Ad-hoc IM Conference has ended 14 Verify that User B is notified that user A has left the Ad-hoc IM Conference 15 User B leaves the Ad-hoc IM Conference 16 Verify that User B is informed that the Ad-hoc IM Conference has ended Conformance Criteria: Check 1 TP_IMS_5070_01 in CFW step 79 (100 Trying) ensure that { when { IMS_A receives an initial INVITE from IMS_B } then { IMS_A sends a 100_response to IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share video with user B 3 INVITE UE_A sends INVITE to share video with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 177 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IMS_A 16 100 Trying IMS_A responds with a 100 Trying provisional response 17 INVITE IMS_A forwards INVITE to UE_B 18 100 Trying UE_B responds with a 100 Trying provisional response 19 User B is requested to accept to share video 20 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 21 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 22 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 23 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 24 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 27 180 Ringing IMS_A forwards 180 Ringing response to UE_A 28 User B accepts to share video 29 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 30 200 OK IMS_A forwards 200 OK response to IBCF_A 31 200 OK IBCF_A forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IMS_B 33 200 OK IMS_B forwards 200 OK response to IBCF_B 34 200 OK IBCF_B forwards 200 OK response to IBCF_A 35 200 OK IBCF_A forwards 200 OK response to IMS_A 36 IMS_A forwards 200 OK response to UE_A 37 User A is informed that request has been answered 38 ACK UE_A acknowledges the receipt of 200 OK for INVITE 39 ACK IMS_A forwards ACK to IBCF_A 40 ACK IBCF_A forwards ACK to IBCF_B 41 ACK IBCF_B forwards ACK to IMS_B 42 ACK IMS_B forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 178 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 44 ACK IBCF_A forwards ACK to IMS_A 45 ACK IMS_A forwards ACK to UE_B 46 Video sharing starts 47A User A ends video sharing 48A BYE UE_A releases the call with BYE 49A BYE IMS_A forwards BYE to IBCF_A 50A BYE IBCF_A forwards BYE to IBCF_B 51A BYE IBCF_B forwards BYE to IMS_B 52A BYE IMS_B forwards BYE to IBCF_B 53A BYE IBCF_B forwards BYE to IBCF_A 54A BYE IBCF_A forwards BYE to IMS_A 55A BYE IMS_A forwards BYE to UE_B 56A User B is informed that video sharing has ended 57A 200 OK UE_B sends 200 OK for BYE 58A 200 OK IMS_A forwards 200 OK response to IBCF_A 59A 200 OK IBCF_A forwards 200 OK response to IBCF_B 60A 200 OK IBCF_B forwards 200 OK response to IMS_B 61A 200 OK IMS_B forwards the 200 OK response to IBCF_B 62A 200 OK IBCF_B forwards 200 OK response to IBCF_A 63A 200 OK IBCF_A forwards 200 OK response to IMS_A 64A 200 OK IMS_A forwards the 200 OK response to UE_A 65A Video sharing terminates 66A OPTIONS UE_B sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_A 67A OPTIONS IMS_A forwards OPTIONS to IBCF_A 68A OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69A OPTIONS IBCF_B forwards OPTIONS to IMS_B 70A OPTIONS IMS_B forwards OPTIONS to IBCF_B 71A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 72A OPTIONS IBCF_A forwards OPTIONS to IMS_A 73A OPTIONS IMS_A forwards OPTIONS to UE_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 179 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 74A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 75A 200 OK IMS_A forwards 200 OK to IBCF_A 76A 200 OK IBCF_A forwards 200 OK to IBCF_B 77A 200 OK IBCF_B forwards 200 OK to IMS_B 78A 200 OK IMS_B forwards 200 OK to IBCF_B 79A 200 OK IBCF_B forwards 200 OK to IBCF_A 80A 200 OK IBCF_A forwards 200 OK to IMS_A 81A 200 OK IMS_A forwards 200 OK to UE_B 82A User A terminates voice call 47B User B ends video sharing 48B BYE UE_B releases the call with BYE 49B BYE IMS_A forwards BYE to IBCF_A 50B BYE IBCF_A forwards BYE to IBCF_B 51B BYE IBCF_B forwards BYE to IMS_B 52B BYE IMS_B forwards BYE to IBCF_B 53B BYE IBCF_B forwards BYE to IBCF_A 54B BYE IBCF_A forwards BYE to IMS_A 55B BYE IMS_A forwards BYE to UE_A 56B User A is informed that video sharing has ended 57B 200 OK UE_A sends 200 OK for BYE 58B 200 OK IMS_A forwards 200 OK response to IBCF_A 59B 200 OK IBCF_A forwards 200 OK response to IBCF_B 60B 200 OK IBCF_B forwards 200 OK response to IMS_B 61B 200 OK IMS_B forwards 200 OK response to IBCF_B 62B 200 OK IBCF_B forwards 200 OK response to IBCF_A 63B 200 OK IBCF_A forwards 200 OK response to IMS_A 64B 200 OK IMS_A forwards the 200 OK response to UE_B 65B Video sharing terminates 66B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of video sharing capability of the UE_B 67B OPTIONS IMS_A forwards OPTIONS to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 180 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 68B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69B OPTIONS IBCF_B forwards OPTIONS to IMS_B 70B OPTIONS IMS_B forwards OPTIONS to IBCF_B 71B OPTIONS IBCF_B forwards OPTIONS to IBCF_A 72B OPTIONS IBCF_A forwards OPTIONS to IMS_A 73B OPTIONS IMS_A forwards OPTIONS to UE_B 74B 200 OK UE_B responds with 200 OK to IMS_A with updated capabilities 75B 200 OK IMS_A forwards 200 OK to IBCF_A 76B 200 OK IBCF_A forwards 200 OK to IBCF_B 77B 200 OK IBCF_B forwards 200 OK to IMS_B 78B 200 OK IMS_B forwards 200 OK to IBCF_B 79B 200 OK IBCF_B forwards 200 OK to IBCF_A 80B 200 OK IBCF_A forwards 200 OK to IMS_A 81B 200 OK IMS_A forwards 200 OK to UE_A 82B User B terminates voice call
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.3 Pictures sharing
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.3.1 Pictures sharing- interworking	Interoperability Test Description Identifier: TD_IMS_SHARE_0005 Summary: IMS network supports Picture sharing service and messages exchange between two users in their networks can be performed. User A starts video sharing with User B during a voice call Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5115_02 TS 124 229 [1], clause 5.4.3.3 ¶91 (item 2 in 4th numbered list) TP_IMS_5115_04 TS 124 229 [1], clause 5.4.3.3 ¶92 (item 2 in 4th numbered list) Use Case ref.: UC_RCS_8_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 181 Interoperability Test Description • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share picture with user B 3 User B is requested to accept to share picture 4 User B accepts to share picture 5 User A is informed that request has been answered 6 Picture sharing starts 7 Picture transfer completed (size checked) 8 User B is informed that picture transfer has finished 9 User A is informed that picture transfer has finished 10A Voice call termination initiated by user A 10B Voice call termination initiated by user B Conformance Criteria: Check 1 TP_IMS_5115_02 in CFW step 72 (2xx): ensure that { when { UE_B sends a 2xx_response to UE_A } then { IMS_A receives the 2xx_response from IMS_B containing a P-Charging-Vector_header containing an orig-ioi_parameter indicating operator_identifier of IMS_A and containing a term-ioi_parameter indicating operator_identifier of IMS_B } 2 TP_IMS_5115_04 in CFW step 72 (2xx): ensure that { when { UE_B sends a 2xx_response to UE_A } then { IMS_A receives the 2xx_response from IMS_B containing a P-Asserted-Identity_header indicating the SIP_URI of UE_B and containing a P-Asserted-Identity_header indicating the Tel_URI of UE_B} } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share picture with user B 3 INVITE UE_A sends INVITE to share picture with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 182 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to UE_B 12 100 Trying UE_B responds with a 100 Trying provisional response 13 User B is requested to accept to share picture 14 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 15 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 16 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 17 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User B accepts to share picture 20 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 21 200 OK IMS_B forwards 200 OK response to IBCF_B 22 200 OK IBCF_B forwards 200 OK response to IBCF_A 23 200 OK IBCF_A forwards 200 OK response to IMS_A 24 200 OK IMS_A forwards 200 OK response to UE_A 25 User A is informed that request has been answered 26 ACK UE_A acknowledges the receipt of 200 OK for INVITE 27 ACK IMS_A forwards ACK to IBCF_A 28 ACK IBCF_A forwards ACK to IBCF_B 29 ACK IBCF_B forwards ACK to IMS_B 30 ACK IMS_B forwards ACK to UE_B 31 Picture sharing starts (see clause 5.3.3Image data via MSRP ) 32 Picture transfer completed (size checked) 33 BYE UE_A releases the call with BYE 34 BYE IMS_A forwards BYE to IBCF_A 35 BYE IBCF_A forwards BYE to IBCF_B 36 BYE IBCF_B forwards BYE to IMS_B 37 BYE IMS_B forwards BYE to UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 183 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 38 User B is informed that picture transfer has finished 39 200 OK UE_B sends 200 OK for BYE 40 200 OK IMS_B forwards 200 OK response to IBCF_B 41 200 OK IBCF_B forwards 200 OK response to IBCF_A 42 200 OK IBCF_A forwards 200 OK response to IMS_A 43 200 OK IMS_A forwards the 200 OK response to UE_A 44 User A is informed that picture transfer has finished 45A Voice call termination initiated by user A 45B Voice call termination initiated by user B
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.3.2 Pictures sharing- roaming (optional)	Interoperability Test Description Identifier: TD_IMS_SHARE_0006 Summary: IMS network supports Picture sharing service and messages exchange between two users, one user in its home network and one user roaming can be performed. User A starts video sharing with User B during a voice call Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5107_04 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Use Case ref.: UC_RCS_8_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share picture with user B 3 User B is requested to accept to share picture 4 User B accepts to share picture 5 User A is informed that request has been answered 6 Picture sharing starts 7 Picture transfer completed (size checked) ETSI ETSI TS 102 901 V4.1.1 (2012-05) 184 Interoperability Test Description 8 User B is informed that picture transfer has finished 9 User A is informed that picture transfer has finished 10A User A terminates voice call 10B User B terminates voice call Conformance Criteria: Check 1 TP_IMS_5107_04 in CFW in step 68 (REFER): ensure that { when { IUT receives a REFER from UE_B addressed_to UE_A } then { IUT sends the REFER to IMS_A not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share picture with user B 3 INVITE UE_A sends INVITE to share picture with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IBCF_A 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IMS_A 16 100 Trying IMS_A responds with a 100 Trying provisional response 17 INVITE IMS_A forwards INVITE to UE_B 18 100 Trying UE_B responds with a 100 Trying provisional response 19 User B is requested to accept to share picture 20 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 21 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 22 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 23 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 24 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 185 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 27 180 Ringing IMS_A forwards 180 Ringing response to UE_A 28 User B accepts to share picture 29 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 30 200 OK IMS_A forwards 200 OK response to IBCF_A 31 200 OK IBCF_A forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IMS_B 33 200 OK IMS_B forwards 200 OK response to IBCF_B 34 200 OK IBCF_B forwards 200 OK response to IBCF_A 35 200 OK IBCF_A forwards 200 OK response to IMS_A 36 IMS_A forwards 200 OK response to UE_A 37 User A is informed that request has been answered 38 ACK UE_A acknowledges the receipt of 200 OK for INVITE 39 ACK IMS_A forwards ACK to IBCF_A 40 ACK IBCF_A forwards ACK to IBCF_B 41 ACK IBCF_B forwards ACK to IMS_B 42 ACK IMS_B forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IBCF_A 44 ACK IBCF_A forwards ACK to IMS_A 45 ACK IMS_A forwards ACK to UE_B 46 Picture sharing starts (see clause 5.3.3Image data via MSRP ) 47 Picture transfer completed (size checked) 48 BYE UE_A releases the call with BYE 49 BYE IMS_A forwards BYE to IBCF_A 50 BYE IBCF_A forwards BYE to IBCF_B 51 BYE IBCF_B forwards BYE to IMS_B 52 BYE IMS_B forwards BYE to IBCF_B 53 BYE IBCF_B forwards BYE to IBCF_A 54 BYE IBCF_A forwards BYE to IMS_A 55 BYE IMS_A forwards BYE to UE_B 56 User B is informed that picture transfer has finished 57 200 OK UE_B sends 200 OK for BYE 58 200 OK IMS_A forwards 200 OK response to IBCF_A 59 200 OK IBCF_A forwards 200 OK response to IBCF_B 60 200 OK IBCF_B forwards 200 OK response to IMS_B 61 200 OK IMS_B forwards the 200 OK response to IBCF_B 62 200 OK IBCF_B forwards 200 OK response to IBCF_A 63 200 OK IBCF_A forwards 200 OK response to IMS_A 64 200 OK IMS_A forwards the 200 OK response to UE_A 65 User A is informed that picture transfer has finished 66A User A terminates voice call 66B User B terminates voice call ETSI ETSI TS 102 901 V4.1.1 (2012-05) 186
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.4 Pictures sharing rejection
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.4.1 Pictures sharing rejection - interworking	Interoperability Test Description Identifier: TD_IMS_SHARE_0007 Summary: IMS network supports Picture sharing service and messages exchange between two users in their networks can be performed. User A starts video sharing with User B during a voice call, but User B rejects the invitation Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5110_01 TS 124 229 [1], clause 5.4.3.3 ¶79 (after 6th dashed list) Use Case ref.: UC_RCS_8_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share picture with user B 3 User B is requested to accept to share picture 4 User B rejects to share picture 5 User A is informed that request has been rejected 6A Voice call termination initiated by user A 6B Voice call termination initiated by user B Conformance Criteria: Check 1 TP_IMS_5110_01 in CFW step 85 (200 OK) ensure that { when { IMS_A receives a 200_response from AS_A addressed_to UE_B } then { IMS_A sends the 200_response to IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share picture with user B 3 INVITE UE_A sends INVITE to share picture with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 187 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to UE_B 12 100 Trying UE_B responds with a 100 Trying provisional response 13 User B is requested to accept to share picture 14 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 15 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 16 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 17 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User B rejects to share picture 20 603 Decline UE_B responds INVITE with 603 Decline to indicate that the request has been rejected 21 603 Decline IMS_B forwards 603 Decline response to IBCF_B 22 603 Decline IBCF_B forwards 603 Decline response to IBCF_A 23 603 Decline IBCF_A forwards 603 Decline response to IMS_A 24 603 Decline IMS_A forwards 603 Decline response to UE_A 25 User A is informed that request has been rejected 26 ACK UE_A acknowledges the receipt of 603 Decline response for INVITE 27 ACK IMS_A forwards ACK to IBCF_A 28 ACK IBCF_A forwards ACK to IBCF_B 29 ACK IBCF_B forwards ACK to IMS_B 30 ACK IMS_B forwards ACK to UE_B 31A Voice call termination initiated by user A 31B Voice call termination initiated by user B
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.4.2 Pictures sharing rejection- roaming (optional)	Interoperability Test Description Identifier: TD_IMS_SHARE_0008 Summary: IMS network supports Picture sharing service and messages exchange between two users, one user in its home network and one user roaming can be performed. User A starts video sharing with User B during a voice call, but User B rejects the invitation Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Use Case ref.: UC_RCS_8_R Pre-test • HSS of IMS_A and of IMS B is configured according to table 1 ETSI ETSI TS 102 901 V4.1.1 (2012-05) 188 Interoperability Test Description conditions: • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share picture with user B 3 User B is requested to accept to share picture 4 User B rejects to share picture 5 User A is informed that request has been rejected 6A User A terminates voice call 6B User B terminates voice call Conformance Criteria: Check 1 TP_IMS_5097_09 in CFW step 105 (INVITE) ensure that { when { IUT receives an INVITE from IMS_A from UE_B } then {IUT sends the INVITE to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header including an orig-ioi_parameter indicating the operator_identifier of IMS_A and not including a term-ioi_parameter and including access-network-charging-info } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share picture with user B 3 INVITE UE_A sends INVITE to share picture with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 189 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IBCF_A 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IMS_A 16 100 Trying IMS_A responds with a 100 Trying provisional response 17 INVITE IMS_A forwards INVITE to UE_B 18 100 Trying UE_B responds with a 100 Trying provisional response 19 User B is requested to accept to share picture 20 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 21 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 22 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 23 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 24 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 27 180 Ringing IMS_A forwards 180 Ringing response to UE_A 28 User B rejects to share picture 29 603 Decline UE_B responds INVITE with 603 Decline to indicate that the request has been rejected 30 603 Decline IMS_A forwards 603 Decline response to IBCF_A 31 603 Decline IBCF_A forwards 603 Decline response to IBCF_B 32 603 Decline IBCF_B forwards 603 Decline response to IMS_B 33 603 Decline IMS_B forwards 603 Decline response to IBCF_B 34 603 Decline IBCF_B forwards 603 Decline response to IBCF_A 35 603 Decline IBCF_A forwards 603 Decline response to IMS_A 36 603 Decline IMS_A forwards 603 Decline response to UE_A 37 User A is informed that request has been rejected 38 ACK UE_A acknowledges the receipt of 603 Decline response for INVITE 39 ACK IMS_A forwards ACK to IBCF_A 40 ACK IBCF_A forwards ACK to IBCF_B 41 ACK IBCF_B forwards ACK to IMS_B 42 ACK IMS_B forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IBCF_A 44 ACK IBCF_A forwards ACK to IMS_A 45 ACK IMS_A forwards ACK to UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 190 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 46A User A terminates voice call 46B User B terminates voice call
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.5 Stop sharing pictures
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.5.1 Stop sharing pictures - interworking	Interoperability Test Description Identifier: TD_IMS_SHARE_0009 Summary: IMS network supports Picture sharing service and messages exchange between two users in their networks can be performed. User A starts video sharing with User B during a voice call, but users decided to stop sharing picture Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5110_01 TS 124 229 [1], clause 5.4.3.3 ¶79 (after 6th dashed list) Use Case ref.: UC_RCS_8_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share picture with user B 3 User B is requested to accept to share picture 4 User B accepts to share picture 5 User A is informed that request has been answered 6 Picture sharing starts 7A User A terminates picture sharing 8A User B is informed that picture sharing has terminated 9A User A is informed that picture sharing has terminated 10A Voice call termination initiated by user A 7B User B terminates picture sharing 8B User A is informed that picture sharing has terminated 9B User B is informed that picture sharing has terminated 10B Voice call termination initiated by user B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 191 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5110_01 in CFW step 85 (200 OK) ensure that { when { IMS_A receives a 200_response from AS_A addressed_to UE_B } then { IMS_A sends the 200_response to IMS_B } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A establishes a voice call to user B 1B User B establishes a voice call to user A 2 User A requests to share picture with user B 3 INVITE UE_A sends INVITE to share picture with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to UE_B 12 100 Trying UE_B responds with a 100 Trying provisional response 13 User B is requested to accept to share picture 14 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 15 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 16 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 17 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User B accepts to share picture 20 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 21 200 OK IMS_B forwards 200 OK response to IBCF_B 22 200 OK IBCF_B forwards 200 OK response to IBCF_A 23 200 OK IBCF_A forwards 200 OK response to IMS_A 24 200 OK IMS_A forwards 200 OK response to UE_A 25 User A is informed that request has been answered 26 ACK UE_A acknowledges the receipt of 200 OK for INVITE 27 ACK IMS_A forwards ACK to IBCF_A 28 ACK IBCF_A forwards ACK to IBCF_B 29 ACK IBCF_B forwards ACK to IMS_B 30 ACK IMS_B forwards ACK to UE_B 31 Picture sharing starts 32A User A terminates picture sharing 33A BYE UE_A releases the call with BYE ETSI ETSI TS 102 901 V4.1.1 (2012-05) 192 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 34A BYE IMS_A forwards BYE to IBCF_A 35A BYE IBCF_A forwards BYE to IBCF_B 36A BYE IBCF_B forwards BYE to IMS_B 37A BYE IMS_B forwards BYE to UE_B 38A User B is informed that picture sharing has terminated 39A 200 OK UE_B sends 200 OK for BYE 40A 200 OK IMS_B forwards 200 OK response to IBCF_B 41A 200 OK IBCF_B forwards 200 OK response to IBCF_A 42A 200 OK IBCF_A forwards 200 OK response to IMS_A 43A 200 OK IMS_A forwards the 200 OK response to UE_A 44A User A is informed that picture sharing has terminated 45A OPTIONS UE_B sends OPTIONS to IMS_B to verify availability of picture sharing capability of the UE_A 46A OPTIONS IMS_B forwards OPTIONS to IBCF_B 47A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 48A OPTIONS IBCF_A forwards OPTIONS to IMS_A 49A OPTIONS IMS_A forwards OPTIONS to UE_A 50A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 51A 200 OK IMS_A forwards 200 OK to IBCF_A 52A 200 OK IBCF_A forwards 200 OK to IBCF_B 53A 200 OK IBCF_B forwards 200 OK to IMS_B 54A 200 OK IMS_B forwards 200 OK to UE_B 55A Voice call termination initiated by user A 32B User B terminates picture sharing 33B BYE UE_B releases the call with BYE 34B BYE IMS_B forwards BYE to IBCF_B 35B BYE IBCF_B forwards BYE to IBCF_A 36B BYE IBCF_A forwards BYE to IMS_A 37B BYE IMS_A forwards BYE to UE_A 38B User A is informed that picture sharing has terminated 39B 200 OK UE_A sends 200 OK for BYE 40B 200 OK IMS_A forwards 200 OK response to IBCF_A 41B 200 OK IBCF_A forwards 200 OK response to IBCF_B 42B 200 OK IBCF_B forwards 200 OK response to IMS_B 43B 200 OK IMS_B forwards the 200 OK response to UE_B 44B User B is informed that picture sharing has terminated 45B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of picture sharing capability of the UE_B 46B OPTIONS IMS_A forwards OPTIONS to IBCF_A 47B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 48B OPTIONS IBCF_B forwards OPTIONS to IMS_B 49B OPTIONS IMS_B forwards OPTIONS to UE_B 50B 200 OK UE_B responds with 200 OK to IMS_B with updated capabilities 51B 200 OK IMS_B forwards 200 OK to IBCF_B 52B 200 OK IBCF_B forwards 200 OK to IBCF_A 53B 200 OK IBCF_A forwards 200 OK to IMS_A 54B 200 OK IMS_A forwards 200 OK to UE_A 55B Voice call termination initiated by user B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 193
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.4.5.2 Stop sharing pictures - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_SHARE_0010 Summary: IMS network supports Picture sharing service and messages exchange between two users, one user in its home network and one user roaming can be performed. User A starts video sharing with User B during a voice call, but users decided to stop sharing picture Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Use Case ref.: UC_RCS_8_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share picture with user B 3 User B is requested to accept to share picture 4 User B accepts to share picture 5 User A is informed that request has been answered 6 Picture sharing starts 7A User A terminates picture sharing 8A User B is informed that picture sharing has terminated 9A User A is informed that picture sharing has terminated 10A User A terminates voice call 7B User B terminates picture sharing 8B User A is informed that picture sharing has terminated 9B User B is informed that picture sharing has terminated 10B User B terminates voice call ETSI ETSI TS 102 901 V4.1.1 (2012-05) 194 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5097_09 in CFW step 105 (INVITE) ensure that { when { IUT receives an INVITE from IMS_A from UE_B } then {IUT sends the INVITE to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header including an orig-ioi_parameter indicating the operator_identifier of IMS_A and not including a term-ioi_parameter and including access-network-charging-info } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1A User A sets up a voice call to user B 1B User B sets up a voice call to user A 2 User A requests to share picture with user B 3 INVITE UE_A sends INVITE to share picture with user B 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IBCF_A 14 100 Trying IBCF_A responds with a 100 Trying provisional response 15 INVITE IBCF_A forwards INVITE to IMS_A 16 100 Trying IMS_A responds with a 100 Trying provisional response 17 INVITE IMS_A forwards INVITE to UE_B 18 100 Trying UE_B responds with a 100 Trying provisional response 19 User B is requested to accept to share picture 20 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 21 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 195 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 22 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 23 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 24 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 27 180 Ringing IMS_A forwards 180 Ringing response to UE_A 28 User B accepts to share picture 29 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 30 200 OK IMS_A forwards 200 OK response to IBCF_A 31 200 OK IBCF_A forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IMS_B 33 200 OK IMS_B forwards 200 OK response to IBCF_B 34 200 OK IBCF_B forwards 200 OK response to IBCF_A 35 200 OK IBCF_A forwards 200 OK response to IMS_A 36 IMS_A forwards 200 OK response to UE_A 37 User A is informed that request has been answered 38 ACK UE_A acknowledges the receipt of 200 OK for INVITE 39 ACK IMS_A forwards ACK to IBCF_A 40 ACK IBCF_A forwards ACK to IBCF_B 41 ACK IBCF_B forwards ACK to IMS_B 42 ACK IMS_B forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IBCF_A 44 ACK IBCF_A forwards ACK to IMS_A 45 ACK IMS_A forwards ACK to UE_B 46 Picture sharing starts 47A User A terminates picture sharing 48A BYE UE_A releases the call with BYE 49A BYE IMS_A forwards BYE to IBCF_A 50A BYE IBCF_A forwards BYE to IBCF_B 51A BYE IBCF_B forwards BYE to IMS_B 52A BYE IMS_B forwards BYE to IBCF_B 53A BYE IBCF_B forwards BYE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 196 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 54A BYE IBCF_A forwards BYE to IMS_A 55A BYE IMS_A forwards BYE to UE_B 56A User B is informed that picture sharing has terminated 57A 200 OK UE_B sends 200 OK for BYE 58A 200 OK IMS_A forwards 200 OK response to IBCF_A 59A 200 OK IBCF_A forwards 200 OK response to IBCF_B 60A 200 OK IBCF_B forwards 200 OK response to IMS_B 61A 200 OK IMS_B forwards the 200 OK response to IBCF_B 62A 200 OK IBCF_B forwards 200 OK response to IBCF_A 63A 200 OK IBCF_A forwards 200 OK response to IMS_A 64A 200 OK IMS_A forwards the 200 OK response to UE_A 65A User A is informed that picture sharing has terminated 66A OPTIONS UE_B sends OPTIONS to IMS_A to verify availability of picture sharing capability of the UE_A 67A OPTIONS IMS_A forwards OPTIONS to IBCF_A 68A OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69A OPTIONS IBCF_B forwards OPTIONS to IMS_B 70A OPTIONS IMS_B forwards OPTIONS to IBCF_B 71A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 72A OPTIONS IBCF_A forwards OPTIONS to IMS_A 73A OPTIONS IMS_A forwards OPTIONS to UE_A 74A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 75A 200 OK IMS_A forwards 200 OK to IBCF_A 76A 200 OK IBCF_A forwards 200 OK to IBCF_B 77A 200 OK IBCF_B forwards 200 OK to IMS_B 78A 200 OK IMS_B forwards 200 OK to IBCF_B 79A 200 OK IBCF_B forwards 200 OK to IBCF_A 80A 200 OK IBCF_A forwards 200 OK to IMS_A 81A 200 OK IMS_A forwards 200 OK to UE_B 82A User A terminates voice call 47B User B terminates picture sharing 48B BYE UE_B releases the call with BYE ETSI ETSI TS 102 901 V4.1.1 (2012-05) 197 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 49B BYE IMS_A forwards BYE to IBCF_A 50B BYE IBCF_A forwards BYE to IBCF_B 51B BYE IBCF_B forwards BYE to IMS_B 52B BYE IMS_B forwards BYE to IBCF_B 53B BYE IBCF_B forwards BYE to IBCF_A 54B BYE IBCF_A forwards BYE to IMS_A 55B BYE IMS_A forwards BYE to UE_A 56B User A is informed that picture sharing has terminated 57B 200 OK UE_A sends 200 OK for BYE 58B 200 OK IMS_A forwards 200 OK response to IBCF_A 59B 200 OK IBCF_A forwards 200 OK response to IBCF_B 60B 200 OK IBCF_B forwards 200 OK response to IMS_B 61B 200 OK IMS_B forwards 200 OK response to IBCF_B 62B 200 OK IBCF_B forwards 200 OK response to IBCF_A 63B 200 OK IBCF_A forwards 200 OK response to IMS_A 64B 200 OK IMS_A forwards the 200 OK response to UE_B 65B User B is informed that picture sharing has terminated 66B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of picture sharing capability of the UE_B 67B OPTIONS IMS_A forwards OPTIONS to IBCF_A 68B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 69B OPTIONS IBCF_B forwards OPTIONS to IMS_B 70B OPTIONS IMS_B forwards OPTIONS to IBCF_B 71B OPTIONS IBCF_B forwards OPTIONS to IBCF_A 72B OPTIONS IBCF_A forwards OPTIONS to IMS_A 73B OPTIONS IMS_A forwards OPTIONS to UE_B 74B 200 OK UE_B responds with 200 OK to IMS_A with updated capabilities 75B 200 OK IMS_A forwards 200 OK to IBCF_A 76B 200 OK IBCF_A forwards 200 OK to IBCF_B 77B 200 OK IBCF_B forwards 200 OK to IMS_B 78B 200 OK IMS_B forwards 200 OK to IBCF_B 79B 200 OK IBCF_B forwards 200 OK to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 198 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 80B 200 OK IBCF_A forwards 200 OK to IMS_A 81B 200 OK IMS_A forwards 200 OK to UE_A 82B User B terminates voice call
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5 File transfer service
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.1 Instant file transfer
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.1.1 Instant file transfer - interworking	Interoperability Test Description Identifier: TD_IMS_FILE_0001 Summary: IMS network supports instant File transfer service and messages exchange between two users in their home network can be performed. User A starts file transfer Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (1st numbered list) TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶89 (4th numbered list) Use Case ref.: UC_RCS_9_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A initiates a file transfer to user B 2 User B is informed of incoming file and accepts the transfer 3 User A is informed that file transfer has been accepted by user B 4 File transfer starts 5 File transfer completed (size checked) 6 User B is informed that file transfer completed 7 User A is informed that file transfer completed ETSI ETSI TS 102 901 V4.1.1 (2012-05) 199 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 10 (INVITE): ensure that { when { UE_A sends an initial INVITE to UE_B } then { IMS_B receives the initial INVITE not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A containing a P-Charging-Vector_header (containing an icid-value_parameter and containing a orig-ioi_parameter indicating IMS_A and not containing an access-network-charging-info_parameter and not containing a term-ioi_parameter) and containing a Record-Route_header indicating the originating S-CSCF_SIP_URI } } 2 TP_IMS_5108_03 in CFW step 14 (INVITE) ensure that { when {IMS_B receives an initial INVITE from IMS_A addressed_to UE_B} then {IMS_B sends the INVITE to AS_B containing a topmost Route_header indicating the SIP_URI of AS_B and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter } } 3 TP_IMS_5115_08 in CFW step 35 (200 OK) ensure that { when { IMS_B receives 200_response from AS_B addressed to UE_A } then { IMS_B sends the 200_response to IMS_A containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and including a term-ioi_parameter indicating operator_identifier of IMS_B } } Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User A initiates a file transfer to user B 2 INVITE UE_A sends INVITE to IMS_A to establish a session with the SDP offer indicating all specific data for a MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to AS/IM_A 5 100 Trying AS/IM_A responds with a 100 Trying provisional response 6 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 7 100 Trying IMS_A responds with a 100 Trying provisional response 8 INVITE IMS_A forwards INVITE to IBCF_A 9 100 Trying IBCF_A responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 200 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 10 INVITE IBCF_A forwards INVITE to IBCF_B 11 100 Trying IBCF_B responds with a 100 Trying provisional response 12 INVITE IBCF_B forwards INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to AS/IM_B 15 100 Trying AS/IM_B responds with a 100 Trying provisional response 16 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 17 100 Trying IMS_B responds with a 100 Trying provisional response 18 INVITE IMS_B forwards INVITE to UE_B 19 100 Trying UE_B optionally responds with a 100 Trying provisional response 20 User B is informed of incoming file and accepts the transfer 21 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform A-side with specific data for a MSRP connection set up 22 200 OK IMS_B forwards 200 OK response to AS/IM_B 23 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 24 200 OK IMS_B forwards 200 OK response to IBCF_B 25 200 OK IBCF_B forwards 200 OK response to IBCF_A 26 200 OK IBCF_A forwards 200 OK response to IMS_A 27 200 OK IMS_A forwards 200 OK response to AS/IM_A 28 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 29 200 OK IMS_A forwards 200 OK response to UE_A 30 User A is informed that file transfer has been accepted by user B 31 ACK UE_A acknowledges the receipt of 200 OK for INVITE 32 ACK IMS_A forwards ACK to AS/IM_A 33 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 34 ACK IMS_A forwards ACK to IBCF_A 35 ACK IBCF_A forwards ACK to IBCF_B 36 ACK IBCF_B forwards ACK to IMS_B 37 ACK IMS_B forwards ACK to AS/IM_B 38 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 39 ACK IMS_B forwards ACK to UE_B 40 File transfer starts (see clause 5.3.3 Image data via MSRP ) 41 File transfer completed (size checked) 42 BYE UE_A releases the file transfer session with BYE ETSI ETSI TS 102 901 V4.1.1 (2012-05) 201 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 43 BYE IMS_A forwards BYE to AS/IM_A 44 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 45 BYE IMS_A forwards BYE to IBCF_A 46 BYE IBCF_A forwards BYE to IBCF_B 47 BYE IBCF_B forwards BYE to IMS_B 48 BYE IMS_B forwards BYE to AS/IM_B 49 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 50 BYE IMS_B forwards BYE to UE_B 51 User B is informed that file transfer completed 52 200 OK UE_B sends 200 OK for BYE 53 200 OK IMS_B forwards 200 OK response to AS/IM_B 54 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 55 200 OK IMS_B forwards 200 OK response to IBCF_B 56 200 OK IBCF_B forwards 200 OK response to IBCF_A 57 200 OK IBCF_A forwards 200 OK response to IMS_A 58 200 OK IMS_A forwards 200 OK response to AS/IM_A 59 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 60 200 OK IMS_A forwards 200 OK response to UE_A 61 User A is informed that file transfer completed
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.1.2 Instant file transfer - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_FILE_0002 Summary: IMS network supports instant File transfer service and messages exchange between two users, one user in its home network and one user roaming can be performed. User B starts file transfer Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ¶1 (1st numbered list) TP_IMS_5067_01 TS 124 229 [1], clause 5.2.7.2 ¶5 TP_IMS_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Use Case ref.: UC_RCS_9_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 202 Interoperability Test Description • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B initiates a file transfer to user A 2 User A is informed of incoming file and accepts the transfer 3 User B is informed that file transfer has been accepted by user A 4 File transfer starts 5 File transfer completed (size checked) 6 User A is informed that file transfer completed 7 User B is informed that file transfer completed Conformance Criteria: Check 1 TP_IMS_5046_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a Route_header not indicating the P-CSCF_SIP_URI of IMS_A and containing a Route_header indicating the "list of Service Route header URIs from the registration" and containing an additional Via_header containing ( the P-CSCF_via_port_number and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and containing an additional topmost Record-Route_header indicating (the P-CSCF_port_number 'where it awaits subsequent requests' from UE_A and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and not containing P-Preferred-Identity_header and containing a P-Asserted-Identity_header containing an address of UE_B and containing a P-Charging-Vector_header containing an icid-value_parameter } } 2 TP_IMS_5067_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a P-Charging-Vector_header } } 3 TP_IMS_5097_09 in CFW step 10 (INVITE) ensure that { when { IMS_B receives an initial INVITE from IMS_A addressed to UE_A } then { IMS_B sends the initial INVITE to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header (including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter and including access-network-charging-info) } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 203 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User B initiates a file transfer to user A 2 INVITE UE_B sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to AS/IM_B 11 100 Trying AS/IM_B responds with a 100 Trying provisional response 12 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to IBCF_B 15 100 Trying IBCF_B responds with a 100 Trying provisional response 16 INVITE IBCF_B forwards INVITE to IBCF_A 17 100 Trying IBCF_A responds with a 100 Trying provisional response 18 INVITE IBCF_A forwards INVITE to IMS_A 19 100 Trying IMS_A responds with a 100 Trying provisional response 20 INVITE IMS_A forwards INVITE to AS/IM_A 21 100 Trying AS/IM_A responds with a 100 Trying provisional response 22 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 23 100 Trying IMS_A responds with a 100 Trying provisional response 24 INVITE IMS_A forwards INVITE to UE_A 25 100 Trying UE_A optionally responds with a 100 Trying provisional response 26 User A is informed of incoming file and accepts the transfer 27 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform B-side with specific data for a new MSRP connection set up 28 200 OK IMS_A forwards 200 OK response to AS/IM_A 29 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 30 200 OK IMS_A forwards 200 OK response to IBCF_A 31 200 OK IBCF_A forwards 200 OK response to IBCF_B 32 200 OK IBCF_B forwards 200 OK response to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 204 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 33 200 OK IMS_B forwards 200 OK response to AS/IM_B 34 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 35 200 OK IMS_B forwards 200 OK response to IBCF_B 36 200 OK IBCF_B forwards 200 OK response to IBCF_A 37 200 OK IBCF_A forwards 200 OK response to IMS_A 38 200 OK IMS_A forwards 200 OK response to UE_B 39 User B is informed that file transfer has been accepted by user B 40 ACK UE_B acknowledges the receipt of 200 OK for INVITE 41 ACK IMS_A forwards ACK to IBCF_A 42 ACK IBCF_A forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IMS_B 44 ACK IMS_B forwards ACK to AS/IM_B 45 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 46 ACK IMS_B forwards ACK to IBCF_B 47 ACK IBCF_B forwards ACK to IBCF_A 48 ACK IBCF_A forwards ACK to IMS_A 49 ACK IMS_A forwards ACK to AS/IM_A 50 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 51 ACK IMS_A forwards ACK to UE_A 52 File transfer starts (see clause 5.3.3 Image data via MSRP ) 53 File transfer completed (size checked) 54 BYE UE_B releases the file transfer session with BYE 55 BYE IMS_A forwards BYE to IBCF_A 56 BYE IBCF_A forwards BYE to IBCF_B 57 BYE IBCF_B forwards BYE to IMS_B 58 BYE IMS_B forwards BYE to AS/IM_B 59 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 60 BYE IMS_B forwards BYE to IBCF_B 61 BYE IBCF_B forwards BYE to IBCF_A 62 BYE IBCF_A forwards BYE to IMS_A 63 BYE IMS_A forwards BYE to AS/IM_A 64 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 65 BYE IMS_A forwards BYE to UE_A 66 User A is informed that file transfer completed 67 200 OK UE_A sends 200 OK for BYE 68 200 OK IMS_A forwards 200 OK response to AS/IM_A 69 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 70 200 OK IMS_A forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 205 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 71 200 OK IBCF_A forwards 200 OK response to IBCF_B 72 200 OK IBCF_B forwards 200 OK response to IMS_B 73 200 OK IMS_B forwards 200 OK response to AS/IM_B 74 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 75 200 OK IMS_B forwards 200 OK response to IBCF_B 76 200 OK IBCF_B forwards 200 OK response to IBCF_A 77 200 OK IBCF_A forwards 200 OK response to IMS_A 78 200 OK IMS_A forwards 200 OK response to UE_B 79 User B is informed that file transfer completed
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.2 Instant file transfer rejection
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.2.1 Instant file transfer rejection - interworking	Interoperability Test Description Identifier: TD_IMS_FILE_0003 Summary: IMS network supports instant File transfer service and messages exchange between two users in their home networks can be performed. User A starts file transfer, but User B rejects the invitation Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 9 in 1st numbered list) TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶89 (4th numbered list) Use Case ref.: UC_RCS_9_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A initiates a file transfer to user B 2 User B is informed of incoming file and rejects the transfer 3 User A is informed that file transfer has been rejected by user B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 206 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 10 (INVITE): ensure that { when { UE_A sends an initial INVITE to UE_B } then { IMS_B receives the initial INVITE not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A containing a P-Charging-Vector_header (containing an icid-value_parameter and containing a orig-ioi_parameter indicating IMS_A and not containing an access-network-charging-info_parameter and not containing a term-ioi_parameter) and containing a Record-Route_header indicating the originating S-CSCF_SIP_URI } } 2 TP_IMS_5108_03 in CFW step 14 (INVITE) ensure that { when {IMS_B receives an initial INVITE from IMS_A addressed_to UE_B} then {IMS_B sends the INVITE to AS_B containing a topmost Route_header indicating the SIP_URI of AS_B and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter } } 3 TP_IMS_5115_08 in CFW step 25 (200 OK) ensure that { when { IMS_B receives 200_response from AS_B addressed to UE_A } then { IMS_B sends the 200_response to IMS_A containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and including a term-ioi_parameter indicating operator_identifier of IMS_B } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 207 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User A initiates a file transfer to user B 2 INVITE UE_A sends INVITE to IMS_A to establish a session with the SDP offer indicating all specific data for a MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to AS/IM_A 5 100 Trying AS/IM_A responds with a 100 Trying provisional response 6 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 7 100 Trying IMS_A responds with a 100 Trying provisional response 8 INVITE IMS_A forwards INVITE to IBCF_A 9 100 Trying IBCF_A responds with a 100 Trying provisional response 10 INVITE IBCF_A forwards INVITE to IBCF_B 11 100 Trying IBCF_B responds with a 100 Trying provisional response 12 INVITE IBCF_B forwards INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to AS/IM_B 15 100 Trying AS/IM_B responds with a 100 Trying provisional response 16 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 17 100 Trying IMS_B responds with a 100 Trying provisional response 18 INVITE IMS_B forwards INVITE to UE_B 19 100 Trying UE_B optionally responds with a 100 Trying provisional response 20 User B is informed of incoming file and rejects the transfer 21 603 Decline UE_B responds INVITE with 603 Decline to indicate that the session has been rejected 22 603 Decline IMS_B forwards 603 Decline response to AS/IM_B 23 603 Decline AS/IM_B returns, possibly modified, 603 Decline response to IMS_B 24 603 Decline IMS_B forwards 603 Decline response to IBCF_B 25 603 Decline IBCF_B forwards 603 Decline response to IBCF_A 26 603 Decline IBCF_A forwards 603 Decline response to IMS_A 27 603 Decline IMS_A forwards 603 Decline response to AS/IM_A 28 603 Decline AS/IM_A returns, possibly modified, 603 Decline response to IMS_A 29 603 Decline IMS_A forwards 603 Decline response to UE_A 30 User A is informed that file transfer has been rejected by user B 31 ACK UE_A acknowledges the receipt of 603 Decline response for INVITE 32 ACK IMS_A forwards ACK to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 208 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 33 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 34 ACK IMS_A forwards ACK to IBCF_A 35 ACK IBCF_A forwards ACK to IBCF_B 36 ACK IBCF_B forwards ACK to IMS_B 37 ACK IMS_B forwards ACK to AS/IM_B 38 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 39 ACK IMS_B forwards ACK to UE_B
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.2.2 Instant file transfer rejection - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_FILE_0004 Summary: IMS network supports instant File transfer service and messages exchange between two users, one user in its home network and one user roaming can be performed. User B starts file transfer, but User A rejects the invitation Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ¶1 (1st numbered list) TP_IMS_5067_01 TS 124 229 [1], clause 5.2.7.2 ¶5 TP_IMS_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Use Case ref.: UC_RCS_9_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User B initiates a file transfer to user A 2 User A is informed of incoming file and rejects the transfer 3 User B is informed that file transfer has been rejected by user B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 209 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5046_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a Route_header not indicating the P-CSCF_SIP_URI of IMS_A and containing a Route_header indicating the "list of Service Route header URIs from the registration" and containing an additional Via_header containing ( the P-CSCF_via_port_number and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and containing an additional topmost Record-Route_header indicating (the P-CSCF_port_number 'where it awaits subsequent requests' from UE_A and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and not containing P-Preferred-Identity_header and containing a P-Asserted-Identity_header containing an address of UE_B and containing a P-Charging-Vector_header containing an icid-value_parameter } } 2 TP_IMS_5067_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a P-Charging-Vector_header } } 3 TP_IMS_5097_09 in CFW step 10 (INVITE) ensure that { when { IMS_B receives an initial INVITE from IMS_A addressed to UE_A } then { IMS_B sends the initial INVITE to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header (including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter and including access-network-charging-info) } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 210 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User B initiates a file transfer to user A 2 INVITE UE_B sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to AS/IM_B 11 100 Trying AS/IM_B responds with a 100 Trying provisional response 12 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to IBCF_B 15 100 Trying IBCF_B responds with a 100 Trying provisional response 16 INVITE IBCF_B forwards INVITE to IBCF_A 17 100 Trying IBCF_A responds with a 100 Trying provisional response 18 INVITE IBCF_A forwards INVITE to IMS_A 19 100 Trying IMS_A responds with a 100 Trying provisional response 20 INVITE IMS_A forwards INVITE to AS/IM_A 21 100 Trying AS/IM_A responds with a 100 Trying provisional response 22 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 23 100 Trying IMS_A responds with a 100 Trying provisional response 24 INVITE IMS_A forwards INVITE to UE_A 25 100 Trying UE_A optionally responds with a 100 Trying provisional response 26 User A is informed of incoming file and rejects the transfer 27 603 Decline UE_A responds INVITE with 603 Decline to indicate that the session has been rejected 28 603 Decline IMS_A forwards 603 Decline response to AS/IM_A 29 603 Decline AS/IM_A returns, possibly modified, 603 Decline response to IMS_A 30 603 Decline IMS_A forwards 603 Decline response to IBCF_A 31 603 Decline IBCF_A forwards 603 Decline response to IBCF_B 32 603 Decline IBCF_B forwards 603 Decline response to IMS_B 33 603 Decline IMS_B forwards 603 Decline response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 211 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 34 603 Decline AS/IM_B returns, possibly modified, 603 Decline response to IMS_B 35 603 Decline IMS_B forwards 603 Decline response to IBCF_B 36 603 Decline IBCF_B forwards 603 Decline response to IBCF_A 37 603 Decline IBCF_A forwards 603 Decline response to IMS_A 38 603 Decline IMS_A forwards 603 Decline response to UE_B 39 User B is informed that file transfer has been rejected by user B 40 ACK UE_B acknowledges the receipt of 603 Decline response for INVITE 41 ACK IMS_A forwards ACK to IBCF_A 42 ACK IBCF_A forwards ACK to IBCF_B 43 ACK IBCF_B forwards ACK to IMS_B 44 ACK IMS_B forwards ACK to AS/IM_B 45 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 46 ACK IMS_B forwards ACK to IBCF_B 47 ACK IBCF_B forwards ACK to IBCF_A 48 ACK IBCF_A forwards ACK to IMS_A 49 ACK IMS_A forwards ACK to AS/IM_A 50 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 51 ACK IMS_A forwards ACK to UE_A
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.3 Stop file transfer
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.3.1 Stop file transfer - interworking	Interoperability Test Description Identifier: TD_IMS_FILE_0005 Summary: IMS network supports instant File transfer service and messages exchange between two users in their home networks can be performed. User A starts file transfer, but User B terminates it in the middle of the process Configuration: CF_INT_AS SUT IMS_A and IMS_B References Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 9 in 1st numbered list) TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) TP_IMS_5115_08 TS 124 229 [1], clause 5.4.3.3 ¶89 (4th numbered list) Use Case ref.: UC_RCS_9_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 212 Interoperability Test Description • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A requests a file transfer with user B 2 User B is requested to accept a file transfer 3 User B accepts a file transfer 4 User A is informed that request has been answered 5 File transfer starts 6A User A terminates file transfer 7A User B is informed that file transfer has terminated 8A User A is informed that file transfer has terminated 6B User B terminates file transfer 7B User A is informed that file transfer has terminated 8B User B is informed that file transfer has terminated Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 10 (INVITE): ensure that { when { UE_A sends an initial INVITE to UE_B } then { IMS_B receives the initial INVITE not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A containing a P-Charging-Vector_header (containing an icid-value_parameter and containing a orig-ioi_parameter indicating IMS_A and not containing an access-network-charging-info_parameter and not containing a term-ioi_parameter) and containing a Record-Route_header indicating the originating S-CSCF_SIP_URI } } 2 TP_IMS_5108_03 in CFW step 14 (INVITE) ensure that { when {IMS_B receives an initial INVITE from IMS_A addressed_to UE_B} then {IMS_B sends the INVITE to AS_B containing a topmost Route_header indicating the SIP_URI of AS_B and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter } } 3 TP_IMS_5115_08 in CFW step 25 (200 OK) ensure that { when { IMS_B receives 200_response from AS_B addressed to UE_A } then { IMS_B sends the 200_response to IMS_A containing a P-Charging-Vector_header including a orig-ioi_parameter indicating operator_identifier of IMS_A and including a term-ioi_parameter indicating operator_identifier of IMS_B } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 213 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1 User A requests a file transfer with user B 2 INVITE UE_A sends INVITE to file transfer session with user B 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to UE_B 11 100 Trying UE_B responds with a 100 Trying provisional response 12 User B is requested to accept a file transfer 13 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 14 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 15 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 16 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 17 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 18 User B accepts a file transfer 19 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 20 200 OK IMS_B forwards 200 OK response to IBCF_B 21 200 OK IBCF_B forwards 200 OK response to IBCF_A 22 200 OK IBCF_A forwards 200 OK response to IMS_A 23 200 OK IMS_A forwards 200 OK response to UE_A 24 User A is informed that request has been answered 25 ACK UE_A acknowledges the receipt of 200 OK for INVITE 26 ACK IMS_A forwards ACK to IBCF_A 27 ACK IBCF_A forwards ACK to IBCF_B 28 ACK IBCF_B forwards ACK to IMS_B 29 ACK IMS_B forwards ACK to UE_B 30 File transfer starts (see clause 5.3.3 Image data via MSRP ) 31A User A terminates file transfer 32A BYE UE_A releases the call with BYE 33A BYE IMS_A forwards BYE to IBCF_A 34A BYE IBCF_A forwards BYE to IBCF_B 35A BYE IBCF_B forwards BYE to IMS_B 36A BYE IMS_B forwards BYE to UE_B 37A User B is informed that file transfer has terminated 38A 200 OK UE_B sends 200 OK for BYE 39A 200 OK IMS_B forwards 200 OK response to IBCF_B 40A 200 OK IBCF_B forwards 200 OK response to IBCF_A 41A 200 OK IBCF_A forwards 200 OK response to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 214 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 42A 200 OK IMS_A forwards the 200 OK response to UE_A 43A User A is informed that file transfer has terminated 44A OPTIONS UE_B sends OPTIONS to IMS_B to verify availability of file transfer capability of the UE_A 45A OPTIONS IMS_B forwards OPTIONS to IBCF_B 46A OPTIONS IBCF_B forwards OPTIONS to IBCF_A 47A OPTIONS IBCF_A forwards OPTIONS to IMS_A 48A OPTIONS IMS_A forwards OPTIONS to UE_A 49A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 50A 200 OK IMS_A forwards 200 OK to IBCF_A 51A 200 OK IBCF_A forwards 200 OK to IBCF_B 52A 200 OK IBCF_B forwards 200 OK to IMS_B 53A 200 OK IMS_B forwards 200 OK to UE_B 31B User B terminates file transfer 32B BYE UE_B releases the call with BYE 33B BYE IMS_B forwards BYE to IBCF_B 34B BYE IBCF_B forwards BYE to IBCF_A 35B BYE IBCF_A forwards BYE to IMS_A 36B BYE IMS_A forwards BYE to UE_A 37B User A is informed that file transfer has terminated 38B 200 OK UE_A sends 200 OK for BYE 39B 200 OK IMS_A forwards 200 OK response to IBCF_A 40B 200 OK IBCF_A forwards 200 OK response to IBCF_B 41B 200 OK IBCF_B forwards 200 OK response to IMS_B 42B 200 OK IMS_B forwards the 200 OK response to UE_B 43B User B is informed that file transfer has terminated 44B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of file transfer capability of the UE_B 45B OPTIONS IMS_A forwards OPTIONS to IBCF_A 46B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 47B OPTIONS IBCF_B forwards OPTIONS to IMS_B 48B OPTIONS IMS_B forwards OPTIONS to UE_B 49B 200 OK UE_B responds with 200 OK to IMS_B with updated capabilities 50B 200 OK IMS_B forwards 200 OK to IBCF_B 51B 200 OK IBCF_B forwards 200 OK to IBCF_A 52B 200 OK IBCF_A forwards 200 OK to IMS_A 53B 200 OK IMS_A forwards 200 OK to UE_A
8cd5b88eda99ed076f2e555b906d5fdc	102 901	4.5.5.3.2 Stop file transfer - roaming (optional)	Interoperability Test Description Identifier: TD_IMS_FILE_0006 Summary: IMS network supports instant File transfer service and messages exchange between two users, one user in its home network and one user roaming can be performed. User A starts file transfer, but User B terminates it in the middle of the process Configuration: CF_ROAM_AS (OPTIONAL) SUT IMS_A and IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 215 Interoperability Test Description References Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ¶1 (1st numbered list) TP_IMS_5067_01 TS 124 229 [1], clause 5.2.7.2 ¶5 TP_IMS_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Use Case ref.: UC_RCS_9_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B have IP bearers established to their respective IMS networks as per TS 186 011-2 [9], clause 4.2.1 • UE_A is registered in IMS_A optionally using userPRES according to table 1 • UE_B is registered in IMS_B via IMS_A optionally using userPRES according to table 1 • UE_A is optionally configured to receive notifications with watcher information • UE_A is authorized to see presence information of UE_B • IMS_A is configured to contact AS_A • IMS_B is configured to contact AS_B • AS_B is optionally configured for reactive authorization • IMS_A is within the trust domain of IMS_B • UE_A and UE_B have already performed capability discovery process • IMS_A not configured for topology hiding Test Sequence: Step 1 User A requests a file transfer with user B 2 User B is requested to accept file transfer 3 User B accepts file transfer 4 User A is informed that request has been answered 5 File transfer starts 6A User A terminates file transfer 7A User B is informed that file transfer has terminated 8A User A is informed that file transfer has terminated 6B User B terminates file transfer 7B User A is informed that file transfer has terminated 8B User B is informed that file transfer has terminated Conformance Criteria: Check 1 TP_IMS_5046_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a Route_header not indicating the P-CSCF_SIP_URI of IMS_A and containing a Route_header indicating the "list of Service Route header URIs from the registration" and containing an additional Via_header containing ( the P-CSCF_via_port_number and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and containing an additional topmost Record-Route_header indicating (the P-CSCF_port_number 'where it awaits subsequent requests' from UE_A and (the P-CSCF-FQDN_address or the P-CSCF-IP_address)) of IMS_A and not containing P-Preferred-Identity_header and containing a P-Asserted-Identity_header containing an address of UE_B and containing a P-Charging-Vector_header containing an icid-value_parameter } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 216 Interoperability Test Description 2 TP_IMS_5067_01 in CFW step 6 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends the INVITE to IMS_B containing a P-Charging-Vector_header } } 3 TP_IMS_5097_09 in CFW step 10 (INVITE) ensure that { when { IMS_B receives an initial INVITE from IMS_A addressed to UE_A } then { IMS_B sends the initial INVITE to AS_B containing a Route_header indicating the SIP_URI of AS_B and containing a P-Charging-Function-Addresses_header and containing a P-Charging-Vector_header (including a orig-ioi_parameter indicating operator_identifier of IMS_A and not including a term-ioi_parameter and including access-network-charging-info) } } Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 1 User A requests a file transfer with user B 2 INVITE UE_A sends INVITE to a file transfer session with user B 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to IBCF_B 11 100 Trying IBCF_B responds with a 100 Trying provisional response 12 INVITE IBCF_B forwards INVITE to IBCF_A 13 100 Trying IBCF_A responds with a 100 Trying provisional response 14 INVITE IBCF_A forwards INVITE to IMS_A 15 100 Trying IMS_A responds with a 100 Trying provisional response 16 INVITE IMS_A forwards INVITE to UE_B 17 100 Trying UE_B responds with a 100 Trying provisional response 18 User B is requested to accept file transfer 19 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 20 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 21 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 22 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 23 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 217 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 24 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 25 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 26 180 Ringing IMS_A forwards 180 Ringing response to UE_A 27 User B accepts file transfer 28 200 OK UE_B responds INVITE with 200 OK to indicate that the request has been accepted 29 200 OK IMS_A forwards 200 OK response to IBCF_A 30 200 OK IBCF_A forwards 200 OK response to IBCF_B 31 200 OK IBCF_B forwards 200 OK response to IMS_B 32 200 OK IMS_B forwards 200 OK response to IBCF_B 33 200 OK IBCF_B forwards 200 OK response to IBCF_A 34 200 OK IBCF_A forwards 200 OK response to IMS_A 35 IMS_A forwards 200 OK response to UE_A 36 User A is informed that request has been answered 37 ACK UE_A acknowledges the receipt of 200 OK for INVITE 38 ACK IMS_A forwards ACK to IBCF_A 39 ACK IBCF_A forwards ACK to IBCF_B 40 ACK IBCF_B forwards ACK to IMS_B 41 ACK IMS_B forwards ACK to IBCF_B 42 ACK IBCF_B forwards ACK to IBCF_A 43 ACK IBCF_A forwards ACK to IMS_A 44 ACK IMS_A forwards ACK to UE_B 45 File transfer starts (see clause 5.3.3 Image data via MSRP ) 46A User A terminates file transfer 47A BYE UE_A releases the call with BYE 48A BYE IMS_A forwards BYE to IBCF_A 49A BYE IBCF_A forwards BYE to IBCF_B 50A BYE IBCF_B forwards BYE to IMS_B 51A BYE IMS_B forwards BYE to IBCF_B 52A BYE IBCF_B forwards BYE to IBCF_A 53A BYE IBCF_A forwards BYE to IMS_A 54A BYE IMS_A forwards BYE to UE_B 55A User B is informed that file transfer has terminated 56A 200 OK UE_B sends 200 OK for BYE 57A 200 OK IMS_A forwards 200 OK response to IBCF_A 58A 200 OK IBCF_A forwards 200 OK response to IBCF_B 59A 200 OK IBCF_B forwards 200 OK response to IMS_B 60A 200 OK IMS_B forwards the 200 OK response to IBCF_B 61A 200 OK IBCF_B forwards 200 OK response to IBCF_A 62A 200 OK IBCF_A forwards 200 OK response to IMS_A 63A 200 OK IMS_A forwards the 200 OK response to UE_A 64A User A is informed that file transfer has terminated 65A OPTIONS UE_B sends OPTIONS to IMS_A to verify availability of file transfer capability of the UE_A 66A OPTIONS IMS_A forwards OPTIONS to IBCF_A 67A OPTIONS IBCF_A forwards OPTIONS to IBCF_B 68A OPTIONS IBCF_B forwards OPTIONS to IMS_B 69A OPTIONS IMS_B forwards OPTIONS to IBCF_B 70A OPTIONS IBCF_B forwards OPTIONS to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 218 Step Direction Message Comment U s e r A U E A I M S A I B C F A I B C F B I M S B U E B U s e r B 71A OPTIONS IBCF_A forwards OPTIONS to IMS_A 72A OPTIONS IMS_A forwards OPTIONS to UE_A 73A 200 OK UE_A responds 200 OK to IMS_A with updated capabilities 74A 200 OK IMS_A forwards 200 OK to IBCF_A 75A 200 OK IBCF_A forwards 200 OK to IBCF_B 76A 200 OK IBCF_B forwards 200 OK to IMS_B 77A 200 OK IMS_B forwards 200 OK to IBCF_B 78A 200 OK IBCF_B forwards 200 OK to IBCF_A 79A 200 OK IBCF_A forwards 200 OK to IMS_A 80A 200 OK IMS_A forwards 200 OK to UE_B 46B User B terminates file transfer 47B BYE UE_B releases the call with BYE 48B BYE IMS_A forwards BYE to IBCF_A 49B BYE IBCF_A forwards BYE to IBCF_B 50B BYE IBCF_B forwards BYE to IMS_B 51B BYE IMS_B forwards BYE to IBCF_B 52B BYE IBCF_B forwards BYE to IBCF_A 53B BYE IBCF_A forwards BYE to IMS_A 54B BYE IMS_A forwards BYE to UE_A 55B User A is informed that file transfer has terminated 56B 200 OK UE_A sends 200 OK for BYE 57B 200 OK IMS_A forwards 200 OK response to IBCF_A 58B 200 OK IBCF_A forwards 200 OK response to IBCF_B 59B 200 OK IBCF_B forwards 200 OK response to IMS_B 60B 200 OK IMS_B forwards 200 OK response to IBCF_B 61B 200 OK IBCF_B forwards 200 OK response to IBCF_A 62B 200 OK IBCF_A forwards 200 OK response to IMS_A 63B 200 OK IMS_A forwards the 200 OK response to UE_B 64B User B is informed that file transfer has terminated 65B OPTIONS UE_A sends OPTIONS to IMS_A to verify availability of file transfer capability of the UE_B 66B OPTIONS IMS_A forwards OPTIONS to IBCF_A 67B OPTIONS IBCF_A forwards OPTIONS to IBCF_B 68B OPTIONS IBCF_B forwards OPTIONS to IMS_B 69B OPTIONS IMS_B forwards OPTIONS to IBCF_B 70B OPTIONS IBCF_B forwards OPTIONS to IBCF_A 71B OPTIONS IBCF_A forwards OPTIONS to IMS_A 72B OPTIONS IMS_A forwards OPTIONS to UE_B 73B 200 OK UE_B responds with 200 OK to IMS_A with updated capabilities 74B 200 OK IMS_A forwards 200 OK to IBCF_A 75B 200 OK IBCF_A forwards 200 OK to IBCF_B 76B 200 OK IBCF_B forwards 200 OK to IMS_B 77B 200 OK IMS_B forwards 200 OK to IBCF_B 78B 200 OK IBCF_B forwards 200 OK to IBCF_A 79B 200 OK IBCF_A forwards 200 OK to IMS_A 80B 200 OK IMS_A forwards 200 OK to UE_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 219
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5 MSRP Test Specification
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.1 Introduction	MSRP is a text based, connection-oriented protocol specified in RFC 4975 [10], RFC 4976 [11] and RFC 6135 [12]. It is not designed for use as a standalone protocol and therefore it can be part of the SIP protocol. The MSRP URIs are exchanged using SDP in an offer/answer exchange via SIP. NOTE: Following test descriptions shall be implemented within IMS-NNI Interoperability test descriptions.
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.2 Test Prerequisites
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.2.1 Authorization over MSRP	Client that wants to use the services of IM AS they need to authenticate with authorization procedure. Expected authorization procedure is detailed described in RFC 4976 [11] and its MSRP sequence diagram is: Step Direction Message Comment UE AS IM 1 AUTH The UE sends AUTH 2 401 Unauthorized The AS IM responds with a valid HTTP Digest authentication challenge 3 AUTH The UE sends another AUTH with authentication 4 200 OK The AS IM responds with 200 OK.
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3 Use Cases	The test descriptions with call flow diagrams in clauses 4.5.3, 4.5.4 and 4.5.5 contain basic MSRP transactions which are only marked symbolically, e.g. "Users perform chatting". Detailed MSRP call flows are described in the present clause. This split of MSRP and SIP signalling has been chosen to keep the test description more readable.
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3.1 Chat 1 to 1 via MSRP	Use case index UC_MSRP_01 is used. NOTE: Call flows show only the first chat transmission from one user to another and back. Other transmissions follow depending on who sends the next text message to the other user; this message is transferred with SEND request to the other user. Step Direction Message Comment U s e r A U E A U E B U s e r B 1 User A write a chat message 2 SEND UE A sends SEND MSRP with content to UE B 3 200 OK UE B responds with 200 OK to UE A 4 User B read a chat message 5 User B write a chat message 6 SEND UE B sends SEND MSRP with content to UE A 7 200 OK UE A responds with 200 OK to UE B 8 User A read a chat message ETSI ETSI TS 102 901 V4.1.1 (2012-05) 220
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3.2 Chat 1 to many via MSRP	NOTE: Call flows show only the first chat transmission from one user to all other users. Other transmissions follow depending on who sends the next text message to the other user; this message is transferred with SEND request to the other parties.
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3.2.1 Chat 1 to many via MSRP - Interworking	Use case index UC_MSRP_02_I is used. Step Direction Message Comment U s e r A U E A A S/ I M A U E B U s e r B U E C U s e r C 1 User A write a chat message 2 SEND UE A sends SEND MSRP with content to IM SERVER 3 200 OK IM SERVER responds with 200 OK to UE A 4 SEND IM SERVER sends SEND MSRP with content to UE B 5 200 OK UE responds with 200 OK to IM SERVER 6 User B read a chat message 7 SEND IM SERVER sends SEND MSRP with content to UE C 8 200 OK UE C responds with 200 OK to IM SERVER 9 User C read a chat message
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3.2.2 Chat 1 to many via MSRP - Roaming	Use case index UC_MSRP_02_R is used. Step Direction Message Comment U s e r A U E A A S/ I M B U E B U s e r B U E C U s e r C 1 SEND UE A sends SEND MSRP with content to IM SERVER 2 200 OK IM SERVER responds with 200 OK to UE A 3 User B write a chat message 4 SEND IM SERVER sends SEND MSRP with content to UE B 5 200 OK UE responds with 200 OK to IM SERVER 6 User A read a chat message 7 SEND IM SERVER sends SEND MSRP with content to UE C 8 200 OK UE C responds with 200 OK to IM SERVER 9 User C read a chat message ETSI ETSI TS 102 901 V4.1.1 (2012-05) 221
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3.2.3 Chat 1 to many via MSRP to additional user - Interworking	Use case index UC_MSRP_03_I is used. Step Direction Message Comment U s e r A U E A A S/ I M A U E D U s e r D 1 Follow UC_MSRP_02_I 2 SEND IM SERVER sends SEND MSRP with content to UE D 3 200 OK UE D responds with 200 OK to IM SERVER 4 User D read a chat message
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3.2.4 Chat 1 to many via MSRP to additional user - Roaming	Use case index UC_MSRP_03_R is used. Step Direction Message Comment U s e r A U E A A S/ I M B U E B U s e r B U E D U s e r D 1 Follow UC_MSRP_02_R 2 SEND IM SERVER sends SEND MSRP with content to UE D 3 200 OK UE D responds with 200 OK to IM SERVER 4 User D read a chat message
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.3.3 Image data via MSRP	Use case index UC_MSRP_04 is used. NOTE: Call flows show only the first picture transmission from one user to another and back. Other chunk transmissions in case of bigger files follow with SEND requests. Step Direction Message Comment U s e r A U E A U E B U s e r B 1 User A select a picture 2 SEND (image) UE A sends SEND MSRP with content to UE B 3 200 OK UE B responds with 200 OK to UE A 4 User B look a picture ETSI ETSI TS 102 901 V4.1.1 (2012-05) 222
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.4 Test Descriptions
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.4.1 Chat 1 to 1 procedure via MSRP	Interoperability Test Description Identifier: TD_MSRP_CHAT_0001 Summary: User A transfers message with SEND request to User B via MSRP and if endpoint receives a request it must immediately generate response and send it back. Configuration: CF_INT_AS SUT UE_A and UE_B References Test Purpose Specification Reference TP_MSRP_9000_01 RFC 4975 [10], clauses 5.4 and 7.1 TP_MSRP_9000_02 RFC 4975 [10], clause 7.2 Use Case ref.: UC_MSRP_01 Pre-test conditions: • UE_A has_initiated_a_dialog_with UE_B Test Sequence: Step 1 User A writes a chat message 2 User B reads a chat message ETSI ETSI TS 102 901 V4.1.1 (2012-05) 223 Interoperability Test Description Conformance Criteria: Check 1 TP_MSRP_9000_01 ensure that { when { User A initiates the call to User B } then { UE_A sends the initial INVITE containing an offered session-description indicating a session of MSRP } } 2 TP_MSRP_9000_02 ensure that { when { UE_A sends SEND_MSRP to UE_B } then { UE_A receives the INVITE200 OK response containing an offered session-description indicating a session of MSRP } } 1 TP_MSRP_9000_03 step 2 and 6 (SEND): ensure that { when { UE_A sends SEND_MSRP to UE_B } then { UE_B receives the SEND_MSRP containing FromPath_header indicating the msrp_path from SDP attribute within SIP INVITE containing ToPath_header indicating the msrp_path from SDP attribute within SIP 200_response containing Content-Type_header indicating text/plain } } 2 TP_MSRP_9001_04 step 3 and 7 (200 OK SEND): ensure that { when { UE_B receives SEND_MSRP from UE_A } then { UE_B sends the 200_response_MSRP containing FromPath_header indicating the msrp_path from SDP attribute within SIP INVITE containing ToPath_header indicating the msrp_path from SDP attribute within SIP 200_response } } Step Direction Message Comment U s e r A U E A U E B U s e r B 1 User A writes a chat message 2 SEND UE A sends SEND MSRP with content to UE B 3 200 OK UE B responds with 200 OK to UE A 4 User B reads a chat message 5 User B writes a chat message 6 SEND UE B sends SEND MSRP with content to UE A 7 200 OK UE A responds with 200 OK to UE B 8 User A reads a chat message ETSI ETSI TS 102 901 V4.1.1 (2012-05) 224
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.4.2 Chat 1 to many procedure via MSRP	Interoperability Test Description Identifier: TD_MSRP_CHAT_0002 Summary: User A transfers message with SEND request to AS IM via MSRP. AS IM transfers message to User B and User C like it is predefined in previous SIP dialog. If end users receive a request they must immediately generate response and send it back to AS IM which sends response back to User A. Configuration: SUT UE_A, UE_B, UE_C and AS IM References Test Purpose Specification Reference TP_MSRP_9000_01 RFC 4975 [10], clause 5.4 and 7.1 TP_MSRP_9000_02 RFC 4975 [10], clause 7.2 Use Case ref.: UC_MSRP_02_I Pre-test conditions: • UE_A has_initiated_a_dialog_with UE_B and UE_C Test Sequence: Step 1 User A writes a chat message 2 User B reads a chat message 3 User C reads a chat message Conformance Criteria: Check 1 TP_MSRP_9000_01 ensure that { when { User A initiates the call to User B } then { UE_A sends the initial INVITE containing an offered session-description indicating a session of MSRP } } 2 TP_MSRP_9000_02 ensure that { when { UE_A sends SEND_MSRP to UE_B } then { UE_A receives the INVITE200 OK response containing an offered session-description indicating a session of MSRP } } 3 TP_MSRP_9000_03 step 2,5 and 7 (SEND): ensure that { when { UE_A sends SEND_MSRP to UE_B } then { UE_B receives the SEND_MSRP containing FromPath_header indicating the msrp_path from SDP attribute within SIP INVITE containing ToPath_header indicating the msrp_path from SDP attribute within SIP 200_response containing Content-Type_header indicating text/plain } } 4 TP_MSRP_9001_04 step 3,6 and 8 (200 OK SEND): ensure that { when { UE_B receives SEND_MSRP from UE_A } then { UE_B sends the 200_response_MSRP containing FromPath_header indicating the msrp_path from SDP attribute within SIP INVITE containing ToPath_header indicating the msrp_path from SDP attribute within SIP 200_response } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 225 Step Direction Message Comment U s e r A U E A A S/ I M A U E B U s e r B U E C U s e r C 1 User A writes a chat message 2 SEND UE A sends SEND MSRP with content to IM SERVER 3 200 OK IM SERVER responds with 200 OK to UE A 4 SEND IM SERVER sends SEND MSRP with content to UE B 5 200 OK UE responds with 200 OK to IM SERVER 6 User B reads a chat message 7 SEND IM SERVER sends SEND MSRP with content to UE C 8 200 OK UE C responds with 200 OK to IM SERVER 9 User C reads a chat message
8cd5b88eda99ed076f2e555b906d5fdc	102 901	5.4.3 Image transfer procedure via MSRP	Interoperability Test Description Identifier: TD_MSRP_FILE_0001 Summary: User A transfers file with SEND request to User B via MSRP and if endpoint receives a request it must immediately generate response and send it back. Configuration: SUT UE_A and UE_B References Test Purpose Specification Reference TP_MSRP_9000_03 RFC 4975 [10], clauses 5.4 and 7.1 and RFC 5547 [13] TP_MSRP_9001_01 RFC 4975 [10], clause 7.2 Use Case ref.: UC_MSRP_04 Pre-test conditions: • UE_A has_initiated_a_dialog_with UE_B Test Sequence: Step 1 User A selects a file for sending 2 User B opens received file Conformance Criteria: Check 1 TP_MSRP_9000_03 step 2 (SEND): ensure that { when { UE_A sends SEND_MSRP to UE_B } then { UE_B receives the SEND_MSRP containing FromPath_header indicating the msrp_path from SDP attribute within SIP INVITE containing ToPath_header indicating the msrp_path from SDP attribute within SIP 200_response containing Content-Type_header indicating image/jpg } } ETSI ETSI TS 102 901 V4.1.1 (2012-05) 226 Interoperability Test Description 2 TP_MSRP_9001_04 step 3 (200 OK SEND): when { UE_B receives SEND_MSRP from UE_A } then { UE_B sends the 200_response_MSRP containing FromPath_header indicating the msrp_path from SDP attribute within SIP INVITE containing ToPath_header indicating the msrp_path from SDP attribute within SIP 200_response } } Step Direction Message Comment U s e r A U E A U E B U s e r B 1 User A selects a picture 2 SEND (image) UE A sends SEND MSRP with content to UE B 3 200 OK UE B responds with 200 OK to UE A 4 User B views a picture ETSI ETSI TS 102 901 V4.1.1 (2012-05) 227 Annex A (normative): Zip file with TPLan code The test purposes used in the present document have been originally generated in the TPLan text files in the archive file ts_102901V040101p0.zip which accompanies the present document. ETSI ETSI TS 102 901 V4.1.1 (2012-05) 228 History Document history V1.1.1 June 2011 Publication V2.1.1 November 2011 Publication V4.1.1 May 2012 Publication
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	1 Scope	The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) of the Message Waiting Indication (MWI) service, based on 3GPP stage three Protocol Description of the (MWI) service, based on stage one and two of the ISDN MWI supplementary services.
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	2.1 Normative references	The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 606 (V8.2.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI)using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.606 version 8.2.0 Release 8)". [2] ETSI TS 102 891-1: "Technical Committee for IMS Network Testing (INT); Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Part 1: Protocol Implementation Conformance Statement (PICS)". [3] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)". [4] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification". [5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts".
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	2.2 Informative references	The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	3 Definitions and abbreviations
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	3.1 Definitions	For the purposes of the present document, the terms and definitions given in TS 124 606 [1] and the following apply: Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5]. ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 6 PICS proforma: Refer to ISO/IEC 9646-1 [5]. point of control and observation: Refer to ISO/IEC 9646-1 [5]. Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5]. System Under Test (SUT): Refer to ISO/IEC 9646-1 [5]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	3.2 Abbreviations	For the purposes of the present document, the abbreviations given in TS 124 606 [1] and the following apply: ATM Abstract Test Method ATS Abstract Test Suite IUT Implementation Under Test PICS Protocol Implementation Conformance Statement SUT System Under Test TP Test Purpose TSS Test Suite Structure TSS&TP Test Suite Structure and Test Purposes
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	4 Test Suite Structure (TSS)	UserEquipment MWI_U01_xxx Network AS_ServedUser OIP_N01_xxx
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	4.1 Configuration	The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as described in [1]. The stage 3 description respects the requirements to several network entities and also to requirements regarding to end devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities. Therefore to test the appropriate entities the configurations below are applicable: Testing of the Application Server. This entity is responsible to perform the service. Hence the ISC interface is the appropriate access point. Figure 1 points to this. Application Server Implementation under Test Test System ISC Figure 1: Applicable interface to test AS functionalities ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 7 If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. CSCF (and/or AS) Implementation under Test Test System Test System Mw, Mg, Mx Mw, Mg, Mx Figure 2: Applicable interfaces to test using the (generic) NNI interface Figure 3 illustrates the usage of any NNI interface. Testing of User Equipment. There are several requirements regarding to the end devices. Therefore a special configuration appears. User Equipment Implementation under Test Test System Gm Figure 3: Applicable configuration to test the User Equipment
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5 Test Purposes (TP)
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5.1 Introduction	For each requirement in TS 124 606 [1] a TP is defined.
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5.1.1 TP naming convention	TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 8 Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "MWI" <iut> = type of IUT: U User - equipment N Network <group> = group 2 digit field representing group reference according to TSS <nnn> = 3 digit sequential number (001-999)
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5.1.2 Test strategy	As the base standard TS 124 606 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 102 891-1 [2]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered.
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5.1.3 Reference column "MWI reference"	The column "MWI reference" makes reference to TS 124 606 [1], except where explicitly stated otherwise.
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5.2 Invocation and operation
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5.2.1 Actions at the UE	TSS UserEquipment TP MWI_U01_001 MWI reference 4.7.2.1 Selection expression PICS 2/1 Test purpose: Initial subscription for a public user identity using the public service identity Ensure that the user equipment is able to subscribe to the MWI service. A SUBSCRIBE message is sent. The Request line contains the public service identity of the MA. The Event header is set to 'message-summary', the Expires header is set to a proper value, Accept header is set to 'application/simple-message-summary'. SIP header: SUBSCRIBE sip: public service identity@server SIP/2.0 Event: message-summary Expires: <a valid value> Accept: application/simple-message-summary Comments: User Equipment Test Equipment SUBSCRIBE 200 OK (SUBSCRIBE) TSS UserEquipment TP MWI_U01_002 MWI reference 4.7.2.1 Selection expression PICS 2/2 Test purpose: Initial subscription for a public user identity using the public user identity Ensure that the user equipment is able to subscribe to the MWI service. A SUBSCRIBE message is sent. The Request line contains the public user identity of the subscriber. The Event header is set to 'message-summary', the Expires header is set to a proper value, Accept header is set to 'application/simple-message-summary'. SIP header: SUBSCRIBE sip: public user identity@server SIP/2.0 Event: message-summary Expires: <a valid value> Accept: application/simple-message-summary Comments: User Equipment Test Equipment SUBSCRIBE 200 OK (SUBSCRIBE) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 9 TSS UserEquipment TP MWI_U01_003 MWI reference 4.7.2.1, RFC 3842 [3] 3.6 Selection expression Test purpose: Re-Subscription before subscription is expired Ensure that the user equipment is able to re-subscribe the current subscription before the subscription expires. A SUBSCRIBE message is sent. The Event header is set to 'message-summary', the Expires header is set to a proper value, Accept header is set to 'application/simple-message-summary'. The Call-ID is equal to the Call-ID of the initial subscription. SIP header: SUBSCRIBE Event: message-summary Expires: 500 Accept: application/simple-message-summary Comments: User Equipment Test Equipment SUBSCRIBE 200 OK (SUBSCRIBE) Before subscription expires SUBSCRIBE 200 OK (SUBSCRIBE) TSS UserEquipment TP MWI_U01_004 MWI reference 4.7.2.1, RFC 3842 [3] 3.6 Selection expression Test purpose: Subscription after re-subscription fails Ensure that the user equipment is able to subscribe to the MWI service after a re-subscription failed. A SUBSCRIBE message is sent. The Event header is set to 'message-summary', the Expires header is set to a proper value, Accept header is set to 'application/simple-message-summary'. SIP header: SUBSCRIBE 1 Event: message-summary Expires: 500 Accept: application/simple-message-summary SUBSCRIBE 2 Call-ID: <different from Call-ID of SUBCRIBE 1> Event: message-summary Expires: 500 Accept: application/simple-message-summary Comments: User Equipment Test Equipment SUBSCRIBE 200 OK (SUBSCRIBE) Before subscription expires SUBSCRIBE 1 500 SUBSCRIBE 2 200 OK (SUBSCRIBE) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 10 TSS UserEquipment TP MWI_U01_005 MWI reference 4.7.2.1, RFC 3265 [4] 3.1.4.3 Selection expression Test purpose: Unsubscribe from MWI service Ensure that the user equipment is able to unsubscribe the current subscription. A SUBSCRIBE message is sent. The Event header is set to 'message-summary', the Expires header is set to zero, Accept header is set to 'application/simple-message-summary'. The Call-ID is equal to the Call-ID of the initial subscription. SIP header: SUBSCRIBE2 Event: message-summary Expires: 0 Accept: application/simple-message-summary Comments: User Equipment Test Equipment SUBSCRIBE1 200 OK (SUBSCRIBE) SUBSCRIBE2 200 OK (SUBSCRIBE) TSS UserEquipment TP MWI_U01_006 MWI reference 4.7.2.1, RFC 3842 [3] 3.9 Selection expression Test purpose: Reception of status information after subscription Upon receipt of a valid NOTIFY request after subscription, the user equipment accepts the information and sends a 200 OK response. SIP header: NOTIFY Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes Message-Account: sip:served_user@Server Voice-Message: 4/1 (2/0) Video-Message: 3/1 (1/0) Fax-Message: 2/1 (0/1) Comments: User Equipment Test Equipment SUBSCRIBE 200 OK (SUBSCRIBE) Status information indicate to the user NOTIFY 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 11 TSS UserEquipment TP MWI_U01_007 MWI reference 4.7.2.1, RFC 3842 [3] 3.9 Selection expression Test purpose: Reception of subsequent status information after state change Upon receipt of a valid NOTIFY request to refresh the status of deposited messages, the user equipment accepts the information and sends a 200 OK response. SIP header: NOTIFY 1 Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes Message-Account: sip:served_user@Server Voice-Message: 4/1 (2/0) Video-Message: 3/1 (1/0) Fax-Message: 2/1 (0/1) NOTIFY 2 Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes Message-Account: sip:served_user@Server Voice-Message: 5/1 (2/0) Video-Message: 3/1 (1/0) Fax-Message: 2/1 (0/1) Comments: User Equipment Test Equipment SUBSCRIBE 200 OK (SUBSCRIBE) Status information indicate to the user NOTIFY 1 200 OK (NOTIFY) New voice message in the account Status information indicate to the user NOTIFY 2 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 12
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	5.2.2 Actions at the AS	TSS Network/AS_ServedUser TP MWI_ N01_001 MWI reference 4.7.2.5, RFC 3842 [3] 3.4, RFC 3265 [4] 3.1.4.1, 3.1.6.2 Selection expression Test purpose: Subscription to the message waiting service, all relevant headers present Verify that the SUBSCRIBE request will be accepted with following Subscribe-specific headers: Event, Expires and Accept. The 200 OK (SUBSCRIBE) contains the Expires header indicating the subscription duration for the MWI service. A NOTIFY is sent immediately the actual state of a message account. The From header tag and the Call-ID in the NOTIFY are equal to the values in the SUBSCRIBE. SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary NOTIFY Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) TSS Network/AS_ServedUser TP MWI_N01_002 MWI reference 4.7.2.5, RFC 3265 [4] 3.1.4.3 Selection expression Test purpose: The user is able to unsubscribe the service Verify that the SUBSCRIBE request will be accepted with Expires header with value zero; Check that the 2xx response to the unsubscription contains also an Expires header with value zero. A NOTIFY is sent. SIP header: SUBSCRIBE Event: message-summary Expires: 0 Accept: application/simple-message-summary 200 OK (SUBCRIBE) Expires: 0 NOTIFY Event: message-summary Subscription-State: terminated(; reason=timeout) Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE 200 OK (SUBSCRIBE) NOTIFY 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 13 TSS Network/AS_ServedUser TP MWI_N01_003 MWI reference 4.7.2.5, RFC 3265 [4] 3.1.6.2 Selection expression Test purpose: Refresh of current subscription. Verify that a SUBSCRIBE request will be accepted at any time before the original subscription expires when From header tag and the Call-ID in the subsequent SUBSCRIBE are equal to the values in the original SUBSCRIBE request. A NOTIFY is sent. SIP header: SUBSCRIBE 1 To-header with tag=tag_value1 CallId=callId_value1 SUBSCRIBE 2 To-header with tag=tag_value1 CallId=_callId_value1 Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE 1 CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) Refreshing of Subscription SUBSCRIBE 2 CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 14 TSS Network/AS_ServedUser TP MWI_N01_004 MWI reference 4.7.2.5, RFC 3265 [4] 3.1.4.2 Selection expression Test purpose: Unsuccessful refresh of subscription Verify that a SUBSCRIBE request will be rejected with a "481 Call/Transaction Does Not Exist" response after expiry of the subscription when the subsequent SUBSCRIBE request uses the same dialog (From tag, CallId) as the actual expired subscription. SIP header: SUBSCRIBE 1 To-header with tag=tag_value1 CallId=_callId_value1 SUBSCRIBE 2 To-header with tag=tag_value1 CallId=callId_value1 Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE 1 CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) Subscription time expired SUBSCRIBE 2 481 Call/Transaction Does Not Exist ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 15 TSS Network/AS_ServedUser TP MWI_N01_005 MWI reference 4.7.2.5, RFC 3265 [4] 3.2.2 Selection expression Test purpose: NOTIFY request after initial subscription Verify that after a successfully subscription a NOTIFY request is sent containing a "Subscription-State" header with the value "active" and an "expires" parameter which indicates the time remaining on the subscription. The From header tag and the Call-ID in the NOTIFY are equal to the values in the SUBSCRIBE. The NOTIFY includes: • Event header set to message-summary • Subscription-State header set to active (optional) expires parameter set to the time remaining on the subscription • Content-Type header set to application/simple-message-summary MIME body: • Messages-Waiting: yes • Message-Account: identifying the served user (optional) • msg-summary-line(s) (optional) SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary NOTIFY Event: message-summary Subscription-State: active; expires= <a valid value> Content-Type: application/simple-message-summary Messages-Waiting: yes …. Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) TSS Network/AS_ServedUser TP MWI_N01_006 MWI reference 4.7.2.5, RFC 3265 [4] 3.2.2 Selection expression Test purpose: Subscription terminates after 481 response to NOTIFY request Verify that a non-200 response (e. g. 481) after a received NOTIFY request will remove the corresponding subscription; Check that no further NOTIFY responses will be received. SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 481 Call/Transaction Does Not Exist Action causes in a message summary state change No subsequent NOTIFY is sent ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 16 TSS Network/AS_ServedUser TP MWI_N01_007 MWI reference 4.7.2.5, RFC 3842 [3] 3.5, 5.2 Selection expression Test purpose: Message indicated in the NOTIFY request after initial subscription. Verify that after a successfully subscription, when a message is waiting, a NOTIFY request is sent with a body containing a message summary indicating "Messages-Waiting: yes". SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary NOTIFY Event: message-summary Subscription-State: active; expires= <a valid value> Content-Type: application/simple-message-summary Messages-Waiting: yes Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) TSS Network/AS_ServedUser TP MWI_N01_008 MWI reference 4.7.2.5, RFC 3842 [3] 3.5, 5.2 Selection expression PICS 3/1 Test purpose: Message indicated in the NOTIFY request after initial subscription, msg-account present Verify that after a successfully subscription, when a message is waiting, a NOTIFY request is sent with a body containing a message summary indicating "Messages-Waiting: yes" and containing an "msg-account" line. SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary NOTIFY Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes Message-Account: sip:<URI of served MWI user> Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 17 TSS Network/AS_ServedUser TP MWI_N01_009 MWI reference 4.7.2.5, RFC 3842 [3] 3.5, 5.2 Selection expression PICS 3/2 Test purpose: Message indicated in the NOTIFY request after initial subscription, msg-summary-line present Verify that after a successfully subscription, when a message is waiting, a NOTIFY request is sent with a body containing a message summary indicating "Messages-Waiting: yes" and containing an "msg-summary-line" line. SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary NOTIFY Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes voice-message: <a valid value> / <a valid value> (<a valid value> / <a valid value> ) Preconditions: An arrangement exists with the service provider to deliver state changes Comments: The "new-urgentmsgs SLASH old-urgentmsgs" is optional ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 18 TSS Network/AS_ServedUser TP MWI_N01_010 MWI reference 4.7.2.5, RFC 3842 [3] 3.5, 5.2 Selection expression Test purpose: NOTIFY indicates state change due to a message after successful subscription Verify that after a successfully subscription a NOTIFY message is sent immediately. Afterwards verify that an additional NOTIFY request is sent with a body containing a message summary indicating "Messages-Waiting: yes" when a change in the subscribed state occurs, e.g. a new message has been received at the Message account. The From header tag and the Call-ID in the two NOTIFY requests are equal. SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary NOTIFY 1 Event: message-summary Subscription-State: active; expires=<a valid value> Content-Type: application/simple-message-summary NOTIFY 2 Event: message-summary Subscription-State: active; expires=<a valid value> Content-Type: application/simple-message-summary Messages-Waiting: yes Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 1 200 OK (NOTIFY) Action causes in a message summary state change NOTIFY 2 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 19 TSS Network/AS_ServedUser TP MWI_N01_011 MWI reference 4.7.2.5, RFC 3842 [3] 3.5, 5.2 Selection expression PICS 3/3 Test purpose: NOTIFY indicates state change due to a message after successful subscription, opt-msg-headers are present Verify that after a successfully subscription a NOTIFY message is sent immediately. Afterwards verify that an additional NOTIFY request is sent with a body containing a message summary indicating "Messages-Waiting: yes" and containing opt-msg-headers that describe newly added message(s) when a change in the subscribed state occurs, e.g. a new message has been received at the Message account. The From header tag and the Call-ID in the two NOTIFY requests are equal. SIP header: SUBSCRIBE Event: message-summary Expires: 7200 Accept: application/simple-message-summary NOTIFY 1 Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes NOTIFY 2 Event: message-summary Subscription-State: active Content-Type: application/simple-message-summary Messages-Waiting: yes To: <[email protected]> From: <[email protected]> Message-ID: <a valid value>> Message-Context: voice-message Preconditions: An arrangement exists with the service provider to deliver state changes Comments: Any set of opt-msg-headers is acceptable for this test, the above code serves only as an example ISC SUT SUBSCRIBE CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 1 200 OK (NOTIFY) Action causes in a message summary state change NOTIFY 2 200 OK (NOTIFY) ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 20 TSS Network/AS_ServedUser TP MWI_N03_012 MWI reference 4.7.2.5, RFC 3842 [3] 3.1.4.2 Selection expression Test purpose: Refresh of subscription in a new dialogue Verify that at any time before a subscription expires the subscription will be successfully refreshed by sending of a SUBSCRIBE request on a different dialog (different Call-Id and From-Tag) as the existing subscription. The From header tag and the Call-ID in the SUBCRIBE 1 are unequal to the values in the SUBSCRIBE 2. SIP header: SUBSCRIBE 1 Event: message-summary Expires: 7200 Accept: application/simple-message-summary SUBSCRIBE 2 Event: message-summary Expires: 7200 Accept: application/simple-message-summary Preconditions: An arrangement exists with the service provider to deliver state changes Comments: ISC SUT SUBSCRIBE 1 CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY) Refreshing of Subscription SUBSCRIBE 2 CASE A 200 OK (SUBSCRIBE) CASE B 202 Accepted NOTIFY 200 OK (NOTIFY)
a804f82de4c2f5c67cd7ec4a0ede9db9	102 891-2	6 Compliance	An ATS which complies with the present document shall: a) consist of a set of test cases corresponding to the set or to a subset of the TPs specified in clause 5; b) use a TSS which is an appropriate subset of the whole of the TSS specified in clause 4; c) use the same naming conventions for the test groups and test cases; d) maintain the relationship specified in clause 5 between the test groups and TPs and the entries in the PICS proforma to be used for test case deselection. In the case of a) or b) above, a subset shall be used only where a particular Abstract Test Method (ATM) makes some TPs untestable. All testable TPs from clause 5 shall be included in a compliant ATS. ETSI ETSI TS 102 891-2 V3.2.1 (2011-08) 21 History Document history V3.1.1 July 2010 Publication V3.2.1 August 2011 Publication
f33e61678ba2128cc7b64c3ba6f33e28	102 891-1	1 Scope	The present document specifies the Protocol Implementation Conformance Statement of the Message Waiting Indication (MWI) service, based on 3GPP stage three Protocol Description of the Message Waiting Indication (MWI) service, based on stage one and two of the ISDN MWI supplementary services.
f33e61678ba2128cc7b64c3ba6f33e28	102 891-1	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
f33e61678ba2128cc7b64c3ba6f33e28	102 891-1	2.1 Normative references	The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 406 (2008): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification (3GPP TS 24.406 Release 8)". [2] ISO/IEC 9646-1: "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 1: General concepts". [3] ISO/IEC 9646-7: "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [4] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)".
f33e61678ba2128cc7b64c3ba6f33e28	102 891-1	2.2 Informative references	The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.