hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1f1ab48bf07a660f0e3392826799d4d9 | 186 018-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... |
1f1ab48bf07a660f0e3392826799d4d9 | 186 018-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... |
1f1ab48bf07a660f0e3392826799d4d9 | 186 018-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... |
1f1ab48bf07a660f0e3392826799d4d9 | 186 018-3 | 5.3.2.4 Additional concepts and conventions | IMS procedures and tests require 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 paramete... |
1f1ab48bf07a660f0e3392826799d4d9 | 186 018-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. |
1f1ab48bf07a660f0e3392826799d4d9 | 186 018-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... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 1 Scope | The present document specifies the test suite structure and test purposes of the Malicious Communication Identification (MCID) service based on the stage three of IMS MCID simulation service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol base... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-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... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-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 016: "Telecommunications and Internet con... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-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. [i.1] IETF RFC 3966: "The tel URI for Telephone Number... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 3 Definitions and abbreviations | |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 181 002 [3], TS 181 006 [4], TR 180 000 [5] and the following apply: communication information: information collected and registered by the MCID service identity information: includes all the information (RFC 3966 [i.1] // RFC 3986 [i.2]) i... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACM Address Complete Message ANM Answer Message AS Application Server CDIV Communication DIVersion services HOLD communication HOLD IAM Initial Address Message IDR Identification Request message IM IP Multimedia IMS IP Multimedia Subsystem IP ... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 4 Test Suite Structure (TSS) | MCID terminating_S-CSCF MCID_N01_xxx terminating_AS MCID_N02_xxx destination_UE MCID_U01_xxx SIP-ISUP SS MCID TP507xxx ISUP-SIP SS MCID TP614xxx |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5 Test Purposes (TP) | |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.1 Introduction | For each test requirement a TP is defined. |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-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... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.1.2 Test strategy | As the base standard TS 183 016 [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 018-1 [2]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered. ETSI... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.2 TPs for Malicious Communication Identification (MCID) | |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.2.1 Actions at the terminating S-CSCF | TSS MCID/terminating_S-CSCF TP MCID_N01_001 SUB reference clause 4.5.2 Selection expression PICS 1/3 Test purpose Called user has permanent MCID subscription Ensure that the S-CSCF forwards the INVITE request to the AS if the called subscriber has a permanent MCID subscription. Preconditions: SIP header values: Comment... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.2.2 Actions at the AS of the terminating user | TSS MCID/terminating_AS TP MCID_N02_001 SUB reference clause 4.5.2 Selection expression PICS 1/9 Test purpose The AS requests identification information in an INFO request, if no identification was received in the initial INVITE. Ensure that the AS sends an INFO request including a XML mcid request McidRequestIndicator... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.2.3 Actions at the destination UE | TSS MCID/destination_UE TP MCID_U01_001 SUB reference clause 4.5.2 Selection expression NOT PICS 1/1 Test purpose The UE sends a MCID request Ensure that the UE is able to invoke MCID. The UE sends a reINVITE without session modification. Preconditions: SIP header values: reINVITE without session modification Comments:... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.3 Interaction with other services | |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.3.1 Communication Diversion Services (CDIV) | It is not possible to test MCID in case of CDIV. ETSI ETSI TS 186 018-2 V1.0.0 (2008-06) 14 |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.4 Test purposes for the ISUP/SIP Interworking | |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.4.1 Interworking at the I-MGCF | TP507001 Reference: ES 283 027 [6], clause 7.4.4 Selection criteria: NOT PICS 1/6 TSS reference: SIP-ISUP/SS/MCID/ Preconditions: Test purpose: No interworking MGCF sends IRS Ensure that the SUT if an IDR is received returns an IRS message. The MCID response indicator is set to "MCID not included". The SIP signalling p... |
86ee5808f5cc5965b2c7d7b47202895b | 186 018-2 | 5.4.2 Interworking at the O-MGCF | TP614001 MCID Reference: 4.7.1.2 Selection criteria: PICS 1/6 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of XML mcid request (McidRequestIndicator) Ensure that the XML mcid McidRequestIndicator contained in a received INFO request mapped into the MCID request indicator requested in the sent I... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 1 Scope | The present document specifies the protocol implementation conformance statement of the Malicious Call Communication Identification (MCID) service based on the stage IMS Malicious Communication Identification simulation service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP ... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-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... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-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 016: "Telecommunications and Internet con... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-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. |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 3 Definitions and abbreviations | |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 181 002 [2], TS 181 006 [3], TR 180 000 [4] and the following apply: communication information: information collected and registered by the MCID service identity information: includes all the information (RFC 3966 [6] // RFC 3986 [7]) ident... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS Application server HOLD communication HOLD IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Digital Network IUT Implementation Under Test MCID Malicious Call Identification MGCF Media Gateway Control Function NGN Nex... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-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. |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-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 specifications [1] to [7] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of i... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.1.2 Abbreviations and conventions | The PICS proforma is composed of an information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [5]. 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 ... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-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 ... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.2.1 Date of the statement | Date of the statement: |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 9 |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.3 PICS proforma tables | |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 10 |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 4.3.2 Roles and network capabilities | Table 1: Roles and network capabilities Item Item description Reference Status Support 1 [UE] Is the invocation of the MCID service provided? 4.5.2.12.1 o 2 [UE] Is the invocation of the MCID service using the XML MIME body mcid provided? 4.5.2.12.1 o 3 Is the MCID service in permanent case provided? 4.5.2.5 o1 4 Is th... |
14acadeac50f478346a0fb8fb6f3e11f | 186 018-1 | 5 Additional information for PICS | ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 11 History Document history V1.0.0 June 2008 Publication |
ca7429b61f8f4fee76a132269f558127 | 186 017-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 017-2 [3]. The TSS&TP have been developed to test the Anonymous Communication Rejection (ACR) and Communic... |
ca7429b61f8f4fee76a132269f558127 | 186 017-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... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 183 011: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Pr... |
ca7429b61f8f4fee76a132269f558127 | 186 017-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. [i.1] ETSI EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework". [i.2] ETSI TS 102... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 3 Definitions and abbreviations | |
ca7429b61f8f4fee76a132269f558127 | 186 017-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 [i.2] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [5]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [5]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5]. Implementation Un... |
ca7429b61f8f4fee76a132269f558127 | 186 017-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] and the following apply: NOTE: Abbreviations have been used both in the present document and in the TTCN-3 library modules (see annex B). ACR Anonymous Communication Rejection AS Application Server ATM Abstract T... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4 Abstract Test Method (ATM) | |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.1 Network architecture | The SUT is assumed as a complete IMS core network and contains the following components: P-CSCF, I/S-CSCF, E-CSCF and IBCF. As illustrated in figure the PCOs for the communication between the systems are Gm, Mw, Ic and Isc. Each component can play role of SUT. Figure 1: SUT test interface AS IMSx IMSy UE IMS Mw Ic Isc ... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.2 Protocol architecture | The Implementation Under Test (IUT) for which this test case specification applies consists of the SIP protocol (see figure 2). SUT IMS CN SIP/IMS Extension SIP RFC 3261 Compression algorithms (2) UDP TCP Security Algorithms (2) IPV4/IPV6 (1) (LAN) Figure 2: SIP protocol architecture |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3 Test architecture | The target SUT to be covered by the test purposes of TS 186 017-2 [3] address the IMS functional entities that are accessible via the following interfaces: Gm, Mw, Ic and ISC. This clause introduces the test configurations that have been used for the test purpose definitions. Depending on the specific configuration the... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.1 Test configuration | |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.1.1 Configuration using Gm interface | The Gm interface is located between UE and IMS. UE1 SUT IMS P gm ue1home PCSCFwithHomeUE UE1 SUT IMS P gm ue1home PCSCFwithHomeUE Figure 3: Test configuration with CF_1Ue ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 11 IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome IMS SUT UE1 P UE3 gm ue1home ue3home gm ... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.1.2 Configuration using ISC interface | The ISC interface provides an access to the AS. AS SUT IMS S isc AS ue1home SCSCFwithHomeUE AS SUT IMS S isc AS ue1home SCSCFwithHomeUE Figure 5: Test configuration with CF_1Scscf AS IMS SUT S isc P AS ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome AS IMS SUT S isc P AS ue1home ue2home UE1 UE2 gm gm UE1atSUTho... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.1.3 Configuration using Mw and Ic interfaces | The Mw or Ic interface is located between two different IMS, e.g. due to at least one user visiting a network outside of the home network. IMS SUT mw IMS TS B UE uehome IBCFwithHomeUE IMS TS I UE uehome ICSCFwithHomeUE ic IMS SUT mw IMS TS B UE uehome IBCFwithHomeUE IMS TS I UE uehome ICSCFwithHomeUE ic Figure 7: Test ... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2 Test system architecture | |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.1 General | Test systems that implement this ATS shall conform to the requirements as defined in this clause. |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.2 Structure | An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 8 and also stated in ES 201 873-5 [9]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) | |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.3.1 Sending and receiving SIP/IMS messages | Before starting a test case, the SA shall provide the transport of SIP messages by establishing appropriate connections on the lower layers (shown in figure 2). ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 13 In order to forward messages received in the SA to the test suite and to send them to the SUT a clear and unique ass... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.3.2 Security & messages compression feature | Security transport layer and signalling compression may be used transparently to the ATS. |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.3.3 Additional SA constraints | In order to execute this test suite the SA should support: • communication channel handling (at least UDP and possibly also TCP); • IPv4 transport. |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.4 Encoding/Decoding requirements | |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers | SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use an EDS to parse received encoded messages into TTCN-3 type structures and values and encode structured TTCN-3 type structures and values into encoded messages. This ... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 4.3.2.5 Platform adaptation requirements | For the execution of this test suite implementations of the following external functions have to be provided (see module LibSip_Steps): 1) rndStr() return charstring; returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case; ETSI ETSI TS 186 01... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 5 The ATS development process | |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 186 017-2 [3]. The requirements applicable to this TP are given by a reference to RFC 3261 [4] (SIP), or TS 183 011 [1]. There are no explicit formulations of requirements. |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 5.2 ATS structure | |
ca7429b61f8f4fee76a132269f558127 | 186 017-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 017-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 017-2 [3], but use the naming conventions defined for the ATS (see clause 5.... |
ca7429b61f8f4fee76a132269f558127 | 186 017-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 ... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 5.3 ATS specification framework | |
ca7429b61f8f4fee76a132269f558127 | 186 017-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 [14], TS 186 017-2 [3] and TS 186 018-2 [15]. 2) LibIms modules. 3) LibSip modules (see RFC 3261 [4]). 4) LibCommon modules (taken from an improved versio... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 5.3.2 Use of TTCN-3 | |
ca7429b61f8f4fee76a132269f558127 | 186 017-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... |
ca7429b61f8f4fee76a132269f558127 | 186 017-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... |
ca7429b61f8f4fee76a132269f558127 | 186 017-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... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 5.3.2.4 Additional concepts and conventions | IMS procedures and tests require 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 paramete... |
ca7429b61f8f4fee76a132269f558127 | 186 017-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. |
ca7429b61f8f4fee76a132269f558127 | 186 017-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... |
ca7429b61f8f4fee76a132269f558127 | 186 017-3 | 5.4 ATS archive | Annex B contains the ATS archive (ts_18601703v020201p0.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 21 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of ... |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 1 Scope | The present document specifies the test suite structure and test purposes of the Anonymous Communication Rejection (ACR) and Communication Barring (CB) simulation service, based on stage three of the IMS simulation service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing Communication B... |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-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... |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-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 011: "Telecommunications and Internet con... |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-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. [i.1] ETSI TS 186 017-1: "Telecommunications and Inter... |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 3 Definitions and abbreviations | |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 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. |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement ACR Anonymous Communication Rejection AS Application Server CB Communication Barring CDIV Communication DIVersion services HOLD communication HOLD ICB Incoming Communication Barring IMS IP Multimedia Subsystem IP Internet P... |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 4 Test Suite Structure (TSS) | ACR-CB ACR_terminating_AS ACR-CB_N01_xxx OBC_originating_AS ACR-CB_N02_xxx IBC_terminating_AS ACR-CB_N03_xxx interaction_OIP ACR-CB_N04_xxx interaction_CDIV ACR-CB_N05_xxx ISUP-SIP SS ACR TP612xxx SIP-ISUP SS ACR TP515xxx |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 5 Test Purposes (TP) | |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 5.1 Introduction | For each test requirement a TP is defined. |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-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... |
3852cdf8f3ce3706df1c4c2e3b23c25f | 186 017-2 | 5.1.2 Test strategy | As the base standard TS 183 011 [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 017-1 [i.1]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered. ET... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.