hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.5 Supplementary Services OIR and ACR with AS | Interoperability Test Description Identifier: TD_IMS_SS_0005 Summary: IMS network supports properly application services based on the example of the OIR and ACR supplementary services Configuration: CF_INT_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5108_03 TS 124 229 [1], clause 5.4... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.6 Supplementary Services OIR and ACR with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0006 Summary: IMS network supports properly application services based on the example of the OIR and ACR supplementary services Configuration: CF_ROAM_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.7 Supplementary Service CFU with AS | Interoperability Test Description Identifier: TD_IMS_SS_0007 Summary: IMS network supports properly application services based on the example of the CFU supplementary service Configuration: CF_INT_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.8 Supplementary Service CFU with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0008 Summary: IMS network supports properly application services based on the example of the CFU supplementary service Configuration: CF_ROAM_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ¶... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.9 Supplementary Services OIP and OIR with AS | Interoperability Test Description Identifier: TD_IMS_SS_0009 Summary: IMS network supports properly application services based on the example of the OIP and OIR supplementary services Configuration: CF_INT_AS SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5097_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.10 Supplementary Services OIP and OIR with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0010 Summary: IMS network supports properly application services based on the example of the OIP and OIR supplementary services Configuration: CF_ROAM_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.11 Ad-hoc Conference Call service | Interoperability Test Description Identifier: TD_IMS_CONF_0001 Summary: IMS network handles subsequent INVITEs, UPDATEs, REFERs and NOTIFYs correctly during Ad-Hoc Conference calls Configuration: CF_INT_CONF_CALL SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5121_02 TS 124 229 [1], clause 5.4.3.3 ¶... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.6 Presence | The test descriptions for the presence service are defined in TS 102 901 [17]. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7 IPTV | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.1 IPTV registration and Service Attachment. Push mode | Interoperability Test Description Identifier: TD_IMS_IPTV_0001 Summary: IMS network supports properly IPTV registration and service attachment in Push mode Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5206_01 TS 124 229 [1], clause 5.4.1.2.2 F ¶15 (before NOTE 3) TP_IMS_5308... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.2 IPTV registration and Service Attachment. Pull mode. | Interoperability Test Description Identifier: TD_IMS_IPTV_0002 Summary: IMS network supports properly IPTV registration and service attachment in Pull mode Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5097_14 TS 124 229 [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.3 BC session | Interoperability Test Description Identifier: TD_IMS_IPTV_0003 Summary: IMS network supports properly IPTV Broadcast session Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5108_03 TS 124 229 [1], clause 5.4.3.2 ¶5 (item 4 in 1st numbered list) TP_IMS_5107_02 TS 124 229 [1], cl... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.7.6 Request for Network PVR offline capture in home network | Interoperability Test Description Identifier: TD_IMS_IPTV_0006 Summary: IMS network supports properly N-PVR offline capture requests Configuration: CF_IPTV SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5108_04 TS 124 229 [1], clause 5.4.3.3 ¶5 (item 4 in 1st numbered list) Use Case ref.: UC_22 Pre-... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8 IMS-PSTN Interoperability | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1 IMS-to-PSTN call | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.1 ENUM Query - IMS-to-PSTN call | Interoperability Test Description Identifier: TD_IMS_ENUM_0002 Summary: ENUM query should result in return of NAPTR with correct Tel URI Configuration: CF_INT_CALL SUT: ENUM _A and ENUM_DB References: Test Purpose Specification Reference TP_IMS_ENUM_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 10 in 1st numbered list) U... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.2 Normal Call, PSTN user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0001 Summary: Outgoing call to PSTN, PSTN user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_02 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_03 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_06 ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.3 Normal Call, IMS user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0002 Summary: Outgoing call to PSTN, IMS user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_02 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_03 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_06 T... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.4 Unsuccessful Call, PSTN user busy | Interoperability Test Description Identifier: TD_IMS_PSTN_0003 Summary: Outgoing call to PSTN, user B busy Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_02 TS 124 229 [1], clause 5.5.3.1.2 TP_IMS_MGCF_09 TS 129 163 [18], clause 7.2.3.1.8 Use Case ref.: UC_23 Pre... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.5 IMS user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0004 Summary: Outgoing call to PSTN, communication hold by IMS user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_11 TS 129 163 [18], clause 7.4.10.1 TP_IMS_MGCF_12 TS 129 163 [18], clause 7.4.10.1 Use Ca... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.1.6 PSTN user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0005 Summary: Outgoing call to PSTN, communication hold by PSTN user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_13 TS 129 163 [18], clause 7.4.10.2 TP_IMS_MGCF_14 TS 129 163 [18], clause 7.4.10.2 Use C... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2 PSTN-to-IMS call | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.1 Normal Call, PSTN user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0006 Summary: Incoming call from PSTN, PSTN user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_01 TS 124 229 [1], clause 5.5.3.1.1 TP_IMS_MGCF_05 TS 124 229 [1], clause 5.5.3.2,1 TP_IMS_MGCF_1... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.2 Normal Call, IMS user clears call | Interoperability Test Description Identifier: TD_IMS_PSTN_0007 Summary: Incoming call from PSTN, IMS user clears call Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_01 TS 124 229 [1], clause 5.5.3.1.1 TP_IMS_MGCF_05 TS 124 229 [1], clause 5.5.3.2,1 TP_IMS_MGCF_15... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.3 Unsuccessful Call, IMS user busy | Interoperability Test Description Identifier: TD_IMS_PSTN_0008 Summary: Incoming call from PSTN, user A busy Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_01 TS 124 229 [1], clause 5.5.3.1.1 TP_IMS_MGCF_10 TS 129 163 [18], clause 7.2.3.2.12 Use Case ref.: UC_24 ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.4 IMS user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0009 Summary: Incoming call from PSTN, communication hold by IMS user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_11 TS 129 163 [18], clause 7.4.10.1 TP_IMS_MGCF_12 TS 129 163 [18], clause 7.4.10.1 Use ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.8.2.5 PSTN user holds/resumes call | Interoperability Test Description Identifier: TD_IMS_PSTN_0010 Summary: Incoming call from PSTN, communication hold by PSTN user Configuration: CF_PSTN SUT: IMS_A and MGCF References: Test Purpose Specification Reference TP_IMS_MGCF_13 TS 129 163 [18], clause 7.4.10.2 TP_IMS_MGCF_14 TS 129 163 [18], clause 7.4.10.2 Use... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 1 Scope | The present document specifies interoperability Test Purposes (TPs) for IMS NNI interworking based on the IP Multimedia Call Control Protocol based on Stage 3 Session Initiation Protocol (SIP) and Session Description Protocol (SDP) standard, TS 124 229 [1]. TPs are defined using the TPLan notation also described in ES ... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 229 (V9.5.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and S... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ACK (positive) ACKnowledgement ACM Address Complete Message AKA Authentication and Key Agreement ANM Answer Message AS (IMS) Application Server ATS Abstract Test Suite CF (Test) Configuration CN Core Net... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 4 Test Suite Structure (TSS) | The Test Suite Structure is based on a Requirements Catalogue which was established prior to test purpose specification. This RC extracts all requirements from [1] which are relevant to the scope of this work. The TSS is defined by the groups within the following TPLan specification of test purposes. The numbering is n... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5 Test Purposes (TP) | The test purposes have been written in the notation TPLan [4] which has been developed at ETSI to express test purposes in a more formal manner. All TPLan TPs have been converted into a symbolic tabular presentation format which is shown in this clause. TPs in the standardized textual TPLan syntax are collected in arch... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.1 The tabular symbolic TPLan presentation format | Each table contains header fields and a description part. The header fields identify the TP, list the related clause reference the base specification that the TP was derived from, introduce the TP with a short summary, references the related test configuration and test case in the ATS. The description part presents the... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.2 General Capabilities | Test Purpose Identifier: TP_IMS_4002_01 Summary: IMS CN components shall support SIP messages > 1 300 bytes IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 4.2A ¶1 Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in IMS B UE A IMS A IMS B UE B... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3 Registration Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.1 Registration at P-CSCF | Test Purpose Identifier: TP_IMS_5005_01 Summary: The P-CSCF shall support the Path header IUT Role: IMS A References: TS 124 229 (V9.5.0), [1] clause 5.2.1 ¶8 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ IMS B has challenged with a 401 response the REGISTER request of UE B IMS A IMS B UE B Step Direc... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.2 Registration at S-CSCF | Test Purpose Identifier: TP_IMS_5088_01 Summary: S-CSCF shall deregister unexpired registration upon receipt of a new REGISTER with new contact information IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.1.2.1 ¶7 (item 2 in 1st numbered list) Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.3 Registration at I-CSCF | Interoperability Test Purpose Identifier: TP_IMS_5129_01 Summary: If a request is received from a non-trusted domain, a 403 (Forbidden) response shall be returned by I-CSCF IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.3.1.2 ¶1 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ ✓ user of UE B... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.3.4 Registration at IBCF | Interoperability Test Purpose Identifier: TP_IMS_5134_01 Summary: If a request includes a Path header the IBCF shall add the routeable SIP URI of an IBCF to the top of the Path header IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.4.1 ¶5 Config Ref: CF_ROAM_REG Entities Condition IMS A IMS B UE B ✓ IM... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4 Dialog Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.1 Dialog at P-CSCF | Test Purpose Identifier: TP_IMS_5046_01 Summary: When the P-CSCF receives an initial INVITE request for a dialog from a UE for which a Service- Route header list exists without topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.3 ¶1 (1st numbered list) Config Ref: CF_ROAM_CALL Entities ... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.2 Dialog at S-CSCF | Test Purpose Identifier: TP_IMS_5097_01 Summary: S-CSCF must inserts orig-ioi parameter, remove access-network-charging-info parameter and P- Access-Network-Info header before sending initial INVITE or a initial request over NNI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (1st numbered list)... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.3 Dialog at I-CSCF | Test Purpose Identifier: TP_IMS_5131_01 Summary: I-CSCF shall remove P-Charging-Function-Addresses header from 180 response to initial request IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.3.2.1 ¶62 (after note 11) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A registered in I... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.4.4 Dialog at IBCF | Test Purpose Identifier: TP_IMS_5135_01 Summary: If a request includes a Record-Route header the IBCF shall add its own routeable SIP URI to the top of the Record-Route header IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.10.4.1 ¶7 (after note 4) Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.5 Messaging Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.5.1 Messaging at P-CSCF | Test Purpose Identifier: TP_IMS_5050_01 Summary: When the P-CSCF receives a MESSAGE request from a UE for which a Service-Route header list exists without topology hiding IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.2.6.3.3 ¶(1st numbered list) Config Ref: CF_ROAM_CALL Entities Condition UE A IMS A IMS... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.5.2 Messaging at S-CSCF | Test Purpose Identifier: TP_IMS_5097_05 Summary: S-CSCF must inserts orig-ioi parameter, remove access-network-charging-info parameter before sending MESSAGE over NNI IUT Role: IMS A References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶1 Config Ref: CF_INT_CALL Entities Condition UE A IMS A IMS B UE B ✓ ✓ UE A register... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.6 Application Server Handling Procedures | |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.6.1 Application Server Handling at S-CSCF | Test Purpose Identifier: TP_IMS_5097_09 Summary: Initial request for a dialog handling by S-CSCF with matching filter criteria AS IUT Role: IMS B References: TS 124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (items 5 and 8 in 1st numbered list ) Config Ref: CF_ROAM_AS Entities Condition UE A IMS A IMS B AS B UE B ✓ ✓ UE A re... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.7 MGCF tests for IMS-PSTN interconnection | Test Purpose Identifier: TP_IMS_MGCF_01 Summary: MGCF shall send INVITE due to indication of an incoming call Clause: TS 124 229 [1], clause 5.5.3.1.1 References: RQ_24.229_5.5.3.1.1 Config Ref: CF_PSTN IUT Role: MGCF Test Case: TC_IMS_MGCF_01 Entities Condition IMS_A IUT PSTN ✓ ✓ IMS A and PSTN with peer-to-peer arran... |
174a17c8b5525d2a7ec906b188573d7c | 186 011-1 | 5.8 ENUM tests for Tel-URI Resolution | Test Purpose Identifier: TP_IMS_ENUM_01 Summary: The ENUM DB resolves a Tel URI into a SIP URI IUT Role: IMS A References: TS124 229 (V9.5.0) [1], clause 5.4.3.2 ¶11 (item 10 1st numbered list) Config Ref: CF_INT_CALL Entities Condition UE A IMS A ENUM _DB IMS B UE B ✓ ✓ UE A registered in IMS A ✓ ✓ UE B registered in ... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 1 Scope | The present document specifies the Protocol implementation conformance statement (PICS) for the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. Within the Next Generation Network (NGN) the stage 3 is specified using the IP Multimedia Call Control Protocol based on Session In... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 005: "Telecommunications and Internet con... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 186 010-2 V2.1.1 (2009-07... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 3 Definitions and abbreviations | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] apply. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] apply. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 4 Test Suite Structure (TSS) and configuration | Table 1: Test suite structure ConferenceFocus CONF_N01_xxx CONF_N02_xxx CONF_N03_xxx CONF_N04_xxx CONF_N05_xxx CONF_N06_xxx CONF_N07_xxx UserEquipment CONF_U01_xxx Interaction TIR CONF_N08_xxx OIR CONF_N09_xxx ACR CONF_N10_xxx |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 4.1 Configuration | The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as described in [1]. The stage 3 description respects the requirements to several network entities and also to requirements regarding to end devices. Therefore several interfaces (reference points) are address... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5 Test Purposes (TP) | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.1 Introduction | For each test requirement a TP is defined. |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 2). Table 2: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = s... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.1.2 Test strategy | As the base standard TS 183 005 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 186 010-1 [2]. ETSI ETSI TS 186 010-2 V2.1.1 (2009-07) 8 |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2 Signalling requirements | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1 Conference Focus | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.1 Conference creation | TSS ConferenceFocus TP CONF_N01_001 Reference 5.3.2.3/ [3] Selection expression Test purpose Conference creation with a conference factory URI. Conference event package subscribed. Ensure that a conference can be created by a UE using the conference factory URI. The "isfocus" feature parameter indicated in Contact head... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.2 Joining a conference | TSS ConferenceFocus TP CONF_N02_001 Reference 5.3.2.4/[3] Selection expression NOT PICS 1/6 Test purpose Participant dial-in the conference, the conference URI is used. ISC#1 established a conference. ISC#2 joins in that conference after has been received a REFER request and the Refer-To header referring to the Focus. ... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.3 Inviting other users to a conference | TSS ConferenceFocus TP CONF_N03_001 Reference 5.3.1.5.3/[3] Selection expression NOT PICS 1/6 Test purpose Inviting participant by sending REFER to the focus. ISC#1 established a conference. ISC#1 invites ISC#2 to join into the conference. The ISC#1 sends a REFER to the focus; the focus sends an INVITE request to ISC#2... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.4 Leaving a conference | TSS ConferenceFocus TP CONF_N04_001 Reference 5.3.2.6/[3] Selection expression PICS 1/6 Test purpose A participant leaves the conference. ISC#2 wishes to leave the conference by sending a BYE request to the focus in accordance to the basic call procedures. SIP header values: REFER 1: Request line=Focus Refer-To=ISC#2 P... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.5 Removing a conference participant from a conference | TSS ConferenceFocus TP CONF_N05_001 Reference 5.3.2.6/[3] Selection expression Test purpose A participant asks the Conference AS to remove a other participant from the conference. The conference AS verify the identity of the user and authorize the request. A participant is not authorized to remove another participant f... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.1.6 Conference termination | TSS ConferenceFocus TP CONF_N06_001 Reference 5.3.2.7/[3] Selection expression Test purpose The conference owner releases the entire conference by sending a BYE to the focus. SIP#1, the conference owner, sends a BYE request to the focus. The entire conference is released. SIP header values: BYE: Request URI = conferenc... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.2 Conference Notification Service | TSS ConferenceFocus TP CONF_N07_001 Reference 5.3.3/[3] Selection expression Test purpose Conference creation, notification service. Ensure that the notification procedure for the conference creation can be performed. The UE, creates the conference subscribes the notification service by sending a SUBSCRIBE. SIP header ... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.2.3 Actions at the UE | TSS UserEquipment TP CONF_U01_001 Reference 5.3.1/[3] Selection expression Test purpose Conference creation by Three-way session creation. REFER request to the Focus, Conference notification service is subscribed. The conference participant is participating in two SIP sessions and wants to join together two of these ac... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.3 Interaction with other supplementary services | |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.3.1 Terminating Identification Restriction (TIR) | TSS Interaction/TIR TP CONF_N08_001 Reference 4.6.3/[3] Selection expression Test purpose Privacy according TIR in the conference notification info send in the INFO request to the conference creator. Ensure the no identity is sent to the conference creator if a Privacy header was received and the privacy vale was set t... |
40c2d32598e77728c3ce47d803f09a6f | 186 010-2 | 5.3.2 Originating Identification Restriction (OIR) | TSS TP CONF_N09_001 Reference 4.6.5/[3] Selection expression Test purpose Conference creator subscribes to OIR: The There is no identity of the creator included in the conference notification. Ensure that the conference notification sent in the NOTIFY request after the participant was join to the conference if the conf... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 1 Scope | The present document specifies the Protocol implementation conformance statement (PICS) for the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. Within the Next Generation Network (NGN) the stage 3 is specified using the IP Multimedia Call Control Protocol based on Session In... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 005 (Release 2): "Telecommunications and ... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ISO/IEC 9646-7: "Information technology; Open Sy... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 3 Definitions and abbreviations | |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] apply. |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] apply. 4 Protocol Implementation Conformance Statement (PICS) proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.1 Instructions for completing the PICS proforma | 4.1.1 More detailed instructions are given at the beginning of the different subclauses of the PICS proforma. The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5. |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.1.1.1 Purposes and structure | The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in specifications [1] and [2] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into subclauses for the following categories of informa... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.1.2 Abbreviations and conventions | The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [3]. Item column: It contains a number that identifies the item in the table. Item description column: It describes each respective item (e.g. parameters, timers, etc.). Reference column: It gives ... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-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 ... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.2.1 Date of the statement | Table 1 Date of the statement: |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.2.2 Implementation Under Test (IUT) identification | Table 2 IUT name: IUT version: ETSI ETSI TS 186 010-1 V2.1.1 (2009-07) 8 |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.2.3 System Under Test (SUT) identification | Table 3 SUT name: Hardware configuration: Operating system: |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.2.4 Product supplier | Table 4 Name: Address: Telephone number: Facsimile number: Additional information: |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.2.5 Client | Table 5 Name: Address: Telephone number: Facsimile number: Additional information: |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.2.6 PICS contact person | Table 6 Name: Telephone number: Facsimile number: Additional information: ETSI ETSI TS 186 010-1 V2.1.1 (2009-07) 9 |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.3 PICS proforma tables | |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.3.1 Global statement of conformance | Table 7 (Yes/No) Are all mandatory capabilities implemented? |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 4.3.2 Terminal and network capabilities | Table 8: Network capabilities Item Item description Reference Status Support 1 Is the conference notification service is implemented? 5.3.3 [2] o 2 It is possible to invite a participant using a REFER request? 5.3.2.5.2 [2] o 3 Is the use of preconditions supported? 5.3.2.3.1, 4) [2] o 4 Does the network support the Or... |
9325cad390eacc60bf1dc18e7cb15d3e | 186 010-1 | 5 Additional information for PICS | If necessary, the supplier may provide additional comments in this clause. ETSI ETSI TS 186 010-1 V2.1.1 (2009-07) 10 History Document history V2.1.1 July 2009 Publication |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.