hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.3.8 Timers
|
Table 14: Timers Item Use of ... Reference Status Support Values in seconds allowed supported 1 Toiw1 7.2.3.3 [20] m 4 - 6 2 Toiw2 7.2.3.3 [20] m 4 - 14 3 Toiw3 7.2.3.3 [20] m 4 - 6 4 ISUP T6 Annex A of ITU-T Rec. Q.764 [1] o ITU-T Rec. Q.118 [17] 5 ISUP T7 Annex A of ITU-T Rec. Q.764 [1] o 20 - 30 6 ISUP T9 Annex A of ITU-T Rec. Q.764 [1] o ITU-T Rec. Q.118 [17] 7 TTIR1 7.2.3.3 [20] o 0,1 - 2
|
91ce9dba04094521913bb9faf18082b2
|
186 009-1
|
5.4 Additional information for PICS
|
This clause contains all additional comments provided by the supplier of the implementation (see clause 5.1.1). ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 21 Annex A (informative): Bibliography • ITU-T Recommendation Q.732.3 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding No Reply (CFNR)". • ITU-T Recommendation Q.732.4 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding Unconditional (CFU)". • ITU-T Recommendation Q.732.5 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Deflection (CD)". • ITU-T Recommendation Q.733.1 (1992): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call waiting (CW)". • ITU-T Recommendation Q.733.2 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call hold (HOLD)". • ITU-T Recommendation Q.733.3 (1997): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls to busy subscriber (CCBS)". • ITU-T Recommendation Q.733.4 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Terminal portability (TP)". • ITU-T Recommendation Q.733.5 (1999): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls on no reply". • ITU-T Recommendation Q.734.1 (1993): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Conference calling". • ITU-T Recommendation Q.734.2 (1996): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Three-party service". • ITU-T Recommendation Q.735.1 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Closed user group (CUG)". • ITU-T Recommendation Q.735.3 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Multi-level precedence and pre-emption". • ITU-T Recommendation Q.735.6 (1996): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Global Virtual Network Service (GVNS)". • ITU-T Recommendation Q.736.1 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: International Telecommunication Charge Card (ITCC)". • ITU-T Recommendation Q.736.3 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: Reverse charging (REV)". • ITU-T Recommendation Q.850 (1998): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". • IETF RFC 2046 (1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". • IETF RFC 2327 (1998): "SDP: Session Description Protocol". • IETF RFC 2806 (2000): "URLs for Telephone Calls". • IETF RFC 3204 (2001): "MIME media types for ISUP and QSIG Objects". • IETF RFC 3311 (2002): "The Session Initiation Protocol UPDATE Method". • IETF RFC 3312 (2002): "Integration of Resource Management and Session Initiation Protocol (SIP)". ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 22 • IETF RFC 3323 (2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)". • IETF RFC 3326 (2002): "The Reason Header Field for the Session Initiation Protocol". • ISO/IEC 9646-1 (1994): "Conformance testing methodology and framework - Part 1: General Concepts". • ISO/IEC 9646-2 (1994): "Conformance testing methodology and framework - Part 2: Abstract Test Suite Specification". • ISO/IEC 9646-3 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation". • ISO/IEC 9646-3/DAM 1 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation; Amendment 1: TTCN extensions". • ISO/IEC 9646-5 (1994): "Conformance testing methodology and framework - Part 5: Requirements on test laboratories and clients for the conformance assessment process". ETSI ETSI TS 186 009-1 V2.1.1 (2009-03) 23 History Document history V2.1.1 March 2009 Publication
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
1 Scope
|
The present document contains the performance benchmark requirements applicable to IMS/PES/VoLTE exchange implementations based on Recommendation ITU-T Q.543 [1] and ETSI TS 101 563 [10]. The definitions of IMS/PES/VoLTE design objectives are based on "best practice" performance of legacy PSTN/ISDN signalling. The values contained in the present document are "best practice" performance values measured on IMS and PES implementations. The ISDN VGW values are based on carrier grade implementations.
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
2 References
| |
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
2.1 Normative 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. The following referenced documents are necessary for the application of the present document. [1] Recommendation ITU-T Q.543: "Digital exchange performance design objectives". [2] ETSI TS 183 036: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification". [3] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)". [4] ETSI TS 183 043: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification". [5] Recommendation ITU-T Q.541 (1993): "Digital exchange design objectives - General". [6] Recommendation ITU-T G.812 (2004): "Timing requirements of slave clocks suitable for use as node clocks in synchronization networks". [7] Recommendation ITU-T G.823: "The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy". [8] Recommendation ITU-T G.826 (12/2002): "End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections". [9] ETSI TS 102 928: "Speech and multimedia Transmission Quality (STQ); End-to-End Transmission Planning Requirements for Real Time Services in an NGN context". [10] ETSI TS 101 563: "Speech and multimedia Transmission Quality (STQ); IMS/PES/VoLTE exchange performance requirements". ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 6
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
2.2 Informative 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. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACK Acknowledgment AGCF Access Gateway Control Function CSCF Call Session Control Function ECM EPS Connection Management EPS Evolved Packet System IAD Integrated Access Device IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network ITU-T ITU Telecommunication Standardization Sector MGW Media GateWay MME Mobility Management Entity MSAN Multi Service Access Node NGN New Generation Network P-CSCF Proxy Call Server Control Function PES PSTN/ISDN Emulation Subsystem PSTN Public Switched Telephone Network QCI QoS Class Identifier RTP Real Time Protocol SBC Session Border Control SDP Session Description Protocol S-GW Signalling Gateway SIP Session Initiation Protocol TIE Time Interval Error UE User Equipment VGW Voice Gateway VoLTE Voice over LTE
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4 Metrics and design objectives
| |
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.1 Delay probability
|
This clause defines delay parameters related to ISDN/PSTN, IMS and VoLTE. The values are based on the values in Recommendation ITU-T Q.543 [1] and ETSI TS 101 563 [10].
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.2 Loads definitions
|
The ISDN/PSTN, IMS and VoLTE reference loads definitions and values described in table 1 to table 9 are the reference loads definitions described in Recommendation ITU-T Q.543 [1] and in ETSI TS 101 563 [10]. The derived ISDN procedures are based on the ISDN/SIP interworking [2] procedures, the derived PES procedures are based on the IMS/PES Emulation specification [4] and the derived SIP procedures are based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) [3]. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 7 Figure 1: IMS/LTE Basic Configuration Figure 2: AGCF/VGW session processing models
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.3 Parameter requirements
|
IMS/VoLTE systems shall comply with the requirements given in tables 1 to 9. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 8 Table 1 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Local exchange call request delay - originating outgoing and internal traffic connections ANALOGUE SUBSCRIBER LINES Local exchange call request delay - originating outgoing and internal traffic connections. clause 2.3.2.1 [1] For ANALOGUE SUBSCRIBER LINES, call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the exchange until the exchange begins to apply dial tone to the line. The call request delay interval is assumed to correspond to the period at the beginning of a call attempt during which the exchange is unable to receive any call address information from the subscriber. PES [4] For ANALOGUE SUBSCRIBER LINES connected to the AGCF/MSAN. Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the AGCF/MSAN until the AGCF/MSAN begins to apply dial tone to the line. ≤ 400 ms ≤ 600 ms ≤ 800 ms ≤ 1 000 ms ANALOGUE SUBSCRIBER with IAD (VGW) Local exchange call request delay - originating outgoing and internal traffic connections. PES [4] For ANALOGUE SUBSCRIBER LINES connected to the VGW. Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the VGW until the VGW begins to apply dial tone to the line. ≤ 400 ms ≤ 600 ms ≤ 800 ms ≤ 1 000 ms ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 9 Figure 3: Local exchange analogue subscriber call request delay: overlap sending Table 2 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Local exchange ISDN subscriber call request delay: overlap sending ISDN SUBSCRIBER LINES Local exchange call request delay - Overlap sending. clause 2.3.2.2 [1] Local exchange call request delay. Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system. ISDN [2] Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system. ≤ 200 ms ≤ 250 ms ≤ 300 ms ≤ 400 ms IMS SUBSCRIBER Local exchange call request delay. IMS [3] Call request delay is defined as the interval from the instant at which the INVITE message has been received from the SIP subscriber until the 100 Trying from the SBC/P-CSCF is passed back to the subscriber. ≤ 15 ms ≤ 20 ms ≤ 30 ms ≤ 40 ms ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 10 Figure 4: Local exchange ISDN subscriber call request delay: overlap sending ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 11 Table 3 Meaning of timers Parameter Q.543 IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Local exchange ISDN subscriber call request delay: en Block sending ISDN SUBSCRIBER LINES Local exchange call request delay en-block sending. clause 2.3.2.3 [1] For DIGITAL SUBSCRIBER LINES using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the call proceeding message is passed back to the subscriber signalling system. ISDN [2] For ISDN using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the CALL PROCCEDING message is passed back to the subscriber signalling system. ≤ 300 ms ≤ 400 ms ≤ 500 ms ≤ 600 ms Figure 5: Local exchange ISDN subscriber call request delay: en Block sending ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 12 Table 4 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Alerting sending delay for terminating traffic (the users are in different locations, controlled by different S-CSCF/P-CSCF) ANALOGUE SUBSCRIBER LINES Alerting sending Delay for terminating traffic. clause 2.3.6.1.1 [1] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the exchange until the ringing tone is sent backwards toward the calling user. PES [4] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the AGCF/MSAN until the ringing tone is sent toward the calling user. ≤ 300 ms ≤ 450 ms ≤ 600 ms ≤ 750 ms ISDN SUBSCRIBER LINES Alerting sending Delay for terminating traffic. clause 2.3.6.1.2 [1] For calls terminating on DIGITAL SUBSCRIBER LINES, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling system to the instant at which an ADDRESS COMPLETE message is passed to the interexchange signalling system or ringing tone is sent backward toward the calling user. ISDN [2] For calls terminating on ISDN, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling to the instant at which an AGCF/MSAN sends the 180 Ringing backward toward the calling user. ≤ 250 ms ≤ 300 ms ≤ 350 ms ≤ 400 ms ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 13 Figure 6: Local exchange Alerting sending delay for terminating traffic (in different locations) ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 14 Table 5 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Alerting sending delay for internal traffic (the user are in same locations, controlled by same AGCF/VGW or P-CSCF) ANALOGUE SUBSCRIBER LINES Alerting sending Delay for internal traffic. clause 2.3.6.2.1 [1] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the exchange until ringing tone is applied to an ANALOGUE calling subscriber. PES [4] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the AGCF/MSAN until Ringing tone is sent towards the calling subscriber. ≤ 300 ms ≤ 450 ms ≤ 600 ms ≤ 750 ms ANALOGUE SUBSCRIBER LINES Alerting sending Delay for internal traffic. PES [4] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the MGW/VGW until Ringing tone is sent towards the calling subscriber. ≤ 550 ms ≤ 800 ms ≤ 1 000 ms ≤ 1 100 ms ISDN SUBSCRIBER LINES Alerting sending Delay for Internal traffic. clause 2.3.6.2.2 [1] For internal calls terminating on DIGITAL SUBSCRIBER LINES originating from DIGITAL SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the signalling system of the called subscriber's line until the ALERTING message is applied to the calling subscriber line. ISDN [2] For calls terminating on ISDN, alerting sending delay is defined as the interval from the instant that an ALERTING message is received and ALERTING is sent towards the calling subscriber. ≤ 300 ms ≤ 350 ms ≤ 400 ms ≤ 450 ms IMS SUBSCRIBER LINES 180 sending Delay for Internal traffic. IMS For calls terminating sending delay is defined as the interval from the instant that a 180 message at the Gm interface has received and 180 is sent on the Gm towards the calling subscriber. ≤ 100 ms ≤ 150 ms ≤ 200 ms ≤ 250 ms VoLTE SUBSCRIBER LINES 180 sending Delay for Internal traffic. VoLTE For calls terminating sending delay is defined as the interval from the instant that a 180 message at the VoLTE - UE interface has received and 180 is sent on the VoLTE - UE towards the calling subscriber. ≤ 150 ms ≤ 200 ms ≤ 250 ms ≤ 300 ms ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 15 Figure 7: Alerting sending delay for internal traffic (the user are in same locations, controlled by same AGCF/VGW or P-CSCF) ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 16 Table 6 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Call set up delay ISDN SUBSCRIBER LINES Call set up delay using overlap signalling. clause 2.4.3.1 of [1] Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system. Exchange call setup delay for originating outgoing traffic connections, digital subscriber lines. The time interval starts when the INFORMATION message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the corresponding signalling information is passed to the outgoing signalling system. ISDN [2] Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on the Ic interface has been sent. ≤ 400 ms ≤ 500 ms ≤ 550 ms ≤ 650 ms ISDN [2] Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on terminating Gm interface has been sent. ≤ 450 ms ≤ 450 ms ≤ 550 ms ≤ 650 ms IMS [3] Session initiation call set-up delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user ≤ 250 ms ≤ 350 ms ≤ 450 ms ≤ 550 ms ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 17 Figure 8: Call set up delay: Overlap sending is used ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 18 Table 7 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Call set up delay: en Block sending is used ISDN SUBSCRIBER LINES Call set up delay using en-block signalling. clause 2.4.3.1 of [1] Exchange call setup delay for originating outgoing traffic connections. For call attempts using en-bloc sending Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system. The time interval starts when the SETUP message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the call setup is sent on the outgoing signalling system. ISDN [2] Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the Ic interface. ≤ 350 ms ≤ 450 ms ≤ 550 ms ≤ 650 ms ISDN [2] Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the terminating Gm interface. ≤ 350 ms ≤ 450 ms ≤ 550 ms ≤ 650 ms ISDN [2] Call set-up delay for Internal traffic is defined as the interval from the instant when the SETUP including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding SETUP signalling information is passed to the called line signalling system (see note 1). ≤ 450 ms ≤ 550 ms ≤ 650 ms ≤ 750 ms IMS SUBSCRIBER Call set up delay using for Internal traffic. IMS [3] Session initiation call set-up delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Gm interface to the called user. ≤ 250 ms ≤ 350 ms ≤ 450 ms ≤ 550 ms ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 19 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Call set up delay: en Block sending is used VoLTE VoLTE Session initiation call set-up delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating VoLTE - UE (ECM idle) interface until the instant when the corresponding INVITE signalling information is passed on the terminating VoLTE - UE (ECM Idle) interface to the called user with QCI 1 (see note 2). ≤ 1 800 ms (see note 4) ≤ 1 900 ms (see note 4) ≤ 2 000 ms (see note 4) ≤ 2 100 ms (see note 4) VoLTE Session initiation call set-up delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating VoLTE - UE (ECM Connected) interface until the instant when the corresponding INVITE signalling information is passed on the terminating VoLTE - UE (ECM Connected) interface to the called user (see note 3). ≤ 280 ms ≤ 380 ms ≤ 500 ms ≤ 600 ms NOTE 1: If SC (#) is not included, the setup delay may increase up to the digit collection timer (15 s). NOTE 2: Paging Cycle 1,28 s. NOTE 3: S1-Control plane delay: 2 ms - 15 ms (S1 is the interface between eNode Bs and MME and S-GW). NOTE 4: In the ETSI TS 101 563 [10] was erroneously specified the value for Call set up time ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 20 Figure 9: Call set up delay: en-block sending is used ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 21 Table 8 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Through-connection delay ISDN SUBSCRIBER LINES Through-connection delay. clause 2.4.4.2 [1] Through-connection delay. The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the ANSWER and CONNECT ACKNOWLEDGEMENT messages have been passed to the appropriate signalling systems. ISDN [2] The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the CONNECT message has been sent to the calling user signalling system (see note). ≤ 300 ms ≤ 350 ms ≤ 400 ms ≤ 450 ms IMS Through-connection delay Delay for Internal traffic. IMS [3] The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating Gm interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating Gm interface. ≤ 100 ms ≤ 150 ms ≤ 200 ms ≤ 250 ms VoLTE VoLTE The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating VoLTE - UE interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating VoLTE - UE interface. ≤ 150 ms ≤ 200 ms ≤ 250 ms ≤ 300 ms NOTE: The through connection of RTP is not considered. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 22 Figure 10: Through-connection delay ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 23 Table 9 Meaning of timers Parameter Q.543 [1] IMS, PES equivalent Reference Load A Reference Load B Detailed description Mean Value 95 % probability of not exceeding Mean Value 95 % probability of not exceeding Connection release delay: ISDN SUBSCRIBER LINES Connection call release delay. clause 2.4.6 [1] Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant when the connection is no longer available for use on the call (and is available for use on another call) and a corresponding RELEASE or DISCONNECT message is passed to the other signalling system involved in the connection. ISDN [2] Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant when RELEASE COMPLETE is sent and a corresponding RELEASE or DISCONNECT message is sent, or vice versa. ≤ 300 ms ≤ 350 ms ≤ 400 ms ≤ 450 ms IMS SUBSCRIBER Connection call release delay Delay for Internal traffic. IMS [3] Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating Gm interface until the instant when 200OK is sent and a corresponding BYE message is sent at the terminating or originating Gm interface respectively. ≤ 100 ms ≤ 150 ms ≤ 200 ms ≤ 250 ms VoLTE - IMS SUBSCRIBER Connection call release delay Delay for Internal traffic. VoLTE Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating VoLTE - UE interface until the instant when 200OK is sent and a corresponding BYE message is sent at the terminating or originating VoLTE - UE interface respectively. ≤ 150 ms ≤ 200 ms ≤ 250 ms ≤ 300 ms ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 24 Figure 11: Connection call release delay ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 25
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.4 Call processing performance objectives
| |
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.4.1 Premature release
|
The probability that an exchange malfunction will result in the premature release of an established connection in any one minute interval shall be: P ≤ 2 × 10-5
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.4.2 Release failure
|
The probability that an exchange malfunction will prevent the required release of a connection shall be: P ≤ 2 × 10-5
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.4.3 Incorrect charging or accounting
|
The probability of a call attempt receiving incorrect charging or accounting treatment due to an exchange malfunction shall be: P ≤ 10-4
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.4.4 Misrouting
|
The probability of a call attempt misrouted following receipt by the exchange of a valid address shall be: P ≤ 10-4
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.4.5 No tone
|
The probability of a call attempt encountering no tone following receipt of a valid address by the exchange shall be: P ≤ 10-4
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.4.6 Other failures
|
The probability of the exchange causing a call failure for any other reason not identified specifically above shall be: P ≤ 10-4
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.5 Transmission performance
| |
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.5.1 64 kbit/s switched connections
|
The probability of a connection being established with an unacceptable transmission quality across the exchange shall be: P ≤ 10-5 The transmission quality across the exchange is said to be unacceptable when the bit error ratio is above the alarm condition. NOTE: In Recommendation ITU-T G.826 [8], budgets of 18,5 % of 1,5 × 10-6 were allocated to each national network, so the packet loss for a national connection should be no more than 2,75 × 10-7 [9].
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.6 Slip rate
| |
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.6.1 Normal conditions
|
The slip rate under normal conditions is covered in Recommendation ITU-T Q.541 [5]. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 26
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.6.2 Temporary loss of timing control
|
The case of temporary loss of timing control corresponds to the "holdover operation" defined and recommended in Recommendation ITU-T G.812 [6]. The allowable slip rate will correspond to the maximum relative TIE also recommended therein.
|
78957ee0f55c0b3981b5ea170807e2f5
|
186 008-4
|
4.6.3 Abnormal conditions at the exchange input
|
The slip rate in case of abnormal conditions (wide phase deviations, etc.) at the exchange input is the subject of further study taking into account the requirements of Recommendation ITU-T G.823 [7]. ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 27 Annex A (informative): Bibliography ETSI TS 186 008-1 (V1.2.2): "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 1: Core Concepts". ETSI TS 186 008-2 (V2.1.1): "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 2: Subsystem Configurations and Benchmarks". ETSI TS 186 008-3: "Core Network and Interoperability Testing (INT); IMS/NGN Performance and Robustness Benchmarking; Part 3: Traffic Sets and Traffic Profiles". ETSI ETSI TS 186 008-4 V2.1.1 (2015-05) 28 History Document history V2.1.1 May 2015 Publication
|
047bc52479713610812aa1b711044d22
|
186 005-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 005-2 [2]. The TSS&TP have been developed to test the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) PSTN/ISDN simulation services. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [6]). 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.
|
047bc52479713610812aa1b711044d22
|
186 005-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.
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 183 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification". [2] 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)". [3] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [4] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 6 [5] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [6] 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". [7] 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)". [8] 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)". [9] 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)". [10] 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". [11] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [12] 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)". [13] 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)". [14] 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)". [15] 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". [16] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". [17] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 7
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
3 Definitions and abbreviations
| |
047bc52479713610812aa1b711044d22
|
186 005-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [5], TS 102 587-2 [15] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [4]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [4]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [4]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [4]. Lower Tester (LT): Refer to ISO/IEC 9646-1 [4]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [4].
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [4], ISO/IEC 9646-7 [5] and the following apply: NOTE: Abbreviations have been used both in the present document and in the TTCN-3 library modules (see annex B). AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CDIV Communication DIVersion services CSCF Call Session Control Function E-CSCF Emergency CSCF EDS Encoding/Decoding System ETS Executable Test Suite IBCF Interconnection Border Control Function I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IP Internet Protocol ISC International Switching Centre ISDN Integrated Services Digital Network IUT Implementation Under Test LAN Local Area Network LT Lower Tester 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 Switch Telephony Network SA SUT Adapter S-CSCF Serving CSCF SDP Session Description Protocol 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 ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 8 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 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
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4 Abstract Test Method (ATM)
| |
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.1 Network architecture
|
The SUT is assumed as a complete IMS core network and contains the following components: P-CSCF, I/S-CSCF, E-CSCF, and IBCF. As illustrated in the following figure the PCOs for the communication between the systems are Gm, Mw, Ic, and Isc. Each component can play role of SUT. Figure 1: SUT test interface
|
047bc52479713610812aa1b711044d22
|
186 005-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). AS IMSx IMSy UE IMS Mw Ic Isc Gm SIP protocol ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 9 SUT IMS CN SIP/IMS Extension SIP RFC 3261 [3] Compression algorithms (2) UDP TCP Security Algorithms (2) IPV4/IPV6 (1) (LAN) Figure 2: SIP protocol architecture
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3 Test architecture
|
The target SUT to be covered by the test purposes of TS 186 005-2 [2] 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).
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.1 Test configuration
| |
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.1.1 Configuration using Gm interface
|
The Gm interface is located between UE and IMS. UE1 SUT IMS P gm ue1home PCSCFwithHomeUE UE1 SUT IMS P gm ue1home PCSCFwithHomeUE Figure 3: Test configuration with CF_1Ue IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome IMS SUT UE1 P UE3 gm ue1home ue3home gm UE1atSUThome UE3atSUThome Figure 4: Test configuration with CF_2Ue ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 10
|
047bc52479713610812aa1b711044d22
|
186 005-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
|
047bc52479713610812aa1b711044d22
|
186 005-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
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.2 Test system architecture
| |
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.2.1 General
|
Test systems that implement this ATS shall conform to the requirements as defined in this clause.
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.2.2 Structure
|
An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 4 and also stated in ES 201 873-5 [8]. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 11 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 [8], whereas the specification and implementation of the TCI is in ES 201 873-6 [9]. 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 [10].
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA)
| |
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.2.3.1 Sending and receiving SIP/IMS messages
|
Before starting a test case, the SA shall provide the transport of SIP messages by establishing appropriate connections on the lower layers (shown in figure 2). In order to forward messages received 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. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 12 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 function 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. 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
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.2.3.2 Security and messages compression feature
|
Security transport layer, and signalling compression may be used transparently to the ATS. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 13
|
047bc52479713610812aa1b711044d22
|
186 005-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.
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
4.3.2.4 Encoding/Decoding requirements
| |
047bc52479713610812aa1b711044d22
|
186 005-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 [3]. Parameter name name of header parameters as defined in RFC 3261 [3]. Parameter value the value of a parameter as defined in RFC 3261 [3]. 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 [3]. 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 [3], 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. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 14 RFC 3261 [3] 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 [3] 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 [3]. Values of type Raw shall be sent to the SUT without any modification.
|
047bc52479713610812aa1b711044d22
|
186 005-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; 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.)
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
5 The ATS development process
| |
047bc52479713610812aa1b711044d22
|
186 005-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 5 of TS 186 005-2 [2]. The requirements applicable to this TP are given by a reference to RFC 3261 [3] (SIP), or TS 183 008 [1]. There are no explicit formulations of requirements.
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
5.2 ATS structure
| |
047bc52479713610812aa1b711044d22
|
186 005-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 005-2 [2]. 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 005-2 [2], but use the naming conventions defined for the ATS (see clause 5.3.2.2). ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 15 Table 2: ATS structure TIP/TIR TermUserE TIP_U01_XXX OrigUserE TIP_U02_XXX DestAS TIP_N01_XXX OrigAS TIP_N02_XXX CDIV TIP_N03_XXX OtherNetw TIP_N04_XXX
|
047bc52479713610812aa1b711044d22
|
186 005-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_TIP_N01_001: i) the identifier has Group index "TIP_N01", i.e. it is in the subgroup having complete path: SupplementaryServices_TIP_TIR/SS_TIPTIR_SIPSIP/ TermUserE; ii) the identifier is the first test case of this group/subgroup. NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 005-2 [2] and test case names. The TP identifier of TC_ TIP_N01_001 is TP TIP_N01_001.
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
5.3 ATS specification framework
| |
047bc52479713610812aa1b711044d22
|
186 005-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 [2], TS 186 016-2 [13], TS 186 017-2 [12] and TS 186 018-2 [14]. 2) LibIms modules. 3) LibSip modules (RFC 3261 [3]). 4) LibCommon modules (taken from an improved version of TS 102 351 [11]). NOTE: Due to the common LibSip and LibIms library approach with some other parallel running projects there is necessary to create tag version of all library modules. Table 3 shows the organization of the ATS as library of modules. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 16 Table 3: Library of modules Module Class Module Id Description AtsCommon SS_Ims_PICS Module Parameter declarations associated with PICS SS_Ims_PIXITS SIP common Module Parameter declarations associated with PIXIT SS_Ims_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations SS_Ims_TestSystem TSI components, test system internal ports SS_Ims_TestCases Test case definitions SS_Ims_TCFunctions Test case functions LibIms LibIms_PIXITS IMS specific common Module Parameter (e.g. addresses related to SUT components and TS) declarations associated with PIXIT LibIms_Interface IMS component LibIms_SIPTypesAndValues IMS specific user and interface specific profile data (see note) LibIms_Templates Modified templates with IMS specific header fields LibIms_Steps functions using IMS specific types LibSip LibSip_PIXITS SIP general common Module Parameter (e.g. SDP/SIP procedure options) declarations associated with PIXIT LibSip_Interface SIP component LibSip_SIPTypesAndValues SIP message types and constants, simple user profiles (see note) LibSip_SDPTypes SDP types and constants LibSip_Templates Basic and modified templates with SIP specific header fields LibSip_Steps SIP specific behaviour function library LibSip_XMLTypes XML types for SIP tests XSDAUX Basic types used in XML LibCommon LibCommon_AbstractData Generic data types for a stack and its operations LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean) LibCommon_DataStrings Bit and Octet string types LibCommon_Sync Co-ordination/synchronization of test components LibCommon_TextStrings Basic character and string types with fixed length LibCommon_Time Time handling functions and module parameter LibCommon_VerdictControl Basic functions for setting of test component verdicts NOTE: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only.
|
047bc52479713610812aa1b711044d22
|
186 005-3
|
5.3.2 Use of TTCN-3
| |
047bc52479713610812aa1b711044d22
|
186 005-3
|
5.3.2.1 General
|
TTCN-3 as defined in ES 201 873-1 [6] is used as ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the SIP IMS ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and naming conventions. 4) TTCN-3 is human-readable. 5) TTCN-3 specification is feasible, implementable, compilable and maintainable. 6) Test cases shall be designed in a way to be easily adaptable, upwards compatible with the evolution of the base protocol and protocol interworking of future releases. 7) The test declarations, data structures and data values shall be largely reusable. 8) Modularity and modular working method. 9) Minimizing the requirements of intelligence on the emulators of the lower testers. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 17 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.
|
047bc52479713610812aa1b711044d22
|
186 005-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 [13] should be followed; • the names of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) should reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or other conventions being explicitly stated); • the subfield names of TTCN-3 objects being associated with standardized data type should also be similar to corresponding element names in the base standards (be recognizable in the local context); • in most other cases, identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents; • prefixes should be separated from the body of the identifier with an underscore ("_"); • only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. Table 4 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 18 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 TS 102 351 [11], 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 [10] (SIP ATS).
|
047bc52479713610812aa1b711044d22
|
186 005-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 this modification include the keyword "Base", e.g. m_ACK_Request_Base, mw_ACK_Request_Base. More specific templates are then derived on the basis of these base templates and modify fields that need to be restricted for a very specific purpose, e.g. m_ACK_Request_route etc. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 19
|
047bc52479713610812aa1b711044d22
|
186 005-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 (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).
|
047bc52479713610812aa1b711044d22
|
186 005-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.
|
047bc52479713610812aa1b711044d22
|
186 005-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 ES 201 873-2 [7] and the tags shown in table 6. Table 6: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of TTCN-3 code. @desc Describes the purpose of a particular piece of TTCN-3 code. The description should be concise yet informative and describe the function and use of the construct. @remark Adds extra information, such as the highlighting of a particular feature or aspect not covered in the description. @img Associates images with a particular piece of TTCN-3 code. @see Refers to other TTCN-3 definitions in the same or another module. @url Associates references to external files or web pages with a particular piece of TTCN-3 code, e.g. a protocol specification or standard. @return Provides additional information on the value returned by a given function. @param Documents the parameters of parameterized TTCN-3 definitions. @version States the version of a particular piece of TTCN-3 code. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 20 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the interworking type of ATS defined in the present document, the PIXIT are divided in SIP-related PIXIT and IMS-related PIXIT. NOTE: The tables in this clause have been generated automatically from the TTCN-3 modules. A.2.1 SIP-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. NOTE: The SIP-related PIXIT definitions are part of a SIP TTCN-3 library that contains additional PIXIT definitions on SIP and TS address information that are not used in this ATS and therefore not present in table A.1. 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 ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 21 No PIXIT Name Description 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) 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] 3.2.2.2 passwd of UE1: A known shared secret, the password of user of the specified username ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 22 No PIXIT Name Description 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] 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] 3.2.2.2 passwd of UE3: A known shared secret, the password of user of the specified username 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] 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 ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 23 No PIXIT Name Description 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 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 ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 24 No PIXIT Name Description 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 Table A.3: TIP/TIR-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) 3 PX_SIP_NameAddr_PAsserted_Tel_URI NameAddr default value for PAsserted2(with tel scheme) ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 25 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_18600503v020201p0.zip which accompanies the present document. ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 26 Annex C (informative): Bibliography ETSI TS 186 005-1: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Part 1: Protocol Implementation Conformance Statement (PICS)". 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 EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework". ETSI ETSI TS 186 005-3 V2.2.1 (2010-10) 27 History Document history V1.1.1 September 2008 Publication V2.1.1 September 2009 Publication V2.2.1 October 2010 Publication
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
1 Scope
|
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) of the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) services. Within the TISPAN NGN Release 2 Next Generation Network (NGN) the TS 183 008 [3] Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) PSTN/ISDN simulation services is specified. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document.
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
f112baf3880993acab42075b5abfe996
|
186 005-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] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax". [2] IETF RFC 3261: "SIP: Session Initiation Protocol". [3] ETSI TS 183 008 (V2.8.0): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) Protocol specification". [4] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". [5] IETF RFC 2806: "URLs for Telephone Calls". [6] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [7] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)". [8] ETSI TS 186 005-1: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Part 1: Protocol Implementation Conformance Statement (PICS)". ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 6 [9] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification". [10] ITU-T Recommendation Q.9: "Vocabulary of switching and signalling terms".
|
f112baf3880993acab42075b5abfe996
|
186 005-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 009-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks; Part 2: Test Suite Structure and Test Purposes (TSS&TP)".
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
3 Definitions and abbreviations
| |
f112baf3880993acab42075b5abfe996
|
186 005-2
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: abstract test case: Refer to ISO/IEC 9646-1 [6]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [6]. address identity: See Recommendation E.164 or/and RFC 2806 [5]. call: See ITU-T Recommendation Q.9 [10], definition 2201. dialog: Refer to RFC 3261 [2]. final response: Refer to RFC 3261 [2]. header: Refer to RFC 3261 [2]. header field: Refer to RFC 3261 [2]. identity information: includes all the information (RFC 2806 [5]/RFC 2396 [1]/E.164 [4]) identifying a user, including trusted (network generated) and/or untrusted (user generated) addresses Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [6]. implicit send event: Refer to ISO/IEC 9646-3 [7]. lower tester: Refer to ISO/IEC 9646-1 [6]. method: Refer to RFC 3261 [2]. option-tag: Refer to RFC 3261 [2]. PICS proforma: Refer to ISO/IEC 9646-1 [6]. PIXIT proforma: Refer to ISO/IEC 9646-1 [6]. point of control and observation: Refer to ISO/IEC 9646-1 [6]. Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [6]. Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [6]. provisional response: Refer to RFC 3261 [2]. ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 7 proxy, proxy server: Refer to RFC 3261 [2]. request: Refer to RFC 3261 [2]. response: Refer to RFC 3261 [2]. session: Refer to RFC 3261 [2]. (SIP) transaction: Refer to RFC 3261 [2]. system under test: Refer to ISO/IEC 9646-1 [6]. tag: Refer to RFC 3261 [2]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [6]. trusted identity: network generated user address information untrusted identity: user generated user address information voice session: existing voice connection between two terminal equipments NOTE: example via RTP.
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CDIV Communication DIVersion CN Core Network CSCF Call Session Control Function IBCF Interconnection Border Control Function IM IP Multimedia IP Internet Protocol ISDN Integrated Service Data Network NGN Next Generation Network P-CSCF Proxy - CSCF PSTN Public Switched Telephone Network RTP Real time Transport Protocol SDP Session Description Protocol SIP Session Initiation Protocol TIP Terminating Identification Presentation TIR Terminating Identification Restriction TP Test Purposes TSS Test Suite Structure UA User Agent UE User Equipment URI Universal Resource Identifier ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 8
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
4 Test Suite Structure (TSS)
|
User TermUserE TIP_U01_xxx OrigUserE TIP_U02_xxx Network entity DestAS TIP_N01_xxx OrigAS TIP_N02_xxx CDIV TIP_N03_xxx OtherNetw TIP_N04_xxx Figure 1: Test suite structure
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
4.1 Configuration
|
The scope of the current specification is to test the signalling and procedural aspects of the stage 3 requirements as described in TS 183 008 [3]. The stage 3 description describes the requirements for several network entities and also the requirements regarding for terminal devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different entities. Therefore to test the appropriate entities the configurations below are applicable:
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
4.1.1 Testing of the AS
|
The AS entity is responsible for performing and managing services. The ISC interface is the appropriate access point for testing. Figure 2: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also possible to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (see figure 3). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible. ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 9 CSCF (and/or AS) Implementation under Test Test System Test System Mw, Mg, Mx Mw, Mg, Mx Figure 3: Applicable interfaces for tests using a (generic) NNI interface
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
4.1.2 Testing of the UE
|
There are special clauses in the protocol standard describing the procedures that apply at the originating and terminating user equipment. Therefore the test configuration in figure 4 has been chosen. User Equipment Implementation under Test Test System Gm Figure 4: Applicable configuration to test UE functionalities
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
4.1.3 Testing of the IBCF
|
The IBCF is the separation point between trusted and entrusted IMS networks and can be tested with the test configuration in figure 5. Figure 5: Applicable configuration to test IBCF functionalities If the ISC interface is not accessible it is also possible to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (see figure 3). In case only the Gm interface is accessible this interface can be used instead for testing, but the verification of all requirements may not be possible. ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 10
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5 Test Purposes (TP)
| |
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.1 Introduction
|
For each test requirement a TP is defined. All PICS items referred to in this clause are as specified in TS 186 005-1 [8] unless indicated otherwise by another numbered reference.
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.1.1 TP naming convention
|
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "TIP" <iut> = type of IUT: U User N Network entity, e.g. P-CSCF <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.2 User TPs for TIP
| |
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.2.1 Terminating user equipment
|
Selection expression for group U01: PICS 1/2. TSS User/TermUserE TP TIP_U01_001 TIP/TIR reference 4.5.2.12 Selection expression PICS 2/6, 1/2 Test purpose: The Terminating UE supports the "from-change" tag in the Supported header. Ensure that the Terminating UE supports the "from-change" tag in the Supported header. If the UE receives a "from-change" tag in a Supported header in an initial INVITE, the UE sends the "from-change" tag in the Supported header in any provisional or final response message (e.g. 180, 183, 200). SIP messages: INVITE: Supported: from-change 18x/200: Supported: from-change Comments: Test equipment User equipment INVITE with "from-change" tag Provisional or final response with "from-change" tag ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 11 TSS User/TermUserE TP TIP_U01_002 TIP/TIR reference 4.5.2.12 Selection expression PICS 2/6, 1/2, 2/7 Test purpose: The Terminating UE sends an UPDATE request with an updated From and To header. Ensure that the Terminating UE supports the "from-change" tag in the Supported header. If the UE receives a "from- change" tag in a Supported header in an initial INVITE, the user equipment sends an UPDATE request after the ACK for the 200 OK INVITE was received containing a connected identity in the From header. SIP messages: INVITE: Supported: from-change 18x/200: Supported: from-change UPDATE: From <identity user equipment> Comments: Test equipment User equipment INVITE with "from-change" tag 180 Ringing 200 OK INVITE ACK UPDATE with updated From and To header 200 OK UPDATE TSS User/TermUserE TP TIP_U01_003 TIP/TIR reference 4.5.2.12 Selection expression PICS 2/3, 1/2 Test purpose: The Terminating UE overrides a default "Presentation not restricted" by sending Privacy "id". Ensure that the Terminating UE having subscribed to TIR temporary mode, default value "presentation not restricted", to override the default TIR setting, sends a Privacy header with value "id" in any non 100 response message (e.g. 180, 183, 200). SIP messages: 18x/200: Privacy: "id" Comments: Test equipment User equipment INVITE Non 100 response wit Privacy "id" TSS User/TermUserE TP TIP_U01_004 TIP/TIR reference 4.5.2.12 Selection expression PICS 2/4, 1/2 Test purpose: The Terminating UE overrides a default "Presentation restricted" by sending Privacy "none". Ensure that the Terminating UE having subscribed to TIR temporary mode, default value "presentation restricted", to override the default TIR setting, sends a Privacy header with value "none" in any non 100 response message (e.g. 180, 183, 200). SIP messages: 18x/200: Privacy: "none" Comments: Test equipment User equipment INVITE Non 100 response wit Privacy "none"
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.2.2 Originating user equipment
|
Selection expression for group U01: PICS 1/1 and 2/1. ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 12 TSS User/OrigUserE TP TIP_U02_001 TIP/TIR reference 4.5.2.1 Selection expression PICS 1/1 Test purpose: The originating UE receives one P-Asserted-Identity in a sip URI. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA containing a P-Asserted-Identity heeder with a valid sip URI accepts the call following the basic request handling procedures. Comments: User equipment Test equipment INVITE SIP_MESSAGE_VA With one P-Asserted-Identity TSS User/OrigUserE TP TIP_U02_002 TIP/TIR reference 4.5.2.1 Selection expression PICS 1/1 Test purpose: The originating UE receives one P-Asserted-Identity in a tel URI. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA containing a P-Asserted-Identity heeder with a valid tel URI, accepts the call following the basic request handling procedures. Comments: User equipment Test equipment INVITE SIP_MESSAGE_VA With one P-Asserted-Identity TSS User/OrigUserE TP TIP_U02_003 TIP/TIR reference 4.5.2.1 Selection expression PICS 1/1 Test purpose: The originating UE receives two P-Asserted-Identity headers in a sip URI and a tel URI. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA containing one P-Asserted-Identity header with a valid sip URI and one P-Asserted-Identity header with a valid tel URI, accepts the call following the basic request handling procedures. Comments: User equipment UA S INVITE SIP_MESSAGE_VA with two P-Asserted-Identity TSS User/OrigUserE TP TIP_U02_004 TIP/TIR reference 4.5.2.1 Selection expression PICS 1/1 Test purpose: The originating UE receives a Privacy header field value 'id' indicating the TIR service. Ensure that the Originating UE, receiving any non 100 response message defined as SIP_MESSAGE_VA with a Privacy header with privacy type of "id" and without P-Asserted-Identity headers, accepts the call following the basic request handling procedures. Comments: User equipment Test equipment INVITE SIP_MESSAGE_VA with Privacy 'id' without P-Asserted-Identity Values for tests purposes TIP_U02_001 to TIP_U02_004 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 13 TSS User/OrigUserE TP TIP_U02_005 TIP/TIR reference 4.5.2.1 Selection expression PICS 1/1,2/6 Test purpose: The originating user is able to send the "from-change" tag in the Supported header in the initial INVITE. Ensure that the Originating UE sends a "from-change" tag in the Supported header in the initial INVITE. SIP message: INVITE Supported "from-change" Comments: User equipment Test equipment INVITE with "from-change" tag TSS Syntax/OrigUserE TP TIP_U02_006 TIP/TIR reference 4.5.2.1 Selection expression PICS 1/1,2/1 AND PICS 2/6 Test purpose: The originating user is able to receive a connected identity in the From header of an UPDATE request. Ensure that the Originating UE is able to receive a second identity in the From header of an UPDATE request if the UE indicates the support of this procedure by sending the "from-change" tag in the Supported header in the initial INVITE and this identity is displayed to the user. SIP message: INVITE Supported "from-change" UPDATE From <second identity> Comments: User equipment SUT Test equipment INVITE with "from-change" tag 180 Ringing 200 OK INVITE ACK UPDATE with new URI in From header 200 OK UPDATE
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.3 Network entity TPs for TIP
| |
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.3.1 Requirements on the AS serving the terminating UE
|
TSS Network entity/DestAS TP TIP_N01_001 TIP/TIR reference 4.5.2.9 Selection expression Test purpose: The AS inserts the Privacy id value in the response if the response does not contain any Privacy. The terminating user subscribes to TIR in permanent mode. Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "permanent mode", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA without a Privacy header, the AS shall insert a Privacy header with privacy value "id" before forwarding the response. Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA with Privacy header "id" SIP_MESSAGE_VA without Privacy header ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 14 TSS Network entity/DestAS TP TIP_N01_002 TIP/TIR reference 4.5.2.9 Selection expression Test purpose: The AS inserts the Privacy id value in the response if the response contains Privacy "none". The terminating user subscribes to TIR in permanent mode. Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "permanent mode", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA with a Privacy header "none", the AS shall remove the "none" and insert a Privacy header with privacy value "id" before forwarding the response. Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA without Privacy header "id" SIP_MESSAGE_VA with Privacy header "none" TSS Network entity/DestAS TP TIP_N01_003 TIP/TIR reference 4.5.2.9 Selection expression Test purpose: The AS inserts the Privacy id value in the response if the response does not contain any Privacy. The user subscribes TIR temporary mode with default "presentation restricted". Ensure that the IUT acting as AS serving the terminating user that subscribes to TIR in "temporary mode" with default value "presentation restricted", receiving a 1xx or 2xx response message defined as SIP_MESSAGE_VA without a Privacy header, the AS shall insert a Privacy header with privacy value "id" before forwarding the response. Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA SIP_MESSAGE_VA Values for tests purposes TIP_N01_001 to TIP_N01_003 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK TSS Network entity/DestNetw TP TIP_N01_004 TIP/TIR reference 4.5.2.9 Selection expression Test purpose: The AS remove the "from-change" tag from the Supported header. The user subscribes TIR in permanent mode. Ensure that the IUT acting as AS serving the terminating user that subscribes to the TIR service in "permanent mode" removes the "from-change" tag from the Supported header in a received initial INVITE request before forwarding the request. SIP messages: INVITE1 Supported: "from-change" INVITE2 Supported without "from-change" Comments: Test equipment AS Test equipment INVITE1 with "from-change" tag INVITE2 without "from-change" tag ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 15 TSS Signalling/DestNetw TP TIP_N01_005 TIP/TIR reference 4.5.2.9 Selection expression Test purpose: The terminating user is not subscribed to the "no screening" special arrangement. Ensure that, if the IUT attempt to match the information in the From header with the set of registered public user identities for the served user and if no match is found, the AS changes the value of the From header in the UPDATE to the public user identity of the served user if the terminating user is not subscribed to the "no screening" special arrangement. SIP messages: UPDATE1: From <connected user identity> UPDATE2: From <public user identity> Precondition: The AS attempts to match the information in the From header fields of UPDATE messages and changes the value, if no match is found with any of the registered public user identities of the served user. Comments: Test equipment AS Test equipment INVITE INVITE 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK UPDATE2 UPDATE1 200 OK UPDATE 200 OK UPDATE
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.3.2 Requirements on the AS serving the originating UE
|
TSS Signalling/OrigNetw TP TIP_N02_001 TIP/TIR reference 4.3.2 Selection expression Test purpose: The originating user subscribes to the TIP service. Ensure that for originating users that subscribe to TIP simulation service, if network provided identity information about the terminator is available, and if presentation is not restricted, the AS shall pass that information in any non 100 response message defined as SIP_MESSAGE_VA. Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA with P-Asserted_Identity SIP_MESSAGE_VA with P-Asserted_Identity TSS Network entity/OrigNetw TP TIP_N02_002 TIP/TIR reference 4.5.2.4 Selection expression Test purpose: The originating user does not subscribe to the TIP service. Ensure that the IUT acting as AS serving the originating user that does not subscribe to the TIP service removes any P-Asserted-Identity header fields or Privacy header fields included in the SIP response defined as SIP_MESSAGE_VA before forwarding the response. Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA without P-Asserted_Identity and Privacy headers SIP_MESSAGE_VA with P-Asserted_Identity and Privacy headers ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 16 TSS Signalling/TIR TP TIP_N02_003 TIP/TIR reference 4.6.3 Selection expression Test purpose: The originating user has TIR override category Ensure that, if the originating user has the override category, the AS will remove Privacy header fields restricting the presentation of the terminating identity and will keep the P-Asserted-Identity header in the SIP response defined as SIP_MESSAGE_VA before forwarding the response. Precondition: Originating user has the override category SIP messages: SIP_MESSAGE_VA1: P-Asserted-Identity, Privacy = id SIP_MESSAGE_VA2: P-Asserted-Identity, no Privacy header or Privacy = none Comments: Test equipment AS Test equipment INVITE INVITE SIP_MESSAGE_VA2 SIP_MESSAGE_VA1 Values for tests purposes TIP_N02_001 to TIP_N02_003 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK TSS Network entity/OrigAS TP TIP_N02_004 TIP/TIR reference 4.5.2.4 Selection expression Test purpose: The originating user subscribes to the TIP service. The "from-change" tag is passed on. Ensure that the IUT acting as AS serving the originating user that subscribes to the TIP service passes on the "from change" tag from the Supported header in a received initial INVITE request before forwarding the request. SIP message: INVITE1 Supported "from-change" INVITE2 Supported "from-change" Comments: Test equipment AS Test equipment INVITE1 with "from-change" tag INVITE2 with "from-change" tag TSS Network entity/OrigAS TP TIP_N02_005 TIP/TIR reference 4.5.2.4 Selection expression Test purpose: The originating user subscribes to the TIP service. The "from-change" tag is not received. Ensure that the IUT acting as AS serving the originating user that subscribes to the TIP service, receiving an initial INVITE request without the "from-change" tag into the Supported header, inserts the "from-change" tag into the Supported header before forwarding the request. SIP message: INVITE1 Supported "from-change" not included INVITE2 Supported "from-change" Comments: Test equipment AS Test equipment INVITE1 without "from-change" tag INVITE2 with "from-change" tag TSS Network entity/OrigAS TP TIP_N02_006 TIP/TIR reference 4.5.2.4 Selection expression Test purpose: The originating user does not subscribe to the TIR service. The "from-change" tag is removed from the Supported header. Ensure that the IUT acting as AS serving the originating user that does not subscribe to the TIP service removes the "from-change" tag from the Supported header in a received initial INVITE request before forwarding the request. SIP message: INVITE1 Supported "from-change" INVITE2 Supported "from-change" not included Comments: Test equipment AS Test equipment INVITE INVITE ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 17
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.3.3 Communication diversion services
|
TSS Network entity/CDIV TP TIP_N03_001 TIP/TIR reference 4.6.7 Selection expression Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in permanent mode and the originating user has subscribed to the TIP service, no P-Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info Header entry identifying the diverted-to user is removed from the History -Info header. Precondition: Test equipment (Diverting user) activates Communication diversion unconditional with option "originating user is notified of diversion with the diverted-to address". Comments: Test equipment (Originating user) SUT Test equipment (Diverted-to user) INVITE INVITE 181 Call is being forwarded History-Info header without URI of the diverted-to user SIP_MESSAGE_VA without P-Asserted-Identity SIP_MESSAGE_VA TSS Network entity/CDIV TP TIP_N03_002 TIP/TIR reference 4.6.7 Selection expression Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in temporary mode default "presentation restricted" and the originating user has subscribed to the TIP service, when the diverted-to user has send no Privacy header within the SIP_MESSAGE_VA response, no P- Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info Header entry identifying the diverted-to user is removed from the History -Info header. Precondition: Test equipment (Diverting user) activates Communication diversion unconditional with option "originating user is notified of diversion with the diverted-to address". Comments: Test equipment (Originating user) SUT Test equipment (Diverted-to user) INVITE INVITE 181 Call is being forwarded History-Info header without URI of the diverted-to user SIP_MESSAGE_VA without P-Asserted-Identity SIP_MESSAGE_VA TSS Network entity/CDIV TP TIP_N03_003 TIP/TIR reference 4.6.7 Selection expression Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in temporary mode default "presentation not restricted" and the originating user has subscribed to the TIP service, when the diverted-to user has send a Privacy header with value "id" within the SIP_MESSAGE_VA response, no P-Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. The History-Info Header entry identifying the diverted-to user is removed from the History -Info header. Precondition: Test equipment (Diverting user) activates Communication diversion unconditional with option "originating user is notified of diversion with the diverted-to address". Comments: Test equipment (Originating user) SUT Test equipment (Diverted-to user) INVITE INVITE 181 Call is being forwarded History-Info header without URI of the diverted-to user SIP_MESSAGE_VA without P-Asserted-Identity SIP_MESSAGE_VA with Privacy "id" ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 18 TSS Network entity/CDIV TP TIP_N03_004 TIP/TIR reference 4.6.7 Selection expression Test purpose: Ensure that if the served (diverting) user of the communication diversion service selects the option that the originating user is notified of diversion with the diverted-to address and the diverted-to user has subscribed to the TIR service in temporary mode default "presentation restricted" and the originating user has subscribed to the TIP service, when the diverted-to user has send a Privacy header with value "none" within the SIP_MESSAGE_VA response, the P- Asserted-Identity header including the URI of the diverted-to user is sent within the SIP_MESSAGE_VA response to the originating user. Precondition: Test equipment (Diverting user) activates Communication diversion unconditional with option "originating user is notified of diversion with the diverted-to address". Comments: Test equipment (Originating user) SUT Test equipment (Diverted-to user) INVITE INVITE 181 Call is being forwarded SIP_MESSAGE_VA with P-Asserted-Identity SIP_MESSAGE_VA with Privacy "none" Values for tests purposes TIP_N03_001 to TIP_N03_004 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
5.3.4 Requirements on the interconnection with other IP network
|
TSS Network entity/OtherNetw TP TIP_N04_001 TIP/TIR reference 4.7.3 Selection expression Test purpose: Interworking with a trusted network; SUT is call destination Ensure that a SIP response defined as SIP_MESSAGE_VA including P-Asserted-Identity header fields for a request from a trusted network is received; the outgoing IBCF shall retain the P-Asserted-Identity header fields in the response. Comments: Test equipment (Ic) IBCF Test equipment (Mx) INVITE INVITE SIP_MESSAGE_VA with P-Asserted-Identity header SIP_MESSAGE_VA with P-Asserted-Identity header TSS Network entity/OtherNetw TP TIP_N04_002 TIP/TIR reference 4. .37 Selection expression Test purpose: Interworking with an un-trusted network; SUT is call destination Ensure that a SIP response defined as SIP_MESSAGE_VA including P-Asserted-Identity header fields for a request from an un-trusted network is received; the outgoing IBCF shall remove the P-Asserted-Identity header fields from the response. Comments: Test equipment (Ic) IBCF Test equipment (Mx) INVITE INVITE SIP_MESSAGE_VA without P-Asserted-Identity header SIP_MESSAGE_VA with P-Asserted-Identity header ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 19 TSS Network entity/OtherNetw TP TIP_N04_003 TIP/TIR reference 4.7.3 Selection expression Test purpose: Interworking with a trusted network; SUT is call origination Ensure that a communication is established to a trusted network and P-Asserted-Identity header fields are included in SIP responses from the other IP network defined as SIP_MESSAGE_VA, the incoming IBCF shall retain the P-Asserted-Identity header fields. Comments: Test equipment (Mx) IBCF Test equipment (Ic) INVITE INVITE SIP_MESSAGE_VA with P-Asserted-Identity header SIP_MESSAGE_VA with P-Asserted-Identity header TSS Network entity/OtherNetw TP TIP_N04_004 TIP/TIR reference 4.7.3 Selection expression Test purpose: Interworking with an un-trusted network; SUT is call origination Ensure that a communication is established to an un-trusted network and P-Asserted-Identity header fields are included in SIP responses from the other IP network defined as SIP_MESSAGE_VA, the incoming IBCF shall remove the P-Asserted-Identity header fields from the SIP response. Comments: Test equipment (Mx) IBCF Test equipment (Ic) INVITE INVITE SIP_MESSAGE_VA without P-Asserted-Identity header SIP_MESSAGE_VA with P-Asserted-Identity header Values for tests purposes TIP_N04_001 to TIP_N04_004 VA_01 180 Ringing VA_02 183 Session progress VA_03 200 OK
|
f112baf3880993acab42075b5abfe996
|
186 005-2
|
6 Compliance
|
An ATS which complies with the present document shall: a) consist of a set of test cases corresponding to the set or to a subset of the TPs specified in clause 5; b) use a TSS which is an appropriate subset of the whole of the TSS specified in clause 4; c) use the same naming conventions for the test groups and test cases; d) maintain the relationship specified in clause 5 between the test groups and TPs and the entries in the PICS proforma to be used for test case deselection; e) comply with ISO/IEC 9646-2 [9]. In the case of a) or b) above, a subset shall be used only where a particular Abstract Test Method (ATM) makes some TPs untestable. All testable TPs from clause 5 shall be included in a compliant ATS. ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 20 Annex A (informative): Bibliography • ETSI TS 122 228: "Service requirements for the IP multimedia core network subsystem; Stage 1". • ETSI TS 123 002: "Network architecture". • ETSI TS 123 003: "Numbering, addressing and identification". • ETSI TS 123 228: "IP multimedia subsystem; Stage 2". • ETSI TS 124 229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP)and Session Description Protocol (SDP);Stage 3". • IETF RFC 3966: "The tel URI for Telephone Numbers". • ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". • IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)". • IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks". ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 21 Annex B (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 10-06- 09 21PTD088 001 F Update of complete document during STF368's first work session 2.1.1 2.1.2 Publication 2.1.2 2.2.1 ETSI ETSI TS 186 005-2 V2.2.1 (2009-07) 22 History Document history V2.1.1 February 2009 Publication V2.2.1 July 2009 Publication
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
1 Scope
|
The present document specifies the Protocol implementation conformance statement (PICS) for the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) NGN Basic Service, TS 183 008 [10]. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document. Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The TIP service provides the originating party with the possibility to receive a trusted (network-provided) identity of the terminating party, and is applicable to all session-based services of the NGN. The OIR service enables the terminating party to prevent presentation of any network-provided identity to the originating party, and is applicable to all session-based services of the NGN.
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version 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.
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [2] ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". [3] ETSI EN 300 089: "Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) supplementary service; Service description". [4] ETSI EN 300 090: "Integrated Services Digital Network (ISDN); Calling Line Identification Restriction (CLIR) supplementary service; Service description". [5] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)". [6] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks". ETSI ETSI TS 186 005-1 V2.1.1 (2009-02) 6 [7] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax". [8] IETF RFC 3966: "The tel URI for Telephone Numbers". [9] IETF RFC 3261: "SIP: Session Initiation Protocol". [10] ETSI TS 183 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification". [11] Void. [12] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [13] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)". [14] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [15] ETSI TS 183 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification".
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
3 Definitions and abbreviations
| |
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: abstract test case: Refer to ISO/IEC 9646-1 [12]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [12]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [12]. implicit send event: Refer to ISO/IEC 9646-3 [13]. lower tester: Refer to ISO/IEC 9646-1 [12]. Point of Control and Observation (PCO): Refer to ISO/IEC 9646-1 [12]. Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [12]. PICS proforma: Refer to ISO/IEC 9646-1 [12]. Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [12]. PIXIT proforma: Refer to ISO/IEC 9646-1 [12]. system under test: Refer to ISO/IEC 9646-1 [12]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [12]. ETSI ETSI TS 186 005-1 V2.1.1 (2009-02) 7
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AS Application Server CLIP Calling Line Identification Presentation CLIR Calling Line Identification Restriction IP Internet Protocol ISDN Integrated Service Data Network IUT Implementaion Under Test n/a not applicable NGN Next Generation Network OIR Originating Identification Restriction PSTN Public Switched Telephone Network SDP Session Description Protocol SIP Session Initiation Protocol SUT System Under Test TIP Terminating Identification Presentation TIR Terminating Identification Restriction URI Universal Resource Identifier 4 Protocol Implementation Conformance Statement (PICS) 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.
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
4.1 Instructions for completing the PICS proforma
|
4.1.1 More detailed instructions are given at the beginning of the different clauses of the PICS proforma. The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5.
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
4.1.1.1 Purposes and structure
|
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in reference specifications [1] to [10] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of 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). ETSI ETSI TS 186 005-1 V2.1.1 (2009-02) 8
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
4.1.2 Abbreviations and conventions
|
The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [14]. Item column: It contains a number that identifies the item in the table. Item description column: It describes each respective item (e.g. parameters, timers, etc.). Reference column: It gives reference to the TIP/TIR specification [10], except where explicitly stated otherwise. Status column: The following notations, defined in ISO/IEC 9646-7 [14], 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. 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 specifications [1] to [10]. 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 [14], 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).
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
4.2 Identification of the implementation
|
Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the ICS should be named as the contact person. ETSI ETSI TS 186 005-1 V2.1.1 (2009-02) 9
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
4.2.1 Date of the statement
|
Date of the statement:
|
8aabeb8f451991c8be3dd27eacf2cd2f
|
186 005-1
|
4.2.2 Implementation Under Test (IUT) identification
|
IUT name: IUT version:
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.