hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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 the implementation connected with an untrusted network? 4.5.2.7, 4.5.2.8/ [10] o 5 Does the network insert the display-name in the P-Asserted-Identity RFC 3325 [6] o 6 Is the network able to divert a call? TS 183 004 [15] o 7 Does the network supports the “special arrangement” for the terminating user? 4.5.2.9 [10] o
|
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 default value "presentation not restricted"? 4.3.1.2/ [10] o 4 Does the terminating user subscribe the TIR service in temporary mode with default value "presentation restricted"? 4.3.1.2/ [10] o 5 Does the originating user subscribe the override category for the TIR service? 4.6.3/ [10] o 6 Does the user equipment supports the “from-change” tag in the Supported header? 4.5.2.12 [10] o 7 [2/6] Does the terminating user equipment send an UPDATE request if a “from-change” tag was received in the initial INVITE? 4.5.2.12 [10] o 8 The terminating user subscribes “special arrangement”? 4.5.2.9 [10] o Table 3: CDIV user capabilities Item Item description Reference Status Support 1 Does the served (forwarding/deflecting) user selects the option that the originating user is not notified of communication diversion? TS 183 004 [15] c31 2 Does the served (forwarding/deflecting) user selects the option that the originating user is notified, but without the diverted-to address? TS 183 004 [15] c31 c31: IF 1/6 THEN o ELSE n/a ETSI ETSI TS 186 005-1 V2.1.1 (2009-02) 11 History Document history V2.1.1 February 2009 Publication
|
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) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part, Profiles C. The ATS is sometimes referred to in the present document as 'SIP-ISUP-Interworking ATS'. The test notation used in the ATS is TTCN-3 (ES 201 873-1 [8]). The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (IXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS. NOTE: The current version of the document covers test purposes for SIP-I to ISUP and ISUP to SIP-I basic call and supplementary services only. ATS and PIXIT for ISDN-(ISUP)-SIP-I interworking defined in annex A of TS 186 002-3 [1] will be added in a later version of the present document.
|
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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
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); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP); Part 3: Test Suite Structure and Test Purposes (TSS&TP) for Profile C". ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 6 [2] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [3] ETSI TS 186 002-1 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP); Part 1: Protocol Implementation Conformance Statement (PICS)". [4] ETSI EN 383 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control (BICC) Protocol or ISDN User Part (ISUP) [ITU-T Recommendation Q.1912.5, modified]". [5] ITU-T Recommendation .1912.5 (2004): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part". [6] ITU-T Recommendation Q.2150.1 (2001): "Signalling Transport Converter on MTP3 and MTP3b". [7] ETSI TS 102 027-3 (V3.1.1): "Methods for Testing and Specification (MTS); Conformance Test Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma". [8] ETSI ES 201 873-1 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [9] ETSI ES 201 873-5 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)". [10] ETSI ES 201 873-6 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)". [11] ISO/IEC 9646-1 (1992): "Information Technology - Open Systems Interconnection - Conformance Testing Methodology and Framework - Part 1: General concepts". [12] ISO/IEC 9646-7 (1994): "Conformance testing methodology and framework - Part 7: Implementation Conformance Statement". [13] ITU-T Recommendation E.164 (2005): "The international public telecommunication numbering plan". [14] ITU-T Recommendation Q.761 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP); functional description". [15] ITU-T Recommendation Q.762 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP); general functions of messages and signals". [16] ITU-T Recommendation Q.763 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP); formats and codes". [17] ITU-T Recommendation Q.764 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP); signalling procedures". [18] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [19] IETF RFC 2617 (1999): "HTTP Authentication: Basic and Digest Access Authentication".
|
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.1 (2010-06) 7
|
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 • terms defined in ES 201 873-1 [8] (TTCN-3). In particular, 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 and ending in a stable testing state Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract test cases to be specified for this method Abstract Test Suite (ATS): test suite composed of abstract test cases Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider relationship, being part of a real open system which is to be studied by testing SIP number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [13] Means of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection, parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a conformance log PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes the PICS PIXIT proforma: document, in the form of a questionnaire, which when completed for the IUT becomes the PIXIT Point of Control and Observation: point within a testing environment where the occurrence of test events is to be controlled and observed, as defined in an Abstract Test Method pre-test condition: setting or state in the IUT which cannot be achieved by providing stimulus from the test environment Protocol Implementation Conformance Statement (PICS): statement made by the supplier of a protocol claimed to conform to a given specification, stating which capabilities have been implemented Protocol Implementation eXtra Information for Testing (PIXIT): statement made by a supplier or implementor of an IUT (protocol) which contains or references all of the information related to the IUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT System Under Test (SUT): real open system in which the IUT resides ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 8
|
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 Message ASP Abstract Service Primitive NOTE: Exchanged between entities inside the TS or between the user of the ATS (operator) and the TS. ATC Abstract Test Case ATM Abstract Test Method ATM Asynchronous Transfer Mode ATS Abstract Test Suite BCI Backward Call Indicators CIC Circuit Identification Code CON Connect message CPG Call Progress message CW Call Waiting DSS1 Digital Subscriber System No. 1 EDS Encoding/Decoding System ETS Executable Test Suite FCI Forward Call Indicators IAM Initial Address Message IETF Internet Engineering Task Force ISDN Integrated Services Digital Network ISUP ISDN User Part IUT Implementation Under Test IWU Interworking Unit LT Lower Tester MOT Means Of Testing MTP Message Transfer Part NCI Nature of Connection Indicators NGN Next Generation Network PA Platform Adapter PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing PTC Parallel Test Component REL Release message SA SUT Adapter SAM Subsequent Address Message SDP Session Description Protocol SIP Session Initiation Protocol SN Signalling Node STC Signalling Transport Converter NOTE According to ITU-T Recommendation Q.2150.1 [6]. SUT System Under Test TC Test Case TCI TTCN-3 Control Interface TCP Test Coordination Procedures TD Test Description TE Test Equipment TISPAN ETSI technical body with responsibility for NGN standardization TL Test Logging TM Test Management TMR Transmission Medium Requirement TP Test Purpose ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 9 TRI TTCN-3 Runtime Interface TS Test System TSS Test Suite Structure TSS&TP Test Suite Structure and Test Purposes TTCN Tree and Tabular Combined Notation TTCN-3 Testing and Test Control Notation edition 3
|
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 network architecture for SIP-BICC Interworking. SIP BICC <------------------------------------------> <-----------------------------------------> IWU <------------------------------------------> ATM bearer control Figure 2: Interworking between SIP and BICC NOTE: There are 3 profiles defined for IWU: Profile A, Profile B and Profile C. Figures 3 to 7 in clause 4 of TS 186 002-1 [3] shows the substructures of the IWU for Profiles C in terms of gateways and signalling nodes. In the ATS the SUT (IWU) represents either a G/W Type 3 or 4.
|
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 as one protocol. NOTE: No signalling is used within the SIP-ISUP-Interworking ATS to control the ATM bearer in case of BICC (ASPs are used). ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 10 Figure 3 shows the protocol architecture in 2 branches. SUT IUT IUT SIP ISUP BICC STC STC UDP TCP MTP 3 MTP 3b IP MTP Layer 2 AAL (LAN) G.703/G.704 ATM Figure 3: Protocol architecture of the SIP-ISUP-Interworking ATS
|
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 (SA) Platform Adapter (PA) Figure 5: Abstract Test System Architecture A TS has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and Platform Adapter (PA) entities, respectively. Out of these two interfaces the TRI has been standardized in ES 201 873-5 [9], whereas the specification and implementation of the TCI is in ES 201 873-6 [10]. The part of TS that deals with interpretation and execution of TTCN-3 modules, i.e. the Executable Test Suite (ETS), is shown as part of the TTCN-3 Executable (TE). This ETS corresponds either to the executable code produced by a TTCN-3 compiler or a TTCN-3 interpreter from the TTCN-3 ATS in a TS implementation. The remaining part of the TS, which deals with any aspects that cannot be concluded from information being present in the TTCN-3 ATS alone, can be decomposed into Test Management (TM), SUT Adapter (SA), and Platform Adapter (PA) entities. In general, these entities cover a TS user interface, test execution control, test event logging, communication of test data with the SUT, and timer implementation. The part of SA used for SIP message transfer shall implement the TRI adaptation as well as the SIP transport protocol architecture described in clause 4.2. The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, with the TE and Test Logging (TL) entity within the TM shall comply with the conventions defined in clause 4.3.2 of TS 102 027-3 [7]. The part of SA used for ISUP/BICC message transfer shall implement the TRI adaptation as well as the ISUP/BICC transport protocol architecture described in clause 4.2. For BICC, in addition, the ATM bearer control shall be implemented. The Encoding/Decoding System (EDS) entity, as far as applied to ISUP/BICC messages, shall comply with the conventions and requirements defined in the following clauses. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 12
|
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 system initializations have been successfully performed. ISUP_BICC_MSG_req Used to send an ISUP/BICC message. ISUP_BICC_MSG_ind Used to receive an ISUP/BICC message. BearerSetup_req For BICC: request TS to setup the bearer connection between TS and SUT. BearerSetup_acc For BICC: answer to BearerSetup_req. BearerSetup_ind For BICC: indication that the bearer has been setup. BearerRelease_req For BICC: request to release established bearer connection. BearerRelease_cnf For BICC: confirmation that the requested bearer is released. BearerRelease_ind For BICC: indication that the bearer has been released (when no BearerRelease_req has been issued before). s_IsupBicc_conversation Check that conversation is possible on the bearer. s_IsupBicc_ringing Check that ringing occurs. Tables 2 to 13 contain the descriptions of the ASPs used in the present document, including the ASP parameters (if any) and the types of values these may assume. No ASP parameter is optional. Table 2: ISUP_BICC_MSG_req ASP structure ASP Name: ISUP_BICC_MSG_req Port: sysPort Direction: TE -> SA Description: ASP used to send an ISUP/BICC message. Parameter Type Description isupBiccSelection SelectIsupOrBicc Selector used to distinguish between ISUP and BICC testing. '00000000'B means 'ISUP' and any other value means 'BICC'. serviceIndicatorOctet ServiceIndicatorOctet The contents of this ASP parameter is evaluated in SA only if ISUP has been selected in 'isupBiccSelection'. routingLabel RoutingLabel The contents of this ASP parameter is evaluated in SA only if ISUP has been selected in 'isupBiccSelection'. circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is evaluated in SA only if ISUP has been selected in 'isupBiccSelection'. callInstanceCode CallInstanceCode The contents of this ASP parameter is evaluated in SA only if BICC has been selected in 'isupBiccSelection'. iSUP_BICC_MSG ISUP_BICC_MSG ISUP_BICC_MSG is a union over all ISUP/BICC message body types, where a message body starts with the 'message type' field. This body is common for ISUP and BICC messages. When using this ASP, a particular message(body) template is selected from the union for transmission. Comments: The SA takes from the ASP, depending on the value of parameter 'isupBiccSelection', either the ordered combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (ISUP), or 'callInstanceCode' (BICC'), puts it in front of encoded parameter 'iSUP_BICC_MSG', and sends the so constructed message at the ISUP or BICC interface respectively. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 13 Table 3: ISUP_BICC_MSG_ind ASP structure ASP Name: ISUP_BICC_MSG_ind Port: sysPort Direction: SA -> TE Description: ASP used to receive an ISUP/BICC message. Parameter Type Description isupBiccSelection SelectIsupOrBicc Selector used to distinguish between ISUP and BICC testing. '00000000'B means 'ISUP' and any other value means 'BICC'. serviceIndicatorOctet ServiceIndicatorOctet The contents of this ASP parameter is evaluated in TE only if ISUP has been selected in 'isupBiccSelection'. routingLabel RoutingLabel The contents of this ASP parameter is evaluated in TE only if ISUP has been selected in 'isupBiccSelection'. circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is evaluated in TE only if ISUP has been selected in 'isupBiccSelection'. callInstanceCode CallInstanceCode The contents of this ASP parameter is evaluated in TE only if BICC has been selected in 'isupBiccSelection'. iSUP_BICC_MSG ISUP_BICC_MSG ISUP_BICC_MSG is a union over all ISUP/BICC message body types, where a message body starts with the 'message type' field. This body is common for ISUP and BICC messages. When using this ASP, a particular message(body) template is selected from the union for receive matching. Comments: The SA takes from the received message, depending on the value of parameter 'isupBiccSelection', either the ordered combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (ISUP), or 'callInstanceCode' (BICC'), and puts it into the associated ASP parameters. The complementary ASP parameters 'callInstanceCode' (ISUP) and combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (BICC) are filled by the SA with '0'-bits according to the lengths of their types. The TE does not evaluate the contents of the complementary parameters (but needs the correct lengths to identify the start of 'iSUP_BICC_MSG'. The received message (body) is put by the SA into parameter 'iSUP_BICC_MSG' and is matched in the ATS with an according receive template. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 14 Table 4: InitializeIsupBicc_req ASP structure ASP Name: InitializeIsupBicc_req Port: IsupBiccPort Direction: TE -> SA Description: Initialize ISUP/BICC part of the test system. Parameter Type Description isupBiccSelection SelectIsupOrBicc Selector used to distinguish between ISUP and BICC testing. '00000000'B means 'ISUP' and any other value means 'BICC'. ts_pointCode Bit14 Signalling point code of the TS (ISUP). sut_pointCode Bit14 Signalling point code of the SUT (ISUP). ts_address_sip Octetstring Address (e.g. IP) of the TS (SIP side). The use of this address is to enable the TS to communicate with the SUT at the SIP side to establish and maintain the lower layer connections. ts_address_isup_bicc Octetstring Address (e.g. IP) of the TS (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. sut_address_isup_bicc Octetstring Address (e.g. IP) of the SUT (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. Comments: This ASP is used at the beginning of each test case to initiate the necessary initialization of the test system, particularly the interfaces to the SUT. If parameter isupBiccSelection indicates 'bicc', the values of parameters 'ts_pointCode' and 'sut_pointCode' shall be ignored by the SA. If parameter isupBiccSelection indicates 'isup', the values of parameters 'ts_address_isup_bicc' and 'sut_address_isup_bicc' may be ignored, if they are not necessary. Among the initializing actions there shall be: a) Verification that the ISUP/BICC link is operable between SUT and TS. b) Verification that the TS is ready to send and receive SIP messages. NOTE: It is a matter of TS implementation whether the TS, upon this request, sets up and initializes lower layer connections, if these are not setup. Other initialization actions may be TS-specific. Table 5: InitializeIsupBicc_cnf ASP STRUCTURE ASP Name: InitializeIsupBicc_cnf Port: sysPort Direction: LT -> TTCN Description: Answer whether all necessary ISUP/BICC test system initializations have been successfully performed. The result can be positive or negative. The result will be positive only if the TS is able to send and receive messages at the ISUP/BICC-interface of the SUT. Parameter Type Description result Boolean Indicating success or non-success of the whole initialization. Comments: Table 6: BearerSetup_req ASP structure ASP Name: BearerSetup_req Port: IsupBiccPort Direction: TE -> SA Description: For BICC: request TS to setup the bearer connection between TS and SUT. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 15 Table 7: BearerSetup_acc ASP structure ASP Name: BearerSetup_acc Port: IsupBiccPort Direction: SA -> TE Description: For BICC: answer to BearerSetup_req. The answer can be positive (bearer connection setup successful) or negative (bearer connection setup failed). Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. result Boolean The answer is positive when the bearer connection setup was successful and negative when the bearer connection setup failed. Comments: Table 8: BearerSetup_ind ASP structure ASP Name: BearerSetup_ind Port: IsupBiccPort Direction: SA -> TE Description: For BICC: indication that the bearer has been setup. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: Table 9: BearerRelease_req ASP structure ASP Name: BearerRelease_req Port: bcPort Direction: TE -> SA Description: For BICC: request to release the established bearer connection. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: Table 10: BearerRelease_cnf ASP structure ASP Name: BearerRelease_cnf Port: bcPort Direction: SA -> TE Description: For BICC: confirmation that the requested bearer is released. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. result boolean Indication of whether the bearer is successfully released. Comments: At release collision the result is still 'true'. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 16 Table 11: BearerRelease_ind ASP structure ASP Name: BearerRelease_ind Port: bcPort Direction: SA -> TE Description: For BICC: indication that the bearer has been released (when no BearerRelease_req has been issued before). Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: Table 12: s_IsupBicc_conversation ASP structure ASP Name: s_IsupBicc_conversation Port: operatorPort_IsupBicc Direction: SA <-> TE Description: Check that conversation is possible on the through-connected bearer. Parameter Type Description text Charstring Request operator to check the conversation. answer Boolean Check result entered by the operator. Comments: This ASP has been implemented as a signature. "text" is an "input" parameter and "answer" is an output parameter. Table 13: s_IsupBicc_ringing ASP structure ASP Name: s_IsupBicc_ringing Port: operatorPort_IsupBicc Direction: SA <-> TE Description: Check that occurs on the through-connected bearer. Parameter Type Description text Charstring Request operator to check the ringing. answer Boolean Check result entered by the operator. Comments: This ASP has been implemented as a signature. "text" is an "input" parameter and "answer" is an output parameter.
|
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 Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, shall comply with the conventions defined in clause 6.1 of TS 102 027-3 [7]. 4.3.2.3.2.2.2 Encoding/Decoding System requirements for ISUP/BICC 4.3.2.3.2.2.2.1 General ISUP/BICC messages are sent and received in the test suite by embedding them in ASPs ISUP_BICC_MSG_req and ISUP_BICC_MSG_ind respectively. The ASPs contain all information to route the ISUP/BICC messages to/from the SUT. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 17 ISUP messages and parameters are structured by using tables (see ITU-T Recommendation Q.763 [16]). NOTE: The term 'parameter' is used as defined in the ISUP protocol context. It corresponds e.g. to the term 'Information Element' in other protocols. All structure elements are bitstrings, hexstrings or octetstrings. For ISUP message/parameter elements a specific way is defined to extend bitstring- or hexstring elements over octet boundaries. This is known as 'LowToHigh encoding', as shown in the following example: EXAMPLE 1: Coding of element 'Circuit Identity Code' (CIC), consisting of 12 bits: Octet # Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Octet 1 CIC (LSB) Octet 2 spare CIC (MSB) Figure 6: Bit field structure of the 'CIC' parameter The 8 least significant bits of the CIC value fill octet 1 (the least significant bit of CIC is assigned to bit 1 of octet 1), and the 4 most significant bits of the CIC value fill the lower 4 bits of octet 2. NOTE: When a bitstring (hexstring) is presented as a sequence of bits (semi-octets) from left to right, the leftmost bit (semi-octet) is the most significant and the rightmost bit (semi-octet) is the least significant. EXAMPLE 2: Address digits Several ISUP parameters have an element 'Address digits', where the individual digits are BCD-encoded (e.g. digit '0' is encoded as '0000'B, digit '9' is encoded as '1001'B. When an address string is given as a sequence of ASCII digits, as a user would type them in, e.g. "0123456789", the encoded value is as shown on figure 7. Octet # Bits 8 7 6 5 Bits 4 3 2 1 Octet 1 0001 0000 Octet 2 0011 0010 Octet 3 0101 0100 Octet 4 0111 0110 Octet 5 1001 1000 Figure 7: Hex (BCD) field structure of an 'address digits' element This also corresponds to a 'LowToHigh' encoding. In this particular case however, for the sake of ATS user convenience, a conversion function is used in the ATS in the following way: • All module parameters containing address digits have type 'charstring' (resp. IA5String), which means that the user enters digits as ASCII characters '1', '2' and so on. • Inside the address parameter templates the conversion function converts the ASCII string into a BCD-coded octetstring, taking also care of: - 'sending complete' digit (only applicable to the Called Party Number); - filler (final semi-octet, if the number of coded digits is odd. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 18 The encoding of octetstrings however is not LowToHigh, as shown in the following example: EXAMPLE 3: octetstring value The octetstring value '01234ABCDE'O is encoded as shown on figure 8: Octet # Bits 8 7 6 5 Bits 4 3 2 1 Octet 1 0000 0001 Octet 2 0010 0011 Octet 3 0100 1010 Octet 4 1011 1100 Octet 5 1101 1110 Figure 8: Octetstring field encoding 4.3.2.3.2.2.2.2 Decoding of parameters containing strings of variable length Typical fields addressed here are e.g. the 'address digits' field in the 'Called Party Number' parameter, or the 'diagnostics' field in the 'Cause Indicators' parameter. The above mentioned strings of variable length are the last elements of the related parameter, which has a preceding length field. A 'real' decoder deduces the length (and thereby the value) of such fields from the value of the 'length' field of the parameter and the position of the decoder where the field starts. The decoder of the test system shall also be able to decode such fields when the value of the template is '?' or '*'. In order to support this encoding the relevant types have a trailing "with { encode ..." statement, like in the following example (Called Party Number): EXAMPLE 4: .... with { encode (paramLen) "tag=""CDN_paramLen"";"; encode (addressSignals) "length=valueOf(getTag(""CDN_paramLen"")).toInt()-2;"; } End EXAMPLE 4 4.3.2.3.2.2.2.3 Decoding of parameters containing extension bits Some parameters transport IEs from the DSS1 protocol (Q.931), such as the Bearer Capability IE: • IEs of this kind contain extension bits specifying the presence of succeeding octets. The decoder shall be able to evaluate the extension bits to deduce the presence of optional octets in case wildcards '?' or '*' are specified in templates of such IEs. 4.3.2.3.2.2.2.4 Receipt of unknown ISUP/BICC messages Unknown messages in this context are messages not defined in the dated version of [16] referred to in the present document. Unknown messages shall not be passed to TE by the test system. 4.3.2.3.2.2.2.5 Receipt of unknown ISUP/BICC parameters Unknown parameters in this context are parameters not defined in the dated version of ITU-T Recommendation Q.763 [16] referred to in the present document, or defined parameters not being assigned in ITU-T Recommendation Q.763 [16] to the particular received message carrying this parameter. Unknown parameters shall not be passed to TE by the test system (i.e. they shall be removed from the carrying known message before passing this message to TE). ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 19 4.3.2.3.2.2.2.6 Ordering of optional ISUP/BICC parameters and multiple occurrence of parameters According to ITU-T Recommendation Q.763 [16] optional parameters may occur in any order in a message, and some (few) parameters may occur more than once. For the controlled test environment specified in this ATS the following assumption has been made: • Parameters that may occur more than once appear at most two times in a message. For each message that may contain optional parameters the list of parameters has been specified in the ATS as a set. The decoder shall be able to decode the parameters of a received message correctly, even if they appear in an order different from the one specified in the message template (and type).
|
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 clause 5.3.2.2). Table 14: ATS structure Group Subgroup Sub-Subgroup Group Index Basic call SIP-ISUP 1 Sending of the Initial Address Message (IAM) 101 Sending of the Subsequent Address Message (SAM) 102 Sending of COT 103 Receipt of the Address Complete Message (ACM) 104 Receipt of the Call Progress message (CPG) 105 Receipt of the Answer Message (ANM) 106 Receipt of the Connect message (CON) 107 Receipt of the Release message (REL) 108 Autonomous release at I-IWU 109 Receipt of the BYE, CANCEL message / sending of a REL message 110 Receipt of Reset Circuit Message (RSC), Circuit group reset message (GRS) or Circuit group blocking message (CGB) with the indication hardware failure oriented 111 Receipt of the SUSPEND Message (SUS) 112 Receipt of the RESUME Message (RES) 113 Receipt of Confusion Message (CFN) 114 Receipt of Segmentation Message (SGM) 115 ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 20 Group Subgroup Sub-Subgroup Group Index ISUP-SIP 3 Sending of the INVITE message 301 Receipt of the Subsequent address message (SAM) 302 Sending of the Address complete message (ACM) 303 Sending of the Call progress message (CPG) 304 Sending of the answer message (ANM) 305 Sending of the Connect message (CON) 306 Receipt of the Release message (REL) 307 Sending of the Release Message (REL) 308 Receipt of Reset circuit message (RSC), Circuit group reset message (GRS) or Circuit group blocking message (CGB) with the indication hardware failure oriented 309 Receipt of Confusion Message (CFN) 310 Receipt of the SUSPEND Message (SUS) and RESUME Message (RES) 311 Receipt of the Blocking Message (BLO) 312 Receipt of the User Part Test Message (UPT) 313 Receipt of Segmentation Message (SGM) 314 Supplementary Services 4 Calling Line Identification Presentation (CLIP) 401 Calling Line Identification Restriction (CLIR) 402 Connected Line Identification Presentation (COLP) 403 Connected Line Identification Restriction (COLR) 404 Terminal Portability (TP) 405 Subaddressing (SUB) 406 Malicious call identification (MCID) 407 Call Hold (HOLD) 408 Call Waiting (CW) 409 Call Diversion (CFB, CFNR, CFU, CD) 410 Conference Calling (CONF) 411 Explicit Call transfer (ECT) 412 Three-Party (3PTY) 413 User to User Signalling (UUS) User to User service 1 4140 User to User service 1 4141 User to User service 1 4142 ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 21 Group Subgroup Sub-Subgroup Group Index ISDN SIP Interworking BasicCall FromSIPtoISDN 5 SendingSETUP 501 SendingINFO 502 Receiving_ALERT_CALLPROC_PROGRESS 503 Receiving_CONNECT 504 Receiving_DISC_REL 505 Receipt_BYE_CANCEL 506 BasicCall FromISDNtoSIP 6 Sending_INVITE 601 Overlap_sending 602 Sending_ALERT_CALLPROC 603 Sending_CONNECT 604 Receiving_DISC_REL 605 Receipt_BYE_Backward_Resp_CANCEL 606 Autonomous_release 607 Supplementary Services 7 CLIP 701 CLIR 702 COLP 703 COLR 704 TP 705 USS1 7060 USS2 7061 USS3 7062 CUG 707 SUB 708 MCID 709 CONF 710 ECT 711 CFB_CFNR_CFU_CD 712 HOLD 713 CW 714 3PTY 715
|
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 number> is a running 3-digit (or 2-digit) decimal number, starting in each subgroup path with "001" (or "01"). EXAMPLE: TC_101_001: i) the identifier has Group index "101", i.e. it is in the subgroup having complete path: BasicCall/SIP-ISUP/Sending of the Initial address message (IAM)/; ii) the identifier is the first test case of this group/subgroup. NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 002-3 [1] and test case names. The TP identifier of TC_101_001 is TP101001. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 22
|
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 like test cases are common, the TTCN-3 library modules are basically organized as: 1) SIP modules; 2) ISUP modules; 3) Common modules (generated for the present ATS); 4) LibCommon modules (taken from TS 102 351 [2]). ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 23 Table 15 shows the organization of the ATS as library of modules. Table 15: Library of modules Module Class Module Id Description LibCommon LibCommon_AbstractData Generic data types for a stack and its operations. LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean). LibCommon_DataStrings Bit and Octet string types. LibCommon_Sync Co-ordination/synchronization of test components. LibCommon_TextStrings Basic character and string types with fixed length. LibCommon_Time Time handling functions and module parameter. LibCommon_VerdictControl Basic functions for setting of test component verdicts. CommonAts SIPI_PICS Module Parameter declarations associated with PICS. SIPI_PIXITS SIP-ISUP common Module Parameter declarations associated with PIXIT. SIPI_TestCases Test case functions. SIPI_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations. SIPI_TestExecution Module control: execute test cases depending on selection conditions; repeat parameterized test cases based on the "Variant-tables" defined in the test prose. SIPI_TestSystem Common functions, components, ASPs controlling the test system. SIPI_TypesAndValues Definitions are based on component type definitions from IPv6, SCOP and common synchronization libraries. SIPAts SIPI_SIP_TCFunctions PTC root functions for test cases (e.g. f_Sip_TC_101_001). SIPI_SIP_Types SIP data types (messages, header fields) and parallel test component (according to TS 102 027-3 [7]). SIPI_SIP_Templates Templates for SIP messages and header fields (according to RFC 3261 [18]). SIPI_SIP_Steps SIP auxiliary functions. SIPI_SDPTypes SIP SDP data types. SIPI_EncapsISUP ISUP templates used for the encapsulated ISUP messages in SIP message bodies. ISUPAts SIPI_ISUP_Constants Constant declarations, mostly corresponding to field values of ISUP messages/parameters. SIPI_ISUP_ParamTypes ISUP data types (parameter types according to ITU-T Recommendation Q.763 [16] and types required for ASPs). SIPI_ISUP_MsgTypes ISUP data types (message types according to ITU-T Recommendation Q.763 [16] and ASP type declarations). SIPI_ISUP_ParamTemplates Templates for ISUP message parameters. SIPI_ISUP_MsgTemplates Templates for ISUP messages. SIPI_ISUP_Steps Test step declarations, including preambles, postambles and default. SIPI_ISUP_TCFunctions Test case functions running on the Isup/Bicc component.
|
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 style and naming conventions. 4) TTCN-3 is human-readability. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 24 5) TTCN-3 specification is feasible, implementable, compilable and maintainable. 6) Test cases shall be designed in a way to be easily adaptable, upwards compatible with the evolution of the base protocol and protocol interworking of future releases. 7) The test declarations, data structures and data values shall be largely reusable. 8) Modularity and modular working method. 9) Minimizing the requirements of intelligence on the emulators of the lower testers. 10) Giving enough design freedom to the test equipment manufacturers. Fulfilling these requirements should ensure the investment of the test equipment manufacturers and users of the ATS having stable testing means for a relatively long period.
|
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 following underlying principles: • when constructing meaningful identifiers, the general guidelines specified for naming in clause 9 of [2] should be followed; • the names of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) should reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or other conventions being explicitly stated); • the subfield names of TTCN-3 objects being associated with standardized data type should also be similar to corresponding element names in the base standards (be recognizable in the local context); • in most other cases, identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents; • prefixes should be separated from the body of the identifier with an underscore ("_"); • only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. Table 16 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 25 Table 16: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Module Use upper-case initial letter none IPv6Templates TSS grouping Use all upper-case letters as specified in clause 7.1.2.1.1 none TP_RT_PS_TR Item group within a module Use lower-case initial letter none messageGroup ISUP message type Use upper-case initial letter and message name abbreviations as defined in ITU-T Recommendation Q.762 [15] none IAM ISUP parameter type Use upper-case initial letter and parameter name abbreviations taken from ITU-T Recommendation Q.763 [16] none CalledPartyNumber SIP message type Use upper-case initial letter none Request, Response Note 4 SIP header type Use upper-case initial letter none MaxForwards Note 4 Basic common data types (e.g. bit string types of fixed length) Use upper-case initial letter none Take from common module Other Data types Use upper-case initial letter none SetupContents Template None m_ m_IAM_Basic Note 1 Note 5 Message template with wildcard or matching expression None mw_ mw_AnyUserReply Note 2 Note 5 Signature template Use lower-case initial letter s_ s_callSignature Port instance Use lower-case initial letter none signallingPort Test component ref Use lower-case initial letter none userTerminal Constant Use lower-case initial letter c_ c_maxRetransmission External constant Use lower-case initial letter cx_ cx_macId Function Use lower-case initial letter f_ f_authentication() External function Use lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup() Test case Use naming as specified in clause 5.2.2 TC_ TC_101_001 Variable (local) Use lower-case initial letter v_ v_macId Variable (defined within a component) Use lower-case initial letters vc_ vc_systemName Timer (local) Use lower-case initial letter t_ t_wait Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin Module parameter Use initial upper case letters PX PX_MAC_ID Note 3 Parameterization Use lower-case initial letter p_ p_macId Enumerated Value Use lower-case initial letter e_ e_syncOk NOTE 1: This prefix must be used for all template definitions which do not assign or refer to templates with wildcards or matching expressions, e.g. templates specifying a constant value, parameterized templates without matching expressions, etc. NOTE 2: This prefix must be used in identifiers for templates which either assign a wildcard or matching expression (e.g. ?, *, value list, if present, pattern, etc.) or reference another template which assigns a wildcard or matching expression. NOTE 3: In this case it is acceptable to use underscore as a word delimiter. NOTE 4: This convention has been used in TS 102 027-3 [7] (SIP ATS). NOTE 5: Names of ISUP messages and parameters (IEs) start with a syllable being composed of capital letters only, like IAM e.g. This is different for SIP. Naming conventions concerning the first letter of a template (after prefix 'm_' or 'mw_', may be handled differently for ISUP/BICC and SIP respectively.
|
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 freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the interworking type of ATS defined in the present document, the PIXIT are divided in SIP-related PIXIT and ISUP/BICC-related PIXIT (there are no common PIXIT defined, but a set of integer values due to the possibility to select test case variants, if appropriate to the test case definition only). NOTE: The tables in this clause have been generated automatically from the TTCN-3 modules. A.2.1 SIP-related PIXIT For the SIP side of the ATS the PIXIT defined in TS 102 351 [2] apply. In addition the SIP-related PIXIT of tables A.1 to A.4 apply, which have been provided for the particular purposes of this ATS. Each PIXIT item corresponds to a Module Parameter of the ATS. Table A.1: SIP-related PIXIT items (Connection) Index / Identifier Type / Description 1) PX_SIP_TRANSPORT characterstring for used transport in upper case "UDP"/"TCP" 2) PX_SIP_IUT_PORT characterstring for IUT port number to exchange SIP messages 3) PX_SIP_IUT_IPADDR characterstring for IUT IP address to exchange SIP messages (used for CallId) 4) PX_SIP_IUT_HOME_DOMAIN characterstring for IP host address of called user (used for CallId IP domain) 5) PX_SIP_IUT_HOME_DOMAIN_UNKNOWN characterstring for IP host address of called user (invalid IP domain) 6) PX_SIP_IUT_USER characterstring for URL user info (identity) to be called at ISDN side 7) PX_SIP_IUT_USER_FULL characterstring for international format URL user info (identity) to be called at ISDN side 8) PX_SIP_IUT_USER_UNKNOWN characterstring for invalid URL user info (identity) to be called at ISDN side 9) PX_SIP_ETS_IPADDR characterstring for IP host address used by the ETS to exchange SIP messages 10) PX_SIP_ETS_PORT Port number (integer) used by the ETS to exchange SIP messages 11) PX_SIP_ETS_BEARER_PORT characterstring for port number used by the ETS to exchange media streams 12) PX_SIP_ETS_LOCAL_USER characterstring for identity of the local user (URL user info for ETS) 13) PX_SIP_ETS_LOCAL_USER_FULL characterstring for identity of the local user (format "+"cc+ndc+sn, for ETS) 14) PX_SIP_REGISTRAR_DOMAIN characterstring for IUT domain to register SIP user 15) PX_SIP_REGISTRAR_PORT characterstring for IUT port number to register SIP user ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 27 Table A.2: SIP-related PIXIT items (Procedure) Index / Identifier Type / Description 16) PX_SIP_100rel boolean flag on the support of the 100rel mechanism (true if support) 17) PX_SIP_precondition boolean flag on the support of the precondition mechanism (true if support) 18) PX_SIP_BYE_CAUSE cause value (integer) in reason header field of BYE request message 19) PX_SIP_CheckConversation boolean flag value on the implementation of conversation check operation (user plane) 20) PX_SIP_CheckRinging boolean flag value on the implementation of ringing check operation (user plane) 21) PX_SIP_REGISTRATION boolean flag indicates if the SIP user has to register itself before executing a testcase? 22) PX_SIP_REGISTRATION_AUTHENTIC ATION_ENABLED boolean flag on option controlling if authentication is enabled/disabled for registration messages 23) PX_SIP_RFC2617_QOP characterstring for IUT port number to register SIP user RFC 2617 [19] (3-2-1) qop options: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection; example: "auth, auth-int" 24) PX_SIP_RFC2617_USERNAME characterstring for name of user in the specified realm. 25) PX_SIP_RFC2617_PASSWD A known shared secret (charstring), the password of user of the specified username 26) PX_SIP_RFC2617_URI URI (charstring) used for the calculation of the digists (external function) Table A.3: SIP-related PIXIT items (Timer) Index / Identifier Type / Description 27) PX_T6 T6 float value on ISUP max allowed suspend time (1 min to 2 min) 28) PX_T8 T8 float value on ISUP max allowed time for continuity check (10 s to 15 s) 29) PX_T9 T9 float value on ISUP max allowed time for awaiting user answer (ACM) (90 s to 180 s) 30) PX_T39 T39 float value on ISUP max allowed time for awaiting MCID answer (IRS) (12 s to 15 s) 31) PX_TECT T(ECT) float value for ISUP ECT explicit call transfer max value (2 s to 6 s) 32) PX_TOIW1 TOIW1 default (float) value for waiting for address complete signal (4 s to 6 s) 33) PX_SIP_TWAIT default timeout (float) value for SUT request message INVITE, CANCEL, etc. (to avoid deadlock) 34) PX_SIP_TACK default timeout (float) value for SUT acknowledge message ACK (to avoid deadlock) 35) PX_SIP_TRESP default timeout (float) value for SUT response 1xx (to avoid deadlock) 36) PX_SIP_TNOACT default timeout (float) value for SUT "silence" (no message from SUT is received) ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 28 Table A.4: SIP-related PIXIT items (Message body) Index / Identifier Type / Description 37) PX_SIP_SDP_dyn characterstring for SDP media-field fmt-subfield dynamic payload-type (default 0=PCMU is used in preamble) 38) PX_SIP_SDP_port1 integer for SDP media port for audio media (first port in case of 2 ports) 39) PX_SIP_SDP_port2 integer for SDP media port for audio media (second port in case of 2 ports) 40) PX_SIP_SDP_port3 integer for SDP media port for video media 41) PX_SIP_SDP_b_modifier characterstring for SDP bandwidth modifier 42) PX_SIP_SDP_b_bandwidth SDP bandwidth (integer) value 43) PX_SIP_SDP_encoding characterstring for SDP media attribute encoding (used as default in preamble) 44) PX_SIP_SDP_transport characterstring for SDP media-field transport protocol for T38 45) PX_SIP_MIME_Boundary characterstring used in SIP message body to separate MIME parts (boundary) 46) PX_SIP_SDP_ContentType characterstring used for the SDP content-type 47) PX_SIP_ISUP_ContentType characterstring used for the ISUP content-type 48) PX_SIP_ISUP_ContentDisposition characterstring used for the ISUP content-type version A.2.2 ISUP/BICC-related PIXIT Tables A.5 to A.7 list the ISUP/BICC-related PIXIT items associated with the ATS. Each PIXIT item corresponds to a Module Parameter of the ATS. Default values are not provided. Table A.5: ISUP-related PIXIT items (Timer) Index / Identifier Type / Description 49) PX_TDelay_ACM Time (float value) to delay ACM message before sending 50) PX_TDelay_ANM Time (float value) to delay ANM message before sending 51) PX_TDelay_APM Time (float value) to delay APM message before sending 52) PX_TDelay_BLA Time (float value) to delay BLA message before sending 53) PX_TDelay_BLO Time (float value) to delay BLO message before sending 54) PX_TDelay_CFN Time (float value) to delay CFN message before sending 55) PX_TDelay_CGB Time (float value) to delay CGB message before sending 56) PX_TDelay_CGU Time (float value) to delay CGU message before sending 57) PX_TDelay_CON Time (float value) to delay CON message before sending 58) PX_TDelay_COT Time (float value) to delay COT message before sending 59) PX_TDelay_CPG Time (float value) to delay CPG message before sending 60) PX_TDelay_FAA Time (float value) to delay FAA message before sending 61) PX_TDelay_FAC Time (float value) to delay FAC message before sending 62) PX_TDelay_FAR Time (float value) to delay FAR message before sending 63) PX_TDelay_FRJ Time (float value) to delay FRJ message before sending 64) PX_TDelay_GRS Time (float value) to delay GRS message before sending 65) PX_TDelay_IDR Time (float value) to delay IDR message before sending 66) PX_TDelay_IRS Time (float value) to delay IRS message before sending 67) PX_TDelay_LOP Time (float value) to delay LOP message before sending 68) PX_TDelay_REL Time (float value) to delay REL message before sending 69) PX_TDelay_RES Time (float value) to delay RES message before sending 70) PX_TDelay_RLC Time (float value) to delay RLC message before sending 71) PX_TDelay_RSC Time (float value) to delay RSC message before sending 72) PX_TDelay_SAM Time (float value) to delay SAM message before sending 73) PX_TDelay_SEG Time (float value) to delay SEG message before sending 74) PX_TDelay_SUS Time (float value) to delay SUS message before sending 75) PX_TDelay_UBA Time (float value) to delay UBA message before sending 76) PX_TDelay_UBL Time (float value) to delay UBL message before sending 77) PX_TDelay_UPA Time (float value) to delay UPA message before sending ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 29 Index / Identifier Type / Description 78) PX_TDelay_UPT Time (float value) to delay UPT message before sending 79) PX_TDelay_UUI Time (float value) to delay UUI message before sending 80) PX_TDelay_UNKNOWN Time (float value) to delay UNKNOWN message before sending 81) PX_Timeout_T2 Nominal timeout (float) value of ISUP protocol timer T2 82) PX_Timeout_T39 Nominal timeout (float) value of ISUP protocol timer T39 83) PX_Timeout_T4 Nominal timeout (float) value of ISUP protocol timer T4 84) PX_Timeout_T6 Nominal timeout (float) value of ISUP protocol timer T6 85) PX_Timeout_T7 Nominal timeout (float) value of ISUP protocol timer T7 86) PX_Timeout_T8 Nominal timeout (float) value of ISUP protocol timer T8 87) PX_Timeout_T9 Nominal timeout (float) value of ISUP protocol timer T9 88) PX_Timeout_T18 Nominal timeout (float) value of ISUP protocol timer T18 89) PX_Timeout_TOIW1 Nominal timeout (float) value of ISUP/SIP interworking protocol timer TOIW1 90) PX_Timeout_TOIW2 Nominal timeout (float) value of ISUP/SIP interworking protocol timer TOIW2 91) PX_Timeout_TECT Nominal timeout (float) value of ISUP/SIP interworking protocol timer TECT 92) PX_ISUP_TAC Time (float value) to control the reception of a message 93) PX_ISUP_TNOAC Time (float value) to control that IUT sends nothing 94) PX_ISUP_TWAIT Time (float value) to control that IUT reacts prior to Upper Tester action 95) PX_ISUP_TSYNC Time (float value) to control that IUT reacts prior to Upper Tester action 96) PX_ISUP_TSYNC_TIME_LIMIT Time (float value) to control that IUT reacts prior to Upper Tester action Table A.6: ISUP-related PIXIT items (General) Index / Identifier Type / Description 97) PX_ISUP_IsupOrBicc Select whether ISUP or BICC testing is done (selectIsup, selectBicc) 98) PX_ISUP_Isup Flag (boolean) if ISUP is used 99) PX_ISUP_NW_IND Network indicator (2 bits) inside the Service Indicator Octet (SIO) 100) PX_ISUP_PC_TS Point code (14 bits) of the TS (ISUP interface) 101) PX_ISUP_PC_SUT Point code (14 bits) of the SUT (ISUP interface) 102) PX_ISUP_SLS Signalling Link Selection (SLS) value (4 bits) of the ISUP link between TS and SUT 103) PX_TS_ADRESS_ISUP_BICC octetstring for address (eg IP) of the TS (ISUP/BICC side) - The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections 104) PX_SUT_ADRESS_ISUP_BICC octetstrinng for address (eg IP) of the SUT (ISUP/BICC side) - The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections 105) PX_ISUP_TX_CIC_cicv1 Default Circuit Identity Code value (12 bits) for signalling connection 1) 106) PX_ISUP_TX_CIC_cicv2 Default Circuit Identity Code value (12 bits) for signalling connection 2) 107) PX_ISUP_TX_CIC_caicv1 Default Call Instance Code value (octetstring) for signalling connection 1) 108) PX_ISUP_TX_CIC_caicv2 Default Call Instance Code value (octetstring) for signalling connection 2) 109) PX_IsupBicc_CheckConversation boolean value is true if conversation check is used 110) PX_IsupBicc_CheckRinging boolean value is true if ringing check is used Table A.7: ISUP-related PIXIT items (Message parameter) Index / Identifier Type / Description 111) PX_ISUP_CGB_RAS_raValue 8 bits for 'Range value' (Parameter value bigger than 1) sent in the 'Range and Status' parameter in the CGB, CGU message 112) PX_ISUP_CGB_RAS_statValue octetstring for 'Status' value (Parameter value bigger than 1) sent in the 'Range and Status' parameter in the CGB, CGU message 113) PX_ISUP_CGB2_RAS_raValue 8 bits for 'Range value' (Parameter value bigger than 1) sent in the 'Range and Status' parameter in the second CGB, CGU message ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 30 Index / Identifier Type / Description 114) PX_ISUP_CGB2_RAS_statValue octetstring for 'Status' value (Parameter value bigger than 1) sent in the 'Range and Status' parameter in the second CGB, CGU message 115) PX_ISUP_FAC_comp_txDef octetstring for 'component' value (accepted by the SUT without immediate response (PIXIT)) sent in the 'Facility' parameter in the FAC message 116) PX_ISUP_TX_CGC_cliPCategory_rxDef 8 bits for default value for element callingPartysCategory received inside Calling party's category parameter (CGC); Optional(O) format 117) PX_ISUP_IAM_CLD_digits_rxInat characterstring for 'address digits' value (CC NDC SN) received in the 'Called party number' parameter in the IAM message, when the nature of address is 'international number' 118) PX_ISUP_IAM_CLD_digits_rxDef characterstring for default 'address digits' value received in the 'Called party number' parameter in the IAM message 119) PX_ISUP_IAM_CLD_digits_rxNat characterstring for 'address digits' value (NDC SN) received in the 'Called party number' parameter in the IAM message, when the nature of address is 'national number' 120) PX_ISUP_IAM_CLD_digits_txInat_encaps characterstring for 'address digits' value (CC NDC SN) send in the 'Called party number' parameter in the IAM encapsulated message, when the nature of address is 'international number' 121) PX_ISUP_IAM_CLD_digits_txDef_encaps characterstring for default 'address digits' value send in the 'Called party number' parameter in the encapsulated IAM message 122) PX_ISUP_IAM_CLD_digits_txNat_encaps characterstring for 'address digits' value (NDC SN) send in the 'Called party number' parameter in the encapsulated IAM message, when the nature of address is 'national number' 123) PX_ISUP_TX_CDN_addrSignals_encaps characterstring for default value for element addressSignals inside Called party number parameter (CDN) for encapsulated ISUP; Variable(V) format (to be sent when the TP does not specify a specific value for that field) 124) PX_ISUP_IAM_CLI_digits_rxInat characterstring for default 'address digits' value received in the 'Calling party number' parameter in the IAM message, when the Called party number is 'international' 125) PX_ISUP_IAM_CLI_digits_rxNat characterstring for default 'address digits' value received in the 'Calling party number' parameter in the IAM message, when the Called party number is 'national (sign) number' 126) PX_ISUP_IAM_CLI_digits_rxDef characterstring for default 'address digits' value received in the 'Calling party number' parameter in the IAM message, when the Nature of address is not explicitly specified 127) PX_ISUP_IAM_CLI_numIncmplInd_rxDef 1 bit for default 'Number incomplete indicator' value received in the 'Calling party number' parameter in the IAM message 128) PX_ISUP_IAM_CLI_digits_txInat characterstring for default 'address digits' value sent in the 'Calling party number' parameter in the IAM message, when the Called party number is 'international' 129) PX_ISUP_IAM_CLI_digits_txNat characterstring for default 'address digits' value sent in the 'Calling party number' parameter in the IAM message, when the Called party number is 'national (sign) number' 130) PX_ISUP_TX_EIF_v_eventInd 7 bits for default 'PROGRESS event indicator' value received in the 'Event information' parameter in the CPG message 131) PX_ISUP_IAM_FCI_nInatCallInd_rxDef 1 bit for default 'National/international call indicator' value received in the 'Forward call Indicators' parameter in the IAM message 132) PX_ISUP_IAM_FCI_eToEndMavail_rxDef 2 bits for default 'End-to-end method available' value received in the 'Forward call Indicators' parameter in the IAM message 133) PX_ISUP_IAM_FCI_interwInd_rxDef 1 bit for default 'Interworking indicator' value received in the 'Forward call Indicators' parameter in the IAM message 134) PX_ISUP_IAM_FCI_eToEndInfoInd_rxDef 1 bit for default 'End-to-end information indicator' value received in the 'Forward call Indicators' parameter in the IAM message 135) PX_ISUP_IAM_FCI_isdnUpInd_rxDef 1 bit for default 'ISDN user part indicator' value received in the 'Forward call Indicators' parameter in the IAM message 136) PX_ISUP_IAM_FCI_isdnUpPrefInd_rxDef 2 bits for default 'ISDN user part preference indicator' value received in the 'Forward call Indicators' parameter in the IAM message 137) PX_ISUP_IAM_FCI_isdnAccInd_rxDef 1 bit for default 'ISDN access indicator' value received in the 'Forward call Indicators' parameter in the IAM message ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 31 Index / Identifier Type / Description 138) PX_ISUP_IAM_FCI_sccpMind_rxDef 2 bits for default 'SCCP method indicator' value received in the 'Forward call Indicators' parameter in the IAM message 139) PX_ISUP_IAM_CLD_digits_auto characterstring for complete 'address digits' value sent in the 'Called party number' parameter in the IAM message, when the destination is an automatically answering SIP 140) PX_ISUP_TX_CLD_natAddr_auto 7 bits for 'nature of address' value sent in the 'Called party number' parameter in the IAM message, when the destination is an automatically answering SIP 141) PX_ISUP_IAM_CLD_digits_analysis characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by analysis of the number 142) PX_ISUP_TX_CLD_natAddr_analysis 7 bits for 'nature of address' value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by analysis of the number 143) PX_ISUP_IAM_CLD_digits_timeout characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by timeout 144) PX_ISUP_TX_CLD_natAddr_timeout 7 bits for 'nature of address' value value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by timeout 145) PX_ISUP_IAM_CLD_digits_max characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing the maximum number of digits according to the national numbering plan, and no 'sending complete' 146) PX_ISUP_TX_CLD_natAddr_max 7 bits for 'nature of address' value sent in the 'Called party number' parameter in the IAM message, containing the maximum number of digits according to the national numbering plan, and no 'sending complete' 147) PX_ISUP_IAM_CLD_digits_min characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing the minimum number of digits required for routing, and no 'sending complete' 148) PX_ISUP_TX_CLD_natAddr_min 7 bits for 'nature of address' value sent in the 'Called party number' parameter in the IAM message, containing the minimum number of digits required for routing, and no 'sending complete' 149) PX_ISUP_IAM_CLD_digits_SipUri characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, converted by the IWU such that the To header field contains a sip: URI 150) PX_ISUP_TX_CLD_natAddr_SipUri 7 bits for 'nature of address' value sent in the 'Called party number' parameter in the IAM message, converted by the IWU such that the To header field contains a sip: URI 151) PX_ISUP_IAM_CLD_digits_txDef characterstring for default 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing the complete address and 'sending complete' 152) PX_ISUP_TX_CLD_natAddr_txDef 7 bits for default 'nature of address' value sent in the 'Called party number' parameter in the IAM message, containing the complete address and 'sending complete' 153) PX_ISUP_IAM_CLD_digits_Leading_subs characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), and where the nature of address is 'subscriber number' 154) PX_ISUP_IAM_CLD_digits_Leading_nat characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), and where the nature of address is 'national (sign) number' 155) PX_ISUP_IAM_CLD_digits_Leading_sipUri characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), converted by the IWU such that the To header field contains a sip: URI ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 32 Index / Identifier Type / Description 156) PX_ISUP_IAM_CLD_digits_Leading_inat characterstring for 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), and where the nature of address is 'international number' 157) PX_ISUP_IAM_CLD_digits_txDef_inat characterstring for default 'complete address digits' value sent in the 'Called party number' parameter in the IAM message, when the nature of address is specified as 'international number' 158) PX_ISUP_IAM_CLD_digits_txDef_nat characterstring for default 'complete address digits' value sent in the 'Called party number' parameter in the IAM message, when the nature of address is specified as 'national (sign) number' 159) PX_ISUP_IAM_CLD_digits_less characterstring for 'address digits' value (less than minimum number digits to route the call) sent in the 'Calling party number' parameter in the IAM message 160) PX_ISUP_IAM_CLD_natAddr_less 7 bits for 'nature of address' value (number of digits less than minimum number digits to route the call) sent in the 'Calling party number' parameter in the IAM message 161) PX_ISUP_REL_CAU_cVal integer 'Cause' value (decimal) send in the 'Cause' parameter in the REL message 162) PX_ISUP_SAM_SQN_digits_rx1 characterstring for 'address digits' value (PIXIT) received in the 'Subsequent number' parameter in the first SAM message 163) PX_ISUP_SAM_SQN_digits_rx2 characterstring for 'address digits' value (PIXIT) received in the 'Subsequent number' parameter in the second SAM message 164) PX_ISUP_SAM_SQN_digits_txFinLess characterstring for 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, containing the final part of the number, where the IAM contained less than the minimum digits to route the call 165) PX_ISUP_SAM_SQN_digits_txFinDef characterstring for 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, completing the (subscriber) number 166) PX_ISUP_SAM_SQN_digits_txMidDef characterstring for 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, containing the middle part of the complete (subscriber) number 167) PX_ISUP_SAM_SQN_digits_txFinNat characterstring for final 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, completing the (national sign) number 168) PX_ISUP_SAM_SQN_digits_txMidNat characterstring for middle 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, not completing the (national sign) number 169) PX_ISUP_SAM_SQN_digits_txFinPhone characterstring for final 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, where the whole number is mapped to the addr-spec component of the To header field which includes the "user=phone" URI parameter 170) PX_ISUP_SAM_SQN_digits_txFinInat characterstring for 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, completing the (international) number 171) PX_ISUP_SAM_SQN_digits_txMidPhone characterstring for middle 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, where the whole number is mapped to the addr-spec component of the To header field which includes the "user=phone" URI parameter 172) PX_ISUP_SAM_SQN_digits_txMidInat characterstring for 'address digits' value (PIXIT (middle part of standard international address/ to be completed by next SAM)) sent in the 'Subsequent number' parameter in the SAM message 173) PX_ISUP_TX_BCI_v_chargeInd 2 bits for default value for element chargeIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 174) PX_ISUP_TX_BCI_v_cldPStatInd 2 bits for default value for element calledPartysStatusIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 33 Index / Identifier Type / Description 175) PX_ISUP_TX_BCI_v_cldPCatInd 2 bits for default value for element calledPartysCategoryIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 176) PX_ISUP_TX_BCI_v_eTOeMethodInd 2 bits for default value for element end_to_endMethodIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 177) PX_ISUP_TX_BCI_v_interwInd 1 bit for default value for element interworkingIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 178) PX_ISUP_TX_BCI_v_eTOeInfoInd 1 bit for default value for element end_to_endInformationIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 179) PX_ISUP_TX_BCI_v_iSDNUserPartInd 1 bit for default value for element iSDNUserPartIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 180) PX_ISUP_TX_BCI_v_holdingInd 1 bit for default value for element holdingIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 181) PX_ISUP_TX_BCI_v_iSDNAccessInd 1 bit for default value for element iSDNAccessIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 182) PX_ISUP_TX_BCI_v_echoContrDevInd 1 bit for default value for element echoControlDeviceIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 183) PX_ISUP_TX_BCI_v_sCCPMethodInd 2 bits for default value for element sCCPMethodIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 184) PX_ISUP_TX_CDN_natOfAddressInd 7 bits for default value for element natureOfAddressIndicator inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field) 185) PX_ISUP_TX_CDN_numbPlanInd 3 bits for default value for element numberingPlanIndicator inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field) 186) PX_ISUP_TX_CDN_iNN 1 bit for default value for element iNN inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field) 187) PX_ISUP_TX_CDN_addrSignals characterstring for default value for element addressSignals inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field) 188) PX_ISUP_TX_CGC_cliPCategory 8 bits for default value for element callingPartysCategory inside Calling party's category parameter (CGC); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 189) PX_ISUP_TX_CPN_natOfaddressind 7 bits for default value for element natureOfaddressindicator inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 190) PX_ISUP_TX_CPN_screenInd 2 bits for default value for element screeningIndicator inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 191) PX_ISUP_TX_CPN_addrPresRestrInd 2 bits for default value for element APRI = 'presentation allowed' inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 192) PX_ISUP_TX_CPN_numbplanInd 3 bits for default value for element numbering plan Indicator inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). 193) PX_ISUP_TX_CPN_addrSignals_txNat characterstring for default value for element 'addressSignals' (national format) inside 'Connected number' parameter; (to be sent when the TP does not specify a specific value for that field) ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 34 Index / Identifier Type / Description 194) PX_ISUP_TX_CPN_addrSignals_txInat characterstring for default value for element 'addressSignals' (international format) inside 'Connected number' parameter; (to be sent when the TP does not specify a specific value for that field) 195) PX_ISUP_TX_CPN_addrSignals_rxNat characterstring for default 'addressSignals' value received in the 'Connected number' parameter in the ANM or CON message when the Called party number is 'national' 196) PX_ISUP_TX_CPN_addrSignals_rxInat characterstring for default 'addressSignals' value received in the 'Connected number' parameter in the ANM or CON message when the Called party number is 'international' 197) PX_ISUP_TX_CTN_natOfaddressind 7 bits for default value for element natureOfaddressindicator inside Call transfer number (CTN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 198) PX_ISUP_TX_CTN_screenInd 2 bits for default value for element screeningIndicator inside Call transfer number (CTN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 199) PX_ISUP_TX_CTN_addrPresRestrInd 2 bits for default value for element addrPresRestrInd inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 200) PX_ISUP_TX_CTN_numbplanInd 3 bits for default value for element numberingplanIndicator inside Call transfer number (CTN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 201) PX_ISUP_TX_CTN_addrSignals_txNat characterstring for default value for element 'addressSignals' (national format) inside Call transfer number (CTN) parameter; (to be sent when the TP does not specify a specific value for that field) 202) PX_ISUP_TX_CTN_addrSignals_rxNat characterstring for default 'addressSignals' value received in the Call transfer number (CTN) parameter in the ANM or CON message when the Called party number is 'national' 203) PX_ISUP_TX_CTN_addrSignals_rxInat characterstring for default 'addressSignals' (international format) value received in the Call transfer number (CTN) parameter in the ANM or CON message when the Called party number is 'national' 204) PX_ISUP_TX_FCI_natInternatCallInd 1 bit for default value for element natInternatCallIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 205) PX_ISUP_TX_FCI_endToEndMethodInd 2 bits for default value for element endToEndMethodIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 206) PX_ISUP_TX_FCI_interwInd 1 bit for default value for element interworkingIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 207) PX_ISUP_TX_FCI_eTOeInfoIndic 1 bit for default value for element endToEndInfoIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 208) PX_ISUP_TX_FCI_iSDNUserPartInd 1 bit for default value for element iSDNUserPartIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 209) PX_ISUP_TX_FCI_iSDNUserPartPrefInd 2 bits for default value for element iSDNUserPartPrefIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 210) PX_ISUP_TX_FCI_iSDNAccessInd 1 bit for default value for element iSDNAccessIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 211) PX_ISUP_TX_FCI_sCCPMethodInd 2 bits for default value for element sCCPMethodIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 212) PX_ISUP_TX_FCI_reserved 4 bits for default value for element reserved inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 213) PX_ISUP_TX_GEN_addrSignals_rxInat characterstring for 'address digits' value received in the 'Generic number' parameter, when the Nature of Address is 'international number' ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 35 Index / Identifier Type / Description 214) PX_ISUP_TX_GEN_addrSignals_rxNat characterstring for 'address digits' value received in the 'Generic number' parameter, when the Nature of Address is 'national (sign) number' 215) PX_ISUP_TX_GEN_addrSignals_txInat characterstring for 'address digits' value sent in the 'Generic number' parameter, when the Nature of Address is 'international number' 216) PX_ISUP_TX_GEN_addrSignals_txNat characterstring for 'address digits' value sent in the 'Generic number' parameter, when the Nature of Address is 'national (sign) number' 217) PX_ISUP_TX_NCI_satelliteInd 2 bits for default value for element satelliteIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 218) PX_ISUP_TX_NCI_contCheckInd 2 bits for default value for element continuityCheckIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 219) PX_ISUP_TX_NCI_echoContrDevInd 1 bit for default value for element echoControlDeviceIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field) 220) PX_ISUP_TX_OCN_natOfAddressInd 7 bits for default value for element natureOfAddressIndicator inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 221) PX_ISUP_TX_OCN_addrPresRestrInd 2 bits for default value for element addrPresRestrInd inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 222) PX_ISUP_TX_OCN_numbPlanInd 3 bits for default value for element numberingPlanIndicator inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 223) PX_ISUP_TX_OCN_addrSignals_Nat characterstring for default value for element addressSignals inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 224) PX_ISUP_TX_OCN_addrSignals_Inat characterstring for default 'addressSignals' value received in the 'Original called number' parameter in the IAM message when the called party number is 'international' 225) PX_ISUP_TX_RAS_range 8 bits for default value for element range inside Range and status parameter (RAS); Variable(V) format (to be sent when the TP does not specify a specific value for that field) 226) PX_ISUP_TX_RAS_status octetstring for default value for element status inside Range and status parameter (RAS); Variable(V) format (to be sent when the TP does not specify a specific value for that field) 227) PX_ISUP_TX_RAS_status_noDefault octetstring for default value for element status inside Range and status parameter (RAS); Variable(V) format (to be sent when the TP does not specify a specific value for that field) 228) PX_ISUP_TX_RDN_natOfAddressInd 7 bits for default value for element natureOfAddressIndicator inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 229) PX_ISUP_TX_RDN_addrPresRestrInd 2 bits for default value for element addrPresRestrInd inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 230) PX_ISUP_TX_RDN_numbPlanInd 3 bits for default value for element numberingPlanIndicator inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 231) PX_ISUP_TX_RDN_addrSignals_Nat characterstring fornational value for element addressSignals inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 36 Index / Identifier Type / Description 232) PX_ISUP_TX_RDN_addrSignals_Inat characterstring for international value for element addressSignals inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 233) PX_ISUP_TX_RNN_natOfAddressInd 7 bits for default value for element natureOfAddressIndicator inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 234) PX_ISUP_TX_RNN_numbPlanInd 3 bits for default value for element numberingPlanIndicator inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 235) PX_ISUP_TX_RNN_iNN 1 bit for default value for element Internal Network Number indicator inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 236) PX_ISUP_TX_RNN_addrSignals_Nat characterstring for national value for element addressSignals inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 237) PX_ISUP_TX_RNN_addrSignals_Inat characterstring for international value for element addressSignals inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 238) PX_ISUP_TX_RNS_presRestrInd 2 bits for default value for element presRestrIndicator inside Redirection number restriction parameter (RNS); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 239) PX_ISUP_TX_TMR_transmMedReq 8 bits for default value for element transmissionMediumRequirement inside Transmission medium requirement prime parameter (TMRP); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 240) PX_ISUP_TX_UUI_userInfo_S1 octetstring for default 'user-to-user information' (Service 1 data) value sent in the 'User-to-user information' parameter in the IAM message 241) PX_ISUP_TX_UUI_userInfo_S2 octetstring for default 'user-to-user information' (Service 2 data) value sent in the 'User-to-user information' parameter in the IAM message 242) PX_ISUP_TX_UUI_userInfo_S3 octetstring for default 'user-to-user information3' (Service 3 data) value sent in the 'User-to-user information' parameter in the IAM message 243) PX_ISUP_TX_HPC_hopCounter 5 bits for default value for element hopCounter inside Hop counter parameter (HPC); Optional(O) format (to be sent when the TP does not specify a specific value for that field) 244) PX_ISUP_TX_digits_Prefix characterstring for default prefix digits defined for 'address digits' value 245) PX_ISUP_TX_unknown_parameter_type 8 bits for default value for an unknown parameter type (to be sent when the TP does not specify a specific value for that field) 246) PX_ISUP_TX_unknown_message_type 8 bits for default value for an unknown message type (to be sent when the TP does not specify a specific value for that field) 247) PX_ISUP_TX_cgps_information octetstring for default value for calling party subaddress information in the Access transport(to be sent when the TP does not specify a specific value for that field) 248) PX_ISUP_TX_cgps_odd_even_indicator 1 bit for default value for calling party subaddress odd even indicator in the Access transport(to be sent when the TP does not specify a specific value for that field) 249) PX_ISUP_TX_cgps_type_of_subaddress 3 bits for default value for calling party subaddress type of subaddress in the Access transport(to be sent when the TP does not specify a specific value for that field) 250) PX_ISUP_TX_cdps_information octetstring for default value for called party subaddress information in the Access transport(to be sent when the TP does not specify a specific value for that field) ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 37 Index / Identifier Type / Description 251) PX_ISUP_TX_cdps_odd_even_indicator 1 bit for default value for called party subaddress odd even indicator in the Access transport (to be sent when the TP does not specify a specific value for that field) 252) PX_ISUP_TX_cdps_type_of_subaddress 3 bits for default value for called party subaddress type of subaddress in the Access transport(to be sent when the TP does not specify a specific value for that field) 253) PX_ISUP_TX_connsub_type_of_subaddress 3 bits for default value for connected subaddress type of subaddress in the Access transport (to be sent when the TP does not specify a specific value for that field) 254) PX_ISUP_TX_connsub_odd_even_indicator 1 bits for default value for connected party subaddress odd even indicator in the Access transport (to be sent when the TP does not specify a specific value for that field) 255) PX_ISUP_TX_connsub_information octetstring for default value for connected subaddress information in the Access transport(to be sent when the TP does not specify a specific value for that field) 256) PX_ISUP_TX_without_Cancel_Encaps According to RFC 3398 [i.1] and Q.1912.5 [5], received CANCEL message does not contain encapsulated REL. If false, received CANCEL message with encapsulated REL is supported. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 38 Annex B (informative): TTCN-3 library modules B.1 Electronic annex, zip file with TTCN-3 code The TTCN-3 library modules are contained in archive ts_18600205v010101p0.zip which accompanies the present document. ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 39 Annex C (informative): Bibliography • ETSI ES 201 873-7 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 7: Using ASN.1 with TTCN-3". • ETSI TS 102 237-1 (V4.1.1): "Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to interoperability testing". • ETSI EG 202 106 (V2.1.1): "Methods for Testing and Specification (MTS); Guidelines for the use of formal SDL as a descriptive tool". • ISO/IEC 9646-2 (1994): "Conformance testing methodology and framework - Part 2: Abstract Test Suite Specification". • ISO/IEC 9646-3 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation". • ISO/IEC 9646-3/DAM 1 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation; Amendment 1: TTCN extensions". • ISO/IEC 9646-5 (1994): "Conformance testing methodology and framework - Part 5: Requirements on test laboratories and clients for the conformance assessment process". • ITU-T Recommendation Q.1902.1 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC): Functional description". • ITU-T Recommendation Q.1902.2 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC): General functions of messages and parameters". • ITU-T Recommendation Q.1902.3 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC): Formats and codes". • ITU-T Recommendation Q.1902.4 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC): Basic call procedures". • ITU-T Recommendation Q.731.7 (1997): "Stage 3 description for number identification supplementary services using Signalling System No. 7: Malicious call identification (MCID)". • ITU-T Recommendation Q.732.2 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call diversion services - Call Forwarding Busy (CFB)". • ITU-T Recommendation Q.732.3 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding No Reply (CFNR)". • ITU-T Recommendation Q.732.4 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding Unconditional (CFU)". • ITU-T Recommendation Q.732.5 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Deflection (CD)". • ITU-T Recommendation Q.732.7 (1996): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Explicit Call Transfer". • ITU-T Recommendation Q.733.1 (1992): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call waiting (CW)". • ITU-T Recommendation Q.733.2 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call hold (HOLD)". ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 40 • ITU-T Recommendation Q.733.3 (1997): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls to busy subscriber (CCBS)". • ITU-T Recommendation Q.733.4 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Terminal portability (TP)". • ITU-T Recommendation Q.733.5 (1999): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls on no reply". • ITU-T Recommendation Q.734.1 (1993): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Conference calling". • ITU-T Recommendation Q.734.2 (1996): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Three-party service". • ITU-T Recommendation Q.735.1 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Closed user group (CUG)". • ITU-T Recommendation Q.735.3 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Multi-level precedence and preemption". • ITU-T Recommendation Q.735.6 (1996): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Global Virtual Network Service (GVNS)". • ITU-T Recommendation Q.736.1 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: International Telecommunication Charge Card (ITCC)". • ITU-T Recommendation Q.736.3 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: Reverse charging (REV)". • ITU-T Recommendation Q.737.1 (1997): "Stage 3 description for additional information transfer supplementary services using Signalling System No. 7: User-to-user signalling (UUS)". • ITU-T Recommendation Q.850 (1998): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". • IETF RFC 2046 (1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". • IETF RFC 2327 (1998): "SDP: Session Description Protocol". • IETF RFC 2806 (2000): "URLs for Telephone Calls". • IETF RFC 3204 (2001): "MIME media types for ISUP and QSIG Objects". • IETF RFC 3262 (2002): "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". • IETF RFC 3264 (2002): "An Offer/Answer Model with the Session Description Protocol (SDP)". • IETF RFC 3311 (2002): "The Session Initiation Protocol UPDATE Method". • IETF RFC 3312 (2002): "Integration of Resource Management and Session Initiation Protocol (SIP)". • IETF RFC 3323 (2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)". • IETF RFC 3326 (2002): "The Reason Header Field for the Session Initiation Protocol". • IETF RFC 1035 (1997): "Domain names - implementation and specification". ETSI ETSI TS 186 002-5 V1.1.1 (2010-06) 41 History Document history V1.1.1 June 2010 Publication
|
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 (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part, Profiles A and B. The ATS is sometimes referred to in the present document as "SIP-ISUP-Interworking ATS". The test notation used in the ATS is TTCN-3 (ES 201 873-1 [8]). The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the partial Implementation eXtra Information for Testing (IXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
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 accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
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 002-2: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP); Part 2: Test Suite Structure and Test Purposes (TSS&TP) for Profile A and B". [2] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [3] ETSI TS 186 002-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICC) or ISDN User Part (ISUP); Part 1: Protocol Implementation Conformance Statement (PICS)". [4] ETSI EN 383 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control (BICC) Protocol or ISDN User Part (ISUP) [ITU-T Recommendation Q.1912.5, modified]". [5] ITU-T Recommendation Q.1912.5 (2004): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part". [6] ITU-T Recommendation Q.2150.1 (2001): "Signalling Transport Converter on MTP3 and MTP3b". [7] ETSI TS 102 027-3 (V3.1.1): "Methods for Testing and Specification (MTS); Conformance Test Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma". [8] ETSI ES 201 873-1 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [9] ETSI ES 201 873-5 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)". [10] ETSI ES 201 873-6 (V3.1.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)". [11] Void. [12] ISO/IEC 9646-1 (1992): "Information Technology - Open Systems Interconnection - Conformance Testing Methodology and Framework - Part 1: General concepts". [13] ISO/IEC 9646-7 (1994): "Conformance testing methodology and framework - Part 7: Implementation Conformance Statement". [14] ITU-T Recommendation Q.761 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". [15] ITU-T Recommendation Q.762(2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". [16] ITU-T Recommendation Q.763 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP); ISDN user part formats and codes". [17] ITU-T Recommendation Q.764 (2000): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". [18] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [19] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". [20] ETSI ES 283 027: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Endorsement of the SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks [3GPP TS 29.163 (Release 7), modified]". ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 7 [21] ETSI EN 300 356-1 (V4.2.1): "Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 for the international interface; Part 1: Basic services [ITU-T Recommendations Q.761 to Q.764 (1999) modified]".
|
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 interface layer 3 specification for basic call control".
|
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 [12] and ISO/IEC 9646-7 [13]; • ES 201 873-1 [8] (TTCN-3). and the following 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 and ending in a stable testing state Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to make the description independent of any particular realization of a Means of Testing, but with enough detail to enable abstract test cases to be specified for this method Abstract Test Suite (ATS): test suite composed of abstract test cases Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider relationship, being part of a real open system which is to be studied by testing Means Of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection, parameterization and execution of test cases, in conformance with a reference standardized ATS, and can produce a conformance log PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes the PICS PIXIT proforma: document, in the form of a questionnaire, which when completed for the IUT becomes the PIXIT point of Control and Observation: point within a testing environment where the occurrence of test events is to be controlled and observed, as defined in an Abstract Test Method pre-test condition: setting or state in the IUT which cannot be achieved by providing stimulus from the test environment Protocol Implementation Conformance Statement (PICS): statement made by the supplier of a protocol claimed to conform to a given specification, stating which capabilities have been implemented ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 8 Protocol Implementation eXtra Information for Testing (PIXIT): statement made by a supplier or implementor of an IUT (protocol) which contains or references all of the information related to the IUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT SIP number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [19] System Under Test (SUT): real open system in which the IUT resides
|
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 Test Case ATM Abstract Test Method ATM Asynchronous Transfer Mode ATS Abstract Test Suite BCI Backward Call Indicators BICC Bearer Independent Call Control CIC Circuit Identification Code DSS1 Digital Subscriber System No. 1 EDS Encoding/Decoding System ETS Executable Test Suite FCI Forward Call Indicators G/W Type 1 GateWay Type 1 G/W Type 2 GateWay Type 2 IETF Internet Engineering Task Force ISDN Integrated Services Digital Network ISUP ISDN User Part IUT Implementation Under Test IWU InterWorking Unit IXIT Implementation eXtra Information for Testing LT Lower Tester MOT Means Of Testing MTP Message Transfer Part NCI Nature of Connection Indicators NGN Next Generation Network PA Platform Adapter PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing PTC Parallel Test Component SA System Adapter SDP Session Description Protocol SIP Session Initiation Protocol SN Signalling Node STC Signalling Transport Converter (according to ITU-T Recommendation Q.2150.1 [6]) SUT System Under Test TC Test Case TCI TTCN-3 Control Interface TCP Test Coordination Procedures TD Test Description TE Test Equipment TISPAN Telecommunications and Internet converged Services and Protocols for Advanced Networking TL Test Logging TM Test Management TMR Transmission Medium Requirement TP Test Purpose ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 9 TRI TTCN-3 Runtime Interface TS Test System TSS Test Suite Structure TSS&TP Test Suite Structure and Test Purposes TTCN Tree and Tabular Combined Notation TTCN-3 Testing and Test Control Notation edition 3
|
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 network architecture for SIP-BICC Interworking. SIP BICC <------------------------------------------> <-----------------------------------------> IWU <------------------------------------------> ATM bearer control Figure 2: Interworking between SIP and BICC NOTE: There are 3 profiles defined for IWU: Profile A, Profile B and Profile C (out of scope of the present document). Figures 1 and 2 in clause 5 of TS 186 002-2 [1] show the substructures of the IWU for Profiles A and B in terms of gateways and signalling nodes. In the ATS the SUT (IWU) represents either a G/W Type 1 (Profile A) or the combination of G/W Type 2 and SN (Profile B).
|
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 protocol. NOTE: No signalling is used within the SIP-ISUP-Interworking ATS to control the ATM bearer in case of BICC (ASPs are used). Figure 3 shows the protocol architecture in 2 branches. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 10 SUT IUT IUT SIP ISUP BICC STC STC UDP TCP MTP 3 MTP 3b IP MTP Layer 2 AAL (LAN) G.703/G.704 ATM Figure 3: Protocol architecture of the SIP-ISUP-Interworking ATS
|
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 (SA) Platform Adapter (PA) Figure 5: Abstract Test System Architecture A TS has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and Platform Adapter (PA) entities, respectively. Out of these two interfaces the TRI has been standardized in ES 201 873-5 [9], whereas the specification and implementation of the TCI is in ES 201 873-6 [10]. The part of TS that deals with interpretation and execution of TTCN-3 modules, i.e. the Executable Test Suite (ETS), is shown as part of the TTCN-3 Executable (TE). This ETS corresponds either to the executable code produced by a TTCN-3 compiler or a TTCN-3 interpreter from the TTCN-3 ATS in a TS implementation. The remaining part of the TS, which deals with any aspects that cannot be concluded from information being present in the TTCN-3 ATS alone, can be decomposed into Test Management (TM), SUT Adapter (SA) and Platform Adapter (PA) entities. In general, these entities cover a TS user interface, test execution control, test event logging, communication of test data with the SUT, and timer implementation. The part of SA used for SIP message transfer shall implement the TRI adaptation as well as the SIP transport protocol architecture described in clause 4.2. The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, with the TE and Test Logging (TL) entity within the TM shall comply with the conventions defined in clause 4.3.2 of TS 102 027-3 [7]. The part of SA used for ISUP/BICC message transfer shall implement the TRI adaptation as well as the ISUP/BICC transport protocol architecture described in clause 4.2. For BICC, in addition, the ATM bearer control shall be implemented. The Encoding/Decoding System (EDS) entity, as far as applied to ISUP/BICC messages, shall comply with the conventions and requirements defined in the following clauses. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 12
|
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 system initializations have been successfully performed. ISUP_BICC_MSG_req Used to send an ISUP/BICC message. ISUP_BICC_MSG_ind Used to receive an ISUP/BICC message. BearerSetup_req For BICC: request TS to setup the bearer connection between TS and SUT. BearerSetup_acc For BICC: answer to BearerSetup_req. BearerSetup_ind For BICC: indication that the bearer has been setup. BearerRelease_req For BICC: request to release established bearer connection. BearerRelease_cnf For BICC: confirmation that the requested bearer is released. BearerRelease_ind For BICC: indication that the bearer has been released (when no BearerRelease_req has been issued before). s_IsupBicc_conversation Check that conversation is possible on the bearer. s_IsupBicc_ringing Check that ringing occurs. The following tables 2 to 13 contain the descriptions of the ASPs used in the present document, including the ASP parameters (if any) and the types of values these may assume. No ASP parameter is optional. Table 2: ISUP_BICC_MSG_req ASP structure ASP Name: ISUP_BICC_MSG_req Port: sysPort Direction: TE->SA Description: ASP used to send an ISUP/BICC message. Parameter Type Description isupBiccSelection SelectIsupOrBicc Selector used to distinguish between ISUP and BICC testing. '00000000'B means 'ISUP' and any other value means 'BICC'. serviceIndicatorOctet ServiceIndicatorOctet The contents of this ASP parameter is only evaluated in SA if ISUP has been selected in 'isupBiccSelection'. routingLabel RoutingLabel The contents of this ASP parameter is only evaluated in SA if ISUP has been selected in 'isupBiccSelection'. circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is only evaluated in SA if ISUP has been selected in 'isupBiccSelection'. callInstanceCode CallInstanceCode The contents of this ASP parameter is only evaluated in SA if BICC has been selected in 'isupBiccSelection'. iSUP_BICC_MSG ISUP_BICC_MSG ISUP_BICC_MSG is a union over all ISUP/BICC message body types, where a message body starts with the 'message type' field. This body is common for ISUP and BICC messages. When using this ASP, a particular message (body) template is selected from the union for transmission. Comments: The SA takes from the ASP, depending on the value of parameter 'isupBiccSelection', either the ordered combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (ISUP), or 'callInstanceCode' (BICC'), puts it in front of encoded parameter 'iSUP_BICC_MSG', and sends the so constructed message at the ISUP or BICC interface respectively. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 13 Table 3: ISUP_BICC_MSG_ind ASP structure ASP Name: ISUP_BICC_MSG_ind Port: sysPort Direction: SA->TE Description: ASP used to receive an ISUP/BICC message. Parameter Type Description isupBiccSelection Bit8 Selector used to distinguish between ISUP and BICC testing. '00000000'B means 'ISUP' and any other value means 'BICC'. serviceIndicatorOctet ServiceIndicatorOctet The contents of this ASP parameter is only evaluated in TE if ISUP has been selected in 'isupBiccSelection'. routingLabel RoutingLabel The contents of this ASP parameter is only evaluated in TE if ISUP has been selected in 'isupBiccSelection'. circuitIdentityCode CircuitIdentityCode The contents of this ASP parameter is only evaluated in TE if ISUP has been selected in 'isupBiccSelection'. callInstanceCode CallInstanceCode The contents of this ASP parameter is only evaluated in TE if BICC has been selected in 'isupBiccSelection'. iSUP_BICC_MSG ISUP_BICC_MSG ISUP_BICC_MSG is a union over all ISUP/BICC message body types, where a message body starts with the 'message type' field. This body is common for ISUP and BICC messages. When using this ASP, a particular message (body) template is selected from the union for receive matching. Comments: The SA takes from the received message, depending on the value of parameter 'isupBiccSelection', either the ordered combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (ISUP), or 'callInstanceCode' (BICC'), and puts it into the associated ASP parameters. The complementary ASP parameters 'callInstanceCode' (ISUP) and combination of 'serviceIndicatorOctet', 'routingLabel' and 'circuitIdentityCode' (BICC) are filled by the SA with '0'-bits according to the lengths of their types. The TE does not evaluate the contents of the complementary parameters (but needs the correct lengths to identify the start of 'iSUP_BICC_MSG'. The received message (body) is put by the SA into parameter 'iSUP_BICC_MSG' and is matched in the ATS with an according receive template. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 14 Table 4: InitializeIsupBicc_req ASP structure ASP Name: InitializeIsupBicc_req Port: IsupBiccPort Direction: TE->SA Description: Initialize ISUP/BICC part of the test system. Parameter Type Description isupBiccSelection Bit8 Selector used to distinguish between ISUP and BICC testing. '00000000'B means 'ISUP' and any other value means 'BICC'. ts_pointCode Bit14 Signalling point code of the TS (ISUP). sut_pointCode Bit14 Signalling point code of the SUT (ISUP). ts_address_sip octetstring Address (e.g. IP) of the TS (SIP side). The use of this address is to enable the TS to communicate with the SUT at the SIP side to establish and maintain the lower layer connections. ts_address_isup_bicc octetstring Address (e.g. IP) of the TS (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. sut_address_sip octetstring Address (e.g. IP) of the SUT (SIP side). The use of this address is to enable the TS to communicate with the SUT at the SIP side to establish and maintain the lower layer connections. sut_address_isup_bicc octetstring Address (e.g. IP) of the SUT (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. Comments: This ASP is used at the beginning of each test case to initiate the necessary initialization of the test system, particularly the interfaces to the SUT. If parameter isupBiccSelection indicates 'bicc', the values of parameters 'ts_pointCode' and 'sut_pointCode' shall be ignored by the SA. If parameter isupBiccSelection indicates 'isup', the values of parameters 'ts_address_isup_bicc' and 'sut_address_isup_bicc' may be ignored, if they are not necessary. Among the initializing actions there shall be: a) Verification that the ISUP/BICC link is operable between SUT and TS. b) Verification that the TS is ready to send and receive SIP messages. NOTE: It is a matter of TS implementation whether the TS, upon this request, sets up and initializes lower layer connections, if these are not setup. Other initialization actions may be TS-specific. Table 5: InitializeIsupBicc_cnf ASP STRUCTURE ASP Name: InitializeIsupBicc_cnf Port: sysPort Direction: LT->TTCN Description: Answer whether all necessary ISUP/BICC test system initializations have been successfully performed. The result can be positive or negative. The result will be positive only if the TS is able to send and receive messages at the ISUP/BICC- interface of the SUT. Parameter Type Description result boolean Indicating success or non-success of the whole initialization. Comments: ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 15 Table 6: BearerSetup_req ASP structure ASP Name: BearerSetup_req Port: IsupBiccPort Direction: TE->SA Description: For BICC: request TS to setup the bearer connection between TS and SUT. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: Table 7: BearerSetup_acc ASP structure ASP Name: BearerSetup_acc Port: IsupBiccPort Direction: SA->TE Description: For BICC: answer to BearerSetup_req. The answer can be positive (bearer connection setup successful) or negative (bearer connection setup failed). Parameter Type Description result boolean The answer is positive when the bearer connection setup was successful and negative when the bearer connection setup failed. Comments: Table 8: BearerSetup_ind ASP structure ASP Name: BearerSetup_ind Port: IsupBiccPort Direction: SA->TE Description: For BICC: indication that the bearer has been setup. Parameter Type Description cic CallInstanceCode Call Instance Code identifying the bearer connection. Comments: Table 9: BearerRelease_req ASP structure ASP Name: BearerRelease_req Port: bcPort Direction: TE->SA Description: For BICC: request to release the established bearer connection. Parameter Type Description cic CIC Circuit identity code identifying the bearer connection. Comments: Table 10: BearerRelease_cnf ASP structure ASP Name: BearerRelease_cnf Port: bcPort Direction: SA->TE Description: For BICC: confirmation that the requested bearer is released. Parameter Type Description result boolean Indication of whether the bearer is successfully released. Comments: At release collision the result is still 'true'. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 16 Table 11: BearerRelease_ind ASP structure ASP Name: BearerRelease_ind Port: bcPort Direction: SA->TE Description: For BICC: indication that the bearer has been released (when no BearerRelease_req has been issued before). Parameter Type Description cic CIC Circuit identity code identifying the bearer connection. Comments: Table 12: s_IsupBicc_conversation ASP structure ASP Name: s_IsupBicc_conversation Port: operatorPort_IsupBicc Direction: SA-<>TE Description: Check that conversation is possible on the through-connected bearer. Parameter Type Description text char string Request operator to check the conversation. answer boolean Check result entered by the operator. Comments: This ASP has been implemented as a signature. ‘text' is an ‘input' parameter and ‘answer' is an output parameter. Table 13: s_IsupBicc_ringing ASP structure ASP Name: s_IsupBicc_ringing Port: operatorPort_IsupBicc Direction: SA-<>TE Description: Check that occurs on the through-connected bearer. Parameter Type Description text charstring Request operator to check the ringing. answer boolean Check result entered by the operator. Comments: This ASP has been implemented as a signature. ‘text' is an ‘input' parameter and ‘answer' is an output parameter.
|
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 Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, shall comply with the conventions defined in clause 6.1 of TS 102 027-3 [7]. 4.3.2.3.2.2.2 Encoding/Decoding System requirements for ISUP/BICC 4.3.2.3.2.2.2.1 General ISUP/BICC messages are sent and received in the test suite by embedding them in ASPs ISUP_BICC_MSG_req and ISUP_BICC_MSG_ind respectively. The ASPs contain all information to route the ISUP/BICC messages to/from the SUT. ISUP messages and parameters are structured by using tables (see ITU-T Recommendation Q.763 [16]). ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 17 NOTE 1: The term 'parameter' is used as defined in the ISUP protocol context. It corresponds e.g. to the term 'Information Element' in other protocols. All structure elements are bitstrings, hexstrings or octetstrings. For ISUP message/parameter elements a specific way is defined to extend bitstring- or hexstring elements over octet boundaries. This is known as 'LowToHigh encoding', as shown in the following example: EXAMPLE 1: Coding of element 'Circuit Identity Code' (CIC), consisting of 12 bits. Octet # Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Octet 1 CIC (LSB) Octet 2 spare CIC (MSB) Figure 6: Bit field structure of the 'CIC' parameter The 8 least significant bits of the CIC value fill octet 1 (the least significant bit of CIC is assigned to bit 1 of octet 1), and the 4 most significant bits of the CIC value fill the lower 4 bits of octet 2. NOTE 2: When a bitstring (hexstring) is presented as a sequence of bits (semi-octets) from left to right, the leftmost bit (semi-octet) is the most significant and the rightmost bit (semi-octet) is the least significant. EXAMPLE 2: Adress digits Several ISUP parameters have an element 'Adress digits', where the individual digits are BCD-encoded (i.e. e.g. digit '0' is encoded as '0000'B, digit '9' is encoded as '1001'B). When an address string is given as a sequence of ASCII digits, as a user would type them in, e.g. "0123456789", the encoded value is as shown on figure 7. Octet # Bits 8 7 6 5 Bits 4 3 2 1 Octet 1 0001 0000 Octet 2 0011 0010 Octet 3 0101 0100 Octet 4 0111 0110 Octet 5 1001 1000 Figure 7: Hex (BCD) field structure of an 'address digits' element This also corresponds to a 'LowToHigh' encoding. In this particular case however, for the sake of ATS user convenience, a conversion function is used in the ATS in the following way: • All module parameters containing address digits have type 'charstring' (resp. IA5String), which means that the user enters digits as ASCII characters '1', '2' and so on. • Inside the address parameter templates the conversion function converts the ASCII string into a BCD-coded octetstring, taking also care of: - 'sending complete' digit (only applicable to the Called Party Number); - filler (final semi-octet, if the number of coded digits is odd. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 18 The encoding of octetstrings however is not LowToHigh, as shown in the following example: EXAMPLE 3: octetstring value The octetstring value '01234ABCDE'O is encoded as shown on figure 8: Octet # Bits 8 7 6 5 Bits 4 3 2 1 Octet 1 0000 0001 Octet 2 0010 0011 Octet 3 0100 1010 Octet 4 1011 1100 Octet 5 1101 1110 Figure 8: Octetstring field encoding 4.3.2.3.2.2.2.2 Decoding of parameters containing strings of variable length Typical fields addressed here are e.g. the 'adress digits' field in the 'Called Party Number' parameter, or the 'diagnostics' field in the 'Cause Indicators' parameter. The above mentioned strings of variable length are the last elements of the related parameter, which has a preceding length field. A 'real' decoder deduces the length (and thereby the value) of such fields from the value of the 'length' field of the parameter and the position of the decoder where the field starts. The decoder of the test system shall also be able to decode such fields when the value of the template is '?' or '*'. In order to support this encoding the relevant types have a trailing "with { encode ..." statement, like in the following example (Called Party Number): EXAMPLE: .... with { encode (paramLen) "tag=""CDN_paramLen"";"; encode (addressSignals) "length=valueOf(getTag(""CDN_paramLen"")).toInt()-2;"; } End 4.3.2.3.2.2.2.3 Decoding of parameters containing extension bits Some parameters transport IEs from the DSS1 protocol (ITU-T Recommendation Q.931 [i.1]), such as the Bearer Capability IE: • IEs of this kind contain extension bits specifying the presence of succeeding octets. • The decoder shall be able to evaluate the extension bits to deduce the presence of optional octets in case wildcards '?' or '*' are specified in templates of such IEs. 4.3.2.3.2.2.2.4 Receipt of unknown ISUP/BICC messages Unknown messages in this context are messages not defined in the dated version of ITU-T Recommendation Q.763 [16] referred to in the present document. Unknown messages shall not be passed to TE by the test system. 4.3.2.3.2.2.2.5 Receipt of unknown ISUP/BICC parameters Unknown parameters in this context are parameters not defined in the dated version of ITU-T Recommendation Q.763 [16] referred to in the present document, or defined parameters not being assigned in ITU-T Recommendation Q.763 [16] to the particular received message carrying this parameter. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 19 Unknown parameters shall not be passed to TE by the test system (i.e. they shall be removed from the carrying known message before passing this message to TE). 4.3.2.3.2.2.2.6 Ordering of optional ISUP/BICC parameters and multiple occurrence of parameters According to ITU-T Recommendation Q.763 [16] optional parameters may occur in any order in a message, and some (few) parameters may occur more than once. For the controlled test environment specified in this ATS the following assumption has been made: • Parameters that may occur more than once appear at most two times in a message. For each message that may contain optional parameters the list of parameters has been specified in the ATS as a set. The decoder shall be able to decode the parameters of a received message correctly, even if they appear in an odder different from the one specified in the message template (and type).
|
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 comments have been made on TS 186 002-2 [1] (TSS&TP) and TS 186 002-1 [3] (PICS). These are not referred to in detail in the present document. Part of the comments related to inconsistent namings of the TP tables in TS 186 002-2 [1]. Re-naming of the TP tables was agreed by TISPAN. The test purposes listed in table 14 have not been transformed into complete test cases: Table 14: Untested test purposes TP Reason for not implementing TP108103 The test purpose description requires that unrecognized backward ISUP or BICC signalling has to be sent by the SS, but it does not specify the specific signalling contents. TP108107 The test purpose description does not specify the action or signalling that would make the IUT release the call in both directions. TP308020 The test purpose description does not specify the action or signalling that would make the IUT release the call in both directions. TP308021 The test purpose description does not specify the action or signalling that would make the IUT release the call in both directions. TP301038 The contents of the APM message the test purpose description requires to be set does not correspond to any APM structure definition contained in a document listed in the 'References' clause of TS 186 002-2 [1]. TP301043 The contents of the APM message the test purpose description requires to be set does not correspond to any APM structure definition contained in a document listed in the 'References' clause of TS 186 002-2 [1]. NOTE 2: Formally these test cases exist in the ATS, but their executables will not yield the expected results. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 20
|
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 clause 5.3.2.2). ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 21 Table 15: ATS structure Group Subgroup Sub-Subgroup Group Index Basic call SIP-ISUP 1 Sending of the Initial Address Message (IAM) 101 Sending of the Subsequent Address Message (SAM) 102 Sending of COT 103 Receipt of the Address Complete Message (ACM) 104 Receipt of the Call Progress messaGe (CPG) 105 Receipt of the ANswer Message (ANM) 106 Receipt of the Connect message (CON) 107 Receipt of the Release message (REL) 108 Autonomous release at I-IWU 1081 Receipt of the BYE, CANCEL message / sending of a REL message 109 Receipt of Reset circuit message (RSC), Circuit group reset message (GRS) or Circuit group blocking message (CGB) with the indication hardware failure oriented 110 Receipt of the SUSPEND Message (SUS) 111 Receipt of the RESUME Message (RES) 112 ISUP-SIP 3 Sending of the INVITE message 301 Receipt of the Subsequent address message (SAM) 302 Sending of the Address complete message (ACM) 303 Sending of the Call progress message (CPG) 304 Sending of the answer message (ANM) 305 Sending of the Connect message (CON) 306 Receipt of the Release message (REL) 307 Sending of the Release Message (REL) 308 Receipt of Reset circuit message (RSC), Circuit group reset message (GRS) or Circuit group blocking message (CGB) with the indication hardware failure oriented 309 Supplementary Services SIP-ISUP 5 Calling Line Identification (CLI) 501 Call Hold (HOLD) 502 Terminal Portability (TP) 503 Conference Calling (CONF) 504 Three-Party (3PTY) 505 Connected Line Identification (COL) 506 Malicious call identification (MCID) 507 Subaddressing (SUB) 508 Call Diversion (CDIV) 509 Call Waiting (CW) 510 User to User Signalling (UUS) 511 Explicit Call Transfer (ECT) 512 Completion of Call to Busy Subscriber (CCBS) 513 Completion of Calls on No reply (CCNR) 514 Anonymous Call Rejection (ACR) 515 ISUP-SIP 6 Calling Line Identification (CLI) 601 Call Hold (HOLD) 602 Terminal Portability (TP) 603 Conference Calling (CONF) 604 Three-Party (3PTY) 605 Connected Line Identification (COL) 606 Subaddressing (SUB) 607 Closed User Group (CUG) 608 Call Diversion (CDIV) 609 User to User Signalling (UUS) 610 Explicit Call transfer (ECT) 611 NOTE: All subgroups except for "Autonomous release at I-IWU"/1081 use 3 digits to number test cases inside this subgroup. For ‘Autonomous release at I-IWU'/1081 only 2 digits are available. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 22
|
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 running 3-digit decimal number, starting in each subgroup path with "001". NOTE 1: See note in table 15 for the one exception from this rule and its reason. EXAMPLE: TC_101_001: i the identifier has Group index "101", i.e. it is in the subgroup having complete path: BasicCall/SIP-ISUP/Sending of the Initial address message (IAM)/; ii the identifier is the first test case of this group/subgroup. NOTE 2: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 002-2 [1] and test case names. The TP identifier of TC_101_001 is TP101001.
|
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 like test cases are common, the TTCN-3 library modules are basically organized as: 1) SIP modules; 2) ISUP modules; 3) Common modules (generated for the present ATS); 4) LibCommon modules (taken from TS 102 351 [2]). Table 16 shows the organization of the ATS as library of modules. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 23 Table 16: Library of modules Module Class Module Id Description LibCommon LibCommon_AbstractData Generic data types for a stack and its operations. LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean). LibCommon_DataStrings Bit and Octet string types. LibCommon_Sync Co-ordination/synchronization of test components. LibCommon_TextStrings Basic character and string types with fixed length. LibCommon_Time Time handling functions and moduleparameter. LibCommon_VerdictControl Basic functions for setting of test component verdicts. AtsCommon SipIsup_PICS Module Parameter declarations associated with PICS. SipIsup_PIXITS SIP-ISUP common Module Parameter declarations associated with PIXIT. SipIsup_Testcases Test case functions. SipIsup_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations. SipIsup_TestExecution Module control: execute test cases depending on selection conditions; repeat parameterized test cases based on the "Variant-tables" defined in the test prose. SipIsup_TestSystem Common functions, components, ASPs controlling the test system. SipIsup_TypesAndValues Definitions are based on component type definitions from IPv6, SCOP and common synchronization libraries. SipAts SipIsup_SIP_TCFunctions PTC root functions for test cases (e.g. f_Sip_TC_101_001). SipIsup_SIP_TypesAndConfig SIP data types (messages, header fields) and parallel test component (according to TS 102 027-3 [7]). SipIsup_SIP_Templates Templates for SIP messages and header fields (according to RFC 3261 [18]). SipIsup_SIP_Steps SIP auxiliary functions. IsupAts SipIsup_ISUP_Constants Constant declarations, mostly corresponding to field values of ISUP messages/parameters. SipIsup_ISUP_ModuleParams Module parameters (all associated with PIXIT). SipIsup_ISUP_ParamTypes ISUP data types (parameter types according to ITU-T Recommendation Q.763 [16] and types required for ASPs). SipIsup_ISUP_MsgTypes ISUP data types (message types according to ITU-T Recommendation Q.763 [16] and ASP type declarations). SipIsup_ISUP_ParamTemplates Templates for ISUP message parameters. SipIsup_ISUP_MsgTemplates Templates for ISUP messages. SipIsup_ISUP_Steps Test step declarations, including preambles, postambles and default. SipIsup_ISUP_TCFunctions Test case functions running on the Isup/Bicc component.
|
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 style and naming conventions. 4) TTCN-3 is human-readability. 5) TTCN-3 specification is feasible, implementable, compilable and maintainable. 6) Test cases shall be designed in a way to be easily adaptable, upwards compatible with the evolution of the base protocol and protocol interworking of future releases. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 24 7) The test declarations, data structures and data values shall be largely reusable. 8) Modularity and modular working method. 9) Minimizing the requirements of intelligence on the emulators of the lower testers. 10) Giving enough design freedom to the test equipment manufacturers. Fulfilling these requirements should ensure the investment of the test equipment manufacturers and users of the ATS having stable testing means for a relatively long period.
|
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 following underlying principles: • when constructing meaningful identifiers, the general guidelines specified for naming in clause 9 of TS 102 351 [2] should be followed; • for the SIP ATS part, which is based on a subset of TS 102 027-3 [7], with extensions, the naming conventions defined in TS 102 027-3 [7] should be followed; • the names of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) should reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or other conventions being explicitly stated); • the subfield names of TTCN-3 objects being associated with standardized data type should also be similar to corresponding element names in the base standards (be recognizable in the local context); • in most other cases, identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents; • prefixes should be separated from the body of the identifier with an underscore ("_"); • only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. Table 17 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 25 Table 17: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Module Use upper-case initial letter none IPv6Templates TSS grouping Use all upper-case letters as specified in clause 7.1.2.1.1 none TP_RT_PS_TR Item group within a module Use lower-case initial letter none messageGroup ISUP message type Use upper-case initial letter and message name abbreviations as defined in [15] none IAM ISUP parameter type Use upper-case initial letter and parameter name abbreviations taken from [16] none CalledPartyNumber SIP message type Use upper-case initial letter none Request, Response note 4 SIP header type Use upper-case initial letter none MaxForwards note 4 Basic common data types (e.g. bit string types of fixed length) Use upper-case initial letter none Take from common module Other Data types Use upper-case initial letter none SetupContents Template None m_ m_IAM_Basic note 1 note 5 Message template with wildcard or matching expression None mw_ mw_AnyUserReply note 2 note 5 Signature template Use lower-case initial letter s_ s_callSignature Port instance Use lower-case initial letter none signallingPort Test component ref Use lower-case initial letter none userTerminal Constant Use lower-case initial letter c_ c_maxRetransmission External constant Use lower-case initial letter cx_ cx_macId Function Use lower-case initial letter f_ f_authentication() External function Use lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup() Test case Use naming as specified in clause 5.2.2 TC_ TC_101_001 Variable (local) Use lower-case initial letter v_ v_macId Variable (defined within a component) Use lower-case initial letters vc_ vc_systemName Timer (local) Use lower-case initial letter t_ t_wait Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin Module parameter Use initial upper case letters PX PX_MAC_ID note 3 Parameterization Use lower-case initial letter p_ p_macId Enumerated Value Use lower-case initial letter e_ e_syncOk NOTE 1: This prefix must be used for all template definitions which do not assign or refer to templates with wildcards or matching expressions, e.g. templates specifying a constant value, parameterized templates without matching expressions, etc. NOTE 2: This prefix must be used in identifiers for templates which either assign a wildcard or matching expression (e.g. ?, *, value list, if present, pattern, etc.) or reference another template which assigns a wildcard or matching expression. NOTE 3: In this case it is acceptable to use underscore as a word delimiter. NOTE 4: This convention has been used in TS 102 027-3 [7] (SIP ATS). NOTE 5: Names of ISUP messages and parameters (IEs) start with a syllable being composed of capital letters only, like IAM e.g. This is different for SIP. Naming conventions concerning the first letter of a template (after prefix 'm_' or 'mw_', may be handled differently for ISUP/BICC and SIP respectively. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 26
|
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 comments, as illustrated: /* ----------------------- * @desc This line of text is now identified as a description * which covers multiple lines * -----------------------*/ Comments tags specified within a single line may be specified using line comments, as illustrated: // @author John Doe or: /* @author John Doe */ Table 18 lists the tags that can be used in ETSI TTCN-3 test specifications with a short description of the intended use of each tag. Tools may support other, non standard tags. Such tags should not be used in TTCN-3 modules standardized by ETSI. NOTE: Tools may also extract other information from the TTCN-3 code based, for example, on TTCN- 3 keywords. The definition of that extraction is beyond the scope of the present document. Table 18: TTCN-3 Comment Tags Tag Description @author This tag should be used to specify the names of the authors or an authoring organization which either has created or is maintaining a particular piece of TTCN-3 code. @desc This is probably the most import of all the tags. It should be used to describe the purpose of a particular piece of TTCN-3 code. The description should be concise yet informative and describe the function and use of the construct. @remark This tag may be used to add additional information, such as highlighting a particular feature or aspect not covered in the description. @img This tag may be used to associate images with a particular piece of TTCN-3 code. @see This tag may be used to refer to other TTCN-3 definitions in the same or another module. @url This tag should be used to associate references to external files or web pages with a particular piece of TTCN-3 code, e.g. a protocol specification or standard. @return This tag should only be used with functions. It is used to provide additional information on the value returned by the given function. @param This tag is used to document the parameters of parameterized TTCN-3 definitions. @version This tag is used to state the version of a particular piece of TTCN-3 code. The following provides some basic guidelines on the usage of tags for specific TTCN-3 definitions: • each TTCN-3 module should use the @author, @version and @desc tags; • the @desc tag should be used with all TTCN-3 definitions. However, this should not be taken to the extreme. For example, it is probably not useful to tag literally every single constant or template declaration. It is left to the discretion of the writer to find the right level of use. At least all major constructs such as test cases and functions should have a comprehensive description: - when a TTCN-3 definition uses module parameters, it is also recommended to mention this explicitly in the description; - descriptions for behavioural constructs should mention if they set the test component verdict and also all known limitations of the construct; - descriptions for type definitions, e.g. component types, should mention if the type has been designed to be type compatible to another type or vice versa to be used as a basis for other type definitions. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 27 • the @see tag should be used to make dependencies between TTCN-3 definitions which are described by a @desc tag more explicit in the documentation, e.g. if some TTCN-3 definition uses a module parameter then its TTCN-3 definition should be referenced to using a @see tag; • where applicable, parameterized constructions such as functions, altsteps and templates should use the @param and @return tags. The @param tags should first list the parameter name and then a brief description of how this parameter is used by the construct; • the @url tag should be used to refer to the specification from which the TTCN-3 definition was derived from, e.g. a type definition could refer to a particular RFC IETF page. In some cases it may be necessary to use the @desc tag instead for this purpose as documents often are hard to access internally, i.e. it may only be possible to specify a reference to a complete document but impossible to point to a very specific clause in the present document; • the @url and @img tag may be used to link to relevant documentation such as Test Purposes or original requirements or even drawings of test configurations. Generally, the corresponding Test Purpose (in the TSS&TP) and to the corresponding Requirement (in the Requirements Catalogue) should be linked from the relevant TTCN-3 test case definition; • the @remark tag may be used with any TTCN-3 definition. It should be used sparingly, e.g. possibly to indicate how a TTCN-3 definition should not be used.
|
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 freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the interworking type of ATS defined in the present document, the PIXIT are divided in SIP-related PIXIT and ISUP/BICC-related PIXIT (there are no common PIXIT defined). ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 29 A.2.1 SIP-related PIXIT For the SIP side of the ATS the PIXIT defined in TS 102 351 [2] apply. In addition the SIP-related PIXIT of table A.1 apply, which have been provided for the particular purposes of this ATS. Each PIXIT item corresponds to a Module Parameter of the ATS. Table A.1: Additional SIP-related PIXIT items Item Module Parameter Description Type Value 1.1 PX_SIP_SDPBODY3 additional SDP parameter proposed by the ETS (delivered with UPDATE) charstring 1.2 PX_SIP_SDPBODY4 additional SDP parameter proposed by the SUT (delivered with 200 OK UPDATE), for session modification testing charstring 1.3 PX_SIP_SDPBODY_A_and_U additional SDP parameter proposed by the ETS (delivered with INVITE), should propose PCMA and PCMU charstring 1.4 PX_SIP_PASSERTEDID additional SDP parameter proposed by the ETS (delivered with INVITE), used in Suppl. Services Group format: sip: +CC NDC+SNN charstring 1.5 PX_SIP_PASSERTEDID2 2nd P-Asserted-ID, according to rfc3325(9.1) format: sip: +CC NDC+SNN charstring 1.6 PX_MAX_NR_OF_HOPS f_Sip_TC_301_060 integer 1.7 PX_SIP_BYE_CAUSE f_Sip_TC_308_004, also used in Failure messages (TC_308_017) integer 1.8 PX_SIP_SDPBODY_WITHOUT _MEDIA SDP parameter proposed by the ETS (delivered with INVITE), includes only the lines up to the m line, e.g. v, o, s, c, t lines charstring 1.9 PX_SIP_SDPBODY_DEFAULT _MEDIA SDP parameter proposed by the ETS (delivered with INVITE), includes only the m and optionally the a line(s) charstring 1.10 PX_SDP_MEDIA_PORT port for SDP media line charstring 1.11 PX_SDP_MEDIA_DYNAMIC_P T Dynamic PT for SDP media line charstring 1.12 PX_SDP_T38_ATTRIBUTE T.38 attribute for SDP attribute line charstring 1.13 PX_SIP_MAX_FORWARDS Max Forwards value for TC101023 integer 1.14 PX_SIPURL_CDPN_INTERNAT IONAL_HOME SIP Url with a called party number in the format +CC NDC SN, where CC is the country code of the network in which the next hop terminates. used in TC101024 charstring 1.15 PX_SIPURL_CDPN_INTERNAT IONAL_ABROAD SIP Url with a called party number in the format +CC NDC SN, where CC is NOT the country code of the network in which the next hop terminates. used in TC101025 charstring 1.16 PX_SIPURL_CDPN SIP Url with a called party number used in TC101026 charstring 1.17 PX_SIPURL_CGPN calling party number (From field) used in TP501 and TP601 charstring 1. 18 PX_SIPURL_CGPN_DISPLAY calling party number (From field, display name only!) used in TP501 and TP601 charstring 1.19 PX_SIPURL_CGPN_PASSERT ED calling party number (P-AssertedID line1) used in TP501 and TP601 charstring 1.20 PX_SIPURL_CGPN_PASSERT ED2 calling party number (P-AssertedID line2) used in TP501 and TP601 charstring 1.21 PX_SIP_CheckConversation true if conversation check is implemented and used boolean 1.22 PX_SIP_CheckRinging true if ringing check is implemented and used boolean ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 30 A.2.2 ISUP/BICC-related PIXIT The following tables A.2 to A.5 list the ISUP/BICC-related PIXIT items associated with the ATS. Each PIXIT item corresponds to a Module Parameter of the ATS. Default values are not provided. Table A.2: General SS/SUT-related ISUP/BICC PIXIT items Item IModule Parameter Description Type Value 2.1 PX_ISUP_Isup Select whether ISUP (true) or BICC (false) testing is done (depending on whether the SUT implements ISUP or BICC on the outgoing circuits under test). boolean 2.2 PX_ISUP_NW_IND Network indicator inside the Service Indicator octet (SIO). bitstring(2) 2.3 PX_ISUP_SLS Signalling Link Selection (SLS) value of the ISUP link between TS and SUT. bitstring(4) 2.4 PX_ISUP_PC_SUT Point code of the SUT (ISUP interface). bitstring(14) 2.5 PX_ISUP_PC_TS Point code of the TS (ISUP interface). bitstring(14) 2.6 PX_SUT_ADRESS_ISUP_BICC Address (e.g. IP) of the SUT (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. charstring 2.7 PX_TS_ADRESS_ISUP_BICC Address (e.g. IP) of the TS (ISUP/BICC side). The use of this address is to enable the TS to communicate with the SUT at the ISUP/BICC side to establish and maintain the lower layer connections. octetstring 2.8 PX_ISUP_TX_CIC_cicv1 Default Circuit Identity Code value for signalling connection 1). bitstring(12) 2.9 PX_ISUP_TX_CIC_cicv2 Default Circuit Identity Code value for signalling connection 2). bitstring(12) 2.10 PX_ISUP_TX_CIC_caicv1 Default Call Instance Code value for signalling connection 1). octetstring(4) 2.11 PX_ISUP_TX_CIC_caicv2 Default Call Instance Code value for signalling connection 2). octetstring(4) ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 31 Table A.3: Timer-related ISUP/BICC PIXIT items Item IModule Parameter Description Type Value 3.1 PX_ISUP_TAC Time to control the reception of a message. float 3.2 PX_ISUP_TNOAC Time to control that IUT sends nothing. float 3.3 PX_ISUP_TSYNC Time to control synchronization. float 3.4 PX_ISUP_TSYNC_TIME_LIMIT Time to control synchronization. float 3.5 PX_ISUP_TDONE Time to control PTC.stop. float 3.6 PX_ISUP_TWAIT Time to control that IUT reacts prior to Upper Tester action. float 3.7 PX_TDelay_ACM Time to delay ACM message before sending. float 3.8 PX_TDelay_ANM Time to delay ANM message before sending. float 3.9 PX_TDelay_APM Time to delay APM message before sending. float 3.10 PX_TDelay_CGB Time to delay CGB message before sending. float 3.11 PX_TDelay_CON Time to delay CON message before sending. float 3.12 PX_TDelay_COT Time to delay COTM message before sending. float 3.13 PX_TDelay_CPG Time to delay CPG message before sending. float 3.14 PX_TDelay_FAC Time to delay FAC message before sending. float 3.15 PX_TDelay_FAR Time to delay FAR message before sending. float 3.16 PX_TDelay_GRS Time to delay GRS message before sending. float 3.17 PX_TDelay_IDR Time to delay IDR message before sending. float 3.18 PX_TDelay_LOP Time to delay LOP message before sending. float 3.19 PX_TDelay_REL Time to delay REL message before sending. float 3.20 PX_TDelay_RES Time to delay RES message before sending. float 3.21 PX_TDelay_RLC Time to delay RLC message before sending. float 3.22 PX_TDelay_RSC Time to delay RSC message before sending. float 3.23 PX_TDelay_SAM Time to delay SAM message before sending. float 3.24 PX_TDelay_SUS Time to delay SUS message before sending. float 3.25 PX_TDelay_UNKNOWN Time to delay UNKNOWN message before sending. float 3.26 PX_Timeout_T2 Nominal timeout value of ISUP protocol timer T2. float 3.27 PX_Timeout_T39 Nominal timeout value of ISUP protocol timer T39. float 3.28 PX_Timeout_T6 Nominal timeout value of ISUP protocol timer T6. float 3.29 PX_Timeout_T7 Nominal timeout value of ISUP protocol timer T7. float 3.30 PX_Timeout_T8 Nominal timeout value of ISUP protocol timer T8. float 3.31 PX_Timeout_T9 Nominal timeout value of ISUP protocol timer T9. float 3.32 PX_Timeout_TOIW1 Nominal timeout value of ISUP/SIP interworking protocol timer TOIW1. float 3.33 PX_Timeout_TOIW2 Nominal timeout value of ISUP/SIP interworking protocol timer TOIW2. float ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 32 Item IModule Parameter Description Type Value 3.34 PX_Timeout_TOIW3 Nominal timeout value of ISUP/SIP interworking protocol timer TOIW3. float Table A.4: Operator-check-related ISUP/BICC PIXIT items Item IModule Parameter Description Type Value 4.1 PX_IsupBicc_CheckConversation True if conversation check is implemented and used. Otherwise false (see note 1). boolean 4.2 PX_IsupBicc_CheckRinging True if ringing check is implemented and used. Otherwise false (see note 2). boolean NOTE 1: If true, test execution will stop at positions where the TP indicates 'conversation' until the operator enters the check result. NOTE 2: If true, test execution will stop at positions where the TP indicates 'ringing' until the operator enters the check result. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 33 Table A.5: ISUP/BICC PIXIT items associated with message fields Item Module Parameter Description Type Value Connected Party Subaddress 5.1.1 PX_ISUP_TX_connsub_information Default value for connected subaddress information (to be sent when the TP does not specify a specific value for that field). Ref.: Q.931 [i.1], M.5.4. octetstring 5.1.2 PX_ISUP_TX_connsub_type_of_subaddress Default value for connected subaddress type of subaddress (to be sent when the TP does not specify a specific value for that field). Ref.: Q.931 [i.1], M.5.4. bitstring(3) 5.1.3 PX_ISUP_TX_connsub_odd_even_indicator Default value for connected party subaddress odd even indicator (to be sent when the TP does not specify a specific value for that field). Ref.: Q.931 [i.1], M.5.4. bitstring(1) Facility 5.2 PX_ISUP_FAC_comp_txDef 'component' value (accepted by the SUT without immediate response (PIXIT)) sent in the 'Facility' parameter in the FAC message. octetstring Called party number - receiving 5.3.1 PX_ISUP_IAM_CLD_digits_rxDef Default 'address digits' value received in the 'Called party number' parameter in the IAM message. Ref.: Q.763 [16], 3.9. IA5String 5.3.2 PX_ISUP_IAM_CLD_digits_rxInat 'address digits' value (CC NDC SN) received in the 'Called party number' parameter in the IAM message, when the nature of address is 'international number'. Ref.: Q.763 [16], 3.9. IA5String 5.3.3 PX_ISUP_IAM_CLD_digits_rxNat 'address digits' value (NDC SN) received in the 'Called party number' parameter in the IAM message, when the nature of address is 'national number'. Ref.: Q.763 [16], 3.9. IA5String Called party number - sending 5.4.1.1 PX_ISUP_IAM_CLD_digits_auto Complete 'address digits' value sent in the 'Called party number' parameter in the IAM message, when the destination is an automatically answering SIP. Ref.: Q.763 [16], 3.9. IA5String 5.4.1.2 PX_ISUP_TX_CLD_natAddr_auto 'nature of address' value sent in the 'Called party number' parameter in the IAM message, when the destination is an automatically answering SIP. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.2.1 PX_ISUP_IAM_CLD_digits_analysis 'address digits' value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by analysis of the number. Ref.: Q.763 [16], 3.9. IA5String ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 34 Item Module Parameter Description Type Value 5.4.2.2 PX_ISUP_TX_CLD_natAddr_analysis 'nature of address' value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by analysis of the number. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.3.1 PX_ISUP_IAM_CLD_digits_timeout 'address digits' value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by timeout. Ref.: Q.763 [16], 3.9. IA5String 5.4.3.2 PX_ISUP_TX_CLD_natAddr_timeout 'nature of address' value sent in the 'Called party number' parameter in the IAM message, when 'sending complete' is not sent, not the maximum number of digits are sent, the number is complete and completeness is determined by timeout. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.4.1 PX_ISUP_IAM_CLD_digits_max 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing the maximum number of digits according to the national numbering plan, and no 'sending complete'. Ref.: Q.763 [16], 3.9. IA5String 5.4.4.2 PX_ISUP_TX_CLD_natAddr_max 'nature of address' value sent in the 'Called party number' parameter in the IAM message, containing the maximum number of digits according to the national numbering plan, and no 'sending complete'. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.5.1 PX_ISUP_IAM_CLD_digits_min 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing the minimum number of digits required for routing, and no 'sending complete'. Ref.: Q.763 [16], 3.9. IA5String 5.4.5.2 PX_ISUP_TX_CLD_natAddr_min 'nature of address' value sent in the 'Called party number' parameter in the IAM message, containing the minimum number of digits required for routing, and no 'sending complete'. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.6.1 PX_ISUP_IAM_CLD_digits_SipUri 'address digits' value sent in the 'Called party number' parameter in the IAM message, converted by the IWU such that the To header field contains a sip: URI. Ref.: Q.763 [16], 3.9. IA5String ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 35 Item Module Parameter Description Type Value 5.4.6.2 PX_ISUP_TX_CLD_natAddr_SipUri 'nature of address' value sent in the 'Called party number' parameter in the IAM message, converted by the IWU such that the To header field contains a sip: URI. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.7.1 PX_ISUP_IAM_CLD_digits_txDef Default 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing the complete address and 'sending complete'. Ref.: Q.763 [16], 3.9. IA5String 5.4.7.2 PX_ISUP_TX_CLD_natAddr_txDef Default 'nature of address' value sent in the 'Called party number' parameter in the IAM message, containing the complete address and 'sending complete'. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.8 PX_ISUP_IAM_CLD_digits_Leading_subs 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), and where the nature of address is 'subscriber number'. Ref.: Q.763 [16], 3.9. IA5String 5.4.9 PX_ISUP_IAM_CLD_digits_Leading_nat 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), and where the nature of address is 'national (sign.) number'. Ref.: Q.763 [16],3.9. IA5String 5.4.10 PX_ISUP_IAM_CLD_digits_Leading_sipUri 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), converted by the IWU such that the To header field contains a sip: URI. Ref.: Q.763 [16], 3.9. IA5String 5.4.11 PX_ISUP_IAM_CLD_digits_Leading_inat 'address digits' value sent in the 'Called party number' parameter in the IAM message, containing a leading part of an address (to be completed by 2 SAM messages), and where the nature of address is 'international number'. Ref.: Q.763 [16], 3.9. IA5String 5.4.12 PX_ISUP_IAM_CLD_digits_txDef_inat Default 'complete address digits' value sent in the 'Called party number' parameter in the IAM message, when the nature of address is specified as 'international number'. Ref.: Q.763 3.9. IA5String 5.4.13 PX_ISUP_IAM_CLD_digits_txDef_nat Default 'complete address digits' value sent in the 'Called party number' parameter in the IAM message, when the nature of address is specified as 'national (sign.) number'. IA5String ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 36 Item Module Parameter Description Type Value 5.4.14.1 PX_ISUP_IAM_CLD_digits_less 'address digits' value (less than minimum number digits to route the call) sent in the 'Called party number' parameter in the IAM message. IA5String 5.4.14.2 PX_ISUP_IAM_CLD_natAddr_less 'nature of address' value (number of digits less than minimum number digits to route the call) sent in the 'Calling party number' parameter in the IAM message. Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.15.1 PX_ISUP_TX_CDN_addrSignals Default value for element addressSignals inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.9. IA5String 5.4.15.2 PX_ISUP_TX_CDN_natOfAddressInd Default value for element natureOfAddressIndicator inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.9. bitstring(7) 5.4.15.3 PX_ISUP_TX_CDN_numbPlanInd Default value for element numberingPlanIndicator inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.9. bitstring(3) 5.4.15.4 PX_ISUP_TX_CDN_iNN Default value for element iNN inside Called party number parameter (CDN); Variable(V) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.9. bitstring(1) Calling party number - receiving 5.5.1 PX_ISUP_IAM_CLI_digits_rxInat Default 'address digits' value received in the 'Calling party number' parameter in the IAM message, when the Called party number is 'international'. Ref.: Q.763 [16], 3.10. IA5String 5.5.2 PX_ISUP_IAM_CLI_digits_rxNat Default 'address digits' value received in the 'Calling party number' parameter in the IAM message, when the Called party number is 'national (sign.) number'. Ref.: Q.763 [16], 3.10. IA5String 5.5.3 PX_ISUP_IAM_CLI_digits_rxDef Default 'address digits' value received in the 'Calling party number' parameter in the IAM message, when the Nature of address is not explicitly specified. Ref.: Q.763 [16], 3.10. IA5String 5.5.4 PX_ISUP_IAM_CLI_numIncmplInd_rxDef Default 'Number incomplete indicator' value received in the 'Calling party number' parameter in the IAM message. Ref.: Q.763 [16], 3.10. bitstring(1) ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 37 Item Module Parameter Description Type Value Calling party number - sending 5.6.1 PX_ISUP_IAM_CLI_digits_txInat Default 'address digits' value sent in the 'Calling party number' parameter in the IAM message, when the Called party number is 'international'. Ref.: Q.763 [16], 3.10. IA5String 5.6.2 PX_ISUP_IAM_CLI_digits_txNat Default 'address digits' value sent in the 'Calling party number' parameter in the IAM message, when the Called party number is 'national (sign.) number'. Ref.: Q.763 [16], 3.10. IA5String Generic number - receiving 5.7.1 PX_ISUP_IAM_GEN_digits_rxInat 'address digits' value received in the 'Generic number' parameter in the IAM message, when the Nature of Address is 'international number'. Ref.: Q.763 [16], 3.26. IA5String 5.7.2 PX_ISUP_IAM_GEN_digits_rxNat 'address digits' value received in the 'Generic number' parameter in the IAM message, when the Nature of Address is 'national (sign.) number'. Ref.: Q.763 [16], 3.26. IA5String Generic number - sending 5.8.1 PX_ISUP_IAM_GEN_digits_txInat 'address digits' value sent in the 'Generic number' parameter in the IAM message, when the Nature of Address is 'international number'. Ref.: Q.763 [16], 3.26. IA5String 5.8.2 PX_ISUP_IAM_GEN_digits_txNat 'address digits' value sent in the 'Generic number' parameter in the IAM message, when the Nature of Address is 'national (sign.) number'. Ref.: Q.763 [16], 3.26. IA5String User-user information 5.9.1 PX_ISUP_IAM_UUI_userInfo_S1 Default 'user-to-user information' value (Service 1 data) sent in the 'User-to-user information' parameter in the IAM message. Ref.: Q.763 [16], 3.61. octetstring 5.9.2 PX_ISUP_IAM_UUI_userInfo_S2 Default 'user-to-user information' value (Service 2 data) sent in the 'User-to-user information' parameter in the IAM message. Ref.: Q.763 3.61. octetstring 5.9.3 PX_ISUP_IAM_UUI_userInfo_S3 Default 'user-to-user information' value (Service 3 data) sent in the 'User-to-user information' parameter in the IAM message. Ref.: Q.763 [16], 3.61. octetstring Cause indicator 5.10.1 PX_ISUP_REL_CAU_cVal_bye 'Cause' value (decimal) received in the 'Cause' parameter in the REL message, when the IW-U has received a BYE message from SIP. Ref.: Q.763 [16], 3.12. integer ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 38 Item Module Parameter Description Type Value 5.10.2 PX_ISUP_REL_CAU_cVal_cancel 'Cause' value (decimal) received in the 'Cause' parameter in the REL message, when the IW-U has received a CANCEL message from SIP. Ref.: Q.763 [16], 3.12. integer 5.10.3 PX_ISUP_REL_CAU_cVal_autonomous 'Cause' value (decimal) received in the 'Cause' parameter in the REL message, when the IWU-O has autonomously released the call. Ref.: Q.763 [16], 3.12. integer 5.10.4 PX_ISUP_REL_CAU_CCBSposs 'Cause value' value sent in the 'Cause' parameter in the REL message, when the diagnostics field indicates 'CCBS possible'. Ref.: Q.763 [16], 3.12. integer Subsequent number 5.11.1 PX_ISUP_SAM_SQN_digits_rx1 'address digits' value (PIXIT) received in the 'Subsequent number' parameter in the first SAM message. Ref.: Q.763 [16], 3.51. IA5String 5.11.2 PX_ISUP_SAM_SQN_digits_rx2 'address digits' value (PIXIT) received in the 'Subsequent number' parameter in the second SAM message. Ref.: Q.763 [16], 3.51. IA5String 5.11.3 PX_ISUP_SAM_SQN_digits_txMidLess 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, containing the middle part of the number, where the IAM contained less than the minimum digits to route the call. Ref.: Q.763 [16], 3.51. IA5String 5.11.4 PX_ISUP_SAM_SQN_digits_txFinLess 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, containing the final part of the number, where the IAM contained less than the minimum digits to route the call. Ref.: Q.763 [16], 3.51. IA5String 5.11.5 PX_ISUP_SAM_SQN_digits_txFinDef 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, completing the (subscriber) number. Ref.: Q.763 [16], 3.51. IA5String 5.11.6 PX_ISUP_SAM_SQN_digits_txMidDef 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, containing the middle part of the complete (subscriber) number. Ref.: Q.763 [16], 3.51. IA5String 5.11.7 PX_ISUP_SAM_SQN_digits_txFinNat Final 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, completing the (national sign.) number. Ref.: Q.763 [16], 3.51. IA5String 5.11.8 PX_ISUP_SAM_SQN_digits_txMidNat Middle 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, not completing the (national sign.) number. Ref.: Q.763 [16], 3.51. IA5String ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 39 Item Module Parameter Description Type Value 5.11.9 PX_ISUP_SAM_SQN_digits_txFinPhone Final 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, where the whole number is mapped to the addr- spec component of the To header field which includes the "user=phone" URI parameter. Ref.: Q.763 [16], 3.51. IA5String 5.11.10 PX_ISUP_SAM_SQN_digits_txFinInat 'address digits' value sent in the 'Subsequent number' parameter in the second SAM message, completing the (international) number. Ref.: Q.763 [16], 3.51. IA5String 5.11.11 PX_ISUP_SAM_SQN_digits_txMidPhone Middle 'address digits' value sent in the 'Subsequent number' parameter in the first SAM message, where the whole number is mapped to the addr- spec component of the To header field which includes the "user=phone" URI parameter. Ref.: Q.763 [16], 3.51. IA5String 5.11.12 PX_ISUP_SAM_SQN_digits_txMidInat 'address digits' value (PIXIT (middle part of standard international address/ to be completed by next SAM)) sent in the 'Subsequent number' parameter in the SAM message. Ref.: Q.763 [16], 3.51. IA5String Backward call indicators 5.12.1 PX_ISUP_TX_BCI_v_chargeInd Default value for element chargeIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(2) 5.12.2 PX_ISUP_TX_BCI_v_cldPStatInd Default value for element calledPartysStatusIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(2) 5.12.3 PX_ISUP_TX_BCI_v_cldPCatInd Default value for element calledPartysCategoryIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(2) 5.12.4 PX_ISUP_TX_BCI_v_eTOeMethodInd Default value for element end_to_endMethodIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(2) ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 40 Item Module Parameter Description Type Value 5.12.5 PX_ISUP_TX_BCI_v_interwInd Default value for element interworkingIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(1) 5.12.6 PX_ISUP_TX_BCI_v_eTOeInfoInd Default value for element end_to_endInformationIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(1) 5.12.7 PX_ISUP_TX_BCI_v_iSDNUserPartInd Default value for element iSDNUserPartIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(1) 5.12.8 PX_ISUP_TX_BCI_v_holdingInd Default value for element holdingIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(1) 5.12.9 PX_ISUP_TX_BCI_v_iSDNAccessInd Default value for element iSDNAccessIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(1) 5.12.10 PX_ISUP_TX_BCI_v_echoContrDevInd Default value for element echoControlDeviceIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(1) 5.12.11 PX_ISUP_TX_BCI_v_sCCPMethodInd Default value for element sCCPMethodIndicator inside Backward call indicators parameter (BCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.5. bitstring(2) Calling party category 5.13 PX_ISUP_TX_CGC_cliPCategory Default value for element callingPartysCategory inside Calling party's category parameter (CGC); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.11. bitstring(8) ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 41 Item Module Parameter Description Type Value Connected number 5.14.1 PX_ISUP_TX_CPN_natOfaddressind Default value for element natureOfaddressindicator inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.16. bitstring(7) 5.14.2 PX_ISUP_TX_CPN_screenInd Default value for element screeningIndicator inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.16. bitstring(2) 5.14.3 PX_ISUP_TX_CPN_addrPresRestrInd Default value for element addrPresRestrInd inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.16. bitstring(2) 5.14.4 PX_ISUP_TX_CPN_numbplanInd Default value for element numberingplanIndicator inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.16. bitstring(3) 5.14.5 PX_ISUP_TX_CPN_addrSignals Default value for element addressSignals inside Connected number parameter (CPN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.16. IA5String Forward call indicators 5.15.1 PX_ISUP_TX_FCI_natInternatCallInd Default value for element natInternatCallIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(1) 5.15.2 PX_ISUP_TX_FCI_endToEndMethodInd Default value for element endToEndMethodIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(2) 5.15.3 PX_ISUP_TX_FCI_interwInd Default value for element interworkingIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(1) 5.15.4 PX_ISUP_TX_FCI_eTOeInfoIndic Default value for element endToEndInfoIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(1) ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 42 Item Module Parameter Description Type Value 5.15.5 PX_ISUP_TX_FCI_iSDNUserPartInd Default value for element iSDNUserPartIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(1) 5.15.6 PX_ISUP_TX_FCI_iSDNUserPartPrefInd Default value for element iSDNUserPartPrefIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(2) 5.15.7 PX_ISUP_TX_FCI_iSDNAccessInd Default value for element iSDNAccessIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(1) 5.15.8 PX_ISUP_TX_FCI_sCCPMethodInd Default value for element sCCPMethodIndicator inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(2) 5.15.9 PX_ISUP_TX_FCI_reserved Default value for element reserved inside Forward call indicators parameter (FCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.23. bitstring(4) Nature of connection indicators 5.16.1 PX_ISUP_TX_NCI_satelliteInd Default value for element satelliteIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.35. bitstring(2) 5.16.2 PX_ISUP_TX_NCI_contCheckInd Default value for element continuityCheckIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.35. bitstring(2) 5.16.3 PX_ISUP_TX_NCI_echoContrDevInd Default value for element echoControlDeviceIndicator inside Nature of connection indicators parameter (NCI); Fixed(F) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.35. bitstring(1) Original called number 5.17.1 PX_ISUP_TX_OCN_natOfAddressInd Default value for element natureOfAddressIndicator inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.39. bitstring(7) ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 43 Item Module Parameter Description Type Value 5.17.2 PX_ISUP_TX_OCN_addrPresRestrInd Default value for element addrPresRestrInd inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.39. bitstring(2) 5.17.3 PX_ISUP_TX_OCN_numbPlanInd Default value for element numberingPlanIndicator inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.39. bitstring(3) 5.17.4 PX_ISUP_TX_OCN_addrSignals Default value for element addressSignals inside Original called number parameter (OCN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.39. IA5String Range and status 5.18.1 PX_ISUP_TX_RAS_range Default value for element range inside Range and status parameter (RAS); Variable(V) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.43. bitstring(8) 5.18.2 PX_ISUP_TX_RAS_status Default value for element status inside Range and status parameter (RAS); Variable(V) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.43. octetstring Redirecting number 5.19.1 PX_ISUP_TX_RDN_natOfAddressInd Default value for element natureOfAddressIndicator inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.44. bitstring(7) 5.19.2 PX_ISUP_TX_RDN_addrPresRestrInd Default value for element addrPresRestrInd inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.44. bitstring(2) 5.19.3 PX_ISUP_TX_RDN_numbPlanInd Default value for element numberingPlanIndicator inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.44. bitstring(3) 5.19.4 PX_ISUP_TX_RDN_addrSignals Default value for element addressSignals inside Redirecting number parameter (RDN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.44. IA5String ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 44 Item Module Parameter Description Type Value Redirection number 5.20.1 PX_ISUP_TX_RNN_natOfAddressInd Default value for element natureOfAddressIndicator inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.46. bitstring(7) 5.20.2 PX_ISUP_TX_RNN_numbPlanInd Default value for element numberingPlanIndicator inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.46. bitstring(3) 5.20.3 PX_ISUP_TX_RNN_iNN Default value for element Internal Network Number indicator inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.46. bitstring(1) 5.20.4 PX_ISUP_TX_RNN_addrSignals Default value for element addressSignals inside Redirection number parameter (RNN); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.46. IA5String Redirection number restriction 5.21 PX_ISUP_TX_RNS_presRestrInd Default value for element presRestrIndicator inside Redirection number restriction parameter (RNS); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.46. bitstring(2) Transmission medium required 5.22 PX_ISUP_TX_TMR_transmMedReq Default value for element transmissionMediumRequirement inside Transmission medium requirement parameter (TMR); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.54. bitstring(8) Hop counter 5.23 PX_ISUP_TX_HPC_hopCounter Default value for element hopCounter inside Hop counter parameter (HPC); Optional(O) format (to be sent when the TP does not specify a specific value for that field). Ref.: Q.763 [16], 3.80. bitstring(5) Unknown parameter/message identifier 5.24.1 PX_ISUP_TX_unknown_parameter_type Default value for an unknown parameter type (to be sent when the TP does not specify a specific value for that field). bitstring(8) 5.24.2 PX_ISUP_TX_unknown_message_type Default value for an unknown message type (to be sent when the TP does not specify a specific value for that field). bitstring(8) ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 45 Item Module Parameter Description Type Value Calling party subaddress 5.25.1 PX_ISUP_TX_cgps_information Default value for calling party subaddress information (to be sent when the TP does not specify a specific value for that field). Ref.: Q.931 [i.1], 4.5.11. octetstring 5.25.2 PX_ISUP_TX_cgps_odd_even_indicator Default value for calling party subaddress odd even indicator (to be sent when the TP does not specify a specific value for that field). Ref.: Q.931 [i.1], 4.5.11. bitstring(1) 5.25.3 PX_ISUP_TX_cgps_type_of_subaddress Default value for calling party subaddress type of subaddress (to be sent when the TP does not specify a specific value for that field). Ref.: Q.931 [i.1], 4.5.11. bitstring(3) NOTE: For Module Parameters containing address digits the following requirement applies: each digit is represented either as one of the IA5 characters "0" to "9", or as one of the special IA5 characters "*", "#", "a", "b" or "c". ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 46 Annex B (informative): TTCN-3 library modules B.1 Electronic annex, zip file with TTCN-3 code The TTCN-3 library modules are contained in archive ts_18600204v010101p0.zip which accompanies the present document. ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 47 Annex C (informative): Bibliography • ETSI TS 102 237-1 (V4.1.1): "Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to interoperability testing". • ETSI EG 202 106 (V2.1.1): "Methods for Testing and Specification (MTS); Guidelines for the use of formal SDL as a descriptive tool". • ISO/IEC 9646-2 (1994): "Conformance testing methodology and framework - Part 2: Abstract Test Suite Specification". • ISO/IEC 9646-3 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation". • ISO/IEC 9646-3/DAM 1 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation; Amendment 1: TTCN extensions". • ISO/IEC 9646-5 (1994): "Conformance testing methodology and framework - Part 5: Requirements on test laboratories and clients for the conformance assessment process". • IETF RFC 1035 (1997): "Domain names - implementation and specification". • ITU-T Recommendation Q.1902.1 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC)". • ITU-T Recommendation Q.1902.2 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC)". • ITU-T Recommendation Q.1902.3 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC)". • ITU-T Recommendation Q.1902.4 (2001): "Specifications of the Bearer Independent Call Control Protocol (BICC)". • ITU-T Recommendation Q.731.7 (1997): "Stage 3 description for number identification supplementary services using Signalling System No. 7: Malicious call identification (MCID)". • ITU-T Recommendation Q.732.2 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call diversion services - Call Forwarding Busy (CFB)". • ITU-T Recommendation Q.732.3 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding No Reply (CFNR)". • ITU-T Recommendation Q.732.4 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding Unconditional (CFU)". • ITU-T Recommendation Q.732.5 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Deflection (CD)". • ITU-T Recommendation Q.732.7 (1996): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Explicit Call Transfer". • ITU-T Recommendation Q.733.1 (1992): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call waiting (CW)". • ITU-T Recommendation Q.733.2 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call hold (HOLD)". • ITU-T Recommendation Q.733.3 (1997): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls to busy subscriber (CCBS)". ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 48 • ITU-T Recommendation Q.733.4 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Terminal portability (TP)". • ITU-T Recommendation Q.733.5 (1999): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls on no reply". • ITU-T Recommendation Q.734.1 (1993): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Conference calling". • ITU-T Recommendation Q.734.2 (1996): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Three-party service". • ITU-T Recommendation Q.735.1 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Closed user group (CUG)". • ITU-T Recommendation Q.735.3 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Multi-level precedence and preemption". • ITU-T Recommendation Q.735.6 (1996): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Global Virtual Network Service (GVNS)". • ITU-T Recommendation Q.736.1 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: International Telecommunication Charge Card (ITCC)". • ITU-T Recommendation Q.736.3 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: Reverse charging (REV)". • ITU-T Recommendation Q.737.1 (1997): "Stage 3 description for additional information transfer supplementary services using Signalling System No. 7: User-to-user signalling (UUS)". • ITU-T Recommendation Q.850 (1998): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". • IETF RFC 2046 (1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". • IETF RFC 2327 (1998): "SDP: Session Description Protocol". • IETF RFC 2806 (2000): "URLs for Telephone Calls". • IETF RFC 3204 (2001): "MIME media types for ISUP and QSIG Objects". • IETF RFC 3262 (2002): "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". • IETF RFC 3264 (2002): "An Offer/Answer Model with the Session Description Protocol (SDP)". • IETF RFC 3311 (2002): "The Session Initiation Protocol UPDATE Method". • IETF RFC 3312 (2002): "Integration of Resource Management and Session Initiation Protocol (SIP)". • IETF RFC 3323 (2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)". • IETF RFC 3326 (2002): "The Reason Header Field for the Session Initiation Protocol". ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 49 Annex D (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 05-11-08 19PTD034r1 001 F Update of TTCN-3 code 1.0.0 1.0.1 27-01-09 20PTD048 002 F Update of TTCN-3 code 1.0.1 1.0.2 Publication 1.0.1 1.1.1 ETSI ETSI TS 186 002-4 V1.1.1 (2009-05) 50 History Document history V1.0.0 April 2008 Publication V1.1.1 May 2009 Publication
|
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 for Testing (PIXIT) proforma based on the present document. Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 610: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.610 version 8.3.0 Release 8)". [2] ETSI TS 186 007-1: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Communication HOLD (CH); Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts".
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
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.
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
3 Definitions and abbreviations
| |
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions given in TS 124 610 [1] and the following apply: Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3]. ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 6 PICS proforma: Refer to ISO/IEC 9646-1 [3]. point of control and observation: Refer to ISO/IEC 9646-1 [3]. Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3]. System Under Test (SUT): Refer to ISO/IEC 9646-1 [3]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 610 [1] and the following apply: TSS Test Suite Structure
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
4 Test Suite Structure (TSS)
|
ServedUser WithUPDATE CH_U01_xxx WithoutUPDATE CH_U02_xxx Figure 1: Test suite structure 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 124 610 [1]. The stage 3 description describes the requirements for several network entities and also the requirments regarding for terminal devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities. Therefore to test the appropriate entities the configurations below are applicable. 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 tesst of the AS using any NNI (Mw, Mg, Mx) interface (see figure 3). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible. ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 7 CSCF (and/or AS) Implementation under Test Test System Test System Mw, Mg, Mx Mw, Mg, Mx Figure 3: Applicable interfaces for tests using a (generic) NNI interface 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 below has been chosen. User Equipment Implementation under Test Test System Gm Figure 4: Applicable configuration to test UE functionalities
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
5 Test Purposes (TP)
| |
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
5.1 Introduction
|
For each test requirement a TP is defined.
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-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). ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 8 Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "CH" <iut> = type of IUT: U User N Network <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
5.1.2 Test strategy
|
As the base standard TS 124 610 [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 007-1 [2].
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
5.2 User TPs for HOLD
|
All PICS items referred to in this clause are as specified in TS 186 007-1 [2] unless indicated otherwise by another numbered reference.
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
5.2.1 Served user
| |
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
5.2.1.1 Communication Hold with support for UPDATE
|
TSS ServedUser/WithUPDATE TP CH_U01_001 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session hold. UPDATE method is used. Individual media streams are affected. The media stream was previously set to sendrecv. Ensure that the IUT to hold an individual media stream of the communication session, sends an UPDATE request containing an sdp body with an attribute line indicating 'a= sendonly'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'sendrecv' • Individual media streams Comments: User Equipment Test Equipment UPDATE(sendonly) TSS ServedUser/WithUPDATE TP CH_U01_002 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session hold. UPDATE method is used. Individual media streams are affected. The media stream was previously set to recvonly. Ensure that the IUT to hold an individual media stream of the communication session, sends an UPDATE request containing an sdp body with an attribute line indicating 'a=inactive'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'recvonly' • Individual media streams Comments: User Equipment Test Equipment UPDATE(inactive) ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 9 TSS ServedUser/WithUPDATE TP CH_U01_003 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session resume. UPDATE method is used. Individual media streams are affected. The media stream was previously set to sendonly. Ensure that the IUT to resume an individual media stream of the communication session, sends an UPDATE request containing an sdp body with an attribute line indicating 'a=sendrecv' or without attribute line. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'sendonly' • Individual media streams Comments: User Equipment Test Equipment UPDATE(sendrecv or empty) TSS ServedUser/WithUPDATE TP CH_U01_004 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session resume. UPDATE method is used. Individual media streams are affected. The media stream was previously set to inactive. Ensure that the IUT to resume an individual media stream of the communication session, sends an UPDATE request containing an sdp body with an attribute line indicating 'a=recvonly'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'inactive' • Individual media streams Comments: User Equipment Test Equipment UPDATE(sendonly) TSS ServedUser/WithUPDATE TP CH_U01_005 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session hold. UPDATE method is used. All media streams are affected. The media stream were previously set to sendrecv. Ensure that the IUT to hold all media streams of the communication session, sends an UPDATE request containing an sdp body with a session level direction attribute line indicating 'a=sendonly'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'sendrecv' • Individual media streams Comments: User Equipment Test Equipment UPDATE(sendonly) ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 10 TSS ServedUser/WithUPDATE TP CH_U01_006 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session hold. UPDATE method is used. All media streams are affected. The media stream were previously set to recvonly. Ensure that the IUT to hold all media streams of the communication session, sends an UPDATE request containing an sdp body with a session level direction attribute line indicating 'a=inactive'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'recvonly' • Individual media streams Comments: User Equipment Test Equipment UPDATE(inactive) TSS ServedUser/WithUPDATE TP CH_U01_007 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session resume. UPDATE method is used. All media streams are affected. The media stream were previously set to sendonly. Ensure that the IUT to resume all media streams of the communication session, sends an UPDATE request containing an sdp body with a session level direction attribute line indicating 'a=sendrecv' or without attribute line. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'sendonly' • Individual media streams Comments: User Equipment Test Equipment UPDATE(sendrecv or empty) TSS ServedUser/WithUPDATE TP CH_U01_008 HOLD reference 4.5.2.1 Selection expression PICS 1/2 Test purpose: Session resume. UPDATE method is used. All media streams are affected. The media streams were previously set to inactive. Ensure that the IUT to resume all media streams of the communication session, sends an UPDATE request containing an sdp body with a session level direction attribute line indicating 'a=recvonly'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'inactive' • Individual media streams Comments: User Equipment Test Equipment UPDATE(sendonly)
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-2
|
5.2.1.2 Communication Hold without support for UPDATE
|
TSS ServedUser/WithoutUPDATE TP CH_U02_001 HOLD reference 4.5.2.1 Selection expression Test purpose: Session hold. UPDATE method is not used. Individual media streams are affected. The media stream was previously set to sendrecv. Ensure that the IUT to hold an individual media stream of the communication session, sends a ReINVITE request containing an sdp body with an attribute line indicating 'a=sendonly'. ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 11 Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'sendrecv' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(sendonly) TSS ServedUser/WithoutUPDATE TP CH_U02_002 HOLD reference 4.5.2.1 Selection expression Test purpose: Session hold. UPDATE method is not used. Individual media streams are affected. The media stream was previously set to recvonly. Ensure that the IUT to hold an individual media stream of the communication session, sends a ReINVITE request containing an sdp body with an attribute line indicating 'a=inactive'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'recvonly' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(inactive) TSS ServedUser/WithoutUPDATE TP CH_U02_003 HOLD reference 4.5.2.1 Selection expression Test purpose: Session resume. UPDATE method is not used. Individual media streams are affected. The media stream was previously set to sendonly. Ensure that the IUT to resume an individual media stream of the communication session, sends a ReINVITE request containing an sdp body with an attribute line indicating 'a=sendrecv' or without attribute line. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'sendonly' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(sendrecv or empty) TSS ServedUser/WithoutUPDATE TP CH_U02_004 HOLD reference 4.5.2.1 Selection expression Test purpose: Session resume. UPDATE method is not used. Individual media streams are affected. The media stream was previously set to inactive. Ensure that the IUT to resume an individual media stream of the communication session, sends a ReINVITE request containing an sdp body with an attribute line indicating 'a=recvonly'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • The media stream was previously set to 'inactive' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(sendonly) ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 12 TSS ServedUser/WithoutUPDATE TP CH_U02_005 HOLD reference 4.5.2.1 Selection expression Test purpose: Session hold. UPDATE method is not used. All media streams are affected. The media stream were previously set to sendrecv. Ensure that the IUT to hold all media streams of the communication session, sends a ReINVITE request containing an sdp body with a session level direction attribute line indicating 'a=sendonly'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'sendrecv' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(sendonly) TSS ServedUser/WithoutUPDATE TP CH_U02_006 HOLD reference 4.5.2.1 Selection expression Test purpose: Session hold. UPDATE method is not used. All media streams are affected. The media stream were previously set to recvonly. Ensure that the IUT to hold all media streams of the communication session, sends a ReINVITE request containing an sdp body with a session level direction attribute line indicating 'a=inactive'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'recvonly' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(inactive) TSS ServedUser/WithoutUPDATE TP CH_U02_007 HOLD reference 4.5.2.1 Selection expression Test purpose: Session resume. UPDATE method is not used. All media streams are affected. The media stream were previously set to sendonly. Ensure that the IUT to resume all media streams of the communication session, sends a ReINVITE request containing an sdp body with a session level direction attribute line indicating 'a=sendrecv' or without attribute line. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'sendonly' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(sendrecv or empty) ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 13 TSS ServedUser/WithoutUPDATE TP CH_U02_008 HOLD reference 4.5.2.1 Selection expression Test purpose: Session resume. UPDATE method is not used. All media streams are affected. The media streams were previously set to inactive. Ensure that the IUT to resume all media streams of the communication session, sends a ReINVITE request containing an sdp body with a session level direction attribute line indicating 'a=recvonly'. Precondition: • A session was established between the served user and a remote user according to the 'basic Call' procedures • All media streams were previously set to 'inactive' • Individual media streams Comments: User Equipment Test Equipment ReINVITE(sendonly)
|
574bdb176b57d4ef38a2d306f32039b2
|
186 007-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 cases; d) maintain the relationship specified in clause 5 between the test groups and TPs and the entries in the PICS proforma to be used for test case deselection. In the case of a) or b) above, a subset shall be used only where a particular Abstract Test Method (ATM) makes some TPs untestable. All testable TPs from clause 5 shall be included in a compliant ATS. ETSI ETSI TS 186 007-2 V3.1.1 (2011-08) 14 History Document history V1.1.1 July 2006 Publication V3.1.1 August 2011 Publication
|
8b829831b46dc8e03e84642342a48b60
|
186 006-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 006-2 [2]. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specification and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
8b829831b46dc8e03e84642342a48b60
|
186 006-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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
8b829831b46dc8e03e84642342a48b60
|
186 006-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 607: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.607 version 8.4.0 Release 8)". [2] ETSI TS 186 006-2 (V3.1.1): "Technical Committee for IMS Network Testing (INT); Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Testing; Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [3] ETSI TS 102 790-3: "Technical Committee for IMS Network Testing (INT); Network Integration Testing; IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification". ETSI ETSI TS 186 006-3 V3.1.1 (2012-01) 6 [4] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [6] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [7] ETSI ES 201 873-1 (V4.3.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [8] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [9] ETSI TS 102 587-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Conformance testing for the Peer-to-Peer Digital Private Mobile Radio; Part 2: Test Suite Structure and Test Purposes (TSS&TP) specification". [10] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication".
|
8b829831b46dc8e03e84642342a48b60
|
186 006-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.
|
8b829831b46dc8e03e84642342a48b60
|
186 006-3
|
3 Definitions and abbreviations
| |
8b829831b46dc8e03e84642342a48b60
|
186 006-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.
|
8b829831b46dc8e03e84642342a48b60
|
186 006-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 607 [1] apply.
|
8b829831b46dc8e03e84642342a48b60
|
186 006-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. ETSI ETSI TS 186 006-3 V3.1.1 (2012-01) 7
|
8b829831b46dc8e03e84642342a48b60
|
186 006-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 The ISC interface provides an access to the AP. SUT IMS AS ISC TS Figure 2: Test configuration CF_1ISC
|
8b829831b46dc8e03e84642342a48b60
|
186 006-3
|
5 The ATS development process
| |
8b829831b46dc8e03e84642342a48b60
|
186 006-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 5 of TS 186 006-2 [2]. The requirements applicable to this TP are given by a reference to TS 124 607 [1]. There are no explicit formulations of requirements.
|
8b829831b46dc8e03e84642342a48b60
|
186 006-3
|
5.2 ATS structure
| |
8b829831b46dc8e03e84642342a48b60
|
186 006-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 006-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 006-2 [2], but use the naming conventions defined for the ATS (see clause 5.2.2). Table 1: OIP/OIR ATS structure OIP/OIR CallingUser OIP_U01_xxx CalledUser OIP_U02_xxx AS_OrigUser OIP_N01_xxx AS_TermUser OIP_N02_xxx
|
8b829831b46dc8e03e84642342a48b60
|
186 006-3
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" ETSI ETSI TS 186 006-3 V3.1.1 (2012-01) 8 where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in Table 1 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit decimal number, starting in each subgroup path with "001". EXAMPLE: TC_OIP_N01_001: i) the identifier has Group index "OIP_N01", i.e. it is in the subgroup having complete path: SupplementaryServices_OIP_OIR/AS_OrigUser; ii) the identifier is the first test case of this group/subgroup. NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 006-2 [2] and test case names. The TP identifier of TC_OIP_N01_001 is TP OIP_N01_001.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.