hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5 The ATS development process | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 186 016-2 [3]. The requirements applicable to this TP are given by a reference to RFC 3261 [4] (SIP), or ES 183 054 [1]. There are no explicit formulations of requirements. |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.2 ATS structure | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.2.1 Test case grouping | The ATS structure defined in table 2 is based on the structuring of Test Purposes in clause 4 of TS 186 016-2 [3]. The group names in column 2 of table 2 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 016-2 [3], but use the naming conventions defined for the ATS (see clause 5.... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.2.2 Test case identifiers | The test case names are built up according to the following scheme: <"TC">"_"<Group index>"_"<TC number> where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in column 4 of table 2 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running ... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3 ATS specification framework | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.1 ATS Library | For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules – project includes test cases from documents TS 186 005-2 [13], TS 186 016-2 [3], TS 186 017-2 [14] and TS 186 018-2 [15]; 2) LibIms modules; 3) LibSip modules (RFC 3261 [4]); 4) LibCommon modules (taken from an improved version of... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.2 Use of TTCN-3 | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.2.1 General | TTCN-3 as defined in ES 201 873-1 [7] is used as ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the SIP IMS ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and namin... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.2.2 TTCN-3 naming conventions | Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. The naming conventions applied to the SIP/IMS ATS are based on the following under... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.2.3 Additional TTCN-3 IMS/SIP naming convention | In addition to the general TTCN-3 naming conventions listed in the previous clause the following rules have been applied to templates Table 5: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Message template Use lower-case initial letter, followed by message type in upper-case letters ... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.2.4 Additional concepts and conventions | IMS procedures and tests requires the inclusion of user identification and network address information in SIP messages. Since this information depends on the specific SUT at hand it is defined using module parameters. Due to the big amount of such parameters a profile concept have been introduced for particular paramet... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.2.5 PICS information | No TTCN-3 control part has been defined for this test suite. If applicable PICS information is evaluated at the beginning of each test case definition using an "if" statement. Log information is provided in case that a test has not been executed due to PICS setting violation. |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.3.2.6 Test Suite documentation | In order to allow browsing of the SIP/IMS ATS without the use of a specific TTCN-3 test development environment, the TTCN ATS is made available in HTML format with hyperlinks between entities in the ATS. The documentation in the ATS makes use of special comment tags used by the tool that converts the ATS to the HTML fo... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 5.4 ATS archive | Annex B contains the ATS archive (ts_18601603v020201p0.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 20 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of the p... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 1 Scope | The present document specifies the test suite structure and test purposes of the Closed User Group (CUG) service, based on stage three of the IMS closed user group (CUG) simulation services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP-Multimedia Call Control Protocol based... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 054: "Telecommunications and Internet con... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 016-2 V2.2.1 (2009-07... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 3 Definitions and abbreviations | |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 181 002 [3] and the following apply: escaped character: See RFC 3261 [4]. NOTE: This may contain additional information. |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS Application Server CUG Closed User Group ICB Incoming Communication Barring within a CUG IMS IP Multimedia Subsystem IP Internet Protocol NGN Next Generation Network OAE Outgoing Access, explicit request required OAI Outgoing Access, implic... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 183 054 [1]. The stage 3 description describes the requirements for several network entities and also the requirements regarding terminal devices. Therefore several interfaces (reference poi... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 2: 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, Mg, Mx) interface (see f... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 has been chosen. ETSI ETSI TS 186 016-2 V2.2.1 (2009-07) 8 User Equipment Implementation under Test Test System Gm Figure 4: Applicable ... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 5 Test Purposes (TP) | |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 5.1 Introduction | For each test requirement a TP is defined. |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 5.1.2 Test strategy | As the base standard TS 183 054 [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 016-1 [2]. The criteria applied include the following: • Whether or not a test case can be built from the TP is not considered. ETSI... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 5.2 Test Purposes for Closed User Group (CUG) | |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 5.2.1 TPs at the originating UA | TSS CUG/originating_UE TP CUG_U01_001 CUG reference clause 4.5.2.1 Selection expression Test purpose Explicit request of CUG service. 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... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 5.2.2 Test Purposes at the Application Server of the originating User | In clauses 5.2.2.1 through to 5.2.2.6 the originating user is member of one closed user group which is not assigned as preferential. In the following test purposes the CUG index of this closed user group is referred to as "registered CUGIndex". In clause 5.2.2.4 through to 5.2.2.6 the originating user is also member of... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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 CU... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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 r... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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 r... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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 registe... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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 registe... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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 registered CUGIndex, rejects the INVITE request by s... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-2 | 5.2.3 Actions at the AS of the terminating User | |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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 elemen... |
433ee6bcb33f8457a4d52f8ac89add14 | 186 016-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 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. ... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 1 Scope | The present document specifies the protocol implementation conformance statement of the Closed User Group (CUG) service, based on stage three of the IMS closed user group (CUG) simulation services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP-Multimedia Call Control Protoco... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-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... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-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 054: "Telecommunications and Internet con... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-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. Not applicable. ETSI ETSI TS 186 016-1 V2.1.1 (2009-02... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 3 Definitions and abbreviations | |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 181 002 [2] and the following apply: escaped character: See RFC 3261 [3]. NOTE: This may contain additional information. |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement CUG Closed User Group HOLD communication HOLD IFC Initial Filter Criteria IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Data Network IUT Implementation Under Test MCID Malicious Communication IDen... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.1 Instructions for completing the PICS proforma | 4.1.1 More detailed instructions are given at the beginning of the different clauses 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. ETSI ETSI TS 186 016-1 V2.1.1 (... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-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 reference specification [1] to [3] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of in... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-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 [4]. 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 ref... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-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 ... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.2.1 Date of the statement | Date of the statement: |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: ETSI ETSI TS 186 016-1 V2.1.1 (2009-02) 9 |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.3 PICS proforma tables | |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 4.3.2 Network capabilities | Table 1: Network capabilities Item Item description Reference Status Support 1 Is the CUG without preference supported? 4.5.2.4 o1 2 Is the CUG Outgoing access, explicit request required without preference supported? 4.5.2.4 o1 3 Is the CUG Outgoing access, implicit outgoing access for all communications without prefer... |
4a9aaef052a3100fd2237ad8b123c1c1 | 186 016-1 | 5 Additional information for PICS | ETSI ETSI TS 186 016-1 V2.1.1 (2009-02) 10 History Document history V2.1.1 February 2009 Publication |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 1 Scope | The present document specifies the protocol implementation conformance statement of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service, based on stage three of the IMS simulation services. Within the Next Generation Network (NGN) the stage 3... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-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... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-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 042 (V2.1.1): "Telecommunications and Int... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-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. Not applicable. ETSI ETSI TS 186 021-1 V2.1.1 (2009-07... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 3 Definitions and abbreviations | |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] apply. |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] and the following apply: IUT Implementation Under Test. SUT System Under Test 4 Protocol Implementation Conformance Statement proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants ... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.1 Instructions for completing the PICS proforma | 4.1.1 More detailed instructions are given at the beginning of the different clauses 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. |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-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 reference specification [1] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of informati... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-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 [2]: Item column It contains a number that identifies the item in the table. ETSI ETSI TS 186 021-1 V2.1.1 (2009-07) 7 Item description column It describes each respective item (e.g. parameters, ti... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-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 ... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.2.1 Date of the statement | Date of the statement: ETSI ETSI TS 186 021-1 V2.1.1 (2009-07) 8 |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: ETSI ETSI TS 186 021-1 V2.1.1 (2009-07) 9 |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.3 PICS proforma tables | |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 4.3.2 Network capabilities | Table 1: Network capabilities Item Item description Reference Status Support 1 Is the CCBS/CCNR request retention option supported? 4.5.4.2.3.2.4/[1] o 2 Is the retain option supported? 4.5.4.3.4.2/[1] o 3 Is it possible to activate a further CCBS or CCNR request for an identical communication, determined by the stored... |
c77f98f4316a16eb3ad7082d8f1aac6b | 186 021-1 | 5 Additional informations for PICS | If necessary, the supplier may provide additional comments in this clause. ETSI ETSI TS 186 021-1 V2.1.1 (2009-07) 10 History Document history V2.1.1 July 2009 Publication |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 010-2 [2]. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specific... |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 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... |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 605: "Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS); Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GP... |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 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. |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 3 Definitions and abbreviations | |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [6], TS 102 587-2 [9] and TS 102 790-3 [3] apply. |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-7 [6], TS 102 790-3 [3] and TS 124 605 [1] apply. |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 4 Abstract Test Method (ATM) | For the purposes of the present document, the ATM described in clause 4 of TS 102 790-3 [3] applies with following additions. |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 4.1 Configurations for testing UE | The Gm interface is located between SUT (UE) and the IMS. SUT TS UE IMS Gm Figure 1: Test configuration CF_1GmUE ETSI ETSI TS 186 010-3 V3.1.1 (2012-01) 7 The ISC interface provides an access to the AS. SUT IMS AS ISC TS Figure 2: Test configuration CF_1ISC |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5 The ATS development process | |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 186 010-2 [2]. The requirements applicable to this TP are given by a reference to TS 124 605 [1]. There are no explicit formulations of requirements. |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.1.1 Untestable test purposes | The test cases CONF_N01_003 and CONF_N01_004 could not be implemented with the test methodology in use. |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.2 ATS structure | |
eb958be9a7659cc0b89e6468deb3c359 | 186 010-3 | 5.2.1 Test case grouping | The ATS structure defined in Table 1 is based on the structuring of Test Purposes in clause 4 of TS 186 010-2 [2]. The group names in column 2 of Table 1 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 010-2 [2], but use the naming conventions defined for the ATS (see clause 5.... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.