hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2.1 General guidelines | The naming conventions are based on the following underlying principles: • In most cases, identifiers should be prefixed with a short alphabetic string (specified in table 1) indicating the type of TTCN-3 element it represents. • Suffixes should not be used except in those specific cases identified in table 2. • Prefixes and suffixes should be separated from the body of the identifier with an underscore ("_"): EXAMPLE 1: c_sixteen, t_wait_max. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 12 • Only module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. • The start of second and subsequent words in an identifier should be indicated by capitalizing the first character. Underscores should not be used for this purpose. EXAMPLE 2: f_authenticateUser. Table 1 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix, suffixes (if any) and capitalization. Table 1: TTCN-3 naming convention Language element Naming convention Prefix Suffix Example Notes Module Use upper-case initial letter DiameterGx_ none DiameterGx_Steps TSS grouping Use all upper-case letters none none TP_PCEFRole_IPS Message template Use lower-case initial letter m_ none m_authApplicationId Message template with wildcard or matching expression Use lower-case initial letters mw_ none mw_subscriptionId Port instance Use upper-case initial letter none none DiameterPort Constant Use lower-case initial letter c_ none c_maxRetransmission Function Use lower-case initial letter f_ none f_authentication() Altstep Use lower-case initial letter a_ none a_receive() Variable Use lower-case initial letter v_ none v_basicId PICS values Use all upper case letters PC_ _ none PC_PCRF_DATA_CON Note PIXIT values Use all upper case letters PX_ none PX_DIAMETER_IP_ADDR Note Parameterization Use lower-case initial letter p_ none p_macId Enumerated Value Use lower-case initial letter e_ none e_synCpk NOTE: In this case it is acceptable to use underscore as a word delimiter. |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2.2 Test case grouping | The ATS structure is based on the Test Purposes for the Diameter protocol on the Gx interface as defined in TS 101 606-2 [2]. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 13 |
f4d6a2fe2bbe984943adbb4d1a61708b | 101 606-3 | 5.2.3 Test case identifiers | The test cases have been divided according to the functionalities into several groups. The test case names are built up according to the following scheme: Table 2: TC identifier naming convention scheme Identifier: "<tc>"_"<iut >"_"<scope >"_"<number>" <tc> = Test Case: fixed to "TC" <iut> = type of IUT: PCRF or PCEF <scope> = group IPS Initial Provisioning Session MSI Modification of Session Information INV Invalid Behaviour ST Session Termination PCC PCC rules EMS Emergency services UMC Usage monitoring control IRS IMS Restoration Support MPS Multimedia Priority Support SDC Sponsored Data Connectivity RAU Reporting Accumulated Usage <number> = sequential number (01-99) NOTE: This naming scheme results into a one-to-one correspondence between the test purpose identifiers as defined in TS 101 606-2 [2] and the test case identifiers. The TP identifier of the test case TC_xxx_01 is TP_xxx_01. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 14 Annex A (normative): DIAMETER Gx Abstract Test Suite (ATS) This ATS has been produced using the Testing and Test Control Notation (TTCN-3) according to ES 201 873-1 [7]. A.1 The TTCN-3 Module The TTCN-3 library modules corresponding to the ATS are contained in archive ts10160603v010101p0.zip which accompanies the present document. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 15 Annex B (normative): DIAMETER Gx Partial PIXIT proforma for IUT PCRF 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 Partial PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed Partial PIXIT. The PIXIT Proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this international standard document. B.1 Identification summary Table B.1 PIXIT Number: Test Laboratory Name: Date of Issue: Issued to: B.2 ATS summary Table B.2 Protocol Specification: TS 129 212 [1] Protocol to be tested: ATS Specification: TS 101 606-3 Abstract Test Method: TS 101 606-3 clause 4 B.3 Test laboratory Table B.3 Test Laboratory Identification: Test Laboratory Manager: Means of Testing: SAP Address: B.4 Client identification Table B.4 Client Identification: Client Test manager: Test Facilities required: ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 16 B.5 SUT Table B.5 Name: Version: SCS Number: Machine configuration: Operating System Identification: IUT Identification: PICS Reference for IUT: Limitations of the SUT: Environmental Conditions: B.6 Protocol layer information B.6.1 Protocol identification Table B.6 Name: TS 129 212 [1] Version: PICS References: B.6.2 Configuration Tables in this clause need to be filled by the IUT Manufacturer to specify how the IUT needs to be configured with IUT specific values or describe IUT specific procedures required for complete testing of the IUT. Table B.7: PIXIT for the Gx interface Gx PIXIT Summary 1 PX_DIAMETER_GX_ETS_IPADDR charstring, IP address of the test system 2 PX_DIAMETER_GX_SUT_IPADDR charstring, IP address of the system under test 3 PX_DIAMETER_GX_ETS_PORT charstring, Port number of the test system 4 PX_DIAMETER_GX_SUT_PORT charstring, Port number of the system under test 5 PX_SessionID UTF8String, Session-Id AVP (AVP Code 263) 6 PX_Logical_Access_ID octetstring, the logical Access ID in case of xDSL IP-CAN type 7 PX_Physical_Access_ID UTF8String, the physical Access ID in case of xDSL IP-CAN type 8 PX_OriginHost charstring, the Origin-Host AVP (AVP Code 264) 9 PX_OriginRealm charstring, the Origin-Realm AVP (AVP Code 296) 10 PX_DestinationHost charstring, the Destination-Host AVP (AVP Code 293) 11 PX_DestinationRealm charstring, the Destination-Realm AVP (AVP Code 283) 12 PX_UE_framedIpAddress octetstring the Framed-IP-Address AVP (AVP Code 8) 13 PX_UE_framedIp6Address octetstring, the Framed-IPv6-Prefix AVP (AVP Code 97) 14 PX_SUBSCRIPTION_ID_TYPE enumerated type, Subscription_Id_Ty_Type, avp_Data within Subscription_Id_Type_AVP 15 PX_SUBSCRIPTION_ID_DATA UTF8String, avp_Data within Subscription_Id_AVP ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 17 Gx PIXIT Summary 16 PX_IP_CAN_TYPE enumerated type, IP_CAN_Type, avp_Data within IP_CAN_Type_AVP 17 PX_RAT_TYPE enumerated type, RAT_Type, avp_Data within RAT_Type_AVP 18 PX_APN_AGGREGATE_MAX_BITRATE_UL_AVP_DATA UInt32, avp_Data within APN_Aggregate_Max_Bitrate_UL_AVP 19 PX_3GPP_MS_TIMEZONE_DATA octetstring, avp_Data within ThreeGPP_MS_TimeZone_DATA 20 PX_CALLED_STATION_ID_DATA UTF8String, avp_Data within Called_Station_Id_AVP 21 PX_PDN_CONNECTION_ID_DATA octetstring, avp_Data within PDN_Connection_ID_AVP 22 PX_BEARER_USAGE_DATA enumerated type, Bearer_Usage, avp_Data within Bearer_Usage_AVP 23 PX_ANCA_ipv4 The ANCA (Access-Network-Charging-Address) in IPv4Addr format 24 PX_ANCA_ipv6 The ANCA (Access-Network-Charging-Address) in type IPv6Addr format 25 PX_SGW_AGW_ipv4 The SGW_AGW address (3GPP-EPS and 3GPP2 accesses) in IPv4Addr format 26 PX_SGW_AGW_ipv6 The SGW_AGW address (3GPP-EPS and 3GPP2 accesses) in IPv6Addr format 27 PX_ACCESS_NETWORK_CHARGING_IDENTIFIER_VALUE octetstring, avp_Data within Access_Network_Charging_Identifier_Value_AVP 28 PX_ROUTING_RULE_IDENTIFIER_VALUE octetstring, avp_Data within Routing_Rule_Identifier_AVP 29 PX_NETWORK_REQUEST_SUPPORT enumerated type Network_Request_Support, avp_Data within Network_Request_Support_AVP is of enumerated type Network_Request_Support 30 PX_CHARGING_RULE_NAME_DATA octetstring, avp_Data within Charging_Rule_Name_AVP 31 PX_PCC_RULE_STATUS enumerated type, PCC_Rule_Status, avp_Data within PCC_Rule_Status_AVP 32 PX_PRECEDENCE_DATA UInt32, avp_Data within Precedence_AVP 33 PX_PACKET_FILTER_IDENTIFIER_DATA octetstring, avp_Data within Packet_Filter_Identifier_AVP 34 PX_RULE_FAILURE_CODE enumerated type, PCC_Rule_Status, avp_Data within Rule_Failure_Code_AVP 35 PX_OFFLINE_DATA enumerated type, PCC_Rule_Status, avp_Data within Offline_AVP 36 PX_MPS_IDENTIFIER octectstring, avp_Data within MPS_Identifier_AVP (parameter is part of AAR message) 37 PX_ONLINE_DATA enumerated type, PCC_Rule_Status, avp_Data within Online_AVP Table B.8: PIXIT for the Rx interface Rx PIXIT Summary 1 PX_DIAMETER_RX_ETS_IPADDR charstring, IP address of the test system 2 PX_DIAMETER_RX_SUT_IPADDR charstring, IP address of the system under test 3 PX_DIAMETER_RX_ETS_PORT charstring, Port number of the test system 4 PX_DIAMETER_RX_SUT_PORT charstring, Port number of the system under test 5 PX_ANCA_ipv4 charstring, The ANCA (Access-Network-Charging-Address) in IPv4Addr format 6 PX_ANCA_ipv6 charstring, The ANCA (Access-Network-Charging-Address) in type IPv6Addr format ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 18 Annex C (normative): DIAMETER Gx Partial PIXIT proforma for IUT PCEF 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 Partial PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed Partial PIXIT. The PIXIT Proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this international standard document. C.1 Identification summary Table C.1 PIXIT Number: Test Laboratory Name: Date of Issue: Issued to: C.2 ATS summary Table C.2 Protocol Specification: TS 129 212 [1] (3GPP TS 29.212 version 10.5.0 Release 10) Protocol to be tested: ATS Specification: TS 101 606-2 [2] Abstract Test Method: TS 101 606-3, clause 4 C.3 Test laboratory Table C.3 Test Laboratory Identification: Test Laboratory Manager: Means of Testing: SAP Address: C.4 Client identification Table C.4 Client Identification: Client Test manager: Test Facilities required: ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 19 C.5 SUT Table C.5 Name: Version: SCS Number: Machine configuration: Operating System Identification: IUT Identification: PICS Reference for IUT: Limitations of the SUT: Environmental Conditions: C.6 Protocol layer information C.6.1 Protocol identification Table C.6 Name: TS 129 212 [1] (3GPP TS 29.212 version 10.5.0 Release 10) Version: PICS References: C.6.2 Configuration Tables in this clause need to be filled by the IUT Manufacturer to specify how the IUT needs to be configured with IUT specific values or describe IUT specific procedures required for complete testing of the IUT. Table C.7: PIXIT for the Gx interface Gx PIXIT Summary 1 PX_DIAMETER_GX_ETS_IPADDR charstring, IP address of the test system 2 PX_DIAMETER_GX_SUT_IPADDR charstring, IP address of the system under test 3 PX_DIAMETER_GX_ETS_PORT charstring, Port number of the test system 4 PX_DIAMETER_GX_SUT_PORT charstring, Port number of the system under test 5 PX_SessionID UTF8String, the Session-Id AVP (AVP Code 263) 6 PX_OriginHost charstring, the Origin-Host AVP (AVP Code 264) 7 PX_OriginRealm charstring, the Origin-Realm AVP (AVP Code 296) 8 PX_DestinationHost charstring, the Destination-Host AVP (AVP Code 293) 9 PX_DestinationRealm charstring, the Destination-Realm AVP (AVP Code 283) 10 PX_UE_framedIpAddress octetstring the Framed-IP-Address AVP (AVP Code 8) 11 PX_UE_framedIp6Address octetstring, the Framed-IPv6-Prefix AVP (AVP Code 97) 12 PX_BEARER_IDENTIFIER octetstring, avp_Data within Bearer_Identifier_AVP 13 PX_UNKNOWN_RATING_GROUP UInt32, avp_Data within Rating_Group_AVP 14 PX_CHARGING_RULE_NAME_DATA octetstring, avp_Data within Charging_Rule_Name_AVP 15 PX_CHARGING_RULE_NAME_DATA2 octetstring, avp_Data (2nd rule) within Charging_Rule_Name_AVP ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 20 Gx PIXIT Summary 16 PX_CHARGING_RULE_NAME_DATA3 octetstring, avp_Data (3rd rule) within Charging_Rule_Name_AVP 17 PX_CHARGING_RULE_NAME_DATA_NONEXIST octetstring, avp_Data within Charging_Rule_Name_AVP 18 PX_CHARGING_RULE_BASE_NAME_DATA octetstring, avp_Data within PX_CHARGING_RULE_BASE_NAME_DATA 19 PX_PACKET_FILTER_IDENTIFIER_DATA octetstring, avp_Data within Packet_Filter_Identifier_AVP 20 PX_MONITORING_KEY octectstring, avp_Data within MONITORING_KEY_AVP (parameter is part of RAR/CCR message) 21 PX_MONITORING_KEY2 octectstring, avp_Data within MONITORING_KEY_AVP (parameter is part of RAR/CCR message) 22 PX_REVALIDATION_TIME octectstring, avp_Data within Revalidation_Time_AVP (parameter is part of RAR message) 23 PX_ACTIVATION_TIME octectstring, avp_Data within Rule_Activation_Time_AVP (parameter is part of Charging_Rule_Install_AVP) 24 PX_DEACTIVATION_TIME octectstring, avp_Data within Rule_DeActivation_Time_AVP (parameter is part of Charging_Rule_Install_AVP) 25 PX_EMERGENCY_APN UTF8String, avp_Data within Called_Station_Id_AVP (parameter is part of Called_Station_Id_AVP) 26 PX_GTPsupport Boolean indicator, TRUE if GTP interface is accessible to triggrt Diameter events ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 21 Annex D (normative): DIAMETER Gx PCTR Proforma for IUT PCRF 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 PCTR proforma in this annex so that it can be used for its intended purposes and may further publish the completed PCTR. The PCTR proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this International standard document. D.1 Identification summary D.1.1 Protocol conformance test report Table D.1 PCTR Number: PCTR Date: Corresponding SCTR Number: Corresponding SCTR Date: Test Laboratory Identification: Test Laboratory Manager: Signature: D.1.2 IUT identification Table D.2 Name: Version: Protocol specification: PICS: Previous PCTR if any: D.1.3 Testing environment Table D.3 PIXIT Number: ATS Specification: TS 101 606-3 Abstract Test Method: TS 101 606-3, clause 4 Means of Testing identification: Date of testing: Conformance Log reference(s): Retention Date for Log reference(s): ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 22 D.1.4 Limits and reservation Additional information relevant to the technical contents or further use of the test report, or the rights and obligations of the test laboratory and the client, may be given here. Such information may include restriction on the publication of the report. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... D.1.5 Comments Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for example, to note disagreement between the two parties. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... D.2 IUT Conformance status This IUT has or has not been shown by conformance assessment to be non-conforming to the specified protocol specification. Strike the appropriate words in this sentence. If the PICS for this IUT is consistent with the static conformance requirements (as specified in clause C.3 in the present document) and there are no "FAIL" verdicts to be recorded (in clause C.6 in the present document) strike the words "has or", otherwise strike the words "or has not". D.3 Static conformance summary The PICS for this IUT is or is not consistent with the static conformance requirements in the specified protocol. Strike the appropriate words in this sentence. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 23 D.4 Dynamic conformance summary The test campaign did or did not reveal errors in the IUT. Strike the appropriate words in this sentence. If there are no "FAIL" verdicts to be recorded (in clause C.6 of the present document) strike the words "did or" otherwise strike the words "or did not". Summary of the results of groups of test: ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... D.5 Static conformance review report If clause C.3 indicates non-conformance, this clause itemises the mismatches between the PICS and the static conformance requirements of the specified protocol specification. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 24 D.6 Test campaign report Table D.4: PCRF test cases ATS Reference Selected? Run? Verdict Observations (Reference to any observations made in clause D.7) TC_PCRF_IPS_01 Yes/No Yes/No TC_PCRF_IPS_02 Yes/No Yes/No TC_PCRF_IPS_03 Yes/No Yes/No TC_PCRF_IPS_04 Yes/No Yes/No TC_PCRF_IPS_05 Yes/No Yes/No TC_PCRF_IPS_06 Yes/No Yes/No TC_PCRF_MSI_01 Yes/No Yes/No TC_PCRF_MSI_02 Yes/No Yes/No TC_PCRF_MSI_03 Yes/No Yes/No TC_PCRF_MSI_04 Yes/No Yes/No TC_PCRF_MSI_05 Yes/No Yes/No TC_PCRF_MSI_06 Yes/No Yes/No TC_PCRF_INV_01 Yes/No Yes/No TC_PCRF_INV_02 Yes/No Yes/No TC_PCRF_ST_01 Yes/No Yes/No TC_PCRF_ST_02 Yes/No Yes/No TC_PCRF_ST_03 Yes/No Yes/No TC_PCRF_PCC_01 Yes/No Yes/No TC_PCRF_PCC_02 Yes/No Yes/No TC_PCRF_PCC_03 Yes/No Yes/No TC_PCRF_PCC_04 Yes/No Yes/No TC_PCRF_PCC_05 Yes/No Yes/No TC_PCRF_PCC_06 Yes/No Yes/No TC_PCRF_PCC_07 Yes/No Yes/No TC_PCRF_PCC_08 Yes/No Yes/No TC_PCRF_PCC_09 Yes/No Yes/No TC_PCRF_EMS_01 Yes/No Yes/No TC_PCRF_UMC_01 Yes/No Yes/No TC_PCRF_IRS_01 Yes/No Yes/No TC_PCRF_IRS_02 Yes/No Yes/No TC_PCRF_MPS_01 Yes/No Yes/No TC_PCRF_MPS_02 Yes/No Yes/No TC_PCRF_SDC_01 Yes/No Yes/No TC_PCRF_SDC_02 Yes/No Yes/No D.7 Observations Additional information relevant to the technical content of the PCTR is given here. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 25 Annex E (normative): DIAMETER Gx PCTR Proforma for IUT PCEF 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 PCTR proforma in this annex so that it can be used for its intended purposes and may further publish the completed PCTR. The PCTR proforma is based on ISO/IEC 9646-6 [4]. Any additional information which may be needed can be found in this International standard document. E.1 Identification summary E.1.1 Protocol conformance test report Table E.1 PCTR Number: PCTR Date: Corresponding SCTR Number: Corresponding SCTR Date: Test Laboratory Identification: Test Laboratory Manager: Signature: E.1.2 IUT identification Table E.2 Name: Version: Protocol specification: PICS: Previous PCTR if any: E.1.3 Testing environment Table E.3 PIXIT Number: ATS Specification: TS 101 606-3 Abstract Test Method: TS 101 606-3, clause 4 Means of Testing identification: Date of testing: Conformance Log reference(s): Retention Date for Log reference(s): ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 26 E.1.4 Limits and reservation Additional information relevant to the technical contents or further use of the test report, or the rights and obligations of the test laboratory and the client, may be given here. Such information may include restriction on the publication of the report. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... E.1.5 Comments Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for example, to note disagreement between the two parties. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... E.2 IUT Conformance status This IUT has or has not been shown by conformance assessment to be non-conforming to the specified protocol specification. Strike the appropriate words in this sentence. If the PICS for this IUT is consistent with the static conformance requirements (as specified in clause C.3 in the present document) and there are no "FAIL" verdicts to be recorded (in clause C.6 in the present document) strike the words "has or", otherwise strike the words "or has not". E.3 Static conformance summary The PICS for this IUT is or is not consistent with the static conformance requirements in the specified protocol. Strike the appropriate words in this sentence. ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 27 E.4 Dynamic conformance summary The test campaign did or did not reveal errors in the IUT. Strike the appropriate words in this sentence. If there are no "FAIL" verdicts to be recorded (in clause C.6 of the present document) strike the words "did or" otherwise strike the words "or did not". Summary of the results of groups of test: ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... E.5 Static conformance review report If clause C.3 indicates non-conformance, this clause itemises the mismatches between the PICS and the static conformance requirements of the specified protocol specification. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 28 E.6 Test campaign report Table E.4: PCEF test cases ATS Reference Selected? Run? Verdict Observations (Reference to any observations made in clause D.7) TC_PCEF_IPS_01 Yes/No Yes/No TC_PCEF_IPS_02 Yes/No Yes/No TC_PCEF_IPS_03 Yes/No Yes/No TC_PCEF_IPS_04 Yes/No Yes/No TC_PCEF_IPS_05 Yes/No Yes/No TC_PCEF_IPS_06 Yes/No Yes/No TC_PCEF_MSI_01 Yes/No Yes/No TC_PCEF_MSI_02 Yes/No Yes/No TC_PCEF_MSI_03 Yes/No Yes/No TC_PCEF_MSI_04 Yes/No Yes/No TC_PCEF_MSI_05 Yes/No Yes/No TC_PCEF_ST_01 Yes/No Yes/No TC_PCEF_ST_02 Yes/No Yes/No TC_PCEF_PCC_01 Yes/No Yes/No TC_PCEF_PCC_02 Yes/No Yes/No TC_PCEF_PCC_03 Yes/No Yes/No TC_PCEF_PCC_04 Yes/No Yes/No TC_PCEF_PCC_05 Yes/No Yes/No TC_PCEF_PCC_06 Yes/No Yes/No TC_PCEF_PCC_07 Yes/No Yes/No TC_PCEF_PCC_08 Yes/No Yes/No TC_PCEF_PCC_09 Yes/No Yes/No TC_PCEF_PCC_10 Yes/No Yes/No TC_PCEF_PCC_11 Yes/No Yes/No TC_PCEF_PCC_12 Yes/No Yes/No TC_PCEF_PCC_13 Yes/No Yes/No TC_PCEF_PCC_14 Yes/No Yes/No TC_PCEF_PCC_15 Yes/No Yes/No TC_PCEF_PCC_16 Yes/No Yes/No TC_PCEF_PCC_17 Yes/No Yes/No TC_PCEF_PCC_18 Yes/No Yes/No TC_PCEF_PCC_19 Yes/No Yes/No TC_PCEF_PCC_20 Yes/No Yes/No TC_PCEF_EMS_01 Yes/No Yes/No TC_PCEF_EMS_02 Yes/No Yes/No TC_PCEF_UMC_01 Yes/No Yes/No TC_PCEF_RAU_01 Yes/No Yes/No TC_PCEF_RAU_02 Yes/No Yes/No TC_PCEF_RAU_03 Yes/No Yes/No TC_PCEF_RAU_04 Yes/No Yes/No TC_PCEF_RAU_05 Yes/No Yes/No TC_PCEF_RAU_06 Yes/No Yes/No TC_PCEF_RAU_07 Yes/No Yes/No TC_PCEF_IRS_01 Yes/No Yes/No TC_PCEF_IRS_02 Yes/No Yes/No ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 29 E.7 Observations Additional information relevant to the technical content of the PCTR is given here. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 101 606-3 V1.1.1 (2012-09) 30 History Document history V1.1.1 September 2012 Publication |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 1 Scope | The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the test specifications for the Diameter protocol on the Gx interface as specified in TS 129 212 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5]. |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 212: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx/Sd reference point (3GPP TS 29.212 version 10.5.0 Release 10)". [2] ETSI TS 101 606-1: "IMS Network Testing (INT); Diameter Conformance testing for Gx interface; Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [5] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [6] IETF RFC 3588: "Diameter Base Protocol". [7] ETSI TS 129 213: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping (3GPP TS 29.213 version 10.3.0 Release 10)". [8] ETSI TS 129 214: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 10.5.0 Release 10)". |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 6 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 3 Definitions and abbreviations | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 129 212 [1] and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [3]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [3]. |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 129 212 [1] and the following apply: TP Test Purpose TSS Test Suite Structure |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 4 Test configurations | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5 Test Suite Structure (TSS) and Test Purposes (TP) | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.1 Test Suite Structure | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 7 Table 1: TP identifier naming convention scheme Identifier: <TP>_<iut>_<scope>_<nn> <tp> = Test Purpose: fixed to "TP" <iut> = type of IUT: PCRF or PCEF <scope> = group IPS Initial Provisioning Session MSI Modification of Session Information INV Invalid Behaviour ST Session Termination PCC PCC rules EMS Emergency services UMC Usage monitoring control IRS IMS Restoration Support MPS Multimedia Priority Support SDC Sponsored Data Connectivity RAU Reporting Accumulated Usage <nn> = sequential number (01 to 99) |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.1.2 Test strategy | As the base standard TS 129 212 [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 101 606-1 [2]. |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.1.3 TP structure | Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs more readable and checkable. A particular structure has been used which is illustrated in table 2. This table should be read in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 8 Table 2: Structure of a single TP TP part Text Example Header <Identifier> see table 1 <clause number in base TS 129 212 [1] > clause 4.4.1 <PICS reference> A.2/3 Summary Short free text description of the test objective Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to IP-CAN session establishment. Initial condition (optional) Free text description of the condition that the IUT has reached before the test purpose applies. The IUT has received AF provisions information about the AF signalling flows between UE and AF. Start point Ensure that the IUT in the <state> see RFC 3588 [6] clause 5.6 Open state and/or further actions before stimulus if the action is sending/receiving see below for message structure having sent an AA-Request Stimulus <trigger>, see below for message structure on receipt of a Capabilities-Exchange- Request (see note 2) or <goal> to require PCC supervision ... Reaction <action>. sends, saves, does, etc. if the action is sending see below for message structure <next action>, etc. Message structure <message type> Capabilities-Exchange-Answer, etc. (see note 2) a) containing a(n) <avp name> AVP b) indicating <coding of the field> and back to a) or b) (see note 3) Vendor-Id, etc. NOTE 1: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one TP to the next. NOTE 2: All messages shall be considered as "valid and compatible" unless otherwise specified in the test purpose. This includes the presence of all mandatory AVPs as specified in RFC 3588 [6] and in TS 129 212 [1], clause 5. NOTE 3: An AVP can be embedded into another AVP. This is expressed by indentations, e.g. if Message1 contains AVP1 and AVP2 where AVP1 has AVP3 embedded this will be expressed like this: sends/receives Message 1 containing AVP1 containing AVP3 indicating ... containing AVP2 indicating ... |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2 Test Purposes | All PICS items referred to in this clause are as specified in TS 101 606-1 [2] unless indicated otherwise by another numbered reference. PICS items are only meant for test selection, therefore only PICS items with status optional or conditional are explicitly mentioned. Call flow information for described test purposes is specified in TS 129 213 [7]. |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1 PCRF Role | Test Selection: IUT takes the role of the PCRF; PICS A.2.1 ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 9 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.1 Session request | TP_PCRF_IPS_01 Standards Reference: 4.5.1 (item 1), 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to IP-CAN session establishment. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing the user identification containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP indicating the full IP address of the UE, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6- Address-Prefix AVP. TP_PCRF_IPS_02 Standards Reference: 4.5.1 ¶1, 4.3a.4.1 ¶3, 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory and optional AVPs in a CC-Request received due to IP-CAN session establishment. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing the user identification containing an IPCAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP containing the Framed-IP-Address containing a Called-Station-ID AVP containing the PDN information containing a PDN Connection-ID AVP containing the PDN connection identifier containing a 3GPP-MS-TimeZone AVP containing the UE time zone information containing an Access-Network-Charging-Identifier-Gx AVPs containing the Access-Network-Charging-Address containing a Network-Request-Support AVP containing an indicator for support of network-initiated bearer request procedures containing a QoS-Information AVP containing an APN-Aggregate-Max-Bitrate-DL/UL AVPs containing the APN-AMBR containing a Bearer-Usage AVP containing an indicator for default bearer request containing a Routing-Rule-Install AVP containing one or more Routing-Rule-Definition AVPs containing Routing-Filter AVP, sends a CC-Answer containing PCC rules. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6-Address- Prefix AVP. The Routing-Rule-Install AVP is configured as for installation of IP flow mobility routing rule. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 10 TP_PCRF_IPS_03 Standards Reference: 4.5.10 ¶2 and 3 PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to an IP-CAN session establishment with bearer control mode selection. Test purpose: Ensure that the IUT, on receipt of a CC-Request containing all mandatory AVPs and containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Network-Request-Support AVP, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS containing a Bearer-Control-Mode AVP. Comments: TP_PCRF_IPS_04 Standards Reference: 4.5.1 (item 1, 2nd paragraph) PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to an IP-CAN session establishment that supports multiple IP-CAN bearers. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Default_EPS_Bearer_QoS AVP containing the QoS_Class_Identifier AVP containing the Allocation_Retention_Priority AVP sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: Usage of Default_EPS_Bearer_QoS_AVP is optional. TP_PCRF_IPS_05 Standards Reference: 4.5.1 (item 1, 3rd paragraph) PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to 3GPP-EPS and 3GPP2 accesses. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a AN-GW-Address AVP containing the IPv4 or IPv6 addresses of SGW/AGW sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: TP_PCRF_IPS_06 Standards Reference: 4.5.1 (item 1, 4th paragraph) PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to xDSL IP-CAN Type. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing a Logical-Access-ID AVP containing a Physical-Access-ID AVP sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 11 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.2 Session modification | TP_PCRF_MSI_01 Standards Reference: 4.5.1 ¶2, 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to IP-CAN session modification. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing previously provisioned PCC rule(s) and their status containing an Event-Trigger AVP containing the reason for the IP-CAN session modification, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS. Comments: TP_PCRF_MSI_02 Standards Reference: 4.5.1 ¶2, 4.3a.4.1 ¶3, 4.5.2(1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory and optional AVPs in a CC-Request received due to IP-CAN session modification. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing an Access-Network-Charging-Address AVP containing an Access-Network-Charging-Identifier-Gx AVP containing a Charging-Rule-Report AVP containing previously provisioned PCC rule(s) and their status containing an Event-Trigger AVP containing the reason for the IP-CAN session modification containing a Routing-Rule-Install AVP containing one or more Routing-Rule-Definition AVPs containing a Routing-Filter AVP, sends a CC-Answer containing PCC rules. Comments: The Routing-Rule-Install AVP is configured as for installation of IP flow mobility routing rule. TP_PCRF_MSI_03 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 1st dash), 4.5.2 1st dashed list (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due a UE request for allocation of new resources. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing an Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating ADDITION containing a Packet-Filter-Information AVPs containing a Precedence AVP containing a Packet-Filter-Content AVP containing a QoS-Information AVP, sends a CC-Answer containing PCC rules. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 12 TP_PCRF_MSI_04 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 2nd dash), 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due a UE request for modification of existing resources. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing an Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating MODIFICATION containing a Packet-Filter-Information AVPs containing a Packet-Filter-Identifier AVP containing a packet filter identifier, sends a CC-Answer containing PCC rules. Comments: TP_PCRF_MSI_05 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 3rd dash), 4.5.2 (1st dash) PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due a UE request for deletion of resources. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating DELETION containing a Packet-Filter-Information AVPs containing a Packet-Filter-Identifier AVP, sends a CC-Answer containing PCC rules. Comments: TP_PCRF_MSI_06 Standards Reference: 4.5.10 ¶2 and 3 PICS item: Summary: Verify that the IUT can successfully process a CC-Request received due to IP-CAN session modification with bearer control mode selection. Test purpose: Ensure that the IUT, when an IP-CAN session is already established, on receipt of a CC-Request containing all mandatory AVPs and containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Network-Request-Support AVP, sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS containing a Bearer-Control-Mode AVP. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 13 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.3 Invalid behaviour | TP_PCRF_INV_01 Standards Reference: 4.5.1 (last paragraph in clause), 4.5.12 ¶1 PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to the failure of installation/activation of PCC rules. Test purpose: Ensure that the IUT on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing ( a Charging-Rule-Name AVP indicating failed PCC rule or a Charging-Rule-Base-Name AVP indicating failed PCC rule ) containing a PCC-Rule-Status AVP containing a Rule-Failure-Code AVP, sends a CC-Answer containing an Experimental-Result AVP indicating DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED. Comments: TP_PCRF_INV_02 Standards Reference: 4.5.1, 4.5.15.2.1 ¶2 and 3 PICS item: Summary: Verify that the IUT can reject a request for PCC rules for an emergency service. Test purpose: Ensure that the IUT, on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP indicating the full IP address of the UE containing a Called-Station-Id AVP indicating the Emergency APN containing a Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Subscription-Id AVP indicating IMSI, sends a CC-Answer containing an Experimental-Result AVP indicating DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6- Address-Prefix AVP. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 14 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.4 Session Termination | TP_PCRF_ST_01 Standards Reference: 4.5.6 ¶3 PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to the termination of an IP-CAN bearer. Test purpose: Ensure that the IUT, when an IP-CAN session is established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing a Rule-Status AVP indicating INACTIVE containing a Rule-Failure-Code AVP indicating RESOURCE_ALOCATION_FAILURE, sends a CC-Answer Comments: TP_PCRF_ST_02 Standards Reference: 4.5.7 ¶4 PICS item: Summary: Verify that the IUT can successfully process all mandatory AVPs in a CC-Request received due to the termination of an IP-CAN session. Test purpose: Ensure that the IUT, when an IP-CAN session is established, on receipt of a CC-Request containing a CC-Request-Type AVP indicating TERMINATION_REQUEST, sends a CC-Answer Comments: TP_PCRF_ST_03 Standards Reference: 4.5.9, [7] 4.2.3.1 PICS item: A.3.9 Summary: Verify that the IUT can terminate an IP-CAN session with an RA-Request and process the subsequent RA-Answer and CC-Request messages. Test purpose: Ensure that the IUT, when an IP-CAN session is established, to terminate an IP CAN session due to an internal or SPR trigger, sends an RA-Request containing a Session-Release-Cause AVP on receipt of a RA-Answer and on receipt of a CC-Request containing a CC-Request-Type AVP indicating TERMINATION_REQUEST, sends a CC-Answer Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.5 PCC rules | TP_PCRF_PCC_01 Standards Reference: 4.5.2 (2nd dashed list 1st dash) PICS item: A.3.3.2 Summary: Verify that the IUT can activate PCC rules with an RA-Request using the PUSH procedure. Test purpose: Ensure that the IUT, to activate a PCC rule, sends a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Name AVP providing a reference to a PCC rule. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 15 TP_PCRF_PCC_02 Standards Reference: 4.5.2 (2nd dashed list 1st dash) PICS item: A.3.3.2 Summary: Verify that the IUT can deactivate PCC rules with an RA-Request using the PUSH procedure. Test purpose: Ensure that the IUT, to deactivate a PCC rule, sends a RA-Request containing a Charging-Rule-Remove AVP containing a Charging-Rule-Name AVP providing a reference to a PCC rule. Comments: TP_PCRF_PCC_03 Standards Reference: 4.5.2 ¶6 PICS item: A.3.3.2 Summary: Verify that the IUT can activate a group of PCC rules with an RA-Request using the PUSH procedure. Test purpose: Ensure that the IUT, to activate a group of PCC rules, sends a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Base-Name AVP providing a reference to a PCC rules. Comments: TP_PCRF_PCC_04 Standards Reference: 4.5.2 (after note 1) PICS item: A.3.3.2, A.3.3.3 Summary: Verify that the IUT can request confirmation of successful resource allocation for a PCC rule with an RA-Request using the PUSH procedure. Test purpose: Ensure that the IUT, to request confirmation that the resources associated to a PCC rule are successfully allocated, sends a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Name AVP providing a reference to a PCC rule containing a Resource-Allocation-Notification AVP indicating ENABLE_NOTIFICATION containing a Event-Trigger AVP indicating SUCCESSFUL_RESOURCE_ALOCATION. Comments: TP_PCRF_PCC_05 Standards Reference: 4.5.2 (2nd dashed list 2nd dash) PICS item: A.3.3.2 Summary: Verify that the IUT can modify a PCC rule with an RA-Request using the PUSH procedure. Test purpose: Ensure that the IUT, to modify a PCC rule, sends a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP. Comments: TP_PCRF_PCC_06 Standards Reference: 4.5.2 (2nd dashed list 3rd dash) PICS item: A.3.3.2 Summary: Verify that the IUT can remove a PCC rule with an RA-Request using the PUSH procedure. Test purpose: Ensure that the IUT, to remove a PCC rule, sends a RA-Request containing a Charging-Rule-Remove AVP containing a Charging-Rule-Name AVP. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 16 TP_PCRF_PCC_07 Standards Reference: 4.5.2 ¶14 PICS item: A.3.3.2 Summary: Verify that the IUT can remove a group of PCC rules with an RA-Request using the PUSH procedure. Test purpose: Ensure that the IUT, to remove a group of PCC rules, sends a RA-Request containing a Charging-Rule-Remove AVP containing a Charging-Rule-Base-Name AVP. Comments: TP_PCRF_PCC_08 Standards Reference: 4.5.4.2 ¶2 and 3 PICS item: A.3.5.2 Summary: Verify that the IUT does not reject CC-Request and IUT can provide a default charging method with a CC-Answer. Test purpose: Ensure that the IUT, to provide a default charging method, on receipt of a CC-Request containing an Online AVP containing an Offline AVP sends a CC-Answer ( containing an Online AVP or containing an Offline AVP. ) Comments: TP_PCRF_PCC_09 Standards Reference: 4.5.5.0 (2nd dash), 4.5.5.2 PICS item: A.3.3.2. A3.5 Summary: Verify that the IUT can provide authorized Qos to a PCC rule with an RA-Request. Test purpose: Ensure that the IUT, to provide authorized QoS to a PCC rule, sends a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a QoS-Information AVP not containing a Bearer-Identifier AVP. Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.6 Special services and features | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.6.1 Emergency services | TP_PCRF EMS_01 Standards Reference: 4.5.15.2.2.2 ¶1 and 2 PICS item: Summary: Verify that the IUT can provide PCC rules for emergency services with an RA-Request. Test purpose: Ensure that the IUT on receipt of IMS service information from the AF for an emergency service via the Rx interface, sends a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a QoS-Information AVP containing an Allocation-Retention-Priority AVP containing a Priority-Level AVP. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 17 TP_PCRF_EMS_02 Standards Reference: 4.5.15.2.2 ¶2, 5.3.23 PICS item: Summary: Verify that the IUT can detect that a Gx session is restricted to IMS Emergency services when a CCR command is received with a CC-Request-Type AVP set to value "INITIAL_REQUEST" and the Called-Station-Id AVP includes a PDN identifier that matches one of the Emergency APNs from the configurable list. Initial Condition: The IUT is configured with Emergency_APN_A included in the PDN identifier configurable list. Test purpose: Ensure that the IUT to detect a Gx session restricted to IMS Emergency services, on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Called-Station-Id AVP indicating an Emergency APN_A sends a CC-Answer containing a Result-Code AVP indicating DIAMETER_SUCCESS containing a Bearer-Control-Mode AVP. indicating NW_mode. Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.6.2 Usage monitoring control | TP_PCRF_UMC_01 Standards Reference: 4.5.16¶2,6 PICS item: A.3.15 Summary: Verify that the IUT can request usage monitoring control. Test purpose: Ensure that the IUT, to request usage monitoring control, on receipt of a CC-Request, sends a CC-Answer containing an Event-Trigger AVP indicating USAGE_REPORT containing a Usage-Monitoring-Information AVP containing a Granted-Service-Unit AVP containing ( a CC-Total-Octets AVP or a CC-Input-Octets AVP or a CC-Output-Octets AVP ) containing a Monitoring-Key AVP containing a monitoring key. Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.6.3 IMS restoration procedures | TP_PCRF_IRS_01 Standards Reference: 4.5.18 ¶1 PICS item: A.3.17 Summary: Verify that the IUT can install dynamic PCC rules with an RA-Request. Initial Condition: The IUT has received AF provisions information about the AF signalling flows between UE and AF. Test purpose: Ensure that the IUT, to install dynamic PCC rules, sends a RA-Request containing Charging-Rule-Install AVP containing the Charging-Rule-Definition AVP containing Flow-Information AVP indicating the signalling flows between UE and AF containing AF-Signalling-Protocol AVP indicating the signalling protocol between UE and AF. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 18 TP_PCRF_IRS_02 Standards Reference: 4.5.18 ¶3 PICS item: A.3.17 Summary: Verify that the IUT can remove dynamic PCC rules with an RA-Request. Initial Condition: The IUT has received AF de-provisions information about the AF signalling flows between UE and AF. Test purpose: Ensure that the IUT, to remove dynamic PCC rules, sends a RA-Request containing Charging-Rule-Remove AVP containing the Charging-Rule-Name AVP. Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.6.4 Multimedia Priority support | TP_PCRF_MPS_01 Standards Reference: 4.5.19.1.1 ¶4 PICS item: Summary: Verify that the IUT can provide PCC rules for multimedia priority services. Initial Condition: The IUT has received AF provisioning information about the AF signalling flows between UE and AF including priority parameters to be stored in SPR (TS 129 214 [8], clause A.9). Test purpose: Ensure that the IUT, on receipt of a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST sends a CC-Answer containing a QoS-Information AVP containing a QoS-Class-Identifier AVP containing an Allocation-Retention-Priority AVP. Comments: Priority parameters that are considered are MPS EPS Priority, MPS Priority Level and IMS Signalling Priority. TP_PCRF MPS_02 Standards Reference: 4.5.19.1.1 ¶5 PICS item: Summary: Verify that the IUT can provide modified PCC rules for multimedia priority services in with an RA-Request. Test purpose: Ensure that the IUT, on receipt of a notification of a change of priority from the SPR, sends a RA-Request containing a QoS-Information AVP containing a QoS-Class-Identifier AVP containing an Allocation-Retention-Priority AVP. Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.1.6.5 Sponsored Data Connectivity | TP_PCRF SDC_01 Standards Reference: 4.5.20 ¶2 PICS item: A.3.1 Summary: Verify that the IUT can provide sponsored data connectivity for PCC rules using the PUSH method. Initial Condition: The IUT has received information about the sponsor of the sponsored data connectivity from the AF. Test purpose: Ensure that the IUT, to provide sponsored data connectivity to PCC rules, sends a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Sponsor-Identity AVP containing a Application-Service-Provider-Identity AVP containing a Reporting_Level AVP indicating SPONSORED_CONNECTIVITY_LEVEL. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 19 TP_PCRF_SDC_02 Standards Reference: 4.5.20 ¶2 PICS item: A.3.1 Summary: Verify that the IUT can provide sponsored data connectivity for PCC rules using the PULL method. Initial Condition: The IUT has received information about the sponsor of the sponsored data connectivity from the AF. Test purpose: Ensure that the IUT, on receipt of a CC-Request, sends a CC-Answer containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Sponsor-Identity AVP containing a Application-Service-Provider-Identity AVP containing a Reporting_Level AVP indicating SPONSORED_CONNECTIVITY_LEVEL. Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2 PCEF Role | Test Selection: IUT takes the role of the PCEF; PICS A.2.2 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.1 Session request | TP_PCEF_IPS_01 Standards Reference: 4.5.1 (item 1) PICS item: Summary: Verify that the IUT can indicate requests for PCC rules at IP-CAN session establishment with a CC-Request. Test purpose: Ensure that the IUT to indicate a request for PCC rules at IP-CAN session establishment, sends a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing the user identification containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP indicating the full IP address of the UE. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6- Address-Prefix AVP. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 20 TP_PCEF_IPS_02 Standards Reference: 4.5.1 (item 1), 4.3a.4.1 ¶3 PICS item: A4.3 Summary: Verify that the IUT can indicate requests for PCC rules and install IP flow mobility routing rules at IP-CAN session establishment with a CC-Request. Test purpose: Ensure that the IUT to indicate a request for PCC rules at IP-CAN session establishment and to install IP flow mobility routing rules, sends a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing a Subscription-Id AVP containing the user identification containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP indicating the full IP address of the UE containing a Routing-Rule-Install AVP containing one or more Routing-Rule-Definition AVPs containing Routing-Filter AVP. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6- Address-Prefix AVP. TP_PCEF_IPS_03 Standards Reference: 4.5.1 PICS item: Summary: Verify that the IUT can reject an IP-CAN session when receiving error from PCRF. Initial Condition: IP-CAN session establishment is outstanding. The IUT has send a CC-Request to the PCRF. The PCRF is not able to provision a policy decision. Test purpose: Ensure that the IUT, on receipt of a CC-Answer containing an Experimental-Result AVP containing an Experimental-Result_Code AVP indicating DIAMETER_ERROR_INITIAL_PARAMETERS, rejects the IP-CAN session establishment or modification. Comments: TP_PCEF_IPS_04 Standards Reference: 4.5.1 PICS item: Summary: Verify that the IUT can reject an IP-CAN session when receiving error from PCRF. Initial Condition: IP-CAN session establishment is outstanding. The IUT has send a CC-Request to the PCRF. The new PCC rule is covered by the packet filters of outstanding PCC rules that the PCRF is provisioning. Test purpose: Ensure that the IUT, on receipt of a CC-Answer containing an Experimental-Result AVP containing an Experimental-Result_Code AVP indicating DIAMETER_ERROR_CONFLICTING_REQUEST, rejects the IP-CAN session establishment or modification. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 21 TP_PCEF_IPS_05 Standards Reference: 4.5.1 PICS item: Summary: Verify that the IUT can reject an IP-CAN session when receiving error from PCRF. Initial Condition: IP-CAN session establishment is outstanding. The IUT has send a CC-Request to the PCRF. The PCRF does not accept one or more of the traffic mapping filters. Test purpose: Ensure that the IUT, on receipt of a CC-Answer containing an Experimental-Result AVP containing an Experimental-Result_Code AVP indicating DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED, rejects the IP-CAN session establishment or modification. Comments: TP_PCEF_IPS_06 Standards Reference: 4.5.4.2, 3rd paragraph PICS item: Summary: Verify that the IUT can successfully process all Online_AVP and Offline_AVP in a CC-Answer from PCRF. Initial Condition: IP-CAN session establishment is outstanding. The IUT has send a CC-Request to the PCRF. IUT has pre-configured Default charging method. Test purpose: Ensure that the IUT, on receipt of a CC-Answer containing an Online_AVP containing an Offline_AVP, accepts the message and overwrites use of any pre-configured Default charging method. Comments: NOTE: Verification of the result needs further study. |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.2 Session modification | TP_PCEF_MSI_01 Standards Reference: 4.5.1 (item 2) PICS item: Summary: Verify that the IUT can indicate requests for PCC rules at IP-CAN session modification with a CC-Request. Test purpose: Ensure that the IUT, when an IP-CAN session is established, to indicate a request for PCC rules at IP-CAN session modification, sends a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing PCC rule(s) and their status containing a Event-Trigger AVP containing IP-CAN session modification. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 22 TP_PCEF_MSI_02 Standards Reference: 4.5.1 (item 2), 4.3a.4.1 ¶3 PICS item: A.4.3 Summary: Verify that the IUT can indicate requests for PCC rules at IP-CAN session modification and install IP flow mobility routing rules with a CC-Request. Test purpose: Ensure that the IUT, when an IP-CAN session is established, to indicate a request for PCC rules at IP-CAN session modification and to install IP flow mobility routing rules, sends a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing PCC rule(s) and their status containing a Event-Trigger AVP containing IP-CAN session modification containing a Routing-Rule-Install AVP containing one or more Routing-Rule-Definition AVPs containing Routing-Filter AVP. Comments: TP_PCEF_MSI_03 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 1st dash) PICS item: A.4.4.1 Summary: Verify that the IUT can indicate requests for PCC rules at IP-CAN session modification (UE requested allocation of new resources) with a CC-Request. Initial Condition UE has requested allocation of new resources for PCC rules. Test purpose: Ensure that the IUT, when an IP-CAN session is established, to indicate a request for PCC rules at IP-CAN session modification, sends a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing PCC rule(s) and their status containing a Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating ADDITION containing one or more Packet-Filter-Information AVP containing a Precedence AVP containing a Packet-Filter-Content AVP containing QoS-Information AVP. Comments: TP_PCEF_MSI_04 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 2nd dash) PICS item: A.4.4.2 Summary: Verify that the IUT can indicate requests for PCC rules at IP-CAN session modification (UE requested modification of existing resources) with a CC-Request. Initial Condition UE has requested modification of existing resources for PCC rules. Test purpose: Ensure that the IUT, when an IP-CAN session is established, to indicate a request for PCC rules at IP-CAN session modification , sends a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing PCC rule(s) and their status containing a Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating MODIFICATION containing one or more Packet-Filter-Information AVP. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 23 TP_PCEF_MSI_05 Standards Reference: 4.5.1 (item 2, 2nd dashed list, 3rd dash) PICS item: A.4.4.3 Summary: Verify that the IUT can indicate requests for PCC rules at IP-CAN session modification (UE requested deletion of existing resources) with a CC-Request. Initial Condition UE has requested deletion of existing resources for PCC rules. Test purpose: Ensure that the IUT, when an IP-CAN session is established, to indicate a request for PCC rules at IP-CAN session modification), sends a CC-Request containing a CC-Request-Type AVP indicating UPDATE_REQUEST containing a Charging-Rule-Report AVP containing PCC rule(s) and their status containing a Event-Trigger AVP indicating RESOURCE_MODIFICATION_REQUEST containing a Packet-Filter-Operation AVP indicating DELETION containing one or more Packet-Filter-Information AVP containing a Packet-Filter-Identifier AVP. Comments: |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.3 Invalid Behaviour | Void |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.4 Session Termination | TP_PCEF_ST_01 Standards Reference: 4.5.7¶4, [7] 4.2.2.1 PICS item: A.4.7 Summary: Verify that the IUT can terminate an IP-CAN session with a CC-Request. Test purpose: Ensure that the IUT, when an IP-CAN session is established, to initiate the IP-CAN session termination, sends a CC-Request containing a CC-Request-Type AVP indicating TERMINATION_REQUEST. Comments: TP_PCEF_ST_02 Standards Reference: 4.5.9 ¶1, [7] 4.2.3.1 PICS item: Summary: Verify that the IUT can process a request for termination of an IP-CAN session. Test purpose: Ensure that the IUT, when an IP-CAN session is established, on receipt of a RA-Request containing a Session-Release-Cause AVP, sends a RA-Answer and sends a CC-Request containing a CC-Request-Type AVP indicating TERMINATION_REQUEST. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 24 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.5 PCC rules | TP_PCEF_PCC_01 Standards Reference: 4.5.2 (2nd dashed list 1st dash) PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) activating one PCC rule. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing one Charging-Rule-Install AVP containing a Charging-Rule-Name AVP providing a reference to one PCC rule, sends an RA-Answer indicating the same IP-CAN session. Comments: NOTE: IP-CAN session identification is realized by DIAMETER session ID. TP_PCEF_PCC_02 Standards Reference: 4.5.2 ¶6 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) activating multiple PCC rules. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing multiple Charging-Rule-Install AVPs containing a Charging-Rule-Base-Name AVP providing a reference to one PCC rule, sends an RA-Answer indicating the same IP-CAN session. Comments: TP_PCEF_PCC_03 Standards Reference: 4.5.2 (after note 1) PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) requesting confirmation of the successful allocation of resource to a PCC rule. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Name AVP providing a reference to a PCC rule containing a Resource-Allocation-Notification AVP indicating ENABLE_NOTIFICATION containing a Event-Trigger AVP indicating SUCCESSFUL_RESOURCE_ALOCATION, sends an RA-Answer indicating the same IP-CAN session. Comments: TP_PCEF_PCC_04 Standards Reference: 4.5.2 (2nd dashed list 2nd dash) PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) installing or modifying a PCC rule. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP, sends an RA-Answer indicating the same IP-CAN session. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 25 TP_PCEF_PCC_05 Standards Reference: 4.5.2 (2nd dashed list 3rd dash) PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) deactivating or removing a PCC rule. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Remove AVP containing a Charging-Rule-Name AVP, sends an RA-Answer indicating the same IP-CAN session. Comments: TP_PCEF_PCC_06 Standards Reference: 4.5.2 ¶12 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) deactivating a group of PCC rules. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Remove AVP containing a Charging-Rule-Base-Name AVP, sends an RA-Answer indicating the same IP-CAN session. Comments: TP_PCEF_PCC_07 Standards Reference: 4.5.2.3 ¶1, 5.3.53 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) activating a PCC rule for a gate function. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Flow-Information AVP containing a Flow-Direction AVP indicating UPLINK or DOWNLINK containing a Packet-Filter-Identifier AVP, sends an RA-Answer containing a Media-Component-Description AVP containing a Flow Status AVP indicating if possible uplink or downlink gate is opened or closed. Comments: NOTE: Check if answer is sent by SUT in case of optional AVP. TP_PCEF_PCC_08 Standards Reference: 4.5.2.5 ¶1 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) activating a PCC rule with usage monitoring control. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Monitoring-Key AVP, sends an RA-Answer. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 26 TP_PCEF_PCC_09 Standards Reference: 4.5.3 ¶1 and 3 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) removing event triggers. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing an Event-Trigger AVP indicating NO_EVENT_TRIGGERS, sends an RA-Answer. Comments: TP_PCEF_PCC_10 Standards Reference: 4.5.4.4 ¶1 and 2 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) requesting provision of the access network charging identifier. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing an Event-Trigger AVP indicating CHARGING_CORELATION_EXCHANGE containing a Charging-Rule-Install AVP containing a Charging-Correlation-Indicator AVP indicating CHARGING_IDENTIFIER_REQUIRED, sends an RA-Answer and sends a CC-Request containing an Access-Network-Charging-Identifier-Gx AVP. Comments: TP_PCEF_PCC_11 Standards Reference: 4.5.5.2 ¶1 and 2 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) provisioning of authorized QoS. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a QoS-Information AVP not containing a Bearer-Identifier AVP, sends an RA-Answer. Comments: TP_PCEF_PCC_12 Standards Reference: 4.5.12 ¶1 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) trying to activate an unknown PCC rule. Test purpose: Ensure that the IUT is in PUSH procedure, on receipt of a RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Name AVP providing a reference to a non existing PCC rule, sends a RA-Answer containing a Charging-Rule-Report AVP containing a Charging-Rule-Name AVP containing a Rule-Failure-Code AVP indicating UNKNOWN_RULE_NAME containing a PCC-Rule-Status AVP indicating INACTIVE. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 27 TP_PCEF_PCC_13 Standards Reference: 4.5.12 ¶7 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) trying to activate a PCC rule with unknown values. Test purpose: Ensure that the IUT, on receipt of an RA- Request- containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Rating-Group AVP indicating unknown value, sends an RA-Answer containing a Charging-Rule-Report AVP containing a Charging Rule-Name AVP containing a Rule-Failure-Code AVP indicating RATING_GROUP_ERROR containing a PCC-Rule-Status AVP indicating INACTIVE. Comments: TP_PCEF_PCC_14 Standards Reference: 4.5.13 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) activating the revalidation timer. Test purpose: Ensure that the IUT trigger a PCRF interaction to request PCC rules from the PCRF for an established IP CAN session on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Revalidation-Time AVP indicating a new value, sends an RA-Answer, and after revalidation timeout sends a CC-Request. Comments: TP_PCEF_PCC_15 Standards Reference: 4.5.13 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) stopping the revalidation timer. Test purpose: Ensure that the IUT trigger a PCRF interaction to request PCC rules from the PCRF for an established IP CAN session on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Revalidation-Time AVP indicating a new value, sends an RA-Answer, and before revalidation timeout on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Event-Trigger AVP indicating REVALIDATION_TIMEOUT, sends an RA-Answer. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 28 TP_PCEF_PCC_16 Standards Reference: 4.5.13 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) activating a PCC rule with time of the day procedure. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Rule-Activation-Time AVP, sends an RA-Answer. Comments: TP_PCEF_PCC_17 Standards Reference: 4.5.13 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) deactivating a PCC rule with time of the day procedure. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP containing a Rule-Deactivation-Time AVP, sends an RA-Answer. Comments: TP_PCEF_PCC_18 Standards Reference: 4.5.2 (10th paragraph) PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) combining multiple PCC rule operations. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a Charging-Rule-Remove AVP containing a Charging-Rule-Name AVP containing two Charging-Rule-Install AVPs containing a Charging-Rule-Definition AVP containing a Charging-Rule-Name AVP, sends an RA-Answer indicating the same IP-CAN session. Comments: TP_PCEF_PCC_19 Standards Reference: 4.5.3 ¶1 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) containing multiple event triggers. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing two Event-Trigger AVPs, sends an RA-Answer. Comments: TP_PCEF_PCC_20 Standards Reference: 4.5.5.0 ¶1st dash PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) provisioning of authorized QoS for IP-CAN bearer. Test purpose: Ensure that the IUT, on receipt of an RA-Request containing a QoS-Information AVP containing a Bearer-Identifier AVP, sends an RA-Answer. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 29 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.6 Special services and features | |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.6.1 Emergency services | TP_PCEF_EMS_01 Standards Reference: 4.5.15.2.1 ¶2 PICS item: Summary: Verify that the IUT can indicate requests for PCC rules at IP-CAN session establishment to an emergency service with a CC-Request. Test purpose: Ensure that the IUT to indicate a request for PCC rules for Emergency services at IP-CAN session establishment, sends a CC-Request containing a CC-Request-Type AVP indicating INITIAL_REQUEST containing an IP-CAN-Type AVP containing the type of IP-CAN containing a RAT-Type AVP containing the radio access technology containing a Framed-IP-Address AVP indicating the full IP address of the UE containing a Called-Station-Id AVP indicating the Emergency APN containing a Subscription-Id AVP indicating IMSI or containing a User-Equipment-Info AVP indicating IMEI. Comments: In the case of IPv6 the Framed-IP-Address AVP is replaced by the Framed-IPv6- Address-Prefix AVP. |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.6.2 Usage monitoring control | TP_PCEF_UMC_01 Standards Reference: 4.5.16 ¶2 and 5 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) requesting usage monitoring control. Test purpose: Ensure that the IUT, on receipt of a RA-Request containing an Event-Trigger AVP containing an USAGE_REPORT containing a Usage-Monitoring-Information AVP containing a Granted-Service-Unit AVP containing a CC-Total-Octets AVP containing a CC-Input-Octets AVP containing a CC-Output-Octets AVP containing a Monitoring-Key AVP containing a monitoring key, sends an RA-Answer. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 30 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.6.3 Reporting Accumulated Usage | TP_PCEF_RAU_01 Standards Reference: 4.5.17.1 PICS item: Summary: Verify that the IUT can report that the usage threshold for a monitoring key has been reached with a CC-Request. Initial Condition: Usage monitoring is enabled for monitoring key: Key_A Test purpose: Ensure that the IUT, when the usage threshold for Key_A is reached, sends a CC-Request containing CC-Request-Type AVP indicating UPDATE_REQUEST. containing Event-Trigger AVP indicating USAGE_REPORT containing Usage-Monitoring-Information AVP containing Monitoring-Key AVP indicating Key_A containing Used-Service-Unit AVP containing CC-Total-Octets AVP indicating the total volume containing ( CC-Input-Octets AVP (Note 1) indicating the uplink volume or CC-Output-Octets AVP (Note 2) indicating the downlink volume ). Comments: NOTE 1: Only for uplink. NOTE 2: Only for downlink. TP_PCEF_RAU_02 Standards Reference: 4.5.17.2 PICS item: Summary: Verify that the IUT can report that the accumulated usage for a rule that has been removed or deactivated with a CC-Request. Initial Condition: Usage monitoring is enabled for monitoring key: Key_A Test purpose: Ensure that the IUT: on receipt of a RA-Request removing or deactivating the PCC rule associated with Key_A, sends a RA-Answer sends a CC-Request containing CC-Request-Type AVP indicating UPDATE_REQUEST containing Event-Trigger AVP indicating USAGE_REPORT containing Usage-Monitoring-Information AVP containing Monitoring-Key AVP indicating Key_A containing Used-Service-Unit AVP containing CC-Total-Octets AVP indicating the total volume containing ( CC-Input-Octets AVP (Note 1) indicating the uplink volume or CC-Output-Octets AVP (Note 2) indicating the downlink volume ). Comments: NOTE 1: Only for uplink. NOTE 2: Only for downlink. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 31 TP_PCEF_RAU_03 Standards Reference: 4.5.17.2 PICS item: Summary: Verify that the IUT can report that the accumulated usage for a rule that has been removed or deactivated with a CC-Request. Initial Condition: Usage monitoring is enabled for monitoring key: Key_A The IUT has sent a CC-Request not related to reporting usage for Key_A. Test purpose: Ensure that the IUT having sent a CC-Request, on receipt of a CC-Answer removing or deactivating the PCC rule associated with Key_A, sends a CC-Request containing CC-Request-Type AVP indicating UPDATE_REQUEST containing Event-Trigger AVP indicating USAGE_REPORT containing Usage-Monitoring-Information AVP containing Monitoring-Key AVP indicating Key_A containing Used-Service-Unit AVP containing CC-Total-Octets AVP indicating the total volume containing ( CC-Input-Octets AVP (Note 1) indicating the uplink volume or CC-Output-Octets AVP (Note 2) indicating the downlink volume ). Comments: NOTE 1: Only for uplink. NOTE 2: Only for downlink. TP_PCEF_RAU_04 Standards Reference: 4.5.17.4 PICS item: Summary: Verify that the IUT can report the accumulated usage at IP-CAN session termination with a CC-Request. Initial Condition: Usage monitoring is enabled for monitoring key: Key_A Test purpose: Ensure that the IUT, when an IP-CAN session has terminated, sends a CC-Request containing CC-Request-Type AVP indicating TERMINATION_REQUEST containing Usage-Monitoring-Information AVP containing Used-Service-Unit AVP containing CC-Total-Octets AVP indicating the total volume containing ( CC-Input-Octets AVP (Note 1) indicating the uplink volume or CC-Output-Octets AVP (Note 2) indicating the downlink volume ). Comments: NOTE 1: Only for uplink. NOTE 2: Only for downlink. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 32 TP_PCEF_RAU_05 Standards Reference: 4.5.17.5 PICS item: Summary: Verify that the IUT can report the accumulated usage requested by the PCRF for all monitored keys with a CC-Request. Initial Condition: Usage monitoring is enabled for multiple monitoring keys. Test purpose: Ensure that the IUT, on receipt of a RA-Request containing Usage-Monitoring-Information AVP containing Usage-Monitoring-Report AVP indicating USAGE_MONITORING_REPORT_REQUIRED not containing Monitoring-Key AVP, sends a RA-Answer sends a CC-Request containing CC-Request-Type AVP indicating UPDATE_REQUEST containing Event-Trigger AVP indicating USAGE_REPORT containing one Usage-Monitoring-Information AVP per monitored key containing Monitoring-Key AVP containing Used-Service-Unit AVP containing CC-Total-Octets AVP indicating the total volume containing ( CC-Input-Octets AVP (Note 1) indicating the uplink volume or CC-Output-Octets AVP (Note 2) indicating the downlink volume ). Comments: NOTE 1: Only for uplink. NOTE 2: Only for downlink. ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 33 TP_PCEF_RAU_06 Standards Reference: 4.5.17.5 PICS item: Summary: Verify that the IUT can report the accumulated usage requested by the PCRF for one monitored keys with a CC-Request. Initial Condition: Usage monitoring is enabled for monitoring key: Key_A. Test purpose: Ensure that the IUT, on receipt of a RA-Request containing Usage-Monitoring-Information AVP containing Usage-Monitoring-Report AVP indicating USAGE_MONITORING_REPORT_REQUIRED containing Monitoring-Key AVP indicating Key_A, sends a RA-Answer sends a CC-Request containing CC-Request-Type AVP indicating UPDATE_REQUEST containing Event-Trigger AVP indicating USAGE_REPORT containing Usage-Monitoring-Information AVP containing Monitoring-Key AVP indicating Key_A containing Used-Service-Unit AVP containing CC-Total-Octets AVP indicating the total volume containing ( CC-Input-Octets AVP (Note 1) indicating the uplink volume or CC-Output-Octets AVP (Note 2) indicating the downlink volume ). Comments: NOTE 1: Only for uplink. NOTE 2: Only for downlink. TP_PCEF_RAU_07 Standards Reference: 4.5.17.3 PICS item: Summary: Verify that the IUT can report when a monitored key has been disabled with a CC-Request. Initial Condition: Usage monitoring is enabled for monitoring key: Key_A. Test purpose: Ensure that the IUT, on receipt of a RA-Request containing Usage-Monitoring-Information AVP containing Usage-Monitoring-Support AVP indicating USAGE_MONITORING_DISABLED, containing Monitoring-Key AVP indicating Key_A, sends a RA-Answer sends a CC-Request containing CC-Request-Type AVP indicating UPDATE_REQUEST containing Event-Trigger AV indicating USAGE_REPORT. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 34 |
97ecb7ef16158b2b662fc69af5cd18a7 | 101 606-2 | 5.2.2.6.4 IMS Restoration Support | TP_PCEF_IRS_01 Standards Reference: 4.5.18 ¶2 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) requesting IMS restoration support. Test purpose: Ensure that the IUT: on receipt of a RA- Request containing a Charging-Rule-Install AVP containing a Charging-Rule-Definition AVP containing a Flow-Information AVP containing a AF-Signaling-Protocol AVP sends an RA-Answer. Comments: TP_PCEF_IRS_02 Standards Reference: 4.5.18 PICS item: Summary: Verify that the IUT can successfully process an RA-Request (PUSH procedure) stopping the IMS restoration support. Initial Condition: IMS restoration support is switched on. Test purpose: Ensure that the IUT: on receipt of a RA- Request containing a Charging-Rule-Remove AVP containing a Charging-Rule-Name AVP, sends an RA-Answer. Comments: ETSI ETSI TS 101 606-2 V1.1.1 (2012-09) 35 History Document history V1.1.1 September 2012 Publication |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 1 Scope | ........................................................................................................................................................ 5 |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 2 References | ................................................................................................................................................ 5 |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 2.1 Normative references | ......................................................................................................................................... 5 |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 2.2 Informative references | ........................................................................................................................................ 5 |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 3 Definitions and abbreviations | ................................................................................................................... 5 |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 3.1 Definitions | .......................................................................................................................................................... 5 |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 3.2 Abbreviations | ..................................................................................................................................................... 6 |
06879c1ef921ff98fd176d53272f5e98 | 101 606-1 | 4 Conformance | ............................................................................................................................................ 6 Annex A (normative): PICS proforma ................................................................................................. 7 A.1 Guidance for completing the ICS proforma ............................................................................................. 7 A.1.1 Purposes and structure ........................................................................................................................................ 7 A.1.2 Abbreviations and conventions .......................................................................................................................... 7 A.1.3 Instructions for completing the PICS proforma.................................................................................................. 8 A.2 Identification of the Network Equipment ................................................................................................. 9 A.2.1 Date of the statement .......................................................................................................................................... 9 A.2.2 Network Equipment Under Test identification................................................................................................... 9 A.2.3 Product supplier .................................................................................................................................................. 9 A.2.4 Client ................................................................................................................................................................ 10 A.2.5 PICS contact person ......................................................................................................................................... 10 A.3 Identification of the protocol .................................................................................................................. 11 A.4 Global statement of conformance ........................................................................................................... 11 A.5 PICS proforma tables ............................................................................................................................. 11 A.5.1 Roles ................................................................................................................................................................. 11 A.5.2 System Capabilities for PCRF .......................................................................................................................... 12 A.5.3 System Capabilities for PCEF .......................................................................................................................... 13 History .............................................................................................................................................................. 14 ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee IMS Network Testing (INT). The present document is part 1 of a multi-part deliverable covering the test specifications for the Diameter protocol on the Gx interface, as identified below: Part 1: "Protocol Implementation Conformance Statement (PICS)"; Part 2: "Test Suite Structure (TSS) and Test Purposes (TP)"; Part 3: "Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification". Introduction To evaluate protocol conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented for a telecommunication specification. Such a statement is called a Protocol Implementation Conformance Statement (PICS). ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 5 1 Scope The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the test specifications for the Diameter protocol on the Gx interface as specified in TS 129 212 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3] and ETS 300 406 [4]. The supplier of a protocol implementation which is claimed to conform to TS 129 212 [1] is required to complete a copy of the PICS proforma provided in annex A of the present document and is required to provide the information necessary to identify both the supplier and the implementation. 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. 2.1 Normative references The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 212: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx/Sd reference point (3GPP TS 29.212 version 10.5.0 Release 10)". [2] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [3] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [4] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". 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. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 129 212 [1] and the following apply: PICS proforma: document, in the form of a questionnaire, designed by the protocol specifier or conformance test suite specifier, which, when completed for an OSI implementation or system, becomes the PICS NOTE: See ISO/IEC 9646-1 [2]. ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 6 Protocol Implementation Conformance Statement (PICS): statement made by the supplier of an Open Systems Interconnection (OSI) implementation or system, stating which capabilities have been implemented for a given OSI protocol NOTE: See ISO/IEC 9646-1 [2]. static conformance review: review of the extent to which the static conformance requirements are met by the IUT, accomplished by comparing the PICS with the static conformance requirements expressed in the relevant standard(s) NOTE: See ISO/IEC 9646-1 [2]. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 129 212 [1] and the following apply: PICS Protocol Implementation Conformance Statement A PICS proforma which conforms to this PICS proforma specification shall be technically equivalent to annex A, and shall preserve the numbering and ordering of the items in annex A. A PICS which conforms to this PICS proforma specification shall: a) describe an implementation which claims to conform to TS 129 212 [1]; b) be a conforming ICS proforma which has been completed in accordance with the instructions for completion given in clause A.1; c) include the information necessary to uniquely identify both the supplier and the implementation. ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 7 Annex A (normative): 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 annex so that it can be used for its intended purposes and may further publish the completed PICS proforma. A.1 Guidance for completing the ICS proforma A.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 relevant specifications may provide information about the implementation in a standardised manner. The PICS proforma is subdivided into clauses for the following categories of information: - instructions for completing the PICS proforma; - identification of the implementation; - identification of the protocol; - PICS proforma tables (for example: Major capabilities, etc). A.1.2 Abbreviations and conventions This annex does not reflect dynamic conformance requirements but static ones. In particular, a condition for support of a PDU parameter does not reflect requirements about the syntax of the PDU (i.e. the presence of a parameter) but the capability of the implementation to support the parameter. In the sending direction, the support of a parameter means that the implementation is able to send this parameter (but it does not mean that the implementation always sends it). In the receiving direction, it means that the implementation supports the whole semantic of the parameter that is described in the related protocol specification. As a consequence, PDU parameter tables in this annex are not the same as the tables describing the syntax of a PDU in the reference specification. The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [3]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". Reference column The reference column gives reference to the relevant sections in core specifications. ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 8 Status column The various status used in this annex are in accordance with the rules in table A.1. Table A.1: Key to status codes Status code Status name Meaning m mandatory The capability shall be supported. It is a static view of the fact that the conformance requirements related to the capability in the reference specification are mandatory requirements. This does not mean that a given behaviour shall always be observed (this would be a dynamic view), but that it shall be observed when the implementation is placed in conditions where the conformance requirements from the reference specification compel it to do so. For instance, if the support for a parameter in a sent PDU is mandatory, it does not mean that it shall always be present, but that it shall be present according to the description of the behaviour in the reference specification (dynamic conformance requirement). o optional The capability may or may not be supported. It is an implementation choice. n/a not applicable It is impossible to use the capability. No answer in the support column is required. c.<integer> conditional The requirement on the capability ("m", "o", "n/a") depends on the support of other optional or conditional items. <integer> is the identifier of the conditional expression. o.<integer> qualified optional For mutually exclusive or selectable options from a set. <integer> is the identifier of the group of options, and the logic of selection of the options. Mnemonic column The Mnemonic column contains mnemonic identifiers for each item. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [3], are used for the support column: Y or y supported by the implementation N or n not supported by the implementation N/A, n/a or - no answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status) References to items For each possible item answer (answer in the support column) within the PICS proforma there exists a unique reference, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. EXAMPLE: A.5/4 is the reference to the answer of item 4 in table A.5. A.1.3 Instructions for completing the PICS proforma The supplier of the implementation may complete the PICS proforma in each of the spaces provided. More detailed instructions are given at the beginning of the different clauses of the PICS proforma. ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 9 A.2 Identification of the Network Equipment Identification of the Network Equipment should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person. A.2.1 Date of the statement ......................................................................................................................................................................................... A.2.2 Network Equipment Under Test identification Name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Software configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.3 Product supplier Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 10 Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.4 Client Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.5 PICS contact person Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 11 A.3 Identification of the protocol This PICS proforma applies to the following specifications: TS 129 212 [1]. A.4 Global statement of conformance The implementation described in this PICS meets all the mandatory requirements of the referenced standard? [ ] Yes [ ] No NOTE: Answering "No" to this question indicates non-conformance to the protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming. Explanations may be entered in the comments field at the bottom of each table or on attached pages. In the tabulations which follow, all references are to TS 129 212 [1] unless another numbered reference is explicitly indicated. A.5 PICS proforma tables A.5.1 Roles Table A.2: Roles Item Roles Reference Status Support 1 PCRF 4.4.1 o.1 2 PCEF 4.4.2 o.1 o.1: At least one of these roles shall be supported. ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 12 A.5.2 System Capabilities for PCRF The tables provided in this clause need only to be completed for PCRF implementations, where item A.2/1 above is supported. Table A.3: System Capabilities for PCRF Item Does the IUT support ... Reference Status Support 1 the sponsored data connectivity feature? 4.3.1, 4.5.20 o 2 requests for PCC rules? 4.5.1 m 2.1 acceptance of requests for PCC rules? (Note 1) 4.5.1, 4.4.1 m 2.2 rejection of requests for PCC rules? 4.5.1 m 2.2.1 ... due to incomplete, erroneous or missing information? 4.5.1 o 2.2.2 ... due to conflicting requests for PCC rules? 4.5.1 o 2.2.3 ... due to non-acceptance of the received packet filters? 4.5.1 m 3 provisioning of PCC rules? 4.5.2 m 3.1 ... using the PULL procedure? 4.5.2 m 3.2 ... using the PUSH procedure? 4.5.2 o 3.3 request for successful resource allocation confirmation? 4.5.2 o 4 provisioning of event triggers? 4.5.3 o 5 provisioning of charging related information for an IP-CAN session? 4.5.4 o 5.1 provisioning of charging addresses? 4.5.4.1 o 5.2 provisioning of default charging methods? 4.5.4.2 o 5.3 provisioning of access network charging identifier? 4.5.4.4 o 6 provisioning and policy enforcement for authorized QoS? 4.5.5 o 7 processing of IP-CAN session termination indications? 4.5.6, 4.5.7 m 8 procedures for requesting IP-CAN bearer termination? 4.5.8 o 9 IP-CAN session termination due to internal trigger or trigger from the SPR? 4.5.9 o 10 bearer control mode selection? 4.5.10 m 11 provisioning of event report indication? 4.5.11 m 12 PCC rule error handling? 4.5.12 m 13 time of the day procedures? 4.5.13 o 14 procedures for IMS emergency sessions? 4.5.15 m 15 usage monitoring control? 4.5.16 o 16 procedures for reporting accumulated usage? 4.5.17 m 17 IMS restoration support? 4.5.18 o 18 procedures for multimedia priority support? 4.5.19 m NOTE 1: Support of the acceptance of requests for PCC rules is not explicitly mentioned in clause 4.5.1 but can be assumed from clause 4.4.1's statement "The PCRF shall provision PCC Rules to the PCEF via the Gx reference point". ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 13 A.5.3 System Capabilities for PCEF The tables provided in this clause need only to be completed for PCEF implementations, where item A.2/2 above is supported. Table A.4: System Capabilities for PCEF Item Does the IUT support ... Reference Status Support 1 the sponsored data connectivity feature? 4.3.1, 4.5.20 o 2 requests for PCC rules? 4.5.1 m 2.1 ... at IP-CAN session establishment? 4.5.1 m 2.2 ... at IP-CAN session modification? 4.5.1 m 2.3 ... at IP-CAN session termination? 4.5.1, 4.5.7 m 2.4 ... without trigger event (failure in PCC rule installation/activation or enforcement)? 4.5.1, 4.5.12 m 3 provision of IP flow mobility routing rules? 4.3a.4, 4.5.1 o 4 procedures for UE initiated resource modification? 4.5.1 o 4.1 procedures for UE requested allocation of new resources? 4.5.1 o 4.2 procedures for UE requested modification of existing resources? 4.5.1 o 4.3 procedures for UE requested deletion of existing resources? 4.5.1 o 3.3 request for successful resource allocation confirmation? 4.5.2 o 4 procedures for provisioning of event triggers? 4.5.3 m 5 provisioning of charging related information for an IP-CAN session? 4.5.4 m 6 procedures for provisioning and policy enforcement for authorized QoS? 4.5.5 m 7 IP-CAN session termination indications? 4.5.6, 4.5.7 m 8 processing of requests for IP-CAN bearer termination? 4.5.8 m 9 IP-CAN session termination due to internal trigger or trigger from the SPR? 4.5.9 m 10 bearer control mode selection? 4.5.10 o 11 provisioning of event report indication? 4.5.11 o 12 PCC rule error handling? 4.5.12 m 13 time of the day procedures? 4.5.13 m 14 procedures for IMS emergency sessions? 4.5.15 m 15 processing of requests for usage monitoring control? 4.5.16 m 16 reporting accumulated usage? 4.5.17 m 17 procedures for IMS restoration support? 4.5.18 m 18 procedures for multimedia priority support? 4.5.19 m ETSI ETSI TS 101 606-1 V1.1.1 (2012-07) 14 History Document history V1.1.1 July 2012 Publication |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes for the Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem defined in Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem [1] in compliance with the relevant requirements. |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced 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. |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 654: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification (3GPP TS 24.654 Release 10)". [2] ETSI TS 101 597-1: "IMS Network Testing (INT); Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification; Part 1: Protocol Implementation Conformance Statement (PICS)". |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 3 Definitions, symbols and abbreviations | |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 654 [1] apply. |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in TS 124 654 [1] and the following apply: Gm Reference point: supports the communication between UE and IMS Mw Reference point allows the communication and forwarding of signalling messaging between CSCFs ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 6 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 654 [1] and the following apply: AS Application Server CD Communication Deflection CDIV Communication DIVersion service CFB Communication Forwarding on Busy CFNL Communication Forwarding on Not Logged-in CFNR Communication Forwarding on no Reply CFU Communication Forwarding Unconditional CONF CONFerence calling CSCF Call Session Control Function CUG Closed User Group ECT Explicit Communication Transfer IA Incoming Access ICB Incoming Communication Barring within a CUG IMS IP Multimedia Subsystem IP Internet Protocol ISC Reference point between Serving CSCF and Application Server IUT Implementation Under Test NNI Network-to-Network Interface OA Outgoing Access OAE Outgoing Access, explicit request required OAI Outgoing Access, implicit outgoing access for all communications OCB Outgoing Communication Barring within a CUG PIXIT Protocol Implementation eXtra Information for Testing SIP Session Initiation Protocol SS Supplementary Services SUT System Under Test TP Test Purposes TSS Test Suite Structure UA User Agent UE User Equipment XML eXtensible Markup Language |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 4 Test Suite Structure (TSS) | CUG originating_UE CUG_U01_xxx originating_AS CUG without preference CUG_N01_xxx CUG without preference + OAE CUG_N02_xxx CUG without preference + OAI CUG_N03_xxx CUG with preference CUG_N04_xxx CUG with preference + OAE CUG_N05_xxx CUG with preference + OAI CUG_N06_xxx No CUG CUG_N07_xxx terminating_AS CUG with OA not allowed CUG_N08_xxx CUG with OA allowed CUG_N09_xxx No CUG CUG_N10_xxx Services CONF CUG_N11_xxx CDIV CUG_N12_xxx ECT CUG_N13_xxx ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 7 |
5882237be8e6c3816c60b16792fa1330 | 101 597-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 TS 124 654 [1]. The stage 3 description describes the requirements for several network entities and also the requirements regarding terminal 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. |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 4.1.1 Testing of the AS | The AS entity is responsible for performing and managing services. The ISC interface is the appropriate access point for testing. Figure 4.1.1-1: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also possible to perform the test of the AS using any NNI (Mw, Mw, Mx) interface (see figure 4.1.1-2). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible. CSCF (and/or AS) Implementation under Test Test System Test System Mw, Mg, Mx Mw, Mg, Mx Figure 4.1.1-2: Applicable interfaces for tests using a (generic) NNI interface |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 4.1.2 Testing of the UE | There are special clauses in the protocol standard describing the procedures that apply at the originating and terminating user equipment. Therefore the test configuration in figure 4.1.2-1 has been chosen. ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 8 User Equipment Implementation under Test Test System Gm Figure 4.1.2-1: Applicable configuration to test UE functionalities |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5 Test Purposes (TP) | |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.1 Introduction | For each test requirement a TP is defined. |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "CUG" <iut> = type of IUT: U User equipment N Network entity <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999) |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.1.2 Test strategy | As the base standard TS 124 654 [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 101 597-1 [2]. The criteria applied include the following: • Whether or not a test case can be built from the TP is not considered. ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 9 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2 Test Purposes for Closed User Group (CUG) | |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.1 Actions at the originating UA | TSS CUG/originating_UE TP CUG_U01_001 CUG reference clause 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose Explicit request of CUG service Outgoing Access. The originating user requests explicitly the CUG service by including in the initial INVITE an xml CUGrequestType containing the preferred CUG and an outgoing access request set to "true". Preconditions: SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[PIXIT]</cugIndex> </cugCallOperation> </cug> Comments: User equipment Test equipment INVITE requesting CUG explicitly TSS CUG/originating_UE TP CUG_U01_002 CUG reference clause 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose Explicit request of CUG service without Outgoing Access. The originating user requests explicitly the CUG service by including in the initial INVITE an xml CUGrequestType containing the preferred CUG and an outgoing access request set to "false". Preconditions: SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[PIXIT]</cugIndex> </cugCallOperation> </cug> Comments: User equipment Test equipment INVITE requesting CUG explicitly ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 10 TSS CUG/originating_UE TP CUG_U01_003 CUG reference clause 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 AND PICS 4.6.1/2 Test purpose Explicit request of CUG service without CUG index. The originating user requests explicitly the CUG service by including in the initial INVITE an xml CUGrequestType containing the preferred CUG and no 'cugIndex' element is present. Preconditions: SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[PIXIT]</cugIndex> </cugCallOperation> </cug> Comments: User equipment Test equipment INVITE requesting CUG explicitly |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2 Actions at the AS of the originating User | |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.1 CUG without preference | TSS CUG/originating_AS/CUG without preference TP CUG_N01_001 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose CUG without preference: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 11 TSS CUG/originating_AS/CUG without preference TP CUG_N01_002 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/10 Test purpose CUG without preference + OCB: INVITE with CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK TSS CUG/originating_AS/CUG without preference TP CUG_N01_003 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose CUG without preference: INVITE with unallocated CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 12 TSS CUG/originating_AS/CUG without preference TP CUG_N01_004 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose CUG without preference: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[registered CUG index]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 13 TSS CUG/originating_AS/CUG without preference TP CUG_N01_005 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 4.7.1/10 Test purpose CUG without preference +OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK TSS CUG/originating_AS/CUG without preference TP CUG_N01_006 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose CUG without preference: INVITE with unallocated CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 14 TSS CUG/originating_AS/CUG without preference TP CUG_N01_007 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose CUG without preference: INVITE without CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, rejects the INVITE request by sending a 403 Forbidden due to missing CUGindex. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK TSS CUG/originating_AS/CUG without preference TP CUG_N01_008 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose CUG without preference: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, rejects the INVITE request by sending a 403 Forbidden due to missing CUGindex. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 15 TSS CUG/originating_AS/CUG without preference TP CUG_N01_009 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose CUG without preference: INVITE for non-CUG communication, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden due to missing cug XML element. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: No xml element <cug> Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.2 CUG without preference + OAE | TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_001 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 16 TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_002 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND PICS 4.7.1/10 Test purpose CUG without preference + OAE + OCB: INVITE with CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_003 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE: INVITE with unallocated CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 17 TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_004 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE: INVITE with CUG index and outgoingAccessRequest = true, successful non CUG communication. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 18 TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_005 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE + OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards the INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: OCB within CUG Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_006 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE: INVITE with unallocated CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 19 TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_007 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE: INVITE without CUG index, unsuccessful outgoing access not allowed. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, rejects the INVITE request by sending a 403 Forbidden due to outgoing access not allowed. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_008 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE: INVITE without CUG index and with outgoingAccessRequest = true, successful outgoing access allowed. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, forwards the INVITE request containing no xml element cug due to outgoing access allowed. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 20 TSS CUG/originating_AS/CUG without preference + OAE TP CUG_N02_009 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 Test purpose CUG without preference + OAE: INVITE for non-CUG communication, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed per communication SIP header values: INVITE: No xml element <cug> 403 Forbidden Reason: … Comments: Test equipment (ISC) AS INVITE 403 Forbidden ACK |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.3 CUG without preference + OAI | TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_001 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 21 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_002 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI and OCB within CUG: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: OCB within CUG Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_003 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI: INVITE with unregistered CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 22 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_004 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards the INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[ registered CUG]</cugIndex> </cugCallOperation> </cug> INVITE2: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 23 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_005 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI and OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: OCB within CUG Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_006 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 24 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_007 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI: INVITE without CUG index, successful outgoing access allowed. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, forwards an INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_008 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI: INVITE without CUG index and with outgoingAccessRequest = true, successful outgoing access allowed. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, forwards an INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 25 TSS CUG/originating_AS/CUG without preference + OAI TP CUG_N03_009 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/3 Test purpose CUG without preference + OAI: INVITE for non-CUG communication, successful. Ensure that the SUT on receipt of an INVITE request containing no xml element cug, forwards an INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: allowed permanent SIP header values: INVITE1: No xml element <cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.4 CUG with preference | TSS CUG/originating_AS/CUG with preference TP CUG_N04_001 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose CUG with preference: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 26 TSS CUG/originating_AS/CUG with preference TP CUG_N04_002 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 AND PICS 4.7.1/10 Test purpose CUG with preference + OCB: INVITE with CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK TSS CUG/originating_AS/CUG with preference TP CUG_N04_003 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose CUG with preference: INVITE with unregistered CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 27 TSS CUG/originating_AS/CUG with preference TP CUG_N04_004 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose CUG with preference: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[registered CUG index]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 28 TSS CUG/originating_AS/CUG with preference TP CUG_N04_005 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 AND PICS 4.7.1/10 Test purpose CUG with preference +OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK TSS CUG/originating_AS/CUG with preference TP CUG_N04_006 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose CUG with preference: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 29 TSS CUG/originating_AS/CUG with preference TP CUG_N04_007 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose CUG with preference: INVITE without CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to preferred CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[registered CUG index]</ networkIndicator> <cugInterlockBinaryCode>[related to preferred CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 30 TSS CUG/originating_AS/CUG with preference TP CUG_N04_008 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose CUG with preference: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, rejects the INVITE request by sending a 403 Forbidden due to outgoing access not allowed. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK TSS CUG/originating_AS/CUG with preference TP CUG_N04_009 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/4 Test purpose CUG with preference: INVITE for non-CUG communication, successful. Ensure that the SUT on receipt of an INVITE request containing no xml element cug, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to preferred CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: not allowed SIP header values: INVITE1: No xml element <cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[registered CUG index]</ networkIndicator> <cugInterlockBinaryCode>[related to preferred CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 31 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.5 CUG with preference + OAE | TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_001 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 32 TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_002 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 AND PICS 4.7.1/10 Test purpose CUG with preference + OAE + OCB: INVITE with CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, rejects the INVITE request by sending a 603 Decline to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_003 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE: INVITE with unregistered CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 33 TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_004 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 34 TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_005 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE + OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB within CUG Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_006 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 35 TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_007 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE: INVITE without CUG index and with outgoingAccessRequest = false, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to preferred CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> </cugCallOperation> </cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to preferred CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_008 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE: INVITE without CUG index and with outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, forwards an INVITE request containing no xml element cug. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 36 TSS CUG/originating_AS/CUG with preference + OAE TP CUG_N05_009 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/5 Test purpose CUG with preference + OAE: INVITE for non-CUG communication, successful. Ensure that the SUT on receipt of an INVITE request containing no xml element cug, returns an INVITE request containing an xml element cug with cugInterlockBinaryCode related to preferred CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed per communication SIP header values: INVITE1: No xml element <cug> INVITE2: Content-Disposition: …;handling=required <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to preferred CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 37 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.6 CUG with preference + OAI | TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_001 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose CUG with preference + OAI: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 38 TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_002 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 AND PICS 4.7.1/10 Test purpose CUG with preference + OAI and OCB: INVITE with CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_003 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose CUG with preference + OAI and OCB within CUG: INVITE with CUG index, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, forwards an INVITE request containing no xml element cug is present Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB within CUG Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 39 TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_004 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose CUG with preference + OAI: INVITE with unregistered CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to non allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 40 TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_005 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose CUG with preference + OAI: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG]</cugIndex> </cugCallOperation> </cug> INVITE2: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 41 TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_006 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 AND PICS 4.7.1/10 Test purpose CUG with preference + OAI and OCB: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE 603 Decline ACK TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_007 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose CUG with preference + OAI and OCB within CUG: INVITE with CUG index and outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and registered CUGIndex, forwards an INVITE request containing no xml element cug is present Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB within CUG Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[registered CUG]</cugIndex> </cugCallOperation> </cug> INVITE2: No xml element <cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 42 TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_008 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose CUG with preference + OAI: INVITE with unregistered CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and unregistered CUGIndex, rejects the INVITE request by sending a 403 Forbidden due to not allocated CUG index. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[unregistered CUG]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 43 TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_009 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 Test purpose CUG with preference + OAI: INVITE without CUG index and with outgoingAccessRequest = true, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, forwards an INVITE request containing an xml element cug with cugInterlockBinaryCode related to preferred CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access). Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> INVITE2: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to preferred CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 TSS CUG/originating_AS/CUG with preference + OAI TP CUG_N06_010 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/6 AND PICS 4.7.1/10 Test purpose CUG with preference + OAI and OCB: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, rejects the INVITE request by sending a 603 Decline due to Outgoing Communication Barring. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: OCB Options for public identity in use: Preferential CUG: registered CUG Outgoing access: allowed permanent SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE 603 Decline ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 44 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.7 No CUG | TSS CUG/originating_AS/No CUG TP CUG_N07_001 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 Test purpose No CUG: INVITE with CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing any CUGIndex, rejects the INVITE request by sending a 403 Forbidden. Preconditions: Originating user has not subscribed to CUG SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[any CUG index]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK TSS CUG/originating_AS/No CUG TP CUG_N07_002 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 Test purpose No CUG: INVITE with CUG index and outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true and any CUGIndex, rejects the INVITE request by sending a 403 Forbidden. Preconditions: Originating user has not subscribed to CUG SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> <cugIndex>[ any CUG index]</cugIndex> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 45 TSS CUG/originating_AS/No CUG TP CUG_N07_003 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 Test purpose No CUG: INVITE without CUG index, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = false, rejects the INVITE request by sending a 403 Forbidden. Preconditions: Originating user has not subscribed to CUG SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK TSS CUG/originating_AS/No CUG TP CUG_N07_004 CUG reference clause 4.5.2.4 Selection expression PICS 4.5.1/2 Test purpose No CUG: INVITE without CUG index and with outgoingAccessRequest = true, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugCallOperation containing outgoingAccessRequest = true, rejects the INVITE request by sending a 403 Forbidden. Preconditions: Originating user has not subscribed to CUG SIP header values: INVITE: <cug> <cugCallOperation> <outgoingAccessRequest>TRUE</outgoingAccessRequest> </cugCallOperation> </cug> 403 Forbidden Reason: … Comments: Test equipment (Gm) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 46 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.3 Actions at the AS of the terminating user | |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.3.1 CUG with OA not allowed | TSS CUG/ terminating _AS/CUG with OA not allowed TP CUG_N08_001 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA not allowed: INVITE with interlock code matching registered CUG index and without outgoing access, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access), forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-ICB) Options for public identity in use: Incoming access: not allowed SIP header values: INVITE1: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 TSS CUG/ terminating _AS/CUG with OA not allowed TP CUG_N08_002 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA not allowed and ICB: INVITE with interlock code matching registered CUG index and without outgoing access, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access), rejects the INVITE request by sending a 603 Decline due to incoming calls barred. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: ICB Options for public identity in use: Incoming access: not allowed SIP header values: INVITE: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (ISC, Mw) AS INVITE 603 Decline ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 47 TSS CUG/ terminating _AS/CUG with OA not allowed TP CUG_N08_003 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA not allowed: INVITE with interlock code not matching registered CUG index and without outgoing access, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode not related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access), rejects the INVITE request by sending a 403 Forbidden due to not matched CUG index. Preconditions: Terminating user has subscribed to CUG Options for public identity in use: Incoming access: not allowed SIP header values: INVITE: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[not related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (ISC, Mw) AS INVITE 403 Forbidden ACK TSS CUG/ terminating _AS/CUG with OA not allowed TP CUG_N08_004 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA allowed: INVITE with interlock code matching registered CUG index and without outgoing access, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access), forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-ICB) Options for public identity in use: Incoming access: allowed SIP header values: INVITE1: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 48 TSS CUG/ terminating _AS/CUG with OA not allowed TP CUG_N08_005 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA allowed and ICB: INVITE with interlock code matching registered CUG index and without outgoing access, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access), rejects the INVITE request by sending a 603 Decline due to incoming calls barred. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: ICB Options for public identity in use: Incoming access: allowed SIP header values: INVITE: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (ISC, Mw) AS INVITE 603 Decline ACK TSS CUG/ terminating _AS/CUG with OA not allowed TP CUG_N08_006 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA allowed: INVITE with interlock code not matching registered CUG index and without outgoing access, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode not related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access), rejects the INVITE request by sending a 403 Forbidden due to not matched CUG index. Preconditions: Terminating user has subscribed to CUG Options for public identity in use: Incoming access: allowed SIP header values: INVITE: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[not related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (ISC, Mw) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 49 TSS CUG/ terminating _AS/CUG with OA not allowed TP CUG_N08_007 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose No CUG: INVITE with interlock code and without outgoing access, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode, networkIndicator (PIXIT) and cugCommunicationIndicator set to "11" (CUG without outgoing access), rejects the INVITE request by sending a 403 Forbidden due to 'Outgoing access not allowed'. Preconditions: Terminating user has not subscribed to CUG SIP header values: INVITE: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to any CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>11</cugCommunicationIndicator> </cug> Comments: Test equipment (ISC, Mw) AS INVITE 403 Forbidden ACK |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.3.2 CUG with OA allowed | TSS CUG/ terminating _AS/CUG with OA allowed TP CUG_N09_001 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA not allowed: INVITE with interlock code matching registered CUG index and with outgoing access, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access), forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-ICB) Options for public identity in use: Incoming access: not allowed SIP header values: INVITE1: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 50 TSS CUG/ terminating _AS/CUG with OA allowed TP CUG_N09_002 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA not allowed and ICB: INVITE with interlock code matching registered CUG index and with outgoing access, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access), rejects the INVITE request by sending a 603 Decline due to incoming calls barred. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: ICB Options for public identity in use: Incoming access: not allowed SIP header values: INVITE: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (ISC, Mw) AS INVITE 603 Decline ACK TSS CUG/ terminating _AS/CUG with OA allowed TP CUG_N09_003 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA not allowed: INVITE with interlock code not matching registered CUG index and with outgoing access, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode not related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access), rejects the INVITE request by sending a 403 Forbidden due to not matched CUG index. Preconditions: Terminating user has subscribed to CUG Options for public identity in use: Incoming access: not allowed SIP header values: INVITE: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[not related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> Comments: Test equipment (ISC, Mw) AS INVITE 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 51 TSS CUG/ terminating _AS/CUG with OA allowed TP CUG_N09_004 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA allowed: INVITE with interlock code matching registered CUG index and with outgoing access, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access), forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: None designated (-ICB) Options for public identity in use: Incoming access: allowed SIP header values: INVITE1: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 TSS CUG/ terminating _AS/CUG with OA allowed TP CUG_N09_005 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA allowed and ICB: INVITE with interlock code matching registered CUG index and with outgoing access, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access), forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has subscribed to CUG Options for registered CUG index: Intra CUG restrictions: ICB Options for public identity in use: Incoming access: allowed SIP header values: INVITE1: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 52 TSS CUG/ terminating _AS/CUG with OA allowed TP CUG_N09_006 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA allowed: INVITE with interlock code not matching registered CUG index and with outgoing access, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode not related to registered CUG index, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access), forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has subscribed to CUG Options for public identity in use: Incoming access: allowed SIP header values: INVITE1: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[not related to registered CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 TSS CUG/ terminating _AS/CUG with OA allowed TP CUG_N09_007 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose No CUG: INVITE with interlock code and with outgoing access, successful. Ensure that the SUT on receipt of an INVITE request containing an xml element cug with cugInterlockBinaryCode, networkIndicator (PIXIT) and cugCommunicationIndicator set to "10" (CUG with outgoing access), forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has not subscribed to CUG SIP header values: INVITE1: <cug> <networkIndicator >[PIXIT]</ networkIndicator> <cugInterlockBinaryCode>[related to any CUG index]</cugInterlockBinaryCode> <cugCommunicationIndicator>10</cugCommunicationIndicator> </cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 53 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.2.2.3 No CUG | TSS CUG/ terminating _AS/No CUG TP CUG_N10_001 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA not allowed: INVITE without xml element cug, unsuccessful. Ensure that the SUT on receipt of an INVITE request containing no xml element cug, rejects the INVITE request by sending a 403 Forbidden. Preconditions: Terminating user has subscribed to CUG Options for public identity in use: Incoming access: not allowed SIP header values: INVITE: No xml element <cug> Comments: Test equipment (ISC) AS INVITE 403 Forbidden ACK TSS CUG/ terminating _AS/No CUG TP CUG_N10_002 CUG reference clause 4.5.2.10 Selection expression PICS 4.5.1/2 Test purpose CUG with IA allowed: INVITE without xml element cug, successful. Ensure that the SUT on receipt of an INVITE request containing no xml element cug, forwards an INVITE request containing no xml element cug. Preconditions: Terminating user has subscribed to CUG Options for public identity in use: Incoming access: allowed SIP header values: INVITE1: No xml element <cug> INVITE2: No XML <cug> element Comments: Test equipment (ISC, Mw) AS Test equipment (Gm) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 54 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.3 Interaction with other services | |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.3.1 Conference calling (CONF) | TSS CUG/Services/CONF TP CUG_N11_001 CUG reference clause 4.6.6 Selection expression PICS 4.7.1/7 Test purpose CUG with OA not allowed: First added conferee join the conference, successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the conference focus allows to join the created conference as the first conferee. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: Request Line <conference URI> <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS A conference is already created INVITE 200 OK TSS CUG/Services/CONF TP CUG_N11_002 CUG reference clause 4.6.6 Selection expression PICS 4.7.1/7 Test purpose CUG with OA not allowed: Subsequent conferee added to the conference, successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the conference focus allows to join the created conference as a subsequent conferee and belongs to the same closed user group. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed SIP header values: INVITE: Request Line <conference URI> <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (ISC, Mw) AS A conference is already created A CUG user is already added to the conference INVITE 200 OK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 55 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.3.2 Communication Diversion Services (CDIV) | TSS CUG/Services/CDIV TP CUG_N12_001 CUG reference clause 4.6.7.1 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarding party, CFU successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFU. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding Unconditional (CFU) Originating party and forwarding party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 56 TSS CUG/Services/CDIV TP CUG_N12_002 CUG reference clause 4.6.7.1 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFU successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFU) and the communication to the forwarded-to party is successful. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding Unconditional (CFU) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 57 TSS CUG/Services/CDIV TP CUG_N12_003 CUG reference clause 4.6.7.1 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFU unsuccessful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFU) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding Unconditional (CFU) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in different CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE1 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 58 TSS CUG/Services/CDIV TP CUG_N12_004 CUG reference clause 4.6.7.2 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarding party, CFB successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFB. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Busy user (CFB) Originating party and forwarding party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw) INVITE1 INVITE2 486 Busy Here ACK INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 59 TSS CUG/Services/CDIV TP CUG_N12_005 CUG reference clause 4.6.7.2 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFB successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFB) and the communication to the forwarded-to party is successful. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Busy user (CFB) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm) INVITE1 INVITE2 486 Busy Here ACK INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 60 TSS CUG/Services/CDIV TP CUG_N12_006 CUG reference clause 4.6.7.2 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFB unsuccessful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFB) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Busy user (CFB) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in different CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) INVITE1 INVITE2 486 Busy Here ACK 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 61 TSS CUG/Services/CDIV TP CUG_N12_007 CUG reference clause 4.6.7.3 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarding party, CFNR successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNR. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on no Reply (CFNR) Originating party and forwarding party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw) INVITE1 INVITE2 180 Ringing INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 62 TSS CUG/Services/CDIV TP CUG_N12_008 CUG reference clause 4.6.7.3 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNR successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNR) and the communication to the forwarded-to party is successful. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on no Reply (CFNR) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm) INVITE1 INVITE2 180 Ringing INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 63 TSS CUG/Services/CDIV TP CUG_N12_009 CUG reference clause 4.6.7.3 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNR unsuccessful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNR) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on no Reply (CFNR) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in different CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) INVITE1 INVITE2 180 Ringing 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 64 TSS CUG/Services/CDIV TP CUG_N12_010 CUG reference clause 4.6.7.4 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarding party, CFNL successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNL. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Not Logged-in (CFNL) Originating party and forwarding party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (ISC, Mw) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 65 TSS CUG/Services/CDIV TP CUG_N12_011 CUG reference clause 4.6.7.4 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNL successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNL) and the communication to the forwarded-to party is successful. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Not Logged-in (CFNL) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 66 TSS CUG/Services/CDIV TP CUG_N12_012 CUG reference clause 4.6.7.4 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNL unsuccessful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNL) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Not Logged-in (CFNL) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in different CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS INVITE1 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 67 TSS CUG/Services/CDIV TP CUG_N12_013 CUG reference clause 4.6.7.5 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarding party, CNRc successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party and the forwarding party and performs the Communication Diversion Service CFNRc. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Subscriber Not Reachable (CFNRc) Originating party and forwarding party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw) INVITE1 INVITE2 INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 68 TSS CUG/Services/CDIV TP CUG_N12_014 CUG reference clause 4.6.7.5 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNRc successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNRc) and the communication to the forwarded-to party is successful. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Subscriber Not Reachable (CFNRc) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm) INVITE1 INVITE2 INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 69 TSS CUG/Services/CDIV TP CUG_N12_015 CUG reference clause 4.6.7.5 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CFNRc unsuccessful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the forwarding party and the forwarded-to party (CFNRc) and the communication to the forwarded-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Forwarding user has subscribed to CDIV Communication Forwarding on Subscriber Not Reachable (CFNRc) Forwarded-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and forwarding party are in the same CUG Originating party and forwarded-to party are in different CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm) INVITE1 INVITE2 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 70 TSS CUG/Services/CDIV TP CUG_N12_016 CUG reference clause 4.6.7.6 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and deflecting party, CD successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party and the deflecting party and performs the Communication Diversion Service CD. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Forwarding user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Deflecting user has subscribed to CDIV Communication Deflection (CD) Originating party and deflecting party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw) INVITE1 INVITE2 180 Ringing 302 Moved Temporarily ACK INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 71 TSS CUG/Services/CDIV TP CUG_N12_017 CUG reference clause 4.6.7.6 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and forwarded-to party, CD successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the deflecting party and the deflected-to party (CD) and the communication to the deflected-to party is successful. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Deflecting user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Deflected-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and deflecting party are in the same CUG Originating party and deflected-to party are in the same CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (Gm) INVITE1 INVITE2 180 Ringing 302 Moved Temporarily ACK INVITE3 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 72 TSS CUG/Services/CDIV TP CUG_N12_018 CUG reference clause 4.6.7.6 Selection expression PICS 4.7.1/8 Test purpose CUG with OA not allowed: Call setup between originating party and deflected-to party, CD unsuccessful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the originating party, the deflecting party and the deflected-to party (CD) and the communication to the deflected-to party is unsuccessful. The SUT rejects the INVITE request by sending a 403 Forbidden due to not matched CUG data. Preconditions: Originating user has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Deflecting user has subscribed to CUG Options for public identity in use: Incoming access: not allowed deflected-to user has subscribed to CUG Options for public identity in use: Incoming access: not allowed Originating party and deflecting party are in the same CUG Originating party and deflected-to party are in different CUG SIP header values: INVITE1: <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) INVITE1 INVITE2 180 Ringing 302 Moved Temporarily ACK 403 Forbidden ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 73 |
5882237be8e6c3816c60b16792fa1330 | 101 597-2 | 5.3.3 Explicit Communication Transfer (ECT) | TSS CUG/Services/ECT TP CUG_N13_001 CUG reference clause 4.6.7.10 Selection expression PICS 4.7.1/9 Test purpose CUG with OA not allowed: Communication transfer - transferor and transferee in the same CUG, successful. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the transferor and the transferee. The communication is successful Preconditions: Transferor has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferee has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferor and transferee are in the same CUG SIP header values: INVITE: Request Line <conference URI> <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) INVITE INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 74 TSS CUG/Services/ECT TP CUG_N13_001 CUG reference clause 4.6.7.10 Selection expression PICS 4.7.1/9 Test purpose CUG with OA not allowed: Call Communication transfer transferee and transfer target in the same CUG, successful blind transfer. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the transferee and the transfer target and performs the Communication transfer Service (Blind transfer). Preconditions: Transferor has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferee has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferor and transferee are in the same CUG SIP header values: INVITE1: Request Line <conference URI> <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw) A communication between transferor and transferee already exits REFER 202 Accepted BYE 200 OK (BYE) INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 75 TSS CUG/Services/ECT TP CUG_N13_001 CUG reference clause 4.6.7.10 Selection expression PICS 4.7.1/9 Test purpose CUG with OA not allowed: Call Communication transfer transferee and transfer target in the same CUG, successful assured transfer. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the transferee and the transfer target and performs the Communication transfer Service (assured transfer). Preconditions: Transferor has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferee has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferor and transferee are in the same CUG SIP header values: INVITE1: Request Line <conference URI> <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw) A communication between transferor and transferee already exits REFER 202 Accepted INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 76 TSS CUG/Services/ECT TP CUG_N13_001 CUG reference clause 4.6.7.10 Selection expression PICS 4.7.1/9 Test purpose CUG with OA not allowed: Call Communication transfer transferee and transfer target in the same CUG, successful consultative transfer. Ensure that on receipt of an INVITE request containing an xml element cug with cugCallOperation containing registered CUGIndex, the SUT checks the CUG restrictions for the transferee and the transfer target and performs the Communication transfer Service (assured transfer). Preconditions: Transferor has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferee has subscribed to CUG Options for registered and preferred CUG index: Intra CUG restrictions: None designated (-OCB) Options for public identity in use: Preferential CUG: None designated Outgoing access: not allowed Transferor and transferee are in the same CUG SIP header values: INVITE1: Request Line <conference URI> <cug> <cugCallOperation> <outgoingAccessRequest>FALSE</outgoingAccessRequest> <cugIndex>[registered CUG index]</cugIndex> </cugCallOperation> </cug> Comments: Test equipment (Gm) AS Test equipment (Gm) Test equipment (ISC, Mw) A communication between transferor and transferee already exits A communication between transferor and transfer target already exits REFER 202 Accepted INVITE1 INVITE2 ETSI ETSI TS 101 597-2 V1.1.1 (2013-07) 77 History Document history V1.1.1 July 2013 Publication |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 1 Scope | The present document provides the Implementation Conformance Statement (ICS) proforma for the Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem defined in Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [2]. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-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 referenced 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. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 654: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification (3GPP TS 24. Release 10) ". [2] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [3] ISO/IEC 9646-1: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements". |
df032bfa28c1891d3701f3a069f221a7 | 101 597-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. [i.1] ETSI TS 124 605: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 Release 10)". [i.2] ETSI TS 124 604: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 Release 10)". [i.3] ETSI TS 124 629: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.629 Release 10)". ETSI ETSI TS 101 597-1 V1.1.1 (2013-07) 6 [i.4] ETSI TS 124 611 "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.611 Release 10)". |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 3 Definitions and abbreviations | |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 654 [1], ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply. ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes an ICS Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system claimed to conform to a given specification, stating which capabilities have been implemented NOTE: The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, API ICS, etc. Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification NOTE: This may contain additional information. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 654 [1] and the following apply: ICS Implementation Conformance Statement IUT Implementation Under Test PICS Protocol ICS SCS System Conformance Statement SUT System Under Test |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4 PICS proforma for TS 124 654 | 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. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.1 Guidance for completing the PICS proforma | |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.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 TS 124 654 [1] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of information: • guidance for completing the PICS proforma; • identification of the implementation; • identification of the TS 124 654 [1]; ETSI ETSI TS 101 597-1 V1.1.1 (2013-07) 7 • global statement of conformance; • roles; • user role: - major capabilities; • network role. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.1.2 Abbreviations and conventions | The PICS proforma contained in this clause is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [4]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". Status column The following notations, defined in ISO/IEC 9646-7 [4], are used for the status column: m mandatory - the capability is required to be supported. o optional - the capability may be supported or not. n/a not applicable - in the given context, it is impossible to use the capability. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies an unique group of related optional items and the logic of their selection which is defined immediately following the table. Reference column The reference column makes reference to TS 124 654 [1], except where explicitly stated otherwise. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [4], are used for the support column: Y or y supported by the implementation. N or n not supported by the implementation. N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). References to items For each possible item answer (answer in the support column) within the PICS proforma a unique reference exists, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. If there is more than one support column in a table, the columns are discriminated by letters (a, b, etc.), respectively. EXAMPLE 1: 4.5/4 is the reference to the answer of item 4 in table 4.5 of clause 4. ETSI ETSI TS 101 597-1 V1.1.1 (2013-07) 8 EXAMPLE 2: 4.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in table 4.6 of clause 4. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.1.3 Instructions for completing the PICS proforma | The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause 4.1.2. If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately. More detailed instructions are given at the beginning of the different clauses of the PICS proforma. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2 Identification of the implementation | Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person. |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.1 Date of the statement | ......................................................................................................................................................................................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... IUT version: ......................................................................................................................................................................................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.3 System Under Test (SUT) identification | SUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Operating system: ......................................................................................................................................................................................... ETSI ETSI TS 101 597-1 V1.1.1 (2013-07) 9 |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.4 Product supplier | Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.5 Client (if different from product supplier) | Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 101 597-1 V1.1.1 (2013-07) 10 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.