hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4 Messaging | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.1 Messaging with ENUM lookup procedure | Interoperability Test Description Identifier: TD_IMS_MESS_0004 Summary: IMS network handles messaging with DNS/ENUM lookup procedure correctly Configuration: CF_INT_CALL SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_ENUM_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 10 in 1st numbered list) TP_IMS_5097_08 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 10 in 1st numbered) TP_IMS_5117_06 TS 124 229 [1], clause 5.4.3.3 ¶44 Use Case ref.: UC_05_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is registered in IMS_B using userTEL_priv according to table 1 • IMS_A is within the trust domain of IMS_B • Common DNS is configured with a DNS/ENUM entry mapping ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 209 Interoperability Test Description • MESSAGE request and response has to be supported at II-NNI (TS 129 165 [16] see Table 6.1 and Table 6.3) Test Sequence: Step 1 User A sends message to user B's Tel URI (i.e. userTEL in IMS_B) 2 Verify that user B receives message from user A Conformance Criteria: Check 1 TP_IMS_ENUM_01 in CFW step 4 (NAPTR Response): ensure that { when { UE_A sends an initial INVITE for UE_B to IMS_A containing a Request_URI indicating a Tel_URI and IMS_A sends a NAPTR_Query to ENUM_DB containing the TN derived_from the Tel_URI_E.164_Number } then { ENUM_DB sends a NAPTR_Response to IMS_A containing a NAPTR_Resource_Record containing the TTL of the NAPTR_record containing the service_type indicating E2U+sip containing the_regular_expressiob indicating !^(.*)$! containing the SIP_URI of UE_B indicating backreference (\1) for the user part indicating domain name for the host part containing SIP_URI_parameters 'if applicable' } 2 TP_IMS_5097_08 in CFW step 6 (MESSAGE) ensure that { when { UE_A sends a MESSAGE to UE_B containing a Request_URI indicating a Tel_URI } then { IMS_A sends a NAPTR_Query to ENUM DB containing the Tel_URI_E.164_Number } when { IMS_A receives NAPTR_Response containing a NAPTR_Resource_Record indicating the SIP_URI of UE_B } then { IMS_A sends the MESSAGE to IMS_B containing a Request_URI indicating a SIP_URI containing a P-Charging-Vector_header not containing a access-network-charging-info_parameter } } 3 TP_IMS_5117_06 in CFW step 12 (200 OK) ensure that { when { UE_B sends a 2xx_response to UE_A } then { IMS_A receives the 2xx_response 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 E N U M DB 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 sends an instant message to user B 2 MESSAGE UE_A sends MESSAGE to IMS_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 210 Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A 5 MESSAGE IMS_A sends MESSAGE to IBCF_A 6 MESSAGE IBCF_A sends MESSAGE to IBCF_B 7 MESSAGE IBCF_B sends MESSAGE to IMS_B 8 MESSAGE IMS_B sends MESSAGE to UE_B 9 User B is informed about the instant message 10 200 OK UE_B sends 200 OK to IMS_B 11 200 OK IMS_B sends 200 OK to IBCF_B 12 200 OK IBCF_B sends 200 OK to IBCF_A 13 200 OK IBCF_A sends 200 OK to IMS_A 14 200 OK IMS_A sends 200 OK to UE_A 15 Optional: User A is presented a delivery report |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.2 Messaging with SIP URI public identities | Interoperability Test Description Identifier: TD_IMS_MESS_0002 Summary: IMS network handles messaging with SIP identity correctly without topology hiding Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5097_05 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5097_06 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 9 in 1st numbered list) TP_IMS_5117_02 TS 124 229 [1], clause 5.4.3.3 ¶100 (item 2 in 5th numbered list) TP_IMS_5118_01 TS 124 229 [1], clause 5.4.3.3 ¶105 (item 2 in 6th numbered list) Use Case ref.: UC_05_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 clause 4.2.1 • UE_A is registered in IMS_A using userSIP_priv according to table 1 • UE_B is registered in IMS_B using any user identity • IMS_A is within the trust domain of IMS_B • UE_A and UE_B registered with SIP URI public identities • IMS_A not configured for topology hiding • MESSAGE request and response has to be supported at II-NNI (TS 129 165 [16] see Tables 6.1 and 6.3) Test Sequence: Step 1 User A sends message to user B ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 211 Interoperability Test Description 2 Verify that user B receives message from user A Conformance Criteria: Check 1 TP_IMS_5097_05 in CFW step 6 (MESSAGE) ensure that { when { UE_A sends a MESSAGE to UE_B } then { IMS_B receives the MESSAGE 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) } } 2 TP_IMS_5097_06 in CFW step 6 (MESSAGE) ensure that { when { UE_A sends a MESSAGE to UE_B } then { IMS_B receives the MESSAGE containing a P-Asserted-Identity_header indicating the SIP_URI of UE_A and containing a P-Asserted-Identity_header indicating the Tel_URI of UE_A } } 3 TP_IMS_5117_02 in CFW step 12 (200 OK) ensure that { when { UE_B sends a 2xx_response to UE_A } then { IMS_A receives the 2xx_response containing a P-Charging-Vector_header not containing an access-network-charging-info_parameter } } 4 TP_IMS_5118_01 in CFW step 12 (200 OK) ensure that { when { UE_B sends 200_response to UE_A } then { IMS_A receives the 200_response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating operator_identifier of IMS_A and containing a term-ioi_parameter indicating operator_identifier of IMS_B } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB 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 sends an instant message to user B 2 MESSAGE UE_A sends MESSAGE to IMS_A 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A 5 MESSAGE IMS_A sends MESSAGE to IBCF_A 6 MESSAGE IBCF_A sends MESSAGE to IBCF_B 7 MESSAGE IBCF_B sends MESSAGE to IMS ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 212 Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 8 MESSAGE IMS_B sends MESSAGE to UE_B 9 User B is informed about the instant message 10 200 OK UE_B sends 200 OK to IMS_B 11 200 OK IMS_B sends 200 OK to IBCF_B 12 200 OK IBCF_B sends 200 OK to IBCF_A 13 200 OK IBCF_A sends 200 OK to IMS_A 14 200 OK IMS_A sends 200 OK to UE_A 15 Optional: User A is presented a delivery report |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.3 Messaging with TEL URI identities | Interoperability Test Description Identifier: TD_IMS_MESS_0003 Summary: IMS network handles messaging with TEL URI identities correctly Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5097_07 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5117_02 TS 124 229 [1], clause 5.4.3.3 ¶100 (item 2 in 5th numbered list) TP_IMS_5118_01 TS 124 229 [1], clause 5.4.3.3 ¶105 (item 2 in 6th numbered list) TP_IMS_5117_06 TS 124 229 [1], clause 5.4.3.3 ¶100 (item 1 in 5th numbered list) Use Case ref.: UC_05_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 clause 4.2.1 • UE_A is registered in IMS_A using userTEL_priv according to table 1 • UE_B is registered in IMS_B using userTEL_priv according to table 1 • IMS_A is within the trust domain of IMS_B • MESSAGE request and response has to be supported at II-NNI (TS 129 165 [16] see Tables 6.1 and 6.3) Test Sequence: Step 1 User A sends message to User B (i.e. userTEL in IMS_B) 2 Verify that user B receives message from user A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 213 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5097_07 in CFW step 6 (MESSAGE) ensure that { when { UE_A sends a MESSAGE to UE_B } then { IMS_B receives the MESSAGE containing a P-Asserted-Identity_header indicating the SIP_URI of UE_A and containing a P-Asserted-Identity_header indicating the Tel_URI of UE_A } } 2 TP_IMS_5117_02 in CFW step 12 (200 OK) ensure that { when { UE_B sends a 2xx_response to UE_A } then { IMS_A receives the 2xx_response containing a P-Charging-Vector_header not containing a access-network-charging-info_parameter } } 3 TP_IMS_5118_01 in CFW step 12 (200 OK) ensure that { when { UE_B sends 200_response to UE_A } then { IMS_A receives the 200_response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating operator_identifier of IMS_A and containing a term-ioi_parameter indicating operator_identifier of IMS_B } } 4 TP_IMS_5117_06 in CFW step 12 (200 OK) ensure that { when { UE_B sends a 2xx_response to UE_A } then { IMS_A receives the 2xx_response 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 E N U M DB 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 sends an instant message to user B 2 MESSAGE UE_A sends MESSAGE to IMS_A 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A 5 MESSAGE IMS_A sends MESSAGE to IBCF_A 6 MESSAGE IBCF_A sends MESSAGE to IBCF_B 7 MESSAGE IBCF_B sends MESSAGE to IMS 8 MESSAGE IMS_B sends MESSAGE to UE_B 9 User B is informed about the instant message ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 214 Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 10 200 OK UE_B sends 200 OK to IMS_B 11 200 OK IMS_B sends 200 OK to IBCF_B 12 200 OK IBCF_B sends 200 OK to IBCF_A 13 200 OK IBCF_A sends 200 OK to IMS_A 14 200 OK IMS_A sends 200 OK to UE_A 15 Optional: User A is presented a delivery report |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.4 Messaging when roaming | Interoperability Test Description Identifier: TD_IMS_MESS_0005 Summary: IMS network handles messaging while roaming correctly Configuration: CF_ROAM_CALL SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5108_02 TS 124 229 [1], clause 5.4.3.3 ¶5 (1st numbered list) TP_IMS_5118_01 TS 124 229 [1], clause 5.4.3.3 ¶105 (item 2 in 6th numbered list) Use Case ref.: UC_05_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is registered in IMS_B via IMS_A using any user identity • MESSAGE request and response has to be supported at II-NNI (TS 129 165 [16] see tables 6.1 and 6.3) Test Sequence: Step 1 User A sends message to user B 2 Verify that user B receives message from user A Conformance Criteria: Check 1 TP_IMS_5108_02 in CFW step 7 (MESSAGE) ensure that { when { UE_A sends a MESSAGE to UE_B IMS_A sends the MESSAGE to IMS_B containing a P-Charging-Vector_header containing an icid-value_parameter } then { IMS_B sends the MESSAGE to IMS_A containing a Route_header not indicating the S-CSCF_SIP_URI of IMS_B and containing a P-Charging-Vector_header containing the same icid-value_parameter and not containing ioi_parameters containing a Record-Route_header containing the S-CSCF_SIP_URI of IMS_B } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 215 Interoperability Test Description 2 TP_IMS_5118_01 in CFW step 18 (200 OK) ensure that { when { UE_B sends 200_response to UE_A } then { IMS_A receives the 200_response containing a P-Charging-Vector_header containing a orig-ioi_parameter indicating operator_identifier of IMS_A and containing a term-ioi_parameter indicating operator_identifier 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 E N U M DB I M S B U E B U s e r B 1 User B sends an instant message to user A 2 MESSAGE UE_B sends MESSAGE to IMS_A 3 MESSAGE IMS_A sends MESSAGE to IBCF_A 4 MESSAGE IBCF_A sends MESSAGE to IBCF_B 5 MESSAGE IBCF_B sends MESSAGE to IMS_B 6 ENUM IMS_A sends query to ENUM DB 7 ENUM ENUM DB sends response to IMS_A 8 MESSAGE IMS_B sends MESSAGE to IBCF_B 9 MESSAGE IBCF_B sends MESSAGE to IBCF_A 10 MESSAGE IBCF_A sends MESSAGE to IMS_A 11 MESSAGE IMS_A sends MESSAGE to UE_A 12 User A is informed about the instant message 13 200 OK UE_A sends 200 OK to IMS_A 14 200 OK IMS_A sends 200 OK to IBCF_A 15 200 OK IBCF_A sends 200 OK to IBCF_B 16 200 OK IBCF_B sends 200 OK to IMS_B 17 200 OK IMS_B sends 200 OK to IBCF_B 18 200 OK IBCF_B sends 200 OK to IBCF_A 19 200 OK IBCF_A sends 200 OK to IMS_A 20 200 OK IMS_A sends 200 OK to UE_B 21 Optional: User B is presented a delivery report ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 216 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.5 Messaging with receiving user not registered | Interoperability Test Description Identifier: TD_IMS_MESS_0006 Summary: IMS network handles messaging correctly when receiving user is not registered Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5114_02 TS 124 229 [1], clause 5.4.3.3 ¶85 (item 3 in 3rd numbered list) Use Case ref.: UC_05_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is not registered in IMS_B • IMS_B is not configured with any filter criteria to contact "any AS" • MESSAGE request and response has to be supported at II-NNI (TS 129 165 [16] see tables 6.1 and 6.3) Test Sequence: Step 1 User A sends message to a valid user B identity 2 Verify that user A is informed that user B could not be reached Conformance Criteria: Check 1 TP_IMS_5114_02 in CFW step 12 (4xx Response) ensure that { when { UE_A sends a MESSAGE to UE_B and IMS_A sends the MESSAGE to IMS_B } then { IMS_B sends a 4xx_response to IMS_A } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB 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 sends an instant message to user B 2 MESSAGE UE_A sends MESSAGE to IMS_A 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A 5 MESSAGE IMS_A sends MESSAGE to IBCF_A 7 MESSAGE IBCF_A sends MESSAGE to IBCF_B 9 MESSAGE IBCF_B sends MESSAGE to IMS_B 10 IMS_B detects that user B is not registered 11 4xx Response IMS_B sends 4xx Response to IBCF_B 12 4xx Response IBCF_B forwards 4xx Response to IBCF_A 13 4xx Response IBCF_A forwards 4xx Response to IMS_A 14 4xx Response IMS_A forwards 4xx Response to UE_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 217 Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 15 Optional: User A is presented a delivery report |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.6 Messaging with receiving user barred | Interoperability Test Description Identifier: TD_IMS_MESS_0007 Summary: IMS network handles messaging correctly when receiving user has been barred Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5108_06 TS 124 229 [1], clause 5.4.3.3 ¶6 (item 1 in1st numbered list) Use Case ref.: UC_05_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is registered in IMS_B using any user identity • User B is barred in IMS_B • MESSAGE request and response has to be supported at II-NNI (TS 129 165 [16] see tables 6.1 and 6.3) Test Sequence: Step 1 User A sends message to User B 2 Verify that user A is informed that user B could not be reached Conformance Criteria: Check 1 TP_IMS_5108_06 in CFW step 12 (404 Response) ensure that { when { UE_A sends a MESSAGE to UE_B and IMS_A sends the MESSAGE to IMS_B containing a Request_URI indicating a barred_user in IMS_B } then { IMS_B sends 404_response to IMS_A } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB 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 sends an instant message to user B 2 MESSAGE UE_A sends MESSAGE to IMS_A 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A 5 MESSAGE IMS_A sends MESSAGE to IBCF_A 7 MESSAGE IBCF_A sends MESSAGE to IBCF_B ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 218 Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 9 MESSAGE IBCF_B sends MESSAGE to IMS_B 10 IMS_B detects that user B is not registered 11 404 Not Found IMS_B sends 404 Response to IBCF_B 12 404 Not Found IBCF_B forwards 404 Response to IBCF_A 13 404 Not Found IBCF_A forwards 404 Response to IMS_A 14 404 Not Found IMS_A forwards 404 Response to UE_A 15 Optional: User A is presented a delivery report |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5 Supplementary Services | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.1 Supplementary Service HOLD with AS | Interoperability Test Description Identifier: TD_IMS_SS_0001 Summary: IMS network supports properly application services based on the example of the HOLD supplementary service Configuration: CF_INT_AS SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5310_01 TS 124 229 [1], clause 5.4.6.1.2 ¶1 TP_IMS_5312_01 TS 124 229 [1], clause 5.4.6.1.3 ¶1 Use Case ref.: UC_10_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is registered in IMS_B using userHOLD identity according to table 1 • IMS_B is configured to contact AS_B (HOLD) • UE_B is subscribed to HOLD service • AS B in same trust domain as IMS B Test Sequence: Step 1 User A calls User B (i.e. userHOLD in IMS_B) 2 Verify that user B is informed of incoming call of User A 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user B is informed that call is established 7 User B puts call on hold 8 Verify that user A is informed that call on hold with AS tone 9 Verify that user B is informed that call on hold 10 User B resumes call 11 Verify that user A is informed that call is resumed 12 Verify that user B is informed that call is resumed 13 User A ends call 14 Verify that user B is informed that call has ended 15 Verify that user A is informed that call has ended ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 219 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5310_01 in CFW step 37 (INVITE) ensure that { when { UE_B sends a subsequent INVITE to IMS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the INVITE to AS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } } 2 TP_IMS_5312_01 in CFW step 52 and Step 54 (200 OK) ensure that { when { IMS_B receives a 200_response from IMS_A containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the 200_response to AS_B containing a P-Charging-Vector_header containing a access-network-charging-info_parameter } } 3 TP_IMS_5310_01 in CFW step 65 (INVITE) ensure that { when { UE_B sends a subsequent INVITE to IMS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the INVITE to AS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } } 4 TP_IMS_5312_01 in CFW step 80 and Step 82 (200 OK) ensure that { when { IMS_B receives a 200_response from IMS_A containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the 200_response to AS_B containing a P-Charging-Vector_header containing a access-network-charging-info_parameter } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 34 User B puts call on hold 35 INVITE UE_B sends reINVITE message indicating media attribute "sendonly" 36 100 Trying IMS_B responds with a 100 Trying provisional response 37 INVITE IMS_B sends reINVITE to AS_B 38 100 Trying AS_B optionally responds with a 100 Trying provisional response 39 INVITE AS_B sends reINVITE to IMS_B ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 220 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 40 100 Trying IMS_B responds with a 100 Trying provisional response 41 INVITE IMS_B forwards reINVITE to IBCF_B 42 100 Trying IBCF_B responds with a 100 Trying provisional response 43 INVITE IBCF_B forwards reINVITE to IBCF_A 44 100 Trying IBCF_A responds with a 100 Trying provisional response 45 INVITE IBCF_A forwards reINVITE to IMS_A 46 100 Trying IMS_A responds with a 100 Trying provisional response 47 INVITE IMS_A forwards reINVITE to UE_A 48 100 Trying UE _A optionally responds with a 100 Trying provisional response 49 User A is informed that call is on hold with AS tone 50 200 OK UE_A responds to reINVITE with 200 OK indicating media attribute "recvonly" 51 200 OK IMS_A forwards 200 OK response to IBCF_A 52 200 OK IBCF_A forwards 200 OK response to IBCF_B 53 200 OK IBCF_B forwards 200 OK response to IMS_B 54 200 OK IMS_B forwards 200 OK response to AS_B 55 200 OK AS_B forwards 200 OK response to IMS_B 56 200 OK IMS_A forward the 200 OK to UE_B 57 User B is informed that the call is on hold 58 ACK UE_B acknowledges the receipt of 200 OK for reINVITE 59 ACK IMS_B forwards ACK to AS_B 60 ACK AS_B forwards ACK to IMS_B 61 ACK IMS_B forwards ACK to UE_B 62 User B resumes call 63 INVITE UE_B sends second reINVITE message indicating media attribute C 64 100 Trying IMS_B responds with a 100 Trying provisional response 65 INVITE IMS_B sends reINVITE to AS_B 66 100 Trying AS_B optionally responds with a 100 Trying provisional response 67 INVITE AS_B forwards INVITE to IMS_B ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 221 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 68 100 Trying IMS_B responds with a 100 Trying provisional response 69 INVITE IMS_B sends reINVITE to IBCF_B 70 100 Trying IBCF_B responds with a 100 Trying provisional response 71 INVITE IBCF_B sends reINVITE to IBCF_A 72 100 Trying IBCF_A responds with a 100 Trying provisional response 73 INVITE IBCF_A sends reINVITE to IMS_A 74 100 Trying IMS_A responds with a 100 Trying provisional response 75 INVITE IMS_A forwards reINVITE to UE_A 76 100 Trying UE_A optionally responds with a 100 Trying provisional response 77 User A is informed that call is resumed 78 200 OK UE_A sends the 200 OK indicating media attribute "sendrecv" 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_B 83 200 OK AS_B forwards the 200 OK for INVITE 84 200 OK IMS_B forwards 200 OK to UE_B 85 User B is informed that call is resumed ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 222 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.2 Supplementary Service HOLD with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0002 Summary: IMS network supports properly application services based on the example of the HOLD supplementary service Configuration: CF_ROAM_AS SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5310_01 TS 124 229 [1], clause 5.4.6.1.2 ¶1 TP_IMS_5312_01 TS 124 229 [1], clause 5.4.6.1.3 ¶1 Use Case ref.: UC_10_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is registered in IMS_B via IMS_A using userHOLD identity according to table 1 • IMS_B is configured to contact AS_B (HOLD) • UE_B is subscribed to HOLD service • AS B in same trust domain as IMS B Test Sequence: Step 1 User A calls User B (i.e. userHOLD in IMS_B) 2 Verify that user B is informed of incoming call of User A 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user B is informed that call is established 7 User B puts call on hold 8 Verify that user A is informed that call on hold with AS tone 9 Verify that user B is informed that call on hold 10 User B resumes call 11 Verify that user A is informed that call is resumed 12 Verify that user B is informed that call is resumed 13 User A ends call 14 Verify that user B is informed that call has ended 15 Verify that user A is informed that call has ended ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 223 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5310_01 in CFW step 54 and Step 58 (INVITE) ensure that { when { UE_B sends a subsequent INVITE to IMS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the INVITE to AS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } } 2 TP_IMS_5312_01 in CFW step 73 and Step 75 (200 OK) ensure that { when { IMS_B receives a 200_response from IMS_A containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the 200_response to AS_B containing a P-Charging-Vector_header containing a access-network-charging-info_parameter } } 3 TP_IMS_5310_01 in CFW step 95 and Step 101 (INVITE) ensure that { when { UE_B sends a subsequent INVITE to IMS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the INVITE to AS_B containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } } 4 TP_IMS_5312_01 in CFW step 112 and Step 114 (200 OK) ensure that { when { IMS_B receives a 200_response from IMS_A containing a P-Charging-Vector_header containing an access-network-charging-info_parameter } then { IMS_B sends the 200_response to AS_B containing a P-Charging-Vector_header containing a access-network-charging-info_parameter } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S B 49 User B puts call on hold 50 INVITE UE_B sends reINVITE message indicating media attribute 51 100 Trying IMS_A responds with a 100 Trying provisional response 52 INVITE IMS_A forwards INVITE to IBCF_A 53 100 Trying IBCF_A responds with a 100 Trying provisional response ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 224 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S B 54 INVITE IBCF_A forwards INVITE to IBCF_B 55 100 Trying IBCF_B responds with a 100 Trying provisional response 56 INVITE IBCF_B forwards INVITE to IMS_B 57 100 Trying IMS_B responds with a 100 Trying provisional response 58 INVITE IMS_B sends reINVITE to AS_B 59 100 Trying AS_B optionally responds with a 100 Trying provisional response 60 INVITE AS_B sends reINVITE to IMS_B 61 100 Trying IMS_B responds with a 100 Trying provisional response 62 INVITE IMS_B forwards reINVITE to IBCF_B 63 100 Trying IBCF_B responds with a 100 Trying provisional response 64 INVITE IBCF_B forwards reINVITE to IBCF_A 65 100 Trying IBCF_A responds with a 100 Trying provisional response 66 INVITE IBCF_A forwards reINVITE to IMS_A 67 100 Trying IMS_A responds with a 100 Trying provisional response 68 INVITE IMS_A forwards reINVITE to UE_A 69 100 Trying UE _A optionally responds with a 100 Trying provisional response 70 User A is informed that call is on hold with AS tone 71 200 OK UE_A responds to reINVITE with 200 OK indicating media attribute 72 200 OK IMS_A forwards 200 OK response to IBCF_A 73 200 OK IBCF_A forwards 200 OK response to IBCF_B 74 200 OK IBCF_B forwards 200 OK response to IMS_B 75 200 OK IMS_B forwards 200 OK response to AS_B 76 200 OK AS_B forwards 200 OK response to IMS_B 77 200 OK IMS_B forwards 200 OK response to IBCF_B 78 200 OK IBCF_B forwards 200 OK response to IBCF_A 79 200 OK IBCF_A forwards 200 OK response to IMS_A 80 200 OK IMS_A forward the 200 OK to UE_B 81 User B is informed that the call is on hold ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 225 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S B 82 ACK UE_B acknowledges the receipt of 200 OK for reINVITE 83 ACK IMS_A forwards ACK to IBCF_A 84 ACK IBCF_A forwards ACK to IBCF_B 85 ACK IBCF_A forwards ACK to IMS_B 86 ACK IMS_B forwards ACK to AS_B 87 ACK AS_B forwards ACK to IMS_B 88 ACK IMS_B forwards ACK to IBCF_B 89 ACK IBCF_B forwards ACK to IBCF_A 90 ACK IBCF_A forwards ACK to IMS_A 91 ACK IMS_A forwards ACK to UE_B 92 User B resumes call 93 INVITE UE_B sends second reINVITE message indicating media 94 100 Trying IMS_A responds with a 100 Trying provisional response 95 INVITE IMS_A sends reINVITE to IBCF_A 96 100 Trying IBCF_A responds with a 100 Trying provisional response 97 INVITE IBCF_A sends reINVITE to IBCF_B 98 100 Trying IBCF_B responds with a 100 Trying provisional response 99 INVITE IBCF_B sends reINVITE to IMS_B 100 100 Trying IMS_B responds with a 100 Trying provisional response 101 INVITE IMS_B sends reINVITE to AS_B 102 100 Trying AS_B optionally responds with a 100 Trying provisional response 103 INVITE AS_B forwards INVITE to IMS_B 104 100 Trying IMS_B responds with a 100 Trying provisional response 105 INVITE IMS_B sends reINVITE to IBCF_B 106 100 Trying IBCF_B responds with a 100 Trying provisional response 107 INVITE IBCF_B forwards reINVITE to IBCF_A 108 100 Trying IBCF_A responds with a 100 Trying provisional response 109 INVITE IBCF_A forwards reINVITE to IMS_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 226 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S B 110 100 Trying IMS_A responds with a 100 Trying provisional response 107 INVITE IMS_A forwards reINVITE to UE_A 108 100 Trying UE_A optionally responds with a 100 Trying provisional response 109 User A is informed that call is resumed 110 200 OK UE_A sends the 200 OK indicating media attribute "sendrecv" to IMS_A 111 200 OK IMS_A forwards 200 OK response to IBCF_A 112 200 OK IBCF_A forwards 200 OK response to IBCF_B 113 200 OK IBCF_B forwards 200 OK response to IMS_B 114 200 OK IMS_B forwards 200 OK response to AS_B 115 200 OK AS_B forwards the 200 OK for INVITE 116 200 OK IMS_B forwards 200 OK to IBCF_B 117 200 OK IBCF_B forwards 200 OK to IBCF_A 118 200 OK IBCF_A forwards 200 OK to IMS_A 119 200 OK IMS_A forwards 200 OK to UE_B 120 User B is informed that call is resumed |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.3 Supplementary Service OIP with AS | Interoperability Test Description Identifier: TD_IMS_SS_0003 Summary: IMS network supports properly application services based on the example of the OIP supplementary service Configuration: CF_INT_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5097_02 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_08_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is registered in IMS_B using userOIP identity according to table 1 • IMS_B is configured to contact AS_B (OIP) • UE_B is subscribed to OIP service ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 227 Interoperability Test Description Test Sequence: Step 1 User A calls User B (i.e. userOIP in IMS_B) 2 Verify that user B is informed of incoming call of User A, user A's identity is displayed 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user B is informed that the call is established 7 User A ends call 8 Verify that user B is informed that call has ended 9 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_5097_02 in CFW step 8 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_A addressed to UE_B } then { IMS_A sends the initial INVITE to IMS_B containing a P-Asserted-Identity_header indicating the SIP_URI of UE_A and containing a P-Asserted-Identity_header indicating the Tel_URI of UE_A } } 2 TP_IMS_5108_03 in CFW step 12 (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 32 (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 U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired media and codecs that 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 ENUM IMS_A sends query to ENUM DB 5 ENUM ENUM DB sends response to IMS ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 228 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 6 INVITE IMS_A forwards INVITE to IBCF_A 7 100 Trying IBCF_A responds with a 100 Trying provisional response 8 INVITE IBCF_A forwards INVITE to IBCF_B 9 100 Trying IBCF_B responds with a 100 Trying provisional response INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE triggers the OIP IFC in IMS_B 12 INVITE IMS_B forwards the INVITE to IMS_B AS 13 100 Trying AS optionally responds with a 100 Trying provisional response 14 INVITE IMS_B AS returns, possibly modified, INVITE to IMS_B 15 100 Trying IMS_B responds with a 100 Trying provisional response 16 INVITE IMS_B forwards the INVITE to UE_B 17 100 Trying UE_B optionally responds with a 100 Trying provisional response 18 User B is informed of incoming call of User A, User A's identity is displayed 19 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 20 180 Ringing IMS_B forwards 180 Ringing response to IMS_B AS 21 180 Ringing IMS_B AS forwards 180 Ringing response to IMS_B 22 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 23 180 Ringing IBCF_B forwards the 180 Ringing response to IBCF_A 24 180 Ringing IBCF_A forwards the 180 Ringing response to IMS_A 25 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 26 User A is informed that UE_B is ringing 27 User B answers call 28 200 OK UE_B responds INVITE with 200 OK to indicate that the call has been answered 29 200 OK IMS_B forwards 200 OK response to IMS_B AS 30 200 OK IMS_B AS forwards 200 OK response 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 ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 229 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 33 200 OK IBCF_A forwards the 200 OK response to IMS_A 34 200 OK IMS_A forwards the 200 OK response to UE_A 35 User A is informed that call has been answered |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.4 Supplementary Service OIP with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0004 Summary: IMS network supports properly application services based on the example of the OIP supplementary service Configuration: CF_ROAM_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5097_02 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_08_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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B is registered in IMS_B via IMS_A using userOIP identity according to table 1 • IMS_B is configured to contact AS_B (OIP) • UE_B is subscribed to OIP service Test Sequence: Step 1 User A calls User B (i.e. userOIP in IMS_B) 2 Verify that user B is informed of incoming call of User A, user A's identity is displayed 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user B is informed that the call is established 7 User A ends call 8 Verify that user B is informed that call has ended 9 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_5097_02 in CFW step 8 (INVITE) ensure that { when { IMS_A receives an initial INVITE from UE_A addressed_to UE_B } then { IMS_A sends the initial INVITE to IMS_B containing a P-Asserted-Identity_header indicating the SIP_URI of UE_A and containing a P-Asserted-Identity_header indicating the Tel_URI of UE_A } } 2 TP_IMS_5108_03 in CFW step 12 (INVITE) ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 230 Interoperability Test Description 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 IUT_ 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 39 (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 IUT_ } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired media and codecs that 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 ENUM IMS_A sends query to ENUM DB 5 ENUM ENUM DB sends response to IMS_A 6 INVITE IMS_A forwards INVITE to IBCF_A 7 100 Trying IBCF_A responds with a 100 Trying provisional response 8 INVITE IBCF_A forwards INVITE to IBCF_B 9 100 Trying IBCF_B responds with a 100 Trying provisional response INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE triggers the OIP IFC in IMS_B 12 INVITE IMS_B forwards the INVITE to IMS_B AS 13 100 Trying AS optionally responds with a 100 Trying provisional response 14 INVITE IMS_B AS returns, possibly modified, INVITE to IMS_B 15 100 Trying IMS_B responds with a 100 Trying provisional response 16 INVITE IMS_B forwards the INVITE to IBCF_B ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 231 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 17 100 Trying IBCF_B responds with a 100 Trying provisional response 18 INVITE IBCF_B forwards INVITE to IBCF_A 19 100 Trying IBCF_A responds with a 100 Trying provisional response 20 INVITE IBCF_A forwards INVITE to IMS_A 21 100 Trying IMS_A responds with a 100 Trying provisional response 22 INVITE IMS_A forwards the INVITE to UE_B 23 100 Trying UE_B optionally responds with a 100 Trying provisional response 24 User B is informed of incoming call of User A, User A's identity is displayed 25 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has started alerting 26 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 27 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 28 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 29 180 Ringing IMS_B forwards 180 Ringing response to IMS_B AS 30 180 Ringing IMS_B AS forwards 180 Ringing response to IMS_B 31 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 32 180 Ringing IBCF_B forwards the 180 Ringing response to IBCF_A 33 180 Ringing IBCF_A forwards the 180 Ringing response to IMS_A 34 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 35 User A is informed that UE_B is ringing 36 User B answers call 37 200 OK UE_B responds INVITE with 200 OK to indicate that the call has been answered 38 200 OK IMS_A forwards 200 OK response to IBCF_A 39 200 OK IBCF_A forwards 200 OK response to IBCF_B 40 200 OK IBCF_B forwards 200 OK response to IMS_B 41 200 OK IMS_B forwards 200 OK response to IMS_B AS 42 200 OK IMS_B AS forwards 200 OK response to IMS_B 43 200 OK IMS_B forwards the 200 OK response to IBCF_B 44 200 OK IBCF_B forwards the 180 Ringing response to IBCF_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 232 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 45 200 OK IBCF_A forwards the 180 Ringing response to IMS_A 46 200 OK IMS_A forwards the 200 OK response to UE_A 47 User A is informed that call has been answered |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.5 Supplementary Services OIR and ACR with AS | Interoperability Test Description Identifier: TD_IMS_SS_0005 Summary: IMS network supports properly application services based on the example of the OIR and ACR supplementary services 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) TP_IMS_5313_01 TS 124 229 [1], clause 5.4.6.1.3 ¶2 Use Case ref.: UC_06_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 clause 4.2.1 • UE_A is registered in IMS_A using userOIR identity according to table 1 • UE_B is registered in IMS_B using any userACR identity according to table 1 • IMS_A is configured to contact AS_A (OIR) • UE_B is subscribed to ACR service • IMS_B is configured to contact AS_B (ACR) Test Sequence: Step 1 User A calls User B (i.e. userACR in IMS_B) 2 Verify that user A is informed that call has been rejected due to ACR Conformance Criteria: Check 1 TP_IMS_5108_03 in CFW step 16 (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 } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 233 Interoperability Test Description 2 TP_IMS_5313_01 in CFW step 22 (433 Anonymity Disallowed) 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 } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired media and 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 ENUM IMS_A sends query to ENUM DB 5 ENUM ENUM DB sends response to IMS_A INVITE triggers the OIR IFC in IMS_A 6 INVITE IMS_A forwards the INVITE to IMS_A AS 7 100 Trying IMS_A AS optionally responds with a 100 Trying provisional response 8 INVITE IMS_A AS returns modified INVITE including Privacy header (value "id" or 9 100 Trying IMS_A responds with a 100 Trying provisional response 10 INVITE IMS_A forwards INVITE to IBCF_A 11 100 Trying IBCF_A responds with a 100 Trying provisional response 12 INVITE IBCF_A forwards INVITE to IBCF_B 13 100 Trying IBCF_B responds with a 100 Trying provisional response 14 INVITE IBCF_B forwards INVITE to IMS_B 15 100 Trying IMS_B responds with a 100 Trying provisional response INVITE triggers the ACR IFC in IMS_B 16 INVITE IMS_B forwards the INVITE to IMS_B AS 17 100 Trying AS optionally responds with a 100 Trying provisional response 18 433 Anonymity IMS_B AS responds with 433 Anonymity Disallowed to IMS_B 19 433 Anonymity IMS_B forwards the 433 Anonymity Disallowed to IBCF_B 20 433 Anonymity IBCF_B forwards the 433 Anonymity Disallowed to IBCF_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 234 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 21 433 Anonymity IBCF_A forwards the 433 Anonymity Disallowed to IMS_A 22 433 Anonymity IMS_A forwards the 433 Anonymity Disallowed to IMS_A AS 23 433 Anonymity IMS_A AS forwards, possibly modified, 433 Anonymity Disallowed to IMS_A 24 433 Anonymity IMS_A forwards the 433 Anonymity Disallowed to UE_A 25 User A is informed that the call has been rejected due to ACR 26 ACK UE_A sends ACK to IMS_A 27 ACK IMS_A forwards the ACK to IMS_A AS 28 ACK IMS_A AS forwards, possibly modified, ACK to IMS_A 29 ACK IMS_A forwards ACK to IBCF_A 30 ACK IBCF_A forwards ACK to IBCF_B 31 ACK IBCF_B forwards ACK to IMS_B 32 ACK IMS_B forwards ACK to IMS_B AS |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.6 Supplementary Services OIR and ACR with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0006 Summary: IMS network supports properly application services based on the example of the OIR and ACR supplementary services Configuration: CF_ROAM_AS 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_06_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 clause 4.2.1 • UE_A is registered in IMS_A using any userACR identity according to table 1 • UE_B is registered in IMS_B via IMS_A using userOIR identity according to table 1 • UE_A is subscribed to ACR service • IMS_B is configured to contact AS_B (OIR) • IMS_A is configured to contact AS_A (ACR) • UE_B is subscribed to OIR service Test Sequence: Step 1 User B calls User A (i.e. userACR in IMS_B) 2 Verify that user B is informed that call has been rejected due to ACR ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 235 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 12 (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 U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired 3 100 Trying IMS_A responds with a 100 Trying provisional response ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 236 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 4 INVITE IMS_A sends INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A sends INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B sends INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 ENUM IMS B sends query to ENUM DB 11 ENUM ENUM DB sends response to IMS B INVITE triggers the OIR IFC in IMS_B 12 INVITE IMS_B forwards the INVITE to IMS_B AS 13 100 Trying IMS_B AS optionally responds with a 100 Trying provisional response 14 INVITE IMS_B AS returns modified INVITE including Privacy header (value "id" 15 100 Trying IMS_B responds with a 100 Trying provisional response 16 INVITE IMS_B forwards INVITE to IBCF_B 17 100 Trying IBCF_B responds with a 100 Trying provisional response 18 INVITE IBCF_B forwards INVITE to IBCF_A 19 100 Trying IBCF_A responds with a 100 Trying provisional response 20 INVITE IBCF_A forwards INVITE to IMS_A 21 100 Trying IMS_A responds with a 100 Trying provisional response INVITE triggers the ACR IFC in IMS_A 22 INVITE IMS_A forwards the INVITE to IMS_A AS 23 100 Trying AS optionally responds with a 100 Trying provisional response 24 433 Anonymity IMS_A AS responds with 433 Anonymity Disallowed to IMS_A 25 433 Anonymity IMS_A forwards the 433 Anonymity Disallowed to IBCF_A 26 433 Anonymity IBCF_A forwards the 433 Anonymity Disallowed to IBCF_B 27 433 Anonymity IBCF_B forwards the 433 Anonymity Disallowed to IMS_B 28 433 Anonymity IMS_B forwards the 433 Anonymity Disallowed to IMS_B AS 29 433 Anonymity IMS_B AS forwards, possibly modified, 433 Anonymity Disallowed ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 237 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 30 433 Anonymity IMS_B forwards the 433 Anonymity Disallowed to IBCF_B 31 433 Anonymity IBCF_B forwards the 433 Anonymity Disallowed to IBCF_A 32 433 Anonymity IBCF_A forwards the 433 Anonymity Disallowed to IMS_A 33 433 Anonymity IMS_A forwards the 433 Anonymity Disallowed to UE_B 34 User B is informed that the call has been rejected due to ACR 35 ACK UE_B sends ACK to IMS_A 36 ACK IMS_A sends ACK to IBCF_A 37 ACK IBCF_A sends ACK to IBCF_B 38 ACK IBCF_B sends ACK to IMS_B 39 ACK IMS_B forwards the ACK to IMS_B AS 40 ACK IMS_B AS forwards, possibly modified, 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 IMS_A AS |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.7 Supplementary Service CFU with AS | Interoperability Test Description Identifier: TD_IMS_SS_0007 Summary: IMS network supports properly application services based on the example of the CFU supplementary service 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_11_I Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B2 have IP bearers established to IMS_B as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B2 is registered in IMS_B using any user identity • IMS_B is configured to contact AS_B (CFU) for userCFU • UE_B1 is subscribed to IMS_B and has activated CFU service ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 238 Interoperability Test Description Test Sequence: Step 1 User A calls User B (i.e. userCFU in IMS_B) 2 User A may be informed of call diversion 3 User B2 answers call 4 Verify that user A is informed that call has been answered 6 Verify that user B2 is informed that call is established 7 User A ends call 8 Verify that user B2 is informed that call has ended 9 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 8 (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 12 (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 30 (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 U s e r B2 U E B2 I M S A E N U M DB I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 ENUM IMS_A sends query to ENUM DB ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 239 Step Direction Message Comment U s e r A U E A U s e r B2 U E B2 I M S A E N U M DB I B C F A I B C F B I M S B A S B 5 ENUM ENUM DB sends response to IMS_A 6 INVITE IMS_A forwards INVITE to IBCF_A 7 100 Trying IBCF_A responds with a 100 Trying provisional response 8 INVITE IBCF_A forwards INVITE to IBCF_B 9 100 Trying IBCF_B responds with a 100 Trying provisional response 10 INVITE IBCF_B forwards INVITE to IMS_B 11 100 Trying IMS_B responds with a 100 Trying provisional response INVITE triggers the CFU IFC in IMS_B 12 INVITE IMS_B forwards the INVITE to AS_B 13 100 Trying AS_B optionally responds with the 100 Trying to IMS_B AS_B applies the CDIV CFU procedure 14 181 Call is being AS_B indicates optionally to IMS_B that call has been 15 181 Call is being IMS_B indicates to IBCF_B that call has been forwarded 16 181 Call is being IBCF_B indicates to IBCF_A that call has been forwarded 17 181 Call is being IBCF_A indicates to IMS_A that call has been forwarded 18 181 Call is being IMS_A indicates that call to UE_B has been forwarded 19 User A may be informed of call diversion 20 INVITE AS_B returns modified INVITE including new request URI and 21 100 Trying IMS_B responds with a 100 Trying provisional response 22 INVITE IMS_B forwards the INVITE to UE_B2 23 100 Trying UE_B2 optionally responds with a 100 Trying provisional response 24 User B2 is informed of incoming call of User A 25 User B2 answers call 26 200 OK UE_B2 responds to INVITE with 200 OK to indicate that the call 27 200 OK IMS_B forwards 200 OK response to AS_B 28 200 OK AS_B returns, possibly modified, 200 OK to IMS_B 29 200 OK IMS_B forwards 200 OK response to IBCF_B 30 200 OK IBCF_B forwards 200 OK response to IBCF_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 240 Step Direction Message Comment U s e r A U E A U s e r B2 U E B2 I M S A E N U M DB I B C F A I B C F B I M S B A S B 31 200 OK IBCF_A forwards 200 OK response to IMS_A 32 200 OK IMS_A forwards 200 OK response to UE_A 33 User A is informed that call has been answered |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.8 Supplementary Service CFU with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0008 Summary: IMS network supports properly application services based on the example of the CFU supplementary service Configuration: CF_ROAM_AS 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_5070_01 TS 124 229 [1], clause 5.2.7.3 ¶3 TP_IMS_5110_01 TS 124 229 [1], clause 5.4.3.3 ¶79 (after 6th dashed list) Use Case ref.: UC_11_R Pre-test conditions: • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A and UE_B2 have IP bearers established to IMS_B as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • UE_B2 is registered in IMS_B via IMS_A using any user identity • IMS_A is configured to contact AS_A (CFU) for userCFU • UE_A1 is subscribed to IMS_A and has activated CFU service Test Sequence: Step 1 User B calls User A (i.e. userCFU in IMS_A) 2 User B may be informed of call diversion 3 User A2 answers call 4 Verify that user B is informed that call has been answered 6 Verify that user A2 is informed that call is established 7 User B ends call 8 Verify that user A2 is informed that call has ended 9 Verify that user B is informed that call has ended ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 241 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_5070_01 in CFW step 15 (100 Trying) ensure that { when { IMS_A receives an initial INVITE from UE_B } then { IMS_A sends a 100_response to IMS_B } } 4 TP_IMS_5110_01 in CFW step 39 (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 A2 U E A2 U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S A 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired media and 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 ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 242 Step Direction Message Comment U s e r A2 U E A2 U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S A 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 ENUM IMS_A sends query to ENUM DB 11 ENUM ENUM DB sends response to IMS_A 12 INVITE IMS_B forwards INVITE to IBCF_B 13 100 Trying IBCF_B responds with a 100 Trying provisional response 14 INVITE IBCF_B forwards INVITE to IBCF_A 15 100 Trying IBCF_A responds with a 100 Trying provisional response 16 INVITE IBCF_A forwards INVITE to IMS_A 17 100 Trying IMS_A responds with a 100 Trying provisional response INVITE triggers the CFU IFC in IMS_A 18 INVITE IMS_A forwards the INVITE to IMS_A AS 19 100 Trying IMS_A AS optionally responds with the 100 Trying to IMS_A IMS_A AS applies the CDIV CFU procedure 20 181 Call is being IMS_A AS indicates optionally to IMS_A that call has been forwarded 21 181 Call is being IMS_A indicates to IBCF_A that call has been forwarded 22 181 Call is being IBCF_A indicates to IBCF_B that call has been forwarded 23 181 Call is being IBCF_B indicates to IMS_B that call has been forwarded 24 181 Call is being IMS_B indicates to IBCF_B that call has been forwarded 25 181 Call is being IBCF_B indicates to IBCF_A that call has been forwarded 26 181 Call is being IBCF_A indicates to IMS_A that call has been forwarded 27 181 Call is being IMS_A indicates to UE_B that call to UE_A has been forwarded 28 User B may be informed of call diversion 29 INVITE IMS_A AS returns modified INVITE including new request URI and history 30 100 Trying IMS_A responds with a 100 Trying provisional response 31 INVITE IMS_A forwards the INVITE to UE_A2 32 100 Trying UE_A2 optionally responds with a 100 Trying provisional response ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 243 Step Direction Message Comment U s e r A2 U E A2 U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S A 33 User A2 is informed of incoming call of User B 34 User A2 answers call 35 200 OK UE_A2 responds to INVITE with 200 OK to indicate that the call has been 36 200 OK IMS_A forwards 200 OK response to IMS_A AS 37 200 OK IMS_A AS returns, possibly modified, 200 OK to IMS_A 38 200 OK IMS_A forwards 200 OK response to IBCF_A 39 200 OK IBCF_A forwards 200 OK response to IBCF_B 40 200 OK IBCF_B forwards 200 OK response to IMS_B 41 200 OK IMS_B forwards 200 OK response to IBCF_B 42 200 OK IBCF_B forwards 200 OK response to IBCF_A 43 200 OK IBCF_A forwards 200 OK response to IMS_A 44 200 OK IMS_A forwards 200 OK response to UE_B 45 User B is informed that call has been answered |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.9 Supplementary Services OIP and OIR with AS | Interoperability Test Description Identifier: TD_IMS_SS_0009 Summary: IMS network supports properly application services based on the example of the OIP and OIR supplementary services Configuration: CF_INT_AS SUT: 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) Use Case ref.: UC_09_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 clause 4.2.1 • UE_A is registered in IMS_A using userOIR_priv identity according to table 1 • UE_B is registered in IMS_B using userOIP_priv identity according to table 1 • IMS_A is configured to contact AS_A (OIR) • UE_A is subscribed to OIR service • IMS_B is configured to contact AS_B (OIP) • UE_B is subscribed to OIP service ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 244 Test Sequence: Step 1 User A calls User B (i.e. userOIP in IMS_B) 2 Verify that user B is informed of incoming call of User A and User A's identity is not displayed 3 Verify that user A is informed that UE_A is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user B is informed that the call is established 7 User B ends call 8 Verify that user A is informed that call has ended 9 Verify that user B is informed that call has ended Conformance Criteria: Check 1 TP_IMS_5097_01 in CFW step 120 (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 16 (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 } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired media and 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 ENUM IMS B sends query to ENUM DB 5 ENUM ENUM DB sends response to IMS B INVITE triggers the OIR IFC in IMS_A 6 INVITE IMS_A forwards the INVITE to IMS_A AS 7 100 Trying IMS_A AS optionally responds with a 100 Trying provisional response ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 245 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 8 INVITE IMS_A AS returns modified INVITE including Privacy header (value "id" or 9 100 Trying IMS_A responds with a 100 Trying provisional response 10 INVITE IMS_A forwards the INVITE to IBCF_A 11 100 Trying IBCF_A responds with a 100 Trying provisional response 12 INVITE IBCF_A forwards the INVITE to IBCF_B 13 100 Trying IBCF_B responds with a 100 Trying provisional response 14 INVITE IBCF_B forwards the INVITE to IMS_B 15 100 Trying IMS_B responds with a 100 Trying provisional response INVITE triggers the OIP IFC in IMS_B 16 INVITE IMS_B forwards the INVITE to IMS_B AS 17 100 Trying IMS_B AS optionally responds with a 100 Trying provisional response 18 INVITE IMS_B AS returns modified INVITE including modified From and P- 19 100 Trying IMS_B responds with a 100 Trying provisional response 20 INVITE IMS_B forwards the INVITE to UE_B 21 100 Trying UE_B optionally responds with a 100 Trying provisional response 22 User B is informed of incoming call of User A, user A's identity is not 23 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that it has 24 180 Ringing IMS_B forwards the 180 Ringing to IMS_B AS 25 180 Ringing IMS_B AS forwards, possibly modified, 180 Ringing to IMS_B 26 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 27 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 28 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 29 180 Ringing IMS_A forwards 180 Ringing response to IMS_A AS 30 180 Ringing IMS_A AS forwards, possibly modified, 180 Ringing response to IMS_A 31 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 32 User A is informed that UE_B is ringing 33 User B answers call 34 200 OK UE_B responds INVITE with 200 OK to indicate that the call has been ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 246 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 35 200 OK IMS_B forwards the 200 OK to IMS_B AS 36 200 OK IMS_B AS forwards, possibly modified, 200 OK to IMS_B 37 200 OK IMS_B forwards 200 OK response to IBCF_B 38 200 OK IBCF_B forwards 200 OK response to IBCF_A 39 200 OK IBCF_A forwards 200 OK response to IMS_A 40 200 OK IMS_A forwards 200 OK response to IMS_A AS 41 200 OK IMS_A AS forwards, possibly modified, 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 call has been answered |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.10 Supplementary Services OIP and OIR with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0010 Summary: IMS network supports properly application services based on the example of the OIP and OIR supplementary services Configuration: CF_ROAM_AS 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_5097_09 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) TP_IMS_5308_01 TS 124 229 [1], clause 5.4.4.2.2 ¶2 TP_IMS_5308_02 TS 124 229 [1], clause 5.4.4.2.2 ¶2 TP_IMS_5067_01 TS 124 229 [1], clause 5.2.7.2 ¶5 Use Case ref.: UC_09_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 clause 4.2.1 • UE_A is registered in IMS_A using userOIP_priv identity according to table 1 • UE_B is registered in IMS_B via IMS_A using userOIR_priv identity according to table 1 • IMS_A is configured to contact AS_A (OIP) • UE_A is subscribed to OIP service • IMS_B is configured to contact AS_B (OIR) • UE_B is subscribed to OIR service Test Sequence: Step 1 User B calls User A (i.e. userOIP in IMS_A) 2 Verify that user A is informed of incoming call of User B and User B's identity is not displayed 3 Verify that user B is informed that UE_A is ringing 4 User A answers call 5 Verify that user B is informed that call has been answered 6 Verify that user A is informed that the call is established 7 User A ends call ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 247 Interoperability Test Description 8 Verify that user B is informed that call has ended 9 Verify that user A is informed that call has ended 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_5097_09 in CFW step 12 (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 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) } } 3 TP_IMS_5308_01 in CFW step 30 (180 ringing) ensure that { when { IMS_A receives a 180 response from UE_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } then { IMS_A sends the 180 response to AS_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } 3 TP_IMS_5308_02 in CFW step 44 (200 OK) ensure that { when { IMS_A receives a 200 response from UE_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } then { IMS_A sends the 200 response to AS_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 248 Interoperability Test Description 4 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 } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired 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 ENUM IMS B sends query to ENUM DB 11 ENUM ENUM DB sends response to IMS B INVITE triggers the OIR IFC in IMS_B 12 INVITE IMS_B forwards the INVITE to IMS_B AS 13 100 Trying IMS_B AS optionally responds with a 100 Trying provisional response 14 INVITE IMS_B AS returns modified INVITE including Privacy header (value "id" 15 100 Trying IMS_B responds with a 100 Trying provisional response 16 INVITE IMS_B forwards the INVITE to IBCF_B 17 100 Trying IBCF_B responds with a 100 Trying provisional response 18 INVITE IBCF_B forwards the INVITE to IBCF_A 19 100 Trying IBCF_A responds with a 100 Trying provisional response 20 INVITE IBCF_A forwards the INVITE to IMS_A 21 100 Trying IMS_A responds with a 100 Trying provisional response INVITE triggers the OIP IFC in IMS_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 249 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 22 INVITE IMS_A forwards the INVITE to IMS_A AS 23 100 Trying IMS_A AS optionally responds with a 100 Trying provisional response 24 INVITE IMS_A AS returns modified INVITE including modified From and P- 25 100 Trying IMS_A responds with a 100 Trying provisional response 26 INVITE IMS_A forwards the INVITE to UE_A 27 100 Trying UE_A optionally responds with a 100 Trying provisional response 28 User A is informed of incoming call of User B, user B's identity is not 29 180 Ringing UE_A responds to initial INVITE with 180 Ringing to indicate that it 30 180 Ringing IMS_A forwards the 180 Ringing to IMS_A AS 31 180 Ringing IMS_A AS forwards, possibly modified, 180 Ringing to IMS_A 32 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 33 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 34 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 35 180 Ringing IMS_B forwards 180 Ringing response to IMS_B AS 36 180 Ringing IMS_B AS forwards, possibly modified, 180 Ringing response to 37 180 Ringing IMS_B forwards the 180 Ringing response to IBCF_B 38 180 Ringing IBCF_B forwards the 180 Ringing response to IBCF_A 39 180 Ringing IBCF_A forwards the 180 Ringing response to IMS_A 40 180 Ringing IMS_A forwards the 180 Ringing response to UE_B 41 User B is informed that UE_A is ringing 42 User A answers call 43 200 OK UE_A responds INVITE with 200 OK to indicate that the call has been 44 200 OK IMS_A forwards the 200 OK to IMS_A AS 45 200 OK IMS_A AS forwards, possibly modified, 200 OK to IMS_A 46 200 OK IMS_A forwards 200 OK response to IBCF_A 47 200 OK IBCF_A forwards 200 OK response to IBCF_B 48 200 OK IBCF_B forwards 200 OK response to IMS_B 49 200 OK IMS_B forwards 200 OK response to IMS_B AS ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 250 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 50 200 OK IMS_B AS forwards, possibly modified, 200 OK response to 51 200 OK IMS_B forwards the 200 OK response to IBCF_B 52 200 OK IBCF_B forwards the 200 OK response to IBCF_A 53 200 OK IBCF_A forwards the 200 OK response to IMS_A 54 200 OK IMS_A forwards the 200 OK response to UE_B 55 User B is informed that call has been answered |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.11 Ad-hoc Conference Call service | Interoperability Test Description Identifier: TD_IMS_CONF_0001 Summary: IMS network handles subsequent INVITEs, UPDATEs, REFERs and NOTIFYs correctly during Ad-Hoc Conference calls Configuration: CF_INT_CONF_CALL SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5121_02 TS 124 229 [1], clause 5.4.3.3 ¶123 (9th numbered list) Use Case ref.: UC_16 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 clause 4.2.1 • UE_A is registered in IMS_A using any user identity • IMS_A is configured to contact AS_A (CONF) • UE_B is registered in IMS_B using any user identity • IMS_B is configured to contact AS_B (CONF) • User A and B are subscribed to CONF service • User A is pre-provisioned with conference-factory URI in IMS_A Test Sequence: Step 1 User A initiates an ad-hoc conference call with a pre-configured conference- factory URI 2 Verify that User A is informed the Ad Hoc Conference Call is being set up 3 Verify that User A is informed the Ad Hoc Conference Call is established 4 User A invites User B to join the Conference Call. 5 Verify that User B is informed of incoming invitation from User A to join the Conference Call 6 Verify that User A is informed that User B is being alerted 7 User B joins the Conference Call 8 Verify that User A is alerted when User B joins the Conference Call 9 User B leaves the Conference Call 10 Verify that User B is informed that the Conference Call has ended 11 Verify that User A is alerted when User B leaves the Conference Call ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 251 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5121_02 in CFW in step 36 & 46 (200 OK ): ensure that { when { UE_B sends a 1xx or 2xx_response to UE_A } then { IMS_A receives the 1xx or 2xx_response containing a P-Charging-Vector_header not containing a access-network-charging-info_parameter and not containing a P-Access-Network-Info_header } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 1 User A initiates an ad-hoc conference call 2 INVITE UE_A sends INVITE to IMS_A with information for all commonly supported presence elements 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 User A is informed the Ad Hoc Conference Call is being set up 5 INVITE IMS_A forwards INVITE to IMS_A AS 6 100 Trying IMS_A AS responds with a 100 Trying provisional response 7 200 OK IMS_A AS responds with a 200 OK to IMS_A, with isfocus parameter. 8 200 OK IMS_A forwards the 200OK response to UE_A 9 User A is informed the Ad Hoc Conference Call is established 10 ACK UE_A acknowledges the receipt of 200 OK for INVITE 11 ACK IMS_A forwards the ACK to IMS_A AS 12 User A invites user B to join the ad-hoc conference call 13 REFER UE_A sends REFER message to IMS_A, with Refer-To : <UE_B uri ;method=INVITE> 14 REFER IMS_A forwards the REFER to IMS_A AS 15 202 Accepted IMS_A AS responds with a 202 Accepted 16 202 Accepted IMS_A forwards the 202 Accepted response to UE_A 17 NOTIFY IMS_A AS sends a NOTIFY to IMS_A to inform the conference initiator the REFER message is being processed 18 NOTIFY IMS_A forwards the NOTIFY to UE_A 19 200 OK UE_A responds with 200 OK to IMS_A 20 200 OK IMS_A forwards the 200 OK response to IMS_A AS ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 252 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 21 INVITE IMS_A AS sends INVITE to UE_B with conference-factory URI (received in the REFER message from UE A) 22 100 Trying IMS_A responds with a 100 Trying provisional response 23 ENUM IMS_A sends query to ENUM DB 24 ENUM ENUM DB sends response to IMS_A 25 INVITE IMS_A forwards the INVITE to IBCF_A 26 100 Trying IBCF_A responds with a 100 Trying provisional response 27 INVITE IBCF_A forwards the INVITE to IBCF_B 28 100 Trying IBCF_B responds with a 100 Trying provisional response 29 INVITE IBCF_B forwards the INVITE to IMS_B 30 100 Trying IMS_B responds with a 100 Trying provisional response 31 INVITE IMS_B forwards the INVITE to UE_B 32 100 Trying UE_B responds with a 100 Trying provisional response 33 User B is informed of incoming invitation from User A to join the Conference Call 34 180 Ringing UE_B sends a 180 ringing to IMS_B 35 180 Ringing IMS_B forwards the 180 ringing to IBCF_B 36 180 Ringing IBCF_B forwards the 180 ringing to IBCF_A 37 180 Ringing IBCF_A forwards the 180 ringing to IMS_A 38 180 Ringing IMS_A forwards the 180 ringing to IMS_A AS 39 NOTIFY Upon reception of 180 Ringing from UE_B, IMS_A AS sends NOTIFY with sipfrag: 180 Ringing to inform conference initiator that UE_B is being invited to join the conference 40 NOTIFY IMS_A forwards the NOTIFY to UE_A 41 User A is notified that User B is being invited to join the call 42 200 OK UE_A responds with 200 OK to IMS_A for NOTIFY 43 200 OK IMS_A forwards the 200 OK response to IMS_A AS 44 200 OK UE_B responds with 200 OK to IMS_B for INVITE 45 200 OK IMS B forwards the 200 OK response to IBCF_B 46 200 OK IBCF_B forwards the 200 OK response to IBCF_A 47 200 OK IBCF_A forwards the 200 OK response to IMS_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 253 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 48 200 OK IMS_A forwards the 200 OK response to IMS_A AS 49 User B joins the conference 50 ACK UE_B acknowledges the 200 OK for INVITE 51 ACK IMS B forwards the ACK to IBCF_B 52 ACK IBCF_B forwards the ACK to IBCF_A 53 ACK IBCF_A forwards the ACK to IMS_A 54 ACK IMS_A forwards the ACK to IMS_A AS 55 NOTIFY AS_A sends NOTIFY to UE_A to inform it has successfully joined the conference 56 NOTIFY IMS_A forwards NOTIFY to UE_A 57 User A is alerted that User B has joined the conference 58 200 OK UE_A sends 200 OK response for NOTIFY 59 200 OK IMS_A forwards the 200 OK response to IMS_A AS 60 User B leaves the conference 61 BYE UE_B sends BYE to IMS_B to leave the conference 62 BYE IMS_B forwards the BYE to IBCF_B 63 BYE IBCF_B forwards the BYE to IBCF_A 64 BYE IBCF_A forwards the BYE to IMS_A 65 BYE IMS_A forwards the BYE to IMS_A AS 66 200 OK IMS_A AS releases resources for this conference caller and sends a 200 OK response for BYE 67 200 OK IMS_A forwards the 200 OK response to IBCF_A 68 200 OK IBCF_A forwards the 200 OK response to IBCF_B 69 200 OK IBCF_B forwards the 200 OK response to IMS_B 70 200 OK IMS_B forwards the 200 OK response to UE_B 71 User B is informed that the conference has ended 72 NOTIFY AS_A sends NOTIFY to IMS _A to inform UE_A that UE_B has left the conference 73 NOTIFY IMS_A forwards NOTIFY to UE_A 74 User A is notified that user B has left the conference 75 200 OK UE_A sends a 200 OK response for NOTIFY 76 200 OK IMS_A forwards the 200 OK response to IMS_A AS ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 254 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.6 Presence | The test descriptions for the presence service are defined in TS 102 901 [17]. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7 IPTV | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.1 IPTV registration and Service Attachment. Push mode | Interoperability Test Description Identifier: TD_IMS_IPTV_0001 Summary: IMS network supports properly IPTV registration and service attachment in Push mode Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5206_01 TS 124 229 [1], clause 5.4.1.2.2 F ¶15 (before NOTE 3) TP_IMS_5308_02 TS 124 229 [1], clause 5.4.4.2.2 ¶2 Use Case ref.: Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its respective IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using userIPTV according to table 1 • IMS_A is configured to send a third party register to AS_A (SDF) • IMS_A not configured for topology hiding Test Sequence: Step 29 Verify that user A receives service attachment information Conformance Criteria: Check 1 TP_IMS_5206_01 in CFW step 23 (REGISTER) ensure that { when { IMS_A receives a protected REGISTER containing an Authorization header containing a integrity protected parameter indicating (yes or tls-pending or tls-yes or ip-assoc-pending or ip-assoc-yes)} then { IMS_A sends a third party register to AS_A containing a P-Access-Network-Info header containing a P-Visited-Network-ID header } } 2 TP_IMS_5308_02 in CFW step 28 (200 OK) ensure that { when { IUT receives a 200_response from UE_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } then { IUT sends the 200_response to AS_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 255 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I M S B A S B IMS_A matches the iFC of the service profile belong to the user, and find out the AS (SDF) that user has subscribed 23 REGISTER IMS_A sends a REGISTER to AS_A (third party registration) 24 200 OK AS_A responds with 200 OK 25 MESSAGE AS_A sends a MESSAGE containing the service attachment information 26 MESSAGE IMS_A forwards the MESSAGE to UE_A 27 200 OK UE_A responds with 200 OK 28 200 OK IMS_A forwards the 200 OK response to AS_A 29 UE receives service attachment information |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.2 IPTV registration and Service Attachment. Pull mode. | Interoperability Test Description Identifier: TD_IMS_IPTV_0002 Summary: IMS network supports properly IPTV registration and service attachment in Pull mode Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5097_14 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) TP_IMS_5308_02 TS 124 229 [1], clause 5.4.4.2.2 ¶2 Use Case ref.: Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its respective IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using userIPTV according to table 1 • UE_A, IMS_A, AS_A support pull mode service discovery • IMS_A not configured for topology hiding Test Sequence: Step 31 Verify that user A receives service attachment information Conformance Criteria: Check 1 TP_IMS_5097_14 in CFW step 24 (SUBSCRIBE): ensure that { when { IMS_A sends the SUBSCRIBE to AS_A } then { AS_A receives the SUBSCRIBE containing a Route_header indicating the SIP_URI of AS_A containing a P-Charging-Function-Addresses_header containing a P-Charging-Vector_header (including a orig-ioi_parameter indicating IMS_A and not including a term-ioi_parameter and including access-network-charging-info)} } 2 TP_IMS_5308_02 in CFW step 30 (200 OK) ensure that { when { IUT receives a 200_response from UE_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter } then { IUT sends the 200_response to AS_A containing a P-Charging-Vector_header including an access-network-charging-info_parameter ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 256 Interoperability Test Description } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I M S B A S B UE retrieves the PSI/address of AS_A (SDF) 23 SUBSCRIBE UE_A sends a SUBSCRIBE for "ua-profile" event to IMS_A 24 SUBSCRIBE IMS_A forwards the SUBSCRIBE to AS_A 25 200 OK AS_A responds with 200OK 26 200 OK IMS_A forwards the 200 OK response to UE_A 27 NOTIFY AS_A sends a NOTIFY for the service attachment information to IMS_A 28 NOTIFY IMS_A forwards the NOTIFY to UE_A 29 200 OK UE_A responds with 200 OK 30 200 OK IMS_A forwards the 200 OK response to AS_A 31 UE receives service attachment information |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.3 BC session | Interoperability Test Description Identifier: TD_IMS_IPTV_0003 Summary: IMS network supports properly IPTV Broadcast session Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.2 ¶5 (item 4 in 1st numbered list) TP_IMS_5107_02 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Use Case ref.: UC_19 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its respective IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using userIPTV according to table 1 • UE_A has done IPTV registration and service attachment procedures using push or pull mode • IMS_A not configured for topology hiding Test Sequence: Step 1 User A initiates a BC session 11 Verify that user A receives the broadcast content 12 User A terminates the session 19 Verify that user A is informed that session is terminated ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 257 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5108_03 in CFW step 3 (INVITE) ensure that { when { IUT receives an initial INVITE from IMS_A} then { IUT sends the initial INVITE to AS_A containing a topmost Route_header indicating the SIP_URI of AS_A and containing a Route_header indicating the S-CSCF SIP_URI of IMS_A 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 } } 2 TP_IMS_5107_02 in CFW step 7 (ACK) ensure that { when { UE_A sends ACK to addressed to UE_B} then { IMS_B receives the ACK not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A and not containing a P-Access-Network-Info_header } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I M S B A S B 1 User A initiates a BC session 2 INVITE UE_A sends a INVITE to IMS_A 3 INVITE IMS_A forwards the INVITE to AS_A 4 200 OK AS_A responds with 200 OK 5 200 OK IMS_A forwards the 200 OK response to UE_A 6 ACK UE_A acknowledges the receipt of 200 OK for INVITE 7 ACK IMS_A forwards the ACK to AS_A 8 User A receives the broadcast content 9 User A terminates the session 10 BYE UE_A sends a BYE to IMS_A 11 BYE IMS_A forwards the BYE to AS_A 12 200 OK AS_A responds with 200 OK 13 200 OK IMS_A forwards the 200 OK response to UE_A 14 User A is informed that session is terminated ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 258 4.5.7.4 CoD session. Establishing content control channel and content delivery channels using RTSP Method 1 Interoperability Test Description Identifier: TD_IMS_IPTV_0004 Summary: IMS network supports properly IPTV content on demand session Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.2 ¶5 (item 4 in 1st numbered list) TP_IMS_5107_02 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Use Case ref.: UC_20 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its respective IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using userIPTV according to table 1 • UE_A has done IPTV registration and service attachment procedures using push or pull mode • UE_A, IMS_A and AS_A are configured to establish content control channel and content delivery channels using RTSP method 1 • IMS_A not configured for topology hiding Test Sequence: Step 1 User A initiates a CoD session (content selection) 26 Verify that user A starts receiving the streaming content 27 User A terminates the session 36 Verify that user A is informed that session is terminated Conformance Criteria: Check 1 TP_IMS_5108_03 in CFW step 3 (INVITE) ensure that { when { IUT receives an initial INVITE from IMS_A} then { IUT sends the initial INVITE to AS_A containing a topmost Route_header indicating the SIP_URI of AS_A and containing a Route_header indicating the S-CSCF SIP_URI of IMS_A 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 } } 2 TP_IMS_5107_02 in CFW step 11 (ACK) ensure that { when { UE_A sends ACK to addressed to UE_B} then { IMS_B receives the ACK not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A and not containing a P-Access-Network-Info_header } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 259 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I M S B A S B 1 User A initiates a CoD session (content selection) 2 INVITE UE_A sends a INVITE to IMS_A 3 INVITE IMS_A forwards the INVITE to AS_A (SCF) 4 INVITE AS_A forwards the INVITE to IMS_A 5 INVITE IMS_A forwards the INVITE to AS_A (MF) 6 200 OK AS_A (MF) responds with 200 OK 7 200 OK IMS_A forwards the 200 OK response to AS_A (SCF) 8 200 OK AS_A forwards the 200 OK response to IMS_A 9 200 OK IMS_A forwards the 200 OK response to UE_A 10 ACK UE_A acknowledges the receipt of 200 OK for INVITE 11 ACK IMS_A forwards the ACK to AS_A (SCF) 12 ACK AS_A forwards the ACK to IMS_A 13 ACK IMS_A forwards the ACK to AS_A (MF) UE_A sets up RTSP with AS_A (MF) 14 INVITE UE_A sends reINVITE message indicating media attribute "a=recvonly" 15 INVITE IMS_A forwards the reINVITE to AS_A 16 INVITE AS_A forwards the reINVITE to IMS_A 17 INVITE IMS_A forwards the reINVITE to AS_A (MF) 18 200 OK AS_A (MF) responds with 200 OK 19 200 OK IMS_A forwards the 200 OK response to AS_A (SCF) 20 200 OK IMS_B forwards the 200 OK response to IMS_A 21 200 OK IMS_A forwards the 200 OK response to UE_A 22 ACK UE_A acknowledges the receipt of 200 OK for reINVITE 23 ACK IMS_A forwards the ACK to AS_A (SCF) 24 ACK AS_A forwards the ACK to IMS_A 25 ACK IMS_A forwards the ACK to AS_A (MF) 26 User A starts receiving the streaming content 27 User A terminates the session ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 260 Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I M S B A S B 28 BYE UE_A sends a BYE to IMS_A 29 BYE IMS_A forwards the BYE to AS_A (SCF) 30 BYE AS_A forwards the BYE to IMS_A 31 BYE IMS_A forwards the BYE to AS_A (MF) 32 200 OK AS_A (MF) responds with 200 OK 33 200 OK IMS_A forwards the 200 OK response to AS_A (SCF) 34 200 OK IMS_B forwards the 200 OK response to IMS_A 35 200 OK IMS_A forwards the 200 OK response to UE_A 36 User A is informed that session is terminated 4.5.7.5 CoD session. Establishing content control channel and content delivery channels using RTSP Method 2 Interoperability Test Description Identifier: TD_IMS_IPTV_0005 Summary: IMS network supports properly IPTV content on demand session Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.2 ¶5 (item 4 in 1st numbered list) TP_IMS_5107_02 TS 124 229 [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Use Case ref.: UC_21 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its respective IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using userIPTV • UE_A has done IPTV registration and service attachment procedures using push or pull mode • UE_A, IMS_A and AS_A are configured to establish content control channel and content delivery channels with RTSP method 2 • IMS_A not configured for topology hiding Test Sequence: Step 1 User A initiates a CoD session (content selection) 32 Verify that user A starts receiving the streaming content ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 261 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_5108_03 in CFW step 3 (INVITE) ensure that { when { IUT receives an initial INVITE from IMS_A} then { IUT sends the initial INVITE to AS_A containing a topmost Route_header indicating the SIP_URI of AS_A and containing a Route_header indicating the S-CSCF SIP_URI of IMS_A 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 } } 2 TP_IMS_5107_02 in CFW step 11 (ACK) ensure that { when { UE_A sends ACK to addressed to UE_B} then { IMS_B receives the ACK not containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A and not containing a P-Access-Network-Info_header } } Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I M S B A S B 1 User A initiates a CoD session (content selection) 2 INVITE UE_A sends a INVITE to IMS_A 3 INVITE IMS_A forwards the INVITE to AS_A (SCF) 4 INVITE AS_A forwards the INVITE to IMS_A 5 INVITE IMS_A forwards the INVITE to AS_A (MF) 6 200 OK AS_A (MF) responds with 200 OK 7 200 OK IMS_A forwards the 200 OK response to AS_A (SCF) 8 200 OK AS_A forwards the 200 OK response to IMS_A 9 200 OK IMS_A forwards the 200 OK response to UE_A 10 ACK UE_A acknowledges the receipt of 200 OK for INVITE 11 ACK IMS_A forwards the ACK to AS_A (SCF) 12 ACK AS_A forwards the ACK to IMS_A 13 ACK IMS_A forwards the ACK to AS_A (MF) 14 UE_A starts receiving the streaming content ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 262 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.6 Request for Network PVR offline capture in home network | Interoperability Test Description Identifier: TD_IMS_IPTV_0006 Summary: IMS network supports properly N-PVR offline capture requests Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5108_04 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) Use Case ref.: UC_22 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its respective IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using userIPTV according to table 1 • UE_A has done IPTV registration and service attachment procedures using either push or pull mode • IMS_A not configured for topology hiding Test Sequence: Step 1 User A requests to record a live programme that has not started yet 6 Verify that user A is informed that recording has started Conformance Criteria: Check 1 TP_IMS_5108_04 in CFW step 3 (MESSAGE): ensure that { when { IMS_A receives a MESSAGE from UE_A } then { IMS_A sends the MESSAGE to AS_A containing a topmost Route_header indicating the SIP_URI of AS_A and containing a Route_header indicating the S-CSCF_SIP_URI of IMS_A 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 U s e r B U E B I M S A A S A I M S B A S B 1 User a requests to record a live programme that has not started yet 2 MESSAGE UE_A sends a MESSAGE to IMS_A 3 MESSAGE IMS_A forwards the MESSAGE to AS_A 4 200 OK AS_A responds with 200 OK 5 200 OK IMS_A forwards the 200 OK response to UE_A 6 User A is informed that recording has started ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 263 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8 IMS-PSTN Interoperability | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1 IMS-to-PSTN call | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.1 ENUM Query - IMS-to-PSTN call | Interoperability Test Description Identifier: TD_IMS_ENUM_0002 Summary: ENUM query should result in return of NAPTR with correct Tel URI Configuration: CF_INT_CALL SUT: ENUM _A and ENUM_DB References: Test Purpose Specification Reference TP_IMS_ENUM_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 10 in 1st numbered list) Use Case ref.: UC_I_23 Pre-test conditions: • ENUM DB is configured according to table 1 • IMS_A is configured to support ENUM • HSS of IMS_A and of IMS B is configured according to table 1 • UE_A has IP bearer established to its respective IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity Test Sequence: Step 1 User A calls user B 2 User B is informed about incoming call of user B Conformance Criteria: Check 1 TP_IMS_ENUM_01 in CFW step 4 (NAPTR Response): ensure that { when { UE_A sends an initial INVITE for UE_B to IMS_A containing a Request_URI indicating a Tel_URI and IMS_A sends a NAPTR_Query to ENUM_DB containing the TN derived_from the Tel_URI_E.164_Number } then { ENUM_DB sends a NAPTR_Response to IMS_A containing a NAPTR_Resource_Record containing the TTL of the NAPTR_record containing the service_type indicating E2U+sip containing the_regular_expressiob indicating !^(.*)$! containing the SIP_URI of UE_B indicating backreference (\1) for the user part indicating domain name for the host part containing SIP_URI_parameters 'if applicable' } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired medias and codecs that 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 264 Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 5 100 Trying IMS_A responds with a 100 Trying provisional response 6 INVITE IMS_A forwards INVITE to MGCF 7 100 Trying MGCF responds with a 100 Trying provisional response 8 183 Session Progress MGCF responds with 183 Session Progress response 9 183 Session Progress IMS_forwards 183 Session Progress response to UE_A 10 PRACK UE_A sends PRACK to IMS_A 11 PRACK IMS_A forwards PRACK to MGCF 12 200 OK (PRACK) MGCF responds with 200 OK response to IMS_A 13 200 OK (PRACK) IMS_A forwards 200 OK response to UE_A 14 IAM MGCF sends IAM to PSTN 15 User B is informed of incoming call of User A |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.2 Normal Call, PSTN user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0001 Summary: Outgoing call to PSTN, PSTN user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_02 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_03 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_06 TS 124 229 [1], clause 5.5.3.2.2 TS 129 163 [18], clause 7.2.3.1.4 TP_IMS_MGCF_07 TS 124 229 [1], clause 5.4.1.2.2 TS 129 163 [18], clause 7.2.3.1.5 TP_IMS_MGCF_08 TS 124 229 [1], clause 5.5.4.1 TS 129 163 [18], clause 7.2.3.1.8 Use Case ref.: UC_23 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A Test Sequence: Step 1 User A calls User B 2 Verify that user B is informed of incoming call of User A 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user A and B can communicate 7 User B ends call 8 Verify that user B is informed that call has ended 9 Verify that user A is informed that call has ended ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 265 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_MGCF_02 in CFW step 7 (100 Trying): ensure that { when { IUT receives an initial INVITE from IAM_A} then { IUT sends a 100_response to IMS_A } } 2 TP_IMS_MGCF_03 in CFW step 7 and 8 (183 Session Progress): ensure that { when { IUT receives an initial INVITE from IMS_A } then { IUT sends a 100_response to IMS_A and sends 183_response to IMS_A containing Require_header indicating 100rel_value and containing a P-Charging-Vector_header including a term-ioi_parameter indicating the operator_identifier of IMS_A } } 3 TP_IMS_MGCF_06 in CFW step 17 (180 Ringing): ensure that { when { IUT receives an ACM indicating subscriber_free or receives a CPG indicating ALERTING from PSTN } then { IUT sends a 180_response to IMS_A } } 4 TP_IMS_MGCF_07 in CFW step 22 (200 OK): ensure that { when { IUT receives an ANM from PSTN} then { IUT sends a 200_response to IMS_A } } 5 TP_IMS_MGCF_08 in CFW step 32B (BYE): ensure that { when { IUT receives an REL from PSTN} then { IUT sends a BYE to IMS_A } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired medias and codecs that 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 ENUM IMS_A sends query to ENUM DB 5 ENUM ENUM DB sends response to IMS_A 6 INVITE IMS_A forwards INVITE to MGCF 7 100 Trying MGCF responds with a 100 Trying provisional response 8 183 Session Progress MGCF responds with 183 Session Progress response 9 183 Session Progress IMS_forwards 183 Session Progress response to UE_A 10 PRACK UE_A sends PRACK to IMS_A ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 266 Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 11 PRACK IMS_A forwards PRACK to MGCF 12 200 OK (PRACK) MGCF responds with 200 OK response to IMS_A 13 200 OK (PRACK) IMS_A forwards 200 OK response to UE_A 14 IAM MGCF sends IAM to PSTN 15 User B is informed of incoming call of User A 16 ACM/CPG PSTN responds with ACM/CPG 17 180 Ringing MGCF sends 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User A is informed that UE_B is ringing 20 User B answers call 21 ANM PSTN sends ANM to MGCF 22 200 OK MGCF sends 200 OK response to IMS_A 23 200 OK IMS_A forwards 200 OK response to UE_A 24 User A is informed that call has been answered 25 ACK UE_A acknowledges the receipt of 200 OK for INVITE 26 ACK IMS_A forwards ACK to MGCF 27 User A and B can communicate 28B User B ends call 29B REL PSTN sends BYE to MGCF 30B RLC MGCF responds RLC to PSTN 31B User B is informed that call has ended 32B BYE MGCF sends BYE to IMS_A 33B BYE IMS_A forwards BYE to UE_A 34B User A is informed that call has ended 35B 200 OK UE_A sends 200 OK for BYE 36B 200 OK IMS_A forwards 200 OK response to MGCF ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 267 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.3 Normal Call, IMS user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0002 Summary: Outgoing call to PSTN, IMS user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_02 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_03 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_06 TS 124 229 [1], clause 5.5.3.2.2 TS 129 163 [18], clause 7.2.3.1.4 TP_IMS_MGCF_07 TS 124 229 [1], clause 5.4.1.2.2 TS 129 163 [18], clause 7.2.3.1.5 TP_IMS_MGCF_17 TS 129 163 [18], clause 7.2.3.2.13 Use Case ref.: UC_23 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A Test Sequence: Step 1 User A calls User B 2 Verify that user B is informed of incoming call of User A 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user A and B can communicate 7 User A ends call 8 Verify that user B is informed that call has ended 9 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_MGCF_02 in CFW step 7 (100 Trying): ensure that { when { IUT receives an initial INVITE from IAM_A} then { IUT sends a 100_response to IMS_A } } 2 TP_IMS_MGCF_03 in CFW step 7 and 8 (183 Session Progress): ensure that { when { IUT receives an initial INVITE from IMS_A } then { IUT sends a 100_response to IMS_A and sends 183_response to IMS_A containing Require_header indicating 100rel_value and containing a P-Charging-Vector_header including a term-ioi_parameter indicating the operator_identifier of IMS_A } } 3 TP_IMS_MGCF_06 in CFW step 17 (180 Ringing): ensure that { when { IUT receives an ACM indicating subscriber_free or receives a CPG indicating ALERTING from PSTN } then { IUT sends a 180_response to IMS_A } } 4 TP_IMS_MGCF_07 in CFW step 22 (200 OK): ensure that { when { IUT receives an ANM from PSTN} then { IUT sends a 200_response to IMS_A } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 268 Interoperability Test Description 5 TP_IMS_MGCF_29A in CFW step 31A (REL): ensure that { when { IUT receives a BYE from IMS_A } then { IUT sends an REL to PSTN } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired medias and codecs that 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 ENUM IMS_A sends query to ENUM DB 5 ENUM ENUM DB sends response to IMS_A 6 INVITE IMS_A forwards INVITE to MGCF 7 100 Trying MGCF responds with a 100 Trying provisional response 8 183 Session Progress MGCF responds with 183 Session Progress response 9 183 Session Progress IMS_forwards 183 Session Progress response to UE_A 10 PRACK UE_A sends PRACK to IMS_A 11 PRACK IMS_A forwards PRACK to MGCF 12 200 OK (PRACK) MGCF responds with 200 OK response to IMS_A 13 200 OK (PRACK) IMS_A forwards 200 OK response to UE_A 14 IAM MGCF sends IAM to PSTN 15 User B is informed of incoming call of User A 16 ACM/CPG PSTN responds with ACM/CPG 17 180 Ringing MGCF sends 180 Ringing response to IMS_A 18 180 Ringing IMS_A forwards the 180 Ringing response to UE_A 19 User A is informed that UE_B is ringing 20 User B answers call 21 ANM PSTN sends ANM to MGCF 22 200 OK MGCF sends 200 OK response to IMS_A 23 200 OK IMS_A forwards 200 OK response to UE_A 24 User A is informed that call has been answered ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 269 Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 25 ACK UE_A acknowledges the receipt of 200 OK for INVITE 26 ACK IMS_A forwards ACK to MGCF 27 User A and B can communicate 28A User A ends call 29A BYE UE_A sends BYE 30A BYE IMS_A forwards BYE to MGCF 31A REL MGCF sends REL to PSTN 32A User B is informed that call has ended 33A RLC PSTN sends RLC response to MGCF 34A 200 OK MGCF sends 200 OK response to IMS_A 35A 200 OK IMS_A forwards the 200 OK response to UE_A 36A User A is informed that call has ended |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.4 Unsuccessful Call, PSTN user busy | Interoperability Test Description Identifier: TD_IMS_PSTN_0003 Summary: Outgoing call to PSTN, user B busy Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_02 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_09 TS 129 163 [18], clause 7.2.3.1.8 Use Case ref.: UC_23 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A • User B in the PSTN is busy Test Sequence: Step 1 User A calls User B 2 Verify that user A is informed that User B is busy Conformance Criteria: Check 1 TP_IMS_MGCF_02 in CFW step 8 (100 Trying): ensure that { when { IUT receives an initial INVITE from IAM_A} then { IUT sends a 100_response to IMS_A } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 270 Interoperability Test Description 2 TP_IMS_MGCF_09 in CFW step 18 (486 Busy Here): ensure that { when { IUT receives an REL with cause17 from PSTN} then { IUT sends a 486_response to IMS_A } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 1 User B is busy 2 User A calls User B 3 INVITE UE_A sends INVITE with the first SDP offer indicating all desired medias and codecs that UE_A supports 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 ENUM IMS_A sends query to ENUM DB 6 ENUM ENUM DB sends response to IMS_A 7 INVITE IMS_A forwards INVITE to MGCF 8 100 Trying MGCF responds with a 100 Trying provisional response 9 183 Session Progress MGCF responds with 183 Session Progress response 10 183 Session Progress IMS_forwards 183 Session Progress response to UE_A 11 PRACK UE_A sends PRACK to IMS_A 12 PRACK IMS_A forwards PRACK to MGCF 13 200 OK (PRACK) MGCF responds with 200 OK response to IMS_A 14 200 OK (PRACK) IMS_A forwards 200 OK response to UE_A 15 IAM MGCF sends IAM to PSTN 16 REL (cause #17) PSTN responds with REL “user busy” 17 RLC MGCF sends RLC to PSTN 18 486 Busy Here MGCF sends 486 Busy Here response to IMS_A 19 486 Busy Here IMS_A forwards 486 Busy Here response to UE_A 20 User A is informed that User B is busy 21 ACK UE_A acknowledges the receipt of 486 for INVITE 22 ACK IMS_A forwards ACK to MGCF ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 271 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.5 IMS user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0004 Summary: Outgoing call to PSTN, communication hold by IMS user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_11 TS 129 163 [18], clause 7.4.10.1 TP_IMS_MGCF_12 TS 129 163 [18], clause 7.4.10.1 Use Case ref.: UC_23 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A • UE_A configured to perform user initiated hold/resume using INVITE Test Sequence: Step 1 User A calls User B 2 Verify that user B is informed of incoming call of User A 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user A and B can communicate 7 User A puts connection to B on hold 8 Verify that user A and B cannot communicate 9 User A resumes connection to B 10 Verify that user A and B can communicate 11 User B ends call 12 Verify that user B is informed that call has ended 13 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_MGCF_11 in CFW step 33 (CPG): ensure that { when { IUT receives an UPDATE or a target_refresh INVITE containing a SDP indicating sendonly from IMS_A } then { IUT sends a CPG indicating remote_hold to PSTN } } 2 TP_IMS_MGCF_12 in CFW step 39 (CPG): ensure that { when { IUT receives an UPDATE or a target_refresh INVITE containing a SDP indicating sendrecv from IMS_A } then { IUT sends a CPG indicating remote_retrieve to PSTN } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B Follow UC_23 (1-26) 27 User A and B can communicate 28 User A sets B on hold 29 UPDATE/Re-INVITE UE_A sends UPDATE/Re-INVITE (sendonly) to IMS_A 30 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendonly) to MGCF ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 272 Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B 31 200 OK (UPDATE/INVITE) MGCF replies 200 OK to IMS_A 32 200 OK (UPDATE/INVITE) IMS_A forwards 200 OK to UE_A 33 CPG MGCF sends CPG “remote HOLD” 34 User A and B cannot communicate 35 UPDATE/Re-INVITE UE_A sends UPDATE/Re-INVITE (sendrecv) to IMS_A 36 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendrecv) to MGCF 37 200 OK (UPDATE/INVITE) MGCF replies 200 OK to IMS_A 38 200 OK (UPDATE/INVITE) IMS_A forwards 200 OK to UE_A 39 CPG MGCF sends CPG “remote RETRIEVE” 40 User A and B can communicate 41 User B ends call Continue UC_23 (28B-36B) |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.6 PSTN user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0005 Summary: Outgoing call to PSTN, communication hold by PSTN user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_13 TS 129 163 [18], clause 7.4.10.2 TP_IMS_MGCF_14 TS 129 163 [18], clause 7.4.10.2 Use Case ref.: UC_23 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A Test Sequence: Step 1 User A calls User B 2 Verify that user B is informed of incoming call of User A 3 Verify that user A is informed that UE_B is ringing 4 User B answers call 5 Verify that user A is informed that call has been answered 6 Verify that user A and B can communicate 7 User B puts connection to A on hold 8 Verify that user A and B cannot communicate 9 User B resumes connection to A 10 Verify that user A and B can communicate 11 User B ends call 12 Verify that user B is informed that call has ended 13 Verify that user A is informed that call has ended ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 273 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_MGCF_13 in CFW step 30 (UPDATE): ensure that { when { IUT receives a CPG indicating remote_hold from PSTN } then { IUT sends an UPDATE or a target_refresh INVITE containing a SDP indicating sendonly to IMS_A } } 2 TP_IMS_MGCF_14 in CFW step 39 (UPDATE):: ensure that { when { IUT receives a CPG indicating remote_retrieve from PSTN } then { IUT sends an UPDATE or a target_refresh INVITE containing a SDP indicating sendonly to IMS_A } } Step Direction Message Comment U s e r A U E A I M S A E N U M DB M G C F P S T N U s e r B Follow UC_23 (1-26) 27 User A and B can communicate 28 User B sets A on hold 29 CPG MGCF receives CPG with remote HOLD 30 UPDATE/Re-INVITE MGCF sends UPDATE/Re-INVITE (sendonly) to IMS_A 31 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendonly) to UE_A 32 200 OK (UPDATE/INVITE) UE_A replies 200 OK to IMS_A 33 200 OK (UPDATE/INVITE) IMS_A forwards 200 OK to MGCF 34 User A and B cannot communicate 35 CPG MGCF receives CPG with remote RETRIEVE 36 UPDATE/Re-INVITE MGCF sends UPDATE/Re-INVITE (sendrecv) to IMS_A 37 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendrecv) to UE_A 38 200 OK (UPDATE/INVITE) UE_A replies 200 OK to IMS_A 39 200 OK (UPDATE/INVITE) IMS_A forwards 200 OK to MGCF 40 User A and B can communicate 41 User A ends call Continue UC_23 (28A-36A) ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 274 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2 PSTN-to-IMS call | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.1 Normal Call, PSTN user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0006 Summary: Incoming call from PSTN, PSTN user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_01 TS 124 229 [1], clause 5.5.3.1.1 TP_IMS_MGCF_05 TS 124 229 [1], clause 5.5.3.2,1 TP_IMS_MGCF_15 TS 129 163 [18], clauses 7.2.3.2.4 and 7.2.3.2.6 TP_IMS_MGCF_16 TS 129 163 [18], clause 7.2.3.2.8 TP_IMS_MGCF_08 TS 124 229 [1], clause 5.5.4.1 TS 129 163 [18], clause 7.2.3.1.8 Use Case ref.: UC_24 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A Test Sequence: Step 1 User B calls User A 2 Verify that user A is informed of incoming call of User B 3 Verify that user B is informed that UE_A is ringing 4 User A answers the call 5 Verify that user A and B can communicate 6 User B ends call 7 Verify that user B is informed that call has ended 8 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_MGCF_01 in CFW step 3 (INVITE): ensure that { when { IUT receives an initial IAM from PSTN } then { IUT sends a INVITE to IMS_A containing a Request_URI indicating Tel_URI_E.164_Number or (Sip_URI_E.164_Number with user_portion_phone) containing a Contact_header indicating anyvalue_GRUU_format and containing a Supported_header including an 100rel_value and containing a P-Asserted-Identity_header and containing a P-Charging-Vector_header indicating an icid-value_parameter and containing a SDP indicating codec_supported and curr_precondition } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 275 Interoperability Test Description 2 TP_IMS_MGCF_05 in CFW step 14 (UPDATE): ensure that { when { IUT receives an 200OK_PRACK from IMS_A and conditions_fullfilled} then { IUT sends a UPDATE to IMS_A } } 3 TP_IMS_MGCF_15 in CFW step 20 (ACM/CPG): ensure that { when { IUT receives a 180_response from IMS_A } then { IUT sends an ACM indicating subscriber_free or sends a CPG indicating ALERTING to PSTN } } 4 TP_IMS_MGCF_16 in CFW step 25 (ANM): ensure that { when { IUT receives a 200_response from IMS_A } then { IUT sends an ANM to PSTN } } 5 TP_IMS_MGCF_08 in CFW step 33B (BYE): ensure that { when { IUT receives an REL from PSTN} then { IUT sends a BYE to IMS_A } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 276 Step Direction Message Comment U s e r A U E A I M S A M G C F P S T N U s e r B 1 User B calls User A 2 IAM PSTN send IAM to MGCF 3 INVITE MGCF sends INVITE to IMS_A (SDP with precondition status, MIME subtype "telephone-event", clause 6.4.1) 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to UE_A 6 100 Trying UE_A optionally responds with a 100 Trying provisional response 7 183 Session Progress UE_A sends 183 Session Progress response to IMS_A 8 183 Session Progress IMS_A forwards 183 Session Progress response to MGCF 9 PRACK MGCF responds with PRACK to IMS_A 10 PRACK IMS_A forwards PRACK to UE_A 11 200 OK (PRACK) UE_A responds with 200 OK to IMS_A 12 200 OK (PRACK) IMS_A forwards 200 OK to MGCF 13 UPDATE MGCF sends UPDATE to IMS_A 14 UPDATE IMS_A forwards UPDATE to UE_A 15 200 OK (UPDATE) UE_A responds with 200 OK to IMS_A 16 200 OK (UPDATE) IMS_A forwards 200 OK to MGCF 17 User A is informed of incoming call of User B 18 180 Ringing UE_A responds to initial INVITE with 180 Ringing to indicate that it has started alerting 19 180 Ringing IMS_A forwards 180 Ringing response to MGCF 20 ACM/CPG MGCF send ACM/CPG to PSTN 21 User B is informed that UE_A is ringing 22 User A answers the call 23 200 OK UE_A responds INVITE with 200 OK to indicate that the call has been answered 24 200 OK IMS_A forwards 200 OK response to MGCF 25 ANM MGCF sends ANM to PSTN 26 ACK MGCF sends ACK to PSTN 27 ACK IMS_A forwards ACK to UE_A 28 User A and B can communicate ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 277 Step Direction Message Comment U s e r A U E A I M S A M G C F P S T N U s e r B 29B User B ends call 30B REL PSTN sends REL to MGCF 31B RLC MGCF sends RLC to PSTN 32B User B is informed that call has ended 33B BYE MGCF sends BYE to IMS_A 34B BYE IMS_A forwards BYE to UE_A 35B User A is informed that call has ended 36B 200 OK UE_A sends 200 OK for BYE 37B 200 OK IMS_A forwards 200 OK response to MGCF |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.2 Normal Call, IMS user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0007 Summary: Incoming call from PSTN, IMS user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_01 TS 124 229 [1], clause 5.5.3.1.1 TP_IMS_MGCF_05 TS 124 229 [1], clause 5.5.3.2,1 TP_IMS_MGCF_15 TS 129 163 [18], clauses 7.2.3.2.4 and 7.2.3.2.6 TP_IMS_MGCF_16 TS 129 163 [18], clause 7.2.3.2.8 TP_IMS_MGCF_17 TS 129 163 [18], clause 7.2.3.2.13 Use Case ref.: UC_24 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A Test Sequence: Step 1 User B calls User A 2 Verify that user A is informed of incoming call of User B 3 Verify that user B is informed that UE_A is ringing 4 User A answers the call 5 Verify that user A and B can communicate 6 User A ends call 7 Verify that user B is informed that call has ended 8 Verify that user A is informed that call has ended ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 278 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_MGCF_01 in CFW step 3 (INVITE): ensure that { when { IUT receives an initial IAM from PSTN } then { IUT sends a INVITE to IMS_A containing a Request_URI indicating Tel_URI_E.164_Number or (Sip_URI_E.164_Number with user_portion_phone) containing a Contact_header indicating anyvalue_GRUU_format and containing a Supported_header including an 100rel_value and containing a P-Asserted-Identity_header and containing a P-Charging-Vector_header indicating an icid-value_parameter and containing a SDP indicating codec_supported and curr_precondition } } 2 TP_IMS_MGCF_05 in CFW step 14 (UPDATE): ensure that { when { IUT receives an 200OK_PRACK from IMS_A and conditions_fullfilled} then { IUT sends a UPDATE to IMS_A } } 3 TP_IMS_MGCF_15 in CFW step 20 (ACM/CPG): ensure that { when { IUT receives a 180_response from IMS_A } then { IUT sends an ACM indicating subscriber_free or sends a CPG indicating ALERTING to PSTN } } 4 TP_IMS_MGCF_16 in CFW step 25 (ANM): ensure that { when { IUT receives a 200_response from IMS_A } then { IUT sends an ANM to PSTN } } 5 TP_IMS_MGCF_32A in CFW step 24 (REL): ensure that { when { IUT receives a BYE from IMS_A } then { IUT sends an REL to PSTN } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 279 Step Direction Message Comment U s e r A U E A I M S A M G C F P S T N U s e r B 1 User B calls User A 2 IAM PSTN send IAM to MGCF 3 INVITE MGCF sends INVITE to IMS_A (SDP with precondition status, MIME subtype "telephone-event" clause 6.4.1) 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to UE_A 6 100 Trying UE_A optionally responds with a 100 Trying provisional response 7 183 Session Progress UE_A sends 183 Session Progress response to IMS_A 8 183 Session Progress IMS_A forwards 183 Session Progress response to MGCF 9 PRACK MGCF responds with PRACK to IMS_A 10 PRACK IMS_A forwards PRACK to UE_A 11 200 OK (PRACK) UE_A responds with 200 OK to IMS_A 12 200 OK (PRACK) IMS_A forwards 200 OK to MGCF 13 UPDATE MGCF sends UPDATE to IMS_A 14 UPDATE IMS_A forwards UPDATE to UE_A 15 200 OK (UPDATE) UE_A responds with 200 OK to IMS_A 16 200 OK (UPDATE) IMS_A forwards 200 OK to MGCF 17 User A is informed of incoming call of User B 18 180 Ringing UE_A responds to initial INVITE with 180 Ringing to indicate that it has started 19 180 Ringing IMS_A forwards 180 Ringing response to MGCF 20 ACM/CPG MGCF send ACM/CPG to PSTN 21 User B is informed that UE_A is ringing 22 User A answers the call 23 200 OK UE_A responds INVITE with 200 OK to indicate that the call has been answered 24 200 OK IMS_A forwards 200 OK response to MGCF 25 ANM MGCF sends ANM to PSTN 26 ACK MGCF sends ACK to PSTN 27 ACK IMS_A forwards ACK to UE_A 28 User A and B can communicate ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 280 Step Direction Message Comment U s e r A U E A I M S A M G C F P S T N U s e r B 29A User A ends call 30A BYE UE_A releases the call with BYE 31A BYE IMS_A forwards BYE to MGCF 32A REL MGCF sends REL to PSTN 33A RLC PSTN sends response RLC to MGCF 34A User B is informed that call has ended 35A 200 OK MGCF sends 200 OK response to IMS_A 36A 200 OK IMS_A forwards the 200 OK response to UE_A 37A User A is informed that call has ended |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.3 Unsuccessful Call, IMS user busy | Interoperability Test Description Identifier: TD_IMS_PSTN_0008 Summary: Incoming call from PSTN, user A busy Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_01 TS 124 229 [1], clause 5.5.3.1.1 TP_IMS_MGCF_10 TS 129 163 [18], clause 7.2.3.2.12 Use Case ref.: UC_24 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A • User A in IMS is busy Test Sequence: Step 1 User B calls User A 2 Verify that user B is informed that UE_A is busy ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 281 Interoperability Test Description Conformance Criteria: Check 1 TP_IMS_MGCF_01 in CFW step 3 (INVITE): ensure that { when { IUT receives an initial IAM from PSTN } then { IUT sends a INVITE to IMS_A containing a Request_URI indicating Tel_URI_E.164_Number or (Sip_URI_E.164_Number with user_portion_phone) containing a Contact_header indicating anyvalue_GRUU_format and containing a Supported_header including an 100rel_value and containing a P-Asserted-Identity_header and containing a P-Charging-Vector_header indicating an icid-value_parameter and containing a SDP indicating codec_supported and curr_precondition } } 2 TP_IMS_MGCF_10 in CFW step 11 (REL): ensure that { when { IUT receives a 486_response from IMS_A} then { IUT sends a REL with (cause17 or cause34) to PSTN } } Step Direction Message Comment U s e r A U E A I M S A M G C F P S T N U s e r B 1 User B calls User A 2 IAM PSTN send IAM to MGCF 3 INVITE MGCF sends INVITE to IMS_A (SDP with precondition status, MIME subtype "telephone-event", clause 6.4.1) 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to UE_A 6 100 Trying UE_A optionally responds with a 100 Trying provisional response 7 486 Busy Here UE_A responds to initial INVITE with 486 Busy Here to indicate that UE_A is busy 8 486 Busy Here IMS_A forwards 486 Busy Here response to MGCF 9 ACK MGCF sends ACK to IMS_A 10 ACK IMS_A forwards ACK to UE_A 11 REL (cause #17) MGCF send REL (user busy) 12 RLC MGCF receives RLC 13 User B is informed that UE_A is busy ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 282 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.4 IMS user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0009 Summary: Incoming call from PSTN, communication hold by IMS user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_11 TS 129 163 [18], clause 7.4.10.1 TP_IMS_MGCF_12 TS 129 163 [18], clause 7.4.10.1 Use Case ref.: UC_24 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A • UE_A configured to perform user initiated hold/resume using INVITE Test Sequence: Step 1 User B calls User A 2 Verify that user A is informed of incoming call of User B 3 Verify that user B is informed that UE_A is ringing 4 User A answers the call 5 Verify that user A and B can communicate 6 User A puts connection to B on hold 7 Verify that user A and B cannot communicate 8 User A resumes connection to B 9 Verify that user A and B can communicate 10 User A ends call 11 Verify that user B is informed that call has ended 12 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_MGCF_11 in CFW step 34 (CPG): ensure that { when { IUT receives an UPDATE or a target_refresh INVITE containing a SDP indicating sendonly from IMS_A } then { IUT sends a CPG indicating remote_hold to PSTN } } 2 TP_IMS_MGCF_12 in CFW step 40 (CPG): ensure that { when { IUT receives an UPDATE or a target_refresh INVITE containing a SDP indicating sendrecv from IMS_A } then { IUT sends a CPG indicating remote_retrieve to PSTN } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 283 Step Direction Message Comment U s e r A U E A I M S A M G C F P S T N U s e r B Follow UC_21 (1 to 27) 28 User A and B can communicate 29 User A sets B on hold 30 UPDATE/Re-INVITE UE_A sends UPDATE/Re-INVITE (sendonly) to IMS_A 31 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendonly) to MGCF 32 200 OK MGCF replies 200 OK to IMS_A 33 200 OK IMS_A forwards 200 OK to UE_A 34 CPG MGCF sends CPG with remote HOLD 35 User A and B cannot communicate 36 UPDATE/Re-INVITE UE_A sends UPDATE/Re-INVITE (sendrecv) to IMS_A 37 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendrecv) to MGCF 38 200 OK MGCF replies 200 OK to IMS_A 39 200 OK IMS_A forwards 200 OK to UE_A 40 CPG MGCF sends CPG with remote RETRIEVE 41 User A and B can communicate 42 User A ends call 43 Continue UC_21 (29A to 37A) |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.5 PSTN user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0010 Summary: Incoming call from PSTN, communication hold by PSTN user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_13 TS 129 163 [18], clause 7.4.10.2 TP_IMS_MGCF_14 TS 129 163 [18], clause 7.4.10.2 Use Case ref.: UC_24 Pre-test conditions: • HSS of IMS_A is configured according to table 1 • UE_A has IP bearers established to its IMS networks as per clause 4.2.1 • UE_A is registered in IMS_A using any user identity • MGCF within the trust domain of IMS_A Test Sequence: Step 1 User B calls User A 2 Verify that user A is informed of incoming call of User B 3 Verify that user B is informed that UE_A is ringing ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 284 Interoperability Test Description 4 User A answers the call 5 Verify that user A and B can communicate 6 User B puts connection to A on hold 7 Verify that user A and B cannot communicate 8 User B resumes connection to A 9 Verify that user A and B can communicate 10 User A ends call 11 Verify that user B is informed that call has ended 12 Verify that user A is informed that call has ended Conformance Criteria: Check 1 TP_IMS_MGCF_13 in CFW step 30 (UPDATE): ensure that { when { IUT receives a CPG indicating remote_hold from PSTN } then { IUT sends an UPDATE or a target_refresh INVITE containing a SDP indicating sendonly to IMS_A } } 2 TP_IMS_MGCF_14 step 36 (CPG): ensure that { when { IUT receives a CPG indicating remote_retrieve from PSTN } then { IUT sends an UPDATE or a target_refresh INVITE containing a SDP indicating sendonly to IMS_A } } ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 285 Step Direction Message Comment U s e r A U E A I M S A M G C F P S T N U s e r B Follow UC_21 (1 to 27) 28 User A and B can communicate 29 User B sets A on hold 30 CPG MGCF receives CPG " remote HOLD" 31 UPDATE/Re-INVITE MGCF sends UPDATE/Re-INVITE (sendonly) to IMS_A 32 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendonly) to UE_A 33 200 OK UE_A replies 200 OK to IMS_A 34 200 OK IMS_A forwards 200 OK to MGCF 35 User A and B cannot communicate 36 CPG MGCF receives CPG "remote RETRIEVE" 37 UPDATE/Re-INVITE MGCF sends UPDATE/Re-INVITE (sendrecv) to IMS_A 38 UPDATE/Re-INVITE IMS_A forwards UPDATE/Re-INVITE (sendrecv) to UE_A 39 200 OK UE_A replies 200 OK to IMS_A 40 200 OK IMS_A forwards 200 OK to MGCF 41 User A and B can communicate 42 User A ends call Continue UC_21 (30A to 37A) ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 286 History Document history V1.0.0 April 2008 Publication V1.1.1 March 2009 Publication V2.1.1 February 2009 Publication V2.2.1 March 2009 Publication V2.3.1 April 2010 Publication V3.1.1 June 2011 Publication V4.1.1 October 2011 Publication V4.1.3 May 2012 Publication |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 1 Scope | The present document specifies interoperability Test Purposes (TPs) for IMS NNI interworking based on the IP Multimedia Call Control Protocol based on Stage 3 Session Initiation Protocol (SIP) and Session Description Protocol (SDP) standard, TS 124 229 [1]. TPs are defined using the TPLan notation also described in ES 202 553 [4]. Test purposes have been written based on the test specification framework described in TS 102 351 [2] and the interoperability testing methodology defined in TS 102 237-1 [3], i.e. interoperability testing with conformance checking. The scope of these test purposes is not to cover all requirements specified in TS 124 229 [1]. TPs have been only specified for requirements that are observable at the interface between two IMS core network implementations, i.e. IMS NNI. For the purpose of the present document an IMS core network as a whole - not its components - are considered to be under test. In a separate section a set of test purposes has been developed to cover the MGCF aspects as defined in clause 5.5 of TS 124 229 [1]. To trigger events at the Mg and Mj reference point the IMS core network will connect to a PSTN network via an MGCF. The interworking between IMS and PSTN is described in TS 129 163 [6]. NOTE: Requirements pertaining to a UE or an AS implementation or IMS core network requirements that can only be observed at the interface between UE and IMS CN are explicitly not within the scope of the present document. The latter requirements have been dealt with from a UE and conformance perspective in TS 134 229-3 [5]. |
174a17c8b5525d2a7ec906b188573d7c | 186 011-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. |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 229 (V9.5.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 9.5.0 Release 9)". [2] ETSI TS 102 351: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [3] ETSI TS 102 237-1: "Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to interoperability testing". [4] ETSI ES 202 553: "Methods for Testing and Specification (MTS); TPLan: A notation for expressing Test Purposes". [5] ETSI TS 134 229-3 (V7.2.0): "Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Part 3: Abstract test suite (ATS) (3GPP TS 34.229-3 version 7.2.0 Release 7)". ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 6 [6] ETSI TS 129 163 (V9.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 version 9.4.0 Release 9)". [7] RCS-e Advanced Communications: "Services and Client Specification Version 1.1". |
174a17c8b5525d2a7ec906b188573d7c | 186 011-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. |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ACK (positive) ACKnowledgement ACM Address Complete Message AKA Authentication and Key Agreement ANM Answer Message AS (IMS) Application Server ATS Abstract Test Suite CF (Test) Configuration CN Core Network CPG Call ProGress Message CSCF Call Session Control Function DB Data Base DNS Domain Name System ENUM E.164 Number Mapping GRUU Globally Routable User agent URI HSS Home Subscriber Server IAM Initial Address Message IBCF Interconnection Border Control Gateway I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IOI Inter Operator Identifier IP Internet Protocol IPTV IP TeleVision IUT Implementation Under Test MGCF Media Gateway Control Function MRFC Multimedia Resource Function Controller NAPTR Naming Authority Pointer Record NGN Next Generation Network NNI Network-to-Network Interface NWK NetWorK PCO Point of Control and Observation P-CSCF Proxy CSCF PSTN Public Switched Telephone Network RC Requirements Catalogue REL RELease RQ Requirement S-CSCF Serving CSCF SDP Session Description Protocol SIP Session Initiation Protocol TP Test Purpose TPLan Test Purpose Notation TSS Test Suite Structure ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 7 TTL Time To Live UE User Equipment URI Uniform Record Identifier |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 4 Test Suite Structure (TSS) | The Test Suite Structure is based on a Requirements Catalogue which was established prior to test purpose specification. This RC extracts all requirements from [1] which are relevant to the scope of this work. The TSS is defined by the groups within the following TPLan specification of test purposes. The numbering is not contiguous so that new TPs can be added at a later date without the need to completely renumber the TSS groups. NOTE: The requirements catalogue is at this point not accessible as an ETSI document. Requirement identifiers of the catalogue have been replaced in the present document with the location of the requirement in the base specification, i.e. base specification type, identifier, version, clause and paragraph. EXAMPLE: TS 124 229 (V8.10.0), clause 5.2.6.3 ¶66. The test purposes have been divided into 6 major groups: 1) General Capabilities 2) Registration procedures 3) Dialog procedures 4) Messaging procedures 5) Supplementary services 6) MGCF tests for IMS-PSTN interconnection These groups have been further divided into subgroups according to IMS components as follows: Group 1: IMST2 NNI IOP Group 1.1: General Capabilities Group 1.2: Registration procedures Group 1.2.1: Registration at P-CSCF Group 1.2.2: Registration at S-CSCF Group 1.2.3: Registration at I-CSCF Group 1.2.4: Registration at IBCF Group 1.3: Dialog procedures Group 1.3.1: Dialog at P-CSCF Group 1.3.2: Dialog at S-CSCF Group 1.3.3: Dialog at I-CSCF Group 1.3.4: Dialog at IBCF Group 1.4: Messaging procedures Group 1.4.1: Messaging at P-CSCF Group 1.4.2: Messaging at S-CSCF Group 1.5: Supplementary service procedures Group 1.5.1: Supplementary services at S-CSCF |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5 Test Purposes (TP) | The test purposes have been written in the notation TPLan [4] which has been developed at ETSI to express test purposes in a more formal manner. All TPLan TPs have been converted into a symbolic tabular presentation format which is shown in this clause. TPs in the standardized textual TPLan syntax are collected in archive ts_18601101v040103p0.zip that is included in the electronic annex of the present document. The two presentation formats, i.e. textual and symbolic tabular, contain the same information and shall therefore be considered equivalent. In the case that there appears to be syntactical or semantic differences between the two then the files in the electronic annex take precedence over the following tables. Configurations that are referenced by test purposes are shown in Annex B. ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 8 |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.1 The tabular symbolic TPLan presentation format | Each table contains header fields and a description part. The header fields identify the TP, list the related clause reference the base specification that the TP was derived from, introduce the TP with a short summary, references the related test configuration and test case in the ATS. The description part presents the TP using two sections: a) initial conditions that have to be fulfilled for the test purpose body to be valid; and b) the test purpose body which is illustrated with one or more stimulus/response pairs. Both sections are further substructured with columns for affected entities from the test configurations, i.e. IUT, UE, UE2, IMS (test system component) and AS. The condition section lists one or more conditions that have to be fulfilled in order for the test purpose body to apply. Each condition has a description and either "✓" or "" marks to indicate all the entities affected by this condition. "✓" marks indicates a positive condition, e.g. "A is registered in B", whereas ""marks indicate a negative condition, e.g. "B not configured for feature Z". If there is no mark in a column then the condition does not apply for that entity, e.g. entity A is not involved in the condition "B not configured for feature Z". It is assumed that all listed conditions have to be fulfilled in the order listed, i.e. the list reflects an "and" relation. Table 1 shows an example condition section illustrating all of the above examples. Table 1: Example TP condition section Entities Condition A B ✓ ✓ A registered in B B not configured for feature Z The test purpose body section contains one or more steps identified with a number in the first column. Steps belonging IUT stimuli are shown with a green background whereas steps related to IUT responses are shown with a beige background. All listed steps are assumed to be carried out in increasing step number, i.e. they reflect an "and" relation. "or" relations at the level of entire messages are shown with lowercase letters following the step number identifying the different alternatives, e.g. "2a" versus "2b". Each step indicates the exchange of a message from a source entity (identified by the direction symbols " " or ""), e.g. entity A sends the message, to a destination entity (identified by the direction symbols "" or ""), e.g. entity B receives the message. The use of the "||" symbol in combination with the direction symbols, e.g. "||", indicates that a particular message shall either not be sent or received by an entity, e.g. entity B did not send the message. Additional information about valid as well as invalid message content is presented in the "Message" column. First general information about message, e.g. its type, destination, attributes, etc, are shown in bold font. Below this information message headers or parameter content that must be present in that message are listed using "" symbols whereas headers or parameter content that must not be present are listed using the "" symbols. The " " symbol indicates a valid message parameter value where as the " ||"symbol indicates an invalid message parameter value. Any content, e.g. header or parameter, which is not explicitly mentioned in a message description of a TP is not restricted by that TP. The "" symbol together with " ||"symbol means that the message header MUST be present but it cannot contain a specific message parameter value. The "" symbol together with " " symbol means that the message header MAY be present but it cannot contain a specific message parameter value. Finally, the interface identifier to which a message exchange pertains may be shown in the column labelled "IF". Table 2 shows an example test purpose body section illustrating all of the above examples. ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 9 Table 2: Example TP body section A B Step Direction Message IF 1 some request this header this one parameter this value this other parameter || that value that parameter that header Xx 2a failure response Xx 2b || || no message Xx |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.2 General Capabilities | Test Purpose Identifier: TP_IMS_4002_01 Summary: IMS CN components shall support SIP messages > 1 300 bytes IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 4.2A ¶1 Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B a Message Body greater than 1 300 bytes 2 MESSAGE the Message Body greater than 1 300 bytes |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3 Registration Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.1 Registration at P-CSCF | Test Purpose Identifier: TP_IMS_5005_01 Summary: The P-CSCF shall support the Path header IUT Role: IMS A References: TS 124 229 (V9.5.0), [1] clause 5.2.1 ¶8 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ IMS B has challenged with a 401 response the REGISTER request of UE B IMS A IMS B UE B Step Direction Message IF 1 protected REGISTER addressed to IMS B a Path header 2 REGISTER a Path header ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 10 Test Purpose Identifier: TP_IMS_5011_01 Summary: In case of IMS AKA as security mechanism the P-CSCF shall forward REGISTER requests received from the UE to the entry point in the home network IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.2.1 ¶16 (2nd numbered list) and 5.2.2.2 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B IMS A not configured for topology hiding ✓ ✓ user of UE B existing in IMS B UE B has not established a security association with IUT IMS A IMS B UE B Step Direction Message IF 1 unprotected REGISTER a Security-Client header 2 REGISTER a Path header P-CSCF SIP URI of IMS A a Require header a path option tag a P-Charging-Vector header an icid-value parameter an orig-ioi parameter IMS A a term-ioi parameter a Authorization header an integrity-protected parameter no a Security-Verify header a Security-Client header a P-Visited-Network-ID header the visited network at the home network ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 11 Test Purpose Identifier: TP_IMS_5011_02 Summary: In case of IMS AKA as security mechanism the P-CSCF shall forward REGISTER requests received from the UE to the entry point in the home network IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clauses 5.2.2.1 ¶1 ¶16 (2nd numbered list) and 5.2.2.2 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B IMS A not configured for topology hiding ✓ ✓ user of UE B existing in IMS B ✓ ✓ UE B has established a security association with IUT IMS A IMS B UE B Step Direction Message IF 1 protected REGISTER a Security-Client header 2 REGISTER a Path header P-CSCF SIP URI of IMS A a Require header a path option tag a P-Charging-Vector header an icid parameter an orig-ioi parameter IMS A a term-ioi parameter a Authorization header an integrity-protected parameter yes a Security-Verify header a Security-Client header a P-Visited-Network-ID header the visited network at the home network ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 12 Test Purpose Identifier: TP_IMS_5011_03 Summary: In case of IMS digest as security mechanism the P-CSCF shall forward REGISTER requests received from the UE to the entry point in the home network IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clauses 5.2.2.1 ¶16 (2nd numbered list) and 5.2.2.3 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B IMS A not configured for topology hiding ✓ ✓ user of UE B existing in IMS B UE B has not established a security association with IUT IMS A IMS B UE B Step Direction Message IF 1 unprotected REGISTER 2 REGISTER a Path header P-CSCF SIP URI of IMS A a Require header a path option tag a P-Charging-Vector header an icid-value parameter an orig-ioi parameter IMS A a term-ioi parameter a Authorization header an integrity-protected parameter ip-assoc-pending or an integrity-protected parameter a P-Visited-Network-ID header the visited network at the home network Test Purpose Identifier: TP_IMS_5011_04 Summary: In case of IMS digest as security mechanism the P-CSCF shall forward REGISTER requests received from the UE to the entry point in the home network IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clauses 5.2.2.1 ¶1 ¶16 (2nd numbered list) and 5.2.2.3 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B IMS A not configured for topology hiding ✓ ✓ user of UE B existing in IMS B UE B has established a security association with IUT IMS A IMS B UE B Step Direction Message IF 1 protected REGISTER 2 REGISTER a Path header P-CSCF SIP URI of IMS A a Require header a path option tag a P-Charging-Vector header an icid parameter an orig-ioi parameter IMS A a term-ioi parameter a Authorization header an integrity-protected parameter ip-assoc-yes a P-Visited-Network-ID header the visited network at the home network ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 13 Test Purpose Identifier: TP_IMS_5203_01 Summary: The P-CSCF have received a REGISTER request from the UE and modified a number of headers and forwarded the request to an entry point with no response IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.2.1 ¶33 (item 6 in 2nd numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ UE B having sent an initial REGISTER to IMS A ✓ ✓ IMS A configured with multiple entry points for IMS B IMS A IMS B UE B Step Direction Message IF 1 || || Any response 2 REGISTER addressed to another entry point Test Purpose Identifier: TP_IMS_5203_02 Summary: The P-CSCF have received a REGISTER request from the UE and modified a number of headers and forwarded the request to an entry point with 3xx IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.2.1 ¶33 (item 6 in 2nd numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ UE B having sent an initial REGISTER to IMS A ✓ ✓ IMS A configured with multiple entry points for IMS B IMS A IMS B UE B Step Direction Message IF 1 3xx response 2 REGISTER addressed to another entry point Test Purpose Identifier: TP_IMS_5203_03 Summary: The P-CSCF have received a REGISTER request from the UE and modified a number of headers and forwarded the request to an entry point with 480 IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.2.1 ¶33 (item 6 in 2nd numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ UE B having sent an initial REGISTER to IMS A ✓ ✓ IMS A configured with multiple entry points for IMS B IMS A IMS B UE B Step Direction Message IF 1 480 response 2 REGISTER addressed to another entry point ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 14 Test Purpose Identifier: TP_IMS_5044_01 Summary: The P-CSCF have received a REGISTER request from the UE and modified a number of headers and forwarded the request to an entry point IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.3 ¶2 (1st numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ UE B having sent a protected REGISTER to IMS A IMS A not configured for topology hiding IMS A IMS B UE B Step Direction Message IF 1 200 response 2 SUBSCRIBE a Request URI "the resource to which the P-CSCF wants to subscribe to" and a From header P-CSCF_SIP_URI of IMS_A and a To_header the default_public_user_identity of UE_B and an Event_header the reg event package and an Expires_header "a value greater than the one in the Expires_header of the 200_response" and a P-Asserted-Identity_header the P-CSCF_SIP_URI of IMS_A and a P-Charging-Vector header an icid-value parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 15 |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.2 Registration at S-CSCF | Test Purpose Identifier: TP_IMS_5088_01 Summary: S-CSCF shall deregister unexpired registration upon receipt of a new REGISTER with new contact information IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.2.1 ¶7 (item 2 in 1st numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ ✓ UE B registered in IMS B via IMS A ✓ ✓ IMS A within the trust domain of IMS B UE B not de-registered in IMS B IMS A IMS B UE B Step Direction Message IF 1a initial REGISTER an Authorization header an integrity-protected parameter no or tls-pending or ip-assoc-pending 1b initial REGISTER an Authorization header an integrity-protected parameter 2 NOTIFY a Request URI the P-CSCF SIP URI of IMS A an Event header the reg event package a P-Charging-Vector header an icid-value parameter a Route header the original Route header from SUBSCRIBE a Message Body for each registered public identity of UE B a registration element an aor attribute registered public identity of UE B a state attribute terminated a contact subelement an event attribute deactivated or rejected a state attribute terminated a URI subelement the contact address of UE B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 16 Test Purpose Identifier: TP_IMS_5089_01 Summary: In case of IMS AKA as security mechanism the S-CSCF shall return 401 (Unauthorized) upon receipt of a REGISTER from an UE not previously registered IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.2.1A ¶1 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ user of UE B existing in IMS B UE B not registered in IMS B ✓ ✓ UE B visiting IMS A ✓ ✓ IMS A within the trust domain of IMS B IMS A IMS B UE B Step Direction Message IF 1 initial REGISTER an Authorization header an integrity-protected parameter no 2 401 response an WWW-Authenticate header a realm parameter the operator identifier of IMS B a nonce parameter a RAND parameter an AUTN parameter) an algorithm parameter AKAv1-MD5 an ik parameter a ck parameter Test Purpose Identifier: TP_IMS_5089_02 Summary: In case of SIP digest as security mechanism the S-CSCF shall return 401 (Unauthorized) upon receipt of a REGISTER from an UE not previously registered IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.2.1B ¶1 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ user of UE B existing in IMS B UE B not registered in IMS B ✓ ✓ UE B visiting IMS A ✓ ✓ IMS A within the trust domain of IMS B IMS A IMS B UE B Step Direction Message IF 1 initial REGISTER an Authorization header 2 401 response an WWW-Authenticate header a realm parameter the operator identifier of IMS B a nonce parameter an algorithm parameter MD5 a qop parameter auth ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 17 Test Purpose Identifier: TP_IMS_5092_01 Summary: 200 OK on REGISTER from UE to the S-CSCF IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.2.2F ¶1 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ user of UE B existing in IMS B ✓ ✓ UE B visiting IMS A UE B not registered in IMS B ✓ IMS B has challenged with a 401 response the REGISTER request IMS A IMS B UE B Step Direction Message IF 1 protected REGISTER 2 200 response the same Path header as in the protected REGISTER a P-Associated-URI header all registered public identities its associated set of implicitly registered public user identities first the default public user identity no barred public user identities a Service-Route header the S-CSCF SIP URI of IMS B a P-Charging-Vector header a term-ioi parameter operator identifier of IMS B a Contact header all contact addresses for the default public user identity of UE B Test Purpose Identifier: TP_IMS_5096_01 Summary: The network shall handle incoming SUBSCRIBE correctly IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.2.1.1 ¶1 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ UE B registered in IMS B ✓ ✓ UE B visiting IMS A IMS A IMS B UE B Step Direction Message IF 1 SUBSCRIBE an Event header the reg event package 2 2xx response an Expires header the same or lower expiry time than specified in the initial SUBSCRIBE ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 18 Test Purpose Identifier: TP_IMS_5093_01 Summary: S-CSCF shall deregister in network-initiated de-registration IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.5 ¶6 (numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ ✓ UE B registered in IMS B via IMS A ✓ ✓ IMS A within the trust domain of IMS B IMS A IMS B UE B Step Direction Message IF 1 network initiated deregistration event 2 NOTIFY a Request URI UE_B an Event header the reg event package a P-Charging-Vector header an icid-value parameter a Route header the original Route header from SUBSCRIBE a Message Body for each registered public identity of UE B a registration element an aor attribute registered public identity of UE B a state attribute terminated a contact subelement an event attribute deactivated or rejected a state attribute terminated a URI subelement the contact address of UE B 3 NOTIFY a Request URI UE_A an Event header the reg event package a P-Charging-Vector header an icid-value parameter a Route header the original Route header from SUBSCRIBE a Message Body for each registered public identity of UE A a registration element an aor attribute registered public identity of UE A a state attribute terminated a contact subelement an event attribute deactivated or rejected a state attribute terminated a URI subelement the contact address of UE A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 19 Test Purpose Identifier: TP_IMS_5094_01 Summary: S-CSCF shall register in network-initiated re-authentication IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.6 ¶2 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ ✓ UE B registered in IMS B via IMS A ✓ ✓ IMS A within the trust domain of IMS B ✓ IMS B receives an event to reauthenticate UE_B IMS A IMS B UE B Step Direction Message IF 1 network initiated reauthentication event 2 NOTIFY a Request URI UE_B an Event header the reg event package a P-Charging-Vector header an icid-value parameter a Route header the original Route header from SUBSCRIBE a Message Body for each registered public identity of UE B a registration element an aor attribute registered public identity of UE B a state attribute active a contact subelement an event attribute shortened a state attribute active a URI subelement the contact address of UE B 3 NOTIFY a Request URI the P-CSCF_SIP_URI of IMS_A an Event header the reg event package a P-Charging-Vector header an icid-value parameter a Route header the original Route header from SUBSCRIBE a Message Body for each registered public identity of UE A a registration element an aor attribute registered public identity of UE B a state attribute active a contact subelement an event attribute shortened a state attribute active a URI subelement the contact address of UE B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 20 |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.3 Registration at I-CSCF | Interoperability Test Purpose Identifier: TP_IMS_5129_01 Summary: If a request is received from a non-trusted domain, a 403 (Forbidden) response shall be returned by I-CSCF IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.3.1.2 ¶1 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ user of UE B existing in IMS B IMS A not within the trust domain of IMS B IMS A IMS B UE B Step Direction Message IF 1 valid initial REGISTER 2 403 response |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.4 Registration at IBCF | Interoperability Test Purpose Identifier: TP_IMS_5134_01 Summary: If a request includes a Path header the IBCF shall add the routeable SIP URI of an IBCF to the top of the Path header IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.4.1 ¶5 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ IMS A configured for topology hiding IMS A IMS B UE B Step Direction Message IF 1 REGISTER 2 REGISTER an additional topmost Path header the IBCF SIP URI of IMS A Interoperability Test Purpose Identifier: TP_IMS_5401_01 Summary: IBCF shall, if topology hiding is required, apply the encryption for the Path header IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.1 ¶1 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ IMS A configured for topology hiding IMS A IMS B UE B Step Direction Message IF 1 REGISTER Path header 2 REGISTER a Path header encrypted consecutive header entries tokenized-by parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 21 Interoperability Test Purpose Identifier: TP_IMS_5402_01 Summary: IBCF shall select a new entry point and forward the original REGISTER request on no response. IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.1 ¶1 (item 3 in 1st numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B ✓ IMS A configured for topology hiding ✓ ✓ IMS A configured with multiple entry points in IMS B ✓ ✓ IMS A having sent an initial REGISTER to IMS B IMS A IMS B Step Direction Message IF 1 || || Any response 2 original REGISTER addressed to another entry point Interoperability Test Purpose Identifier: TP_IMS_5402_02 Summary: IBCF shall select a new entry point and forward the original REGISTER request on 3xx response. IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.1 ¶1 (item 3 in 1st numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B ✓ IMS A configured for topology hiding ✓ ✓ IMS A configured with multiple entry points for IMS B ✓ ✓ IMS A having sent an initial REGISTER to IMS B IMS A IMS B Step Direction Message IF 1 3xx response 2 original REGISTER addressed to another entry point Interoperability Test Purpose Identifier: TP_IMS_5402_03 Summary: IBCF shall select a new entry point and forward the original REGISTER request on 480 response. IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.1 ¶1 (item 3 in 1st numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B ✓ IMS A configured for topology hiding ✓ ✓ IMS A configured with multiple entry points for IMS B ✓ ✓ IMS A having sent an initial REGISTER to IMS B IMS A IMS B Step Direction Message IF 1 480 response 2 original REGISTER addressed to another entry point ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 22 Interoperability Test Purpose Identifier: TP_IMS_5411_01 Summary: If a request is received from a non-trusted domain, a 403 (Forbidden) response shall be returned by IBCF IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.10.3.1 ¶1 (item 1 in 1st numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B ✓ IMS B configured for topology hiding IMS A not within the trust domain of IMS B IMS A IMS B Step Direction Message IF 1 valid REGISTER 2 403 response |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4 Dialog Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.1 Dialog at P-CSCF | Test Purpose Identifier: TP_IMS_5046_01 Summary: When the P-CSCF receives an initial INVITE request for a dialog from a UE for which a Service- Route header list exists without topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.3 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B IMS A not configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE 2 INVITE a topmost Route header || the P-CSCF SIP URI of IMS A a Route header the list of Service Route header URIs from the registration an additional Via header the P-CSCF via port number the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A an additional topmost Record-Route header the P-CSCF port number where it awaits subsequent requests from UE A the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A P-Preferred-Identity header a P-Asserted-Identity header an address of UE B a P-Charging-Vector header an icid-value parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 23 Test Purpose Identifier: TP_IMS_5046_02 Summary: When the P-CSCF receives an initial INVITE request for a dialog from a UE for which a Service- Route header list exists with topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.3 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE 2 INVITE a topmost Route header the IBCF SIP URI of IMS A || the P-CSCF SIP URI of IMS A a Route header the list of Service Route header URIs from the registration an additional Via header the P-CSCF via port number the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A an additional topmost Record-Route header the P-CSCF port number where it awaits subsequent requests from UE A the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A P-Preferred-Identity header a P-Asserted-Identity header an address of UE A a P-Charging-Vector header an icid-value parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 24 Test Purpose Identifier: TP_IMS_5046_03 Summary: When the P-CSCF receives an initial request for a dialog from a UE for which a Service-Route header list exists without topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.3 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B IMS A not configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 SUBSCRIBE 2 SUBSCRIBE a topmost Route header || the P-CSCF SIP URI of IMS A a Route header the list of Service Route header URIs from the registration an additional Via header the P-CSCF via port number the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A an additional topmost Record-Route header the P-CSCF port number where it awaits subsequent requests from UE A the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A P-Preferred-Identity header a P-Asserted-Identity header an address of UE A a P-Charging-Vector header an icid-value parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 25 Test Purpose Identifier: TP_IMS_5046_04 Summary: When the P-CSCF receives an initial request for a dialog from a UE for which a Service-Route header list exists with topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.3 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 SUBSCRIBE 2 SUBSCRIBE a topmost Route header the IBCF SIP URI of IMS A || the P-CSCF SIP URI of IMS A a Route header the list of Service Route header URIs from the registration an additional Via header the P-CSCF via port number the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A an additional topmost Record-Route header the P-CSCF port number where it awaits subsequent requests from UE A the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A P-Preferred-Identity header a P-Asserted-Identity header an address of UE A a P-Charging-Vector header an icid-value parameter Test Purpose Identifier: TP_IMS_5048_01 Summary: P-CSCF forwards a target refresh request from the UE IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.5 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent INVITE 2 INVITE a topmost Route header || the P-CSCF SIP URI of IMS A an additional Via header the P-CSCF via port number the P-CSCF-FQDN address or the P-CSCF-IP address of the IMS A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 26 Test Purpose Identifier: TP_IMS_5052_01 Summary: The P-CSCF modifies a request, other than a target refresh request, from the UE subsequent to a successful initial request for a dialog IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.9 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A UE A IMS A IMS B UE B Step Direction Message IF 1 BYE 2 BYE a Route header the P-CSCF SIP URI of IMS A the same Record-Route header as in the previous ACK a P-Charging-Vector header an icid-value parameter Test Purpose Identifier: TP_IMS_5053_01 Summary: P-CSCF receives from the UE a request for an unknown method without topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.11 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B IMS A not configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 Unknown Method addressed to UE B 2 Unknown Method a Route header the list of Service Route header URIs from the registration a P-Preferred-Identity header a P-Asserted-Identity header an address of UE A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 27 Test Purpose Identifier: TP_IMS_5053_02 Summary: P-CSCF receives from the UE a request for an unknown method with topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.11 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 Unknown Method addressed to UE B 2 Unknown Method a Route header the list of Service Route header URIs from the registration a P-Preferred-Identity header a P-Asserted-Identity header an address of UE A Test Purpose Identifier: TP_IMS_5055_01 Summary: The P-CSCF receives a 180 response to an initial request for a dialog from the UE IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.4.4 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received an initial request for a dialog from UE B UE A IMS A IMS B UE B Step Direction Message IF 1 180 response 2 180 response a Record-Route header the P-CSCF SIP URI and port number of IMS A where it expects subsequent requests a comp parameter a P-Preferred-Identity header a P-Asserted-Identity header the public identity sent in P-Called Party-ID header sent in the initial request ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 28 Test Purpose Identifier: TP_IMS_5055_02 Summary: The P-CSCF receives a 2xx response to an initial request for a dialog from the UE IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.4.4 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received an initial request for a dialog from UE B UE A IMS A IMS B UE B Step Direction Message IF 1 200 response 2 200 response a Record-Route header the P-CSCF SIP URI and port number of IMS A where it expects subsequent requests a comp parameter a P-Preferred-Identity header a P-Asserted-Identity header the public identity sent in P-Called Party-ID header sent in the initial request Test Purpose Identifier: TP_IMS_5067_01 Summary: The P-CSCF shall include the access-network-charging-info parameter in the P-Charging-Vector header in the first request originated by the UE IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.7.2 ¶5 Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE 2 INVITE a P-Charging-Vector header a access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5070_01 Summary: The P-CSCF shall respond with a 100 (Trying) provisional response on initial INVITE in terminating network IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.7.3 ¶3 Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE 2 100 response ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 29 Test Purpose Identifier: TP_IMS_5072_01 Summary: P-CSCF sends CANCEL in case its UE goes down during dialog initiation IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.8.1.1 ¶1 Config Ref: CF_ROAM_CALL Entities Condition UE A NWK IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received 180 on initial request for dialog from UE A UE A NWK IMS A IMS B UE B Step Direction Message IF 1 an indication that UE B is no longer available 2 CANCEL a Reason header a status code parameter 503 Service Unavailable 3 503 response Test Purpose Identifier: TP_IMS_5073_01 Summary: P-CSCF sends BYE in case its calling UE goes down in ongoing dialog IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.2.8.1.2 ¶1 (item 1 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A NWK IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A UE A IMS A NWK IMS B UE B Step Direction Message IF 1 an indication that UE B is no longer available 2 BYE Request URI Contact header value of UE A To header initial 200 OK To value from UE A From header initial INVITE From value from UE B Call-ID header initial INVITE Call Id value from UE B CSeq header an incremented Sequence Number Route header dialog specific routing information for UE A Reason header 503 Service Unavailable further headers based on local policy or call release reason ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 30 Test Purpose Identifier: TP_IMS_5074_01 Summary: P-CSCF sends BYE in case its called UE goes down in ongoing dialog IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.8.1.2 ¶1 (item 3 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A NWK IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A NWK IMS B UE B Step Direction Message IF 1 an indication that UE B is no longer available 2 BYE Request URI Contact header value of UE A To header initial 200 OK From value from UE B From header initial INVITE To value from UE A Call-ID header initial INVITE Call Id value from UE A CSeq header an incremented Sequence Number Route header dialog specific routing information for UE A Reason header 503 Service Unavailable further headers based on local policy or call release reason Test Purpose Identifier: TP_IMS_5080_01 Summary: The P-CSCF shall include the updated access-network-charging-info parameter from P-Charging- Vector header when sending subsequent INVITE to the S-CSCF. IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.9.1 ¶2 Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent INVITE 2 INVITE a P-Charging-Vector header an updated access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 31 Test Purpose Identifier: TP_IMS_5080_02 Summary: The P-CSCF shall include the updated access-network-charging-info parameter from P-Charging- Vector header when sending the subsequent UPDATE to the S-CSCF. IUT Role: IMS A References: TS 124 229 [1] (V9.5.0), clause 5.2.9.1 ¶2 Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent UPDATE 2 UPDATE a P-Charging-Vector header an updated access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5081_01 Summary: P-CSCF 100 response to a re-INVITE IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.9.2 ¶1 Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent INVITE addressed to UE B 2 100 response Test Purpose Identifier: TP_IMS_5082_01 Summary: P-CSCF sends 200 response to a target refresh request with P-Charging-Vector IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.9.2 ¶2 Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B ✓ ✓ IMS B has received a target refresh request in a dialog from IMS A UE A IMS A IMS B UE B Step Direction Message IF 1 200 response 2 200 response a P-Charging-Vector header an updated access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 32 |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.2 Dialog at S-CSCF | Test Purpose Identifier: TP_IMS_5097_01 Summary: S-CSCF must inserts orig-ioi parameter, remove access-network-charging-info parameter and P- Access-Network-Info header before sending initial INVITE or a initial request over NNI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (1st numbered list) Config Ref: CF_INT_CALL CF_ROAM_AS Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B IMS A not configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B (also valid for SUBSCRIBE) 2 initial INVITE a Route header the S-CSCF SIP URI of IMS A a P-Charging-Vector header an icid-value parameter an orig-ioi parameter IMS A an access-network-charging-info parameter a term-ioi parameter a Record-Route header the originating S-CSCF SIP URI a P-Access-Network-Info header Test Purpose Identifier: TP_IMS_5097_02 Summary: S-CSCF inserts a second P-Asserted-Identity header indicating a registered tel URI or sip URI whichever is not present in initial INVITE IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 9 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE A registered public identities containing a Tel URI and a SIP URI UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B 2 initial INVITE a P-Asserted-Identity header the SIP URI of UE A a P-Asserted-Identity header the Tel URI of UE A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 33 Test Purpose Identifier: TP_IMS_5097_04 Summary: S-CSCF uses ENUM/DNS to translate Tel URIs to SIP URIs in initial INVITE requests IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 10 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A ENUM _DB IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ ENUM_DB configured with an ENUM entry for Tel URI E.164 Number of UE B UE A IMS A ENUM _D B IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B a Request URI a Tel URI 2 NAPTR Query the Tel URI E.164 Number 3 NAPTR Response NAPTR Resource Record the SIP URI of UE B 4 initial INVITE a Request URI a SIP URI of UE B a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5106_01 Summary: S-CSCF must handle subsequent INVITE prior to sending it over NNI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶108 (6th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent INVITE addressed to UE B 2 subsequent INVITE a Record-Route header the S-CSCF SIP URI of IMS A Route header the S-CSCF SIP URI of IMS A a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 34 Test Purpose Identifier: TP_IMS_5106_02 Summary: S-CSCF must handle UPDATE prior to sending it over NNI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶108 (6th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 UPDATE addressed to UE B 2 UPDATE a Record-Route header the S-CSCF SIP URI of IMS A Route header the S-CSCF SIP URI of IMS A a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5107_01 Summary: S-CSCF removes its own SIP URI from the route header before sending BYE IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 BYE addressed to UE B 2 BYE Route header the S-CSCF SIP URI of IMS A Test Purpose Identifier: TP_IMS_5107_02 Summary: S-CSCF removes its own SIP URI from the route header before sending ACK IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received 200OK on initial request for dialog UE B UE A IMS A IMS B UE B Step Direction Message IF 1 ACK addressed to UE B 2 ACK Route header the S-CSCF SIP URI of IMS A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 35 Test Purpose Identifier: TP_IMS_5107_03 Summary: S-CSCF removes its own SIP URI from the route header before sending CANCEL IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received 180 on initial request for dialog from UE B UE A IMS A IMS B UE B Step Direction Message IF 1 CANCEL addressed to UE B 2 CANCEL Route header the S-CSCF SIP URI of IMS A Test Purpose Identifier: TP_IMS_5107_04 Summary: S-CSCF removes its own SIP URI from the route header before sending REFER IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶119 (item 1 in 8th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received 200OK on initial request for dialog to MRFC AS in IMS A UE A IMS A IMS B UE B Step Direction Message IF 1 REFER addressed to UE B 2 REFER Route header the S-CSCF SIP URI of IMS A Test Purpose Identifier: TP_IMS_5108_05 Summary: S-CSCF rejects barred users on initial INVITE IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶8 (item 1 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B barred user in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B a Request URI a barred user in IMS B 2 404 response ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 36 Test Purpose Identifier: TP_IMS_5115_01 Summary: S-CSCF include term-ioi parameter and restores orig-ioi in 180 responses from UE to initial requests in terminating network IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶91 (item 2 in 4th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received an initial request for a dialog from UE A UE A IMS A IMS B UE B Step Direction Message IF 1 180 response addressed to UE A 2 180 response a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter operator identifier of IMS B Test Purpose Identifier: TP_IMS_5115_02 Summary: S-CSCF include term-ioi parameter and restores orig-ioi in 2xx responses from UE to initial requests in terminating network IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶91 (item 2 in 4th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received 180 on initial request for dialog from UE B UE A IMS A IMS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter operator identifier of IMS B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 37 Test Purpose Identifier: TP_IMS_5115_03 Summary: S-CSCF inserts a second P-Asserted-Identity header in 1xx response indicating a registered tel URI or SIP URI whichever is not present IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶92 (item 3 in 4th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B registered public identities containing a Tel URI and SIP URI ✓ ✓ UE B has received an initial request for a dialog from UE A UE A IMS A IMS B UE B Step Direction Message IF 1 1xx response addressed to UE A 2 1xx response a P-Asserted-Identity header the SIP URI of UE B a P-Asserted-Identity header the Tel URI of UE B Test Purpose Identifier: TP_IMS_5115_04 Summary: S-CSCF inserts a second P-Asserted-Identity header in 2xx response indicating a registered tel URI or SIP URI whichever is not present IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶92 (item 3 in 4th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B registered public identities containing a Tel URI ✓ UE B default registered public identity is a SIP URI ✓ ✓ UE A has received 180 on initial request for dialog from UE B UE A IMS A IMS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Asserted-Identity header the SIP URI of UE B a P-Asserted-Identity header the Tel URI of UE B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 38 Test Purpose Identifier: TP_IMS_5120_01 Summary: S-CSCF must Remove its URI from the Route header and insert its SIP-URI in the Record Route header on a target refresh request IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶99 (item 3 and 5 in 7th numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent INVITE addressed to UE B 2 INVITE a topmost Route header the S-CSCF SIP URI of IMS B a Record-Route header the S-CSCF SIP URI Test Purpose Identifier: TP_IMS_5120_02 Summary: S-CSCF must Remove its URI from the Route header and insert its SIP-URI in the Record Route header on a target refresh request IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶99 (item 3 and 5 in 7th numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 UPDATE addressed to UE B 2 UPDATE a topmost Route header the S-CSCF SIP URI of IMS B a Record-Route header the S-CSCF SIP URI Test Purpose Identifier: TP_IMS_5121_01 Summary: S-CSCF remove access-network-charging-info parameter from 1xx response to subsequent or target refresh requests IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶123 (9th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B has received a subsequent or target refresh request in a dialog UE A IMS A IMS B UE B Step Direction Message IF 1 1xx response addressed to UE A 2 1xx response a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 39 Test Purpose Identifier: TP_IMS_5121_02 Summary: S-CSCF remove access-network-charging-info parameter from 2xx response to subsequent or target refresh requests IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶123 (9th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B has received a subsequent or target refresh request in a dialog UE A IMS A IMS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5301_01 Summary: S-CSCF shall prior to forwarding a subsequent request remove its own URI from the Route header and add it to the Record-Route header IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶126 (10th numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 BYE 2 BYE Route header || the S-CSCF SIP URI of IMS A a topmost Record-Route header the S-CSCF SIP URI of IMS A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 40 Test Purpose Identifier: TP_IMS_5139_01 Summary: In case the S-CSCF serves the calling user and the S-CSCF receives a network internal indication to release an existing multimedia session including registration lifetime expiration of the last public user identity IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.5.1.2 ¶1 (item 1 and 2 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A NWK IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A NWK IMS A IMS B UE B Step Direction Message IF 1 network internal indication that the lifetime of the last public user identity has expired 2 BYE a Request URI Contact header value of UE B a To header the To header of the 200 response to initial INVITE a From header the From header of the initial INVITE a Call-ID header the Call-ID header of the initial a CSeq header CSeq header of the calling user incremented by one a Route header routing information towards the called user as stored for the dialog a Reason header further headers, based on local policy or the requested session release reason 2 BYE a Request URI Contact address of UE A a To header the From header of the initial INVITE a From header the To header of the 200 response to initial a Call-ID header the Call-ID header of the initial INVITE a CSeq header CSeq header of the called user incremented by one a Route header routing information towards the calling user as stored for the dialog a Reason header further headers, based on local policy or the requested session release reason ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 41 Test Purpose Identifier: TP_IMS_5139_02 Summary: In case the S-CSCF serves the called user and the S-CSCF receives a network internal indication to release an existing multimedia session including registration lifetime expiration of the last public user identity IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.5.1.2 ¶1 (item 3 and 4 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B NWK UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B NWK UE B Step Direction Message IF 1 network internal indication that the lifetime of the last public user identity has expired 2 BYE a Request URI Contact header value of UE A a To header the From header of the initial INVITE a From header the To header of the 200 response to initial INVITE a Call-ID header the Call-ID header of the initial INVITE a CSeq header CSeq header of the called user incremented by one a Route header routing information towards the calling user as stored for the dialog a Reason header further headers, based on local policy or the requested session release reason 2 BYE a Request URI Contact address of UE A a To header the To header of the 200 response to initial INVITE a From header the From header of the initial INVITE a Call-ID header the Call-ID header of the initial INVITE a CSeq header CSeq header of the calling user incremented by one a Route header routing information towards the calling user as stored for the dialog a Reason header further headers, based on local policy or the requested session release reason ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 42 |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.3 Dialog at I-CSCF | Test Purpose Identifier: TP_IMS_5131_01 Summary: I-CSCF shall remove P-Charging-Function-Addresses header from 180 response to initial request IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.3.2.1 ¶62 (after note 11) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received an initial request for a dialog from UE A UE A IMS A IMS B UE B Step Direction Message IF 1 180 response addressed to UE A 2 180 response a P-Charging-Function-Addresses header Test Purpose Identifier: TP_IMS_5131_02 Summary: I-CSCF shall remove P-Charging-Function-Addresses header from 200 response to initial request IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.3.2.1 ¶Clause 5.3.2.1 ¶62 (after note 11) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received 180 on initial request for dialog from UE B UE A IMS A IMS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Charging-Function-Addresses header Test Purpose Identifier: TP_IMS_5132_01 Summary: I-CSCF shall return an appropriate response to initial request to non-existent user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.3.2.1 ¶54 (after 5th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A IMS B not configured with local policy to attempt request routeing UE B not registered in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B a Request URI a non existing user in IMS B 2a 404 response 2b 604 response ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 43 Test Purpose Identifier: TP_IMS_5133_01 Summary: I-CSCF shall return unsuccessful response to initial request to non-registered user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.3.2.1 ¶55 (before 6th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A UE B not registered in IMS B IMS B not configured with a terminating unregistered filter criterion for UE B UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B 2 4xx response |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.4 Dialog at IBCF | Test Purpose Identifier: TP_IMS_5135_01 Summary: If a request includes a Record-Route header the IBCF shall add its own routeable SIP URI to the top of the Record-Route header IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.4.1 ¶7 (after note 4) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE 2 initial INVITE an additional topmost Record-Route header the IBCF SIP URI of IMS A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 44 Test Purpose Identifier: TP_IMS_5137_01 Summary: The IBCF shall perform encryption for topology hiding before an initial INVITE request is sent IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.4.2 ¶1 (items 7 & 8 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B 2 initial INVITE a Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter a Route header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter Test Purpose Identifier: TP_IMS_5137_02 Summary: The IBCF shall perform encryption for topology hiding before 180 response is sent IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.10.4.2 ¶1 (item 8 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received an initial request for a dialog from UE A ✓ IMS B configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 180 response addressed to UE A 2 180 response Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 45 Test Purpose Identifier: TP_IMS_5137_03 Summary: The IBCF shall perform encryption for topology hiding before 200 response is sent IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.10.4.2 ¶(item 8 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received 180 on initial request for dialog from UE B ✓ IMS B configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 200 response addressed to UE A 2 200 response a Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter Test Purpose Identifier: TP_IMS_5137_04 Summary: The IBCF shall perform encryption for topology hiding before an initial REGISTER request is sent IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clauses 5.10.4.1 and 5.10.4.2 ¶1 (1st numbered list) Config Ref: CF_ROAM_REG Entities Condition UE B IMS A IMS B ✓ IMS A configured for topology hiding UE B IMS A IMS B Step Message IF 1 unprotected REGISTER addressed to IMS B 2 REGISTER a Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter a Route header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter a Path header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 46 Test Purpose Identifier: TP_IMS_5404_01 Summary: IBCF shall remove P-Charging-Function-Addresses header from initial INVITE request IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.2 ¶1 (item 8 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B a P-Charging-Function-Addresses header 2 initial INVITE a P-Charging-Function-Addresses header Test Purpose Identifier: TP_IMS_5408_01 Summary: The IBCF shall perform encryption for topology hiding before ACK request is sent IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.3 ¶1 (item 4 in 1st numbered list ) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has received 200OK on initial request for dialog from UE B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 ACK addressed to UE B 2 ACK a Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter a Route header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 47 Test Purpose Identifier: TP_IMS_5408_02 Summary: The IBCF shall perform encryption for topology hiding before CANCEL request is sent IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.3 ¶1 (item 4 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received 180 on initial request for dialog from UE A ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 CANCEL addressed to UE B 2 CANCEL a Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter a Route header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter Test Purpose Identifier: TP_IMS_5408_03 Summary: The IBCF shall perform encryption for topology hiding before BYErequest is sent IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.3 ¶1 (item 4 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 BYE addressed to UE B 2 BYE a Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter a Route header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 48 Test Purpose Identifier: TP_IMS_5408_04 Summary: The IBCF shall perform encryption for topology hiding before subsequent INVITE request is sent IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.2.3 ¶1 (item 4 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B ✓ IMS A configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent INVITE addressed to UE B 2 subsequent INVITE a Via header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter a Route header the IBCF SIP URI of IMS A encrypted consecutive header entries a tokenized-by parameter Test Purpose Identifier: TP_IMS_5414_01 Summary: When IBCF receives an initial INVITE request and it shall respond with a 100 (Trying) provisional response IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.10.3.2 ¶12 (item 1 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ IMS B configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B 2 100 response Test Purpose Identifier: TP_IMS_CONTENT_SHARE_01 Summary: The IBCF shall pass content share specific information in the OPTIONS request IUT Role: IMS A References: Rich Communication Suite Release 2, Technical realization [7], clause 8.1 Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 OPTIONS addressed to UE B 2 OPTIONS a Contact header +g.3gpp.cs-voice feature tag a Accept-Contact header +g.3gpp.cs-voice feature tag ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 49 Test Purpose Identifier: TP_IMS_CONTENT_SHARE_02 Summary: The IBCF shall pass content share specific information in the subsequent INVITE request IUT Role: IMS A References: Rich Communication Suite Release 2, Technical realization [7], clause 8.1 Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 subsequent INVITE addressed to UE B 2 subsequent INVITE a Contact header +g.3gpp.cs-voice feature tag a Accept-Contact header +g.3gpp.cs-voice feature tag Test Purpose Identifier: TP_IMS_CONTENT_SHARE_03 Summary: The IBCF shall transport content sharing rejection in 603 response IUT Role: IMS A References: Rich Communication Suite Release 2, Technical realization [7], clause 8.1 Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 603 response 2 603 response Test Purpose Identifier: TP_IMS_CONTENT_SHARE_04 Summary: The IBCF shall transport content sharing rejection in 603 response IUT Role: IMS A References: Rich Communication Suite Release 2, Technical realization [7], clause 8.1 Config Ref: CF_INT_ROAM Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE A has initiated a dialog with UE B UE A IMS A IMS B UE B Step Direction Message IF 1 603 response 2 603 response ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 50 |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.5 Messaging Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.5.1 Messaging at P-CSCF | Test Purpose Identifier: TP_IMS_5050_01 Summary: When the P-CSCF receives a MESSAGE request from a UE for which a Service-Route header list exists without topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.3 ¶(1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B IMS A not configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE 2 MESSAGE a Route header || the P-CSCF SIP URI of IMS A the list of Service Route header URIs from registration a P-Preferred-Identity header P-Asserted-Identity header an address of UE A the P-Charging-Vector header an icid-value parameter |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.5.2 Messaging at S-CSCF | Test Purpose Identifier: TP_IMS_5097_05 Summary: S-CSCF must inserts orig-ioi parameter, remove access-network-charging-info parameter before sending MESSAGE over NNI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶1 Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B IMS A not configured for topology hiding UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B 2 MESSAGE a Route header the S-CSCF SIP URI of IMS A a P-Charging-Vector header an icid-value parameter an orig-ioi parameter IMS A an access-network-charging-info parameter a term-ioi parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 51 Test Purpose Identifier: TP_IMS_5097_06 Summary: S-CSCF inserts a second P-Asserted-Identity header indicating a tel URI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 9 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE A registered public identities containing a SIP URI UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B 2 MESSAGE a P-Asserted-Identity header the SIP URI of UE A a P-Asserted-Identity header the Tel URI of UE A Test Purpose Identifier: TP_IMS_5097_07 Summary: S-CSCF inserts a second P-Asserted-Identity header indicating a SIP URI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 9 in 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE A registered public identities containing a Tel URI UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B 2 MESSAGE a P-Asserted-Identity header the SIP URI of UE A a P-Asserted-Identity header the Tel URI of UE A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 52 Test Purpose Identifier: TP_IMS_5097_08 Summary: S-CSCF uses ENUM/DNS to translate Tel URIs to SIP URIs in MESSAGE requests IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 10 in1st numbered) Config Ref: CF_INT_CALL Entities Condition UE A IMS A ENUM _DB IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ ENUM_DB configured with an ENUM entry for Tel URI E.164 Number of UE B UE A IMS A ENUM _DB IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B a Request URI a Tel URI 2 NAPTR Query the Tel URI E.164 Number 3 NAPTR Response NAPTR Resource Record the SIP URI of UE B 4 MESSAGE addressed to UE B a Request URI a SIP URI of UE B a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5097_10 Summary: MESSAGE handling by S-CSCF with matching filter criteria AS IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 5 and 8 in 1st numbered list) Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B visiting IMS A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ ✓ AS B within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 MESSAGE addressed to UE A 2 MESSAGE a Route header the SIP URI of AS B a P-Charging-Function-Addresses header a P-Charging-Vector header an access-network-charging-info parameter an orig-ioi parameter IMS A ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 53 Test Purpose Identifier: TP_IMS_5108_01 Summary: Standalone request; terminated at the served user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶5 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 INVITE addressed to UE B a P-Charging-Vector header an icid-value parameter 2 INVITE Route header || the S-CSCF SIP URI of IMS B a P-Charging-Vector header the same icid-value parameter ioi parameters a Record-Route header the S-CSCF SIP URI of IMS B Test Purpose Identifier: TP_IMS_5108_02 Summary: Standalone request; terminated at the served user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶5 (1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B a P-Charging-Vector header an icid-value parameter 2 MESSAGE Route header || the S-CSCF SIP URI of IMS B a P-Charging-Vector header the same icid-value parameter ioi parameters a Record-Route header the S-CSCF SIP URI of IMS B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 54 Test Purpose Identifier: TP_IMS_5108_06 Summary: S-CSCF rejects barred users on MESSAGE IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶6 (item 1 in1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B barred user in IMS B UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B a Request URI a barred user in IMS B 2 404 response Test Purpose Identifier: TP_IMS_5117_01 Summary: S-CSCF remove access-network-charging-info parameter from 1xx response to standalone transaction IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶100 (item 2 in 5th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B has received a standalone request UE A IMS A IMS B UE B Step Direction Message IF 1 1xx response addressed to UE A 2 1xx response a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5117_02 Summary: S-CSCF remove access-network-charging-info parameter from 2xx response to standalone transaction IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶100 (item 2 in 5th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B has received a standalone request UE A IMS A IMS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 55 Test Purpose Identifier: TP_IMS_5117_05 Summary: S-CSCF inserts a second P-Asserted-Identity header in 1xx response from UE for initial request indicating a registered SIP URI if not present IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶(item 1 in 5th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B registered_public_identities containing a Tel_URI and a SIP_URI ✓ ✓ UE B has received a standalone request from UE A UE A IMS A IMS B UE B Step Direction Message IF 1 1xx response addressed to UE A 2 1xx response a P-Asserted-Identity header the tel URI of UE B a P-Asserted-Identity header a SIP URI of UE B Test Purpose Identifier: TP_IMS_5117_06 Summary: S-CSCF inserts a second P-Asserted-Identity header in 2xx response from UE for initial request indicating a registered SIP URI if not present IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶100 (item 1 in 5th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ UE B registered_public_identities containing a Tel_URI and a SIP_URI ✓ ✓ UE B has received a standalone request from UE A UE A IMS A IMS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Asserted-Identity header the tel URI of UE B a P-Asserted-Identity header the SIP URI of UE B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 56 Test Purpose Identifier: TP_IMS_5118_01 Summary: S-CSCF include term-ioi parameter and restores orig-ioi in 200 responses to standalone requests IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶105 (item 2 in 6th numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received a standalone request from UE A UE A IMS A IMS B UE B Step Direction Message IF 1 200 response addressed to UE A 2 200 response a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter operator identifier of IMS B |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.6 Application Server Handling Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.6.1 Application Server Handling at S-CSCF | Test Purpose Identifier: TP_IMS_5097_09 Summary: Initial request for a dialog handling by S-CSCF with matching filter criteria AS IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list ) Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B visiting IMS A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ ✓ AS B within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 initial INVITE addressed to UE A 2 initial INVITE a Route header the SIP URI of AS B a P-Charging-Function-Addresses header a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter access-network-charging-info ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 57 Test Purpose Identifier: TP_IMS_5097_13 Summary: Standalone request handling by S-CSCF with matching filter criteria AS IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B visiting IMS A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ ✓ AS B within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 PUBLISH sent by UE_B 2 PUBLISH a Route header the SIP URI of AS B a P-Charging-Function-Addresses header a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter access-network-charging-info Test Purpose Identifier: TP_IMS_5097_14 Summary: Initial request for a dialog handling by S-CSCF with matching filter criteria AS IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list) Config Ref: CF_IP_TV Entities Condition UE A IMS A AS A ✓ ✓ UE A registered in IMS A ✓ ✓ IMS A configured with filter criteria to contact AS A UE A IMS A AS A Step Direction Message IF 1 SUBSCRIBE a Route header the SIP URI of AS A a P-Charging-Function-Addresses header a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter access-network-charging-info ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 58 Test Purpose Identifier: TP_IMS_5108_03 Summary: Request for a initial dialog terminated at the served user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) Config Ref: CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS A ✓ ✓ IMS B configured with filter criteria to contact AS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B 2 INVITE a topmost Route header the SIP URI of AS B a Route header the S-CSCF SIP URI of IMS B a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter Test Purpose Identifier: TP_IMS_5108_04 Summary: Standalone request; terminated at the served user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶5 (item 4 in1st numbered list ) Config Ref: CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ IMS B configured with filter criteria to contact AS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B 2 MESSAGE a topmost Route header the SIP URI of AS B a Route header the S-CSCF SIP URI of IMS B a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 59 Test Purpose Identifier: TP_IMS_5108_07 Summary: Request for a initial dialog terminated at the served user (SUBSCRIBE) IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶(item 4 in 1st numbered list) Config Ref: CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS A ✓ ✓ IMS B configured with filter criteria to contact AS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 SUBSCRIBE addressed to UE B 2 SUBSCRIBE a topmost Route header the SIP URI of AS B a Route header the S-CSCF SIP URI of IMS B a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter Test Purpose Identifier: TP_IMS_5109_01 Summary: S-CSCF returns 408 or 5xx response to initial terminating INVITE when there is no response from AS and filter criterion indicates the value SESSION_TERMINATED IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶76 (after 2nd numbered list) Config Ref: CF_INT_CALL CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A UE B not registered ✓ ✓ IMS B configured with a terminating unregistered filter criterion for UE B indicating SESSION TERMINATED on INVITE UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B 2a 408 response 2b 5xx response Test Purpose Identifier: TP_IMS_5110_01 Summary: Forward 200 from AS on final response to an initial request for a dialog or a standalone request IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶79 (after 6th dashed list) Config Ref: CF_INT_AS CF_ROAM_AS Entities Condition UE A AS A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ IMS A configured with filter criteria to contact AS A ✓ ✓ UE B has received 180 on initial request for dialog from UE A UE A AS A IMS A IMS B UE B Step Direction Message IF 1 200 response addressed to UE B 2 200 response ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 60 Test Purpose Identifier: TP_IMS_5114_01 Summary: S-CSCF should turn down initial dialog request when terminated at the not registered served user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶85 (item 3 in 3rd numbered list) Config Ref: CF_INT_CALL CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS B UE B not registered IMS B not configured with filter criteria to contact any AS UE A IMS A IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B 2 4xx response Test Purpose Identifier: TP_IMS_5114_02 Summary: S-CSCF should turn down standalone request when terminated at the not registered served user IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶85 (item 3 in 3rd numbered list) Config Ref: CF_INT_CALL CF_ROAM_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A UE B not registered IMS B not configured with filter criteria to contact any AS UE A IMS A IMS B UE B Step Direction Message IF 1 MESSAGE addressed to UE B 2 4xx response Test Purpose Identifier: TP_IMS_5115_07 Summary: S-CSCF include term-ioi parameter and restores orig-ioi in 1xx responses from AS to initial requests in terminating network IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶89 (4th numbered list) Config Ref: CF_ROAM_AS CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ ✓ AS B has received an initial request for a dialog from UE A UE A IMS A IMS B AS B UE B Step Direction Message IF 1 1xx response addressed to UE A 2 1xx response a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter operator identifier of IMS B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 61 Test Purpose Identifier: TP_IMS_5115_08 Summary: S-CSCF include term-ioi parameter and restores orig-ioi in 2xx responses from AS to initial requests in terminating network Clause: References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶89 (4th numbered list) Config Ref: CF_ROAM_AS CF_INT_AS IUT Role: IMS B Test Case: TC_IMS_5115_08 Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ AS B has received an initial request for a dialog from UE A UE A IMS A IMS B AS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter operator identifier of IMS B Test Purpose Identifier: TP_IMS_5118_02 Summary: S-CSCF include term-ioi parameter and restores orig-ioi in 200 responses from AS to standalone requests IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶106 (item 2 in 6th numbered list) Config Ref: CF_ROAM_AS CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ ✓ AS B has received a standalone request from UE A UE A IMS A IMS B AS B UE B Step Direction Message IF 1 200 response addressed to UE A 2 200 response a P-Charging-Vector header an orig-ioi parameter operator identifier of IMS A a term-ioi parameter operator identifier of IMS B ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 62 Test Purpose Identifier: TP_IMS_5302_01 Summary: The S-CSCF shall retain the access-network-charging-info parameter in the P-Charging-Vector header a 1xx or 2xx response to AS IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶(after 11th numbered list) Config Ref: CF_ROAM_AS CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received a subsequent request in a dialog from UE A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ ✓ AS B within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5302_02 Summary: The S-CSCF receives a 1xx or 2xx response and not AS in same trust domain then it shall remove the access-network-charging-info parameter in the P-Charging-Vector header IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.3 ¶(after 11th numbered list) Config Ref: CF_ROAM_AS CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has received a subsequent request in a dialog from UE A ✓ ✓ IMS B configured with filter criteria to contact AS B AS B not within the trust domain UE A IMS A IMS B AS B UE B Step Direction Message IF 1 2xx response addressed to UE A 2 2xx response a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 63 Test Purpose (TO BE REVISITED) Identifier: TP_IMS_5206_01 Summary: REGISTER request if there is at least on AS that matches Filter Criteria IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.2.2F ¶15 (before note 3) Config Ref: CF_ROAM_AS Entities Condition IMS B AS B UE B ✓ ✓ UE B configured with filter criteria to contact AS B ✓ ✓ IMS B has challenged with a 401 response the REGISTER request of UE B IMS B AS B UE B Step Direction Message IF 1 protected REGISTER an Authorization header an integrity-protected parameter set on (yes or tls-pending or tls-yes or ip-assoc-pending or ip-assoc-yes) 2 third party REGISTER a P-Access-Network-Info header a P-Visited-Network-ID header 3 200 response Test Purpose Identifier: TP_IMS_5308_01 Summary: Retain the access-network-charging-info parameter from the P-Charging-Vector header in 180 to AS IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.4.2.2 ¶2 Config Ref: CF_INT_AS CF_ROAM_AS Entities Condition UE A AS A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ IMS A configured with filter criteria to contact AS A ✓ ✓ AS A has received an initial request for a dialog from UE B UE A AS A IMS A IMS B UE B Step Direction Message IF 1 180 response a P-Charging-Vector header an access-network-charging-info parameter 2 180 response a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 64 Test Purpose Identifier: TP_IMS_5308_02 Summary: Retain the access-network-charging-info parameter from the P-Charging-Vector header in 200 to AS IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.4.2.2 ¶2 Config Ref: CF_INT_AS CF_ROAM_AS Entities Condition UE A AS A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ IMS A configured with filter criteria to contact AS A ✓ ✓ AS A has received 180 on initial request for dialog from UE B UE A AS A IMS A IMS B UE B Step Direction Message IF 1 200 response a P-Charging-Vector header an access-network-charging-info parameter 2 200 response a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5310_01 Summary: Retaining the access-network-charging-info parameter from the P-Charging-Vector IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.6.1.2 ¶1 Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ AS B is within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 subsequent INVITE a P-Charging-Vector header an access-network-charging-info parameter 2 INVITE a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 65 Test Purpose Identifier: TP_IMS_5310_02 Summary: Not retaining the access-network-charging-info parameter from the P-Charging-Vector IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.6.1.2 ¶1 Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ AS B has initiated a dialog with UE A ✓ ✓ IMS B configured with filter criteria to contact AS B AS B is not within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 subsequent INVITE P-Charging-Vector header an access-network-charging-info parameter 2 INVITE a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5310_03 Summary: Retaining in UPDATE the access-network-charging-info parameter from the P-Charging-Vector IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.6.1.2 ¶1 Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ AS B is within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 subsequent UPDATE a P-Charging-Vector header an access-network-charging-info parameter 2 UPDATE a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 66 Test Purpose Identifier: TP_IMS_5310_04 Summary: Not retaining in UPDATE the access-network-charging-info parameter from the P-Charging-Vector IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.6.1.2 ¶1 Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A ✓ ✓ IMS B configured with filter criteria to contact AS B AS B is not within the trust domain of IMS B UE A IMS A IMS B AS B UE B Step Direction Message IF 1 subsequent UPDATE P-Charging-Vector header an access-network-charging-info parameter 2 UPDATE a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5312_01 Summary: Retaining the access-network-charging-info parameter from the P-Charging-Vector on 200 (OK) response IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.6.1.3 ¶1 Config Ref: CF_ROAM_AS CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ UE B has initiated a dialog with UE A ✓ ✓ IMS B configured with filter criteria to contact AS B ✓ ✓ UE B having sent subsequent INVITE or UPDATE to UE A UE A IMS A IMS B AS B UE B Step Direction Message IF 1 200 response addressed to UE B a P-Charging-Vector header an access-network-charging-info parameter 2 200 response a P-Charging-Vector header an access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 67 Test Purpose Identifier: TP_IMS_5313_01 Summary: Retaining the access-network-charging-info parameter from the P-Charging-Vector on any SIP request IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.6.1.3 ¶2 Config Ref: CF_INT_AS CF_ROAM_AS Entities Condition UE A AS A IMS A IMS B UE B ✓ ✓ UE A registered in IMS B ✓ ✓ UE B registered in IMS B ✓ ✓ IMS A configured with filter criteria to contact AS A ✓ ✓ AS A has initiated a dialog with UE B ✓ AS A is within the trust domain of IMS A UE A AS A IMS A IMS B UE B Step Direction Message IF 1 a response a P-Charging-Vector header an access-network-charging-info parameter 2 The response a P-Charging-Vector header an access-network-charging-info parameter Test Purpose Identifier: TP_IMS_5313_02 Summary: Not retaining the access-network-charging-info parameter from the P-Charging-Vector on any SIP request Clause: References: TS 124 229 (V9.5.0) [1], clause 5.4.6.1.3 ¶2 Config Ref: CF_INT_AS IUT Role: IMS A Test Case: TC_IMS_5313_02 Entities Condition UE A AS A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ IMS A configured with filter criteria to contact AS A ✓ ✓ AS A has initiated a dialog with UE B AS A is not within the trust domain of IMS A UE A AS A IMS A IMS B UE B Step Direction Message IF 1 a response a P-Charging-Vector header an access-network-charging-info parameter 2 the response a P-Charging-Vector header access-network-charging-info parameter ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 68 Test Purpose Identifier: TP_IMS_5320_01 Summary: S-CSCF is failing to receive a SIP response or receive 408 (Request Timeout) response or a 5xx response from the AS IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶91 (after note 15) Config Ref: CF_ROAM_AS CF_INT_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ AS B has received an initial request for a dialog from UE B ✓ ✓ AS B filter criteria default handling in IMS B set to SESSION TERMINATED UE A IMS A IMS B AS B UE B Step Direction Message IF 1 || || Any response 2a 408 response 2b 5xx response |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.7 MGCF tests for IMS-PSTN interconnection | Test Purpose Identifier: TP_IMS_MGCF_01 Summary: MGCF shall send INVITE due to indication of an incoming call Clause: TS 124 229 [1], clause 5.5.3.1.1 References: RQ_24.229_5.5.3.1.1 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_01 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 initial IAM 2 INVITE a Request URI Tel URI E.164 Number or (Sip URI E.164 Number with user portion phone) a Contact header anyvalue GRUU format a Supported header an 100rel value a P-Asserted-Identity header a P-Charging-Vector header an icid-value parameter a SDP codec supported curr precondition Test Purpose Identifier: TP_IMS_MGCF_02 Summary: MGCF shall send 100 response due to indication of an incoming INVITE Clause: TS 124 229 [1], clause 5.5.3.1.2 References: RQ_24.229_5.5.3.1.2 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_02 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 initial INVITE 2 100 response ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 69 Test Purpose Identifier: TP_IMS_MGCF_03 Summary: MGCF shall send 183 response codec found or not required Clause: TS 124 229 [1], clause 5.5.3.1.2 References: RQ_24.229_5.5.3.1.2 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_03 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 initial INVITE 2 100 response 3 183 response Require header 100rel value a P-Charging-Vector header a term-ioi parameter the operator identifier of IMS A Test Purpose Identifier: TP_IMS_MGCF_05 Summary: MGCF shall send UPDATE request Clause: TS 124 229 [1], clause 5.5.3.2.1 References: RQ_24.229_5.5.3.2.1 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_05 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 200 response for PRACK conditions fulfilled 2 UPDATE Test Purpose Identifier: TP_IMS_MGCF_06 Summary: MGCF shall send 180 response due to indication of an ACM/CPG Clause: TS 129 163 [6], clause 7.2.3.1.4, TS 124 229 [1], clause 5.5.3.2.2 References: RQ_29.163_7.2.3.1.4 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_06 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1a ACM subscriber free 1b CPG ALERTING 2 180 response Test Purpose Identifier: TP_IMS_MGCF_07 Summary: MGCF shall send 200 response due to indication of ANM Clause: TS 129 163 [6], clause 7.2.3.1.5, TS 124 229 [1], clause 5.5.3.2.2 References: RQ_29.163_7.2.3.1.5 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_07 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 ANM 2 200 response ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 70 Test Purpose Identifier: TP_IMS_MGCF_08 Summary: MGCF shall send BYE response due to indication of release Clause: TS 129 163 [6], clause 7.2.3.1.8, TS 124 229 [1], clause 5.5.4.1 References: RQ_29.163_7.2.3.1.8 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_08 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 REL 2 BYE Test Purpose Identifier: TP_IMS_MGCF_09 Summary: MGCF shall send 486 response due to indication of release with cause indicator 17 Clause: TS 129 163 [6], clause 7.2.3.1.8 References: RQ_29.163_7.2.3.1.8 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_09 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 REL cause17 2 486 response Test Purpose Identifier: TP_IMS_MGCF_10 Summary: MGCF shall send REL with cause #17 or #34 with Diagnostic due to 486 Busy here Clause: TS 129 163 [6], clause 7.2.3.2.12 References: RQ_29.163_7.2.3.2.12 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_10 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 486 response 2 REL cause17 or cause34 Test Purpose Identifier: TP_IMS_MGCF_11 Summary: MGCF shall send CPG with a 'remote hold' Generic notification indicator on receipt of HOLD request from IMS Clause: TS 129 163 [6], clause 7.4.10.1 References: RQ_29.163_7.4.10.1 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_11 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement ✓ ✓ IMS A and PSTN call active IMS_A IUT PSTN Step Direction Message IF 1 UPDATE or a target refresh INVITE a SDP sendonly 2 CPG remote hold ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 71 Test Purpose Identifier: TP_IMS_MGCF_12 Summary: MGCF shall send CPG with a 'remote retrieve' Generic notification indicator on receipt of Resume request from IMS Clause: TS 129 163 [6], clause 7.4.10.1 References: RQ_29.163_7.4.10.1 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_12 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement ✓ ✓ IMS A and PSTN call on hold IMS_A IUT PSTN Step Direction Message IF 1 UPDATE or a target refresh INVITE a SDP sendrecv 2 CPG remote retrieve Test Purpose Identifier: TP_IMS_MGCF_13 Summary: MGCF shall send CPG with a 'remote hold' Generic notification indicator on receipt of HOLD request from IMS Clause: TS 129 163 [6], clause 7.4.10.2 References: RQ_29.163_7.4.10.2 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_13 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement ✓ ✓ IMS A and PSTN call active IMS_A IUT PSTN Step Direction Message IF 1 CPG remote hold 2 UPDATE or a target refresh INVITE a SDP sendonly Test Purpose Identifier: TP_IMS_MGCF_14 Summary: MGCF shall send CPG with a 'remote retrieve' Generic notification indicator on receipt of Resume request from IMS Clause: TS 129 163 [6], clause 7.4.10.2 References: RQ_29.163_7.4.10.2 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_14 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement ✓ ✓ IMS A and PSTN call on hold IMS_A IUT PSTN Step Direction Message IF 1 CPG remote retrieve 2 UPDATE or a target refresh INVITE a SDP sendonly ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 72 Test Purpose Identifier: TP_IMS_MGCF_15 Summary: MGCF shall send ACM/CPG due to indication of a 180 response Clause: TS 129 163 [6], clauses 7.2.3.2.4 and 7.2.3.2.6 References: RQ_29.163_7.2.3.2.4_and_6 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_15 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 180 response 2 ACM subscriber free or sends a CPG ALERTING Test Purpose Identifier: TP_IMS_MGCF_16 Summary: MGCF shall send ANM due to indication of a 200 response Clause: TS 129 163 [6], clause 7.2.3.2.8 References: RQ_29.163_7.2.3.2.8 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_16 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 200 response 2 ANM Test Purpose Identifier: TP_IMS_MGCF_17 Summary: MGCF shall send REL due to indication of a BYE Clause: TS 129 163 [6], clause 7.2.3.2.13 References: RQ_29.163_7.2.3.2.13 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_17 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arrangement IMS_A IUT PSTN Step Direction Message IF 1 BYE 2 REL ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 73 |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.8 ENUM tests for Tel-URI Resolution | Test Purpose Identifier: TP_IMS_ENUM_01 Summary: The ENUM DB resolves a Tel URI into a SIP URI IUT Role: IMS A References: TS124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 10 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A ENUM _DB IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B ✓ ✓ ENUM_DB configured with an ENUM entry for Tel URI E.164 Number of UE B UE A IMS A ENUM _DB IMS B UE B Step Direction Message IF 1 initial INVITE addressed to UE B a Request URI a Tel URI 2 NAPTR Query the derived Tel URI E.164 Number 3 NAPTR Response NAPTR Resource Record the TTL of the NAPTR record the service type E2U+sip the regular expression !^(.*)$! the SIP URI of UE B backreference (\1) for the user part domain name for the host part the SIP URI parameters if applicable ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 74 Annex A (normative): Zip file with TPLan code The test purposes defined in the present document have been automatically generated from the TPLan text files in the archive file ts_18601101v040103p0.zip which accompanies the present document. The raw text files has been converted to a symbolic table format to allow better readability. ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 75 Annex B (normative): IMS NNI Interoperability Test Configurations IMS NNI interoperability test configuration identifiers have been composed using on the following abbreviations: • REG: Only one UE • CALL: One or two UEs • AS: One or two UEs plus Application Server for one UE • ROAM: UE B is roaming in home network of UE A • INT: UE A and B are in interoperating home networks • PSTN: One user is located in the PSTN • IPTV: Only one UE, AS for IPTV present • CONF: Two UEs, AS for Conference present Note that all test configurations assume that observable interfaces are indicated as a solid line, non-observable interfaces as indicated dashed lines, and that IBCF acts in a "pass-through" mode if topology hiding is not required. HSS HSS UE B Mx IMS A IMS B Gm PCO PO Roaming Registration CF_ROAM_REG IBCF A P-CSCF I-CSCF S-CSCF IBCF A PO PO Mx Ic Precondition: Different network operators performing origination and termination, UE_B roaming in visited network A (ROAM). UE_B not yet registered (REG), neither UE_A nor AS involved, a common interconnect ENUM DB and local ENUM is involved, IBCF is involved but no topology hiding performed. Test configuration for: Registration requests and responses from UE_B Example: REGISTER prior to IMS VoIP voice call from UE_B ENUM DB Figure B.1: CF_ROAM_REG ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 76 HSS HSS UE A UE B Mx IMS A IMS B Gm PCO Gm PCO PO Interworking Call CF_INT_CALL IBCF A P-CSCF I-CSCF S-CSCF P-CSCF IBCF A S-CSCF I-CSCF PO PO Mx Ic Precondition: Different network operators performing origination and termination, both Ues or only UE_A in home networks (INT), both Ues registered, no AS, a common interconnect ENUM DB and local ENUM is involved, IBCF is involved, topology hiding may apply. Test configuration for: Requests and responses between UE_A and UE_B in call (CALL) and messaging scenarios. Unsuccessful initiall requests and responses from UE_A (when UE_B is nor registered) Example: Initial INVITE in IMS VoIP voice call from UE_A to UE_B ENUM DB PO PO Figure B.2: CF_INT_CALL HSS HSS UE A UE B Mx IMS A IMS B Gm PCO PO Roaming Call CF_ROAM_CALL IBCF A P-CSCF I-CSCF S-CSCF P-CSCF IBCF A S-CSCF I-CSCF PCO PO PO Mx Ic Precondition: Different network operators performing origination and termination, UE_B roaming (ROAM) via IMS_A, UE_A in home network, both Ues are registered, no AS, a common interconnect ENUM DB and local ENUM is involved, IBCF is involved, topology hiding may apply. Test configuration for: Requests and responses between UE_B and UE_A in call (CALL) and messaging scenarios Example: Initial INVITE in IMS VoIP voice call from UE_B to UE_A ENUM DB Gm Figure B.3: CF_ROAM_CALL ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 77 HSS HSS UE A UE B Mx IMS A IMS B Gm PCO Gm PCO PO Interworking Application Server CF_INT_AS IBCF A AS A P-CSCF I-CSCF S-CSCF P-CSCF IBCF A S-CSCF I-CSCF PCO ISC PCO AS B ISC PO PO Mx Ic Precondition: Different network operators performing origination and termination, UE_A and UE_B in home networks INT), both UEs registered, AS for UE_A and UE_B (AS), a common interconnect ENUM DB and local ENUM is involved, IBCF is involved, topology hiding may apply. Test configuration for: Requests and responses between ASes and UEs Example: Initial INVITE in IMS VoIP voice call unconditionally forwarded to UE_B by AS_A (CFU), AS_A acts as routing AS ENUM DB Figure B.4: CF_INT_AS HSS HSS UE A UE B Mx IMS A IMS B Gm PCO Gm PCO PO Roaming Application Server CF_ROAM_AS IBCF A AS A I-CSCF S-CSCF P-CSCF IBCF A S-CSCF I-CSCF PCO ISC PCO AS B ISC PO PO Mx Ic Precondition: Different network operators performing origination and termination, UE_B roaming (ROAM) via IMS_A, UE_A in home network, both Ues are registered, AS for UE_A and UE_B may be involved (AS), a common interconnect ENUM DB and local ENUM is involved, IBCF is involved, topology hiding may apply. Test configuration for: Requests and responses between AS_B and UEs Example: Initial INVITE in IMS VoIP voice call unconditionally forwarded to UE_B by AS_B (CFU), AS_B acts as routing AS ENUM DB UE B P-CSCF Gm PCO Figure B.5: CF_ROAM_AS ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 78 HSS HSS UE A UE B IMS A IMS B Gm PCO Gm PCO Interworking Conference Server CF_INT_CONF_AS P-CSCF MRFC S-CSCF P-CSCF I-CSCF PCO ISC PO Mw Precondition: Different network operators performing origination and termination, both Ues or only UE_A in home networks (INT), both UEs registered, CONF AS is involved in IMS_A, a common interconnect ENUM DB and local ENUM is involved, IMS_A and IMS_B both include MRFC and MRFP Test configuration for: Requests and responses between UE_A and UE_B in an Ad-hoc Conference call (CONF_CALL) Example: Initial INVITE from UE_A to initiate an ad-hoc Conference call in IMS_A, and subsequent invitation to UE_B to join (via REFER method from UE_A) ENUM DB MRFC Conf AS A Mb S-CSCF MRFP I-CSCF MRFP Figure B.6: CF_INT_CONF_CALL HSS UE A IMS A Gm PCO IPTV CF_IPTV P-CSCF I-CSCF PCO ISC Precondition: UE_A registered in home network, IPTV_AS involved Test configuration for: Requests and responses between UE_A and IPTV AS Example: Initial INVITE from UE_A to initiate an IPTV Broadcast session S-CSCF IBCF IPTV AS Figure B.7: CF_IPTV ENUM PO ENUM PO ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 79 HSS UE A Mx IMS A Legacy Network Gm PCO PO PSTN Interworking CF_PSTN MGCF AS A P-CSCF S-CSCF I-CSCF PCO ISC PCO ISC PO E1 Precondition: Different network operators performing origination and termination, UE_A and UE_B in home networks INT), both UEs registered, AS for UE_A and UE_B (AS), a common interconnect ENUM DB and local ENUM is involved, IBCF is involved, topology hiding may apply. Test configuration for: Requests and responses between ASes and UEs Example: Initial INVITE in IMS VoIP voice call unconditionally forwarded to UE_B by AS_A (CFU), AS_A acts as routing AS ENUM DB ISDN PSTN Figure B.8: CF_PSTN ENUM PO ETSI ETSI TS 186 011-1 V4.1.3 (2012-05) 80 History Document history V1.0.0 April 2008 Publication V1.1.1 March 2009 Publication V2.1.1 February 2009 Publication V2.2.1 March 2009 Publication V2.3.1 April 2010 Publication V3.1.1 June 2011 Publication V4.1.1 October 2011 Publication V4.1.3 May 2012 Publication |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 1 Scope | The present document specifies the Protocol implementation conformance statement (PICS) for the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. Within the Next Generation Network (NGN) the stage 3 is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), TS 183 005 [1]. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. 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. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Conference (CONF); Protocol specification". [2] ETSI TS 186 010-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Conference (CONF); Part 1: Protocol implementation Conformance Statement (PICS)". [3] ETSI TS 124 147: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.147 version 8.2.0 Release 8)". |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 6 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 3 Definitions and abbreviations | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] apply. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] apply. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 4 Test Suite Structure (TSS) and configuration | Table 1: Test suite structure ConferenceFocus CONF_N01_xxx CONF_N02_xxx CONF_N03_xxx CONF_N04_xxx CONF_N05_xxx CONF_N06_xxx CONF_N07_xxx UserEquipment CONF_U01_xxx Interaction TIR CONF_N08_xxx OIR CONF_N09_xxx ACR CONF_N10_xxx |
40c2d32598e77728c3ce47d803f09a6f | 186 010-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. Figure 1: Applicable interface to test AS functionalities ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 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 2 illustrates the usage of any NNI interface. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5 Test Purposes (TP) | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.1 Introduction | For each test requirement a TP is defined. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-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 2). Table 2: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "CONF" <iut> = type of IUT: U User N Network yyy service <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999) |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.1.2 Test strategy | As the base standard TS 183 005 [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 186 010-1 [2]. ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 8 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2 Signalling requirements | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1 Conference Focus | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.1 Conference creation | TSS ConferenceFocus TP CONF_N01_001 Reference 5.3.2.3/ [3] Selection expression Test purpose Conference creation with a conference factory URI. Conference event package subscribed. Ensure that a conference can be created by a UE using the conference factory URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store the content of the received Contact header as the conference URI. In addition the conference participant subscribes to the conference event package. SIP header values: INVITE: Request URI contained the conference factory URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field SUBSCRIBE: Request URI contained the conference URI Event header contains "conference" NOTIFY: Event contains conference; Subscription-State contains active; expires=xxxx Comments: ISC#1 Focus INVITE 200 OK (INVITE) ACK SUBSCRIBE 200 OK (SUBSCRIBE) NOTIFY 200 OK NOTIFY Apply post test routine TSS ConferenceFocus TP CONF_N01_002 Reference 5.3.2.3/[3] Selection expression Test purpose Conference creation with a conference factory URI. Conference event package not subscribed. Ensure that a conference can be created by a UE using the conference factory URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store the content of the received Contact header as the conference URI. The conference participant does not subscribe to the conference event package. SIP header values: INVITE: Request URI contained the conference factory URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus INVITE 200 OK (INVITE) ACK Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 9 TSS ConferenceFocus TP CONF_N01_003 Reference 5.3.2.3/[3] Selection expression PICS 1/5 Test purpose Conference creation with a conference URI. Conference event package subscribed. Ensure that a conference can be created by a UE using the conference URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store the content of the received Contact header as the conference URI. In addition the conference participant subscribes to the conference event package. SIP header values: INVITE: Request URI contained the conference URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field SUBSCRIBE: Request URI contained the conference URI Event header contains "conference" NOTIFY: Event contains conference; Subscription-State contains active; expires=xxxx Comments: ISC#1 Focus INVITE 200 OK (INVITE) ACK SUBSCRIBE 200 OK (SUBSCRIBE) NOTIFY 200 OK NOTIFY Apply post test routine TSS ConferenceFocus TP CONF_N01_004 Reference 5.3.2.3/[3] Selection expression PICS 1/5 Test purpose Conference creation with a conference URI. Conference event package not subscribed. Ensure that a conference can be created by a UE using the conference URI. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store the content of the received Contact header as the conference URI. The conference participant does not subscribe to the conference event package. SIP header values: INVITE: Request URI contained the conference URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus INVITE 200 OK (INVITE) ACK Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 10 TSS ConferenceFocus TP CONF_N01_005 Reference 5.3.2.3/[3] Selection expression NOT PICS 1/4 AND PICS 1/7 Test purpose Conference creation with a conference factory URI. Preconditions indicated a conference URI is sent in the first provisional response. Ensure that a conference can be created by a UE using the conference factory URI. Preconditions are requested by the originating UE. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store the content of the received Contact header as the conference URI. SIP header values: INVITE: Request URI contained the conference factory URI SDP a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos none remote sendrecv 183 conference URI contained in the Contact header field SDP a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos mandatory remote sendrecv a=conf:qos remote sendrecv UPDATE: SDP a=curr:qos local sendrecv a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos mandatory remote sendrecv 200 OK UPDATE SDP a=curr:qos local sendrecv a=curr:qos remote sendrecv a=des:qos mandatory local sendrecv a=des:qos mandatory remote sendrecv 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field SUBSCRIBE: Request URI contained the conference URI Comments: ISC#1 Focus INVITE 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 200 OK (INVITE) ACK Apply post test routine TSS ConferenceFocus TP CONF_N01_007 Reference 5.3.2.3/[3] Selection expression Test purpose Conference creation with a conference factory URI not allocated in the focus unsuccessful. Ensure that a conference cannot be created by a UE using the conference factory URI not allocated in the focus. The request is rejected by the focus with a 488 Not Acceptable Here final response. SIP header values: INVITE: Request URI contained the conference factory URI not allocated in the focus Comments: ISC#1 Focus INVITE 488 Not Acceptable Here ACK ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 11 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.2 Joining a conference | TSS ConferenceFocus TP CONF_N02_001 Reference 5.3.2.4/[3] Selection expression NOT PICS 1/6 Test purpose Participant dial-in the conference, the conference URI is used. ISC#1 established a conference. ISC#2 joins in that conference after has been received a REFER request and the Refer-To header referring to the Focus. The UE sends an INVITE request to the conferencing AS the conference URI is known at the ISC#2. The request is successful. SIP header values: REFER: Request URI=ISC#2 Refer-To=Focus; method=INVITE Referred-By=ISC#1 INVITE 2: Focus 18x "isfocus" feature parameter indicated in Contact header field 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#2 joining in the conference REFER REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK (NOTIFY) 200 OK (NOTIFY) INVITE INVITE 2 18x 18x 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY (200) NOTIFY (200) 200 OK (NOTIFY) 200 OK (NOTIFY) Apply post test routine TSS ConferenceFocus TP CONF_N02_002 Reference 5.3.2.4/[3] Selection expression Test purpose Participant dial-in the conference, the conference URI is not allocated, the request is rejected. ISC#1 established a conference. ISC#2 joins in that conference. The conference URI in the INVITE request is not allocated at the focus. The request is rejected with the final response 4xx. SIP header values: INVITE 2: Request URI contained the conference URI not allocated in the focus (PIXIT) Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#2 joining in the conference INVITE INVITE 2 4xx 4xx ACK ACK ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 12 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.3 Inviting other users to a conference | TSS ConferenceFocus TP CONF_N03_001 Reference 5.3.1.5.3/[3] Selection expression NOT PICS 1/6 Test purpose Inviting participant by sending REFER to the focus. ISC#1 established a conference. ISC#1 invites ISC#2 to join into the conference. The ISC#1 sends a REFER to the focus; the focus sends an INVITE request to ISC#2 to invite the ISC#2 to the conference. SIP header values: REFER: Request URI contained the conference URI Refer-To contains the URI of ISC#2, method=invite Referred-By contains SIP URI of ISC#1 INVITE 2: Request URI contained the conference URI The P-Asserted-Identity contains the conference URI. "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Referred-By contains SIP or tel URI of ISC#1 NOTIFY 1 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 2 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER REFER 202 Accepted 202 Accepted Focus dials out to invite ISC#2 INVITE 2 INVITE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 13 TSS ConferenceFocus TP CONF_N03_002 Reference 5.3.1.5.3/[3] Selection expression NOT PICS 1/6 Test purpose Inviting participant by sending REFER to the participant. ISC#1 established a conference. ISC#1 invites ISC#2 to join into the conference by sending a REFER to this participant. The participant sends an INVITE request to the focus to dial in. The conference event package is not subscribed. SIP header values: REFER: Request URI contained the URI of ISC#2 Refer-To contains the conference URI, method=invite Referred-By contains the URI of ISC#1 INVITE 2: Request URI contained the conference URI The P-Asserted-Identity contains the URI of ISC#2. "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Referred-By contains SIP or tel URI of ISC#1 NOTIFY 1 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 2 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY ISC#2 joins in the conference INVITE INVITE 2 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 14 TSS ConferenceFocus TP CONF_N03_003 Reference 5.3.1.5.4/[3] Selection expression NOT PICS 1/6 Test purpose Inviting participant by sending a participant list to the focus. ISC#1 established a conference. A participant list is contained in the INVITE to create the conference. The AS establishes a communication to the user indicated in the participant list. SIP header values: INVITE 1: Request URI=Focus <resource-lists <entry uri="sip:ISC#2 cp:capacity="to" /> INVITE 2: Request URI = ISC#2 The P-Asserted-Identity contains the conference URI. "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus ISC#2 Conference creation INVITE 1 INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK Focus dials out to invite ISC#2 INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine TSS ConferenceFocus TP CONF_N03_004 Reference 5.3.1.5.4/[3] Selection expression NOT PICS 1/6 Test purpose Inviting participant by sending a participant list to the focus in an active session. ISC#1 established a conference. A participant list is contained in the INVITE to create the conference. The AS establishes a communication to the user indicated in the participant list. SIP header values: INVITE 1: Request URI=Focus <resource-lists <entry uri="<entry uri="S1 URI?Call-ID=S1&From=S1%3Btag%3DS1&To=S1%3Btag%3DS1" cp:copyControl="to"/> INVITE 2: Request URI = ISC#2 The P-Asserted-Identity contains the conference URI. "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Comments: ISC#1 Focus ISC#2 INVITE (S1) 180 Ringing 200 OK INVITE ACK INVITE 1 (S1, sendonly) INVITE 200 OK (INVITE) 200 OK (INVITE (recvonly) ACK ACK Conference creation INVITE 1 (S2) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK Focus dials out to invite ISC#2 INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 15 TSS ConferenceFocus TP CONF_N03_005 Reference 5.3.1.3.3/[3] Selection expression Test purpose Three-way session creation. REFER is sent to the participants. Ensure that it is possible that two active sessions are able to join in a three way session and the existing sessions with the served user is terminated by the remote users. The remote users receive a REFER request and the Refer-To header contains the address of the Focus. The remote users use the URI of the Refer-To header as the Request URI of the INVITE request. SIP header values: REFER (S1): Request line=ISC#2 Refer-To=Focus; method=INVITE Referred-By=ISC#1 REFER (S2): Request line=ISC#3 Refer-To=Focus; method=INVITE Referred-By=ISC#1 INVITE (S4): Request URI=Focus Referred-By=ISC#1 INVITE (S5): Request URI=Focus Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 ISC#3 Establish session #1 Session #1 on hold Establish session #2 Session #2 on hold INVITE (S3) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER (S1) REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK (NOTIFY) 200 OK (NOTIFY) INVITE INVITE (S4) 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY (200) NOTIFY (200) 200 OK (NOTIFY) 200 OK (NOTIFY) BYE (S1) BYE (S1) 200 OK (BYE) 200 OK (BYE) REFER (S2) REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK (NOTIFY) 200 OK (NOTIFY) INVITE INVITE (S5) 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY (200) NOTIFY (200) 200 OK (NOTIFY) 200 OK (NOTIFY) BYE (S1) BYE (S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 16 TSS ConferenceFocus TP CONF_N03_006 Reference 5.3.1.3.3/[3] Selection expression Test purpose Three-way session creation. REFER is sent to the Focus. Ensure that it is possible that two active sessions are able to join in a three way session and the existing sessions with the served user is terminated by the remote users. The session the Focus is performed by the conference Focus. A new session is established by the Focus. SIP header values: REFER (S1): Request line=Focus Refer-To=ISC#2; method=INVITE Referred-By=ISC#1 REFER (S1): Request line=Focus Refer-To=ISC#3; method=INVITE Referred-By=ISC#1 INVITE (S4): Request URI=ISC#2 Referred-By=ISC#1 INVITE (S5): Request URI=ISC#3 Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 ISC#3 Establish session #1 Session #1 on hold Establish session #2 Session #2 on hold INVITE (S3) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER (S1) REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK (NOTIFY) 200 OK (NOTIFY) INVITE (S4) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY (200) NOTIFY (200) 200 OK (NOTIFY) 200 OK (NOTIFY) BYE (S1) BYE (S1) 200 OK (BYE) 200 OK (BYE) REFER (S2) REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK (NOTIFY) 200 OK (NOTIFY) INVITE (S5) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY (200) NOTIFY (200) 200 OK (NOTIFY) 200 OK (NOTIFY) BYE (S1) BYE (S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 17 TSS ConferenceFocus TP CONF_N03_007 Reference 5.3.1.3.3/[3] Selection expression Test purpose Three-way session creation. REFER is sent to the Focus. Replaces header included in the REFER. Ensure that it is possible that two active sessions are able to join in a three way session and the existing sessions with the served user is terminated by the remote users. The remote users receive a Replaces header containing the data for the particular session. The sessions are terminated after the session to the focus is active. SIP header values: REFER (S1): Request line=Focus Refer-To=ISC#2; method=INVITE?Replaces=S1;to-tag=S1;from-tag=S1 Referred-By=ISC#1 REFER (S1): Request line=Focus Refer-To=ISC#3; method=INVITE?Replaces=S2;to-tag=S2;from-tag=S2 Referred-By=ISC#1 INVITE (S4): Request URI=ISC#2 Referred-By=ISC#1 Replaces=S1;to-tag=S1;from-tag=S1 INVITE (S5): Request URI=ISC#3 Referred-By=ISC#1 Replaces=S2;to-tag=S2;from-tag=S2 Comments: ISC#1 Focus ISC#2 ISC#3 Establish session #1 Session #1 on hold Establish session #2 Session #2 on hold INVITE (S3) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER (S1) REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK (NOTIFY) 200 OK (NOTIFY) INVITE (S4) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY (200) NOTIFY (200) 200 OK (NOTIFY) 200 OK (NOTIFY) BYE (S1) BYE (S1) 200 OK (BYE) 200 OK (BYE) REFER (S2) REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK (NOTIFY) 200 OK (NOTIFY) INVITE (S5) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY (200) NOTIFY (200) 200 OK (NOTIFY) 200 OK (NOTIFY) BYE (S1) BYE (S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 18 TSS ConferenceFocus TP CONF_N03_008 Reference 5.3.1.3.3/[3] Selection expression Test purpose Three-way session creation. URI list is sent to the Focus. Ensure that a three way session can be established by sending a uri-list in the initial INVITE request send to the conference AS to create a conference. The existing sessions remains and are now connected to the MRFC. SIP header values: INVITE (S3) Request URI=Conference Factory UR) Content-Type: application/resource-lists+xml Content-Disposition: recipient-list <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:cp="urn:ietf:params:xml:ns:copyControl"> <list> <entry uri="S1 URI?Call-ID=S1&From=S1%3Btag%3DS1&To=S1%3Btag%3DS1" cp:copyControl="to"/> <entry uri="S2 URI?Call-ID=S2&From=S2%3Btag%3DS2&To=S2%3Btag%3DS2" cp:copyControl="to"/> </list> </resource-lists> INVITE (S1): SDP: MRFC INVITE (S2): SDP: MRFC Comments: ISC#1 Focus ISC#2 ISC#3 Establish session #1 Session #1 on hold Establish session #2 Session #2 on hold INVITE (S3) INVITE INVITE (S1) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (S2) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK 200 OK (INVITE) 200 OK (INVITE) ACK ACK Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 19 TSS ConferenceFocus TP CONF_N03_009 Reference 4.5.2.2.1/[3] Selection expression Test purpose Referred-By value does not contain a valid identity of the requesting user. Ensure that the value of the Referred-By header is replaced with the valid value matching the REFER request's P-Asserted-Identity if the Referred-By header does not contain a valid identity of the requesting user. SIP header values: REFER 1: Request line=Focus Refer-To=ISC#2; method=INVITE Referred-By=any value (PIXIT) P-Asserted-Identity=ISC#1 INVITE 1: Request URI=ISC#2 Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER 1 REFER 202 Accepted 202 Accepted Focus dials out to invite ISC#2 INVITE 1 INVITE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 20 TSS ConferenceFocus TP CONF_N03_010 Reference 4.5.2.2.1/[3] Selection expression Test purpose Referred-By header not present. Ensure that a Referred-By header is sent in the initial INVITE based on the REFER request and the REFER request does not contain a Referred-By header. The value of the Referred-By header matches the REFER request's P-Asserted-Identity value. SIP header values: REFER 1: Request line=Focus Refer-To=ISC#2; method=INVITE P-Asserted-Identity=ISC#1 INVITE 1: Request URI=ISC#2 Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 Conference creation INVITE 1 INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER 1 REFER 202 Accepted 202 Accepted Focus dials out to invite ISC#2 INVITE 1 INVITE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 21 TSS ConferenceFocus TP CONF_N03_011 Reference 5.3.1.5.2/[3] Selection expression Test purpose No method parameter present in the Refer-To header. Ensure that the AS invites a remote user to a conference if the method parameter is not present in the Refer-To header of the received REFER request. The conference focus assumes that the method is INVITE. SIP header values: REFER 1: Request line=Focus Refer-To=ISC#2 P-Asserted-Identity=ISC#1 Referred-By=ISC#1 INVITE 1: Request URI=ISC#2 Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 Conference creation INVITE 1 INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER 1 REFER 202 Accepted 202 Accepted Focus dials out to invite ISC#2 INVITE 1 INVITE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 22 TSS ConferenceFocus TP CONF_N03_012 Reference 5.3.2.1/[3] Selection expression Test purpose Inviting participant by sending REFER to the participant. 3pcc REFER interworking applies. The CONF AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method. Ensure that the Focus when receives the REFER request accepts the request and acts according the requirement of the Refer-To header. The Focus sends an INVITE request to the Participant to invite to the conference. SIP header values: REFER: Request URI contained the URI of ISC#2 Refer-To contains the conference URI, method=invite Referred-By contains the URI of ISC#1 INVITE 2: Request URI contained ISC#2 URI The P-Asserted-Identity = conference URI "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field Referred-By contains SIP or tel URI of ISC#1 NOTIFY 1 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 2 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER 202 Accepted NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY Focus dials out to invite ISC#2 INVITE INVITE 2 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 23 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.4 Leaving a conference | TSS ConferenceFocus TP CONF_N04_001 Reference 5.3.2.6/[3] Selection expression PICS 1/6 Test purpose A participant leaves the conference. ISC#2 wishes to leave the conference by sending a BYE request to the focus in accordance to the basic call procedures. SIP header values: REFER 1: Request line=Focus Refer-To=ISC#2 P-Asserted-Identity=ISC#1 Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER 202 Accepted Focus dials out to invite ISC#2 INVITE INVITE 2 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Conference communication Participant leaves the conference BYE 200 OK BYE Apply post test routine |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.5 Removing a conference participant from a conference | TSS ConferenceFocus TP CONF_N05_001 Reference 5.3.2.6/[3] Selection expression Test purpose A participant asks the Conference AS to remove a other participant from the conference. The conference AS verify the identity of the user and authorize the request. A participant is not authorized to remove another participant from the conference. The request fails SIP header values: REFER (S5): Request line=Focus Refer-To=ISC#2; method=BYE Referred-By=ISC#3 Comments: ISC#1 Focus ISC#2 ISC#3 ISC#1 creates a conference Invite participant ISC#2 to the conference (dial out) Invite participant ISC#3 to the conference (dial out) REFER (S5) REFER (S5) 4xx 4xx Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 24 TSS ConferenceFocus TP CONF_N05_002 Reference 5.3.2.6/[3] Selection expression PICS 1/6 Test purpose The conference owner asks the focus to remove a participant from the conference. ISC#2 asks the focus by sending a REFER request to removes another participant from the conference. In this case the focus sends a BYE request to this participant. SIP header values: REFER 1: Request URI contained the URI of conference URI Refer-To contains the ISC#2 URI, method=BYE Referred-By contains the URI of ISC#1 URI NOTIFY 1 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 2 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER 202 Accepted ISC#2 joining in the conference INVITE INVITE 2 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Conference communication ISC#1 wishes to remove ISC#2 from the conference REFER 1 REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY focus removes ISC#2 from the conference BYE 200 OK BYE NOTIFY NOTIFY 2 200 NOTIFY 200 NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 25 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.6 Conference termination | TSS ConferenceFocus TP CONF_N06_001 Reference 5.3.2.7/[3] Selection expression Test purpose The conference owner releases the entire conference by sending a BYE to the focus. SIP#1, the conference owner, sends a BYE request to the focus. The entire conference is released. SIP header values: BYE: Request URI = conference URI Comments: SIP#1 Focus SIP#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER 202 Accepted Focus dials out to invite ISC#2 INVITE INVITE 2 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Conference communication Conference creator wishes to finish the entire conference BYE BYE 200 OK BYE 200 OK BYE focus removes SIP#2 from the conference BYE 200 OK BYE Apply post test routine TSS ConferenceFocus TP CONF_N06_002 Reference 5.3.2.7/[3] Selection expression PICS 1/6 Test purpose Conference termination when the conference creator has left the conference. Ensure that the conference is terminated when the conference creator has left the conference. SIP header values: REFER 1: Request line=Focus Refer-To=ISC#2 P-Asserted-Identity=ISC#1 Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 Conference creation INVITE (S1) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER 202 Accepted Focus dials out to invite ISC#2 INVITE (S2) INVITE 2 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Conference communication Conference creator leaves the conference BYE (S1) BYE (S1) 200 OK BYE 200 OK BYE BYE (S2) BYE 200 OK BYE 200 OK BYE ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 26 TSS ConferenceFocus TP CONF_N06_003 Reference 5.3.2.7/[3] Selection expression PICS 1/6 Test purpose Conference termination when the last participant left the conference. Ensure that the conference is terminated if the last participant has left the conference. SIP header values: REFER 1: Request line=Focus Refer-To=ISC#2 P-Asserted-Identity=ISC#1 Referred-By=ISC#1 Comments: ISC#1 Focus ISC#2 Conference creation INVITE (S1) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER 202 Accepted Focus dials out to invite ISC#2 INVITE (S2) INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Conference communication Conference creator leaves the conference BYE BYE (S2) 200 OK BYE 200 OK BYE BYE (S1) BYE 200 OK BYE 200 OK BYE |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.2 Conference Notification Service | TSS ConferenceFocus TP CONF_N07_001 Reference 5.3.3/[3] Selection expression Test purpose Conference creation, notification service. Ensure that the notification procedure for the conference creation can be performed. The UE, creates the conference subscribes the notification service by sending a SUBSCRIBE. SIP header values: SUBSCRIBE: Request URI contained the conference URI Event header contains "conference" NOTIFY: Event contains conference; Subscription-State contains active; expires=xxxx Comments: ISC#1 Focus INVITE 200 OK (INVITE) ACK SUBSCRIBE 200 OK (SUBSCRIBE) NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 27 TSS ConferenceFocus TP CONF_N07_002 Reference 5.3.3/[3] Selection expression Test purpose Participants dial-in the conference, notification service. Ensure that the notification procedure for the dial-in in a conference can be performed. The UE, joins to the conference, subscribes the notification service by sending a SUBSCRIBE. SIP header values: SUBSCRIBE: Request URI contained the conference URI, Event contains "conference" Event header contains "conference" NOTIFY 1: Event contains conference; Subscription-State contains active; expires=xxxx application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISC#1 URI state="full" <endpoint entity=Endpoint ISC#1 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER REFER 200 OK (REFER) 200 OK (REFER) ISC#2 joining in the conference INVITE INVITE 2 18x 18x 200 OK INVITE 200 OK INVITE ACK ACK SUBSCRIBE 200 OK (SUBSCRIBE) NOTIFY 1 NOTIFY 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 28 TSS ConferenceFocus TP CONF_N07_003 Reference 5.3.3/[3] Selection expression Test purpose Participants dial-in the conference, notification service for conference creator. Ensure that the notification procedure for dial-in in a conference can be performed to the participant who created the conference. SIP header values: NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI, state="full", version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISC#1 URI state="full" <endpoint entity=endpoint ISC#1 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK SUBSCRIBE SUBSCRIBE 200 OK (SUBSCRIBE) 200 OK (SUBSCRIBE) NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY REFER REFER 200 OK (REFER) 200 OK (REFER) ISC#2 joining in the conference INVITE INVITE 2 18x 18x 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 29 TSS ConferenceFocus TP CONF_N07_004 Reference 5.3.3/[3] Selection expression Test purpose Focus dial-out to invite a Participant to the conference, notification service for conference creator. Ensure that the notification procedure for dial-out in a conference can be performed to the participant who created the conference. SIP header values: NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI, state="full", version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISC#1 URI state="full" <endpoint entity=endpoint ISC#1 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK SUBSCRIBE SUBSCRIBE 200 OK (SUBSCRIBE) 200 OK (SUBSCRIBE) NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER 200 OK (REFER) Focus invites ISC#2 to the conference INVITE INVITE 2 18x 18x 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 30 TSS ConferenceFocus TP CONF_N07_005 Reference 5.3.3/[3] Selection expression Test purpose Focus dial-out to invite a Participant to the conference, notification service for the participant. Ensure that the notification procedure for dial-in in a conference can be performed to the participant invited to the conference. SIP header values: NOTIFY: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI, state="full", version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISC#1 URI state="full" <endpoint entity=endpoint ISC#1 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER 200 OK (REFER) Focus invites ISC#2 to the conference INVITE INVITE 2 18x 18x 200 OK INVITE 200 OK INVITE ACK ACK SUBSCRIBE SUBSCRIBE 200 OK (SUBSCRIBE) 200 OK (SUBSCRIBE) NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 31 TSS ConferenceFocus TP CONF_N07_006 Reference 5.3.3/[3] Selection expression PICS 1/6 Test purpose A participant leaves the conference. The remaining participant is notified. A participant wishes to leave the conference by sending a BY request to the focus. Ensure that the notification procedure can be performed to the participant who created the conference. SIP header values: NOTIFY Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI, state="full", version="x" <conference-state> <user-count>1</user-count> if present <active>true</active> if present <users> <user entity=ISC#1 URI state="full" <endpoint entity=endpoint ISC#1 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#3 URI state="full" <endpoint entity=endpoint ISC#3 URI <status>disconnected</status> <joining-method>dialed-out</ joining-method> <disconnecten-type>departed</ disconnecten-type> <media id="1" <status>sendrecv</status> Comments: ISC#1 Focus ISC#2 ISC#3 ISC#1 creates a conference Invite participant ISC#2 to the conference (dial out) Invite participant ISC#3 to the conference (dial out) Participant leaves the conference BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 NOTIFY 200 NOTIFY 200 NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 32 TSS ConferenceFocus TP CONF_N07_007 Reference 5.3.3/[3] Selection expression PICS 1/6 Test purpose A participant leaves the conference. The relevant participant is notified. A participant wishes to leave the conference by sending a BY request to the focus. Ensure that the notification procedure can be performed to the relevant participant. SIP header values: NOTIFY 1 Event contains conference; Subscription-State contains terminated Comments: ISC#1 Focus ISC#2 ISC#3 ISC#1 creates a conference Invite participant ISC#2 to the conference (dial out) Invite participant ISC#3 to the conference (dial out) Participant leaves the conference BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 NOTIFY 200 NOTIFY 200 NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 33 TSS ConferenceFocus TP CONF_N07_008 Reference 5.3.3/[3] Selection expression PICS 1/6 Test purpose A participant is removed from the conference. The conference creator is notified. A participant is removed from the conference by receiving a BY request from the focus. Ensure that the notification procedure can be performed to the participant who created the conference. SIP header values: NOTIFY 2 Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI, state="full", version="x" <conference-state> <user-count>1</user-count> if present <active>true</active> if present <users> <user entity=ISC#1 URI state="full" <endpoint entity=endpoint ISC#1 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>connected</status> <joining-method>dialed-out</ joining-method> <media id="1" <status>sendrecv</status> <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>disconnected</status> <joining-method>dialed-out</ joining-method> <disconnecten-type>booted</ disconnecten-type> <media id="1" <status>sendrecv</status> Comments: ISC#1 Focus ISC#2 ISC#1 Focus ISC#2 ISC#3 ISC#1 creates a conference Invite participant ISC#2 to the conference (dial out) Invite participant ISC#3 to the conference (dial out) Participant leaves the conference BYE BYE 200 OK BYE 200 OK BYE NOTIFY NOTIFY 200 NOTIFY 200 NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 34 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.3 Actions at the UE | TSS UserEquipment TP CONF_U01_001 Reference 5.3.1/[3] Selection expression Test purpose Conference creation by Three-way session creation. REFER request to the Focus, Conference notification service is subscribed. The conference participant is participating in two SIP sessions and wants to join together two of these active sessions to a so-called three-way session. The conference notification service is subscribed. The conference participant shall perform the following steps: • Create a conference at the conference focus by sending an INVITE request with the conference factory URI for the three-way session towards the conference focus. • Perform for each of the active sessions, that are requested to be joined to the three-way session by performing the procedures for inviting a user to a conference by sending a REFER request to the Focus. • The UE releases the session 1 and 2 after the UE was informed concerned the session to the focus is established by Test Equipment S1 and Test Equipment S2. SIP header values: INVITE: Request URI contained the conference factory URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field SUBSCRIBE: Request URI contained the conference URI header contains "conference" NOTIFY 1: Event contains conference; Subscription-State contains active; expires=xxxx REFER: Refer-to header contains the conference URI NOTIFY 2 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 3 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK application/conference-info+xml contains (S1) connected, dialled-in NOTIFY 4 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 5 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK application/conference-info+xml contains (S2) connected, dialled-in Comments: User Equipment Test Equipment Create session 1 Set session 1 on hold Create session 2 Set session 2 on hold Create the conference (S3) SUBSCRIBE SUBSCRIBE 200 OK 200 OK NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER (S1) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 2 (S1, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 3 (S1, 200) 200 OK NOTIFY 200 OK NOTIFY BYE (S1) BYE 200 OK (BYE) 200 OK (BYE) REFER (S2) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 4 (S2, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 5 (S2, 200) 200 OK NOTIFY 200 OK NOTIFY BYE (S2) BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 35 TSS UserEquipment TP CONF_U01_002 Reference 5.3.1/[3] Selection expression Test purpose Conference creation by Three-way session creation. REFER request to the Focus, Conference notification service not subscribed. The conference participant is participating in two SIP sessions and wants to join together two of these active sessions to a so-called three-way session. The conference notification service is not subscribed. The conference participant shall perform the following steps: • Create a conference at the conference focus by sending an INVITE request with the conference factory URI for the three-way session towards the conference focus. • Perform for each of the active sessions, that are requested to be joined to the three-way session by performing the procedures for inviting a user to a conference by sending a REFER request to the Focus. • The ISC#1 releases the session 1 and 2 after the UE was informed concerned the session to the focus is established by Test Equipment S1 and Test Equipment S2. SIP header values: INVITE: Request URI contained the conference factory URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field REFER : Refer-to header contains the conference URI NOTIFY 1 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 2 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK NOTIFY 3 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY 4 Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: User Equipment Test Equipment Create session 1 Set session 1 on hold Create session 2 Set session 2 on hold Create the conference (S3) REFER (S1) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 (S1, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 2 (S1, 200) 200 OK NOTIFY 200 OK NOTIFY BYE (S1) BYE 200 OK (BYE) 200 OK (BYE) REFER (S2) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 3 (S2, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 4 (S2, 200) 200 OK NOTIFY 200 OK NOTIFY BYE (S2) BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 36 TSS UserEquipment TP CONF_U01_005 Reference 4.5.2.1.2/[3] Selection expression Test purpose Conference creation by Three-way session creation. REFER request to the user, Replaces method is used The conference participant is participating in two SIP sessions and wants to join together two of these active sessions to a so-called three-way session. The replaces method is used to terminate previous individual sessions. The conference participants shall perform the following steps: • Create a conference at the conference focus by sending an INVITE request with the conference factory URI for the three-way session towards the conference focus. • Perform for each of the active sessions, that are requested to be joined to the three-way session by performing the procedures for inviting a user to a conference by sending a REFER request to the user. • The Test Equipment S1 and Test Equipment S2 terminates the session 1 and 2 as indicated in the Replaces header received in the INVTE from the focus. SIP header values: INVITE: Request URI contained the conference factory URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field REFER1: Refer-to header contains the S1 URI and Replaces header for session 1 Refer-To: <sip:conference URI?Replaces=call-idS1%3Bto-tag=S1%3Bfrom-tagS1; method=INVITE> BYE 1: Call-ID: call-idS1/ To: ….; tag=S1/ From: …;tag=S1 REFER2: Refer-to header contains the S2 URI and Replaces header for session 2 Refer-To: <sip:conference URI?Replaces=call-idS2%3Bto-tagS2%3Bfrom-tagS2; method=INVITE> BYE 2: Call-ID: call-idS2/ To: ….; tag=S2/ From: …;tag=S2 Comments: User Equipment Test Equipment Create session 1 Set session 1 on hold Create session 2 Set session 2 on hold Create the conference (S3) REFER (S1) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 (S1, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 2 (S1, 200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) REFER (S2) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 3 (S2, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 4 (S2, 200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 37 TSS UserEquipment TP CONF_U01_006 Reference 4.5.2.1.2/[3] Selection expression Test purpose Conference creation by Three-way session creation. REFER request to the focus, Replaces method is used. The conference participant is participating in two SIP sessions and wants to join together two of these active sessions to a so-called three-way session. The replaces method is used to terminate previous individual sessions. The conference participants shall perform the following steps: • Create a conference at the conference focus by sending an INVITE request with the conference factory URI for the three-way session towards the conference focus. • Perform for each of the active sessions, that are requested to be joined to the three-way session by performing the procedures for inviting a user to a conference by sending a REFER request to the focus. • The Test Equipment S1 and Test Equipment S2 terminates the session 1 and 2 as indicated in the Replaces header received in the INVTE from the focus. SIP header values: INVITE: Request URI contained the conference factory URI 200 OK: "isfocus" feature parameter indicated in Contact header field conference URI contained in the Contact header field REFER 1: Refer-to header contains the URI of the Focus and Replaces header for session 1 Refer-To: <sip:S1 URI?Replaces=Call-IDS1%3Bto-tag=S1%3Bfrom-tag=S1; method=INVITE> REFER 2: Refer-to header contains the URI of the Focus and Replaces header for session 2 Refer-To: <sip:S2 URI?Replaces=Call-IDS2%3Bto-tag=S2%3Bfrom-tag=S2; method=INVITE> BYE 1: Call-ID: call-idS1/ To: ….; tag=S1/ From: …;tag=S1 BYE 2: Call-ID: call-idS2/ To: ….; tag=S2/ From: …;tag=S2 Comments: User Equipment Test Equipment Create session 1 Set session 1 on hold Create session 2 Set session 2 on hold Create the conference (S3) REFER (S1) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 (S1, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 2 (S1, 200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) REFER (S2) REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 3 (S2, 100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 4 (S2, 200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S2) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 38 TSS UserEquipment TP CONF_U01_006 Reference 4.5.2.1.2/[3] Selection expression Test purpose The User Equipment has the capability to create a conference. Ensure that the User Equipment to send an initial INVITE request and the Request URI contains a conference factory URI. SIP header values: INVITE: Request URI=conference factory URI 200 OK (INVITE): Contact: conference URI;isfocus Comments: User Equipment Test Equipment INVITE INVITE 200 OK 200 OK ACK ACK Apply post test routine TSS UserEquipment TP CONF_U01_006 Reference 4.5.2.1.2/[3] Selection expression Test purpose The User Equipment has the capability to invite a participant to the conference. REFER request to the participant. Ensure that the User Equipment is able to invite a participant to the established conference. The User Equipment sends a REFER request to the participant and the Refer-To header URI is set to the conference URI, the method parameter is set to INVITE. SIP header values: REFER: Request URI=TestEquipment (User = PIXIT) Refer-To=conference URI; method=INVITE Referred-By=User Equipment URI NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: User Equipment Test Equipment INVITE INVITE 200 OK 200 OK ACK ACK REFER REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 39 TSS UserEquipment TP CONF_U01_006 Reference 4.5.2.1.2/[3] Selection expression Test purpose The User Equipment has the capability to invite a participant to the conference. REFER request to the Focus. Ensure that the User Equipment is able to invite a participant to the established conference. The User Equipment sends a REFER request to the conference AS and the Refer-To header URI is set to the user URI, the method parameter is set to INVITE. SIP header values: REFER: Request URI=Test Equipment (Focus = PIXIT) Refer-To=Participant URI (PIXIT); method=INVITE Referred-By=User Equipment URI NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: User Equipment Test Equipment INVITE INVITE 200 OK 200 OK ACK ACK REFER REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 40 TSS UserEquipment TP CONF_U01_006 Reference 4.5.2.1.2/[3] Selection expression Test purpose The User Equipment has the capability to invite a participant to the conference. REFER request to the Focus. Replaces header is used. Ensure that the User Equipment is able to invite an active session to a conference and the User Equipment sends a Replaces header in a REFER request to the Focus to indicate that the existing session have to be replaced by the new one. SIP header values: INVITE (S1) Request URI=User Equipment (PIXIT) INVITE (S2) Request URI=Test Equipment (Conference Factory URI) REFER: Request URI=Test Equipment (Conference URI = PIXIT) Refer-To=Participant URI?Replaces: S1%3Bto-tag=S1%3Bfrom-tag=S1; method=INVITE Referred-By=User Equipment URI NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: User Equipment Test Equipment INVITE INVITE (S1) 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (S2) INVITE 200 OK 200 OK ACK ACK REFER REFER 202 Accepted 202 Accepted NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 41 TSS UserEquipment TP CONF_U01_006 Reference 5.3.2.1/[3] Selection expression Test purpose The User Equipment has the capability to invite a participant to the conference. Resource list is used. Ensure that the User Equipment is able to send a resource list to the conference AS to invite a participant to a conference. SIP header values: INVITE (S1) Request URI=User Equipment (PIXIT) INVITE (S2) Request URI=Test Equipment (Conference Factory URI) Content-Type: application/resource-lists+xml Content-Disposition: recipient-list <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:cp="urn:ietf:params:xml:ns:copyControl"> <list> <entry uri="S1 URI?Call-ID=S1&From=S1%3Btag%3DS1&To=S1%3Btag%3DS1" cp:copyControl="to"/> </list> </resource-lists> NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 100 Trying NOTIFY: Event contains conference; Subscription-State contains active message/sipfrag contains SIP/2.0 200 OK Comments: User Equipment Test Equipment INVITE INVITE (S1) 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (S2, SDP=sendonly) INVITE 200 OK 200 OK (SDP=recvonly) ACK ACK INVITE (S2) INVITE 200 OK 200 OK ACK ACK BYE (S1) BYE (S1) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 42 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.3 Interaction with other supplementary services | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.3.1 Terminating Identification Restriction (TIR) | TSS Interaction/TIR TP CONF_N08_001 Reference 4.6.3/[3] Selection expression Test purpose Privacy according TIR in the conference notification info send in the INFO request to the conference creator. Ensure the no identity is sent to the conference creator if a Privacy header was received and the privacy vale was set to "id" in the 18x or 200 OK to the INVITE to invite the participant to the conference. SIP header values: 200 OK INVITE 1: Privacy: id NOTIFY 2: Event contains conference; Subscription-State contains active application/conference-info+xml: <conference-info> entity=conference URI, state="full", version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> <user entity=ISC#1 URI state="full" <endpoint entity=endpoint ISC#1 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> [No identity information of ISC#2 or Element is not present] Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK SUBSCRIBE SUBSCRIBE 200 OK (SUBSCRIBE) 200 OK (SUBSCRIBE) NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER 200 OK (REFER) Focus invites ISC#2 to the conference INVITE INVITE 2 180 180 200 OK INVITE 200 OK INVITE 1 ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 43 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.3.2 Originating Identification Restriction (OIR) | TSS TP CONF_N09_001 Reference 4.6.5/[3] Selection expression Test purpose Conference creator subscribes to OIR: The There is no identity of the creator included in the conference notification. Ensure that the conference notification sent in the NOTIFY request after the participant was join to the conference if the conference creator has subscribed to the OIR service. SIP header values: SUBSCRIBE: Request URI contained the conference URI, Event contains "conference" Event header contains "conference" NOTIFY 1: Event contains conference; Subscription-State contains active; expires=xxxx application/conference-info+xml: <conference-info> entity=conference URI state="full" version="x" <conference-state> <user-count>2</user-count> if present <active>true</active> if present <users> [No identity information of ISC#1 or Element is not present] <user entity=ISC#2 URI state="full" <endpoint entity=endpoint ISC#2 URI <status>connected</status> <joining-method>dialed-in</ joining-method> <media id="1" <status>sendrecv</status> Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK REFER 200 OK (REFER) Focus invites ISC#2 to the conference INVITE INVITE 2 18x 18x 200 OK INVITE 200 OK INVITE ACK ACK SUBSCRIBE 200 OK (SUBSCRIBE) NOTIFY 1 NOTIFY 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 44 TSS TP CONF_N09_002 Reference 4.6.5/[3] Selection expression Test purpose Referred-By is not sent in the INVITE request if Privacy value "user" was received in the REFER. Ensure that the Referred-By received in the REFER request is not sent in the INVITE request sent to the participant to invite to the conference if the REFER request contains a Privacy header ant the value is set to "user". SIP header values: REFER 1: Referred-By=ISC#1 Privacy: user INVITE 1: Request URI=ISC#2 no Referred-By included Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER 1 REFER 202 Accepted 202 Accepted Focus dials out to invite ISC#2 INVITE 1 INVITE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine TSS TP CONF_N09_003 Reference 4.6.5/[3] Selection expression Test purpose Referred-By is removed from the INVITE request if Privacy value "user" was received in the REFER. Ensure that the Referred-By header is not sent in the INVITE request sent to the participant invited to the conference if the REFER request contains the Privacy header and the value is set to "user". SIP header values: REFER 1: Referred-By=ISC#1 Privacy: user INVITE 1: Request URI=ISC#2 no Referred-By included Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER 1 REFER 202 Accepted 202 Accepted Focus dials out to invite ISC#2 INVITE 1 INVITE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 45 TSS TP CONF_N09_004 Reference 4.6.5/[3] Selection expression Test purpose Referred-By is removed from the INVITE request if Privacy value "header" was received in the REFER. Ensure that the Referred-By header is not sent in the INVITE request sent to the participant invited to the conference if the REFER request contains the Privacy header and the value is set to "header". SIP header values: REFER 1: Referred-By=ISC#1 Privacy: header INVITE 1: Request URI=ISC#2 no Referred-By included Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER 1 REFER 202 Accepted 202 Accepted Focus dials out to invite ISC#2 INVITE 1 INVITE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine TSS TP CONF_N09_005 Reference 4.6.5/[3] Selection expression NOT PICS 1/6 Test purpose Inviting participant by sending a participant list to the focus in an active session. ISC#1 established a conference. A participant list is contained in the INVITE to create the conference. The AS establishes a communication to the user indicated in the participant list. SIP header values: INVITE 1: Request URI=Focus Privacy user <resource-lists <entry uri="<entry uri="S1 URI?Call-ID=S1&From=S1%3Btag%3DS1&To=S1%3Btag%3DS1" cp:copyControl="to"/> INVITE 2: Request URI = ISC#2 From <sip:anonymous@anonymous.invalid> Comments: ISC#1 Focus ISC#2 Establish session #1 Session #1 on hold Conference creation INVITE 1 (S2) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK Focus dials out to invite ISC#2 INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 46 5.3.3 Anonymous Communication Rejection and Communication Barring (ACR/CB) TSS TP CONF_N10_001 Reference 4.6.9/[3] Selection expression Test purpose A REFER request targeted to the participant barred by the conference creator OBC rules is rejected. Ensure that the conference AS rejects the REFER request targeted to a participant that is barred by the conference creators Outgoing Communication Barring (OCB) rules. SIP header values: REFER: Request URI contained the conference URI Refer-To contains the URI of ISC#2, method=invite Referred-By contains SIP URI of ISC#1 Comments: ISC#1 Focus ISC#2 Conference creation INVITE INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 invites ISC#2 to the conference REFER REFER 4xx 4xx Apply post test routine TSS TP CONF_N10_002 Reference 4.6.9/[3] Selection expression Test purpose The Focus removes the URI from the uri-list that is barred. Ensure that the focus AS removes the URI that is barred by the conference creator Outgoing Communication Barring (OCB) rules from the list of URIs in the "recipient-list" body of INVITE request. The recipient in the list barred by the creator's OCB rules is not invited to the conference. SIP header values: INVITE (S1) Request URI=Test Equipment (Conference Factory URI) Content-Type: application/resource-lists+xml Content-Disposition: recipient-list <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:cp="urn:ietf:params:xml:ns:copyControl"> <list> <entry uri="ISC#2" cp:copyControl="to"/> <entry uri="ISC#3" cp:copyControl="to"/> </list> </resource-lists> Comments: ISC#1 Focus ISC#2 ISC#3 INVITE (S1) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (S2) INVITE 200 OK (INVITE) 200 OK (INVITE) ACK ACK 200 OK (INVITE) 200 OK (INVITE) ACK ACK Apply post test routine ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 47 History Document history V2.1.1 July 2009 Publication |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 1 Scope | The present document specifies the Protocol implementation conformance statement (PICS) for the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. Within the Next Generation Network (NGN) the stage 3 is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), TS 183 005. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document. Within the TISPAN Next Generation Network (NGN) the stage 3 description is specified using the IP-Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. 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. |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 005 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) PSTN/ISDN simulation services: Conference (CONF) Protocol specification". [2] ETSI TS 124 147: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.147 version 8.2.0 Release 8)". |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ISO/IEC 9646-7: "Information technology; Open Systems Interconnection; Conformance testing methodology and framework; Part 7: Implementation Conformance Statements". ETSI ETSI TS 186 010-1 V2.1.1 (2009-07) 6 |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 3 Definitions and abbreviations | |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] apply. |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] apply. 4 Protocol Implementation Conformance Statement (PICS) proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended purposes and may further publish the completed PICS. |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.1 Instructions for completing the PICS proforma | 4.1.1 More detailed instructions are given at the beginning of the different subclauses of the PICS proforma. The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5. |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.1.1.1 Purposes and structure | The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in specifications [1] and [2] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into subclauses for the following categories of information: • instructions for completing the PICS proforma; • identification of the implementation; • identification of the reference protocol specification; • PICS proforma tables (containing the global statement of conformance). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.