hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bd27bfecf4e216ed521ebf95e7320382 | 186 009-3 | 5.4 ATS archive | Annex B contains the ATS archive (.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 009-3 V2.1.1 (2009-09) 30 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 present document may ... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 1 Scope | The present document specifies the network PICS (Protocol Implementation Conformance Statement) of the Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part EN 283 027 [20]. The references [20] and [26] are identical. |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • ... |
91ce9dba04094521913bb9faf18082b2 | 186 009-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] ITU-T Recommendations Q.761 to Q.764 (2000): "Signall... |
91ce9dba04094521913bb9faf18082b2 | 186 009-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. |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 3 Definitions and abbreviations | |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Abstract Test Case (ATC): complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state a... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATC Abstract Test Case ATM Abstract Test Method ATS Abstract Test Suite BICC Bearer Independent Call Control protocol CIC Circuit Identification Code ICS Implementation Conformance Statement ISDN Integrated Services Digital Network ISUP ISDN U... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 4 Scenarios | 4.1 SIP Profile A and B for interworking between SIP and BICC/ISUP IP IP, ATM or TDM BICC or ISUP Profile scope SIP Proxy G/W Type 1 SIP Figure 1: Profile Scope for SIP Interworking with BICC/ISUP with a Type 1 Gateway ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 9 IP IP, ATM or TDM BICC or ISUP Profile scope SIP BICC CSF-T... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5 PICS proforma | |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.1 Instructions for completing the PICS proforma | |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.1.1 Other information | 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.4. ETSI ETSI TS 186 009-1 V2.1.1 (200... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.1.2 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 [25] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of i... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.1.3 Conventions | The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [8]. 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... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.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 ... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.2.1 Date of the statement | Date of the statement: |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 14 |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3 PICS proforma tables | |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? NOTE: Answering "No" to this question indicates non-conformance to the reference protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming. |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.2 Roles | Table 1: Roles Item Item description column Reference Status Support 1 The SUT is a SIP-I implementation? ITU-T RecommendationTRQ.2815 [18] o 2 connected with a BICC Network? ITU-T Recommendation Q.1902.2 [27] o.12 3 connected with a ISUP Network? ITU-T Recommendation Q.764 [1] o.12 4 Is the SUT connected with a µ-law ... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.3 Connection types | Table 2: Connection types Item Item description column Reference Status Support 1 The SUT support the media type "audio" and media format 0, 8? ES 283 027, clause 7.2.3.1.2.5 [20] o.21 2 The SUT support the media type "audio" and media format 9? ES 283 027, clause 7.2.3.1.2.5 [20] o.21 3 The SUT support the media type ... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.4 Forward address signalling | Table 3: Forward address signalling Item Item description column Reference Status Support 1 SIP use the en bloc operation in the forward address signalling (sending)? ES 283 027, clause 7.2.3.2.1 [20] o.31 2 SIP use the overlap operation in the forward address signalling (sending)? ES 283 027, clause 7.2.3.2.1a [20] o.... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.5 Role independent capabilities | Table 4: Role independent capabilities Item Item description column Reference Status Support 1 The SUT use the Continuity check procedures during call setup? ES 283 027 [20], clause 7.2.3.1.1 o 2 The SUT support the Continuity check procedures during call setup? ES 283 027 [20], clause 7.2.3.2.1 m 3 The SUT support hop... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.6 Supplementary Services Major Capabilities | Table 5: Supplementary Services Major Capabilities Item Item description column Reference in ITU-T Rec Q.1912.5 [10] Status Support 1 The SUT support the service Calling Line Identification Presentation (CLIP)? 7.4.1 m 2 The SUT support the service Calling Line Identification Restriction (CLIR)? 7.4.1 m 3 The SUT suppo... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.7 IMS simulation services | Table 13: Simulation services Item Item description column Reference Status Support 1 The SUT support the IMS simulation service Terminating Identificatio Presentatio/Restriction 7.5.2.3 [20] o 2 The SUT support the HOLD simulation service 4/ [22] o 3 The SUT support the ECT simulation service 4/ [23] o 4 The SUT suppo... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.3.8 Timers | Table 14: Timers Item Use of ... Reference Status Support Values in seconds allowed supported 1 Toiw1 7.2.3.3 [20] m 4 - 6 2 Toiw2 7.2.3.3 [20] m 4 - 14 3 Toiw3 7.2.3.3 [20] m 4 - 6 4 ISUP T6 Annex A of ITU-T Rec. Q.764 [1] o ITU-T Rec. Q.118 [17] 5 ISUP T7 Annex A of ITU-T Rec. Q.764 [1] o 20 - 30 6 ISUP T9 Annex A of... |
91ce9dba04094521913bb9faf18082b2 | 186 009-1 | 5.4 Additional information for PICS | This clause contains all additional comments provided by the supplier of the implementation (see clause 5.1.1). ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 21 Annex A (informative): Bibliography • ITU-T Recommendation Q.732.3 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. ... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 1 Scope | The present document contains the performance benchmark requirements applicable to IMS/PES/VoLTE exchange implementations based on Recommendation ITU-T Q.543 [1] and ETSI TS 101 563 [10]. The definitions of IMS/PES/VoLTE design objectives are based on "best practice" performance of legacy PSTN/ISDN signalling. The valu... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 2 References | |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 2.1 Normative 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... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 2.2 Informative 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. NOTE: While any hyperlinks in... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledgment AGCF Access Gateway Control Function CSCF Call Session Control Function ECM EPS Connection Management EPS Evolved Packet System IAD Integrated Access Device IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4 Metrics and design objectives | |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.1 Delay probability | This clause defines delay parameters related to ISDN/PSTN, IMS and VoLTE. The values are based on the values in Recommendation ITU-T Q.543 [1] and ETSI TS 101 563 [10]. |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.2 Loads definitions | The ISDN/PSTN, IMS and VoLTE reference loads definitions and values described in table 1 to table 9 are the reference loads definitions described in Recommendation ITU-T Q.543 [1] and in ETSI TS 101 563 [10]. The derived ISDN procedures are based on the ISDN/SIP interworking [2] procedures, the derived PES procedures a... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.3 Parameter requirements | IMS/VoLTE systems shall comply with the requirements given in tables 1 to 9. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 8 Table 1 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not ... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.4 Call processing performance objectives | |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.4.1 Premature release | The probability that an exchange malfunction will result in the premature release of an established connection in any one minute interval shall be: P ≤ 2 × 10-5 |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.4.2 Release failure | The probability that an exchange malfunction will prevent the required release of a connection shall be: P ≤ 2 × 10-5 |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.4.3 Incorrect charging or accounting | The probability of a call attempt receiving incorrect charging or accounting treatment due to an exchange malfunction shall be: P ≤ 10-4 |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.4.4 Misrouting | The probability of a call attempt misrouted following receipt by the exchange of a valid address shall be: P ≤ 10-4 |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.4.5 No tone | The probability of a call attempt encountering no tone following receipt of a valid address by the exchange shall be: P ≤ 10-4 |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.4.6 Other failures | The probability of the exchange causing a call failure for any other reason not identified specifically above shall be: P ≤ 10-4 |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.5 Transmission performance | |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.5.1 64 kbit/s switched connections | The probability of a connection being established with an unacceptable transmission quality across the exchange shall be: P ≤ 10-5 The transmission quality across the exchange is said to be unacceptable when the bit error ratio is above the alarm condition. NOTE: In Recommendation ITU-T G.826 [8], budgets of 18,5 % of ... |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.6 Slip rate | |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.6.1 Normal conditions | The slip rate under normal conditions is covered in Recommendation ITU-T Q.541 [5]. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 26 |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.6.2 Temporary loss of timing control | The case of temporary loss of timing control corresponds to the "holdover operation" defined and recommended in Recommendation ITU-T G.812 [6]. The allowable slip rate will correspond to the maximum relative TIE also recommended therein. |
78957ee0f55c0b3981b5ea170807e2f5 | 186 008-4 | 4.6.3 Abnormal conditions at the exchange input | The slip rate in case of abnormal conditions (wide phase deviations, etc.) at the exchange input is the subject of further study taking into account the requirements of Recommendation ITU-T G.823 [7]. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 27 Annex A (informative): Bibliography ETSI TS 186 008-1 (V1.2.2): "IMS Network... |
047bc52479713610812aa1b711044d22 | 186 005-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 005-2 [2]. The TSS&TP have been developed to test the Terminating Identification Presentation (TIP) and Te... |
047bc52479713610812aa1b711044d22 | 186 005-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... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 183 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identificatio... |
047bc52479713610812aa1b711044d22 | 186 005-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. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 7 |
047bc52479713610812aa1b711044d22 | 186 005-3 | 3 Definitions and abbreviations | |
047bc52479713610812aa1b711044d22 | 186 005-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [5], TS 102 587-2 [15] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [4]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [4]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [4]. Implementation Und... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [4], ISO/IEC 9646-7 [5] and the following apply: NOTE: Abbreviations have been used both in the present document and in the TTCN-3 library modules (see annex B). AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CDI... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4 Abstract Test Method (ATM) | |
047bc52479713610812aa1b711044d22 | 186 005-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 the following 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 |
047bc52479713610812aa1b711044d22 | 186 005-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). AS IMSx IMSy UE IMS Mw Ic Isc Gm SIP protocol ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 9 SUT IMS CN SIP/IMS Extension SIP RFC 3261 [3] Compression algorithms (2) UDP TCP Security Algorithms (2)... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3 Test architecture | The target SUT to be covered by the test purposes of TS 186 005-2 [2] 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 th... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3.1 Test configuration | |
047bc52479713610812aa1b711044d22 | 186 005-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 IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome Figure 4: Test co... |
047bc52479713610812aa1b711044d22 | 186 005-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... |
047bc52479713610812aa1b711044d22 | 186 005-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 ... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3.2 Test system architecture | |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3.2.1 General | Test systems that implement this ATS shall conform to the requirements as defined in this clause. |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3.2.2 Structure | An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 4 and also stated in ES 201 873-5 [8]. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 11 Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS)... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) | |
047bc52479713610812aa1b711044d22 | 186 005-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). In order to forward messages received in the SA to the test suite and to send them to the SUT a clear and unique association between the TTCN-3 TSI ports and t... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3.2.3.2 Security and messages compression feature | Security transport layer, and signalling compression may be used transparently to the ATS. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 13 |
047bc52479713610812aa1b711044d22 | 186 005-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. |
047bc52479713610812aa1b711044d22 | 186 005-3 | 4.3.2.4 Encoding/Decoding requirements | |
047bc52479713610812aa1b711044d22 | 186 005-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... |
047bc52479713610812aa1b711044d22 | 186 005-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; 3) getIpAddr(charst... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 5 The ATS development process | |
047bc52479713610812aa1b711044d22 | 186 005-3 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 186 005-2 [2]. The requirements applicable to this TP are given by a reference to RFC 3261 [3] (SIP), or TS 183 008 [1]. There are no explicit formulations of requirements. |
047bc52479713610812aa1b711044d22 | 186 005-3 | 5.2 ATS structure | |
047bc52479713610812aa1b711044d22 | 186 005-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 005-2 [2]. 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 005-2 [2], but use the naming conventions defined for the ATS (see clause 5.... |
047bc52479713610812aa1b711044d22 | 186 005-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 ... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 5.3 ATS specification framework | |
047bc52479713610812aa1b711044d22 | 186 005-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 [2], TS 186 016-2 [13], TS 186 017-2 [12] and TS 186 018-2 [14]. 2) LibIms modules. 3) LibSip modules (RFC 3261 [3]). 4) LibCommon modules (taken from an improved version of... |
047bc52479713610812aa1b711044d22 | 186 005-3 | 5.3.2 Use of TTCN-3 | |
047bc52479713610812aa1b711044d22 | 186 005-3 | 5.3.2.1 General | TTCN-3 as defined in ES 201 873-1 [6] 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... |
047bc52479713610812aa1b711044d22 | 186 005-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... |
047bc52479713610812aa1b711044d22 | 186 005-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... |
047bc52479713610812aa1b711044d22 | 186 005-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... |
047bc52479713610812aa1b711044d22 | 186 005-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. |
047bc52479713610812aa1b711044d22 | 186 005-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... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 1 Scope | The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) of the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) services. Within the TISPAN NGN Release 2 Next Generation Network (NGN) the TS 183 008 [3] Terminating Identification Presentation (TIP... |
f112baf3880993acab42075b5abfe996 | 186 005-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... |
f112baf3880993acab42075b5abfe996 | 186 005-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] IETF RFC 2396: "Uniform Resource Identifiers (URI): G... |
f112baf3880993acab42075b5abfe996 | 186 005-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 009-2: "Telecommunications and Inter... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 3 Definitions and abbreviations | |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: abstract test case: Refer to ISO/IEC 9646-1 [6]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [6]. address identity: See Recommendation E.164 or/and RFC 2806 [5]. call: See ITU-T Recommendation Q.9 [10], definition 2201. dialog: ... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CDIV Communication DIVersion CN Core Network CSCF Call Session Control Function IBCF Interconnection Border Control Function IM IP Multimedia IP Internet Protocol ISDN Inte... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 4 Test Suite Structure (TSS) | User TermUserE TIP_U01_xxx OrigUserE TIP_U02_xxx Network entity DestAS TIP_N01_xxx OrigAS TIP_N02_xxx CDIV TIP_N03_xxx OtherNetw TIP_N04_xxx Figure 1: Test suite structure |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.