hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.58M
|
|---|---|---|---|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
3 Definitions and abbreviations
| |
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 181 002 [2], TS 181 006 [3], TR 180 000 [4] and the following apply: communication information: information collected and registered by the MCID service identity information: includes all the information (RFC 3966 [6] // RFC 3986 [7]) identifying a user, including trusted (network generated) and/or untrusted (user generated) identities trusted identity: network generated user address information untrusted identity: user generated user address information NOTE: This may contain additional information.
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AS Application server HOLD communication HOLD IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Digital Network IUT Implementation Under Test MCID Malicious Call Identification MGCF Media Gateway Control Function NGN Next Generation Network PSTN Public Switched Telephone Network SDP Session Description Protocol SIP Session Initiation Protocol SUT System Under Test UE User Equipment URI Uniform Resource Identifier ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 7 4 Protocol Implementation Conformance Statement proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended purposes and may further publish the completed PICS.
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.1 Instructions for completing the PICS proforma
|
4.1.1 More detailed instructions are given at the beginning of the different clauses of the PICS proforma The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5.
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.1.1.1 Purposes and structure
|
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in reference specifications [1] to [7] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of information: • instructions for completing the PICS proforma; • identification of the implementation; • identification of the reference protocol specification; • PICS proforma tables (containing the global statement of conformance).
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.1.2 Abbreviations and conventions
|
The PICS proforma is composed of an information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [5]. Item column It contains a number that identifies the item in the table. Item description column It describes each respective item (e.g. parameters, timers, etc.). Reference column It gives reference to the MCID specification [1], except where explicitly stated otherwise. Status column The following notations, defined in ISO/IEC 9646-7 [5], are used for the status column: m mandatory - the capability is required to be supported. n/a not applicable - in the given context, it is impossible to use the capability. No answer in the support column is required. o optional - the capability may be supported or not. ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 8 o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression that is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE n/a" shall be implied. NOTE: Support of a capability means that the capability is implemented in conformance to the specification(s) [1] to [7]. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [5], are used for the support column: Y or y supported by the implementation. N or n not supported by the implementation. N/A or n/a - no answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status).
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.2 Identification of the implementation
|
Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.2.1 Date of the statement
|
Date of the statement:
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.2.2 Implementation Under Test (IUT) identification
|
IUT name: IUT version:
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.2.3 System Under Test (SUT) identification
|
SUT name: Hardware configuration: Operating system: ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 9
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.2.4 Product supplier
|
Name: Address: Telephone number: Facsimile number: Additional information:
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.2.5 Client
|
Name: Address: Telephone number: Facsimile number: Additional information:
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.2.6 PICS contact person
|
Name: Telephone number: Facsimile number: Additional information:
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.3 PICS proforma tables
| |
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.3.1 Global statement of conformance
|
(Yes/No) Are all mandatory capabilities implemented? ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 10
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
4.3.2 Roles and network capabilities
|
Table 1: Roles and network capabilities Item Item description Reference Status Support 1 [UE] Is the invocation of the MCID service provided? 4.5.2.12.1 o 2 [UE] Is the invocation of the MCID service using the XML MIME body mcid provided? 4.5.2.12.1 o 3 Is the MCID service in permanent case provided? 4.5.2.5 o1 4 Is the MCID service case by case provided? 4.5.2.5 o1 5 Is the invocation of MCID by sending XML-MIME with XML mcid body MCID XML Request schema containing a McidRequestIndicator set to 1 provided? 4.5.2.12.1 c.1 6 [MGCF] Is the interworking between MCID XML MIME body and ISUP IDR/IRS provided? 4.7.1 o 7 [MGCF] Is the interworking of the "Holding indicator" provided (for national use)? 4.7.1.1 o 8 Is a missing or incomplete originating ID requested? 4.5.2.5.3 c.1 c.1: IF 1/3 THEN o ELSE n/a. o.1: For this service, it is mandatory to support at least one of these items.
|
14acadeac50f478346a0fb8fb6f3e11f
|
186 018-1
|
5 Additional information for PICS
|
ETSI ETSI TS 186 018-1 V1.0.0 (2008-06) 11 History Document history V1.0.0 June 2008 Publication
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
1 Scope
|
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 017-2 [3]. The TSS&TP have been developed to test the Anonymous Communication Rejection (ACR) and Communication Barring (CB) 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.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 183 011: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification". [2] ETSI TS 186 017-1: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Part 1: Protocol Implementation Conformance Statement (PICS)". ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 7 [3] 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)". [4] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [6] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [7] ETSI ES 201 873-1 (V3.4.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [8] 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)". [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 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)". [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] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". [17] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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". [i.2] 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". ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 8
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
3 Definitions and abbreviations
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-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 [i.2] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [5]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [5]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5]. Lower Tester (LT): Refer to ISO/IEC 9646-1 [5]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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 (see annex B). ACR Anonymous Communication Rejection AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CB Communication Barring CDIV Communication DIVersion services CN Core Network CSCF Call Session Control Function DTMF Dual Tone Multi Frequency EDS Encoding/Decoding System ETS Executable Test Suite IBCF Interconnection Border Control Function I-CSCF Interrogating CSCF ID IDentifier IMS IP Multimedia Subsystem IP Internet Protocol IPV IP Version ISC Interface between SUT and AS ISDN Integrated Services Digital Network IUT Implementation Under Test LAN Local Area Network LT Lower Tester LWS Linear White Spaces OIP Originating Identification Presentation PA Platform Adapter PCO Point of Control and Observation P-CSCF Proxy CSCF PICS Protocol Implementation Conformance Statement PIXIT partial Protocol Implementation Extra Information for Testing PSTN Public Switched Telephone Network PTC Parallel Test Component SA SUT Adapter S-CSCF Serving CSCF ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 9 SDP Session Description Protocol SE Session Expires SIP Session Initiation Protocol SS Supplementary Services SUT System under Test T3RTS TTCN 3 Runtime System TC Test Case TCI TTCN-3 Control Interface TCP Transmission Control Protocol TE TTCN 3 Executable TIP Terminating Identification Presentation TIR Terminating Identification Restriction TL Test Logging TM Test Management TP Test Purpose TRI TTCN-3 Runtime Interface TS Test System TSI TS 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
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4 Abstract Test Method (ATM)
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-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 figure the PCOs for the communication between the systems are Gm, Mw, Ic and Isc. Each component can play role of SUT. Figure 1: SUT test interface AS IMSx IMSy UE IMS Mw Ic Isc Gm SIP protocol ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 10
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3 Test architecture
|
The target SUT to be covered by the test purposes of TS 186 017-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 provides the different configuration 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).
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.1 Test configuration
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-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 ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 11 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
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.1.2 Configuration using ISC interface
|
The ISC interface provides an access to the AS. AS SUT IMS S isc AS ue1home SCSCFwithHomeUE AS SUT IMS S isc AS ue1home SCSCFwithHomeUE Figure 5: Test configuration with CF_1Scscf AS IMS SUT S isc P AS ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome AS IMS SUT S isc P AS ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome Figure 6: Test configuration with CF_1As2Ue
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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 ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 12
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.2 Test system architecture
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.2.1 General
|
Test systems that implement this ATS shall conform to the requirements as defined in this clause.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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 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].
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA)
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-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). ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 13 In order to forward messages received in the SA to the test suite and to send them to the SUT a clear and unique association between the TTCN-3 TSI ports and 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 017-3 V2.2.1 (2010-10) 14 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
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.2.3.2 Security & messages compression feature
|
Security transport layer and signalling compression may be used transparently to the ATS.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.2.4 Encoding/Decoding requirements
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers
|
SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use an EDS to parse received encoded messages into TTCN-3 type structures and values and encode structured TTCN-3 type structures and values into encoded messages. This 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]. ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 15 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". 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 with the definition of NOT APPLICABLE in RFC 3261 [4], clause 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. However the message is subject to logging as defined in clause 4.3.3 ("Logging conventions"). 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 clause 7.3.1 of RFC 3261 [4]. Values of type Raw shall be sent to the SUT without any modification.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
4.3.2.5 Platform adaptation requirements
|
For the execution of this test suite implementations of the following external functions have to be provided (see module LibSip_Steps): 1) rndStr() return charstring; returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case; ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 16 3) getIpAddr(charstring host_name) return charstring; resolves a domain name to its equivalent IPv4 address; 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 [16] (HTTP Authentication: Basic and Digest Access Authentication) and RFC 1321 [17] The MD5 Message-Digest Algorithm. (See RFC 2617 [16], clause 5 "Sample implementation", for example usage, as the signature of calculateDigestResponse is according to the example given in the RFC 2617 [16].)
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
5 The ATS development process
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 5 of TS 186 017-2 [3]. The requirements applicable to this TP are given by a reference to RFC 3261 [4] (SIP), or TS 183 011 [1]. There are no explicit formulations of requirements.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
5.2 ATS structure
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-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 017-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 017-2 [3], but use the naming conventions defined for the ATS (see clause 5.3.2.2). Table 2: ATS structure ACR-CB ACR_terminating_AS ACR-CB_N01_xxx OBC_originating_AS ACR-CB_N02_xxx IBC_terminating_AS ACR-CB_N03_xxx interaction_OIP ACR-CB_N04_xxx interaction_CDIV ACR-CB_N05_xxx
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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_ACR_CB_N01_001: i) the identifier has Group index "ACR_CB_N01", i.e. it is in the subgroup having complete path: SupplementaryService_ACR/SS_ACR_CB_SIPSIP/ ACR_terminating_AS; ii) the identifier is the first test case of this group/subgroup. ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 17 NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 017-2 [3] and test case names. The TP identifier of TC_ ACR_CB_N01_001 is TP ACR-CB_N01_001.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
5.3 ATS specification framework
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-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 [14], TS 186 017-2 [3] and TS 186 018-2 [15]. 2) LibIms modules. 3) LibSip modules (see RFC 3261 [4]). 4) LibCommon modules (taken from an improved version of TS 102 351 [12]). NOTE 1: 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 comprehasive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only. ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 18 NOTE 2: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
5.3.2 Use of TTCN-3
| |
ca7429b61f8f4fee76a132269f558127
|
186 017-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, compliable 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.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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 ("_"); ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 19 • only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. Table 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).
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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 nidufues respective dummy templates and includes all mandatory header fields. Template identifiers of these modifications include the keyword "Base", e.g. m_ACK_Request_Base, ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 20 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.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
5.3.2.4 Additional concepts and conventions
|
IMS procedures and tests require the inclusion of user identification and network address information in SIP messages. Since this information depends on the specific SUT at hand it is defined using module parameters. Due to the big amount of such parameters a profile concept have been introduced for particular parameter collections (records) that are related to IMS users and interfaces. The so-called user profile information (see 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 (see RFC 2617 [16], clause 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 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 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 module LibIMS_Steps).
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-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 [8] 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.
|
ca7429b61f8f4fee76a132269f558127
|
186 017-3
|
5.4 ATS archive
|
Annex B contains the ATS archive (ts_18601703v020201p0.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 21 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI 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 017-3 V2.2.1 (2010-10) 22 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 [16], 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 [16], clause 3.2.2 username: The name of user in the specified realm 25 PX_SIP_SUT_UE1_PASSWD charstring for RFC 2617 [16], 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 [16], 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 [16], clause 3.2.2 username: The name of user in the specified realm 28 PX_SIP_SUT_UE2_PASSWD charstring for RFC 2617 [16], 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 017-3 V2.2.1 (2010-10) 23 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 [16], 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 [16], 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 [16], 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 [16], 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 [16], 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 [16], 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 [16], 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 [16], clause 3.2.2.2 passwd of UE3: A known shared secret, the password of user of the specified username ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 24 No PIXIT Name Description 26 PX_IMS_SUT_UE3_QOP charstring for RFC 2617 [16], 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 [16], 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 [16], 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 [16], 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 017-3 V2.2.1 (2010-10) 25 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 017-3 V2.2.1 (2010-10) 26 Table A.3: ACR-CB-related PIXIT (ATS specific) No PIXIT Name Description 1 PX_TC_VA integer for testcase variant according to table entry in table to test purpose description, if present 2 PX_SIP_NameAddr_PAsserted NameAddr default value for PAsserted(with sip scheme) ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 27 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_18601703v020201p0.zip which accompanies the present document. ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 28 Annex C (informative): Bibliography ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification". ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". ETSI ETSI TS 186 017-3 V2.2.1 (2010-10) 29 History Document history V2.1.1 July 2009 Publication V2.2.1 October 2010 Publication
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
1 Scope
|
The present document specifies the test suite structure and test purposes of the Anonymous Communication Rejection (ACR) and Communication Barring (CB) simulation service, based on stage three of the IMS simulation service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing Communication Barring (OCB). 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).
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-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. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-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 011: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification". [2] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [3] IETF RFC 3261: "SIP: Session Initiation Protocol". ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 6
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 186 017-1: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Part 1: Protocol Implementation Conformance Statement (PICS)".
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
3 Definitions and abbreviations
| |
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 181 002 [2] and the following apply: escaped character: See RFC 3261 [3]. NOTE: This may contain additional information.
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement ACR Anonymous Communication Rejection AS Application Server CB Communication Barring CDIV Communication DIVersion services HOLD communication HOLD ICB Incoming Communication Barring IMS IP Multimedia Subsystem IP Internet Protocol ISUP ISDN User Part ISDN Integrated Service Data Network NGN Next Generation Network OCB Outgoing Communication Barring OIP Originating Identification Presentation PSTN Public Switched Telephone Network SDP Session Description Protocol SIP Session Initiation Protocol SUB SUBaddressing TP Test Purposes TSS Test Suite Structure UA User Agent ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 7
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
4 Test Suite Structure (TSS)
|
ACR-CB ACR_terminating_AS ACR-CB_N01_xxx OBC_originating_AS ACR-CB_N02_xxx IBC_terminating_AS ACR-CB_N03_xxx interaction_OIP ACR-CB_N04_xxx interaction_CDIV ACR-CB_N05_xxx ISUP-SIP SS ACR TP612xxx SIP-ISUP SS ACR TP515xxx
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5 Test Purposes (TP)
| |
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.1 Introduction
|
For each test requirement a TP is defined.
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-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. "ACR-CB" <iut> = type of IUT: U User – equipment N Network <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.1.2 Test strategy
|
As the base standard TS 183 011 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 186 017-1 [i.1]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered. ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 8
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.2 TPs for Anonymous Communication Rejection (ACR)
| |
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.2.1 Action for ACR at the terminating AS
|
TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_001 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 Test purpose ACR service rejects an anonymous communication, Privacy value is id. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “id”. Ensure that the ACR is sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 433 Anonymity Disallowed ACK TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_002 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose ACR service rejects an anonymous communication, Privacy value is id. An announcement is provided. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “id”. Ensure that the ACR service provides an announcement to the originating user before sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying Announcement 433 Anonymity Disallowed ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 9 TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_003 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/5 Test purpose ACR service forwards an anonymous communication, Privacy value is id. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “id”. Ensure that the communication is forwarded to voice message service instead of rejecting the communication with a 433 (Anonymity Disallowed) final response. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 200 OK INVITE ACK Voice message BYE 200 OK BYE TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_004 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 Test purpose ACR service rejects an anonymous communication, Privacy value is header. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “header”. Ensure that the ACR is sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 433 Anonymity Disallowed ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 10 TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_005 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose ACR service rejects an anonymous communication, Privacy value is header. An announcement is provided. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “header”. Ensure that the ACR service provides an announcement to the originating user before sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying Announcement 433 Anonymity Disallowed ACK TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_006 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/5 Test purpose ACR service forwards an anonymous communication, Privacy value is header Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “header”. Ensure that the communication is forwarded to voice message service instead of rejecting the communication with a 433 (Anonymity Disallowed) final response. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 200 OK INVITE ACK Voice message BYE 200 OK BYE ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 11 TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_007 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 Test purpose ACR service rejects an anonymous communication, Privacy value is user. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “user”. Ensure that the ACR is sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 433 Anonymity Disallowed ACK TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_008 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose ACR service rejects an anonymous communication, Privacy value is user. An announcement is provided. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “user”. Ensure that the ACR service provides an announcement to the originating user before sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying Announcement 433 Anonymity Disallowed ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 12 TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_009 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/5 Test purpose ACR service forwards an anonymous communication, Privacy value is user. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “user”. Ensure that the communication is forwarded to voice message service instead of rejecting the communication with a 433 (Anonymity Disallowed) final response. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 200 OK INVITE ACK Voice message BYE 200 OK BYE TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_010 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 Test purpose ACR service rejects an anonymous communication, Privacy value is critical. An. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “critical”. Ensure that the ACR is sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 433 Anonymity Disallowed ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 13 TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_011 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose ACR service rejects an anonymous communication, Privacy value is critical. announcement is provided. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “critical”. Ensure that the ACR service provides an announcement to the originating user before sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying Announcement 433 Anonymity Disallowed ACK TSS ACR_CB/ACR_terminating_AS TP ACR-CB_N01_012 CB reference TS 183 011, clause 4.5.2.6.2 [1] Selection expression PICS 1/2 AND PICS 1/5 Test purpose ACR service forwards an anonymous communication, Privacy value is critical. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “icritical”. Ensure that the communication is forwarded to voice message service instead of rejecting the communication with a 433 (Anonymity Disallowed) final response. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 200 OK INVITE ACK Voice message BYE 200 OK BYE ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 14
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.3 TPs for Communication Barring (CB)
| |
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.3.1 Actions for OCB at the originating AS
|
TSS ACR-CB/OBC_originating_AS TP ACR-CB_N02_001 CB reference TS 183 011, clauses 4.5.2.4.1 and 4.9.1.4 [1] Selection expression PICS 1/2 AND NOT PICS 1/4 Test purpose Outgoing communication barring evaluates media. Ensure that a outgoing communication is rejected when the evaluation of the media field condition matches in one of the "m=" lines of the served users outgoing communication barring rules. Ensure that the ACR is sending a 603 (Decline) final response when the communication is rejected. Preconditions: outgoing-communication-barring active=true conditions: sub element media is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 603 Decline ACK TSS ACR-CB/OBC_originating_AS TP ACR-CB_N02_002 CB reference TS 183 011, clauses 4.5.2.4.1 and 4.9.1.4 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose Outgoing communication barring evaluates media. Ensure that a outgoing communication is rejected when the evaluation of the media field condition matches in one of the "m=" lines of the served users outgoing communication barring rules. Ensure that the ACR service provides an announcement to the originating user before sending a 603 (Decline) final response when the communication is rejected. Preconditions: outgoing-communication-barring active=true conditions: sub element media is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying Announcement 603 Decline ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 15
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.3.2 Actions for ICB at the terminating AS
|
TSS ACR-CB/IBC_terminating_AS TP ACR-CB_N03_001 CB reference TS 183 011 clause 4.5.2.6.1 [1] Selection expression PICS 1/2 AND NOT PICS 1/4 Test purpose Outgoing communication barring evaluates media. Ensure that a outgoing communication is rejected when the evaluation of the presence-status field condition matches in one of the "m=" lines of the served users outgoing communication barring rules. Ensure that the ACR is sending a 603 (Decline) final response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element presence-status is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 433 Anonymity Disallowed ACK TSS ACR-CB/IBC_terminating_AS TP ACR-CB_N03_002 CB reference TS 183 011 clause 4.5.2.6.1 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose Outgoing communication barring evaluates media. Ensure that a outgoing communication is rejected when the evaluation of the presence-status field condition matches in one of the "m=" lines of the served users outgoing communication barring rules. Ensure that the ACR service provides an announcement to the originating user before sending a 603 (Decline) final response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element presence-status is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying Announcement 433 Anonymity Disallowed ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 16
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.4 Interaction with other simulation services
| |
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.4.1 Originating Identification Presentation (OIP)
|
TSS ACR-CB/interaction_OIP TP ACR-CB_N04_001 CB reference TS 183 011, clause 4.6.4 [1] Selection expression Test purpose ACR does not apply to due override category according to the OIP service. Ensure that the ACR service shall not apply If the called user has subscribed to the override category according to the OIP service. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK Communication BYE BYE 200 OK BYE 200 OK BYE
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.4.2 Communication Diversion services (CDIV)
|
TSS ACR-CB/interaction_CDIV TP ACR-CB_N05_001 CB reference TS 183 011, clause 4.6.7 [1] Selection expression Test purpose ACR has precedence if the served user has activated the communication diversion service. Ensure that the ACR service shall take precedence over the Communication Diversion service for the served user If the served user has activated the ACR. Ensure that the ACR service rejects the incoming communication where the request includes the P-Asserted-Identity header AND the Privacy header indicating “id”. Ensure that the ACR is sending a 433 (Anonymity Disallowed) response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element anonymous is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 433 Anonymity Disallowed ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 17 TSS ACR-CB/interaction_CDIV TP ACR-CB_N05_002 CB reference TS 183 011, clause 4.6.7 [1] Selection expression Test purpose ICB has precedence if the served user has activated the communication diversion service. Ensure that the ICB service shall take precedence over the Communication Diversion service for the served user If the served user has activated the ICB. Ensure that a outgoing communication is rejected when the evaluation of the presence-status field condition matches in one of the "m=" lines of the served users outgoing communication barring rules. Ensure that the ACR is sending a 603 (Decline) final response when the communication is rejected. Preconditions: incoming-communication-barring active=true conditions: sub element presence-status is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 603 Decline ACK TSS ACR-CB/interaction_CDIV TP ACR-CB_N05_003 CB reference TS 183 011, clause 4.6.7 [1] Selection expression Test purpose OBC has precedence if the served user has activated the communication diversion service. Ensure that the OCB service shall take precedence over the Communication Diversion service for the served user. Ensure that a outgoing communication is rejected when the evaluation of the media field condition matches in one of the "m=" lines of the served users outgoing communication barring rules. Ensure that the ACR is sending a 603 (Decline) final response when the communication is rejected. Preconditions: outgoing-communication-barring active=true conditions: sub element media is evaluate to “true” actions: sub element allow is evaluate to “false” Comments: UA C SUT UA S INVITE 100 Trying 603 Decline ACK ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 18
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.5 Test purposes for the ISUP/SIP Interworking
| |
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.5.1 Interworking from ISUP to SIP (Outgoing Call)
|
TP612001 ACR-CB Reference: TS 183 011 clause 4.7.1.3.1 [1] Selection criteria: TSS reference: ISUP-SIP/SS/ACR Preconditions: Test purpose: Mapping of 433 Anonymity Disallowed to REL cause 24. Ensure that the 433 Anonymity Disallowed final response received to due the ACR service is mapped into a REL cause 24 "call rejected due to ACR supplementary service". SIP Parameter values: 433 Anonymity Disallowed ISUP Parameter values: REL cause value 24 "call rejected due to ACR supplementary service" ISUP MGCF SIP IAM INVITE 100 Trying REL(24) 433 Anonymity Disallowed RLC ACK Comments:
|
3852cdf8f3ce3706df1c4c2e3b23c25f
|
186 017-2
|
5.5.2 Interworking from SIP to ISUP (Incoming Call)
|
TP515001 ACR-CB Reference: TS 183 011 clause 4.7.1.2.1 [1] Selection criteria: TSS reference: SIP-ISUP/SS/ACR/ Preconditions: Test purpose: Mapping of REL cause 24 to 433 Anonymity Disallowed. Ensure that the SUT, if a destination user has subscribed the ACR supplementary service: the call attempt is rejected with a REL cause value 24 "call rejected due to ACR supplementary service". The REL cause 24 is mapped into a 433 Anonymity Disallowed final response. SIP Parameter values: 433 Anonymity Disallowed ISUP Parameter values: REL cause value 24 "call rejected due to ACR supplementary service" SIP MGCF ISUP INVITE IAM 100 Trying 433 Anonymity Disallowed REL(24) ACK RLC Comments: ETSI ETSI TS 186 017-2 V1.0.0 (2008-06) 19 History Document history V1.0.0 June 2008 Publication
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
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 first part of the multi-part deliverable which consists of four parts. The present document contains the overall benchmark descriptions, architectures, processes, and information models that are common to all specific benchmarking scenarios. TS 186 025-2 [1] 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 TS 186 025-2 [1].
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
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.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 186 025-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark Part 2: Subsystem Configurations and Benchmarks". [2] ITU-T Recommendation Q.543: "Digital exchange performance design objective".
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
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". [i.3] ITU-T Recommendation P.862: "Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs". ETSI ETSI TS 186 025-1 V2.1.1 (2011-01) 6 [i.4] ITU-T Recommendation P.862.1: "Mapping function for transforming P.862 raw result scores to MOS-LQO". [i.5] ITU-T Recommendation P.56: "Objective measurement of active speech level".
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
3 Definitions and abbreviations
| |
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
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 NOTE: This load varies with the traffic intensity. traffic-time profile: evolution of the average scenario over a time interval 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. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01) 7 workload factor (WLF): traffic load for different types of calls in relation to the traffic load of the reference call (ISUP call)
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: %IHS Percent Inadequately Handled Scenarios A-BGF Access Border Gateway Function AGCF Access Gateway Control Function APS Attempts per Second BC Bearer Capability CLIP Calling Line Identification Presentation CW Communication Waiting DO Design Objective IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network ISUP ISDN User Part MCID Malicious Communication IDentification MGW Media Gateway MHT Mean Holding Time NGN Next Generation Networks PIXIT Protocol Implementation eXtra Information for Testing PSTN Public Switched Telecommunications Network RC Reference Call SAPS Session Attempts Per Second SUT System Under Test TA Tones and Announcement TSS Telephony Softswitch Solution UDI Unrestricted Digital Information WLF WorkLoad Factor
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4 Benchmark information model
|
In this clause, "benchmark information model" refers to the structure of the information elements that define the benchmark. This information model is depicted in figure 1. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01) 8 Figure 1: IMS/PES benchmark information model ETSI ETSI TS 186 025-1 V2.1.1 (2011-01) 9 The information model consists of three primary elements: use-cases, which describe the behaviour of an individual user, and which in turn define scenarios; benchmark tests, which generate a workload by aggregating the behaviour of individual scenarios in a controlled manner, and collect log files of measurements during the test; and benchmark test reports, which report metrics interpreted from the benchmark test log files.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.1 Use-case
|
The top level of the individual behavioural model is the use-case. A use-case describes the goal that a user has in interacting with a system, the various actors (e.g. other users, network elements) that participate in the use-case, the basic course of events that are carried out by the user and the SUT, the design objective of the use-case, the possible outcomes that apply to the use-case, and the metrics to be collected. The goal and actors of a use-case are documented in narrative text and diagrams; the other elements are complex information elements, which are described in their respective clauses. 4.1.1 Call Flow The calls flows define the characteristic message flows, the tones and announcement for a specific interface. 4.1.2 Load Profile To facilitate the calculation of processing capacity and the appropriate load profile the concept of workload factor 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 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.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.1.3 Metrics
|
The metrics of a use-case describe the measurements collected from the execution of a scenario attempt. Typical metrics include response times and message rates. If a scenario is selected for execution in a benchmark test, its metrics are collected. See clause 7 for more detail.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.1.4 Use-case outcomes
|
A use-case outcome is a set of possible outcomes of the scenarios of a use-case. An outcome may be simply "correct", it may reflect an error or failure condition; or it may reflect a correct behaviour that took an excessive amount of time to occur. An instance of a scenario that experiences an error, failure, or timeout outcome is referred to as an inadequately handled scenario attempt.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.1.5 Scenarios and scenario attempts
|
A scenario is a trace of a path through a use-case. It is analogous to "call attempt", but applies to all interactions within an IMS/PES network, different Bearer, and application interactions. A scenario may succeed, fail, or succeed functionally. The terms "scenario attempt" and "scenario attempts per second" are used in this standard in place of "call attempt" and "call attempts per second" because IMS/PES is a transaction-oriented system with transactions of a variety of types (e.g. speech calls, 3,1 kHz calls, modem calls, Fax calls, etc.). Traffic sets, and indeed the real world, do not operate according to only one transaction type, so the more generalized term is necessary. It would be incorrect and misleading to attempt to report the capacity of a system in "call attempts per second", "registration attempts per second", etc., for system loads that were other than purely call attempts, registration attempts, etc. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01) 10
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.1.6 Design Objective (DO)
|
The Design Objective (DO) describes the maximal acceptable rate handled scenario attempts for a use-case.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.1.7 Scenario
|
A scenario describes a single interaction sequence among the actors of a use-case. It is documented by a set of preconditions on its actors (typically specified by parameter values). In case of IMS/PES the scenario is defined as a set of different Bearer Capabilities (e.g. speech , 3,1 kHz audio, UDI, UDI/TA), services (fax, modem ) or dial mode.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.2 Benchmark test
|
A benchmark by definition measures the behaviour of a population of users. To accomplish this, the behaviours of individual users must be aggregated into input traffic to the SUT. The input traffic must be realistic, in the sense that a population of users would perform such actions in the real world, and in the sense that statistical variation in user behaviour is similar to statistical variation that would occur in the real world.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.2.1 Traffic set
|
The traffic set is a collection of scenarios which are determined to be likely to co-occur in a real-world scenario. The scenarios do not need to come from the same use-case. Within a traffic set, each scenario has an associated relative occurrence frequency, interpreted as the probability with which it would occur in the course of the test procedure.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.2.2 Background load
|
Background load is a workload presented to the SUT in order to consume its resources. It may consist of a stream of traffic presented to the SUT by an external system apart from the test system; or it may be a workload presented to the processing elements, network, or storage subsystem of the SUT. The purpose of background traffic is to make possible the measurement of a design objective capacity in SUT when the capacity of the test system is insufficient to reach the design objective capacity. If a benchmark test is published in which background load is used, then the following requirements apply: • The hardware used to generate the background load must be fully specified. If the background load is generated by software running directly on the SUT, then the components of the SUT on which the background load is executed must be fully specified. • The software used to generate the background load must be provided in source form, including make files and any other configuration files required to compile the software.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.2.3 Traffic-time profile
|
The traffic-time profile is a function describing the average scenario attempt arrival rate as a function of elapsed time during a benchmark test. A traffic-time profile should be chosen in such a manner that, for a given scenario attempt arrival rate, sufficient samples are generated that metrics can be collected with an appropriate confidence bound. Following Call Profiler Traffic Patterns are used today: Saw Tooth Blast Ramp Steady Call Rate Rolling Blast Poisson Distribution. To get a realistic scenario a combination of at least two scenarios is needed.
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.2.4 Test parameters
|
The benchmark test parameters are used to control the behaviour of the test script. The data elements required to configure the test system are listed in table 1. Table 1 is a non-exhaustive list of test parameters defined for the benchmark standard. The list is expected to grow over time, as additional subsystems and system configurations are developed. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01) 11 Table 1: Test parameters Parameter Description Start time Amount of time that a system load is presented to a SUT at the start of a test Stop time Amount of time that a system load is presented to a SUT at the end of a test TotalProvisionedSubscribers The number of simulated subscribers provisioned in the network PercentSimulatedSubscriber The average percentage of simulated subscribers Simulated Maximum simultaneous call legs The number of simulated Maximum simultaneous call legs Traffic per subscriber Traffic per subscriber; default value 0,1 Erlang MHT Mean Holding Time of a call ; default value 120 seconds Ringing time Duration between (180 ringing and 200 OK INVITE ) Default value 1 to 5 s NoS number of subscribers originating traffic per subscriber CAPS/BHCA Call attempts per second / busy hour call attempts WLF for Call Controller The workload factor for Call Controller for specific configuration. Default value 1 to 3 WLF for Gateway Controller The workload factor for Gateway Controller for specific configuration. Default value 1 to 3 WLF for MGW The workload factor for Media Gateways for specific configuration. Default value 1 to 3 TDM Trunks Number of TDM trunks ETH Number of ETH Connections Type of call Calls requesting DTMF receiver POTS calls with CLIP POTS calls with CW POTS calls with Call diversion POTS calls with MCID POTS calls with Fax POTS calls with Modem IN calls using GS devices Calls with tone sending for Continuity Check Calls requesting a loop for Continuity Check ISDN calls with CLIP ISDN calls with CW ISDN calls with Call diversion ISDN Call with MCID ISDN calls with Fax ISDN calls with Modem ISDN with BC=3.1 kHz ISDN with BC= speech ISDN with BC= UDI Protocol call type SIP-I Basic PRACK PRAC & PREC SIP Basic PRACK PRAC & PREC Protocol call type H.323 Fast connect Tunnelling Separate H.245 SIGTRAN M3UA (ISUP) IUA/DUA M2PA DNS/ENUM ISUP routes utilization usually ISUP routes utilization usually, Default value 0,8 ETSI ETSI TS 186 025-1 V2.1.1 (2011-01) 12 Parameter Description Traffic Case MGW (ISUP) - MGW (ISUP) ● inter-MGW MGW (POTS) - MGW (POTS) ● inter-MGW MGW (BA/PRA) - MGW (BA/PRA) ● inter-MGW MGW (PRA - MGW (PRA) ● inter-MGW MGW (POTS) - MGW (BA/PRA) ● inter-MGW MGW (V5.2 POTS) - MGW (V5.2 POTS) ● inter-MGW MGW (ISUP) - MGW (ISUP) ● intra-MGW MGW (POTS) - MGW (POTS) ● intra-MGW MGW (BA/PRA) - MGW (BA/PRA) ● intra-MGW MGW (PRA) - MGW (PRA) ● intra-MGW MGW (V5.2 POTS) - MGW (V5.2 POTS) ● intra-MGW MGW (ISUP) - AGW (POTS) MGW (ISUP) - AGW (ISDN) MGW (ISUP) - SIP-I MGW (POTS) - SIP-I MGW (ISDN) - SIP-I MGW (PRA) - SIP-I MGW (V5.2 POTS) - SIP-I SIP - SIP Transit H.323 - H.323 SIP - H.323
|
d91a3cd4bd32801f28f2fb2b87e27b31
|
186 025-1
|
4.3 Benchmark report
|
A test report is a document, with accompanying data files, that provides a full description of an execution of a benchmark test on a test system. The SUT and test system, as well as their parameters, are described in sufficient detail that an independent test site can replicate the test. The results of the test include data, represented as charts and data sets, depicting the behaviour of the SUT over the elapsed time of the test; reports of the relevant metrics that are conventionally used to compare benchmark results of differing SUTs; and a full description of other observations and exceptions noted during the test.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.