hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 ... |
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 ... |
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... |
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 ... |
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 con... |
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... |
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-Reques... |
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 Charg... |
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 contain... |
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 U... |
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 rule... |
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 ... |
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... |
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-Requ... |
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, s... |
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 A... |
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... |
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 establis... |
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 U... |
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... |
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 AV... |
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 profor... |
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 a... |
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 Specif... |
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 Repl... |
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... |
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 poi... |
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 ... |
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:... |
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> = s... |
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... |
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 C... |
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 con... |
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 cugCallO... |
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 cugCallO... |
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 containin... |
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 cugCallOperati... |
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 cugCallOperati... |
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 reques... |
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 cont... |
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 ... |
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 40... |
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, th... |
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 ... |
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 contai... |
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 acco... |
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 a... |
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 Specif... |
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) usi... |
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 (I... |
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: • guidanc... |
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 ... |
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 b... |
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 ... |
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: ......................................................................................................................................................................................... ............................................................................................................................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.3 System Under Test (SUT) identification | SUT name: ......................................................................................................................................................................................... ............................................................................................................................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.4 Product supplier | Name: ......................................................................................................................................................................................... Address: .......................................................................................................................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.5 Client (if different from product supplier) | Name: ......................................................................................................................................................................................... Address: .......................................................................................................................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.2.6 PICS contact person | (A person to contact if there are any queries concerning the content of the PICS) Name: ......................................................................................................................................................................................... Telephone number: ............................... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.3 Identification of the TS 124 654 | This PICS proforma applies to the following standard: TS 124 654 [1]: 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)". |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.4 Global statement of conformance | Are all mandatory capabilities implemented? (Yes/No) ..................... NOTE: Answering "No" to this question indicates non-conformance to the <reference specification type> specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conf... |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.5 Roles | Table 4.5.1: Roles Item Role Reference Status Support 1 User 1.3 o.1 2 Network 1.2 o.1 o.1: It is mandatory to support exactly one of these items. Comments: |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.6 User role | This clause contains the PICS proforma tables related to the user role. They need to be completed only for user implementations: Prerequisite: 4.5.1/1 -- user role |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.6.1 Major capabilities | Table 4.6.1: Call directions Item Call direction Reference Status Support 1 The user equipment supports the "cug" XML schema? 4.5.2.1 4.4.1 o 2 The user equipment is able to send the 'cugCallOperation' element without the 'cugIndex' sub element 4.5.2.1 4.4.1 c4611 c4611: IF x.4.6.1/1 THEN o ELSE n/a. Comments: |
df032bfa28c1891d3701f3a069f221a7 | 101 597-1 | 4.7 Network role | This clause contains the PICS proforma tables related to the network role. They need to be completed only for Application Server implementations: Prerequisite: 4.5.1/2 network role ETSI ETSI TS 101 597-1 V1.1.1 (2013-07) 12 Table 4.7.1: Network capabilities Item Item description Reference Status Support 1 Is the CUG wi... |
c98c8c16b30ad1284cf64a54f8c7b3ea | 101 596-2 | 1 Scope | The present document provides the Test suite structure and test purposes for the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification (based on TS 124 608 (3GPP Release 10) [1]). |
c98c8c16b30ad1284cf64a54f8c7b3ea | 101 596-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 a... |
c98c8c16b30ad1284cf64a54f8c7b3ea | 101 596-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 608: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR... |
c98c8c16b30ad1284cf64a54f8c7b3ea | 101 596-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. |
c98c8c16b30ad1284cf64a54f8c7b3ea | 101 596-2 | 3 Definitions, symbols and abbreviations |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.