hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f112baf3880993acab42075b5abfe996 | 186 005-2 | 4.1 Configuration | The scope of the current specification is to test the signalling and procedural aspects of the stage 3 requirements as described in TS 183 008 [3]. The stage 3 description describes the requirements for several network entities and also the requirements regarding for terminal devices. Therefore several interfaces (refe... |
f112baf3880993acab42075b5abfe996 | 186 005-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... |
f112baf3880993acab42075b5abfe996 | 186 005-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. User Equipment Implementation under Test Test System Gm Figure 4: Applicable configuration to test UE functionalities |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 4.1.3 Testing of the IBCF | The IBCF is the separation point between trusted and entrusted IMS networks and can be tested with the test configuration in figure 5. Figure 5: Applicable configuration to test IBCF 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) inter... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5 Test Purposes (TP) | |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.1 Introduction | For each test requirement a TP is defined. All PICS items referred to in this clause are as specified in TS 186 005-1 [8] unless indicated otherwise by another numbered reference. |
f112baf3880993acab42075b5abfe996 | 186 005-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... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.2 User TPs for TIP | |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.2.1 Terminating user equipment | Selection expression for group U01: PICS 1/2. TSS User/TermUserE TP TIP_U01_001 TIP/TIR reference 4.5.2.12 Selection expression PICS 2/6, 1/2 Test purpose: The Terminating UE supports the "from-change" tag in the Supported header. Ensure that the Terminating UE supports the "from-change" tag in the Supported header. If... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.2.2 Originating user equipment | Selection expression for group U01: PICS 1/1 and 2/1. ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 12 TSS User/OrigUserE TP TIP_U02_001 TIP/TIR reference 4.5.2.1 Selection expression PICS 1/1 Test purpose: The originating UE receives one P-Asserted-Identity in a sip URI. Ensure that the Originating UE, receiving any non 100... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.3 Network entity TPs for TIP | |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.3.1 Requirements on the AS serving the terminating UE | TSS Network entity/DestAS TP TIP_N01_001 TIP/TIR reference 4.5.2.9 Selection expression Test purpose: The AS inserts the Privacy id value in the response if the response does not contain any Privacy. The terminating user subscribes to TIR in permanent mode. Ensure that the IUT acting as AS serving the terminating user ... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.3.2 Requirements on the AS serving the originating UE | TSS Signalling/OrigNetw TP TIP_N02_001 TIP/TIR reference 4.3.2 Selection expression Test purpose: The originating user subscribes to the TIP service. Ensure that for originating users that subscribe to TIP simulation service, if network provided identity information about the terminator is available, and if presentatio... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.3.3 Communication diversion services | TSS Network entity/CDIV TP TIP_N03_001 TIP/TIR reference 4.6.7 Selection expression Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed t... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 5.3.4 Requirements on the interconnection with other IP network | TSS Network entity/OtherNetw TP TIP_N04_001 TIP/TIR reference 4.7.3 Selection expression Test purpose: Interworking with a trusted network; SUT is call destination Ensure that a SIP response defined as SIP_MESSAGE_VA including P-Asserted-Identity header fields for a request from a trusted network is received; the outgo... |
f112baf3880993acab42075b5abfe996 | 186 005-2 | 6 Compliance | An ATS which complies with the present document shall: a) consist of a set of test cases corresponding to the set or to a subset of the TPs specified in clause 5; b) use a TSS which is an appropriate subset of the whole of the TSS specified in clause 4; c) use the same naming conventions for the test groups and test ca... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 1 Scope | The present document specifies the Protocol implementation conformance statement (PICS) for the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) NGN Basic Service, TS 183 008 [10]. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Pr... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-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. • ... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-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 181 002: "Telecommunications and Internet con... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-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. |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 3 Definitions and abbreviations | |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 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 [12]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [12]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [12]. implicit send event: Refer to ISO/IEC 9646-3 [13]. lower tester: ... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS Application Server CLIP Calling Line Identification Presentation CLIR Calling Line Identification Restriction IP Internet Protocol ISDN Integrated Service Data Network IUT Implementaion Under Test n/a not applicable NGN Next Generation Netw... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-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. |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-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 [10] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of ... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-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 [14]. 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... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-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 ... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.2.1 Date of the statement | Date of the statement: |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.3 PICS proforma tables | |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? ETSI ETSI TS 186 005-1 V2.1.1 (2009-02) 10 |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.3.2 Roles and network capabilities | Table 1: Roles and network capabilities Item Item description Reference Status Support 1 Is the implementation an originating user equipment? 4.5.2.1/ [10] o 2 Is the terminating user a terminating user equipment? 4.5.2.12/ [10] o 3 Is the implementation connected with a trusted network? 4.5.2.7, 4.5.2.8/ [10] o 4 Is t... |
8aabeb8f451991c8be3dd27eacf2cd2f | 186 005-1 | 4.3.3 TIP/TIR user capabilities | Table 2: TIP/TIR user capabilities Item Item description Reference Status Support 1 Does the originating user subscribe the TIP service? 4.3.1.1/ [10] o 2 Does the terminating user subscribe the TIR service in permanent mode? 4.3.1.2/ [10] o 3 Does the terminating user subscribe the TIR service in temporary mode with d... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Testsuite Structure and Testpurposes defined in TS 186 002-3 [1]. The TSS&TP have been developed to test the interworking between Session Initiation Protocol (SIP)... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 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... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. NOTE: References have been used both in the present document and in the TTCN-3 library modules (annex B). [1] ETSI TS 186 002-3: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 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] IETF RFC 3398: "Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping". ETSI ETSI TS 186 002-5 V1.1... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 3 Definitions and abbreviations | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 3.1 Definitions | For the purposes of the present document, definitions from the following list of documents apply: • terms defined in SIP / ISUP interworking reference specification [5]; • terms defined in ISDN User Part (ISUP) reference specification [14] to [17]; • terms defined in ISO/IEC 9646-1 [11] and ISO/IEC 9646-7 [12]; and • t... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations given in Table 2/Q.762 of ITU-T Recommendation Q.762 [15] (ISUP messages) and the following apply: NOTE: Abbreviations have been used both in the present document and in the TTCN-3 library modules (annex B). ACM Address Complete Message ANM Answer Me... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4 Abstract Test Method (ATM) | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.1 Network architecture | Figures 1 and 2 show the network architecture for SIP-ISUP/BICC Interworking Units. Figure 1 shows the network architecture for SIP-ISUP Interworking. SIP ISUP <-----------------------------------------> IWU <------------------------------------------> Figure 1: Interworking between SIP and ISUP Figure 2 shows the netw... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.2 Protocol architecture | Figures 1 and 2 above show that there are 2 interfaces of the IWU (representing the SUT in the testing environment described in the present document): • a SIP interface; and • an ISUP- or BICC interface. Since the ISUP and BICC protocols are very similar (the latter one being derived from ISUP), they are treated here a... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3 Test architecture | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.1 Interconnection of TS and SUT | Figure 4 shows the interconnection of TS and SUT in terms of signalling message flows. SIP SUT ISUP/ BICC <------------------------> <------------------------> IWU <------------------------> ATM bearer control (only for BICC) Test System Figure 4: Interconnection of TS and SUT |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.2 Test system architecture | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.2.1 General | Test systems that implement this ATS shall conform to the requirements as defined in this clause. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 11 |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.2.2 Structure | An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 5 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 (... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.2.3.1 Control of the SUT Adapter (SA) by using ASPs | Table 1 lists the ASPs used in the SIP-ISUP-Interworking ATS. Detailed descriptions of the ASPs together with their parameters follow. Table 1: List of ASPs ASP Name Short description InitializeIsupBicc_req Initialize ISUP/BICC part of the test system. InitializeIsupBicc_cnf Answer whether all necessary ISUP/BICC test ... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.2.3.2 Sending and receiving SIP and ISUP/BICC messages | 4.3.2.3.2.1 General Before starting a test case, the SA shall be prepared to provide the transport of SIP and ISUP/BICC messages by establishing appropriate connections on the lower layers (see figure 3). 4.3.2.3.2.2 Encoding/Decoding System requirements 4.3.2.3.2.2.1 Encoding/Decoding System requirements for SIP The E... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 4.3.2.3.3 Logging conventions | As the ATS defines on an abstract level the message exchange between TS and SUT the messages encoded messages send and received shall be logged. The TM entity in the TS shall provide access to this log. |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5 The ATS development process | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 6 of TS 186 002-3 [1]. The requirements applicable to this TP are given by a reference to RFC 3261 [18] (SIP) and ITU-T Recommendation Q.1912.5 [5] or EN 383 001 [4] (ISUP). There are no explicit formulations of requirements. |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.2 ATS structure | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.2.1 Test case grouping | The ATS structure defined in table 14 is based on the structuring of Test Purposes in clause 5 of TS 186 002-3 [1]. The group names in columns 1 to 3 of table 14 are those assigned in the ATS; they are based on the names provided in clause 5 of TS 186 002-3 [1], but use the naming conventions defined for the ATS (see c... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 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 3-digit (or 4-digit) number in column 4 of Table 14 (which uniquely identifies the path of groups/subgroups); d) <TC numb... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.3 ATS specification framework | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.3.1 ATS Library | For this interworking ATS there are 2 applicable base protocols: a) SIP protocol (RFC 3261 [18]); and b) ISUP protocol (ITU-T Recommendation Q.76n series [14] to [17], plus associated standards for supplementary services, etc.). Since e.g. the data structures of these 2 base protocols are independent, and other objects... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.3.2 Use of TTCN-3 | |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.3.2.1 General | TTCN-3 as defined in ES 201 873-1 [8] 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/ISUP Interworking ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 s... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 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/ISUP Interworking ATS are based on the f... |
03fb2efc5f0db5f52156dfc26e091ac7 | 186 002-5 | 5.4 ATS archive | Annex B contains the ATS archive (.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 26 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 ... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 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 002-2 [1]. The TSS&TP have been developed to test the interworking between Session Initiation Protocol (SI... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 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... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 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. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 6 [1] ETSI TS 186... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 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] ITU-T Recommendation Q.931: "ISDN user-network i... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 3 Definitions and abbreviations | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 3.1 Definitions | For the purposes of the present document, the terms and definitions are given in: • SIP/ISUP interworking reference specification defined in EN 383 001 [4]; • ISDN layer 3 reference specification defined in EN 300 356-1 [21]; • ISDN User Part (ISUP) reference specification defined in EN 300 356-1 [21]; • ISO/IEC 9646-1... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: NOTE: The ISUP message acronyms can be found in table 2/Q.762 in ITU-T Recommendation Q.762 [15]. ASP Abstract Service Primitive NOTE: Exchanged between entities inside the TS or between the user of the ATS (operator) and the TS. ATC Abstract ... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4 Abstract Test Method (ATM) | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.1 Network architecture | Figures 1 and 2 show the network architecture for SIP-ISUP/BICC Interworking Units. Figure 1 shows the network architecture for SIP-ISUP Interworking. SIP ISUP <-----------------------------------------> IWU <------------------------------------------> Figure 1: Interworking between SIP and ISUP Figure 2 shows the netw... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.2 Protocol architecture | Figures 1 and 2 show that there are 2 interfaces of the IWU (representing the SUT in the testing environment described in the present document): a SIP interface and an ISUP- or BICC interface. Since the ISUP and BICC protocols are very similar (the latter one being derived from ISUP), they are treated here as one proto... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3 Test architecture | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.1 Interconnection of TS and SUT | Figure 4 shows the interconnection of TS and SUT in terms of signalling message flows. SIP SUT ISUP/ BICC <------------------------> <------------------------> IWU <------------------------> ATM bearer control (only for BICC) Test System Figure 4: Interconnection of TS and SUT |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.2 Test system architecture | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.2.1 General | Test systems that implement this ATS shall conform to the requirements as defined in this clause. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 11 |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.2.2 Structure | An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 5 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 (... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.2.3.1 Control of the SUT Adapter (SA) by using ASPs | Table 1 lists the ASPs used in the SIP-ISUP-Interworking ATS. Detailed descriptions of the ASPs together with their parameters follow. Table 1: List of ASPs ASP Name Short description InitializeIsupBicc_req Initialize ISUP/BICC part of the test system. InitializeIsupBicc_cnf Answer whether all necessary ISUP/BICC test ... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.2.3.2 Sending and receiving SIP and ISUP/BICC messages | 4.3.2.3.2.1 General Before starting a test case, the SA shall be prepared to provide the transport of SIP and ISUP/BICC messages by establishing appropriate connections on the lower layers (see figure 3). 4.3.2.3.2.2 Encoding/Decoding System requirements 4.3.2.3.2.2.1 Encoding/Decoding System requirements for SIP The E... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 4.3.2.3.3 Logging conventions | As the ATS defines on an abstract level the message exchange between TS and SUT the messages encoded messages send and received shall be logged. The TM entity in the TS shall provide access to this log. |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5 The ATS development process | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 6 of TS 186 002-2 [1]. The requirements applicable to this TP are given by a reference to RFC 3261 [18] (SIP) and ITU-T Recommendation Q.1912.5 [5] or ES 283 027 [20] (ISUP). There are no explicit formulations of requirements. NOTE 1: During the ATS development c... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.2 ATS structure | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.2.1 Test case grouping | The ATS structure defined in table 15 is based on the structuring of Test Purposes in clause 5 of TS 186 002-2 [1]. The group names in columns 1 to 3 of table 15 are those assigned in the ATS; they are based on the names provided in clause 5 of TS 186 002-2 [1], but use the naming conventions defined for the ATS (see c... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 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 3-digit number in column 4 of table 15 (which uniquely identifies the path of groups/subgroups); d) <TC number> is a runn... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.3 ATS specification framework | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.3.1 ATS Library | For this interworking ATS there are 2 applicable base protocols: a) SIP protocol (RFC 3261 [18]); and b) ISUP protocol (ITU-T Recommendation Q.76n series [14] to [17], plus associated standards for supplementary services, etc.). Since e.g. the data structures of these 2 base protocols are independent, and other objects... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.3.2 Use of TTCN-3 | |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.3.2.1 General | TTCN-3 as defined in ES 201 873-1 [8] 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/ISUP Interworking ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 s... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 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/ISUP Interworking ATS are based on the f... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.3.2.3 TTCN-3 comment tags | Any TTCN-3 definition in the Test Suite Repository or Library should contain embedded comment tags. These comment tags can be used by tools to extract information from the TTCN-3 code to create, for example, a HTML-based reference documentation. Comment tags which cover one or more lines should be specified using block... |
70d91ba4c372209e0fdbdfec9f2931bb | 186 002-4 | 5.4 ATS archive | Annex B contains the ATS archive (.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 28 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 ... |
574bdb176b57d4ef38a2d306f32039b2 | 186 007-2 | 1 Scope | The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) of the Communication HOLD service, based on stage one and two of the ISDN HOLD supplementary services. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information f... |
574bdb176b57d4ef38a2d306f32039b2 | 186 007-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.