hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.4 Slip rate | |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.4.1 Normal conditions | The slip rate under normal conditions is covered in Recommendation ITU-T Q.541 [i.5]. |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.4.2 Temporary loss of timing control | The case of temporary loss of timing control corresponds to the "holdover operation" defined and recommended in Recommendation ITU-T G.812 [i.6]. The allowable slip rate will correspond to the maximum relative TIE also recommended therein. |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.4.3 Abnormal conditions at the exchange input | The slip rate in case of abnormal conditions (wide phase deviations, etc.) at the exchange input is the subject of further study taking into account the requirements of Recommendation ITU-T G.823 [i.7]. ETSI ETSI TS 186 025-4 V2.2.1 (2013-06) 28 History Document history V2.1.1 July 2011 Publication V2.2.1 June 2013 Pub... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 1 Scope | The present document describes the Abstract Test Suite (ATS) to test interoperability at IMS NNI for IP multimedia call control protocol based on [1]. The ATS has been specified on the basis of the Test Descriptions for IMS NNI interoperability testing presented in TS 186 011-2 [3]. It defines a TTCN-3 framework as wel... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 283 003 (V1.8.0): "Telecommunications and Int... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI ES 201 873-1: "Methods for Testing and Spec... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS (IMS) Application Server ATS Abstract Test Suite CSCF Call Session Control Function IBCF Interconnection Border Control Gateway I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IP Internet Protocol MTC Main Test Component NNI Network t... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 4 Overview | |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 4.1 Network architecture | The ATS is defined to observe the SIP communication at the Gm, Mw and ISC interface of two IMS core networks for interoperability testing. Figure 1 shows a general architecture of two IMS core networks including the related interfaces. ETSI ETSI TS 186 011-3 V2.2.1 (2009-09) 7 UE AS P-CSCF I-CSCF S-CSCF IBCF IMS core U... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 4.1.1 Core IMS Nodes | The P-CSCF, S-CSCF, I-CSCF and the IBCF are considered to be within a "black box" for testing purposes, i.e. the System Under Test (SUT). Interfaces within the IMS are considered internal and not observable for testing purposes. The Mw interface between two IMS core networks is used as point of observation (PO) for NNI... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 4.1.2 External IMS Nodes | |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 4.1.2.1 UE | The UE is considered to act as stimulus node in this test specification. The Gm interface between the P-CSCF and the UE is used as a Point of Control and Observation (PCO) for NNI interoperability tests. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 4.1.2.2 AS | The Application Server (AS) is considered to act as a stimulus node in this test specification. The ISC interface between the S-CSCF and the AS is used as Point of Control and Observation (PCO) for NNI interoperability tests. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 5 Test configuration | The test configuration is described in detail in TS 186 011-2 [3]. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 6 Test system architecture | Figure 2 illustrate the IMS NNI interoperability test system. The test system architecture is based on the general TTCN-3 test system architecture specified in ES 201 873-6 [5] and ES 201 873-5 [4]. ETSI ETSI TS 186 011-3 V2.2.1 (2009-09) 8 Test System UE A IMS A IMS B UE B AS A AS B MTC Test Adapter gmIN gmIN gmIN gmI... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 6.1 Test Adapter requirements | The test system needs to provide a TA that is able to read a trace file from previous test session including trace information from all relevant interfaces, i.e. Gm, ISC, Mw, and IC. Based on the configured association of IP addresses and ports with TSI ports the TA should enqueue SIP messages matching these addresses ... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 6.1.1 Test adapter configuration | The test system expects the TA to be configurable by primitives sent via the configuration TSI port. These primitives provide all necessary information required to enqueue captured SIP messages at specific TSI ports. To trigger the exchange of these configuration primitives the following functions are used: Function Pa... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 6.2 Codec requirements | The test system needs to provide a full SIP codec which includes also decoding of XML message bodies. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 7 Test design | The ATS has been specified using a library approach. Each library layer is composed of multiple TTCN-3 modules. The libraries are defined in different layers which build on top of each other: • TracePlay Library: A collection of common TTCN-3 definitions and functions related to the configuration of the test adapter. T... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 7.1 Naming Conventions | The naming convention used in this test suite are based on the general principles specified in [i.2]. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 7.2 Documentation | In order to allow browsing of the ATS without the use of a specific TTCN-3 test development tool, this test suite has been documented using TTCN-3 documentation comments defined in [6]. The tags and their usage are summarized in the table below. Tag Description @author Specifies the names of the authors or an authoring... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 7.3 Mapping of test descriptions to test cases | The test cases defined in the ATS follow the naming convention TC_<TD_ID>. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8 Test execution | |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.1 Execution modes | The ATS contains two different execution modes: A normal mode and a simulation mode. The execution mode can be enabled by setting the PX_TA_SIMULATION_MODE module parameter to true. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.1.1 Normal mode | In the normal mode the captured messages will be enqueued at the test component associated with the destination IP address. This mode is useful to see all captured message in TTCN-3 logging in case of IP address conflicts, e.g., when a IMS node receives a message from a unspecified IP address. |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.1.2 Simulation mode | In the simulation mode all messages are enqueued at the test component associated with the source IP address. This test component then forwards this message to the destination component via intercomponent communication. This mode enables the illustration of the captured call flow in TTCN-3 logging. ETSI ETSI TS 186 011... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.2 PIXIT | |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.2.1 Address List Information | |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.2.1.1 User A | • PX_ETS_UE1_ADDR: Address List of User A containing Domain, IP address and Port number. • PX_ETS_UE1_SIP: User A SIP user name. • PX_ETS_UE1_SIP_NUMBER: User A SIP user number (phone number using SIP schema). • PX_ETS_UE1_TEL_NUMBER: User A phone number. • PX_ETS_UE1_BARRED: SIP user name of a barred user. • PX_ETS_UE... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.2.1.2 User B | • PX_ETS_UE2_ADDR: Address List of User B containing Domain, IP address and Port number. • PX_ETS_UE2_SIP: User B SIP user name. • PX_ETS_UE2_SIP_NUMBER: User B SIP user number (phone number using SIP schema). • PX_ETS_UE2_TEL_NUMBER: User B phone number. • PX_ETS_UE2_BARRED: SIP user name of a barred user. • PX_ETS_UE... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.2.1.3 IMS A | • PX_ETS_PCSCF1_ADDR: Address List of P-CSCF containing Domain, IP address and Port number. • PX_ETS_SCSCF1_ADDR: Address List of S-CSCF containing Domain, IP address and Port number. • PX_ETS_ICSCF1_ADDR: Address List of I-CSCF containing Domain, IP address and Port number. • PX_ETS_IBCF1_ADDR: Address List of IBCF co... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.2.1.4 IMS B | • PX_ETS_PCSCF2_ADDR: Address List of P-CSCF containing Domain, IP address and Port number. • PX_ETS_SCSCF2_ADDR: Address List of S-CSCF containing Domain, IP address and Port number. • PX_ETS_ICSCF2_ADDR: Address List of I-CSCF containing Domain, IP address and Port number. • PX_ETS_IBCF2_ADDR: Address List of IBCF co... |
320381f60d052d2b1060ecc4577deb9a | 186 011-3 | 8.2.2 Miscellaneous | • PX_TA_SESSION_ID: A parameter that may be used by the test adapter to locate a trace file, e.g. folder name. ETSI ETSI TS 186 011-3 V2.2.1 (2009-09) 12 • PX_ENQUEUE_TIMER: Guard time to stop waiting for messages from test adapter. • PX_TA_SIMULATION_MODE: Indicates the mode used for test execution. • PX_TA_IGNORE_MES... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 1 Scope | The present document is for an initial release of a PSTN/ISDN Emulation Sub-system (PES) performance benchmark. The same tests can be used also for legacy PSTN/ISDN networks or for inter-working tests between PSTN/ISDN emulation subsystem and legacy PSTN and ISDN. The metrics measured and reported are for performance o... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 186 025-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark; Part 1: Core Concepts". [2] ITU-T Recommendation Q.543: "Digital exchang... |
01b2340d751e820f1bc4db570416d49d | 186 025-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. [i.1] ETSI TS 186 025-3: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark P... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 3 Definitions and abbreviations | |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: background load: workload applied to an SUT during a benchmark test, for the purpose of consuming SUT resources during a benchmark test and changing the traffic intensity at which the capacity of the SUT is reached benchmark report: do... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: A-BGF Access Border Gateway Function AGCF Access Gateway Control Function AGF Access Gateway Function AS Application Server BC Bearer Capability BHCA Busy Hour Call Attempts BRI Basic Rate Interface CAPS Call Attempts Per Second CLIP Calling L... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 4 System Under Test (SUT) | The IMS/PES performance benchmark covers benchmark tests for the PSTN/ISDN Emulation Sub-system (PES), The same tests can be used also for legacy PSTN/ISDN networks or for inter-working tests between PSTN/ISDN emulation subsystem and legacy PSTN and ISDN. The following functional entities appear to be necessary from th... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5 Use cases | This clause defines a set of basic use cases which can be provided simultaneously. Described are ISDN - ISDN, ISDN - PSTN and PSTN-PSTN use cases. They can be handled by the PSTN/ISDN emulation subsystem, by the legacy PSTN/ISDN or as inter-working between PSTN/ISDN emulation subsystem and legacy PSTN and ISDN. Describ... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1 ISDN Use cases | |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.1 ISDN - ISDN Use case 1 | |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.1.1 ISDN - ISDN Scenario 1.1 Basic call with BC = speech - enblock sending | This use case represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. 5.1.1.2 ISDN - ISDN Scenario 1.2 Basic call with BC = speech - enblock sending This scenario represents the case when the call establishment using en-bloc sending is pe... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.1.7 ISDN - ISDN Scenario 1.7 Basic call with BC = 3,1 kHz with PI#3 | This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the called user. 5.1.1.8 ISDN - ISDN Scenario 1.8 Basic call with BC = 3,1 kHz - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s) This scenario represents the case when in the a... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.1.10 ISDN - ISDN Scenario 1.10 Basic call with BC = UDI - enblock sending | This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.1.11 ISDN - ISDN Scenario 1.11 Basic call with BC = UDI - enblock sending | This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the called user. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.1.12 ISDN - ISDN Scenario 1.12 - called user is user determined user busy | This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user with cause value # 17. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.1.13 ISDN - ISDN Scenario 1.13 - no answer from the called user | This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiate call clearing to the calling user with the cause value # 18. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.2 ISDN- PSTN Use case 2 | |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.2.1 ISDN - PSTN Scenario 2.1 Basic call with BC = speech - enblock sending | This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. 5.1.2.2 ISDN - PSTN Scenario 2.2 Basic call with BC = speech - enblock sending This scenario represents the case when the call establishment using en-bloc sending is pe... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.2.3 ISDN - PSTN Scenario 2.3 Basic call - overlap sending with BC = speech | This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. 5.1.2.4 ISDN - PSTN Scenario 2.4 Basic call with BC = 3,1 KHz audio - Fax with 33,6 kbit/s This scenario represents the case when in the active cal... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.2.8 ISDN - PSTN Scenario 2.8 - called user is user determined user busy | This scenario represents the case, when the called user is user determined user busy. the network initiates call clearing to the calling user with cause value # 17. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.2.9 ISDN - PSTN Scenario 2.9 - no answer from the called user | This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiates call clearing to the calling user with the cause value # 18. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.3 PSTN - ISDN Use Case 3 | 5.1.3.1 PSTN - ISDN Scenario 3.1 Basic call, the call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. 5.1.3.2 PSTN - ISDN Scenario 3.2 Basic call, the call is released from the called user This scenario r... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.3.5 PSTN - ISDN Scenario 3.5 Basic call with BC = 3,1 KHz audio - Modem V.90 | This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.3.6 PSTN - ISDN Scenario 3.6 - called user is user determined user busy | This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 14 |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.3.7 PSTN - ISDN Scenario 3.7 - no answer from the called user | This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiate call clearing to the calling user. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.4 PSTN - PSTN Use case 4 | 5.1.4.1 PSTN - PSTN Scenario 4.1 Basic call, the call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. 5.1.4.2 PSTN - PSTN Scenario 4.2 Basic call, the call is released from the called user This scenario r... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.4.4 PSTN - PSTN Scenario 4.4 Basic call with Fax with 14,4 kBit/s | This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly. The echo cancellers in the GW are activated. 5.1.4.5 PSTN - PSTN Scenario 4.5 Basic call with BC = 3,1 KHz audio - Modem V.34 (up to 33,6 kbit/s) This scenario represents the case w... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.4.7 PSTN - PSTN Scenario 4.7 - called user is user busy | This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.1.4.8 PSTN - PSTN Scenario 4.8 - no answer from the called user | This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiate call clearing to the calling user. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 15 |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.2 Metrics and design objectives | 5.2.1 Delay probability - non-ISDN or mixed (ISDN - non-ISDN) environment This clause defines delay parameters related to non-ISDN environment and mixed (ISDN - non-ISDN) environment. The values will be defined in TS 186 025-4 [i.2]. Table 1: Delay parameters related to non-ISDN environment and mixed (ISDN - non-ISDN) ... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.2.2 Speech quality analysis | This clause defines a set of parameters which enables the speech quality analysis of the system under test. They are divided in three parts: speech quality, speech level and PESQ offset. Table 2 shows the speech quality parameters based on PESQ. Table 3 shows the speech level parameters. Table 4 shows the PESQ offset p... |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.3 Call Profiler Traffic Patterns | This clause defines call profiles which are nowadays implemented in benchmark test systems. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.3.1 Saw Tooth | The Saw Tooth ramps up to a peak number of calls and then ramps down from peak. Figure 3: Example of saw tooth call profile |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.3.2 Blast | Blast - all calls go off-hook simultaneously, are connected for a specified time, and then disconnected. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 20 Figure 4: Example of saw tooth call profile |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.3.3 Rolling Blast | Rolling Blast - a defined set of channels go off-hook at once, and the pattern is repeated for all assigned channels. 5.3.4 Ramp Ramp - gradually increases connected calls to a specified number and then maintains those number of calls. Num ber off calls Figure 5 |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.3.5 Steady Call Rate | Steady Call Rate - delivers a fixed, regulated call rate into the system under test. |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.3.6 Poisson Distribution | Poisson Distribution - defines call arrival rate by a statistical distribution. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 21 0 50 100 150 200 250 300 350 400 450 1 9 17 25 33 41 49 57 65 73 81 89 97 105 113 121 129 137 145 153 161 169 177 185 193 201 Figure 6 |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.4 Load Concepts and Definitions | |
01b2340d751e820f1bc4db570416d49d | 186 025-2 | 5.4.1 Processor Load | Processor load is the part of time the processor executes work, normally expressed in percent. The processor load consists of idle load, Traffic load and Usage load. The Idle load is the load that is not dependent on the traffic or other external activities. Figure 7: Processor load The Usage load is the load that is r... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-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 Testsuite Structure and Testpurposes defined in TS 186 016-2 [3]. The TSS&TP have been developed to test the Closed User Group (CUG) PSTN/ISDN simulation services.... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 183 054: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Protocol specification Closed User Group (CUG)". [2] Void. [3] ETSI TS 186... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework". |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 3 Definitions and abbreviations | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-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 [16] and ISO/IEC 9646-1 [5] apply. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 8 |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5] ISO/IEC 9646-7 [6] and the following apply: NOTE: Abbreviations have been used both in the present document and in the TTCN-3 library modules (annex B). AS Application Server ATS Abstract Test Suite CSCF Call Session Control Functio... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4 Abstract Test Method (ATM) | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.1 Network architecture | The SUT is assumed as a complete IMS core network and contains the following components: P-CSCF, I/S-CSCF, E-CSCF and IBCF. As illustrated in the following figure the PCOs for the communication between the systems are Gm, Mw, Ic and Isc. Each component can play role of SUT. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 9 Fig... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.2 Protocol architecture | The Implementation Under Test (IUT) for which this test case specification applies consists of the SIP protocol (see figure 2). SUT IMS CN SIP/IMS Extension SIP RFC 3261 Compression algorithms (2) UDP TCP Security Algorithms (2) IPV4/IPV6 (1) (LAN) Figure 2: SIP protocol architecture AS IMSx IMSy UE IMS Mw Ic Isc Gm SI... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3 Test architecture | The target SUT to be covered by the test purposes of TS 186 016-2 [3] address the IMS functional entities that are accessible via the following interfaces: Gm, Mw, Ic and ISC. This clause introduces the test configurations that have been used for the test purpose definitions. Depending on the specific configuration the... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.1 Test configuration | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.1.1 Configuration using Gm interface | The Gm interface is located between UE and IMS. UE1 SUT IMS P gm ue1home PCSCFwithHomeUE UE1 SUT IMS P gm ue1home PCSCFwithHomeUE Figure 3: Test configuration with CF_1Ue IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome Figure 4: Test co... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.1.2 Configuration using ISC interface | The ISC interface provides an access to the AS. AS SUT IMS S isc AS ue1home SCSCFwithHomeUE AS SUT IMS S isc AS ue1home SCSCFwithHomeUE Figure 5: Test configuration with CF_1Scscf ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 11 AS IMS SUT S isc P AS ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome AS IMS SUT S isc P ... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.1.3 Configuration using Mw and Ic interfaces | The Mw or Ic interface is located between two different IMS, e.g. due to at least one user visiting a network outside of the home network. IMS SUT mw IMS TS B UE uehome IBCFwithHomeUE IMS TS I UE uehome ICSCFwithHomeUE ic IMS SUT mw IMS TS B UE uehome IBCFwithHomeUE IMS TS I UE uehome ICSCFwithHomeUE ic Figure 7: Test ... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2 Test system architecture | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.1 General | Test systems that implement this ATS shall conform to the requirements as defined in this clause. |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.2 Structure | An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 8 and also stated in ES 201 873-5 [9]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.3.1 Sending and receiving SIP/IMS messages | Before starting a test case, the SA shall provide the transport of SIP messages by establishing appropriate connections on the lower layers (shown in figure 2). In order to forward messages received into the SA to the test suite and to send them to the SUT a clear and unique association between the TTCN-3 TSI ports and... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.3.2 Security and messages compression feature | Security transport layer and signalling compression may be used transparently to the ATS. |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.3.3 Additional SA constraints | In order to execute this test suite the SA should support: • communication channel handling (at least UDP and possibly also TCP); • IPv4 transport. |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.4 Encoding/Decoding requirements | |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers | SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use a EDS to parse received encoded messages into TTCN-3 type structures and values and encode structured TTCN-3 type structures and values into encoded messages. This E... |
1c05c7a53a8cd51ab3896ff621be2d4f | 186 016-3 | 4.3.2.5 Platform adaptation requirements | For the execution of this test suite implementations of the following external functions have to be provided (see table 3; LibSip_Steps): 1) rndStr() return charstring; returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case; 3) getIpAddr(char... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.