hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
320381f60d052d2b1060ecc4577deb9a
|
186 011-3
|
8.1 Live versus offline test execution
|
Automated interoperability testing can be used with either live (or "in real time") or an offline test execution settings. In the live case the test suite operates user equipment (or instructs to operate it) and analysis a live capture. In the offline case it is simply assumed that equipment operation has been performed manually and that relevant traffic on all interfaces has been captured in one or more traffic capture trace files, e.g. in a PCAP file in the case of IMS NNI IOT. Interesting or valuable results arise when test cases fail, but often, e.g. due to the challenging testing conditions at an interoperability event which only offers a very limited amount of time or incorrect EUT interface information, it is not possible to analyze results and find out the reasons for a failure especially of conformance assessments in real time. For this reason it is a requirement to an automated interoperability test system to provide a test execution mode that allows to work based purely on interface traces. This test suite supports both approaches. The default execution mode is e_offline. The test execution module parameter PX_TEST_EXECUTION has to be set to the value to "e_live" to enable the use of the real time mode. ETSI ETSI TS 186 011-3 V4.1.3 (2012-05) 22
|
320381f60d052d2b1060ecc4577deb9a
|
186 011-3
|
8.2 Unavailable monitored interfaces
|
During or after an interoperability test, one or more EUT interfaces may not be available for monitoring during test execution analysis. This test suite uses module parameters to indicate the availability of each monitored interface in a test and assumes that by default all interfaces are available. In order to deactivate either an interface monitor component its respective PIXIT, e.g. PIXIT_ISC_A_AVAILABLE should be set to "false". Note that the PIXIT settings are taken into account in all test executions. The effect of removing an interface is that it is not included in the verdict resolution. In the handling of the conformance verdict it results however to a reduction of the pass into an inconclusive verdict in case the test contains one or more explicit checks on a disabled monitored interface.
|
320381f60d052d2b1060ecc4577deb9a
|
186 011-3
|
8.3 Test case selection
|
When selecting test cases, different aspects have to be considered. Test may be selected based on a grouping. Tests can be grouped as follows: • functionality to test: If a certain functionality need to be tested, the test belonging to this functionality should be selected, e.g. in IMS registration, call, or messaging; • test configurations: If the test are selected based on test configurations, the effort to reconfigure the test system is as minimal as possible; • pre-test conditions: This is suggested if certain pre-test-conditions are repeatable in the test description, but , cannot be fulfilled. Therefore, these tests would have to be skipped; • priority: If a priority has been assign to the tests, the tests should be selected based on the priority. Note that the above list is not exhaustive. Based on the aim of testing and available resource, new groups can be added. Also, the test selection can be based on more than one groups.
|
320381f60d052d2b1060ecc4577deb9a
|
186 011-3
|
8.4 PIXIT
| |
320381f60d052d2b1060ecc4577deb9a
|
186 011-3
|
8.4.1 LibIot_PIXITS
|
PX_TTCN3_VERDICT PIXIT defines which verdict (E2E or conformance)is to be kept track of with the TTCN-3 verdict. PX_MAX_MSG_WAIT Maximum time limit used by monitor component for waiting for expected incoming messages. PX_PRODUCTS Example of module parameter based entry of EUT interface information for all products participating in an interoperability event. PX_EUT_A Selects product based on index in PX_PRODCUTS vendor list for EUT_A. PX_EUT_B Selects product based on index in PX_PRODCUTS vendor list for EUT_B. PX_EUT_C Selects product based on index in PX_PRODCUTS vendor list for EUT_C. PX_EUT_B_B2 Selects product based on index in PX_PRODCUTS vendor list for EUT_B_B2. PX_AVAILABLE_INTERFACES Selects if interfaces should be considered in the evaluation interfaceName needs to be consistent to AtsImsIot_TestConfiguration. PX_EUT_TRIGGER_RESPONSE Maximum time limit used by trigger component for waiting for EUT response after command has been sent. PX_IOT_PCAP_SESSIONS_PATH In case of offline mode, it defines the path where all sessions's Pcap files are located. PX_IOT_RECORD_MODE Defines if the record traffic capture mode must be activated or not. PX_IOT_FILE_MERGE_LIST Defines list of the files to merge. ETSI ETSI TS 186 011-3 V4.1.3 (2012-05) 23 PX_IOT_FILE_MERGE_PATH Defines the location of the files to merge. PX_IOT_MERGE_TOOL_PATH Defines the location of the files to merge. PX_IOT_TIMESTAMP_OFFSET Defines the time stamp offset to start playing record traffic capture file. PX_IOT_IFACES List of the network interfaces to monitor. PX_IOT_EUTs_IFACE_INFO_LIST List of EUT network interfaces.
|
320381f60d052d2b1060ecc4577deb9a
|
186 011-3
|
8.4.2 LibIms_UpperTester
|
PX_IMS_USER_DATA Example of module parameter based entry of EUT interface information for all products particpating in an interoperability event. ETSI ETSI TS 186 011-3 V4.1.3 (2012-05) 24 Annex A (normative): Zip file with TTCN-3 code A.1 The ATS in TTCN-3 core (text) format This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ES 201 873-1 [7]. The TTCN-3 core (text) representation corresponding to this ATS is contained in an ASCII file(s) (IMS_TestSystem.ttcn3 contained in archive ts_18601103v040103p0.zip) which accompanies the present document. Where an ETSI Abstract Test Suite (in TTCN-3) is published in both core and tabular format these two forms shall be considered equivalent. In the event that there appears to be syntactical or semantic differences between the two then the problem shall be resolved and the erroneous format (whichever it is) shall be corrected. ETSI ETSI TS 186 011-3 V4.1.3 (2012-05) 25 History Document history V2.2.1 September 2009 Publication V3.1.1 June 2011 Publication V4.1.3 May 2012 Publication
|
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 of this subsystem under a communications application load. The present document is the second part of the multi-part deliverable which consists of four parts. TS 186 025-1 [1] contains the overall benchmark descriptions, architectures, processes, and information models that are common to all specific benchmarking scenarios. The present document contains the specific benchmarking use-cases and scenarios, along with scenario specific metrics and design objectives. It also defines the SUT configuration parameters. This part also contains any required extensions to the overall descriptions present in the present document, if necessary for the specific scenario. TS 186 025-3 [i.1] defines an initial benchmark test through the specification of a traffic set, traffic-time profile and benchmark test procedure. TS 186 025-4 [i.2] defines Reference Load network quality parameters for the use cases defined in the present document.
|
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 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.
|
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 exchange performance design objective". [3] ETSI TS 183 036: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification". [4] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)". [5] ETSI TS 183 043: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification". ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 7
|
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 Part 3 : Traffic Sets and Traffic Profiles". [i.2] ETSI TS 186 025-4: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark; Part 4: Reference Load network quality parameters".
|
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: document generated at the conclusion of a test procedure containing the metrics measured during the execution of the test and/or computed from the data collected in the benchmark log benchmark test: procedure by which a test system interacts with a System Under Test to measure its behaviour and produce a benchmark report configuration: specification of a subset of IMS/PES architectural elements and metrics for which collection of benchmark tests can be defined design objective: probabilistic model of delay and failure requirements for SUT, associated with a use-case, specified by threshold values and probabilities for delay and scenario failure. idle load: load that is not dependent on the traffic or other external activities maximum capacity: maximum processor load that a processor can handle without rejecting new calls metric: performance measurement of SUT reported in a benchmark report parameter: attribute of a SUT, test system, system load, or traffic set whose value is set externally and prior to a benchmark test, and whose value affects the behaviour of the benchmark test processor load: part of time the processor executes work, normally expressed in percent NOTE: The processor load consists of Idle load, Traffic load and Usage load. Reference Call (RC): basic ISUP to ISUP call connected through two MGW in the same MGC domain test parameters: parameters whose values determine the behaviour of a benchmark test test procedure: specification of the steps to be performed by a benchmark test test scenario: specific path through a use-case, whose implementation by a test system creates a system load test system: collection of hardware and software which presents a system load to a system under test and collects data on the system under test's performance, from which metrics can be computed traffic load: load that results from handling traffic events that are directly related to calls; this load varies with the traffic intensity traffic-time profile: evolution of the average scenario over a time interval ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 8 traffic set: mixture of traffic scenarios usage load: load that is reserved for the administrations operation and maintenance activities during busy hour workload: number of reference calls per second (RC/s) NOTE: It is calculated by multiplying calls per second by its corresponding WLF. workload factor: traffic load for different types of calls in relation to the traffic load of the reference call (ISUP call)
|
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 Line Identification Presentation CW Communication Waiting DO Design Objective FM Feature Manager i-BGF Interconnect Border Gateway Function IMS IP Multimedia Subsystem ISDN Integrated Services Digital Network ISUP ISDN User Part MGC Media GateWay Controler MGC Media Gateway Controller MGCP Media Gateway Control Protocol MGF Media Gateway Function MGW Media GateWay MHT Mean Holding Time NGN Next Generation Networks P-CSCF Proxy-Call Session Control Function PES PSTN/ISDN Emulation Sub-system PESQ Perceptual Evaluation of Speech Quality PRI Primary Rate Interface PSTN Public Switched Telecommunications Network RACS Resource Admission Control Subsystem RC Reference Call RG Residential Gateway RTP Real Time Protocol S-CSCF Serving Call Session Control Function SIP Session Initial Protocol SUT System Under Test UA User Equipment UDI Unrestricted Digital Information VGW Voice Gateway WLF WorkLoad Factor ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 9
|
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 the perspective of specifying information flows and ensuring the interoperability of services: • Access Gateway Analogue line function; • Access Gateway BRI function; • Access Gateway PRI function; • Residential Gateway Analogue line function; • Residential Gateway BRI function; • Trunk Gateway function; • Access Call Server function; • Transit Call Server function; • Packet Handler Gateway function; • Media Gateway Controller function; • Media Server Control Function; • Customer Location function; • IN Access Subsystem; • SIP Server Access Function; • Trunk Signalling Gateway. The Functional Architecture is shown in figure 1 in such a way that it can be seen that multiple implementation architectures are possible. There are some fundamental points that should not be missed however. The first of these is that we have gateways that convert legacy interfaces such as national analogue PSTN Z reference points and ISDN S or T reference points into NGN interfaces. These are usually thought of as being H.248 interfaces but that is not the only interface that can be used. Depending on the service set MGCP or interfaces carrying suitable information in SIP can be used. The key point is that the information flow can carry the stimulus information traditionally needed in national PSTNs to carry both line and register signalling from customers as well as specialised service signalling. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 10 Distributor Service A Service B Service C Master Customer Data Customer Location Trunk Routing Service 1 Service 2 Service 3 PSTN/ISDN Services AGCF TGCF SGCF AGF AGF S/T Z AS MGF e A-BGF I-BGF RACS IN PSTN / ISDN RG Gq’ Topology Hiding Gateway Other NGN’s Other NGN’s PSTN/ISDN Emulation Subsystem Transport b a c f g h j i AGCF NOTE: Lines inside the grey area are purely illustrative. Information flows may Be though the Distributor Or direct as an implementation option Local Data Distributor Service A Service B Service C Master Customer Data Customer Location Trunk Routing Service 1 Service 2 Service 3 PSTN/ISDN Services AGCF TGCF SGCF AGF AGF S/T Z AS MGF e A-BGF I-BGF RACS IN PSTN / ISDN RG Gq’ Topology Hiding Function Other NGN’s Other NGN’s PSTN/ISDN Emulation Subsystem Transport b a c f g h j i AGCF NOTE: Lines inside the grey area are purely illustrative. Information flows may Be though the Distributor Or direct as an implementation option Local Data Presence Server k i i Distributor Service A Service B Service C Master Customer Data Customer Location Trunk Routing Service 1 Service 2 Service 3 PSTN/ISDN Services AGCF TGCF SGCF AGF AGF S/T Z AS MGF e A-BGF I-BGF RACS IN PSTN / ISDN RG Gq’ Topology Hiding Function Other NGN’s Other NGN’s PSTN/ISDN Emulation Subsystem Transport b a c f g h j i AGCF NOTE: Lines inside the grey area are purely illustrative. Information flows may Be though the Distributor Or direct as an implementation option Local Data Presence Server k i i f Distributor Service A Service B Service C Master Customer Data Customer Location Trunk Routing Service 1 Service 2 Service 3 PSTN/ISDN Services AGCF TGCF SGCF AGF AGF S/T Z AS MGF e A-BGF I-BGF RACS IN PSTN / ISDN RG Gq’ Topology Hiding Function Other NGN’s Other NGN’s PSTN/ISDN Emulation Subsystem Transport b a c f g h j i AGCF NOTE: Lines inside the grey area are purely illustrative. Information flows may Be though the Distributor Or direct as an implementation option Local Data Presence Server k i i f m d Figure 1: Overview of Functional Entities MGC SIP UA MGF MGF VGW AGCF RTP FM SIP UA FM MGC S-CSCF S-CSCF AS AS P-CSCF Figure 2: AGCF/VGW session processing model ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 11
|
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. Described are user equipment actions.
|
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 performed correctly. The call is released from the called user. 5.1.1.3 ISDN - ISDN Scenario 1.3 Basic call - overlap sending with BC = speech This scenario represents the case when the call establishment using overlap sending is performed correctly. The call is released from the calling user. 5.1.1.4 ISDN - ISDN Scenario 1.4 Basic call with BC = 3,1 KHz audio - Fax with 33,6 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 and the echo cancellers in the GW are not activated. The call is released from the calling user. 5.1.1.5 ISDN - ISDN Scenario 1.5 Basic call with BC = 3,1 KHz audio - 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 and the echo cancellers in the GW are not activated. The call is released from the calling user. 5.1.1.6 ISDN - ISDN Scenario 1.6 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 calling user.
|
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 active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 12 5.1.1.9 ISDN - ISDN Scenario 1.9 Basic call with BC = 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) 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 calling user.
|
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 performed correctly. The call is released from the called user.
|
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 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. The call is released from the called user. 5.1.2.5 ISDN - PSTN Scenario 2.5 Basic call with BC = 3,1 KHz audio - 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 and the echo cancellers in the GW are not activated. The call is released from the called user. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 13 5.1.2.6 ISDN - PSTN Scenario 2.6 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 active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user. 5.1.2.7 ISDN - PSTN Scenario 2.7 Basic call with BC = 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) 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 calling user.
|
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 represents the case when the call establishment is performed correctly. The call is released from the called user. 5.1.3.3 PSTN - ISDN Scenario 3.3 Basic call with BC = 3,1 KHz audio - Fax with 33,6 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 and the echo cancellers in the GW are not activated. 5.1.3.4 PSTN - ISDN Scenario 3.4 Basic call with BC = 3,1 KHz audio - 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 and the echo cancellers in the GW are deactivated.
|
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 represents the case when the call establishment is performed correctly. The call is released from the called user. 5.1.4.3 PSTN - PSTN Scenario 4.3 Basic call with Fax with 33,6 kBit/s (Super G3 Fax) 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 deactivated.
|
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 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 deactivated. 5.1.4.6 PSTN - PSTN Scenario 4.6 Basic call with BC = 3,1 KHz audio - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 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 and the echo cancellers in the GW are activated.
|
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) environment Meaning of timers Parameter Q.543 IMS, PES equivalent Detailed description Local exchange call request delay - originating outgoing and internal traffic connections ANALOGUE SUBSCRIBER LINES local exchange call request delay - originating outgoing and internal traffic connections Clause 2.3.2.1 [2] For ANALOGUE SUBSCRIBER LINES, call request delay is defined as the interval from the instant when the off- hook condition is recognizable at the subscriber line interface of the exchange until the exchange begins to apply dial tone to the line. The call request delay interval is assumed to correspond to the period at the beginning of a call attempt during which the exchange is unable to receive any call address information from the subscriber. PES [5] For ANALOGUE SUBSCRIBER LINES connected to the AGCF or VGW Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the AGCF/VGW until the AGCF/VGW begins to apply dial tone to the line. ISDN SUBSCRIBER LINES local exchange call request delay - Overlap sending Clause 2.3.2.2 [2] Local exchange call request delay - Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system. ISDN [3] Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system. IMS [4] Call request delay is defined as the interval from the instant at which the INVITE message has been received from the SIP subscriber until the 100 Trying from the SBC/P-CSCF is passed back to the subscriber. ISDN SUBSCRIBER LINES local exchange call request delay- Enblock sending Clause 2.3.2.3 [2] For DIGITAL SUBSCRIBER LINES using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the call proceeding message is passed back to the subscriber signalling system. ISDN [3] For ISDN using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the CALL PROCCEDING message is passed back to the subscriber signalling system. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 16 Meaning of timers Parameter Q.543 IMS, PES equivalent Detailed description Alerting sending delay for terminating traffic (the users are in different locations, controlled by different S-CSCF/P-CSCF) ANALOGUE SUBSCRIBER LINES Alerting sending Delay for terminating traffic Clause 2.3.6.1.1 [2] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the exchange until the ringing tone is sent backwards toward the calling user. PES [5] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the AGCF until the ringing tone is sent toward the calling user. ISDN SUBSCRIBER LINES Alerting sending Delay for terminating traffic Clause 2.3.6.1.2 [2] For calls termining on DIGITAL SUBSCRIBER LINES, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling system to the instant at which an ADDRESS COMPLETE message is passed to the interexchange signalling system or ringing tone is sent backward toward the calling user. ISDN [3] For calls termining on ISDN, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling to the instant at which an AGCF/VGW sends the 180 Ringing backward toward the calling user. IMS [5] Call request delay is defined as the interval from the instant at which the 180 Ringing is received from the terminating subscriber until the 180 Ringing is passed back to the originating subscriber. Alerting sending delay for internal traffic (the user are in same locations, controlled by same AGCF/VGW or P-CSCF) ANALOGUE SUBSCRIBER LINES Alerting sending Delay for internal traffic Clause 2.3.6.2.1 [2] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the exchange until ringing tone is applied to an ANALOGUE calling subscriber. PES [5] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the AGCF/ VGW until Ringing tone is sent towards the calling subscriber. ISDN SUBSCRIBER LINES Alerting sending Delay for Internal traffic Clause 2.3.6.2.2 [2] For internal calls terminating on DIGITAL SUBSCRIBER LINES originating from DIGITAL SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the signalling system of the called subscriber's line until the ALERTING message is applied to the calling subscriber line. ISDN [3] For calls terminating on ISDN, alerting sending delay is defined as the interval from the instant that an ALERTING message is received and ALERTING is sent towards the calling subscriber. IMS [4] Call request delay is defined as the interval from the instant at which the 180 Ringing is received from the subscriber at terminating Gm interface until the 180 Ringing is passed back at the originating Gm interface to the calling subscriber. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 17 Meaning of timers Parameter Q.543 IMS, PES equivalent Detailed description Call set up delay ISDN SUBSCRIBER LINES call set up delay using overlap signalling Clause 2.4.3.1 [2] Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system Exchange call setup delay for originating outgoing traffic connections, digital subscriber lines. The time interval starts when the INFORMATION message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the corresponding signalling information is passed to the outgoing signalling system. ISDN [3] Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on the Ic or terminating Gm interface has been sent, or Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the SETUP message has been sent to the called user. IMS [4] the time interval starts when the digit collection function determines that the address information received in the INFO or subsequent INVITE message is sufficient for session initiation, and ends when the INVITE message on the Ic or terminating Gm interface has been sent. ISDN SUBSCRIBER LINES call set up delay using enblock signalling Clause 2.4.3.1 [2] Exchange call setup delay for originating outgoing traffic connections. For call attempts using en-bloc sending. Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system. The time interval starts when the SETUP message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the call setup is sent on the outgoing signalling system. ISDN [3] Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the Ic or terminating Gm interface, or Call set-up delay is defined as the interval from the instant when the SETUP including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding SETUP signalling information is passed to the called line signalling system. (see note 1) IMS [4] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Gm interface to the called user. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 18 Meaning of timers Parameter Q.543 IMS, PES equivalent Detailed description Through-connection delay ISDN SUBSCRIBER LINES Through-connection delay Clause 2.4.4.2 [2] Through-connection delay The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the ANSWER and CONNECT ACKNOWLEDGEMENT messages have been passed to the appropriate signalling systems. ISDN [3] The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the CONNECT message has been sent to the calling user signalling system. (see note 2) IMS [4] The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating Gm interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating Gm interface. Connection release delay ISDN SUBSCRIBER LINES Connection call release delay Clause 2.4.6 [2] Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant when the connection is no longer available for use on the call (and is available for use on another call) and a corresponding RELEASE or DISCONNECT message is passed to the other signalling system involved in the connection. ISDN [3] Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant when RELEASE COMPLETE is sent and a corresponding RELEASE or DISCONNECT message is sent, or vice versa. IMS [4] Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating Gm interface until the instant when 200OK is sent and a corresponding BYE message is sent at the terminating or originating Gm interface respectively. NOTE 1: If SC (#) is not included the setup delay may increase up to the digit collection timer (15 s). NOTE 2: The through connection of RTP is not considered.
|
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 parameters. Table 2: Speech Quality parameters based on PESQ Speech Quality Summary P.862.1 Min Max Mean Std-Dev ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 19 Table 3: Speech level parameters Speech Level Summary (Optional) Active Level Peak Noise Signal to Interval Noise Min Max Mean Std-Dev Table 4: PESQ offset parameters Delay Summary - Delay (PESQ Time Offset) Min Max Mean Std-Dev Range
|
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 reserved for the administration operations and maintenance activities during busy hour. The Traffic load is the load that results from handling traffic events that are directly related to calls; this load varies with the traffic intensity. The maximum capacity is the maximum processor load that a processor can handle without rejecting new calls. It is usually 95 % of the processor capacity. The Dimensioning factor is the ratio between the Maximum capacity and the Dimensioning capacity. The Dimensioning capacity is usually about 85 % of the processor capacity. The processor load is linear versus generated call intensity. 5.4.2 Reference Call and Workload Factors To facilitate the calculation of processing capacity and the appropriate load profile the concept WorkLoad Factor (WLF) has been defined based on the reference call for each combination of traffic case and traffic signalling interface. The Reference Call (RC) is defined as a basic ISUP to ISUP call connected through two MGW in the same MGC domain. Based on the workload factors for all different types of calls, the call intensities and the services used, one can express the total traffic load in an equivalent number of reference calls per second. The dimensioning of any type of network depends on a number of different parameters such as utilization per channel, calls per second, mean holding time, type of accesses being involved, and type of services being requested. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 22 The workload factor is implementation dependent. Following values for MGW are examples: • MGW (ISUP) - AGW (ISDN) = 1 • MGW (ISUP) - SIP-I= 1,6 • SIP - SIP Transit= 2,1 For the calls with special features or services, additional WLF must be considered. Example of such services/features are: • Inter-MGW ISUP calls with a late decision to activate Echo Control Device on the outgoing side. • Calls where a Continuity Check has been requested. • Calls needing announcements. • Calls with IN services using GS devices. • Calls requesting DTMF reception of dialled digits. • Calls requesting supplementary services like CLIP, Call diversion and CW. Depending of the configuration the workload factor for Call Controller, the workload factor for Gateway Controller and the workload factor for Media Gateways must be defined from the manufacturer of the SUT. The call capacity for a signalling terminal is depending on the signalling protocol (i.e. SIP/SIP-I, H.323, SIGTRAN protocols and DNS/ENUM) and call type for control signalling over IP. Table 5: Examples of signalling terminal capacities for different Protocols in % Protocol Call type Capacity at 80 % load SIP-I Basic 26 % call legs/s PRACK 25 % call legs/s PRAC & PREC 13 % call legs/s SIP Basic 35 % call legs/s PRACK 32 % call legs/s PRAC & PREC 16 % call legs/s H.323 Fast connect 43 % call legs/s Tunnelling 22 % call legs/s Separate H.245 17 % call legs/s SIGTRAN M3UA (ISUP) 73 % call legs/s IUA/DUA 100 % call legs/s DNS/ENUM 100 % requests/s ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 23 Annex A (informative): Calls flows This annex defines the calls flows which should be implemented to simulate ISDN - non-ISDN environment. Figure A.1 presents the call flow for the - PTSN environment calling side. Figure A.2 presents the call flow for the - PTSN environment called side. Figure A.3 presents the call flow for the ISDN environment for voice calls calling side - overlap. Figure A.4 presents the call flow for the ISDN environment for voice calls calling side - enblock. Figure A.5 presents the call flow for the ISDN environment for voice calls called side. Figure A.6 presents the call flow for the ISDN environment for data calls calling side. Figure A.7 presents the call flow for the ISDN environment for data calls called side. Figure A.1 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 24 Timer T5 Connection Holding time Alerting Available On Hook Test Pass Test Fail Called party No No Yes Delay time 1000 ms OFF Hook Send Voice Samples Receive Voice Samples Inband Synch Establi shed No Yes Send inband digits Receive inband digits PESQ > limit Yes No Yes 1 DTMF No 1 2 2 Number of Alerting repetions < limit No Yes T5 time out Stop T5 1 Stop T5 Figure A.2 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 25 Figure A.3 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 26 On Hook Timer T1 Test Fail Timer T4 Waiting for answer T4 time out Timer T5 Connection Holding time Send Voice Samples Receive Voice Samples Inband synch Established No T5 time out No Yes Calling party Send digits Enblock SETUP (sending complete) DTMF Send inband digits Receive inband digits PESQ > limit Yes Receiving ALERTING and ringing tone Yes Timer T3 Waiting for ALERTING STOP Timer T3 Waiting for ALERTING Timer T3 Waiting for ALERTING timeout No Yes Yes No No STOP Timer waiting for CONNECT Yes CONNECT Recived Yes No Yes 1 1 1 2 Test Pas 2 CALL PROCEEDING received? Yes 1 No No 1 1 No Stop T5 Stop T5 STOP Timer T1 Figure A.4 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 27 Figure A.5 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 28 Figure A.6 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 29 Figure A.7 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 30 Annex B (informative): Load profiles examples This annex defines the load profiles to simulate ISDN - non-ISDN environments. Figure B.1: the load simulates 2,0 CAPS, call duration 100 s, number of simulated users 200. The number of calls increases each 500 ms. After the call duration of 100 s the calls will be released. The call setup phase is marked orange, the call release phase blue. Figure B.2: the load simulates 2,66 CAPS, call duration 15 s, number of simulated users 30. The number of calls increases each 500 ms. After a call duration of 15 s the calls will be released. In the time interval of 5 s are tested simultaneous ISDN call setups using five channels. In order to simulate a load of 2,0 CAPS, the increase of number of calls is changed to 1,5 per second. Figure B.1 2.6666.. CAPS 0 5 10 15 20 25 30 35 40 45 0 5 10 15 20 25 30 Seconds User Figure B.2 2.0 CAPS 0 50 100 150 200 250 0 20 40 60 80 100 120 140 160 180 200 Seconds User ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 31 Annex C (informative): Load traffic calculation C.1 General The nominal traffic load values specified for the dimensioning of the exchange are average values in the average week day busy hour. That means that the load values may be higher in the busy hour of an individual day. In order to guarantee the grade of service also under these conditions, a high load reserve of normally 20 % is specified. That means that the exchange will work normally without entering overload even if the specified traffic load increases 20 %. C.2 Calculation base on originated/ terminated traffic The required call processing capacity depends on the number of calls offered to the exchange. The basic formula to calculate the required BHCA is: BHCA = A × 3 600 / tm A = traffic tm = mean holding time EXAMPLE 1: - Local exchange with 1 000 analog subscribers - Originating BHCA - A = number of subscribers × originating traffic per subscriber = 1 000 × 0,02 = 20 Erl - tm = mean holding time for originating traffic = 110 s - BHCA = 20 × 3 600 / 110 = 654,5 BHCA - Load A = 654,5 + 20 % = 785,4 BHCA = 0,218 CAPS EXAMPLE 2: - MSAN with 500 ISDN subscribers (2 lines) Originating BHCA - A = number of subscribers × originating traffic per ISDN subscriber (2 lines)= 1 000 × 0,11 = 110 Erl - tm = mean holding time for originating traffic = 110 s - BHCA = 110 × 3 600 / 110 = 3 600 BHCA - Load A = 3 600 + 20 % = 4 320 BHCA = 1,2 CAPS EXAMPLE 3: - MSAN with 34 ISDN PRA=1 020 Users - Originating BHCA - A = number of subscribers × originating traffic per ISDN subscriber = 1 020 × 0,7 = 714 Erl - tm = mean holding time for originating traffic = 440 s - BHCA = 714 × 3 600 / 440 = 5 841,8 BHCA ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 32 - Load A = 5 841,8 + 20 % = 7 010,1 BHCA = 1,9 CAPS C.3 ITU-T load definitions C.3.1 Reference loads Reference load A is intended to represent the normal upper mean level of activity which Administrations would wish to provide for on customer lines and inter-exchange activities. Reference load B is intended to represent an increased level beyond normal planned activity levels. C.3.1.1 Reference load on incoming interexchange circuits a) Reference load A: - 0,7 erlangs average occupancy on all incoming circuits Call attempts/h = 0.7 × number of incoming circuits Average holding time in hours NOTE: Ineffective call attempts should be included in reference call attempts. b) Reference load B: - 0,8 erlangs average occupancy on all incoming circuits with 1,2 times the call attempts/h for reference load A. C.3.1.2 Reference load on subscriber lines (originating traffic) Characteristics of traffic offered to local exchanges vary widely depending upon factors such as the proportions of residence and business lines that are served. Table C.1 provides reference load characteristics for lines typical of four possible local exchange applications. Also provided are representative ISDN cases which are discussed below. Administrations may elect to use other models and/or loads that are more suitable for their intended application. In the following text, ISDN lines will be referred to as digital lines and non-ISDN lines as analogue lines. Reference load A Table C.1: Subscriber line traffic model - Non-ISDN subscriber lines with or without supplementary services Exchange type Average traffic intensity Average BHCA W X Y Z 0,03 E 0,06 E 0,10 E 0,17 E 1,2 2,4 4 6,8 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 33 Table C.2: Subscriber line traffic model - ISDN digital subscriber access 2B + D Line type Average traffic intensity per B channel Average BHCA per B channel Average packets per second per D channel Y′ 0,05 E 2 0,05 (signalling) Data packets (see note) Y′′ 0,10 E 4 0,1 (signalling) Data packets (see note) Y′′′ 0,55 E 2 0,05 (signalling) Data packets (see note) BHCA: Busy Hour Call Attempts. NOTE: Data packet rates are for further study. These include teleaction and packet services data. C.4 High load reserve For a high load reserve of 20 %: load B = 1,20 × load A. The BHCA values (load A) specified for the exchange models consider a high load reserve of 20 %. If a high load reserve of e.g. 30 % is specified by the customer, the corresponding load A values can be calculated as follows: • load A (30 %) = load B / 1,30 = 1,20 × load A (20 %) / 1,30 Load B is in fact the fixed limit (maximum value) of the call processing capacity. Load A values are calculated from the load B values. C.5 Overload If more call attempts are offered to the Coordination Processor than the available call processing capacity under load B conditions (required BHCA > available BHCA-load B), overload control procedures will be activated, i.e. some call attempts will be rejected by the exchange. ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 34 Annex D (informative): Test reports This annex defines a set of reports which enables the quality analysis of the system under test. Following test reports should be possible: • Error detail report; • Error channel report; • Error summary report; • Error summary by channel; • Call detail; • Call detail channel; • Call summary; • Voice Quality Detail; • Voice Quality Channel detail; • Voice Quality Summary. D.1 Example of a Call Detail report CALL DETAIL REPORT Test Name: Basic Call Start Time: Stop Time: Date Time Call ID Server Chan Status Called Number Len Lat ms T1 T2 T3 T4 AVERAGE Date Time Calls Successful Calls Failed : Call Length Latency ms T1 T2 T3 T4 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 35 D.2 Example of a call summary report CALL SUMMARY REPORT Test Name: Basic Call Start Time: Stop Time: Server Channel Attempts Successful Failure Call Length (s) Connect Latency (ms) D.3 Example of a voice summary report Test Name: VQ TEST Start Time: Stop Time: SPEECH LATENCY REPORT Server Channel Number of Tests Average Speech Latency Total Number of Tests: Total Average Speech Latency: DTMF REPORT Server Channel Number of Failures Total Number of Tests: PESQ REPORT Server Channel Number of Tests Average PESQ Score Average Offset Total Averages: ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 36 D.4 Example of a voice quality detail report Test Name: VQ TEST Packetsphere Test: Start Time: Stop Time: SPEECH LATENCY REPORT TimeStamp Call ID Server Channel Speech Lat Number of Speech Latency Tests: Average: (ms) Minimum: (ms) Maximum: (ms) DTMF REPORT TimeStamp Call ID Server Channel Expected Digits Recieved Digits Number of DTMF Test Failures: PESQ REPORT TimeStamp Call ID Server Channel PESQ Value Offset time Prompt Name Value Offset time Total Average: Minimum Maximum Number of PESQ Tests: PESQ Score Above Threshold: ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 37 Annex E (informative): Bibliography ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905 version 7.0.0 Release 7)". ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 6)". ETSI TS 124 247: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.247)". ETSI ES 282 002 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional architecture". ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 38 Annex F (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 16-03- 11 TISPAN06( 11)0007r1 001 1 F CRs for TS 186 025-2: The documents 186 025-2 and 186 025-4 should have the same detailed description. 2.1.1 2.1.3 Publication 2.1.3 2.2.1 ETSI ETSI TS 186 025-2 V2.2.1 (2011-06) 39 History Document history V2.1.1 January 2011 Publication V2.2.1 June 2011 Publication
|
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. The test notation used in the ATS is TTCN-3 (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.
|
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 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.
|
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 016-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Closed User Group (CUG); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [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". ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 7 [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 (V3.4.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [8] Void. [9] ETSI ES 201 873-5: "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: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)". [11] 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". [12] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [13] ETSI TS 186 005-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [14] ETSI TS 186 017-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Anonymous Communication Rejection (ACR) and Communication Barring (CB); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [15] ETSI TS 186 018-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [16] ETSI TS 102 587-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Private Mobile Radio; Part 2: Conformance testing; Test Suite Structure and Test Purposes (TSS&TP) specification". [17] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". [18] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
|
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 Function CUG Closed User Group EDS Encoding/Decoding System ETS Executable Test Suite IBCF Interconnection Border Control Function ICB Incoming Communication Barring I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IP Internet Protocol IUT Implementation Under Test OAE Outgoing Access, Explicit request required OAI Outgoing Access, Implicit outgoing access for all communications OCB Outgoing Communication Barring PA Platform Adapter P-CSCF Proxy CSCF PICS Protocol Implementation Conformance Statement PIXIT Partial Protocol Implementation Extra Information for Testing PTC Parallel Test Component SA SUT Adapter SDP Session Description Protocol SIP Session Initiation Protocol SS Supplementary Services SUT System under Test TC Test Case TCI TTCN-3 Control Interface TCP Transmission Control Protocol TE TTCN-3 Executable TL Test Logging TM Test Management TRI TTCN-3 Runtime Interface TS Test System TSI Test System Information TSS Test Suite Structure TTCN Testing and Test Control Notation TTCN-3 Testing and Test Control Notation version 3 UDP User Datagram Protocol UE User Equipment XML eXtensible Markup Language
|
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 Figure 1: SUT test interface
|
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 SIP protocol ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 10
|
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 test system (TS) simulates the behaviour of the UE or another IMS communicating with the SUT. Figures 3 to 7 provide the different configurations in detail. The test configuration is specified in the context of TTCN-3 functions (e.g. f_cf_1UeUp). The letters "P", "S", "I" and "B" etc. indicate the CSCFs within the SUT or TS. If applicable used identifiers on user profiles (see clause 5.3.2.4) have also been added in the figures (e.g. "PCSCFwithHomeUE" corresponds to TTCN-3 constant c_userProfile_PCSCFwithHomeUE).
|
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 configuration with CF_2Ue
|
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 AS ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome Figure 6: Test configuration with CF_1As2Ue
|
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 configuration with CF_1Scscf1Ibcf
|
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 (SA) Platform Adapter (PA) Figure 8: Abstract Test System Architecture ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 12 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 [11].
|
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 the real IP and port addresses used by the SUT is needed during test execution. The SA retrieves this information via values of TTCN-3 module parameters, i.e. PIXITs and mappings to TSI ports, i.e. triMap operation invocations. TSI port names are the main source for the relating TSI ports with SUT IP addresses and ports. Table 1 provides the relationships for TSI ports and SUT IP addresses and ports. Table 1: TSI port mappings TSI port SUT (IP address, Port Id) Test system (IP address, Port id) UE1 PX_IMS_SUT_PCSCF1_IPADDR, PX_IMS_SUT_PCSCF1_PORT PX_IMS_TS_UE1_IPADDR, PX_IMS_TS_UE1_PORT UE2 PX_IMS_SUT_PCSCF2_IPADDR, PX_IMS_SUT_PCSCF2_PORT PX_IMS_TS_UE2_IPADDR, PX_IMS_TS_UE2_PORT UE3 PX_IMS_SUT_PCSCF3_IPADDR, PX_IMS_SUT_PCSCF3_PORT PX_IMS_TS_UE3_IPADDR, PX_IMS_TS_UE3_PORT PCSCF PX_IMS_SUT_UE_IPADDR, PX_IMS_SUT_UE_PORT PX_IMS_TS_PCSCF_IPADDR, PX_IMS_TS_PCSCF_PORT SCSCF PX_IMS_SUT_AS_IPADDR, PX_IMS_SUT_AS_PORT PX_IMS_TS_SCSCF_IPADDR, PX_IMS_TS_SCSCF_PORT MW_I1 PX_IMS_SUT_ICSCF_IPADDR, PX_IMS_SUT_ICSCF_PORT PX_IMS_TS_SCSCF_IPADDR, PX_IMS_TS_SCSCF_PORT IC1 PX_IMS_SUT_IBCF_IPADDR, PX_IMS_SUT_IBCF_PORT PX_IMS_TS_IBCF1_IPADDR, PX_IMS_TS_IBCF1_PORT AS1 PX_IMS_SUT_SCSCF_IPADDR, PX_IMS_SUT_ SCSCF_PORT PX_IMS_TS_AS1_IPADDR, PX_IMS_TS_AS1_PORT NOTE 1: TSI port names are defined in AtsIms_TestSystem module as part of the ImsComponent type. Module parameters for the address information are defined in LibIms_PIXIT module (see table 3; section LibIms). NOTE 2: For each test configuration listed above a TTCN-3 configuration functions has been implemented with the required mapping and unmapping statements (see table 3; module SS_Ims_TestConfiguration), e.g. f_cf_1Ueup map one UE1 related port of the test system to the SUT. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 13 Figure 9 illustrates the interconnection of TS and SUT in terms of signalling message associations. TS as1 port:sipp port:sipp port:AS1 ue1 port:UE1 port:sipp ic1 port:IC1 port:MW_I1 mwi1 SUT IMS port:UE2 ue2 port:UE3 ue3 SUT AS SUT UE scscf port:SCSCF port:sipp pcscf port:PCSCF port:sipp TS as1 port:sipp port:sipp port:AS1 ue1 port:UE1 ue1 port:UE1 port:sipp ic1 port:IC1 port:IC1 port:MW_I1 port:MW_I1 mwi1 SUT IMS port:UE2 ue2 port:UE2 ue2 port:UE3 ue3 port:UE3 ue3 SUT AS SUT UE scscf port:SCSCF scscf port:SCSCF port:sipp pcscf port:PCSCF pcscf port:PCSCF port:sipp Figure 9: Abstract port association
|
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 EDS is not part of the ATS. Still all encoded messages, i.e. the messages as they are transmitted by the SA to or received by the SA from the SUT, shall be logged. The following terms shall be used for the conventions defined below: Syntactic delimiter syntactic delimiters are characters like "=" or ";" that are used to separate encoded values. LWS linear white spaces as defined in RFC 3261 [4]. Parameter name name of header parameters as defined in RFC 3261 [4]. Parameter value the value of a parameter as defined in RFC 3261 [4]. Undefined method an undefined method is a method other than: "INVITE", "ACK", "OPTIONS", "BYE", "CANCEL" and "REGISTER". ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 14 Undefined header an undefined header is a header other than general-header, entity-header, request-header and response header as defined in RFC 3261 [4]. Unexpected header an unexpected header is a header, which shall not be present in a specific request message. This definition complies to the definition of NOT APPLICABLE in RFC 3261 [4], section 20 for request messages. Decoder requirements TTCN-3 fields should not contain syntactic delimiters like white space, semicolon, equal characters etc. in fully decoded fields. Instead the information provided by a parser shall be used to build the decoded message in TTCN-3. Decoded messages shall use the TTCN-3 enumeration types where ever appropriate, e.g. for the method and the header field name. For charstring fields the following decoding rules shall be applied by the EDS: 1) Subsequent LWS shall compress to a single space character " ". 2) Decoded parameter names shall use only lower case letters. 3) Parameter values containing an integer value shall be decoded to a TTCN-3 integer value where a TTCN-3 integer type is used for a SIP parameter value. The following decoding rules shall be applied by the EDS to each received message in the following order: 1) In case a request message indicating an undefined method is received by the test system, the message shall not be passed in the TE to the ETS. 2) In case an undefined header has been received the header field shall be decoded as UndefinedHeader field. RFC 3261 [4] allows for multiple header field values of the same kind to either arrive in one or multiple occurrences of the corresponding header field. The SIP ATS has been written assuming only the first format. Therefore, should the EDS receive multiple header fields of the same kind in a SIP message, e.g. of a Via header field, it shall convert them into the equivalent single header field with multiple values. This can be achieved by adding the value of, e.g. the second received Via header field as the last value to the value(s) of the first Via header field. Encoder requirements Encoders shall follow all encoding rules that are defined in RFC 3261 [4] when encoding structured values received from templates. This applies in particular to but it is not restricted to section 7.3.1 of RFC 3261 [4]. Values of type Raw shall be send to the SUT without any modification.
|
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(charstring host_name) return charstring; resolves a domain name to its equivalent IPv4 address; 4) calculateDigestResponse(charstring nonce, charstring cnonce, charstring user, charstring realm, charstring passwd, charstring alg, charstring nonceCount, charstring method, charstring qop, charstring URI, charstring HEntity) return charstring; generates a digest response according to RFC 2617 [17] (HTTP Authentication: Basic and Digest Access Authentication) and RFC 1321 [18]. The MD5 Message-Digest Algorithm, (see RFC 2617 [17], chapter 5 Sample implementation, for example usage, as the signature of calculateDigestResponse is according to the example given in the RFC). ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 15
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5 The ATS development process
| |
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 5 of TS 186 016-2 [3]. The requirements applicable to this TP are given by a reference to RFC 3261 [4] (SIP), or ES 183 054 [1]. There are no explicit formulations of requirements.
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.2 ATS structure
| |
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.2.1 Test case grouping
|
The ATS structure defined in table 2 is based on the structuring of Test Purposes in clause 4 of TS 186 016-2 [3]. The group names in column 2 of table 2 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 016-2 [3], but use the naming conventions defined for the ATS (see clause 5.3.2.2). Table 2: ATS structure CUG originating_UE CUG_U01_xxx originating_AS CUG without preference CUG_N01_xxx CUG without preference +OAE CUG_N02_xxx CUG without preference+ OAI CUG_N03_xxx CUG with preference CUG_N04_xxx CUG with preference +OAE CUG_N05_xxx CUG with preference +OAI CUG_N06_xxx No CUG CUG_N07_xxx terminating_AS CUG with OA not allowed CUG_N08_xxx CUG with OA allowed CUG_N09_xxx No CUG CUG_N10_xxx
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: <"TC">"_"<Group index>"_"<TC number> where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in column 4 of table 2 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit decimal number, starting in each subgroup path with "001". EXAMPLE: TC_CUG_N01_001: i) the identifier has Group index " CUG_N01", i.e. it is in the subgroup having complete path: SuplementaryServicee_CUG/SS_CUG_SIPSIP/ originating_UE; 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 016-2 [3] and test case names. The TP identifier of TC_ CUG_N01_001 is TP CUG_N01_001. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 16
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3 ATS specification framework
| |
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.1 ATS Library
|
For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules – project includes test cases from documents TS 186 005-2 [13], TS 186 016-2 [3], TS 186 017-2 [14] and TS 186 018-2 [15]; 2) LibIms modules; 3) LibSip modules (RFC 3261 [4]); 4) LibCommon modules (taken from an improved version of TS 102 351 [12]). NOTE: Due to the common LibSip and LibIms library approach with some other parallel running projects there is necessary to create tag version of all library modules. Table 3 shows the organization of the ATS as library of modules. Table 3: Library of modules Module Class Module Id Description AtsCommon SS_Ims_PICS Module Parameter declarations associated with PICS. SS_Ims_PIXITS SIP common Module Parameter declarations associated with PIXIT. SS_Ims_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations. SS_Ims_TestSystem TSI components, test system internal ports. SS_Ims_TestCases Test case definitions. SS_Ims_TCFunctions Test case functions. LibIms LibIms_PIXITS IMS specific common Module Parameter (e.g. addresses related to SUT components and TS) declarations associated with PIXIT. LibIms_Interface IMS component. LibIms_SIPTypesAndValues IMS specific user and interface specific profile data (see note). LibIms_Templates Modified templates with IMS specific header fields. LibIms_Steps functions using IMS specific types. LibSip LibSip_PIXITS SIP general common Module Parameter (e.g. SDP/SIP procedure options) declarations associated with PIXIT. LibSip_Interface SIP component. LibSip_SIPTypesAndValues SIP message types and constants, simple user profiles (see note). LibSip_SDPTypes SDP types and constants. LibSip_Templates Basic and modified templates with SIP specific header fields. LibSip_Steps SIP specific behaviour function library. LibSip_XMLTypes XML types for SIP tests. XSDAUX Basic types used in XML. 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. NOTE: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 17
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.2 Use of TTCN-3
| |
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.2.1 General
|
TTCN-3 as defined in ES 201 873-1 [7] is used as ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the SIP IMS ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and naming conventions. 4) TTCN-3 is human-readable. 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.
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.2.2 TTCN-3 naming conventions
|
Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. The naming conventions applied to the SIP/IMS ATS are based on the following underlying principles: • when constructing meaningful identifiers, the general guidelines specified for naming in clause 8 [i.1] 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. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 18 Table 4 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. Table 4: 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 SIP message type Use upper-case initial letter none Request, Response Note 2 SIP header type Use upper-case initial letter none MaxForwards Note 2 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 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_IMST2_xxxxx 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 1 Parameterization Use lower-case initial letter p_ p_macId Enumerated Value Use lower-case initial letter e_ e_syncOk NOTE 1: In this case it is acceptable to use underscore as a word delimiter. NOTE 2: This convention has been used in TS 102 027-3 [11] (SIP ATS).
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.2.3 Additional TTCN-3 IMS/SIP naming convention
|
In addition to the general TTCN-3 naming conventions listed in the previous clause the following rules have been applied to templates Table 5: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Message template Use lower-case initial letter, followed by message type in upper-case letters (for requests) or "Response" keyword m_ m_BYE_Request_UE Message template with wildcard or matching expression Use lower-case initial letters mw_ mw_SUBSCRIBE_Request_IMS Templates have been defined in a 3-step approach. First, a dummy template is defined for every message type and direction, e.g. m_ACK_Dummy and mw_ACK_Dummy. Secondly, for each message type and direction a base template has been defined that modifies respective dummy templates and includes all mandatory header fields. Template identifiers of this modifications include the keyword "Base", e.g. m_ACK_Request_Base, mw_ACK_Request_Base. More specific templates are then derived on the basis of these base templates and modify fields that need to be restricted for a very specific purpose, e.g. m_ACK_Request_route, etc. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 19
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.2.4 Additional concepts and conventions
|
IMS procedures and tests requires the inclusion of user identification and network address information in SIP messages. Since this information depends on the specific SUT at hand it is defined using module parameters. Due to the big amount of such parameters a profile concept have been introduced for particular parameter collections (records) that are related to IMS users and interfaces. The so-called user profile information (see table 3; module LibSip_SIPTypesAndValue) contains the following elements: userprofile identifier, current IP port and address to exchange SIP messages, IP port and address for further contact, IP address used by the TS to exchange media streams, public identity (home domain, username), quality-of-protection parameters, authentication parameters (RFC 2617 [17], section 3.2.2). A list of user profile identifiers (module LibIMS_SIPTypesAndValue) introduces available settings for UE with different locations and homes: e.g. c_userProfile_UE1atSUThome should be used in case where UE1 is a registered user of SUT and currently not visiting another IMS. User profiles are constructed from module parameters (see table 3; module LibIMS_Steps). Additionally some interface information is needed to indicate or validate IMS component addresses to be used in SIP header fields like Via, Route, etc. They are defined in a similar way as user profiles (see table 3; LibIms_SIPTypeAndValues) and contain IP address, port and domain information. For example c_interfaceProfile_IMS_SUT_IBCF1 defines an IBCF access point at the SUT. Interface profiles are also constructed based on module parameters (see table 3; module LibIMS_Steps).
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.2.5 PICS information
|
No TTCN-3 control part has been defined for this test suite. If applicable PICS information is evaluated at the beginning of each test case definition using an "if" statement. Log information is provided in case that a test has not been executed due to PICS setting violation.
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.3.2.6 Test Suite documentation
|
In order to allow browsing of the SIP/IMS ATS without the use of a specific TTCN-3 test development environment, the TTCN ATS is made available in HTML format with hyperlinks between entities in the ATS. The documentation in the ATS makes use of special comment tags used by the tool that converts the ATS to the HTML format. These tags are defined in clause 9 of [7] and the tags shown in table 6. Table 6: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of TTCN-3 code. @desc Describes 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 Adds extra information, such as the highlighting of a particular feature or aspect not covered in the description. @img Associates images with a particular piece of TTCN-3 code. @see Refers to other TTCN-3 definitions in the same or another module. @url Associates references to external files or web pages with a particular piece of TTCN-3 code, e.g. a protocol specification or standard. @return Provides additional information on the value returned by a given function. @param Documents the parameters of parameterized TTCN-3 definitions. @version States the version of a particular piece of TTCN-3 code.
|
1c05c7a53a8cd51ab3896ff621be2d4f
|
186 016-3
|
5.4 ATS archive
|
Annex B contains the ATS archive (ts_18601603v020201p0.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 20 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 IMS-related PIXIT. NOTE: The tables in this clause have been generated automatically from the TTCN-3 modules. A.2.1 SIP-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. NOTE: The SIP-related PIXIT definitions are part of a SIP TTCN-3 library that contains additional PIXIT definitions on SIP and TS address information that are not used in this ATS and therefore not present in the following table. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 21 Table A.1: SIP-related PIXIT items No PIXIT Name Description 1 PX_SIP_SDP_dyn charstring for SDP dynamic port 2 PX_SIP_SDP_b_modifier charstring for SDP bandwidth modifier 3 PX_SIP_SDP_b_bandwidth integer for SDP bandwidth value 4 PX_SIP_SDP_encoding charstring for SDP media attribute encoding supported by the IUT 5 PX_SIP_TRANSPORT charstring for Used Transport in upper case "UDP"/"TCP" 6 PX_SIP_SUT_PORT integer for SUT port number to exchange SIP messages 7 PX_SIP_SUT_IPADDR charstring for SUT IP address to exchange SIP messages 8 PX_SIP_TS1_PORT integer for port number used by the TS1 to exchange SIP messages 9 PX_SIP_TS1_IPADDR charstring for IP address used by the TS1 to exchange SIP messages 10 PX_SIP_TS1_LOCAL_DOMAIN charstring for identity of the tester local domain 11 PX_SIP_TS1_LOCAL_USER charstring for identity of the tester local user 12 PX_SIP_TS1_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 13 PX_SIP_TS2_PORT integer for port number used by the TS2 to exchange SIP messages 14 PX_SIP_TS2_IPADDR charstring for IP address used by the TS2 to exchange SIP messages 15 PX_SIP_TS2_LOCAL_DOMAIN charstring for identity of the tester local domain 16 PX_SIP_TS2_LOCAL_USER charstring for identity of the tester local user 17 PX_SIP_TS2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 18 PX_SIP_REGISTRATION boolean for the SIP user if it have to register itself before executing a test case 19 PX_SIP_SUT_REGISTRAR_DOMAIN charstring for REGISTRAR domain 20 PX_SIP_CheckConversation boolean for True, if conversation check is implemented. 21 PX_SIP_REGISTER_AUTHENTICATION_ENABLED boolean for option controlling if authentication is enabled/disabled for REGISTER messages 22 PX_SIP_INVITE_AUTHENTICATION_ENABLED boolean for option controlling if authentication is enabled/disabled for INVITE messages 23 PX_SIP_SUT_UE1_QOP charstring for RFC 2617 [17], clause 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 24 PX_SIP_SUT_UE1_USERNAME charstring for RFC 2617 [17], clause 3.2.2 username: The name of user in the specified realm 25 PX_SIP_SUT_UE1_PASSWD charstring for RFC 2617 [17], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 26 PX_SIP_SUT_UE2_QOP charstring for RFC 2617 [17], clause 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 27 PX_SIP_SUT_UE2_USERNAME charstring for RFC 2617 [17], clause 3.2.2 username: The name of user in the specified realm 28 PX_SIP_SUT_UE2_PASSWD charstring for RFC 2617 [17], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 29 PX_SIP_T1 float for T1 RTT estimate (500 ms) 30 PX_SIP_TF float for TDELAY default value for timeout on outgoing SIP request (ie 64*T1) ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 22 A.2.2 IMS-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. Table A.2: IMS-related PIXIT items (Ports and addresses of IUT) No PIXIT Name Description 1 PX_IMS_SUT_PCSCF1_IPADDR charstring for SUT - PCSCF1 IP address to exchange SIP messages - connection point for UE1 2 PX_IMS_SUT_PCSCF1_PORT integer for SUT - PCSCF1 port number to exchange SIP messages - connection point for UE1 3 PX_IMS_SUT_PCSCF1_HOME_DOMAIN charstring for SUT/PCSCF1 domain - connection point for UE1 4 PX_IMS_SUT_UE1_BEARER_IPADDR charstring for IP address used by the TS to exchangemedia streams for UE1 5 PX_IMS_SUT_UE1_HOME_DOMAIN charstring for identity of the tester UE1 local domain 6 PX_IMS_SUT_UE1_PUBLIC_USER charstring for identity of the tester UE1 local user 7 PX_IMS_SUT_UE1_PRIVAT_USERNAME charstring for RFC 2617 [17], clause 3.2.2 username of UE1: The name of user in the specified realm 8 PX_IMS_SUT_UE1_PRIVAT_PASSWD charstring for RFC 2617 [17], clause 3.2.2.2 passwd of UE1: A known shared secret, the password of user of the specified username 9 PX_IMS_SUT_UE1_QOP charstring for RFC 2617 [17], clause 3.2.1 qop options of UE1: 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 10 PX_IMS_SUT_UE1_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE1 11 PX_IMS_SUT_PCSCF2_IPADDR charstring for SUT - PCSCF2 IP address to exchange SIP messages - connection point for UE2 12 PX_IMS_SUT_PCSCF2_PORT integer for SUT - PCSCF2 port number to exchange SIP messages - connection point for UE2 13 PX_IMS_SUT_PCSCF2_HOME_DOMAIN charstring for SUT/PCSCF2 domain - connection point for UE2 14 PX_IMS_SUT_UE2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE2 15 PX_IMS_SUT_UE2_HOME_DOMAIN charstring for identity of the tester UE2 local domain 16 PX_IMS_SUT_UE2_PUBLIC_USER charstring for identity of the tester UE2 local user 17 PX_IMS_SUT_UE2_PRIVAT_USERNAME charstring for RFC 2617 [17], clause 3.2.2 username of UE2: The name of user in the specified realm 18 PX_IMS_SUT_UE2_PRIVAT_PASSWD charstring for RFC 2617 [17], clause 3.2.2.2 passwd of UE2: A known shared secret, the password of user of the specified username 19 PX_IMS_SUT_UE2_QOP charstring for RFC 2617 [17], clause 3.2.1 qop options of UE2: 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 20 PX_IMS_SUT_UE2_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE2 21 PX_IMS_SUT_UE3_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE3 22 PX_IMS_SUT_UE3_HOME_DOMAIN charstring for identity of the tester UE2 local domain 23 PX_IMS_SUT_UE3_PUBLIC_USER charstring for identity of the tester UE3 local user 24 PX_IMS_SUT_UE3_PRIVAT_USERNAME charstring for RFC 2617 [17], clause 3.2.2 username of UE3: The name of user in the specified realm 25 PX_IMS_SUT_UE3_PRIVAT_PASSWD charstring for RFC 2617 [17], clause 3.2.2.2 passwd of UE3: A known shared secret, the password of user of the specified username ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 23 No PIXIT Name Description 26 PX_IMS_SUT_UE3_QOP charstring for RFC 2617 [17], clause 3.2.1 qop options of UE3: 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 27 PX_IMS_SUT_UE3_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE3 28 PX_IMS_SUT_UE4_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE4 29 PX_IMS_SUT_UE4_HOME_DOMAIN charstring for identity of the tester UE2 local domain 30 PX_IMS_SUT_UE4_PUBLIC_USER charstring for identity of the tester UE4 local user 31 PX_IMS_SUT_UE4_PRIVAT_USERNAME charstring for RFC 2617 [17], clause 3.2.2 username of UE4: The name of user in the specified realm 32 PX_IMS_SUT_UE4_PRIVAT_PASSWD charstring for RFC 2617 [17], clause 3.2.2.2 passwd of UE4: A known shared secret, the password of user of the specified username 33 PX_IMS_SUT_UE4_QOP charstring for RFC 2617 [17], clause 3.2.1 qop options of UE4: 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 34 PX_IMS_SUT_UE4_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE4 35 PX_IMS_SUT_unknownUE_PUBLIC_USER charstring for identity of unknown UE public user 36 PX_IMS_SUT_EMERGENCY_HOME_DOMAIN charstring for identity of emergency service local domain 37 PX_IMS_SUT_EMERGENCY_SERVICE charstring for identity of the emergency service 38 PX_IMS_SUT_EMERGENCY_SERVICE_INVALID charstring for identity of the invalid emergency service 39 PX_IMS_SUT_IBCF1_IPADDR charstring for SUT/IBCF1 IP address to exchange SIP messages 40 PX_IMS_SUT_IBCF1_PORT integer for SUT/IBCF1 port number to exchange SIP messages 41 PX_IMS_SUT_IBCF1_HOME_DOMAIN charstring for SUT/IBCF1 domain 42 PX_IMS_SUT_IBCF2_IPADDR charstring for SUT/IBCF2 IP address to exchange SIP messages 43 PX_IMS_SUT_IBCF2_PORT integer for SUT/IBCF2 port number to exchange SIP messages 44 PX_IMS_SUT_IBCF2_HOME_DOMAIN charstring for SUT/IBCF2 domain 45 PX_IMS_SUT_PCSCF_IPADDR charstring for SUT/P-CSCF IP address to exchange SIP messages 46 PX_IMS_SUT_PCSCF_PORT integer for SUT/P-CSCF port number to exchange SIP messages 47 PX_IMS_SUT_PCSCF_HOME_DOMAIN charstring for SUT/P-CSCFdomain 48 PX_IMS_SUT_SCSCF_IPADDR charstring for SUT/S-CSCF IP address to exchange SIP messages 49 PX_IMS_SUT_SCSCF_PORT integer for SUT/S-CSCF port number to exchange SIP messages 50 PX_IMS_SUT_SCSCF_HOME_DOMAIN charstring for SUT/S-CSCFdomain 51 PX_IMS_SUT_ICSCF_IPADDR charstring for SUT/I-CSCF IP address to exchange SIP messages 52 PX_IMS_SUT_ICSCF_PORT integer for SUT/I-CSCF port number to exchange SIP messages 53 PX_IMS_SUT_ICSCF_HOME_DOMAIN charstring for SUT/I-CSCFdomain 54 PX_IMS_SUT_AS_IPADDR charstring for SUT - AS IP address to exchange SIP messages - connection point for SCSCF 55 PX_IMS_SUT_AS_PORT integer for SUT - AS port number to exchange SIP messages - connection point for SCSCF 56 PX_IMS_SUT_AS_HOME_DOMAIN charstring for SUT/AS domain 57 PX_IMS_SUT_IMGCF_IPADDR charstring for SUT/I-MGCF IP address to exchange SIP messages 58 PX_IMS_SUT_IMGCF_PORT integer for SUT/I-MGCF port number to exchange SIP messages 59 PX_IMS_SUT_IMGCF_HOME_DOMAIN charstring for SUT/I-MGCFdomain ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 24 No PIXIT Name Description 60 PX_IMS_SUT_CONF_PORT integer for SUT/conference port number to exchange SIP messages 61 PX_IMS_SUT_CONF_HOME_DOMAIN charstring for SUT/conference domain 62 PX_IMS_SUT_CONF_FACTORY_NAME charstring for conference factory URI name 63 PX_IMS_TS_UE1_IPADDR charstring for IP address used by the UE1 to exchange SIP messages 64 PX_IMS_TS_UE1_PORT integer for port number used by the UE1 to exchange SIP messages 65 PX_IMS_TS_UE2_IPADDR charstring for IP address used by the UE2 to exchange SIP messages 66 PX_IMS_TS_UE2_PORT integer for port number used by the UE2 to exchange SIP messages 67 PX_IMS_TS_UE3_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 68 PX_IMS_TS_UE3_PORT integer for port number used by the UE3 to exchange SIP messages 69 PX_IMS_TS_UE4_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 70 PX_IMS_TS_UE4_PORT integer for port number used by the UE3 to exchange SIP messages 71 PX_IMS_TS_IBCF_IPADDR charstring for TS/IBCF IP address to exchange SIP messages 72 PX_IMS_TS_IBCF_PORT integer for TS/IBCF port number to exchange SIP messages 73 PX_IMS_TS_ICSCF_IPADDR charstring for TS/I-CSCF IP address to exchange SIP messages 74 PX_IMS_TS_ICSCF_PORT integer for IUT/I-CSCF port number to exchange SIP messages 75 PX_IMS_TS_PCSCF_IPADDR charstring for TS/P-CSCF IP address to exchange SIP messages 76 PX_IMS_TS_PCSCF_PORT integer for IUT/P-CSCF port number to exchange SIP messages 77 PX_IMS_TS_SCSCF_IPADDR charstring for TS/S-CSCF IP address to exchange SIP messages 78 PX_IMS_TS_SCSCF_PORT integer for TS/S-CSCF port number to exchange SIP messages 79 PX_IMS_TS_SCSCF_HOME_DOMAIN charstring for TS/S-CSCFdomain 80 PX_IMS_TS_ECSCF_IPADDR charstring for TS/E-CSCF IP address to exchange SIP messages 81 PX_IMS_TS_ECSCF_PORT integer for TS/E-CSCF port number to exchange SIP messages 82 PX_IMS_TS_IMS1UE_PUBLIC_USER charstring for public userinfo/displayname addressing IMS1UE (simulated by the TS) 83 PX_IMS_TS_IMS1UE_HOME_DOMAIN charstring for TS/domain 84 PX_IMS_TS_ISUP_PUBLIC_USER charstring for public userinfo addressing ISUPUE (simulated by the TS) 85 PX_IMS_TS_ISUP_HOME_DOMAIN charstring for ISUP TS/domain or IPAddres 86 PX_IMS_TS_AS1_IPADDR charstring for TS/AS1 IP address to exchange SIP messages 87 PX_IMS_TS_AS1_PORT integer for TS/AS1 port number to exchange SIP messages 88 PX_IMS_TS_AS1_HOME_DOMAIN charstring for TS/AS1 domain 89 PX_IMS_TS_AS2_IPADDR charstring for TS/AS2 IP address to exchange SIP messages 90 PX_IMS_TS_AS2_PORT integer for TS/AS2 port number to exchange SIP messages 91 PX_IMS_TS_AS2_HOME_DOMAIN charstring for TS/AS2 domain ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 25 Table A.3: CUG-related PIXIT (ATS specific) No PIXIT Name Description 1 PX_CugIndex_Registred_Restrictions_No ne Integer (0 .. 32767) for a registered CugIndex_with Restrictions=None which refers to a value assigned by the network to identify a CUG 2 PX_CugIndex_Registred_Restrictions_O CB Integer (0 .. 32767) for a registered CugIndex_with Restrictions=OCB which refers to a value assigned by the network to identify a CUG 3 PX_CugIndex_Unregistred_Restrictions_ None Integer (0 .. 32767) for an unregistered CugIndex_with Restrictions=None which refers to a value assigned by the network to identify a CUG 4 PX_CugNetworkIndicator hexstring for Cug Network Indicator 5 PX_CugInterlockBinaryCode hexstring for Cug Interlock Binary Code 6 PX_CugInterlockBinaryCode_RelatedToR egistredCUG_Index hexstring for Cug Interlock Binary Code related to registered CUG Index 7 PX_CugInterlockBinaryCode_NotRelated ToRegistredCUG_Index hexstring for Cug Interlock Binary Code not related to registered CUG Index ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 26 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_18601603v020201p0.zip which accompanies the present document. ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 27 Annex C (informative): Bibliography • ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". • ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification". • ETSI TS 186 016-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Closed User Group (CUG); Part 1: Protocol Implementation Conformance Statement (PICS)". • ETSI ES 201 873-2: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)". ETSI ETSI TS 186 016-3 V2.2.1 (2010-10) 28 History Document history V2.1.1 September 2009 Publication V2.2.1 October 2010 Publication
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
1 Scope
|
The present document specifies the test suite structure and test purposes of the Closed User Group (CUG) service, based on stage three of the IMS closed user group (CUG) simulation services. Within the 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).
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is 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.
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 054: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Protocol specification Closed User Group (CUG)". [2] ETSI TS 186 016-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Closed User Group (CUG); Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [4] IETF RFC 3261: "SIP: Session Initiation Protocol". [5] 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".
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 186 016-2 V2.2.1 (2009-07) 6
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
3 Definitions and abbreviations
| |
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 181 002 [3] and the following apply: escaped character: See RFC 3261 [4]. NOTE: This may contain additional information.
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AS Application Server CUG Closed User Group ICB Incoming Communication Barring within a CUG IMS IP Multimedia Subsystem IP Internet Protocol NGN Next Generation Network OAE Outgoing Access, explicit request required OAI Outgoing Access, implicit outgoing access for all communications OCB Outgoing Communication Barring within a CUG PIXIT Protocol Implementation eXtra Information for Testing PSTN Public Switched Telephone Network SDP Session Description Protocol SIP Session Initiation Protocol SS Supplementary Services SUT System Under Test TP Test Purposes TSS Test Suite Structure UA User Agent UE User Equipment XML eXtensible Markup Language
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
4 Test Suite Structure (TSS)
|
CUG originating_UE CUG_U01_xxx originating_AS CUG without preference CUG_N01_xxx CUG without preference + OAE CUG_N02_xxx CUG without preference + OAI CUG_N03_xxx CUG with preference CUG_N04_xxx CUG with preference + OAE CUG_N05_xxx CUG with preference + OAI CUG_N06_xxx No CUG CUG_N07_xxx terminating_AS CUG with OA not allowed CUG_N08_xxx CUG with OA allowed CUG_N09_xxx No CUG CUG_N10_xxx Figure 1: Test suite structure ETSI ETSI TS 186 016-2 V2.2.1 (2009-07) 7
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
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 183 054 [1]. The stage 3 description describes the requirements for several network entities and also the requirements regarding 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:
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
4.1.1 Testing of the AS
|
The AS entity is responsible for performing and managing services. The ISC interface is the appropriate access point for testing. Figure 2: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also possible to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (see 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. 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
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
4.1.2 Testing of the UE
|
There are special clauses in the protocol standard describing the procedures that apply at the originating and terminating user equipment. Therefore the test configuration in figure 4 has been chosen. ETSI ETSI TS 186 016-2 V2.2.1 (2009-07) 8 User Equipment Implementation under Test Test System Gm Figure 4: Applicable configuration to test UE functionalities
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
5 Test Purposes (TP)
| |
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
5.1 Introduction
|
For each test requirement a TP is defined.
|
433ee6bcb33f8457a4d52f8ac89add14
|
186 016-2
|
5.1.1 TP naming convention
|
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "CUG" <iut> = type of IUT: U User equipment N Network entity <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.