hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
f33e61678ba2128cc7b64c3ba6f33e28
|
102 891-1
|
3 Definitions and abbreviations
| |
f33e61678ba2128cc7b64c3ba6f33e28
|
102 891-1
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 406 [1], ISO/IEC 9646-1 [2], ISO/IEC 9646-7 [3] and the following apply: PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system becomes a PICS Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification NOTE: This may contain additional information. ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 6 Protocol Implementation Conformance Statement (PICS): statement made by the supplier of an implementation or system claimed to conform to a given protocol specification, stating which capabilities have been implemented
|
f33e61678ba2128cc7b64c3ba6f33e28
|
102 891-1
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 406 [1] and the following apply: ICS Implementaion Conformance Statement IUT Implementation Under Test MA Message Account MIME Multipurpose Internet Mail Extensions MNUA MWI Notifier User Agent MSUA MWI Subscriber User Agent MWI Message Waiting Indication PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement SCS System Conformance Statement SUT System Under Test ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 7 Annex A (normative): PICS proforma for TS 124 406 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 ICS proforma in this annex so that it can be used for its intended purposes and may further publish the completed ICS. A.1 Guidance for completing the ICS proforma A.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 TS 124 406 [1] may provide information about the implementation in a standardized manner. The ICS proforma is subdivided into clauses for the following categories of information: - guidance for completing the ICS proforma; - identification of the implementation; - identification of the <reference specification type>; - global statement of conformance; - roles; - user role; - network role. A.1.2 Abbreviations and conventions The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [3]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 8 Status column The following notations, defined in ISO/IEC 9646-7 [3], are used for the status column: m mandatory - the capability is required to be supported. o optional - the capability may be supported or not. n/a not applicable - in the given context, it is impossible to use the capability. x prohibited (excluded) - there is a requirement not to use this capability in the given context. 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", "x" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression which is defined immediately following the table. Reference column The reference column makes reference to TS 124 406 [1], except where explicitly stated otherwise. 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 [3], are used for the support column: Y or y supported by the implementation. N or n not supported by the implementation. N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status). If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able to answer that a capability is supported for one profile and not supported for another. In that case, the supplier shall enter the unique reference to a conditional expression, preceded by "?" (e.g. ?3). This expression shall be given in the space for comments provided at the bottom of the table. It uses predicates defined in the SCS, each of which refers to a single profile and which takes the value TRUE if and only if that profile is to be used. EXAMPLE 1: ?3: IF prof1 THEN Y ELSE N In case of protocol, the following text should be added: NOTE: As stated in ISO/IEC 9646-7 [3], support for a received PDU requires the ability to parse all valid parameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter is non- conformant. Support for a parameter on a PDU means that the semantics of that parameter are supported. Prerequisite line A prerequisite line takes the form: Prerequisite: <predicate>. A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is FALSE. A.1.3 Instructions for completing the PICS proforma The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an explicit answer shall be entered, in each of the support column boxes provided, using the notation described in clause A.1.2. ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 9 However, the tables containing in "user role" clause shall only be completed for user implementations, and the tables containing in "network role" clause shall only be completed for network implementations. If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately. More detailed instructions are given at the beginning of the different clauses of the PICS proforma. A.2 Identification of the implementation Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person. A.2.1 Date of the statement ......................................................................................................................................................................................... A.2.2 Implementation Under Test (IUT) identification IUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... IUT version: ......................................................................................................................................................................................... A.2.3 System Under Test (SUT) identification SUT name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Operating system: ......................................................................................................................................................................................... A.2.4 Product supplier Name: ......................................................................................................................................................................................... ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 10 Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.5 Client (if different from product supplier) Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 11 A.2.6 PICS contact person (A person to contact if there are any queries concerning the content of the ICS) Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.3 Identification of the MWI specification This PICS proforma applies to the following standard: ETSI TS 124 406 (2008): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification (3GPP TS 24.406 Release 8)". A.4 Global statement of conformance Are all mandatory capabilities implemented? (Yes/No) ..................... NOTE: Answering "No" to this question indicates non-conformance to the MWI specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma. ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 12 A.5 Roles Table A.1: Roles Item Role Reference Status Support 1 MWI Subscriber User Agent (MSUA) 4.4.1 o 2 MWI Notifier User Agent (MNUA) 4.4.2 m 3 Message Account (MA) 4.4.3 m Comments: A.6 User role This clause contains the PICS proforma tables related to the user role. They need to be completed only for user equipment implementations: Prerequisite: A.1/1 -- user role A.6.1 Major capabilities Table A.2: MWI Subscriber User Agent capabilities Item Item description Reference Status Support 1 The user Equipment is able to address the message account using the public service identity 4.4.3.2 o.1 2 The user Equipment is able to address the message account using the public user identity 4.4.3.2 o.1 o.1: It is mandatory to support at least one of these items. Comments: A.7 Network role This clause contains the PICS proforma tables related to the network role. They need to be completed only for network implementations: Prerequisite: A.1/2 network role Table A.3: MWI Notifier User Agent (MNUA) capabilities Item Item description Reference Status Support 1 The MNUA includes the message account in the MIME body to identify the served user 3.5 [4] o 2 The MNUA includes the message summary line in the MIME body to identify the served user 3.5 [4] o 3 The MNUA append message headers, which further describe newly added messages as "opt-msg- headers" 3.5 [4] o ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 13 Annex B (informative): Bibliography ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". ETSI ETSI TS 102 891-1 V3.1.1 (2010-07) 14 History Document history V3.1.1 July 2010 Publication
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
1 Scope
|
The purpose of the present document is to provide the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for conformance tests of the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5] and ETS 300 406 [6]. The content of the present document follows the requirements that have been first collected in an internal unpublished requirements catalogue and is written according to the guidelines of TS 102 351 [12], ISO/IEC 9646-1 [4] and ETS 300 406 [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.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-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.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. NOTE: References have been used both in the present document and in the TTCN-3 library modules (annex B). [1] ETSI TS 102 790-2: "IMS Network Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 2: Test Suite Structure (TSS) and Test Purposes (TP)". [2] ETSI TS 124 229 (V10.7.0): "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 version 10.7.0 Release 10)". ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 6 [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". [5] ISO/IEC 9646-7: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements". [6] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [7] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [8] ETSI ES 201 873-2: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)". [9] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)". [10] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)". [11] ETSI TS 102 027-3 (V3.1.1): "Methods for Testing and Specification (MTS); Conformance Test Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma". [12] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework".
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework". [i.2] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification". [i.3] IETF RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method". [i.4] IETF RFC 3313: "Private Session Initiation Protocol (SIP) Extensions for Media Authorization". [i.5] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". [i.6] IETF RFC 3327: "Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts". [i.7] IETF RFC 3329: "Security Mechanism Agreement for the Session Initiation Protocol (SIP)". [i.8] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging". [i.9] IETF RFC 3455: "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)". [i.10] IETF RFC 3608: "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)". [i.11] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". [i.12] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". [i.13] Draft-drage-sipping-service-identification-01: "A Session Initiation Protocol (SIP) Extension for the Identification of Services". ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 7
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
3 Definitions and abbreviations
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [5] 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].
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-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: AS Application Server ATS Abstract Test Suite CSCF Call Session Control Function E-CSCF Emergency CSCF IBCF Interconnection Border Control Function I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IP Internet Protocol IUT Implementation Under Test P-CSCF Proxy CSCF PICS Protocol Implementation Conformance Statement PIXIT Partial Protocol Implementation Extra Information for Testing PTC Parallel Test Component S-CSCF Serving CSCF SDP Session Description Protocol SIP Session Initiation Protocol SUT System under Test TC Test Case TP Test Purpose TS Test System TSS Test Suite Structure TTCN-3 Testing and Test Control Notation version 3 UE User Equipment ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 8
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4 Abstract Test Method (ATM)
|
This clause describes the ATM used to test TS 124 229 [2].
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.1 Network architecture
|
IMS interface under test: Figure 1
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.2 Protocol architecture
|
The Implementation Under Test (IUT) for which this test case specification applies consists of the SIP protocol (see figure 1a). AS IMSx IMSx UE SUT Mw Ic Isc Gm SIP protocol ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 9 SUT IMS CN SIP/IMS Extension SIP RFC 3261 Compression algorithms (2) UDP TCP Security Algorithms (2) IPV4/IPV6 (1) (LAN) (1) Both IPV4 and IPV6 addressing should be supported. (2) Optional security and compression algorithms should be supported. Figure 1a: SIP protocol architecture
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3 Test architecture
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.1 Test configuration
|
The target SUT to be covered by the test purposes of TS 124 229 [2] document 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. Dashed boxes are introduced to visualize the assumption of any UE, but do not imply the implementation of the related user behaviour scenarios.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.1.1 Configurations using Gm interface only
|
The Gm interface is located between UE and the SUT. TS IMS UE Gm SUT Figure 1b: Test configuration CF_1Gm ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 10 TS IMS UE1 Gm1 SUT Gm2 UE2 Figure 2: Test configuration CF_2Gm
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.1.2 Configurations using the Mw interface
|
The Mw interface is located between two different IMS, e.g. due to at least one user visiting a network outside of the home network. This interface is used only if no special functions are required to use the Ic interface, e.g. the topology hiding. TS IMS IMS UE Mw Gm SUT Figure 3: Test configuration CF_1Mw TS TS IMS IMS UE2 Mw Gm UE1 Gm SUT Figure 4: Test configuration CF_1Mw1Gm TS TS IMS1 UE1 Mw1 Gm UE2 Mw2 IMS2 Gm IMS SUT Figure 5: Test configuration CF_2Mw
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.1.3 Configurations using the Ic interface
|
The Ic interface is located between two different IMS, e.g. due to any user visit outside of the home network. This interface is used only if special functions (e.g. topology hiding) are required to use the Ic interface instead of the Mw. TS IMS IMS UE Ic Gm SUT Figure 6: Test configuration CF_1Ic ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 11 TS IMS IMS UE2 Ic Gm SUT TS UE1 Gm Figure 7: Test configuration CF_1Ic1Gm TS IMS IMS UE2 Ic1 Gm SUT Ic2 TS UE1 Gm Figure 8: Test configuration CF_2Ic1Gm
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.1.4 Configurations using the ISC interface
|
The ISC interface provides an access to the AP. TS IMS AS ISC SUT TS UE1 Gm Figure 9: Test configuration CF_1ISC1Gm TS IMS AS1 ISC SUT TS UE1 Gm1 UE2 Gm2 Figure 10: Test configuration CF_1ISC2Gm TS IMS AS1 ISC1 SUT TS UE1 ISC2 AS2 TS UE1 Gm1 UE2 Gm2 Figure 11: Test configuration CF_2ISC2Gm ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 12
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.2 Interconnection of TS and SUT
|
Figure 12 shows the interconnection of TS and SUT in terms of signalling message flows. map(p_sipComponent_gm1:SIPP, system: gm1); map(p_sipComponent_gm2:SIPP, system: gm2); map(p_sipComponent_mw1:SIPP, system: mw1); map(p_sipComponent_mw2:SIPP, system: mw2); map(p_sipComponent_ic1:SIPP, system: ic1); map(p_sipComponent_ic2:SIPP, system: ic2 ); map(p_sipComponent_isc1:SIPP, system: isc1); map(p_sipComponent_isc2:SIPP, system: isc2); TS IMS1 AS1 UE1 port:sipp port:sipp port:sipp port:gm1 port:gm2 port:isc1 port:isc2 UE2 port:sipp AS2 port:sipp IMS2 IBCF1 IBCF2 port:mw1 port:mw2 port:ic1 port:ic2 SUT IMS Figure 12
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3 Test system architecture
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3.1 General
|
Test systems that implement this ATS shall conform to the requirements as defined in this clause. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 13
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3.2 Structure
|
An abstract architecture for a test system (TS) implementing a TTCN-3 ATS is displayed in figure 13 and also stated in ES 201 873-5 [9]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (SA) Platform Adapter (PA) Figure 13: Abstract Test System Architecture A TS has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and Platform Adapter (PA) entities, respectively. Out of these two interfaces the TRI has been standardized in ES 201 873-5 [9], whereas the specification and implementation of the TCI is in ES 201 873-6 [10]. The part of TS that deals with interpretation and execution of TTCN-3 modules, i.e. the Executable Test Suite (ETS), is shown as part of the TTCN-3 Executable (TE). This ETS corresponds either to the executable code produced by a TTCN-3 compiler or a TTCN-3 interpreter from the TTCN-3 ATS in a TS implementation. The remaining part of the TS, which deals with any aspects that cannot be concluded from information being present in the TTCN-3 ATS alone, can be decomposed into Test Management (TM), SUT Adapter (SA) and Platform Adapter (PA) entities. In general, these entities cover a TS user interface, test execution control, test event logging, communication of test data with the SUT, and timer implementation. The part of SA used for SIP message transfer shall implement the TRI adaptation as well as the SIP transport protocol architecture described in clause 4.2. The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, with the TE and Test Logging (TL) entity within the TM shall comply with the conventions defined in clause 4.3.2 of TS 102 027-3 [11].
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA)
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3.3.1 Sending and receiving SIP/IMS messages
|
Before starting a test case, the SA shall be prepared to provide the transport of SIP messages by establishing appropriate connections on the lower layers (see figure 13).
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3.3.2 Security & messages compression feature
|
According to figure 13 description, security transport layer, and signalling compression may be used transparently to the ATS, as far as these mechanism does not affect the SIP protocol itself. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 14
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3.4 Encoding/Decoding requirements
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
4.3.3.4.1 Encoding/Decoding System requirements for basic SIP messages/headers
|
SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use a EDS to parse received encoded messages into TTCN-3 type structures and values, and encode structured TTCN-3 type structures and values into encoded messages. This EDS is not part of the ATS. Still all encoded messages, i.e. the messages as they are transmitted by the SA to or received by the SA from the SUT, shall be logged. The following terms shall be used for the conventions defined below: Syntactic delimiter syntactic delimiters are characters like "=" or ";" that are used to separate encoded values. LWS linear white spaces as defined in RFC 3261 [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 to the definition of NOT APPLICABLE in RFC 3261 [3], section 20 for request messages. 4.3.3.4.1.1 Encoding requirements TTCN-3 fields should not contain syntactic delimiters like white space, semicolon, equal characters etc. in fully decoded fields. Instead the information provided by a parser shall be used to build the decoded message in TTCN-3. Decoded messages shall use the TTCN-3 enumeration types where ever appropriate, e.g. for the method and the header field name. For charstring fields the following decoding rules shall be applied by the EDS: 1) Subsequent LWS shall compress to a single space character " ". 2) Decoded parameter names shall use only lower case letters. 3) Parameter values containing an integer value shall be decoded to a TTCN-3 integer value where a TTCN-3 integer type is used for a SIP parameter value. The following decoding rules shall be applied by the EDS to each received message in the following order: 1) In case a request message indicating an undefined method is received by the test system, the message shall not be passed in the TE to the ETS. However the message is subject to logging as defined in clause 4.3.3 ("Logging conventions"). 2) In case an undefined header has been received the header field shall be decoded as UndefinedHeader field. RFC 3261 [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. 4.3.3.4.1.2 Decoding 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 section 7.3.1 of RFC 3261 [3]. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 15 Values of type Raw shall be send to the SUT without any modification. 4.3.3.4.2 Encoding/Decoding System requirements for basic SIP and SIP/IMS specific messages and headers For SIP/IMS testing purpose, new SIP messages and specific header should be supported by the encoding/decoding system. The rules edicted above should apply. Hereafter the complete set of message and header being supported, including the corresponding RFC. Table 1: IMS Basic and Specific messages Msg-Name RFC Gm tx Gm rx Ic tx Ic rx Isc tx Isc rx Mw tx Mw rx Requests ACK 3261 [3] x x x x x x x x BYE 3261 [3] x x x x - - x x INVITE 3261 [3] x x x x - - x x CANCEL 3261 [3] x x x x - - x x MESSAGE 3428 [i.8] x x x x x - x x NOTIFY 3265 [i.2] - - - - - - x - SUBSCRIBE 3265 [i.2] - x - - - - x - PUBLISH x x - - - - x x UPDATE 3311 [i.3] x x - - - - x x PRACK 3262 [i.5] x x - - - - x x REGISTER (unprotected) 3261 [3] - x x (see note 1) - x (see note 1) - x (see note 1) x (see note 1) REGISTER (protected) 3261 [3] - x x (see note 1) - x (see note 1) - x (see note 1) x (see note 1) Responses 100 3261 [3] x ? (see note 2) x ? (see note 2) - - x ? (see note 2) 180 3261 [3] x x x x x - x x 200 3261 [3] x x x x x - x x 3xx 3261 [3] - - - x - - - x 380 3261 [3] x - - - - - - - 4xx 3261 [3] x x - - - - x - 400 3261 [3] x - - - - - x - 401 3261 [3] x - - - - - x x 403 3261 [3] x - x - - - x - 404 3261 [3] - - - - - - x - 408 3261 [3] x - x - - x - - 422 3261 [3] x - - - - - - - 423 3261 [3] - - - - - - x - 480 3261 [3] - - - x - - - 481 3261 [3] x - - - - - - 488 3261 [3] - - - - - - x - 5xx 3261 [3] - - - - - x - - 504 3261 [3] x - x - - - - - NOTE 1: Not clear, if protected or unprotected REGISTER is used here. NOTE 2: 100 not mentioned in any TP, may still be needed in the ATS to acknowledge outstanding INVITE requests. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 16 Table 2: IMS specific headers Header-Name RFC Gm Ic Isc Mw Min-SE 4028 [i.11] x - - - Path 3327 [i.6] - x - x P-Access-Network-Info 3455 [i.9] x - x x P-Asserted-Service draft-drage-sipping-service- identification-01 [i.13] - - x - P-Charging-Function-Addresses 3455 [i.9] x x x x P-Charging-Vector 3455 [i.9] x x x x P-Media-Authorization 3313 [i.4] x - - x P-Visited-Network-ID 3455 [i.9] - - x x Security-Client 3329 [i.7] x - - x Security-Server 3329 [i.7] x - - - Security-Verify 3329 [i.7] x - - x Service-Route 3608 [i.10] x - - - Session-Expires 4028 [i.11] x - - - NOTE: P-Called-Party-ID header (RFC 3455 [i.9]) may be also necessary.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5 The ATS development process
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 6 of TS 102 790-2 [1]. The requirements applicable to this TP are given by a reference to RFC 3261 [3] (SIP) or TS 124 229 [2]. There are no explicit formulations of requirements.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.2 ATS structure
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.2.1 Test case grouping
|
The ATS structure defined in table 3 is based on the structuring of Test Purposes in clause 5 of TS 102 790-2 [1]. The group names in columns 1 to 2 of table 3 are those assigned in the ATS; they are based on the names provided in clause 5 of TS 102 790-2 [1], but use the naming conventions defined for the ATS (see clause 5.3.2.2 of the present document. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 17 Table 3: ATS structure Group Sub-group TC-Identifier Gm Interface General GM_GEN Registration procedures GM_REG Initial dialog request procedures GM_INI Standalone requests procedures GM_STA Subsequent requests on a dialog procedures GM_SUB Target refresh request procedures GM_TAR Emergency GM_EME Exceptional procedures GM_EXC SDP GM_SDP NAT Traversal GM_NAT Mw Interface General MW_GEN Registration procedures MW_REG Initial dialog request procedures MW_INI Standalone requests procedures MW_STA Subsequent requests on a dialog procedures MW_SUB Target refresh request procedures MW_TAR Emergency MW_EME SDP MW_SDP Ic Interface General IC_GEN Registration procedures IC_REG Initial dialog request procedures IC_INI Standalone requests procedures IC_STA Subsequent requests on a dialog procedures IC_SUB Target refresh request procedures IC_TAR ISC Interface Registration procedures ISC_REG Initial dialog request procedures ISC_INI Standalone requests procedures ISC_STA Subsequent requests on a dialog procedures ISC_SUB Target refresh request procedures ISC_TAR ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 18
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: Table 3a: TC identifier naming convention scheme Identifier: TC_<ts>_<int><subgroup>_<nn> <ts> = Test suite name: i.e. "IMST2" IMS version 2 <int> = type of Interface: i.e. "MW" Mw interface <subgroup> = subgroup 3 first letter of the subgroup according to TSS subdivision (i.e. GEN for general) <nn> = sequential number (01 to 99) EXAMPLE : TC_IMST2_GM_GEN_01 stands for 1st test case in the Gm interface only group, and in the general subgroup. NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 102 790-2 [1], and test case names. The TP identifier of TC_IMST2_GM_GEN_01 is TP_IMST2_GM_GEN_01.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.3 ATS specification framework
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.3.1 ATS Library
|
For this ATS the TTCN-3 library modules are basically organized as: 1) SIP/IMS modules; 2) SIP Common modules (RFC 3261 [3]); 4) LibCommon modules (taken from TS 102 351 [12]). ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 19 Table 4 shows the organization of the ATS as library of modules. Table 4: Library of modules Module Class Module Id Description LibCommon LibCommon_AbstractData Generic data types for a stack and its operations. LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean). LibCommon_DataStrings Bit and Octet string types. LibCommon_Sync Co-ordination/synchronization of test components. LibCommon_TextStrings Basic character and string types with fixed length. LibCommon_Time Time handling functions and module parameter. LibCommon_VerdictControl Basic functions for setting of test component verdicts. 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 (see note). 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 type system for SIP tests. XSDAUX ASN.1 base type definitions. SIP/IMS Ats AtsIms_PICS Module Parameter declarations associated with PICS. AtsIms_PIXITS Module Parameter declarations associated with PIXIT. AtsIms_Testcases Test case definitions for the complete module. AtsIms_TestConfiguration Functions for mapping of test components to help setup and tear down different test configurations and configuration of the SUT adapter. AtsIms_TestExecution Module control: execute test cases depending on selection conditions. AtsIms_TestSystem TSI components, test system internal ports. AtsIms_Testcases Test case definitions for the complete module. AtsIms_Gm_TCFunctions TC functions used by the test component for test on the Gm configurations. AtsIms_Gm_Testcases Test case definitions for the Gm configurations. AtsIms_Mw_TCFunctions TC functions used by the test component for test on the Mw configurations. AtsIms_Mw_Testcases Test case definitions for the Mw configurations. AtsIms_Ic_TCFunctions TC functions used by the test component for test on the Ic configuration. AtsIms_Ic_Testcases Test case definitions for the Ic configuration. AtsIms_Isc_TCFunctions TC functions used by the test component for test on the ISC configuration. AtsIms_Isc_Testcases Test case definitions for the ISC configuration. NOTE: This module also addresses test case definition for additional supplementary services and is provided for common test execution to simplify test management.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.3.2 Use of TTCN-3
| |
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.3.2.1 General
|
TTCN-3 as defined in ES 201 873-1 [7] is used as ATS specification language. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 20 A number of requirements have been identified for the development and production of the TTCN-3 specification for the SIP/ISUP Interworking ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and naming conventions. 4) TTCN-3 is human-readability. 5) TTCN-3 specification is feasible, implementable, compilable and maintainable. 6) Test cases shall be designed in a way to be easily adaptable, upwards compatible with the evolution of the base protocol and protocol interworking of future releases. 7) The test declarations, data structures and data values shall be largely reusable. 8) Modularity and modular working method. 9) Minimizing the requirements of intelligence on the emulators of the lower testers. 10) Giving enough design freedom to the test equipment manufacturers. Fulfilling these requirements should ensure the investment of the test equipment manufacturers and users of the ATS having stable testing means for a relatively long period.
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-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 9 of [8] 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 5 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 21 Table 5: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Module Use upper-case initial letter none IPv6Templates TSS grouping Use all upper-case letters as specified in clause 7.1.2.1.1 none TP_RT_PS_TR Item group within a module Use lower-case initial letter none messageGroup SIP message type Use upper-case initial letter none Request, Response Note 4 SIP header type Use upper-case initial letter none MaxForwards Note 4 Basic common data types (e.g. bit string types of fixed length) Use upper-case initial letter none Take from common module Other Data types Use upper-case initial letter none SetupContents Message template Use lower-case initial letter m_ m_setupInit m_setupBasic Note 1 Message template with wildcard or matching expression Use lower-case initial letters mw_ mw_anyUserReply Note 2 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 3 Parameterization Use lower-case initial letter p_ p_macId Enumerated Value Use lower-case initial letter e_ e_syncOk NOTE 1: This prefix shall be used for all template definitions which do not assign or refer to templates with wildcards or matching expressions, e.g. templates specifying a constant value, parameterized templates without matching expressions, etc. NOTE 2: This prefix shall be used in identifiers for templates which either assign a wildcard or matching expression ( e.g. ?, *, value list, if present, pattern, etc.) or reference another template which assigns a wildcard or matching expression. NOTE 3: In this case it is acceptable to use underscore as a word delimiter. NOTE 4: This convention has been used in TS 102 027-3 [11] (SIP ATS). ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 22
|
71bf6f6e9881bfad98b13e0f92bf0dc7
|
102 790-3
|
5.3.2.3 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 [i.1] 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 102 790-3 V2.1.1 (2013-02) 23 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the interworking type of ATS defined in the present document, the PIXIT are divided in SIP-related PIXIT and ISUP/BICC-related PIXIT (there are no common PIXIT defined, but a set of integer values due to the possibility to select test case variants, if appropriate to the test case definition only). NOTE: The tables in this clause have been generated automatically from the TTCN-3 modules. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 24 A.2.1 SIP/IMS-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. Table A.1: SIP library related PIXIT items Index Identifier Type/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_SDP_encoding_unavail charstring for SDP media attribute encoding unavailable by the IUT 6 PX_SIP_SDP_encoding_unsup charstring for SDP media attribute encoding unsupported by the IUT 7 PX_SIP_SDP_transport charstring for SDP media T 8 PX_SIP_ISUP_LANGUAGE charstring for Used CPC language 9 PX_SIP_ISUP_CPC_VALUE charstring for Used CPC language 10 PX_SIP_100rel Boolean for True if 100rel mechanism is supported in SIP 11 PX_SIP_precondition Boolean for True if precondition mechanism is supported in SIP 12 PX_SIP_UDP Boolean for True if UDP Transport is used by the IUT to run campaign 13 PX_SIP_TRANSPORT charstring for Used Transport in upper case "UDP"/"TCP" 14 PX_SIP_SUT_PORT integer for SUT port number to exchange SIP messages 15 PX_SIP_SUT_IPADDR charstring for SUT IP address to exchange SIP messages 16 PX_SIP_SUT_HOME_DOMAIN charstring for SUT domain 17 PX_SIP_SUT_HOME_DOMAIN_UNKNOWN charstring for unknown SUT domain 18 PX_SIP_TS1_PORT integer for port number used by the TS1 to exchange SIP messages 19 PX_SIP_TS1_IPADDR charstring for IP address used by the TS1 to exchange SIP messages 20 PX_SIP_TS1_LOCAL_DOMAIN charstring for identity of the tester local domain 21 PX_SIP_TS1_LOCAL_USER charstring for identity of the tester local user 22 PX_SIP_TS1_LOCAL_USER_DIV charstring for identity of the user with active call diversion service 23 PX_SIP_TS1_LOCAL_USER_FULL charstring for identity of the tester local user (format "+"cc+ndc+sn) 24 PX_SIP_TS1_BEARER_PORT integer for port number used by the TS to exchange media streams 25 PX_SIP_TS1_BEARER_PORT2 charstring for port number used by the TS to exchange media streams 26 PX_SIP_TS1_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 27 PX_SIP_TS2_PORT integer for port number used by the TS2 to exchange SIP messages 28 PX_SIP_TS2_IPADDR charstring for IP address used by the TS2 to exchange SIP messages 29 PX_SIP_TS2_LOCAL_DOMAIN charstring for identity of the tester local domain 30 PX_SIP_TS2_LOCAL_USER charstring for identity of the tester local user 31 PX_SIP_TS2_LOCAL_USER_DIV charstring for identity of the user with active call diversion service 32 PX_SIP_TS2_LOCAL_USER_FULL charstring for identity of the tester local user (format "+"cc+ndc+sn) 33 PX_SIP_TS2_BEARER_PORT integer for port number used by the TS to exchange media streams 34 PX_SIP_TS2_BEARER_PORT2 integer for port number used by the TS to exchange media streams ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 25 Index Identifier Type/Description 35 PX_SIP_TS2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 36 PX_SIP_TS3_PORT integer for Port number used by the TS3 to exchange SIP messages 37 PX_SIP_TS3_IPADDR charstring for IP address used by the TS3 to exchange SIP messages 38 PX_SIP_TS3_LOCAL_DOMAIN charstring for identity of the tester local domain 39 PX_SIP_TS3_LOCAL_USER charstring for identity of the tester local user 40 PX_SIP_REGISTRATION Boolean for the SIP user if it have to register itself before executing a test case 41 PX_SIP_REGISTRATION_exp_min integer for the minimum SIP user registration expires- value 42 PX_SIP_SUT_REGISTRAR_DOMAIN charstring for REGISTRAR domain 43 PX_SIP_BYE_CAUSE integer for Release cause to be used in BYE and in Failure messages 44 PX_SIP_CheckConversation Boolean for True, if conversation check is implemented. 45 PX_SIP_CheckDTMF Boolean for True, if DTMF check is implemented. 46 PX_SIP_SendAnnouncement Boolean for True, if Announcement sending is implemented. 47 PX_SIP_CheckRinging Boolean for True, if ringing check is implemented. 48 PX_SIP_REGISTER_AUTHENTICATION_ENABLE D Boolean for option controlling if authentication is enabled/disabled for REGISTER messages 49 PX_SIP_INVITE_AUTHENTICATION_ENABLED Boolean for option controlling if authentication is enabled/disabled for INVITE messages 50 PX_SIP_SUT_UE1_QOP charstring for RFC 2617 [i.12], 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 51 PX_SIP_SUT_UE1_USERNAME charstring for RFC 2617 [i.12], clause 3.2.2 username: The name of user in the specified realm 52 PX_SIP_SUT_UE1_PASSWD charstring for RFC 2617 [i.12], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 53 PX_SIP_SUT_UE2_QOP charstring for RFC 2617 [i.12], 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 54 PX_SIP_SUT_UE2_USERNAME charstring for RFC 2617 [i.12], clause 3.2.2 username: The name of user in the specified realm 55 PX_SIP_SUT_UE2_PASSWD charstring for RFC 2617 [i.12], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 56 PX_SIP_T1 float for T1 RTT estimate (500 ms) 57 PX_T2 float for T2 Maximum retransmit interval for non-INVITE requests and INVITE response (4 000 ms) 58 PX_T4 float for T4 Maximum duration a message will remain in the network 59 PX_SIP_TF float for TDELAY default value for timeout on outgoing SIP request (i.e. 64*T1) 60 PX_SIP_TWAIT float for TWait default value for waiting an operator action 61 PX_SIP_TACK float for TAck default value for waiting an acknowledgement 62 PX_SIP_TRESP float for TResp default value for waiting for a response from the IUT 63 PX_SIP_TNOACT float for TNoAct default value for waiting no message from the IUT Value given for PX_TNOACT should be less than value of SHORT_REGISTRATION constant (which is currently "3" (seconds)) ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 26 Index Identifier Type/Description 64 PX_SIP_TSYNC float for TSYNC default value to synchronize ptc 65 PX_SIP_TGUARD float for TGUARD default value for an extra long timer to limit test execution 66 PX_TRespRetention float for TRespRetention minimum time that a Proxy will wait before sending a final response Table A.2: IMS library related PIXIT items Index Index/Identifier Type/Description 1 PX_IMS_SUT_UE_IPADDR charstring for SUT - UE IP address to exchange SIP messages - connection point for PCSCF 2 PX_IMS_SUT_UE_PORT integer for SUT - UE port number to exchange SIP messages - connection point for PCSCF 3 PX_IMS_SUT_PCSCF1_IPADDR charstring for SUT - PCSCF1 IP address to exchange SIP messages - connection point for UE1 4 PX_IMS_SUT_PCSCF1_PORT integer for SUT - PCSCF1 port number to exchange SIP messages - connection point for UE1 5 PX_IMS_SUT_PCSCF1_HOME_DOMAIN charstring for SUT/PCSCF1 domain - connection point for UE1 6 PX_IMS_SUT_UE1_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE1 7 PX_IMS_SUT_UE1_HOME_DOMAIN charstring for identity of the tester UE1 local domain 8 PX_IMS_SUT_UE1_PUBLIC_USER charstring for identity of the tester UE1 local user 9 PX_IMS_SUT_UE1_PRIVAT_USERNAME charstring for RFC 2617 [i.12], clause 3.2.2 username of UE1 The name of user in the specified realm 10 PX_IMS_SUT_UE1_PRIVAT_PASSWD charstring for RFC 2617 [i.12], clause 3.2.2.2 passwd of UE1: A known shared secret, the password of user of the specified username 11 PX_IMS_SUT_UE1_QOP charstring for RFC 2617 [i.12], 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 12 PX_IMS_SUT_UE1_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE1 13 PX_IMS_SUT_UE1_DISPLAY charstring for UE1 display name 14 PX_IMS_SUT_PCSCF2_IPADDR charstring for SUT - PCSCF2 IP address to exchange SIP messages - connection point for UE2 15 PX_IMS_SUT_PCSCF2_PORT integer for SUT - PCSCF2 port number to exchange SIP messages - connection point for UE2 16 PX_IMS_SUT_PCSCF2_HOME_DOMAIN charstring for SUT/PCSCF2 domain - connection point for UE2 17 PX_IMS_SUT_UE2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE2 18 PX_IMS_SUT_UE2_HOME_DOMAIN charstring for identity of the tester UE2 local domain 19 PX_IMS_SUT_UE2_PUBLIC_USER charstring for identity of the tester UE2 local user 20 PX_IMS_SUT_UE2_PRIVAT_USERNAME charstring for RFC 2617 [i.12], clause 3 21 PX_IMS_SUT_UE2_PRIVAT_PASSWD charstring for RFC 2617 [i.12], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username of UE2 22 PX_IMS_SUT_UE2_QOP charstring for RFC 2617 [i.12], clause 3.2.1 qop options 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 23 PX_IMS_SUT_UE2_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE2 ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 27 Index Index/Identifier Type/Description 24 PX_IMS_SUT_PCSCF3_IPADDR charstring for SUT - PCSCF3 IP address to exchange SIP messages - connection point for UE3 25 PX_IMS_SUT_PCSCF3_PORT integer for SUT - PCSCF3 port number to exchange SIP messages - connection point for UE3 26 PX_IMS_SUT_PCSCF3_HOME_DOMAIN charstring for SUT/PCSCF3 domain - connection point for UE3 27 PX_IMS_SUT_UE3_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE3 28 PX_IMS_SUT_UE3_HOME_DOMAIN charstring for identity of the tester UE2 local domain 29 PX_IMS_SUT_UE3_PUBLIC_USER charstring for identity of the tester UE3 local user 30 PX_IMS_SUT_UE3_PRIVAT_USERNAME charstring for RFC 2617 [i.12], clause 3 31 PX_IMS_SUT_UE3_PRIVAT_PASSWD charstring for RFC 2617 [i.12], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username of UE2 32 PX_IMS_SUT_UE3_QOP charstring for RFC 2617 [i.12], clause 3.2.1 qop options 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 33 PX_IMS_SUT_UE3_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE3 34 PX_IMS_SUT_PCSCF4_IPADDR charstring for SUT - PCSCF4 IP address to exchange SIP messages - connection point for UE4 35 PX_IMS_SUT_PCSCF4_PORT integer for SUT - PCSCF4 port number to exchange SIP messages - connection point for UE4 36 PX_IMS_SUT_PCSCF4_HOME_DOMAIN charstring for SUT/PCSCF4 domain - connection point for UE4 37 PX_IMS_SUT_UE4_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE4 38 PX_IMS_SUT_UE4_HOME_DOMAIN charstring for identity of the tester UE2 local domain 39 PX_IMS_SUT_UE4_PUBLIC_USER charstring for identity of the tester UE4 local user 40 PX_IMS_SUT_UE4_PRIVAT_USERNAME charstring for RFC 2617 [i.12], clause 3 41 PX_IMS_SUT_UE4_PRIVAT_PASSWD charstring for RFC 2617 [i.12], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username of UE2 42 PX_IMS_SUT_UE4_QOP charstring for RFC 2617 [i.12], clause 3.2.1 qop options 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 43 PX_IMS_SUT_UE4_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE4 44 PX_IMS_SUT_unknownUE_PUBLIC_USER 45 PX_IMS_SUT_EMERGENCY_HOME_DOMAIN charstring for identity of emergency service local domain 46 PX_IMS_SUT_EMERGENCY_SERVICE charstring for identity of the emergency service 47 PX_IMS_SUT_EMERGENCY_SERVICE_INVALID charstring for identity of the invalid emergency service 48 PX_IMS_SUT_IBCF1_IPADDR charstring for SUT/IBCF1 IP address to exchange SIP messages 49 PX_IMS_SUT_IBCF1_PORT integer for SUT/IBCF1 port number to exchange SIP messages 50 PX_IMS_SUT_IBCF1_HOME_DOMAIN charstring for SUT/IBCF1 domain 51 PX_IMS_SUT_IBCF2_IPADDR charstring for SUT/IBCF2 IP address to exchange SIP messages 52 PX_IMS_SUT_IBCF2_PORT integer for SUT/IBCF2 port number to exchange SIP messages 53 PX_IMS_SUT_IBCF2_HOME_DOMAIN charstring for SUT/IBCF2 domain 54 PX_IMS_SUT_PCSCF_IPADDR charstring for SUT/P-CSCF IP address to exchange SIP messages 55 PX_IMS_SUT_PCSCF_PORT integer for SUT/P-CSCF port number to exchange SIP messages 56 PX_IMS_SUT_PCSCF_HOME_DOMAIN charstring for SUT/P-CSCF domain ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 28 Index Index/Identifier Type/Description 57 PX_IMS_SUT_PCSCF_VisitedNetworkID charstring for SUT/P-CSCF P_VisitedNetwork ID header (see RFC 3455 [i.9]) 58 PX_IMS_SUT_PCSCF_MinSE charstring for SUT/P-CSCF Min-SE header lower bound for the session refresh interval (see RFC 4028 [i.11]) 59 PX_IMS_SUT_SCSCF_IPADDR charstring for SUT/S-CSCF IP address to exchange SIP messages 60 PX_IMS_SUT_SCSCF_PORT integer for SUT/S-CSCF port number to exchange SIP messages 61 PX_IMS_SUT_SCSCF_HOME_DOMAIN charstring for SUT/S-CSCFdomain 62 PX_IMS_SUT_SCSCF_REALM charstring for SUT/S-CSCF globally used realm name of IUT S-CSCF 63 PX_IMS_SUT_ICSCF_IPADDR charstring for SUT/I-CSCF IP address to exchange SIP messages 64 PX_IMS_SUT_ICSCF_PORT integer for SUT/I-CSCF port number to exchange SIP messages 65 PX_IMS_SUT_ICSCF_HOME_DOMAIN charstring for SUT/I-CSCFdomain 66 PX_IMS_SUT_AS_IPADDR charstring for SUT - AS IP address to exchange SIP messages - connection point for SCSCF 67 PX_IMS_SUT_AS_PORT integer for SUT - AS port number to exchange SIP messages - connection point for SCSCF 68 PX_IMS_SUT_AS_HOME_DOMAIN charstring for SUT/AS domain 69 PX_IMS_SUT_IMGCF_IPADDR charstring for SUT/I-MGCF IP address to exchange SIP messages 70 PX_IMS_SUT_IMGCF_PORT integer for SUT/I-MGCF port number to exchange SIP messages 71 PX_IMS_SUT_IMGCF_HOME_DOMAIN charstring for SUT/I-MGCF domain 72 PX_IMS_SUT_CONF_IPADDR charstring for SUT/conference IP address to exchange SIP messages 73 PX_IMS_SUT_CONF_PORT integer for SUT/conference port number to exchange SIP messages 74 PX_IMS_SUT_CONF_HOME_DOMAIN charstring for SUT/conference domain 75 PX_IMS_SUT_CONF_FACTORY_NAME charstring for conference factory URI name 76 PX_IMS_TS_UE1_IPADDR charstring for IP address used by the UE1 to exchange SIP messages 77 PX_IMS_TS_UE1_PORT integer for port number used by the UE1 to exchange SIP messages 78 PX_IMS_TS_UE1_REGISTRAR charstring for visited(TS) REGISTRAR domain 79 PX_IMS_TS_UE2_IPADDR charstring for IP address used by the UE2 to exchange SIP messages 80 PX_IMS_TS_UE2_PORT integer for port number used by the UE2 to exchange SIP messages 81 PX_IMS_TS_UE2_REGISTRAR charstring for visited(TS) REGISTRAR domain 82 PX_IMS_TS_UE3_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 83 PX_IMS_TS_UE3_PORT integer for port number used by the UE3 to exchange SIP messages 84 PX_IMS_TS_UE3_REGISTRAR charstring for visited(TS) REGISTRAR domain 85 PX_IMS_TS_UE4_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 86 PX_IMS_TS_UE4_PORT integer for port number used by the UE3 to exchange SIP messages 87 PX_IMS_TS_UE4_REGISTRAR charstring for visited(TS) REGISTRAR domain 88 PX_IMS_TS_IBCF_IPADDR charstring for TS/IBCF IP address to exchange SIP messages 89 PX_IMS_TS_IBCF_PORT integer for TS/IBCF port number to exchange SIP messages 90 PX_IMS_TS_IBCF_HOME_DOMAIN charstring for TS/IBCF domain 91 PX_IMS_TS_ICSCF_IPADDR charstring for TS/I-CSCF IP address to exchange SIP messages ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 29 Index Index/Identifier Type/Description 92 PX_IMS_TS_ICSCF_PORT integer for IUT/I-CSCF port number to exchange SIP messages 93 PX_IMS_TS_ICSCF_HOME_DOMAIN charstring for TS/I-CSCF domain 94 PX_IMS_TS_PCSCF_IPADDR charstring for TS/P-CSCF IP address to exchange SIP messages 95 PX_IMS_TS_PCSCF_PORT integer for IUT/P-CSCF port number to exchange SIP messages 96 PX_IMS_TS_PCSCF_HOME_DOMAIN charstring for TS/P-CSCFdomain 97 PX_IMS_TS_SCSCF_IPADDR charstring for TS/S-CSCF IP address to exchange SIP messages 98 PX_IMS_TS_SCSCF_PORT integer for TS/S-CSCF port number to exchange SIP messages 99 PX_IMS_TS_SCSCF_HOME_DOMAIN charstring for TS/S-CSCFdomain 100 PX_IMS_SUT_BARRED_PUBLIC_USER charstring public user identity for Request-URI to be rejected by IUT S-CSCF as it is barred for incoming calls 101 PX_IMS_SUT_INVALID_GRUU charstring invalid GRUU for Request-URI to be rejected by IUT S-CSCF 102 PX_IMS_SUT_UNSUBSCRIBED_SERVICE charstring Service value in P-Asserted-Service header to be rejected by IUT S-CSCF, as service is not subscribed- to 103 PX_IMS_SUT_UNSUBSCRIBED_SDP_SERVICE charstring Service value in SDP message body to be rejected by IUT S-CSCF, as service is not subscribed-to; intentionally kept as charstring to allow maximum flexibility to construct unsubscribed service 104 PX_IMS_TS_ECSCF_IPADDR charstring for TS/E-CSCF IP address to exchange SIP messages 105 PX_IMS_TS_ECSCF_PORT integer for TS/E-CSCF port number to exchange SIP messages 106 PX_IMS_TS_ECSCF_HOME_DOMAIN charstring for TS/E-CSCFdomain 107 PX_IMS_TS_IMS1UE_PUBLIC_USER charstring for public userinfo/displayname addressing IMS1UE (simulated by the TS) 108 PX_IMS_TS_IMS1UE_HOME_DOMAIN charstring for TS/domain 109 PX_IMS_TS_ISUP_PUBLIC_USER charstring for public userinfo addressing ISUPUE (simulated by the TS) 110 PX_IMS_TS_ISUP_HOME_DOMAIN charstring for ISUP TS/domain or IPAddress 111 PX_IMS_TS_AS1_IPADDR charstring for TS/AS1 IP address to exchange SIP messages 112 PX_IMS_TS_AS1_PORT integer for TS/AS1 port number to exchange SIP messages 113 PX_IMS_TS_AS1_HOME_DOMAIN charstring for TS/AS1 domain 114 PX_IMS_TS_AS2_IPADDR charstring for TS/AS2 IP address to exchange SIP messages 115 PX_IMS_TS_AS2_PORT integer for TS/AS2 port number to exchange SIP messages 116 PX_IMS_TS_AS2_HOME_DOMAIN charstring for TS/AS2 domain 117 PX_SCSCF_reject_unsubscribed_service Boolean (This is an operator option, not a protocol option), True, if SUT/S-CSCF rejects INVITE requests indicating services that are not subscribed to by the called subscriber, service may be requested in SDP or in a P-Asserted-Service header Ref: TS 124 229 [2], 5-4-3-3 ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 30 Table A.3: SIP related PIXIT items Index Identifier Type / Description 1 PX_IMSR10_SCSCF_reject_unsubscribed_service Boolean True, if SUT/S-CSCF rejects INVITE requests indicating services that are not subscribed to by the called subscriber, service may be requested in SDP or in a P-Asserted-Service header Ref: TS 124 229 [2], 5-4-3-3 2 PX_IMSR10_SecTls SecurityMechanism TLS 3 PX_IMSR10_SecAka SecurityMechanism AKA 4 PX_IMSR10_SecNass SecurityMechanism NASS 5 PX_IMSR10_Via Via ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 31 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 ts_10279003v020101p0.zip which accompanies the present document. ETSI ETSI TS 102 790-3 V2.1.1 (2013-02) 32 History Document history V1.1.1 March 2010 Publication V2.1.1 February 2013 Publication
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
1 Scope
|
The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5].
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 229 (V10.7.0): "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 version 10.7.0 Release 10)". [2] ISO/IEC 9646-1: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 1: General concepts". [3] Void [4] ISO/IEC 9646-7: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements". [5] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [6] ETSI ES 202 553: "Methods for Testing and Specification (MTS); TPLan: A notation for expressing Test Purposes". [7] ETSI TS 102 790-1: "IMS Network Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 1: Protocol Implementation Conformance Statement (PICS)". [8] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)".
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Void ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 7
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
3 Definitions and abbreviations
| |
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: abstract Selection Expression: Refer to ISO/IEC 9646-1 [2]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [2]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [2]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [2]. Lower Tester (LT): Refer to ISO/IEC 9646-1 [2]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [2].
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AS Application Server CSCF Call Session Control Function E-CSCF Emergency CSCF FQDN Fully Qualified Domain Name IBCF Interconnection Border Control Function I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IMS-AKA IMS-Authentication and Key Agreement IP Internet Protocol P-CSCF Proxy CSCF PICS Protocol Implementation Conformance Statement S-CSCF Serving CSCF SDP Session Description Protocol SIP Session Initiation Protocol SUT System Under Test TS Test System UE User Equipment
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
4 Test configurations
|
Test purposes of the present document address the IMS functional entities that are accessible via the following standardized SIP interfaces: Gm, Mw, Ic, and ISC. This clause introduces the test configurations that have been used for the definition of test purposes. Depending on the specific configuration the test system (TS) simulates the behaviour of one or more UEs or other IMS core networks communicating with the IMS core network under test. Test configurations try to cover various scenarios of IMS interworking and roaming conditions. Some test configurations show dashed boxes to visualise the implicit presence of a UE in the TS. These dashed boxes have only been introduced to improve understanding but do not have to be reflected in a test suite implementation. ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 8
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
4.1 Test configurations using Gm interface only
|
The Gm interface is located between a UE and the IMS core network. TS IMS UE Gm SUT Figure 1: Test configuration CF_1Gm TS IMS UE1 Gm1 SUT Gm2 UE2 Figure 2: Test configuration CF_2Gm
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
4.2 Test configurations using the Mw interface
|
The Mw interface is used in case of interworking or roaming between two different IMS core networks. This interface is used only if no border control functions like topology hiding are required. TS IMS IMS UE Mw Gm SUT Figure 3: Test configuration CF_1Mw TS TS IMS IMS UE2 Mw Gm UE1 Gm SUT Figure 4: Test configuration CF_1Mw1Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 9 TS TS IMS1 UE1 Mw1 Gm UE2 Mw2 IMS2 Gm IMS SUT Figure 5: Test configuration CF_2Mw
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
4.3 Test configurations using the Ic interface
|
The Ic interface is used in case of interworking or roaming between two different IMS core networks. This interface is used only if border control functions like topology hiding are required. TS IMS IMS UE Ic Gm SUT Figure 6: Test configuration CF_1Ic TS IMS IMS UE2 Ic Gm SUT TS UE1 Gm Figure 7: Test configuration CF_1Ic1Gm TS IMS IMS UE2 Ic1 Gm SUT Ic2 TS UE1 Gm Figure 8: Test configuration CF_2Ic1Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 10
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
4.4 Test configurations using the ISC interface
|
The ISC interface enables the IMS core network to communicate with a AS. TS IMS AS ISC SUT TS UE1 Gm Figure 9: Test configuration CF_1ISC1Gm TS IMS AS1 ISC SUT TS UE1 Gm1 UE2 Gm2 Figure 10: Test configuration CF_1ISC2Gm TS IMS AS1 ISC1 SUT TS UE1 ISC2 AS2 TS UE1 Gm1 UE2 Gm2 Figure 11: Test configuration CF_2ISC2Gm
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
5 Test Suite Structure (TSS)
| |
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
5.1 TP structure
|
Test Purposes have been written for IMS core network functionality that is accessible via SIP based interfaces, i.e. P-, I-, E-, S-CSCF and IBCF components, as defined by TS 124 229 [1]. All test purposes in this document assess mandatory functionality unless they have been marked with the keyword "OPTIONAL" at the beginning of the TP summary. The test purposes have been divided according to the interfaces into four major groups. Subgroups have been introduced to structure TPs further according to different procedures: 1) Test purposes for the Gm interface only: 1.1) General; 1.2) Registration procedures; 1.3) Initial dialogue request procedures; 1.4) Standalone requests procedures; 1.5) Subsequent requests on a dialogue procedures; ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 11 1.6) Target refresh request procedures; 1.7) Emergency procedures; 1.8) Exceptional procedures; 1.9) SDP procedures; 1.10) NAT traversal procedures. 2) Test purposes for the Mw interface: 2.1) General; 2.2) Registration procedures; 2.3) Initial dialogue request procedures; 2.4) Standalone requests procedures; 2.5) Subsequent requests on a dialogue procedures; 2.6) Target refresh request procedures; 2.7) Emergency procedures; 2.8) SDP procedures. 3) Test purposes for the Ic interface: 3.1) General; 3.2) Registration procedures; 3.3) Initial dialogue request procedures; 3.4) Standalone requests procedures; 3.5) Subsequent requests on a dialogue procedures; 3.6) Target refresh request procedures. 4) Test purposes for the ISC interface: 4.1) Registration procedures; 4.2) Initial dialogue request procedures; 4.3) Standalone requests procedures; 4.4) Subsequent requests on a dialogue procedures; 4.5) Target refresh request procedures.
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
5.2 TP naming convention
|
TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 12 Table 1: TP identifier naming convention scheme Identifier: TP_<ts>_<int><subgroup>_<nn> <ts> = Test suite name: i.e. "IMS_T2" <int> = type of Interface: "MW" Mw interface "GM" Gm Interface "IC" Ic interface "ISC" ISC interface <subgroup> = subgroup 3 first letter of the subgroup according to TSS subdivision "GEN" General "REG" Registration procedures "INI" Initial request procedures "STA" Standalone request procedures "SUB" Subsequent request on a dialogue procedures "TAR" Target refresh request procedures "EME" Emergency procedures "SDP" SDP procedures "EXC" Exceptional procedures "NAT" NAT traversal procedures <nn> = sequential number (01-99) EXAMPLE 1: TP_IMS_T2_GM_GEN_01 stands for 1st test case in the Gm interface only group, and in the general subgroup. All PICS items referred to in this clause are as specified in TS 102 790-1 [7] unless indicated otherwise by another numbered reference. For each PICS item there exists a unique reference defined as the table identifier, followed by a solidus character "/", followed by the item number in the table within TS 102 790-1 [7]. EXAMPLE 2: A.5/4 is the reference to the answer of item 4 in table A.5 of TS 102 790-1 [7].
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
5.3 The tabular symbolic TPLan presentation format
|
Each table contains header fields and a description part. The header fields identify the TP, list the related clause reference the base specification that the TP was derived from, introduce the TP with a short summary, references the related test configuration and test case in the ATS. Identifiers starting with the string "RQ_003_" indicate requirements within the internal requirement catalogue. The description part presents the TP using two sections: (a) initial conditions that have to be fulfilled for the test purpose body to be valid and (b) the test purpose body which is illustrated with one or more stimulus/response pairs. Both sections are further substructured with columns for affected entities from the test configurations, i.e. IUT, UE, UE2, IMS (test system component), and AS. The condition section lists one or more conditions that have to be fulfilled in order for the test purpose body to apply. Each condition has a description and either "✓" or " " marks to indicate all the entities affected by this condition. "✓" marks indicates a positive condition, e.g. "A is registered in B", whereas " "marks indicate a negative condition, e.g. "B not configured for feature Z". If there is no mark in a column then the condition does not apply for that entity, e.g. entity A is not involved in the condition "B not configured for feature Z". It is assumed that all listed conditions have to be fulfilled in the order listed, i.e. the list reflects an "and" relation. ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 13 Table 2 shows an example condition section illustrating all of the above examples. Table 2: Example TP condition section Entities Condition A B ✓ ✓ A registered in B B configured for feature Z The test purpose body section contains one or more steps identified with a number in the first column. Steps belonging to IUT stimuli are shown with a green background whereas steps related to IUT responses are shown with a beige background. All listed steps are assumed to be carried out in increasing step number, i.e. they reflect an "and" relation. "or" relations at the level of entire messages are shown with lowercase letters following the step number identifying the different alternatives, e.g. "2a" versus "2b". Each step indicates the exchange of a message from a source entity (identified by the direction symbols " " or ""), e.g. entity A sends the message, to a destination entity (identified by the direction symbols "" or ""), e.g. entity B receives the message. The use of the "||" symbol in combination with the direction symbols, e.g. "||", indicates that a particular message shall either not be sent or received by an entity, e.g. entity B did not send the message. Additional information about valid as well as invalid message content is presented in the "Message" column. First general information about message, e.g. its type, destination, attributes, etc., are shown in bold font. Below this information message headers or parameter content that shall be present in that message are listed using "" symbols whereas headers or parameter content that shall not be present are listed using the "" symbols. The " " symbol indicates a valid message parameter value where as the " ||"symbol indicates an invalid message parameter value. Any content, e.g. header or parameter, which is not explicitly mentioned in a message description of a TP is not restricted by that TP. Finally, the interface identifier to which a message exchange pertains may be shown in the column labelled "IF". Table 3 shows an example test purpose body section illustrating all of the above examples. Table 3: Example TP body section A B Step Direction Message IF 1 some request this header this one parameter this value this other parameter || that value that parameter that header Xx 2a failure response Xx 2b || || no message Xx ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 14
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6 Test Purposes (TP)
|
The test purposes have been written in the notation TPLan as defined in ES 202 553 [6]. TPLan has been developed by ETSI to express test purposes in a more formal manner. All TPLan TPs have been converted into a symbolic tabular presentation format which is shown in this clause. TPs in the standardized textual TPLan syntax are collected in ts_10279002v020101p0.zip (see annex A). The two presentation formats, i.e. textual and symbolic tabular, contain the same information and shall therefore be considered equivalent. In the case that there appears to be syntactical or semantic differences between the two then the files in the electronic annex take precedence over the following tables.
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1 Test purposes for the Gm interface only
| |
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.1 General
|
Test Purpose Identifier: TP_IMST2_GM_GEN_01 Summary: All IMS CN components shall support SIP messages which are greater than 1 300 bytes in length Clause: 4.2A, paragraph 1 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS as security association UE1 IUT UE2 Step Direction Message IF 1 MESSAGE for UE2 Message Body greater than 1 300 bytes 2 MESSAGE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 15
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.2 Registration procedures
|
Test Purpose Identifier: TP_IMST2_GM_REG_01 Summary: When a P-CSCF receives a REGISTER request from the UE and the REGISTER request was received without protection, and the Security-Client header is not present, then the P-CSCF shall return a suitable SIP 4xx response Clause: 5.2.2.2 first numbered list 2 a References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 unprotected REGISTER Security-Client header 2 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 16 Test Purpose Identifier: TP_IMST2_GM_REG_02 Summary: When a P-CSCF receives a protected REGISTER request from the UE and the Security-Verify header is not present, then the P-CSCF shall return a suitable SIP 4xx response. Clause: 5.2.2.2 first numbered list 3)a References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 protected REGISTER Security-Verify header 2 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 17 Test Purpose Identifier: TP_IMST2_GM_REG_03 Summary: When a P-CSCF receives a protected REGISTER request from the UE and the Security-Client header is not present, then the P-CSCF shall return a suitable SIP 4xx response. Clause: 5.2.2.2 first numbered list 3)a References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 protected REGISTER Security-Client header 2 4xx response Gm Test Purpose Identifier: TP_IMST2_GM_REG_04 Summary: When a P-CSCF receives an unprotected REGISTER request from the UE and the Security-Client header is not present, then the P-CSCF shall return a suitable SIP 4xx response. Clause: 5.2.2.2 first numbered list 3)b References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 unprotected REGISTER Security-Client header 2 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 18 Test Purpose Identifier: TP_IMST2_GM_REG_05 Summary: When a P-CSCF receives a protected REGISTER request from a non-registered UE and the private user identity conveyed in the Authorization header of the request are different from the ones previously challenged or authenticated, the P-CSCF shall reject the REGISTER request by returning a SIP 403 (Forbidden) response. Clause: 5.2.2.2 first numbered list 3)c References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 protected REGISTER Authorization header invalid private user identity 2 403 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 19 Test Purpose Identifier: TP_IMST2_GM_REG_06 Summary: When a P-CSCF receives a protected REGISTER request from a registered UE and the private user identity conveyed in the Authorization header of the request are different from the ones previously challenged or authenticated, the P-CSCF shall reject the REGISTER request by returning a SIP 403 (Forbidden) response. Clause: 5.2.2.2 first numbered list 3)c References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT ✓ ✓ UE1 registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 protected REGISTER Authorization header invalid private user identity 2 403 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 20 Test Purpose Identifier: TP_IMST2_GM_REG_07 Summary: When a P-CSCF receives a unprotected REGISTER request from a non-registered UE it accepts it and returns a SIP 401 response. Clause: 5.2.2.2 second numbered list References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 unprotected REGISTER 2 401 response Security-Server header static signalling plane WWW-Authenticate header CK parameter IK parameter Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 21 Test Purpose Identifier: TP_IMST2_GM_REG_08 Summary: When a P-CSCF receives a SIP 200 (OK) response to a REGISTER request and the value of the Expires header field and/or the Expires parameter in the Contact header in the 200 (OK) response is not set to zero it passes the 200 (OK) to the UE. Clause: 5.2.2.2 third numbered list References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 protected REGISTER 2 200 response Gm Test Purpose Identifier: TP_IMST2_GM_REG_09 Summary: If local policy requires the application of IBCF capabilities in the visited network and a P-CSCF fails to forward a REGISTER request from a UE to any IBCF, it shall return a SIP 504 (Server Time-out) response to the UE. Clause: 5.2.2.1 second numbered list 5) References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT IMS ✓ ✓ UE1 is visiting IUT ✓ IUT configured for establishing digest without TLS security association ✓ IUT configured for topology hiding IUT not configured with an entry point to IMS UE1 IUT IMS Step Direction Message IF 1 REGISTER 2 504 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 22 Test Purpose Identifier: TP_IMST2_GM_REG_11 Summary: When a P-CSCF receives a REGISTER request from a registered UE and the value of the Expires header field and/or the Expires parameter in the Contact header is set to zero it sends a 200 (OK) to the UE. Clause: 5.2.5.1 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT ✓ ✓ UE1 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT Step Direction Message IF 1 REGISTER Expires header 0 2 200 response Expires header 0 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 23
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.3 Initial request procedures
|
Test Purpose Identifier: TP_IMST2_GM_INI_01 Summary: When a P-CSCF receives an initial request for a dialogue from a UE then it forwards the request to destination UE and returns a SIP 100 (Trying) response to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.3 item 1,4,5; 5.2.6.4.3 item 5,7; 5.2.7.2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT UE2 Step Direction Message IF 1 INVITE for UE2 2 100 response 3 INVITE Route header SIP URI of IMS P-CSCF Record-Route header address of IUT P-CSCF or FQDN address of IUT P-CSCF Via header address of IUT P-CSCF or FQDN address of IUT P-CSCF P-Charging-Vector header P-Charging-Function-Addresses header P-Preferred-Identity header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 24 Test Purpose Identifier: TP_IMST2_GM_INI_02 Summary: When a P-CSCF receives an initial request for a dialogue from a UE with the preloaded Route not matching the stored Service-Route header then it either returns a SIP 400 response to the UE or forwards the request to destination UE with an updated Route header and returns a SIP 100 (Trying) response to the originating UE. Clause: 5.2.6.3.3 item 2; 5.2.7.2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.4.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT UE2 Step Direction Message IF 1 INVITE for UE2 Route header not matching stored Service-Route header 2a 400 response 3b || || no message 2b 100 response 3b INVITE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 25 Test Purpose Identifier: TP_IMST2_GM_INI_03 Summary: When a P-CSCF receives any valid SIP 1xx response as a result of a forwarded request for an initial dialogue it forwards the response to originating UE. Clause: 5.2.6.3.4; 5.2.6.4.4 first numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 180 response for UE1 2 180 response Gm Test Purpose Identifier: TP_IMST2_GM_INI_03A Summary: When a P-CSCF receives any valid SIP 1xx response as a result of a forwarded request for an initial dialogue it forwards the response to originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.4; 5.2.6.4.4 first numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 180 response for UE1 P-Preferred-Identity header 2 180 response P-Charging-Vector header P-Charging-Function-Addresses header P-Preferred-Identity header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 26 Test Purpose Identifier: TP_IMST2_GM_INI_04 Summary: When a P-CSCF receives any valid SIP 2xx response as a result of a forwarded request for an initial dialogue, it forwards the response to the originating UE. Clause: 5.2.6.3.4; 5.2.6.4.4 first numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 2 200 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 27 Test Purpose Identifier: TP_IMST2_GM_INI_04A Summary: When a P-CSCF receives any valid SIP 2xx response as a result of a forwarded request for an initial dialogue, it forwards the response to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.4; 5.2.6.4.4 first numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 P-Preferred-Identity header 2 200 response P-Charging-Vector header P-Charging-Function-Addresses header P-Preferred-Identity header Gm Test Purpose Identifier: TP_IMST2_GM_INI_05 Summary: When a P-CSCF receives any other response other than a SIP 1xx or a 2xx to an initial request to a UE for a dialogue it forwards it to the originating UE. Clause: 5.2.6.4.4 second numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE1 2 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 28 Test Purpose Identifier: TP_IMST2_GM_INI_06 Summary: When a P-CSCF receives any other response other than a SIP 1xx or a 2xx to an initial request to a UE for a dialogue and if the list of Via headers does not match the saved list of Via headers received in the request corresponding to the same dialog, it either sends no message or forwards it to the originating UE. Clause: 5.2.6.4.4 second numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.4.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE1 Via header not matching stored Via header 2a || || no message 2b 4xx response Via header stored Via header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 29 Test Purpose Identifier: TP_IMST2_GM_INI_07 Summary: If a P-CSCF requires periodic refreshment of a session established after receiving a SIP INVITE request from a UE and the Session-Expires header indicates a too low refresh frequency, it shall reject the INVITE. Clause: 5.2.7.2, RFC 4028 [8] References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/26.1.1 Entities Condition UE1 IUT ✓ ✓ UE1 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT Step Direction Message IF 1 INVITE Supported header timer option tag Session-Expires header || acceptable expiration 2 422 response Min-SE header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 30 Test Purpose Identifier: TP_IMST2_GM_INI_08 Summary: When a P-CSCF requires periodic refreshment of a session established after receiving a SIP INVITE request from a UE and the Session-Expires header of the INVITE request indicates acceptable refresh frequency then it forwards the request to the destination UE and returns a 100 (Trying) to the originating UE. Clause: 5.2.7.2, 5.2.8.3, RFC 4028 [8] References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/26.1.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT UE2 Step Direction Message IF 1 INVITE Supported header timer option tag Session-Expires header acceptable expiration 2 100 response 3 INVITE Session-Expires header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 31
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.4 Standalone requests procedures
|
Test Purpose Identifier: TP_IMST2_GM_STA_01 Summary: When a P-CSCF receives a request for a standalone transaction from a UE with preloaded Route not matching the stored Service-Route header then it either returns a SIP 400 response to the UE or forwards the request to destination UE with an updated Route header and returns a SIP 100 (Trying) response to the originating UE. Clause: 5.2.6.3.7 item 2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.8.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT UE2 Step Direction Message IF 1 MESSAGE for UE2 Route header not matching stored Service-Route header 2a 400 response 3a || || no message Gm 2b 100 response 3b MESSAGE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 32 Test Purpose Identifier: TP_IMST2_GM_STA_02 Summary: When a P-CSCF receives a request for a standalone transaction from a UE with preloaded Route matching the stored Service-Route header then it forwards the request to destination UE and returns a SIP 100 (Trying) response to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.7 item 1,4; 5.2.6.4.7 item 3 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT UE2 Step Direction Message IF 1 MESSAGE for UE2 2 100 response 3 MESSAGE Route header SIP URI of IMS P-CSCF Via header address of IUT P-CSCF or FQDN address of IUT P-CSCF P-Charging-Vector header P-Charging-Function-Addresses header P-Preferred-Identity header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 33 Test Purpose Identifier: TP_IMST2_GM_STA_03 Summary: When a P-CSCF receives a SIP 200 response to a forwarded request for a standalone transaction then it forwards the request to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.8, 5.2.6.4.8 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has sent MESSAGE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 2 200 response P-Charging-Vector header P-Charging-Function-Addresses header P-Preferred-Identity header Gm Test Purpose Identifier: TP_IMST2_GM_STA_04 Summary: When a P-CSCF receives any 4xx response to a forwarded request for a standalone transaction then it forwards the request to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.8, 5.2.6.4.8 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has sent MESSAGE to UE2 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE1 2 4xx response P-Charging-Vector header P-Charging-Function-Addresses header P-Preferred-Identity header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 34 Test Purpose Identifier: TP_IMST2_GM_STA_05 Summary: When a P-CSCF receives any response for a standalone request to a UE for a dialogue and if the list of Via headers does not match the saved list of Via headers received in the request corresponding to the same dialog, it either sends no message or forwards it to the originating UE. Clause: 5.2.6.4.8 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.10.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has sent MESSAGE to UE2 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE1 Via header not matching stored Via header 2a || || no message 2b 4xx response Via header stored Via header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 35
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.5 Subsequent request procedures
|
Test Purpose Identifier: TP_IMST2_GM_SUB_01 Summary: When the P-CSCF receives a subsequent request for non-existing dialogue it rejects it with a SIP 403 response and does not forward it any further. Clause: 5.2.6.3.9 item 1a References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association IUT has not established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 BYE for UE2 2 403 response 3 || || no message Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 36 Test Purpose Identifier: TP_IMST2_GM_SUB_02 Summary: When the P-CSCF receives a subsequent request with unknown URI in Route header it either rejects it with a SIP 400 response or forwards it with an updated Route header. Clause: 5.2.6.3.9 item 2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.8.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 BYE for UE2 Route header not matching stored Record-Route header 2a 400 response 3b || || no message 2b BYE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 37 Test Purpose Identifier: TP_IMST2_GM_SUB_03 Summary: When the P-CSCF receives a subsequent request with unknown URI in Route header from the terminating UE it either rejects it with a SIP 400 response or forwards it with an updated Route header. Clause: 5.2.6.3.9 item 2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.8.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 BYE for UE1 Route header not matching stored Record-Route header 2a 400 response 3a || || no message 2b BYE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 38 Test Purpose Identifier: TP_IMST2_GM_SUB_04 Summary: When the P-CSCF receives a subsequent request for existing dialogue from the originating UE it forwards it to the destination UE without a P-Charging-Vector header. Clause: 5.2.1 before first numbered list; 5.2.6.3.9; 5.2.6.4.9 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 BYE for UE2 2 BYE P-Charging-Vector header P-Charging-Function-Addresses header Gm Test Purpose Identifier: TP_IMST2_GM_SUB_05 Summary: When the P-CSCF receives a subsequent request for existing dialogue from the terminating UE it forwards it to the destination UE without a P-Charging-Vector header. Clause: 5.2.1 before first numbered list; 5.2.6.3.9; 5.2.6.4.9 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 BYE for UE1 2 BYE P-Charging-Vector header P-Charging-Function-Addresses header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 39 Test Purpose Identifier: TP_IMST2_GM_SUB_06 Summary: When the P-CSCF receives a SIP 200 to subsequent request from the originating UE it forwards it to the terminating UE. Clause: 5.2.6.4.10 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received BYE from UE1 for UE2 ✓ ✓ IUT has sent BYE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 2 200 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 40 Test Purpose Identifier: TP_IMST2_GM_SUB_06A Summary: When the P-CSCF receives a SIP 200 to subsequent request from the originating UE it forwards it to the terminating UE. Clause: 5.2.1 before first numbered list; 5.2.6.4.10 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received BYE from UE1 for UE2 ✓ ✓ IUT has sent BYE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 2 200 response P-Charging-Vector header P-Charging-Function-Addresses header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 41 Test Purpose Identifier: TP_IMST2_GM_SUB_07 Summary: When the P-CSCF receives a SIP 200 to subsequent request from the terminating UE it forwards it to the originating UE. Clause: 5.2.6.4.10 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received BYE from UE2 for UE1 ✓ ✓ IUT has sent BYE to UE1 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE2 2 200 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 42 Test Purpose Identifier: TP_IMST2_GM_SUB_07A Summary: When the P-CSCF receives a SIP 200 to subsequent request from the terminating UE it forwards it to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.4.10 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received BYE from UE2 for UE1 ✓ ✓ IUT has sent BYE to UE1 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE2 2 200 response P-Charging-Vector header P-Charging-Function-Addresses header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 43 Test Purpose Identifier: TP_IMST2_GM_SUB_08 Summary: When the P-CSCF receives a SIP 200 with unknown Via header to a subsequent request from the terminating UE it either does not forward it or updates the Via heading prior to forwarding it. Clause: 5.2.6.4.10 item 1 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.12.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received BYE from UE1 for UE2 ✓ ✓ IUT has sent BYE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 Via header not matching stored Via header 2a || || no message 2b 200 response Via header stored Via header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 44 Test Purpose Identifier: TP_IMST2_GM_SUB_09 Summary: When the P-CSCF receives a SIP 200 with unknown Via header to a subsequent request from the originating UE it either does not forward it or updates the Via heading prior to forwarding it. Clause: 5.2.6.4.10 item 1 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.12.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received BYE from UE2 for UE1 ✓ ✓ IUT has sent BYE to UE1 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE2 Via header not matching stored Via header 2a || || no message 2b 200 response Via header stored Via header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 45 Test Purpose Identifier: TP_IMST2_GM_SUB_10 Summary: Upon receipt of a request on a dialogue for which the P-CSCF has already initiated session release, the P-CSCF shall return 481 (Call/Transaction Does Not Exist) response. Clause: 5.2.8.1.3 paragraph 1 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ IUT has received BYE from UE2 ✓ ✓ IUT has sent BYE to UE1 UE1 IUT UE2 Step Direction Message IF 1 BYE for UE2 2 481 3 200 G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 46
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.6 Target refresh request procedures
|
Test Purpose Identifier: TP_IMST2_GM_TAR_01 Summary: When the P-CSCF receives a refresh request for non-existing dialogue it shall reject it with a SIP 403 response. Clause: 5.2.6.3.5 item 1a References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association IUT has not established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 target refresh UPDATE for UE2 2 403 response 3 || || no message G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 47 Test Purpose Identifier: TP_IMST2_GM_TAR_02 Summary: When the P-CSCF receives a refresh request with unknown URI in Route header it shall either reject it or forward it with an updated Route header. Clause: 5.2.6.3.5 item 2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.6.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 target refresh INVITE for UE2 Route header not matching stored Record-Route header 2a 400 response 3a || || no message 2b 100 response 3b INVITE G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 48 Test Purpose Identifier: TP_IMST2_GM_TAR_03 Summary: When the P-CSCF receives a refresh request for existing dialogue from originating UE it shall return a SIP 100 and forward the request. Clause: 5.2.1 before first numbered list; 5.2.6.3.5 items 1A,3; 5.2.6.4.5 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 target refresh INVITE for UE2 2 100 response 3 target refresh INVITE Route header SIP URI of IMS P-CSCF Via header address of IUT P-CSCF or FQDN address of IUT P-CSCF P-Charging-Vector header P-Charging-Function-Addresses header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 49 Test Purpose Identifier: TP_IMST2_GM_TAR_04 Summary: When the P-CSCF receives a refresh request for existing dialogue from terminating UE it shall return a SIP 100 and forward the request. Clause: 5.2.1 before first numbered list; 5.2.6.3.5 items 1A,3; 5.2.6.4.5 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IUT UE2 Step Direction Message IF 1 target refresh INVITE for UE1 2 100 response 3 target refresh INVITE Route header SIP URI of IMS P-CSCF Via header address of IUT P-CSCF or FQDN address of IUT P-CSCF P-Charging-Vector header P-Charging-Function-Addresses header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 50 Test Purpose Identifier: TP_IMST2_GM_TAR_05 Summary: When the P-CSCF receives a valid 180 response to refresh request from terminating UE it forwards the response to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.6; 5.2.6.4.6 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE1 for UE2 ✓ ✓ IUT has sent target refresh INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 180 response for UE1 2 180 response P-Charging-Vector header P-Charging-Function-Addresses header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 51 Test Purpose Identifier: TP_IMST2_GM_TAR_06 Summary: When the P-CSCF receives a valid 180 response to refresh request from originating UE it forwards the response to the terminating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.6; 5.2.6.4.6 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE2 for UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IUT UE2 Step Direction Message IF 1 180 response for UE2 2 180 response P-Charging-Vector header P-Charging-Function-Addresses header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 52 Test Purpose Identifier: TP_IMST2_GM_TAR_07 Summary: When the P-CSCF receives a valid 200 response to refresh request from terminating UE, it returns a SIP ACK and forwards the response to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.6; 5.2.6.4.6 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE1 for UE2 ✓ ✓ IUT has sent target refresh INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 2 ACK 3 200 response P-Charging-Vector header P-Charging-Function-Addresses header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 53 Test Purpose Identifier: TP_IMST2_GM_TAR_08 Summary: When the P-CSCF receives a valid SIP 200 response to refresh request from originating UE, it returns a SIP ACK and forwards the response to the terminating UE. Clause: 5.2.1 before first numbered list; 5.2.6.3.6; 5.2.6.4.6 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE2 for UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE2 2 ACK 3 200 response P-Charging-Vector header P-Charging-Function-Addresses header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 54 Test Purpose Identifier: TP_IMST2_GM_TAR_09 Summary: When the P-CSCF receives a valid 4xx response to refresh request from terminating UE it forwards the response to the originating UE. Clause: 5.2.1 before first numbered list; 5.2.6.4.6 second numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE1 for UE2 ✓ ✓ IUT has sent target refresh INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE1 2 4xx response P-Charging-Vector header P-Charging-Function-Addresses header G m ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 55 Test Purpose Identifier: TP_IMST2_GM_TAR_10 Summary: When the P-CSCF receives a valid SIP 4xx response to refresh request from originating UE it forwards the response to the terminating UE. Clause: 5.2.1 before first numbered list; 5.2.6.4.6 second numbered list References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE2 for UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE2 2 4xx response P-Charging-Vector header P-Charging-Function-Addresses header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 56 Test Purpose Identifier: TP_IMST2_GM_TAR_11 Summary: When the P-CSCF receives a 4xx with unknown Via header to refresh request from the terminating UE it either does not forward the message or forwards it with an updated Via header. Clause: 5.2.6.4.6 second numbered list item 1 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.8.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE1 for UE2 ✓ ✓ IUT has sent target refresh INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE1 Via header not matching stored Via header 2a || || no message 2b 4xx response Via header stored Via header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 57 Test Purpose Identifier: TP_IMST2_GM_TAR_12 Summary: When the P-CSCF receives a 4xx with unknown Via header to refresh request from the originating UE it either does not forward the message or forwards it with an updated Via header. Clause: 5.2.6.4.6 second numbered list item 1 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.8.1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE2 for UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IUT UE2 Step Direction Message IF 1 4xx response for UE2 Via header not matching stored Via header 2a || || no message 2b 4xx response Via header stored Via header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 58
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.7 Emergency procedures
|
Test Purpose Identifier: TP_IMST2_GM_EME_01 Summary: P-CSCF rejects INVITE to emergency service with 380 when emergency calls have to use the CS domain. Clause: 5.2.10.5 I); 7.6.4.1 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT IUT not configured for emergency sessions UE1 IUT Step Direction Message IF 1 INVITE Request URI emergency service identifier 2 380 response Content-Type header application/3gpp-ims+xml P-Asserted-Identity header SIP URI of IMS P-CSCF Gm Test Purpose Identifier: TP_IMST2_GM_EME_02 Summary: P-CSCF accepts INVITE to emergency service from unregistered user and returns SIP 100 (Trying) response. Clause: 5.2.10.2 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for emergency sessions UE1 IUT Step Direction Message IF 1 INVITE Request URI emergency service identifier 2 100 response Gm 3 || || 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 59 Test Purpose Identifier: TP_IMST2_GM_EME_03 Summary: P-CSCF rejects INVITE to non-emergency service from user with emergency registration with SIP 403 response. Clause: 5.2.10.3 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT ✓ ✓ UE1 emergency registered in IUT UE1 IUT Step Direction Message IF 1 INVITE Request URI || emergency service identifier 2 403 response Gm Test Purpose Identifier: TP_IMST2_GM_EME_04 Summary: P-CSCF accepts INVITE to emergency service from user with emergency registration and returns SIP 100 response. Clause: 5.2.10.3 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT ✓ ✓ UE1 emergency registered in IUT UE1 IUT Step Direction Message IF 1 INVITE Request URI emergency service identifier 2 100 response Gm 3 || || 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 60 Test Purpose Identifier: TP_IMST2_GM_EME_05 Summary: P-CSCF accepts INVITE to emergency service from user with normal registration and returns SIP 100 response. Clause: 5.2.10.4 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT ✓ ✓ UE1 registered in IUT UE1 IUT Step Direction Message IF 1 INVITE Request URI emergency service identifier 2 100 response Gm 3 || || 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 61
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.8 Exceptional procedures
|
Test Purpose Identifier: TP_IMST2_GM_EXC_01 Summary: P-CSCF initiates call release due to unacceptable SDP offer in SIP 200 response. Clause: 5.2.8.1.2 item 3 and 4, 6.2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 unacceptable SDP offer 2 200 response 3 ACK SDP answer 4 BYE Reason header 503 response code or 488 response code 5 ACK Gm 6 BYE Reason header 488 response code Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 62 Test Purpose Identifier: TP_IMST2_GM_EXE_01A Summary: When the P-CSCF receives a not valid SIP 200 response to refresh request from originating UE, P- CSCF initiates call release due to unacceptable SDP offer in SIP 200 response. Clause: 5.2.8.1.2 item 1 and 2, 6.2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ ✓ IUT has received target refresh INVITE from UE2 for UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 unacceptable SDP offer 2 200 response Gm 3 ACK SDP answer 4 BYE Reason header 503 response code or 488 response code Gm 5 ACK 6 BYE Reason header 488 response code ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 63 Test Purpose Identifier: TP_IMST2_GM_EXC_02 Summary: OPTIONAL: P-CSCF initiates call release due to encrypted SDP offer in SIP 200 response. Clause: 5.2.8.1.2 item 3 and 4, 6.2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 ✓ IUT configured to reject encrypted SDP offers UE1 IUT UE2 Step Direction Message IF 1 200 response for UE1 encrypted SDP offer 2 200 response 3 ACK SDP answer 4 BYE Reason header 503 response code or 488 response code 5 ACK Gm 6 BYE Reason header 488 response code Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 64
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.9 SDP procedures
|
Test Purpose Identifier: TP_IMST2_GM_SDP_01 Summary: P-CSCF rejects INVITE with SDP offer with unacceptable media parameter with SIP 488 response. Clause: 6.2 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT ✓ ✓ UE1 registered in IUT ✓ IUT configured for establishing digest without TLS security association UE1 IUT Step Direction Message IF 1 INVITE SDP offer unacceptable media parameter 2 488 response SDP offer Gm Test Purpose Identifier: TP_IMST2_GM_SDP_02 Summary: OPTIONAL: P-CSCF rejects INVITE with encrypted SDP offer. Clause: 6.2 References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/30.1.1 Entities Condition UE1 IUT ✓ ✓ UE1 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ IUT configured to reject encrypted SDP offers UE1 IUT Step Direction Message IF 1 INVITE encrypted SDP offer 2 4xx response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 65 Test Purpose Identifier: TP_IMST2_GM_SDP_03 Summary: P-CSCF forwards SIP response with unacceptable SDP media parameter offer in SIP 180 response to originating UE. Clause: 6.2 References: - Config Ref: CF_2Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE2 ✓ ✓ UE1 registered in IUT ✓ IUT configured for establishing digest without TLS security association ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 UE1 IUT UE2 Step Direction Message IF 1 180 response for UE2 SDP offer unacceptable media parameter 2 180 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 66
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.1.10 NAT traversal procedures
|
Test Purpose Identifier: TP_IMST2_GM_NAT_01 Summary: P-CSCF does not respond to unprotected REGISTER from UE if Security-Client header that does not specify UDP tunneling support. Clause: Annex K.2.2.2.2 first numbered list item 2a References: - Config Ref: CF_1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IUT UE1 not registered in IUT ✓ IUT configured for establishing IMS AKA security association ✓ UE1 has initiated IMS AKA security association establishment UE1 IUT Step Direction Message IF 1 unprotected REGISTER Security-Client header || UDP-enc-tun support topmost Via header IP address different from IP source address 2 || || no message Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 67
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2 Test purposes for the Mw interface
| |
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.1 General
|
Test Purpose Identifier: TP_IMST2_MW_GEN_01 Summary: All IMS CN components shall support SIP messages which are greater than 1 300 bytes in length on Mw interface. Clause: 4.2A, paragraph 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 Message Body greater than 1 300 bytes Gm 2 MESSAGE to UE2 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 68 Test Purpose Identifier: TP_IMST2_MW_GEN_02 Summary: A functional entity at the boundary of a trust domain shall remove the P-Access-Network-Info header from any SIP message sent out of the trust domain. Clause: 4.4.3, paragraph 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IUT not configured for topology hiding IMS not configured for being in the same trust domain as IUT UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 Gm 2 MESSAGE P-Access-Network-Info header Mw Test Purpose Identifier: TP_IMST2_MW_GEN_03 Summary: P-CSCF generates the ICID and includes it in the icid parameter of the P-Charging-Vector header. Clause: 4.5.2, paragraph 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 Gm 2 MESSAGE P-Charging-Vector header icid parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 69 Test Purpose Identifier: TP_IMST2_MW_GEN_04 Summary: REGISTER requests exchanged between a P-CSCF in the visited network and the S-CSCF in the home network shall include the type 1 inter operator identifier (IOI). Clause: 4.5.4, paragraph 4 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 visiting IUT UE1 IMS IUT Step Direction Message IF 1 unprotected REGISTER Gm 2 unprotected REGISTER P-Charging-Vector header ioi parameter type1 Mw Test Purpose Identifier: TP_IMST2_MW_GEN_05 Summary: REGISTER responses exchanged between a P-CSCF in the visited network and the S-CSCF in the home network shall include the type 1 inter operator identifier (IOI). Clause: 4.5.4, paragraph 4 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 visiting IMS ✓ IUT has sent unprotected REGISTER and has received 401 response via Mw UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Mw 2 200 response P-Charging-Vector header ioi parameter type1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 70 Test Purpose Identifier: TP_IMST2_MW_GEN_06 Summary: SIP ACK requests that are exchanged between a S-CSCF of the home originating network and a S-CSCF of the home terminating network shall include a type 2 inter operator identifier (IOI). Clause: 4.5.4, paragraph 4 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ UE1 has sent INVITE and has received 200 response UE1 IMS IUT UE2 Step Direction Message IF 1 ACK to UE2 Gm 2 ACK to UE2 P-Charging-Vector header ioi parameter type2 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 71 Test Purpose Identifier: TP_IMST2_MW_GEN_07 Summary: SIP 200 responses that are exchanged between a S-CSCF of the terminating originating network and a S-CSCF of the home network shall include a type 2 inter operator identifier (IOI) and forward the orig-ioi parameter from the P-Charging-Vector header in the initial request. Clause: 4.5.4, paragraph 4 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ IUT has received INVITE addressed to UE1 via Mw ✓ ✓ IUT has sent INVITE to UE1 via Gm UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 Gm 2 200 response to UE2 P-Charging-Vector header ioi parameter type2 orig-ioi parameter of initial INVITE Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 72 Test Purpose Identifier: TP_IMST2_MW_GEN_08 Summary: A S-CSCF shall not pass any P-Charging-Function-Addresses header of SIP requests or responses sent to a visited network or UE. Clause: 4.5.5, paragraph 3 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ UE1 has sent INVITE and has received 200 response UE1 IMS IUT UE2 Step Direction Message IF 1 ACK to UE2 Gm 2 ACK to UE2 P-Charging-Function-Addresses header Mw Test Purpose Identifier: TP_IMST2_MW_GEN_09 Summary: When the P-CSCF sends a SIP MESSAGE request to the UE, it shall remove the P-Charging-Function-Addresses and P-Charging-Vector headers before sending the message, if present. Clause: 5.2.1 before first numbered list References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT ✓ ✓ UE1 registered in IUT ✓ ✓ IUT configured with an entry point to IMS IUT not configured for topology hiding UE1 IMS IUT Step Direction Message IF 1 MESSAGE to UE1 P-Charging-Vector headers P-Charging-Function-Addresses header Mw 2 MESSAGE to UE1 P-Charging-Vector headers P-Charging-Function-Addresses header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 73 Test Purpose Identifier: TP_IMST2_MW_GEN_10 Summary: When the P-CSCF sends a SIP 200 response to the UE, it shall remove the P-Charging-Function-Addresses and P-Charging-Vector headers before sending the message, if present. Clause: 5.2.1 before first numbered list References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received MESSAGE via Gm from UE1 addressed to UE2 ✓ ✓ IUT has sent MESSAGE via Mw addressed to UE2 IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 200 response originated by UE2 P-Charging-Vector headers P-Charging-Function-Addresses header Mw 2 200 response to UE1 P-Charging-Vector headers P-Charging-Function-Addresses header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 74 Test Purpose Identifier: TP_IMST2_MW_GEN_11 Summary: Before forwarding a SIP MESSAGE request received from a UE, a P-CSCF shall remove any P-Charging-Function-Addresses and P-Charging-Vector headers received. Clause: 5.2.1 first numbered list item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 P-Charging-Vector headers of UE1 P-Charging-Function-Addresses header of UE1 Gm 2 MESSAGE to UE2 P-Charging-Vector headers of UE1 P-Charging-Function-Addresses header of UE1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 75 Test Purpose Identifier: TP_IMST2_MW_GEN_12 Summary: Before forwarding a SIP 200 response received from a UE, a P-CSCF shall remove any P-Charging- Function-Addresses and P-Charging-Vector headers received. Clause: 5.2.1 first numbered list item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received MESSAGE originated by UE2 addressed to UE1 via Mw ✓ ✓ IUT has sent MESSAGE via Gm to UE1 IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 P-Charging-Vector headers of UE1 P-Charging-Function-Addresses header of UE1 Gm 2 200 response to UE2 P-Charging-Vector headers of UE1 P-Charging-Function-Addresses header of UE1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 76 Test Purpose Identifier: TP_IMST2_MW_GEN_13 Summary: Before forwarding a SIP MESSAGE request received from a UE, a P-CSCF shall remove P-Access-Network-Info header if such header contains a "network-provided" parameter. Clause: 5.2.1 first numbered list item 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 P-Access-Network-Info header network provider parameter Gm 2 MESSAGE to UE2 P-Access-Network-Info header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 77 Test Purpose Identifier: TP_IMST2_MW_GEN_14 Summary: Before forwarding a SIP 200 response received from a UE, a P-CSCF shall remove P-Access-Network-Info header if such header contains a "network-provided" parameter. Clause: 5.2.1 first numbered list item 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received MESSAGE addressed to UE1 originated by UE2 via Mw ✓ ✓ IUT has sent MESSAGE via Gm to UE1 IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 P-Access-Network-Info header network provider parameter Gm 2 200 response to UE2 P-Access-Network-Info header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 78 Test Purpose Identifier: TP_IMST2_MW_GEN_15 Summary: A P-CSCF shall remove the P-Media-Authorization header from a SIP MESSAGE request from the UE before forwarding the message. Clause: 5.2.1 before NOTE 9 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 P-Media-Authorization header Gm 2 MESSAGE to UE2 P-Media-Authorization header Mw Test Purpose Identifier: TP_IMST2_MW_GEN_16 Summary: A P-CSCF shall remove the P-Media-Authorization header from a SIP 200 response from the UE before forwarding the message. Clause: 5.2.1 before NOTE 9 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE1 has received MESSAGE originated by UE2 IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 P-Media-Authorization header Gm 2 200 response to UE2 P-Media-Authorization header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 79 Test Purpose Identifier: TP_IMST2_MW_GEN_17 Summary: When a P-CSCF receives SIP Redirect response (3xx), other than a 305 (Use Proxy) response, to a request forwarded from the UE, it shall not resend the original message to any of the URIs specified in the Contact header field of the 3xx response. Clause: 5.2.1 before NOTE 10 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ IUT has received MESSAGE addressed to UE2 via Gm ✓ ✓ IUT has sent MESSAGE addressed to UE2 via Mw IUT not configured for topology hiding UE1 IMS IUT UE2 Step Direction Message IF 1 3xx response different to 305 response contact header Contact URI Mw 2 || || MESSAGE to Contact URI Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 80
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.2 Registration procedures
|
Test Purpose Identifier: TP_IMST2_MW_REG_01 Summary: When a P-CSCF receives REGISTER request from the UE, it shall insert a correct Path header containing SIP URI identifying the P-CSCF, Require header with path option tag, P-Charging-Vector header with the icid parameter and a type 1 orig-ioi parameter identifying the sending network but not including term-ioi parameter, and insert a P-Visited-Network-ID header identifying the visited network at the home network. Clause: 5.2.2.1 second numbered list items 1,2,3,4 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE1 visiting IUT UE1 IMS IUT Step Direction Message IF 1 unprotected REGISTER Gm 2 unprotected REGISTER Path header SIP URI of IMS P-CSCF Require header path tag parameter P-Charging-Vector header icid parameter orig-ioi parameter type1 of the sending network term-ioi parameter type1 P-Visited-Network-ID header visited network pre-provisioned string Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 81 Test Purpose Identifier: TP_IMST2_MW_REG_02 Summary: When a P-CSCF receives REGISTER request from the UE, it shall insert the parameter "integrity- protected" with a value "yes" into the Authorization header field if the REGISTER request was received protected with the security association and includes an authentication challenge response. Clause: 5.2.2.2 first numbered list item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ ✓ ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has established an IMS AKA security association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER authentication challenge response parameter Gm 2 REGISTER Authorization header integrity-protected parameter yes Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 82 Test Purpose Identifier: TP_IMST2_MW_REG_03 Summary: When a P-CSCF receives REGISTER request from the UE, it shall insert the parameter "integrity- protected" with a value "yes" into the Authorization header field if the REGISTER request was received on the security association created during the last successful authentication procedure. Clause: 5.2.2.2 first numbered list item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has established an IMS AKA security association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Gm 2 REGISTER Authorization header integrity-protected parameter yes Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 83 Test Purpose Identifier: TP_IMST2_MW_REG_04 Summary: When a P-CSCF receives REGISTER request from the UE, it shall insert the parameter "integrity- protected" with a value "no" into the Authorization header field if the REGISTER request was not received protected with the security association and remove the Security-Client header if the header is present Also the rPort and received parameter of the Via header are set to the received port and IP address. Clause: 5.2.2.2 first numbered list item 2a b, c References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT UE1 has not established a security association UE1 IMS IUT Step Direction Message IF 1 unprotected REGISTER Security-Client header Gm 2 REGISTER Authorization header integrity-protected parameter no Security-Client header Via header rPort parameter received source port received parameter received source IP address Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 84 Test Purpose Identifier: TP_IMST2_MW_REG_05 Summary: When a P-CSCF receives REGISTER request from the UE without protection and without Security- Client header then the P-CSCF shall return a SIP 4xx response. Clause: 5.2.2.2 second numbered list item 5 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT UE1 IMS IUT Step Direction Message IF 1 unprotected REGISTER Security-Client header Gm 2 || || REGISTER Mw 3 4xx response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 85 Test Purpose Identifier: TP_IMST2_MW_REG_06 Summary: When a P-CSCF receives REGISTER request from the UE if the REGISTER request was received with a temporary security association but without a Security-Verify header, then the P-CSCF shall return a 4xx response. Clause: 5.2.2.2 first numbered list item 3a References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has established a temporary IMS AKAsecurity association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Security-Verify header Gm 2 || || REGISTER Mw 3 4xx response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 86 Test Purpose Identifier: TP_IMST2_MW_REG_07 Summary: When a P-CSCF receives REGISTER request from the UE if the REGISTER request was received via a temporary security association and the content of the Security-Verify and the Security-Client header do not match previous information then the P-CSCF shall reject the request by sending a 4xx response. Clause: 5.2.2.2 first numbered list item 3a References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has established a temporary IMS AKAsecurity association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Security-Verify header different to Security-Server header of 401 response Security-Client header equal to Security-Client header of unprotected REGISTER Gm 2 || || REGISTER Mw 3 4xx response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 87 Test Purpose Identifier: TP_IMST2_MW_REG_08 Summary: When a P-CSCF receives REGISTER request from the UE if the REGISTER request was received via a temporary security association and Security-Verify header and Security-Client headers match previous information, the P-CSCF shall remove the Security-Verify and the Security-Client header. Clause: 5.2.2.2 first numbered list item 3a References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has established a temporary IMS AKA security association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Security-Verify header equal to Security-Server header of 401 response Security-Client header equal to Security-Client header of unprotected REGISTER Gm 2 REGISTER Security-Verify header Security-Client header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 88 Test Purpose Identifier: TP_IMST2_MW_REG_09 Summary: When a P-CSCF receives REGISTER request from the UE if the REGISTER request was received via an already established security association, then the P-CSCF shall remove the Security-Client and Security-Verify headers if it is present. Clause: 5.2.2.2 first numbered list item 3b References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has established an IMS AKA security association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Security-Verify header Security-Client header Gm 2 REGISTER Security-Verify header Security-Client header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 89 Test Purpose Identifier: TP_IMST2_MW_REG_10 Summary: When a P-CSCF receives REGISTER request from the UE if the REGISTER request was received via an already established security association and the Security-Client header, then the P-CSCF shall return a suitable 4xx response. Clause: 5.2.2.2 first numbered list item 3b References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has established an IMS AKA security association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Security-Client header Gm 2 || || REGISTER Mw 3 4xx response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 90 Test Purpose Identifier: TP_IMST2_MW_REG_11 Summary: When a P-CSCF receives REGISTER request from the UE if the REGISTER request was received via an already established security association and private user identity in the Authorization header differs from the one in the unprotected REGISTER request, then the P-CSCF shall return a 403 response. Clause: 5.2.2.2 first numbered list item 3b References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has established an IMS AKA security association UE1 IMS IUT Step Direction Message IF 1 protected REGISTER Authorization header private user identity different to private user identity of unprotected REGISTER Gm 2 || || REGISTER Mw 3 403 response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 91 Test Purpose Identifier: TP_IMST2_MW_REG_12 Summary: When a P-CSCF receives SIP 401 (Unauthorized) response to a REGISTER request it shall remove the CK and IK values contained in the 401 (Unauthorized) response insert a Security-Server header in the response. Clause: 5.2.2.2 second numbered list item 2 and 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE1 visiting IUT ✓ UE1 has sent REGISTER UE1 IMS IUT Step Direction Message IF 1 401 response Mw 2 401 response to UE1 WWW-Authenticate header CK parameter IK parameter Security-Server header P-CSCF security list the parameters needed for the security association setup Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 92 Test Purpose Identifier: TP_IMST2_MW_REG_14 Summary: Upon receipt of a SIP 200 (OK) response to an initial SIP REGISTER request, a P-CSCF located in the visited network shall send a SIP SUBSCRIBE request to the entry point of the home network. Clause: 5.2.3 item 1 and 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ IUT configured for establishing digest without TLS security association ✓ ✓ UE1 visiting IUT ✓ UE1 has sent initial REGISTER UE1 IMS IUT Step Direction Message IF 1 200 response Mw 2 SUBSCRIBE Request-URI From header SIP URI of IUT P-CSCF To header SIP URI public user identity Event header reg parameter Expires header a value higher than the value in the 200 response P-Asserted-Identity header SIP URI of IUT P-CSCF inserted into the Path header during the registration of UE1 P-Charging-Vector header icid parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 93 Test Purpose Identifier: TP_IMST2_MW_REG_15 Summary: When an S-CSCF receives SIP REGISTER request in which the "integrity-protected" parameter of its Authorization header is set to the value "no", the Authorization header specifies a private user identity which has previously been used to register one or more public user identities which have not yet expired and authentication is successful, it shall perform network-initiated deregistration of the unexpired public user identities previously registered by the user. Clause: 5.4.1.2.1, 5.4.1.2.2, 5.4.1.5 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE2 visiting IMS ✓ ✓ ✓ UE2 registered public user identity with current private user identity in IUT ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header integrity protected parameter no Mw 2 401 response WWW-Authenticate header Mw 3 REGISTER originated by UE2 Authorization header integrity protected parameter yes Mw 4 200 response Mw 5 NOTIFY NOTIFY body registered public user identity Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 94 Test Purpose Identifier: TP_IMST2_MW_REG_16 Summary: When an S-CSCF receives SIP REGISTER request in which the "integrity-protected" parameter in the Authorization header is set to "no" and the To field contains an unregistered public user identity, the S-CSCF shall send a 401 (Unauthorized) response to the originating UE including WWW-Authenticate header with a realm, RAND, AUTN, algorithm, IK, and CK parameters. Clause: 5.4.1.2.1A References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE2 visiting IMS ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header integrity protected parameter no To header a not registered public user identity Mw 2 401 response WWW-Authenticate header realm parameter a globally unique name of the IUT S-CSCF RAND parameter AUTN parameter algorithm parameter AKAv1-MD5 ik parameter ck parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 95 Test Purpose Identifier: TP_IMST2_MW_REG_17 Summary: When an S-CSCF receives SIP REGISTER request without the "integrity-protected" parameter in the Authorization header, the S-CSCF shall perform the procedure for receipt of a REGISTER request without the "integrity-protected" parameter for the received public user identity and perform network-initiated de-registration if applicable. Clause: 5.4.1.2.1D References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE2 visiting IMS ✓ ✓ ✓ UE2 registered public user identity with another contact address in IUT ✓ IUT configured for NASS-IMS bundled authentication ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header integrity protected parameter Contact header registered public user identities Mw 2 200 response Mw 3 NOTIFY NOTIFY body registered public user identity Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 96 Test Purpose Identifier: TP_IMST2_MW_REG_18 Summary: When S-CSCF receives SIP REGISTER request without the "integrity-protected" parameter in the Authorization header and for existing contact information, it shall process the REGISTER request as if the "integrity-protected" parameter in the Authorization header was set to "yes". Clause: 5.4.1.2.1D References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ ✓ UE2 registered public user identity with current private user identity in IUT ✓ IUT configured for NASS-IMS bundled authentication ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 for registered public user identity Authorization header integrity-protected parameter Mw 2 200 response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 97 Test Purpose Identifier: TP_IMST2_MW_REG_19 Summary: When S-CSCF receives SIP REGISTER request without an Authorization header and for existing contact information, it shall process the REGISTER request as the "integrity-protected" parameter in the Authorization header was set to "yes". Clause: 5.4.1.2.1D References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ ✓ UE2 registered public user identity with current private user identity in IUT ✓ IUT configured for NASS-IMS bundled authentication ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 for registered public user identity Authorization header Mw 2 200 response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 98 Test Purpose Identifier: TP_IMST2_MW_REG_20 Summary: If a S-CSCF receives SIP REGISTER request from a UE and the request contains an Expires header which is set to a value shorter than the minimum time that the S-CSCF is able to process, it shall return a SIP 423 (Interval Too Brief) response containing Min-Expires header. Clause: 5.4.1.2.3 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT IUT not configured for topology hiding IUT not configured for IMS AKA authentication ✓ ✓ IUT configured with an entry point to IMS IMS IUT Step Direction Message IF 1 REGISTER originated by UE2 Expires header duration smaller than minimum Mw 2 423 response Min-Expires header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 99 Test Purpose Identifier: TP_IMST2_MW_REG_21 Summary: When an S-CSCF receives SIP REGISTER request in which the "integrity-protected" parameter in the Authorization header is set to "yes", To header contains an unregistered public user identity, the S-CSCF shall send a 401 (Unauthorized) response to the originating UE including WWW- Authenticate header with realm, a RAND and AUTN, algorithm, ik, and the CK (Cipher Key) parameters. Clause: 5.4.1.2.2 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE2 visiting IMS ✓ IUT configured for IMS AKA authentication ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header integrity protected parameter yes To header a not registered public user identity Mw 2 401 response WWW-Authenticate header realm parameter globally unique name RAND parameter AUTN parameter algorithm parameter AKAv1-MD5 ik parameter ck parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 100 Test Purpose Identifier: TP_IMST2_MW_REG_22 Summary: When an S-CSCF receives SIP REGISTER request containing an authentication challenge response from the UE and the integrity-protected parameter in the Authorization header is set to the value "yes", the S-CSCF shall return a SIP 200 (OK) response to the UE. Clause: 5.4.1.2.2, 5.4.1.2.2F References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE2 visiting IMS ✓ ✓ ✓ UE2 has sent unprotected REGISTER and has received 401 response ✓ IUT configured for IMS AKA authentication ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header integrity protected parameter yes algorithm parameter AKAv1-MD5 username parameter private user identity response parameter valid challenge response initial CallID parameter Mw 2 200 response Path header P-Associated-URI header registered public user identities Service-Route header SIP URI IUT S-CSCF P-Charging-Function-Addresses header P-Charging-Vector header Contact header address of public user identity Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 101 Test Purpose Identifier: TP_IMST2_MW_REG_23 Summary: If a S-CSCF receives SIP REGISTER request containing an authentication challenge response from the UE and the request is not the expected REGISTER and the integrity-protected parameter in the Authorization header is set to the value "yes", the S-CSCF shall return a SIP 403 (Forbidden) response to the UE. Clause: 5.4.1.2.3 last paragraph, 5.4.1.2.3A paragraph 1 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE2 visiting IMS ✓ ✓ ✓ UE2 has sent unprotected REGISTER and has received 401 response ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header integrity-protected parameter yes unknown CallID parameter Mw 2 403 response P-Charging-Vector header orig-ioi parameter type1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 102 Test Purpose Identifier: TP_IMST2_MW_REG_24 Summary: When an S-CSCF receives SIP REGISTER request from the UE containing an Authentication Synchronization (AUTS) directive indicating that the Sequence Number (SQN) was out of range, the S-CSCF shall return a SIP 401 (Unauthorized) or 403 (Forbidden). Clause: 5.4.1.2.3 last paragraph, 5.4.1.2.3A paragraph 3 before NOTE 3 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE2 visiting IMS ✓ ✓ ✓ UE2 has sent unprotected REGISTER and has received 401 response ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header AUTS parameter invalid SQN parameter Mw 2a 401 response to UE2 P-Charging-Vector header orig-ioi parameter type1 Mw 2b 403 response to UE2 P-Charging-Vector header orig-ioi parameter type1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 103 Test Purpose Identifier: TP_IMST2_MW_REG_25 Summary: When an S-CSCF receives SIP REGISTER request with the "integrity-protected" parameter in the Authorization header set to "yes" and neither the user identity received in the To header nor the private user identity received in the Authorization header of the REGISTER request match any of the S-CSCFs registered users, it shall return a SIP 500 (Server Internal Error) response to the UE. Clause: 5.4.1.2.3 last paragraph, 5.4.1.2.3A paragraph 4 before NOTE 6 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ UE2 visiting IMS ✓ ✓ ✓ UE2 has sent unprotected REGISTER and has received 401 response ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 REGISTER originated by UE2 Authorization header integrity-protected parameter yes private user identity matching previous registered public user identity To header public user identity not matching previous registered public user identity Mw 2 500 response to UE2 P-Charging-Vector header orig-ioi parameter type1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 104 Test Purpose Identifier: TP_IMST2_MW_REG_26 Summary: When an S-CSCF receives SIP REGISTER request which was expected to carry the response to an authentication challenge but the request contains no authentication challenge response from the UE and no Authentication Synchronization (AUTS) parameters indicating that the Message Authentication Code (MAC) parameter was invalid in the challenge, the S-CSCF shall return a SIP 403 (Forbidden) response to the UE. Clause: 5.4.1.2.3 last paragraph, 5.4.1.2.3A paragraph 2 before NOTE 2 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for IMS AKA authentication ✓ ✓ ✓ UE2 has sent unprotected REGISTER and has received 401 response ✓ ✓ UE2 visiting IMS ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 subsequent REGISTER originated by UE2 Authorization header authentication challenge response parameter AUTS parameter invalid MAC parameter Mw 2 403 response to UE2 P-Charging-Vector header orig-ioi parameter type1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 105
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.3 Initial request procedures
|
Test Purpose Identifier: TP_IMST2_MW_INI_06 Summary: If a security association exists between the UE and P-CSCF, when a P-CSCF receives any SIP 1xx or 2xx response as a result of a forwarded request for an initial dialog, it shall replace in the response its own Record Route entry with its own SIP URI with the protected server port number of the security association and either the P-CSCF FQDN or the P-CSCF IP address. Clause: 5.2.6.3.4 item 4 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established a security association ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ IUT has received INVITE addressed to UE2 ✓ ✓ IUT has sent INVITE addressed to UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 180 response to UE1 Mw 2 180 response to UE1 Record Route header SIP URI of IUT P-CSCF port number of IUT P-CSCF for security association IP address of IUT P-CSCF or FQDN address of IUT P-CSCF Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 106 Test Purpose Identifier: TP_IMST2_MW_INI_07 Summary: If a security association exists between the UE and P-CSCF, when a P-CSCF receives any SIP 1xx or 2xx response as a result of a forwarded request for an initial dialog, it shall replace in the response its own Record Route entry with its own SIP URI with the protected server port number of the security association and either the P-CSCF FQDN or the P-CSCF IP address. Clause: 5.2.6.3.4 item 4 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established a security association ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ IUT has received INVITE addressed to UE2 ✓ ✓ IUT has sent INVITE addressed to UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE1 Mw 2 200 response to UE1 Record Route header SIP URI of IUT P-CSCF port number of IUT P-CSCF for security association IP address of IUT P-CSCF or FQDN address of IUT P-CSCF Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 107 Test Purpose Identifier: TP_IMST2_MW_INI_08 Summary: When a P-CSCF receives SIP 1xx or 2xx response to an initial request for a dialogue from a UE, it shall remove the P-Preferred-Identity header, if present, and insert a P-Asserted-Identity header with the value saved from the P-Called-Party-ID header that was received in the initial request and the registration display name if available. Clause: 5.2.6.4.4 item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has stored display name of UE1 ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent INVITE via Gm to UE1 ✓ ✓ IUT has stored P-Called-Party-ID header of UE1 ✓ ✓ IUT has stored display name of UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 180 response to UE2 P-Preferred-Identity header Gm 2 180 response P-Preferred-Identity header P-Asserted-Identity header stored display name parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 108 Test Purpose Identifier: TP_IMST2_MW_INI_09 Summary: When a P-CSCF receives SIP 1xx or 2xx response to an initial request for a dialogue from a UE, it shall remove the P-Preferred-Identity header, if present, and insert a P-Asserted-Identity header with the value saved from the P-Called-Party-ID header that was received in the initial request and the registration display name if available. Clause: 5.2.6.4.4 item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has stored display name of UE1 ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent INVITE via Gm to UE1 ✓ ✓ IUT has stored P-Called-Party-ID header of UE1 ✓ ✓ IUT has stored display name of UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 P-Preferred-Identity header Gm 2 200 response P-Preferred-Identity header P-Asserted-Identity header stored display name parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 109 Test Purpose Identifier: TP_IMST2_MW_INI_10 Summary: When a P-CSCF receives SIP 1xx or 2xx response to an initial request for a dialogue from a UE, if Via headers do not match the saved list of Via headers received in the initial request corresponding to the same dialog, it either discards the response or replaces the Via header with the ones from the initial request. Clause: 5.2.6.4.4 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.4.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent INVITE to UE1 ✓ IUT has stored Via header UE1 IMS IUT UE2 Step Direction Message IF 1 180 response to UE2 Via header not matching stored Via header Gm 2a || || 180 response Mw 2b 180 response Via header stored Via header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 110 Test Purpose Identifier: TP_IMST2_MW_INI_11 Summary: When a P-CSCF receives SIP 1xx or 2xx response to an initial request for a dialogue from a UE, if Via headers do not match the saved list of Via headers received in the initial request corresponding to the same dialog, it either discards the response or replaces the Via header with the ones from the initial request. Clause: 5.2.6.4.4 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.4.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent INVITE to UE1 ✓ IUT has stored Via header UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 Via header not matching stored Via header Gm 2a || || 200 response Mw 2b 200 response Via header stored Via header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 111 Test Purpose Identifier: TP_IMST2_MW_INI_12 Summary: When a P-CSCF receives SIP 1xx or 2xx response to an initial request for a dialogue from a UE, with a Record-Route header including a list of URIs different to the one received in the Record-Route header of the initial request, discards the response or replaces the Record-Route header values with those received in the initial request. If a security association exists, the P-CSCF adds to the Record-Route header the port number of its own Record-Route entry with its own SIP URI and the port number where it awaits subsequent requests from the calling party and with either the P-CSCF FQDN that resolves to its IP address; or the P-CSCF IP address; and remove the comp parameter if present. Clause: 5.2.6.4.4 item 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.4.2 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established a security association ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent INVITE to UE1 ✓ IUT has stored Record-Route header UE1 IMS IUT UE2 Step Direction Message IF 1 180 response to UE2 Record-Route header not matching stored Record- Route header Gm 2a || || 180 response Mw 2b 180 response Record-Route header stored Record-Route header port number of Record-Route header of IUT P- CSCF SIP URI port number of IUT P-CSCF FQDN address of IUT P-CSCF or IP address of IUT P-CSCF comp parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 112 Test Purpose Identifier: TP_IMST2_MW_INI_13 Summary: When a P-CSCF receives SIP 1xx or 2xx response to an initial request for a dialogue from a UE, with a Record-Route header including a list of URIs different to the one received in the Record-Route header of the initial request, discards the response or replaces the Record-Route header values with those received in the initial request. If a security association exists, the P-CSCF adds to the Record-Route header the port number of its own Record-Route entry with its own SIP URI and the port number where it awaits subsequent requests from the calling party and with either the P-CSCF FQDN that resolves to its IP address; or the P-CSCF IP address; and remove the comp parameter if present. Clause: 5.2.6.4.4 item 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.4.2 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established a security association ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent INVITE to UE1 ✓ IUT has stored Record-Route header UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 Record-Route header not matching stored Record- Route header Gm 2a || || 200 response Mw 2b 200 response Record-Route header stored Record-Route header port number of Record-Route header of IUT P- CSCF SIP URI port number of IUT P-CSCF FQDN address of IUT P-CSCF or IP address of IUT P-CSCF comp parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 113 Test Purpose Identifier: TP_IMST2_MW_INI_14 Summary: When a P-CSCF receives any other response other than a SIP 1xx or a 2xx to an initial request to a UE for a dialogue and if the list of Via headers does not match the saved list of Via headers received in the initial request corresponding to the same dialog, it shall either discard the response or replace the Via header values with those received in the initial request. Clause: 5.2.6.4.4 second numbered list References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.4.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent INVITE to UE1 ✓ IUT has stored Via header UE1 IMS IUT UE2 Step Direction Message IF 1 4xx response to UE2 Via header not matching stored Via header Gm 2a || || 4xx response Mw 2b 4xx response Via header stored Via header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 114 Test Purpose Identifier: TP_IMST2_MW_INI_15 Summary: If a P-CSCF requires periodic refreshment of a session established after receiving a SIP INVITE request from a UE the P-CSCF shall insert a Session-Expires header field in the request before forwarding it if none was present in the request. The proxy SHALL NOT include a refresher parameter in the header field value. Clause: 5.2.7.2, RFC 4028 [8], clause 8 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/26.1.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for requiring periodic refreshment ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 INVITE to UE2 Session-Expires header Gm 2 INVITE Session-Expires header refresher parameter Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 115 Test Purpose Identifier: TP_IMST2_MW_INI_16 Summary: If a P-CSCF requires periodic refreshment of a session established after receiving a SIP INVITE request from a UE the P-CSCF shall insert a Session-Expires header field in the request before forwarding it if none was present in the request. The duration should not be lower than the value in the Min-SE header field in the request, if it is present. Clause: 5.2.7.2, RFC 4028 [8], clause 8 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/26.1.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for requiring periodic refreshment ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 INVITE to UE2 Session-Expires header Min-SE header Gm 2 INVITE Session-Expires header duration parameter greater than Min-SE header Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 116 Test Purpose Identifier: TP_IMST2_MW_INI_18 Summary: If a P-CSCF requires periodic refreshment of a session established after receiving a SIP INVITE request destined for a UE the P-CSCF shall insert a Session-Expires header field in the request before forwarding it if none was present in the request. The proxy SHALL NOT include a refresher parameter in the header field value. Clause: RFC 4028 [8], clause 8 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/26.2.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for requiring periodic refreshment ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 INVITE originated by UE2 to UE1 Session-Expires header Mw 2 INVITE to UE1 Session-Expires header refresher parameter Gm 3 100 response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 117 Test Purpose Identifier: TP_IMST2_MW_INI_19 Summary: If a P-CSCF requires periodic refreshment of a session established after receiving a SIP INVITE request destined for a UE the P-CSCF shall insert a Session-Expires header field in the request before forwarding it if none was present in the request. The duration should not be lower than the value in the Min-SE header field in the request, if it is present. Clause: 5.2.7.2, RFC 4028 [8], clause 8 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/26.2.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ IUT configured for requiring periodic refreshment ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 INVITE originated by UE2 to UE1 Session-Expires header Min-SE header Mw 2 INVITE to UE1 Session-Expires header duration parameter greater than Min-SE header Gm 3 100 response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 118 Test Purpose Identifier: TP_IMST2_MW_INI_20 Summary: When a P-CSCF receives an initial SIP INVITE request destined for a UE it shall respond with a SIP 100 (Trying) provisional response before forwarding the INVITE to the UE. Clause: 5.2.7.3 paragraph 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 INVITE to UE1 Mw 2 100 response Mw 3 INVITE to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 119 Test Purpose Identifier: TP_IMST2_MW_INI_21 Summary: When a S-CSCF receives a response to an initial request and the response contains term-ioi parameters and is not destined for an AS, the S-CSCF shall remove all received ioi parameters from the P-Charging-Vector header before forwarding the response. Clause: 5.4.3.2 before NOTE 20 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has sent INVITE from UE1 to UE2 via Mw UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE1 P-Charging-Vector header ioi parameter Mw 2 200 response to UE1 P-Charging-Vector header ioi parameter Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 120 Test Purpose Identifier: TP_IMST2_MW_INI_22 Summary: When the S-CSCF receives an initial request for a new dialogue and the Request URI contains a barred public user identity, the S-CSCF shall reject the request by sending a SIP 404 (Not Found) response. Clause: 5.4.3.3 first numbered list item 1 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE2 registered in IMS UE2 not registered in IUT ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 INVITE Request URI barred public user identity Mw 2 404 response to UE2 Mw Test Purpose Identifier: TP_IMST2_MW_INI_23 Summary: When the S-CSCF receives an initial request and the Request URI contains an invalid GRUU, the S- CSCF shall reject the request by sending a SIP 4xx response. Clause: 5.4.3.3 first numbered list 3A References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IMS IUT UE2 Step Direction Message IF 1 INVITE Request URI invalid GRUU parameter Mw 2 4xx response to UE2 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 121 Test Purpose Identifier: TP_IMST2_MW_INI_24 Summary: When the S-CSCF receives an initial request and the P-Asserted-Service header indicates a service that is not subscribed-to by the user, the S-CSCF shall reject the request by sending a SIP 403 (Forbidden) response. Clause: 5.4.3.3 first numbered list 3C References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured to reject unsubscribed service IMS IUT UE2 Step Direction Message IF 1 INVITE P-Asserted-Service header unsubscribed service Mw 2 403 response to UE2 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 122 Test Purpose Identifier: TP_IMST2_MW_INI_25 Summary: When the S-CSCF receives an initial request without P-Asserted-Service header and the SDP offer indicates a service that is not subscribed-to by the user, the S-CSCF shall reject the request by sending a SIP 403 (Forbidden) response. Clause: 5.4.3.3 first numbered list 3D References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured to reject unsubscribed service IMS IUT UE2 Step Direction Message IF 1 INVITE P-Asserted-Service header SDP offer unsubscribed service Mw 2 403 response to UE2 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 123
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.4 Standalone requests procedures
|
Test Purpose Identifier: TP_IMST2_MW_STA_01 Summary: When a P-CSCF receives a request for a standalone transaction from a UE, containing a list of URIs in the Route header different to the stored values of the Service-Route header from the last successful registration or re-registration, then the P-CSCF shall either return a SIP 400 (Bad Request) response and not forward the request or replace the received Route header value in the request with the value of the Service-Route header received during the last SIP 200 (OK) response for a registration or reregistration. Clause: 5.2.6.3.7 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.8.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has stored Service-Route header of UE1 ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 Route header not matching stored Service-Route header 2a || || MESSAGE Mw 3a 400 response Gm 2b MESSAGE Route header stored Record-Route header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 124 Test Purpose Identifier: TP_IMST2_MW_STA_02 Summary: When a P-CSCF receives request for a standalone transaction from a UE, it shall remove the P-Preferred-Identity header, if present, and insert a P-Asserted-Identity header with a value representing the initiator of the request and including display name if previously stored during registration. Clause: 5.2.6.3.7 item 4 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has stored display name of UE1 ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 P-Preferred-Identity header 2 MESSAGE P-Preferred-Identity header P-Asserted-Identity header stored display name parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 125 Test Purpose Identifier: TP_IMST2_MW_STA_03 Summary: When a P-CSCF receives request for a standalone transaction from a UE it shall add a P-Charging- Vector header with the icid parameter. Clause: 5.2.6.3.7 item 5 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has stored Service-Route header of UE1 ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE to UE2 2 MESSAGE P-Charging-Vector header icid parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 126 Test Purpose Identifier: TP_IMST2_MW_STA_04 Summary: When a P-CSCF receives any response to a forwarded request for a standalone transaction, it shall forward the response to the UE. Clause: 5.2.6.3.8 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received MESSAGE from UE1 via Gm addressed to UE2 ✓ IUT has sent MESSAGE via Mw UE1 IMS IUT UE2 Step Direction Message IF 1 200 response originated by UE2 to UE1 Mw 2 200 response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 127 Test Purpose Identifier: TP_IMST2_MW_STA_05 Summary: When a P-CSCF receives request for a standalone transaction or a request for an unknown method (that does not relate to an existing dialog) destined for a UE, it shall add its own address to the top of the received list of Via header in a format that contains the protected server port number of the security association, if established, between the UE and the P-CSCF and either the P-CSCF FQDN that resolves to the IP address of the security association or the P-CSCF IP address of the security association. Clause: 5.2.6.4.7 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established a security association ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT UE2 Step Direction Message IF 1 MESSAGE originated by UE2 to UE1 Mw 2 MESSAGE to UE1 Via header port number of IUT P-CSCF for security association FQDN address of IUT P-CSCF or IP address of IUT P-CSCF for security association Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 128 Test Purpose Identifier: TP_IMST2_MW_STA_06 Summary: When a P-CSCF receives any response to a request for a standalone transaction destined for a UE, if the list of Via headers does not match the saved list of Via headers received in the request, either discard the response or replace the Via header values with those received in the request. Clause: 5.2.6.4.8 item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.10.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ IUT has received MESSAGE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent MESSAGE via Gm to UE1 ✓ IUT has stored Via header UE1 IMS IUT UE2 Step Direction Message IF 1 200 response Via header not matching stored Via header Gm 2a || || 200 response Mw 2b 200 response stored Via header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 129 Test Purpose Identifier: TP_IMST2_MW_STA_07 Summary: When a P-CSCF receives any response to a request for a standalone transaction destined for a UE, remove the P-Preferred-Identity header, if present, and insert a P-Asserted-Identity header with the saved public user identity from the P-Called-Party-ID header of the request plus the display name if previously stored during registration. Clause: 5.2.6.4.8 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has received MESSAGE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent MESSAGE via Gm to UE1 ✓ IUT has stored public user identity from P-Called-Party-ID header UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 P-Preferred-Identity header 2 200 response to UE2 P-Preferred-Identity header P-Asserted-Identity header stored public user identity stored display name parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 130
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.5 Subsequent requests on a dialogue procedures
|
Test Purpose Identifier: TP_IMST2_MW_SUB_01 Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, that does not relate to an existing dialogue in which the originator is involved then the P-CSCF shall send a SIP 403 (Forbidden) response back to the originator and not forward the request. Clause: 5.2.6.3.9 item 1a References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE1 has established an INVITE dialogue with UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 BYE Call-ID header || existent dialog Gm 2 || || BYE Mw 3 403 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 131 Test Purpose Identifier: TP_IMST2_MW_SUB_02 Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, from a UE, containing a list of URIs in the Route header different to the stored values of the Service-Route header for the existing dialogue then the P-CSCF shall either return a SIP 400 (Bad Request) response and not forward the request or replace the received Route header value in the request with the stored value of the Service-Route header for the same dialogue. Clause: 5.2.6.3.9 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.10.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has stored Record-Route header of UE1 ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE1 has established an INVITE dialogue with UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 BYE Route header not matching stored Record-Route header Gm 2b || || BYE Mw 3b 400 response Gm 2a BYE Route header stored Record-Route header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 132 Test Purpose Identifier: TP_IMST2_MW_SUB_03 Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, from a UE, for dialogues that are not INVITE dialogues, it shall add a P-Charging-Vector header with the icid parameter. Clause: 5.2.6.3.9 item 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established a SUBSCRIBE dialogue with UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 PUBLISH Gm 2 PUBLISH P-Charging-Vector header icid parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 133 Test Purpose Identifier: TP_IMST2_MW_SUB_04 Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, for a UE, if the request does not relate to an existing dialogue in which the originator is involved, then the P-CSCF shall send a SIP 403 (Forbidden) response back to the originator and not forward the request. Clause: 5.2.6.3.9 item 1a References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 BYE to UE1 Call-ID header || existent dialog Mw 2 || || BYE to UE1 Gm 3 403 response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 134 Test Purpose Identifier: TP_IMST2_MW_SUB_05 Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, for a UE containing a list of Route headers different to the stored list of Record-Route headers for the same dialog, then the P-CSCF shall either return a SIP 400 (Bad Request) response and not forward the request or replace the Route header value in the request with the stored list of Record-Route headers for the same dialogue. Clause: 5.2.6.3.9 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.10.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 ✓ IUT has stored Record-Route header UE1 IMS IUT UE2 Step Direction Message IF 1 BYE to UE1 Route header not matching stored Record-Route header Mw 2a || || BYE to UE1 Gm 3a 400 response Mw 2b BYE to UE1 stored Record-Route header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 135 Test Purpose Identifier: TP_IMST2_MW_SUB_06 Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, for a UE for dialogues that are not INVITE dialogues, add a P-Charging-Vector header with the icid parameter. Clause: 5.2.6.2.9 item 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established a SUBSCRIBE dialogue with UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 PUBLISH to UE1 Mw 2 PUBLISH to UE1 P-Charging-Vector header Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 136 Test Purpose Identifier: TP_IMST2_MW_SUB_07 Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, for a UE, it shall add its own address to the top of the received list of Via header in a format that contains the protected server port number of the security association if one is established between the UE to the P-CSCF and either the P-CSCF FQDN that resolves to the IP address of the security association or the P-CSCF IP address of the security association. Clause: 5.2.6.4.9 item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established an IMS AKA security association ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE Dialogue with UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 BYE to UE1 originated by UE2 Mw 2 BYE to UE1 Via header port number of IUT P-CSCF for security association FQDN address of IUT P-CSCF or IP address of IUT P-CSCF for security association Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 137 Test Purpose Identifier: TP_IMST2_MW_SUB_07A Summary: When a P-CSCF receives a subsequent request, other than a target refresh request, for a UE, it shall add its own address to the top of the received list of Via header. Clause: 5.2.6.4.9 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established a digest without TLS security association ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE Dialogue with UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 BYE to UE1 originated by UE2 Mw 2 BYE to UE1 Via header port number of IUT P-CSCF address of IUT P-CSCF Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 138 Test Purpose Identifier: TP_IMST2_MW_SUB_08 Summary: When a P-CSCF receives a response to a subsequent request, other than a target refresh request, if the list of Via headers does not match the saved list of Via headers received in the subsequent request, the P-CSCF shall either discard the response or replace the Via header values with those received in the subsequent request. Clause: 5.2.6.4.10 item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.12.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE Dialogue with UE1 ✓ IUT has stored Via header ✓ ✓ ✓ IUT has received BYE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent BYE via Gm to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 200 response to UE2 Via header not matching stored Via header Gm 2a || || 200 response Mw 2b 200 response stored Via header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 139 Test Purpose Identifier: TP_IMST2_MW_SUB_09 Summary: If a P-CSCF receives a subsequent request within a dialogue for which it has previously initiated session release, the P-CSCF shall terminate the request and answer it with a SIP 481 (Call/Transaction Does Not Exist) response. Clause: 5.2.8.1.3 paragraph 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ UE1 has established an INVITE dialog ✓ ✓ IUT has received BYE from UE1 ✓ IUT has sent BYE via Mw UE1 IMS IUT UE2 Step Direction Message IF 1 BYE to UE1 Mw 2 481 response to UE2 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 140 Test Purpose Identifier: TP_IMST2_MW_SUB_10 Summary: When the registration lifetime of the only public user identity currently registered of the calling user expires while there is still an active dialogue that include this user and where the session was initiated with the public user identity currently registered, then the S-CSCF shall send a SIP BYE request destined for the called user and shall send a SIP BYE request destined for the calling user. Clause: 5.4.5.1.2A; 5.4.5.1.2 item 1 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 Registration of UE1 expires 2 BYE to UE1 Gm1 3 BYE to UE2 Request-URI stored Contact header from initial INVITE To header To header from 200 response From header From header from initial INVITE Call-ID header From header from initial INVITE CSeq header as stored for direction calling to called Route header as stored for dialog Reason header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 141
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.6 Target refresh request procedures
|
Test Purpose Identifier: TP_IMST2_MW_TAR_01 Summary: When a P-CSCF receives a target refresh request not relating to an existing dialogue from a UE, it shall answer the request by sending a SIP 403 (Forbidden) response back to the originator and not forward the request. Clause: 5.2.6.3.5 item 1a References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS IUT has not established an INVITE dialogue from UE1 to UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 target refresh UPDATE to UE2 Gm 2 || || target refresh UPDATE to IMS Mw 3 403 response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 142 Test Purpose Identifier: TP_IMST2_MW_TAR_02 Summary: When a P-CSCF receives a target refresh request from a UE, containing a list of URIs in the Route header different to the stored values of the Record-Route headers for the same dialog, then the P-CSCF shall either return a SIP 400 (Bad Request) response and not forward the request or replace the received Route header value in the request with the stored list of Record-Route headers for the same dialogue. Clause: 5.2.6.3.5 item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/24.6.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has stored Record-Route header of UE1 ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 target refresh INVITE to UE2 Route header not matching stored Record-Route header 2a || || INVITE Mw 3a 400 response Gm 2b INVITE Route header stored Record-Route header Mw 3b 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 143 Test Purpose Identifier: TP_IMST2_MW_TAR_03 Summary: When a P-CSCF receives a target refresh request from a UE, it shall add its own address to the Via header and to the Record-Route header, the P-CSCF SIP URI shall be built in a format that contains the port number of the P-CSCF where it awaits responses (in Via header) and subsequent requests (in Record-Route header) from the called party, and either the P-CSCF FQDN that resolves to the IP address or the P-CSCF IP address and updated access-network-charging-info parameter shall be included in the P-Charging-Vector header field. Clause: 5.2.6.3.5 items 1A,2,3; 5.2.9.1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 UE1 IMS IUT UE2 Step Direction Message IF 1 target refresh INVITE to UE2 2 INVITE Route header SIP URI of IMS P-CSCF Via header port number of IUT P-CSCF IP address of IUT P-CSCF or FQDN address of IUT P-CSCF Record-Route header SIP URI of IUT P-CSCF port number of IUT P-CSCF FQDN address of IUT P-CSCF or IP address of IUT P-CSCF P-Charging-Vector header updated access-network-charging-info parameter Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 144 Test Purpose Identifier: TP_IMST2_MW_TAR_04 Summary: If a security association exists between the UE and P-CSCF, when a P-CSCF receives any SIP 1xx or 2xx response as a result of a forwarded target refresh request, it shall replace the address and port number of its own Record Route entry to the same value as for the response to the initial request for the dialogue. Clause: 5.2.6.3.6 item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE1 has established a security association in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ IUT has received target refresh INVITE from UE1 ✓ IUT has sent target refresh INVITE via Mw UE1 IMS IUT UE2 Step Direction Message IF 1 200 response Mw 2 200 response to UE1 Record Route header of IUT P-CSCF same address same port number of IUT P-CSCF of response to initial INVITE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 145 Test Purpose Identifier: TP_IMST2_MW_TAR_04A Summary: If digest without TLS exists between UE and P-CSCF, when a P-CSCF receives any SIP 1xx or 2xx response as a result of a forwarded target refresh request, it shall forward target response. Clause: 5.2.6.3.6 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ IUT has received target refresh INVITE from UE1 ✓ IUT has sent target refresh INVITE via Mw UE1 IMS IUT UE2 Step Direction Message IF 1 200 response Mw 2 200 response to UE1 Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 146 Test Purpose Identifier: TP_IMST2_MW_TAR_05 Summary: When a P-CSCF receives a target refresh request for a dialogue destined for a UE it shall add its own address to the top of the received list of Via header in a format that if a security association exists between the UE and the P-CSCF, contains the protected server port number of the security association and either the P-CSCF FQDN that resolves to the IP address of the security association or the P-CSCF IP address of the security association. Clause: 5.2.6.4.5 item 1,3; 5.2.9.2 paragraph 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ UE1 has established a security association with IUT P- CSCF ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ IUT has received target refresh INVITE via Mw addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE via Gm to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 target refresh INVITE to UE1 Mw 2 target refresh INVITE to UE1 Via header port number of IUT P-CSCF for security association as topmost the IP address of IUT P-CSCF or the FQDN address of IUT P-CSCF Record-Route header as topmost the SIP URI of IUT P-CSCF Gm 3 100 response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 147 Test Purpose Identifier: TP_IMST2_MW_TAR_05A Summary: When a P-CSCF receives a target refresh request for a dialogue destined for a UE it shall add its own address to the top of the received list of Via header in a format that if digest without TLS exists between the UE and the P-CSCF. Clause: 5.2.6.4.5 item 2,4; 5.2.9.2 paragraph 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ ✓ IUT has established an INVITE dialogue from UE1 to UE2 ✓ ✓ IUT has received target refresh INVITE via Mw addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE via Gm to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 target refresh INVITE to UE1 Mw 2 target refresh INVITE to UE1 Via header port number of IUT P-CSCF as topmost the address of IUT P-CSCF Record-Route header as topmost the SIP URI of IUT P-CSCF Gm 3 100 response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 148 Test Purpose Identifier: TP_IMST2_MW_TAR_06 Summary: When a P-CSCF receives SIP 1xx or 2xx response to a target refresh request for a dialogue destined for the UE, if the list of Via headers does not match the saved list of Via headers received in the initial request corresponding to the same dialog, either discard the response or replace the Via header values with those received in the request. Clause: 5.2.6.4.6 first numbered list item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.7.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 ✓ IUT has stored Via header ✓ ✓ ✓ IUT has received target refresh INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 200 response Via header not matching stored Via header Gm 2a || || 200 response Mw 2b 200 response Via header stored Via header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 149 Test Purpose Identifier: TP_IMST2_MW_TAR_07 Summary: When a P-CSCF receives SIP 1xx or 2xx response to a target refresh request for a dialogue destined for the UE, if a security association exists, rewrite the address and port number of its own Record- Route entry to the same value as for the response to the initial request for the dialogue and remove the comp parameter and updated access-network-charging-info parameter shall be included in the P- Charging-Vector header field. Clause: 5.2.6.4.6 first numbered list item 2; 5.2.9.2 paragraph 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE1 has established a security association with IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 ✓ IUT has stored Record-Route header ✓ ✓ ✓ IUT has received target refresh INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 200 response Gm 2 200 response Record-Route header stored Record-Route header P-Charging-Vector header updated access-network-charging-info parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 150 Test Purpose Identifier: TP_IMST2_MW_TAR_07A Summary: When a P-CSCF receives SIP 1xx or 2xx response to a target refresh request for a dialogue destined for the UE, if a digest without TLS exists, updated access-network-charging-info parameter shall be included in the P-Charging-Vector header field. Clause: 5.2.6.4.6 first numbered list item 2; 5.2.9.2 paragraph 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 ✓ IUT has stored Record-Route header ✓ ✓ ✓ IUT has received target refresh INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 200 response Gm 2 200 response P-Charging-Vector header updated access-network-charging-info parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 151 Test Purpose Identifier: TP_IMST2_MW_TAR_08 Summary: When a P-CSCF receives any response other than the SIP 1xx or 2xx response to a target refresh request for a dialogue destined for the UE, if the list of Via headers does not match the saved list of Via headers received in the initial request corresponding to the same dialog, either discard the response or replace the Via header values with those received in the request. Clause: 5.2.6.4.6 second numbered list item 1 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1, A.3/25.8.1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 ✓ IUT has stored Via header ✓ ✓ ✓ IUT has received target refresh INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 4xx response Via header not matching stored Via header Gm 2a || || 4xx response Mw 2b 4xx response Via header stored Via header Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 152 Test Purpose Identifier: TP_IMST2_MW_TAR_09 Summary: When a P-CSCF receives any response other than the SIP 1xx or 2xx response to a target refresh request for a dialogue destined for a UE, if a security association exists, rewrite the address and port number of its own Record-Route entry to the IP address and the port number where it awaits subsequent requests from the calling party and remove the comp parameter. Clause: 5.2.6.4.6 second numbered list item 2 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE1 has established a security association with IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 ✓ ✓ ✓ IUT has received target refresh INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 4xx response Gm 2 4xx response Record-Route header IP address of IUT P-CSCF port number of IUT P-CSCF comp parameter Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 153 Test Purpose Identifier: TP_IMST2_MW_TAR_09A Summary: When a P-CSCF receives any response other than the SIP 1xx or 2xx response to a target refresh request for a dialogue destined for a UE, if digest without TLS exists, forward the response. Clause: 5.2.6.4.6 second numbered list References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT UE2 IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE2 registered in IMS ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE2 has established an INVITE dialogue with UE1 ✓ ✓ ✓ IUT has received target refresh INVITE via Mw originated by UE2 addressed to UE1 ✓ ✓ IUT has sent target refresh INVITE to UE1 UE1 IMS IUT UE2 Step Direction Message IF 1 4xx response Gm 2 4xx response Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 154
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.7 Emergency procedures
|
Test Purpose Identifier: TP_IMST2_MW_EME_01 Summary: When P-CSCF receives from an unregistered user an initial request other than a SIP REGISTER for a dialogue and the Request-URI contained in the request matches one of the emergency service identifiers, it shall insert an emergency service URN into the Request-URI field and select an E-CSCF and add the URI of the selected E-CSCF to the topmost Route header and continue with normal initial SIP request process procedure. Clause: 5.2.10.2 paragraph 1; 5.2.7.2 paragraph 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding UE1 not registered in IUT ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI matching an emergency service identifier 2 INVITE Request URI emergency service URN Route header topmost SIP URI of IUT E-CSCF Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 155 Test Purpose Identifier: TP_IMST2_MW_EME_02 Summary: When P-CSCF receives from an unregistered user an initial request other than a SIP REGISTER for a dialogue and the Request-URI contained in the request matches one of the emergency service identifiers, it shall insert an emergency service URN into the Request-URI field and select an E-CSCF and add the URI of the selected E-CSCF to the topmost Route header and continue with normal initial SIP request process procedure but without removing the P-Preferred-Identity header and inserting a P-Asserted-Identity header. Clause: 5.2.10.2 item 1,2,3,3A; 5.2.7.2 paragraph 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding UE1 not registered in IUT ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE P-Preferred-Identity header 2 INVITE P-Preferred-Identity header P-Asserted-Identity header Request-URI emergency service URN Route header topmost SIP URI of IUT E-CSCF P-Charging-Vector header icid parameter Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 156 Test Purpose Identifier: TP_IMST2_MW_EME_03 Summary: When a P-CSCF receives from a UE, that has previously registered specifically for emergency service, an initial request that is not a SIP REGISTER request, and the Request-URI contained in the request matches one of the emergency service identifiers, the P-CSCF shall include an emergency service URN in the Request-URI. Clause: 5.2.10.3 item 1; 5.2.7.2 paragraph 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered for emergency service in IUT ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI matching an emergency service identifier 2 INVITE Request-URI emergency service URN Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 157 Test Purpose Identifier: TP_IMST2_MW_EME_04 Summary: When a P-CSCF receives from a UE, that has previously registered specifically for emergency service, an initial request that is not a SIP REGISTER request, and the Request-URI contained in the request matches one of the emergency service identifiers the P-CSCF shall include an emergency service URN in the Request-URI and if the P-Preferred-Identity header is present and carries the registered emergency public user identity, remove that header and insert a P-Asserted-Identity header with the registered emergency public user identity a second P-Asserted-Identity header with the tel-URI associated with the registered emergency public user identity. Clause: 5.2.10.3 item 1,1C)i) ; 5.2.7.2 paragraph 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered for emergency service in IUT ✓ IUT has stored display name ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI matching an emergency service identifier P-Preferred-Identity header emergency public user identity 2 INVITE P-Preferred-Identity header P-Asserted-Identity header emergency public user identity second P-Asserted-Identity header tel URI of emergency public user identity Request-URI emergency service URN Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 158 Test Purpose Identifier: TP_IMST2_MW_EME_05 Summary: When a P-CSCF receives from a UE, that has previously registered specifically for emergency service, an initial request that is not a SIP REGISTER request, and the Request-URI contained in the request matches one of the emergency service identifiers, the P-CSCF shall include an emergency service URN in the Request-URI and if the P-Preferred-Identity header is present and carries the tel-URI associated with the registered emergency public user identity, remove that header and insert a P-Asserted-Identity header with the tel-URI associated with the registered emergency public user identity and a second P-Asserted-Identity header with the registered emergency public user identity. Clause: 5.2.10.3 item 1,1C)ii) ; 5.2.7.2 paragraph 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered for emergency service in IUT ✓ IUT has stored display name ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI matching an emergency service identifier P-Preferred-Identity header tel URI of emergency public user identity 2 INVITE P-Preferred-Identity header P-Asserted-Identity header emergency public user identity second P-Asserted-Identity header tel URI of emergency public user identity Request-URI emergency service URN Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 159 Test Purpose Identifier: TP_IMST2_MW_EME_06 Summary: When a P-CSCF receives target refresh request for an emergency dialogue with the Request-URI containing GRUU, it shall obtain the UE IP address and UE protected server port related to the GRUU contained in the Request-URI and rewrite the Request-URI with that UE IP address and UE protected server port. Clause: 5.2.10.3 last dashed list; 5.2.6.4.5 item 2,4 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered for emergency service in IUT ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions ✓ UE1 has established an emergency session UE1 IMS IUT Step Direction Message IF 1 target refresh INVITE Request-URI GRUU Gm 2 INVITE Request-URI UE1 IP address protected server port number Via header port number of IUT P-CSCF as topmost the address of IUT P-CSCF Record-Route header as topmost the SIP URI of IUT P-CSCF Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 160 Test Purpose Identifier: TP_IMST2_MW_EME_07 Summary: When a P-CSCF receives from a UE that has registered for non-emergency service an initial request that is not a SIP REGISTER request, and the Request-URI contained in the request matches one of the emergency service identifiers, the P-CSCF shall include an emergency service URN in the Request-URI field. Clause: 5.2.10.4 item 1; 5.2.7.2 paragraph 3 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ IUT has stored display name ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI matching an emergency service identifier 2 INVITE Request-URI emergency service URN Mw 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 161 Test Purpose Identifier: TP_IMST2_MW_EME_08 Summary: When a P-CSCF receives from a UE that has registered for non-emergency service an initial request that is not a SIP REGISTER request, and the Request-URI contained in the request matches one of the emergency service identifiers, if the public user identity included in the P-Preferred-Identity header matches one of the P-CSCFs registered public user identities remove the P-Preferred-Identity header from the received request, insert a P-Asserted-Identity header that includes the public user identity that was present in the P-Preferred-Identity header and add a second P-Asserted identity header that contains the tel URI associated with the public user identity. Clause: 5.2.10.4 item 1C)i) References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ IUT has stored display name ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI emergency service URN P-Preferred-Identity header registered public user identity Gm 2 INVITE P-Preferred-Identity header P-Asserted-Identity header registered public user identity second P-Asserted-Identity header tel URI of public user identity Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 162 Test Purpose Identifier: TP_IMST2_MW_EME_09 Summary: When a P-CSCF receives from a UE that has registered for non-emergency service an initial request that is not a SIP REGISTER request, and the Request-URI contained in the request matches one of the emergency service identifiers, if the tel URI associated with one of the registered public user identities is included in the P-Preferred-Identity header remove the P-Preferred-Identity header, insert a P-Asserted-Identity header that includes the tel URI that was present in the P-Preferred- Identity header and add a second P-Asserted-Identity header that contains a public user identity. Clause: 5.2.10.4 item 1C)ii) References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ IUT has stored display name ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI emergency service URN P-Preferred-Identity header tel URI of public user identity Gm 2 INVITE P-Preferred-Identity header P-Asserted-Identity header tel URI of public user identity second P-Asserted-Identity header registered public user identity Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 163 Test Purpose Identifier: TP_IMST2_MW_EME_10 Summary: When a P-CSCF receives for a user registered for non-emergency services a target refresh request for an emergency dialogue with the Request-URI containing GRUU, it shall obtain the UE IP address and UE protected server port related to the GRUU contained in the Request-URI and rewrite the Request-URI with that UE IP address and UE protected server port. Clause: 5.2.10.4 last dashed list; 5.2.6.4.5 item 2,4 References: - Config Ref: CF_1Mw1Gm IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured for emergency sessions ✓ UE1 has established an emergency session UE1 IMS IUT Step Direction Message IF 1 target refresh INVITE Request-URI GRUU Gm 2 INVITE Request-URI UE1 IP address protected server port number Via header port number of IUT P-CSCF as topmost the address of IUT P-CSCF Record-Route header as topmost the SIP URI of IUT P-CSCF Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 164 Test Purpose Identifier: TP_IMST2_MW_EME_11 Summary: A P-CSCF shall respond to a SIP INVITE request for an emergency session with a SIP 380 response if it is not capable of or not configured to handle the requested emergency sessions. Clause: 5.2.10.5 I) References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE1 visiting IMS IUT not configured for emergency sessions UE1 IMS IUT Step Direction Message IF 1 INVITE Request-URI emergency service URN Mw 2 380 response to UE1 Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 165
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.2.8 SDP procedures
|
Test Purpose Identifier: TP_IMST2_MW_SDP_01 Summary: When an S-CSCF receives a SIP request containing a SDP offer in which there are media parameters which are not permitted by local policy or by user subscription, it shall send a SIP 488 (Not Acceptable Here) response containing a SDP payload which contains all or an acceptable subset, of the media types, codecs and other SDP parameters permitted by local policy or user subscription. Clause: 6.3 paragraph 1 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ UE1 visiting IMS ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT Step Direction Message IF 1 INVITE to UE1 SDP offer unacceptable media parameter Mw 2 488 response SDP offer Mw ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 166 Test Purpose Identifier: TP_IMST2_MW_SDP_02 Summary: When an S-CSCF receives a SIP request containing an encrypted SDP offer, it may reject the request. Clause: 6.3 paragraph 1 References: - Config Ref: CF_1Mw IUT Role: IMS Selection Expression: PICS A.2/3, A.6/34.1.1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT configured with an entry point to IMS ✓ ✓ UE1 visiting IMS ✓ IUT configured to reject encrypted SDP offers UE1 IMS IUT Step Direction Message IF 1 INVITE to UE1 encrypted SDP offer Mw 2 4xx response Mw 3 || || INVITE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 167 Test Purpose Identifier: TP_IMST2_MW_SDP_03 Summary: When an P-CSCF receives a SIP request containing a SDP answer to a SDP offer which was contained in a previously forwarded SIP response, other than a SIP 200 (OK), the P-CSCF shall not examine the media parameters in the received SDP offer. Clause: 6.2 paragraph 2 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has received INVITE via Mw for UE1 ✓ IUT has sent INVITE via Gm ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT Step Direction Message IF 1 180 response to UE1 SDP offer unacceptable media parameter Mw 2 || || 4xx response Mw 3 180 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 168 Test Purpose Identifier: TP_IMST2_MW_SDP_04 Summary: When a P-CSCF receives a SIP ACK request containing an SDP answer in response to a SDP offer which was previously forwarded in a SIP 200 (OK) response and which contained media parameters not permitted by local policy, it shall terminate the session. Clause: 6.2 paragraph 3 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has received INVITE via Mw for UE1 ✓ ✓ IUT has sent INVITE via Gm to UE1 ✓ ✓ IUT configured with an entry point to IMS UE1 IMS IUT Step Direction Message IF 1 200 response SDP offer unacceptable media parameter Gm 2 200 response Mw 3 ACK SDP answer Mw 4 BYE Mw 5 BYE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 169 Test Purpose Identifier: TP_IMST2_MW_SDP_05 Summary: When a P-CSCF receives a SIP ACK request containing an SDP answer in response to an encrypted SDP offer which was previously forwarded in a SIP 200 (OK) response, it may terminate the session. Clause: 6.2 paragraph 3 References: - Config Ref: CF_1Gm1Mw IUT Role: IMS Selection Expression: PICS A.2/1, A.3/30.3.1 Entities Condition UE1 IMS IUT IUT not configured for topology hiding ✓ ✓ UE1 registered in IUT ✓ ✓ IUT has received INVITE via Mw for UE1 ✓ ✓ IUT has sent INVITE via Gm to UE1 ✓ ✓ IUT configured with an entry point to IMS ✓ IUT configured to reject encrypted SDP offers UE1 IMS IUT Step Direction Message IF 1 200 response encrypted SDP offer Gm 2 200 response Mw 3 ACK encrypted SDP answer Mw 4 BYE Mw 5 BYE Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 170
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.3 Test purposes for the Ic interface
| |
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.3.1 General
|
Test Purpose Identifier: TP_IMST2_IC_GEN_01 Summary: When an IBCF receives SIP REGISTER request from within its own network, it shall add its own routable SIP URI to the top of the Path header. Clause: 5.10.2.1 1) and 2), 5.10.4.1 References: Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured with one entry point to home network UE1 IUT IMS Step Direction Message IF 1 REGISTER 2 REGISTER topmost Path header SIP URI of IUT IBCF Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 171
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.3.2 Registration procedures
|
Test Purpose Identifier: TP_IMST2_IC_REG_01 Summary: When an IBCF receives a SIP 3xx (Redirection) response from a home network entry point to a previously forwarded SIP REGISTER request, it shall resend the Register request to another home network entry point to which it has not previously forwarded the same request. Clause: 5.10.2.1 3) second dash References: - Config Ref: CF_2Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured with two entry points to home network ✓ ✓ IUT has received REGISTER from UE1 ✓ IUT has sent REGISTER via Ic1 UE1 IUT IMS Step Direction Message IF 1 3xx response Ic1 2 REGISTER Ic2 Test Purpose Identifier: TP_IMST2_IC_REG_02 Summary: When an IBCF receives SIP 480 (Temporarily Unavailable) response from a home network entry point to a previously forwarded SIP REGISTER request, it shall forward the Register request to another home network entry point to which it has not previously forwarded the same request. Clause: 5.10.2.1 3) second dash References: - Config Ref: CF_2Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured with two entry points to home network ✓ ✓ IUT has received REGISTER from UE1 ✓ IUT has sent REGISTER via Ic1 UE1 IUT IMS Step Direction Message IF 1 480 response Ic1 2 REGISTER Ic2 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 172 Test Purpose Identifier: TP_IMST2_IC_REG_03 Summary: When ran IBCF receives no response from a home network entry point to a previously forwaded SIP REGISTER request, it shall forward the Register request to another home network entry point to which it has not previously forwarded the same request. Clause: 5.10.2.1 3) first dash References: - Config Ref: CF_2Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured with two entry points to home network ✓ ✓ IUT has received REGISTER from UE1 ✓ IUT has sent REGISTER via Ic1 UE1 IUT IMS Step Direction Message IF 1 || || no response Ic1 2 REGISTER Ic2 Test Purpose Identifier: TP_IMST2_IC_REG_04 Summary: If an IBCF receives a SIP 3xx (Redirection) response to a SIP REGISTER request from all entry points in the registering user s home network, it shall send a SIP 504 (Server Time-Out) response to the P-CSCF. Clause: 5.10.2.1 3) second dash References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured with one entry point to home network ✓ ✓ IUT has received REGISTER from UE1 UE1 IUT IMS Step Direction Message IF 1 3xx response Ic1 2a 408 response 2b 504 response ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 173 Test Purpose Identifier: TP_IMST2_IC_REG_05 Summary: If an IBCF receives a SIP 480 (Temporarily Unavailable) response to a SIP REGISTER request from all entry points in the registering user s home network, it shall send a SIP 504 (Server Time-Out) response to the P-CSCF. Clause: 5.10.2.1 3) second dash References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured with one entry point to home network ✓ ✓ IUT has received REGISTER from UE1 UE1 IUT IMS Step Direction Message IF 1 480 response Ic1 2a 408 response 2b 504 response Test Purpose Identifier: TP_IMST2_IC_REG_06 Summary: If an IBCF receives no response to a SIP REGISTER request from all entry points in the registering user s home network, it shall send a SIP 504 (Server Time-Out) response to the P-CSCF. Clause: 5.10.2.1 3) first dash References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured with one entry point to home network ✓ ✓ IUT has received REGISTER from UE1 UE1 IUT IMS Step Direction Message IF 1 || || no response Ic1 2a 408 response 2b 504 response ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 174 Test Purpose Identifier: TP_IMST2_IC_REG_07 Summary: When an IBCF receives a SIP REGISTER request from an non-trusted domain outside its own network, it shall send a SIP 403 (Forbidden) response to the sender of the request. Clause: 5.10.3.1 1) References: - Config Ref: CF_1Ic IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ ✓ IMS configured as untrusted domain for IUT UE1 IUT IMS Step Direction Message IF 1 REGISTER Ic1 2 403 response Ic1
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.3.3 Initial request procedures
|
Test Purpose Identifier: TP_IMST2_IC_INI_01 Summary: When an IBCF receives an initial SIP INVITE request from within its own network it encrypts all Via header URIs except the one of the IBCF prior to forwarding the request. Clause: 5.10.2.2 1) 3) 8), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ UE1 registered in IUT UE1 IUT IMS Step Direction Message IF 1 INVITE 2 100 response 3 INVITE topmost Via header SIP URI of IUT IBCF encrypted SIP URI tokenized-by parameter P-Charging-Function-Addresses header Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 175 Test Purpose Identifier: TP_IMST2_IC_INI_02 Summary: When an IBCF receives a 180 response to a forwarded initial INVITE request and network topology hiding is required it shall not encrypt Via header URIs when forwarding to the UE. Clause: 5.10.2.2, 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has received INVITE from UE1 ✓ IUT has sent INVITE via Ic1 UE1 IUT IMS Step Direction Message IF 1 180 response Ic1 2 180 response any header encrypted SIP URI tokenized-by parameter Test Purpose Identifier: TP_IMST2_IC_INI_03 Summary: When an IBCF receives a 200 response to a forwarded initial INVITE request and network topology hiding is required it shall not encrypt Via header URIs when forwarding to the UE. Clause: 5.10.2.2, 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has received INVITE from UE1 ✓ IUT has sent INVITE via Ic1 UE1 IUT IMS Step Direction Message IF 1 200 response Ic1 2 200 response any header encrypted SIP URI tokenized-by parameter ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 176 Test Purpose Identifier: TP_IMST2_IC_INI_04 Summary: When an IBCF receives any SIP request, other than a SIP REGISTER request, from a non-trusted domain and the topmost Route header in the request contains the orig parameter, the IBCF shall send a SIP 403 (Forbidden) response to the originator of the request. Clause: 5.10.3.2, second dashed list, second dash References: - Config Ref: CF_1Ic IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition IUT IMS ✓ ✓ IMS configured as untrusted domain for IUT IUT IMS Step Direction Message IF 1 INVITE topmost Route header orig parameter Ic1 2 403 response Ic1 Test Purpose Identifier: TP_IMST2_IC_INI_05 Summary: When an IBCF receives a SIP INVITE request from a trusted domain outside its own network, it shall return a SIP 100 response and not encrypt Via header URIs when forwarding to the UE. Clause: 5.10.3.2 1) 3), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IMS configured as trusted domain for IUT UE1 IUT IMS Step Direction Message IF 1 INVITE Via header topmost SIP URI of IMS encrypted SIP URI tokenized-by parameter Ic1 2 100 response Ic1 3 INVITE any header encrypted SIP URI tokenized-by parameter ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 177 Test Purpose Identifier: TP_IMST2_IC_INI_06 Summary: When the IBCF receives an INVITE request and the IBCF requires the periodic refreshment of the session it shall add a Session-Expires prior to forwarding it to the UE. Clause: 5.10.3.2, RFC 4028 [8] References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4, A.8/10.3.1 Entities Condition UE1 IUT IMS ✓ IUT configured for requiring periodic refreshment UE1 IUT IMS Step Direction Message IF 1 INVITE Ic1 2 INVITE Session-Expires header Test Purpose Identifier: TP_IMST2_IC_INI_07 Summary: When an IBCF receives a valid 180 response from within its own network it shall remove the P-Charging-Function-Addresses header and add its own URI as the topmost Via header and encrypt all other Via header prior to forwarding the response to other networks. Clause: 5.10.3.2 second numbered list, 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT has received INVITE via Ic1 ✓ ✓ IUT has sent INVITE to UE1 UE1 IUT IMS Step Direction Message IF 1 180 response 2 180 response topmost Via header SIP URI of IUT IBCF encrypted SIP URI tokenized-by parameter P-Charging-Function-Addresses header Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 178 Test Purpose Identifier: TP_IMST2_IC_INI_08 Summary: When an IBCF receives a valid 200 response from within its own network it shall remove the P-Charging-Function-Addresses header and add its own URI as the topmost Via header and encrypt all other Via header prior to forwarding the response to other networks. Clause: 5.10.3.2, second numbered list, 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT has received INVITE via Ic1 ✓ ✓ IUT has sent INVITE to UE1 UE1 IUT IMS Step Direction Message IF 1 200 response 2 200 response topmost Via header SIP URI of IUT IBCF encrypted SIP URI tokenized-by parameter P-Charging-Function-Addresses header Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 179 Test Purpose Identifier: TP_IMST2_IC_INI_09 Summary: When an IBCF processes a SIP request or response that contains a contact address which is a Globally Routable User agent URI (GRUU), it shall replace the contact address with an address which is also a GRUU. Clause: 5.10.5, paragraph 4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT has received INVITE via Ic1 containing Contact header indicating GRUU ✓ ✓ IUT has sent INVITE to UE1 containing Contact header indicating GRUU configured for IMS-ALG UE1 IUT IMS Step Direction Message IF 1 200 response 2 200 response Contact header GRUU Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 180
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.3.4 Standalone requests procedures
|
Test Purpose Identifier: TP_IMST2_IC_STA_01 Summary: When an IBCF receives an initial SIP request other than a SIP REGISTER or SIP INVITE from within its own network, it shall add its own URI as the topmost Via header and encrypt all other Via header and exclude charging related headers prior to forwarding the request to other networks. Clause: 5.10.2.2 3) 8), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ UE1 registered in IUT UE1 IUT IMS Step Direction Message IF 1 MESSAGE 2 MESSAGE topmost Via header SIP URI of IUT IBCF encrypted SIP URI tokenized-by parameter P-Charging-Function-Addresses header Ic1 Test Purpose Identifier: TP_IMST2_IC_STA_02 Summary: When the IBCF receives an INVITE request and the IBCF requires the periodic refreshment of the session it shall add a Session-Expires prior to forwarding it to other networks. Clause: 5.10.2.2, RFC 4028 [8] References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4, A.8/9.3.1 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ IUT configured for requiring periodic refreshment ✓ ✓ UE1 registered in IUT UE1 IUT IMS Step Direction Message IF 1 INVITE 2 INVITE Session-Expires header Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 181 Test Purpose Identifier: TP_IMST2_IC_STA_03 Summary: When an IBCF receives a SIP request, other than a SIP REGISTER request or a SIP INVITE request, from a trusted domain outside its own network it shall decrypt all encrypted Via headers prior to forwarding the request to the UE. Clause: 5.10.3.2 3), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IMS configured as trusted domain for IUT UE1 IUT IMS Step Direction Message IF 1 MESSAGE topmost Via header SIP URI of IMS encrypted SIP URI tokenized-by parameter Ic1 2 MESSAGE any header encrypted SIP URI tokenized-by parameter Test Purpose Identifier: TP_IMST2_IC_STA_04 Summary: The IBCF shall handle requests addressed to its currently valid GRUUs when received outside of the dialogue in which the GRUU was provided. Clause: 5.10.5 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for IMS-ALG UE1 IUT IMS Step Direction Message IF 1 MESSAGE To header GRUU of IUT IBCF Ic1 2 MESSAGE ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 182
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.3.5 Subsequent requests on a dialogue procedures
|
Test Purpose Identifier: TP_IMST2_IC_SUB_01 Summary: When an IBCF receives an SIP BYE request from within its own network and subsequent to an initial request it shall add its own URI as the topmost Via header and encrypt all other Via header prior to forwarding the request to other networks. Clause: 5.10.2.3 3) 4), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has established an INVITE dialogue for UE1 UE1 IUT IMS Step Direction Message IF 1 BYE 2 BYE topmost Via header SIP URI of IUT IBCF encrypted SIP URI tokenized-by parameter Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 183 Test Purpose Identifier: TP_IMST2_IC_SUB_02 Summary: When an IBCF receives a response from outside its own network to a request forwarded subsequent to an initial request and network topology hiding is required is shall not encrypt any headers prior to forwarding the response to the UE. Clause: 5.10.2.3, 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has established an INVITE dialogue for UE1 ✓ ✓ IUT has received BYE from UE1 ✓ IUT has sent BYE via Ic1 UE1 IUT IMS Step Direction Message IF 1 200 response Ic1 2 200 response any header encrypted SIP URI tokenized-by parameter ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 184 Test Purpose Identifier: TP_IMST2_IC_SUB_03 Summary: When an IBCF receives a SIP MESSAGE request from outside its own network subsequent to an initial request, then it shall decrypt any headers prior to forwarding the request to the UE. Clause: 5.10.3.3 3) 4), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has established an INVITE dialogue for UE1 UE1 IUT IMS Step Direction Message IF 1 MESSAGE topmost Via header SIP URI of IMS encrypted SIP URI tokenized-by parameter Ic1 2 MESSAGE any header encrypted SIP URI tokenized-by parameter ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 185 Test Purpose Identifier: TP_IMST2_IC_SUB_04 Summary: When an IBCF receives a SIP BYE request from outside its own network subsequent to an initial request, then it shall decrypt any headers prior to forwarding the request to the UE. Clause: 5.10.3.3 3) 4), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has established an INVITE dialogue for UE1 UE1 IUT IMS Step Direction Message IF 1 BYE topmost Via header SIP URI of IMS encrypted SIP URI tokenized-by parameter Ic1 2 BYE any header encrypted SIP URI tokenized-by parameter ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 186 Test Purpose Identifier: TP_IMST2_IC_SUB_05 Summary: When an IBCF receives a SIP 200 response from within its own network to a SIP request forwarded subsequent to an initial request it shall add its own URI to the Via header and encrypt all other Via headers prior to forwarding the response to other networks. Clause: 5.10.3.3, 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has established an INVITE dialogue for UE1 ✓ IUT has received BYE via Ic1 ✓ ✓ IUT has sent BYE to UE1 UE1 IUT IMS Step Direction Message IF 1 200 response 2 200 response topmost Via header SIP URI of IUT IBCF encrypted SIP URI tokenized-by parameter Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 187
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.3.6 Target refresh request procedures
|
Test Purpose Identifier: TP_IMST2_IC_TAR_01 Summary: When an IBCF receives a target refresh request from within its own network it shall respond with a SIP 100 response, add its own URI to the Via header and encrypt all other Via headers prior to forwarding the request to other networks. Clause: 5.10.2.3 1) 2) 4), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has established an INVITE dialogue for UE1 UE1 IUT IMS Step Direction Message IF 1 target refresh INVITE 2 100 response 3 target refresh INVITE topmost Via header SIP URI of IUT IBCF encrypted SIP URI tokenized-by parameter Ic1 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 188 Test Purpose Identifier: TP_IMST2_IC_TAR_02 Summary: When an IBCF receives a target refresh request from outside its own network subsequent to an initial request it shall decrypt all headers before forwarding it to the UE. Clause: 5.10.3.3 1) 2) 4), 5.10.4 References: - Config Ref: CF_1Ic1Gm IUT Role: IMS Selection Expression: PICS A.2/4 Entities Condition UE1 IUT IMS ✓ IUT configured for topology hiding ✓ ✓ IUT has established an INVITE dialogue for UE1 UE1 IUT IMS Step Direction Message IF 1 target refresh INVITE topmost Via header SIP URI of IMS encrypted SIP URI tokenized-by parameter Ic1 2 100 response Ic1 3 target refresh INVITE any header encrypted SIP URI tokenized-by parameter ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 189
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.4 Test purposes for the ISC interface
| |
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.4.1 General
|
Test Purpose Identifier: TP_IMST2_ISC_GEN_01 Summary: SIP MESSAGE requests that are exchanged between the S-CSCF and any AS based on initial filter criteria shall include the type 3 inter operator identifier (IOI). Clause: 4.5.4, paragraph 4 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ IUT configured with an iFC designed to contact AS1 for MESSAGE UE1 IUT AS1 UE2 Step Direction Message IF 1 MESSAGE 2 MESSAGE P-Charging-Vector header ioi parameter type3 ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 190 Test Purpose Identifier: TP_IMST2_ISC_GEN_02 Summary: Responses to SIP MESSAGE requests that are exchanged between the S-CSCF and any AS shall include the type 3 inter operator identifier (IOI). Clause: 4.5.4, paragraph 4 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 ✓ ✓ IUT configured with an iFC designed to contact AS1 for MESSAGE ✓ ✓ IUT has sent MESSAGE to AS1 via ISC ✓ ✓ IUT has sent MESSAGE to UE2 via GM ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 200 response 2 200 response P-Charging-Vector header ioi parameter type3 ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 191 Test Purpose Identifier: TP_IMST2_ISC_GEN_03 Summary: SIP MESSAGE requests that are exchanged between the I-CSCF and any AS shall include the type 3 inter operator identifier (IOI). Clause: 4.5.4, paragraph 4 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/2 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for forwarding MESSAGE directly to AS1 UE1 IUT AS1 UE2 Step Direction Message IF 1 MESSAGE 2 MESSAGE P-Charging-Vector header ioi parameter type3 ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 192
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.4.2 Registration procedures
|
Test Purpose Identifier: TP_IMST2_ISC_REG_01 Summary: An IMS shall support 3rd-party registration or registration with the AS in the same trust domain (initial registration and user-initiated reregistration). Clause: 5.4.1.7, paragraph 1 References: - Config Ref: CF_1Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE1not registered in IUT ✓ IUT configured for establishing security association ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has initiated security association establishment ✓ ✓ IUT configured with an iFC designed to contact AS1 for REGISTER ✓ ✓ AS1 configured for being in the same trust domain as IUT UE1 IUT AS1 Step Direction Message IF 1 protected REGISTER 2 REGISTER P-Access-Network-Info header P-Visited-Network-ID header Request-URI SIP URI of AS1 To header a non barred IMPU from the service profile of the processed iFC From header SIP URI of IUT S-CSCF Contact header SIP URI of IUT S-CSCF P-Charging-Vector header a type3 orig-ioi parameter before the received orig-ioi parameters P-Charging-Function-Addresses header ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 193 Test Purpose Identifier: TP_IMST2_ISC_REG_02 Summary: An IMS shall support 3rd-party registration or registration with the AS outside the trust domain (initial registration and user-initiated reregistration). Clause: 5.4.1.7, paragraph 1 References: - Config Ref: CF_1Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE1 not registered in IUT ✓ IUT configured for establishing security association ✓ UE1 has sent unprotected REGISTER and has received 401 response ✓ UE1 has initiated security association establishment ✓ ✓ IUT configured with an iFC designed to contact AS1 for REGISTER AS1 not configured for being in the same trust domain as IUT UE1 IUT AS1 Step Direction Message IF 1 protected REGISTER 2 REGISTER P-Access-Network-Info header P-Visited-Network-ID header Request-URI SIP URI of AS1 To header a non barred IMPU from the service profile of the processed iFC From header SIP URI of IUT S-CSCF Contact header SIP URI of IUT S-CSCF P-Charging-Vector header a type3 orig-ioi parameter before the received orig-ioi parameters ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 194 Test Purpose Identifier: TP_IMST2_ISC_REG_03 Summary: An IMS shall support 3rd-party deregistration with the AS in the same trust domain. Clause: 5.4.1.7, paragraph 1 References: - Config Ref: CF_1Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 ✓ ✓ UE1 registered in IUT ✓ ✓ IUT configured with an entry point to AS1 ✓ ✓ IUT configured with an iFC designed to contact AS1 for REGISTER ✓ ✓ AS1 configured for being in the same trust domain as IUT UE1 IUT AS1 Step Direction Message IF 1 protected REGISTER Expires header 0 2 REGISTER P-Access-Network-Info header P-Visited-Network-ID header Request-URI SIP URI of AS1 To header a non barred IMPU from the service profile of the processed iFC From header SIP URI of IUT S-CSCF Contact header SIP URI of IUT S-CSCF ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 195
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.4.3 Initial request procedures
|
Test Purpose Identifier: TP_IMST2_ISC_INI_01 Summary: When S-CSCF receives any 1xx or 2xx response for a UE subsequent to the initial SIP INVITE then it forwards it towards an AS inside the home network of the S-CSCF. Clause: 5.4.4.2.2, paragraph 1 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 ✓ ✓ IUT has sent INVITE to AS1 via ISC ✓ ✓ AS1 configured for being within same IMS network as IUT ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 180 response 2 180 response P-Charging-Function-Addresses header ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 196 Test Purpose Identifier: TP_IMST2_ISC_INI_02 Summary: When S-CSCF receives any 1xx or 2xx response for a UE subsequent to the initial SIP INVITE then it forwards it towards an AS inside the home network of the S-CSCF. Clause: 5.4.4.2.2, paragraph 1 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 ✓ ✓ IUT has sent INVITE to AS1 via ISC ✓ ✓ AS1 configured for being within same IMS network as IUT ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 200 response 2 200 response P-Charging-Function-Addresses header ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 197 Test Purpose Identifier: TP_IMST2_ISC_INI_03 Summary: When S-CSCF receives 180 response for a UE subsequent to the initial SIP INVITE then it forwards it towards an AS outside the home network of the S-CSCF. Clause: 5.4.4.2.2, paragraph 2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 AS1not configured for being within same IMS network as IUT S-CSCF ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 180 response P-Charging-Vector header access-network-charging-info parameter 2 180 response P-Charging-Vector header access-network-charging-info parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 198 Test Purpose Identifier: TP_IMST2_ISC_INI_04 Summary: When S-CSCF receives SIP 200 response for a UE subsequent to the initial SIP INVITE then it forwards it towards an AS outside the home network of the S-CSCF. Clause: 5.4.4.2.2, paragraph 2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ IUT has received INVITE from UE1 ✓ ✓ IUT has sent INVITE to UE2 ✓ ✓ IUT has sent INVITE to AS1 via ISC AS1 not configured for being within same IMS network as IUT S-CSCF ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 200 response P-Charging-Vector header access-network-charging-info parameter 2 200 response P-Charging-Vector header access-network-charging-info parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 199 Test Purpose Identifier: TP_IMST2_ISC_INI_05 Summary: When S-CSCF receives no SIP response from the AS for an SIP INVITE request and the iFC has default handling set to SESSION_TERMINATED then it does not forward the request to another AS and returns a SIP 408 response to the originating UE. Clause: 5.4.3.2, fifth paragraph after the first numbered list 14) References: - Config Ref: CF_2Gm2ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 AS2 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received INVITE from UE1 addressed to UE2 ✓ ✓ IUT has sent INVITE to AS1 via ISC1 ✓ ✓ IUT configured with an iFC1 designed to contact AS1 for the INVITE iFC1 has default handling set to SESSION TERMINATED ✓ ✓ IUT configured with an iFC2 designed to contact AS2 for INVITE iFC1 has greater priority than iFC2 UE1 IUT AS1 AS2 UE2 Step Direction Message IF 1 || || no response ISC1 2 408 response 3 || || INVITE ISC2 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 200
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.4.4 Standalone requests procedures
|
Test Purpose Identifier: TP_IMST2_ISC_STA_01 Summary: When the S-CSCF receives a SIP MESSAGE request it forwards the request to an AS within the same trust domain as the IUT. Clause: 5.4.3.2 first numbered list 5) References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 ✓ ✓ UE1 registered in IUT ✓ ✓ AS1 configured for being in the same trust domain as IUT ✓ ✓ IUT configured with an iFC designed to contact AS1 for MESSAGE UE1 IUT AS1 Step Direction Message IF 1 MESSAGE 2 MESSAGE P-Asserted-Service header topmost Route header SIP URI of AS1 second Route header SIP URI of IUT S-CSCF P-Charging-Vector header type3 orig-ioi parameter before the received orig-ioi parameters ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 201 Test Purpose Identifier: TP_IMST2_ISC_STA_02 Summary: When S-CSCF receives 5xx from the AS for a SIP MESSAGE request and the iFC has set to SESSION_CONTINUED then it forwards the request to a second AS. Clause: 5.4.3.2, fifth paragraph after the first numbered list 14) References: - Config Ref: CF_2Gm2ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 AS2 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 ✓ ✓ IUT has sent MESSAGE to AS1 via ISC1 ✓ ✓ IUT configured with an iFC1 designed to contact AS1 for the MESSAGE iFC1 has default handling set to SESSION CONTINUED iFC1 has no default handling ✓ ✓ IUT configured with an iFC2 designed to contact AS2 for MESSAGE iFC1 has greater priority than iFC2 UE1 IUT AS1 AS2 UE2 Step Direction Message IF 1 5xx response ISC1 2 MESSAGE ISC2 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 202 Test Purpose Identifier: TP_IMST2_ISC_STA_03 Summary: When S-CSCF receives 408 response from the AS for a SIP MESSAGE request and the iFC has set to SESSION_CONTINUED then it forwards the request to a second AS. Clause: 5.4.3.2, fifth paragraph after the first numbered list 14) References: - Config Ref: CF_2Gm2ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 AS2 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 ✓ ✓ IUT has sent MESSAGE to AS1 via ISC1 ✓ ✓ IUT configured with an iFC1 designed to contact AS1 for the MESSAGE (iFC1 has default handling set to SESSION CONTINUED iFC1 has no default handling) ✓ ✓ IUT configured with an iFC2 designed to contact AS2 for MESSAGE iFC1 has greater priority than iFC2 UE1 IUT AS1 AS2 UE2 Step Direction Message IF 1 408 response ISC1 2 MESSAGE ISC2 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 203 Test Purpose Identifier: TP_IMST2_ISC_STA_04 Summary: When S-CSCF receives no SIP response from the AS for a SIP MESSAGE request and the iFC has set to SESSION_CONTINUED then it forwards the request to a second AS. Clause: 5.4.3.2, fifth paragraph after the first numbered list 14) References: - Config Ref: CF_2Gm2ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 AS2 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 ✓ ✓ IUT has sent MESSAGE to AS1 via ISC1 ✓ ✓ IUT configured with an iFC1 designed to contact AS1 for the MESSAGE (iFC1 has default handling set to SESSION CONTINUED iFC1 has no default handling) ✓ ✓ IUT configured with an iFC2 designed to contact AS2 for MESSAGE iFC1 has greater priority than iFC2 UE1 IUT AS1 AS2 UE2 Step Direction Message IF 1 || || no response ISC1 2 MESSAGE ISC2 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 204 Test Purpose Identifier: TP_IMST2_ISC_STA_05 Summary: When S-CSCF receives 5xx response from the AS for a SIP MESSAGE request and the iFC has default handling set to SESSION_TERMINATED then it returns the response to the UE and does not forward the request to a second AS. Clause: 5.4.3.2, fifth paragraph after the first numbered list 14) References: - Config Ref: CF_2Gm2ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 AS2 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 ✓ ✓ IUT has sent MESSAGE to AS1 via ISC1 ✓ ✓ IUT configured with an iFC1 designed to contact AS1 for the MESSAGE iFC1 has default handling set to SESSION TERMINATED ✓ ✓ IUT configured with an iFC2 designed to contact AS2 for MESSAGE iFC1 has greater priority than iFC2 UE1 IUT AS1 AS2 UE2 Step Direction Message IF 1 5xx response ISC1 2 5xx response 3 || || MESSAGE ISC2 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 205 Test Purpose Identifier: TP_IMST2_ISC_STA_06 Summary: When S-CSCF receives 408 response from the AS for a SIP MESSAGE request and the iFC has default handling set to SESSION_TERMINATED then it returns the response to the UE and does not forward the request to a second AS. Clause: 5.4.3.2, fifth paragraph after the first numbered list 14) References: - Config Ref: CF_2Gm2ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 AS2 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 ✓ ✓ IUT has sent MESSAGE to AS1 via ISC1 ✓ ✓ IUT configured with an iFC1 designed to contact AS1 for the MESSAGE iFC1 has default handling set to SESSION TERMINATED ✓ ✓ IUT configured with an iFC2 designed to contact AS2 for MESSAGE iFC1 has greater priority than iFC2 UE1 IUT AS1 AS2 UE2 Step Direction Message IF 1 408 response ISC1 2 408 response 3 || || MESSAGE ISC2 ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 206 Test Purpose Identifier: TP_IMST2_ISC_STA_07 Summary: When S-CSCF receives a SIP 200 response from the AS for a SIP MESSAGE request then it forwards it to the UE. Clause: 5.4.3.2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 ✓ ✓ IUT configured with an iFC designed to contact AS1 for the MESSAGE ✓ ✓ IUT has sent MESSAGE to AS1 via ISC UE1 IUT AS1 UE2 Step Direction Message IF 1 200 response ISC 2 200 response ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 207 Test Purpose Identifier: TP_IMST2_ISC_STA_08 Summary: S-CSCF forwards to an Application Server (AS) the response to a SIP MESSAGE request from a served user or from a PSI that initiated the standalone transaction. Clause: 5.4.3.2, fifth paragraph after the first numbered list 14) References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received MESSAGE from UE1 addressed to UE2 containing the type3 orig-ioi parameter ✓ ✓ IUT has sent MESSAGE to UE2 via GM ✓ ✓ IUT has sent MESSAGE to AS1 via ISC ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 200_response 2 200_response P-Charging-Vector header type3 orig-ioi parameter from the initial MESSAGE type3 term-ioi parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 208 Test Purpose Identifier: TP_IMST2_ISC_STA_09 Summary: When a S-CSCF receives a SIP MESSAGE request destined for an unregistered user it forwards the request to the AS. Clause: 5.4.3.3 References: - Config Ref: CF_1Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ UE1 registered in IUT UE2 not registered in IUT ✓ ✓ IUT configured with an iFC designed to contact AS1 for MESSAGE UE1 IUT AS1 UE2 Step Direction Message IF 1 MESSAGE 2 MESSAGE ISC Test Purpose Identifier: TP_IMST2_ISC_STA_10 Summary: When the I-CSCF receives a SIP MESSAGE request containing P-Charging-Vector header including icid parameter it forwards it to the AS. Clause: 5.3.2.1, paragraph 2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for forwarding MESSAGE directly to AS1 UE1 IUT AS1 UE2 Step Direction Message IF 1 MESSAGE P-Charging-Vector header icid parameter 2 MESSAGE P-Charging-Vector header icid parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 209 Test Purpose Identifier: TP_IMST2_ISC_STA_11 Summary: When the I-CSCF receives a SIP MESSAGE request containing P-Charging-Vector header not including icid parameter then it adds this parameter prior to forwarding it to the AS. Clause: 5.3.2.1, paragraph 2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ IUT configured for forwarding MESSAGE directly to AS1 UE1 IUT AS1 UE2 Step Direction Message IF 1 MESSAGE P-Charging-Vector header icid parameter 2 MESSAGE P-Charging-Vector header icid parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 210 6.3.5 Subsequent requests on a dialogue procedures Test Purpose Identifier: TP_IMST2_ISC_SUB_01 Summary: When S-CSCF receives a SIP ACK request then it forwards it to an AS outside the trusted domain. Clause: 5.4.3.2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received INVITE from UE1 addressed to UE2 ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ IUT has sent INVITE to UE2 via GM ✓ ✓ IUT has sent INVITE to AS1 via ISC ✓ ✓ IUT has received 200 response from UE2 ✓ ✓ IUT has sent 200 response to UE1 AS1 not configured for being in the same trust domain as IUT ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 ACK 2 ACK P-Access-Network-Info header P-Charging-Vector header access-network-charging-info parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 211
|
45f119e1872981dca66af2d068b9278b
|
102 790-2
|
6.4.6 Target refresh request procedures
|
Test Purpose Identifier: TP_IMST2_ISC_TAR_01 Summary: When S-CSCF receives from the served user a target refresh request for a dialogue then it forwards it to an AS outside the trusted domain and returns a 100 response to the UE. Clause: 5.4.3.2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ ✓ IUT has received INVITE from UE1 addressed to UE2 ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ IUT has sent INVITE to UE2 via GM ✓ ✓ IUT has sent INVITE to AS1 via ISC AS1 not configured for being in the same trust domain as IUT ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT UE1 IUT AS1 UE2 Step Direction Message IF 1 target refresh INVITE 2 INVITE P-Access-Network-Info header P-Charging-Vector header access-network-charging-info parameter ISC 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 212 Test Purpose Identifier: TP_IMST2_ISC_TAR_02 Summary: When S-CSCF receives a SIP reINVITE request from a UE within an established dialogue then it forwards it to an AS inside the home network of the S-CSCF and returns a 100 response to the UE. Clause: 5.4.3.2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ ✓ UE1 and UE2 registered in IUT ✓ ✓ ✓ IUT has received INVITE from UE1 addressed to UE2 - - INVITE ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ IUT has sent INVITE to UE2 via GM ✓ ✓ IUT has sent INVITE to AS1 via ISC ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT ✓ AS1 configured for being within same IMS network as IUT S-CSCF UE1 IUT AS1 UE2 Step Direction Message IF 1 target refresh INVITE 2 INVITE P-Access-Network-Info header P-Charging-Vector header access-network-charging-info parameter ISC 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 213 Test Purpose Identifier: TP_IMST2_ISC_TAR_03 Summary: When the S-CSCF receives a SIP reINVITE request from a UE within an established dialogue then it forwards it to an AS outside the home network of the S-CSCF without charging information and returns a 100 response to the originating UE. Clause: 5.4.3.2 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ ✓ IUT has received INVITE from UE1 addressed to UE2 ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ IUT has sent INVITE to UE2 via GM ✓ ✓ IUT has sent INVITE to AS1 via ISC ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT AS1 not configured for being within same IMS network as IUT S-CSCF UE1 IUT AS1 UE2 Step Direction Message IF 1 target refresh INVITE 2 INVITE P-Access-Network-Info header P-Charging-Vector header access-network-charging-info parameter ISC 3 100 response Gm ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 214 Test Purpose Identifier: TP_IMST2_ISC_TAR_04 Summary: When S-CSCF receives a SIP 200 (OK) response to a SIP reINVITE request then forwards it to an AS outside the home network of the S-CSCF without charging information. Clause: 5.4.6.1.3, paragraph 1 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ ✓ IUT has received INVITE from UE1 addressed to UE2 ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ IUT has sent INVITE to UE2 via GM ✓ ✓ IUT has sent INVITE to AS1 via ISC AS1 not configured for being within same IMS network as IUT ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT ✓ ✓ IUT has received target refresh INVITE from UE1 ✓ ✓ IUT has sent target refresh INVITE to UE2 via Gm ✓ ✓ IUT has sent target refresh INVITE to AS1 via ISC UE1 IUT AS1 UE2 Step Direction Message IF 1 200 response P-Charging-Vector header access-network-charging-info parameter 2 200 response P-Charging-Vector header access-network-charging-info parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 215 Test Purpose Identifier: TP_IMST2_ISC_TAR_05 Summary: When S-CSCF receives a SIP 200 (OK) response to a SIP reINVITE request then it forwards it to an AS located inside the home network of the S-CSCF. Clause: 5.4.6.1.3, paragraph 1 References: - Config Ref: CF_2Gm1ISC IUT Role: IMS Selection Expression: PICS A.2/3 Entities Condition UE1 IUT AS1 UE2 ✓ ✓ UE1 registered in IUT ✓ ✓ ✓ IUT has received INVITE from UE1 addressed to UE2 ✓ ✓ IUT configured with an iFC designed to contact AS1 for INVITE ✓ ✓ IUT has sent INVITE to UE2 via GM ✓ ✓ IUT has sent INVITE to AS1 via ISC ✓ ✓ AS1 configured for being within same IMS network as IUT ✓ ✓ AS1 has indicated the handling of the whole dialogue to IUT ✓ ✓ IUT has received target refresh INVITE from UE1 ✓ ✓ IUT has sent target refresh INVITE to UE2 via Gm ✓ ✓ IUT has sent target refresh INVITE to AS1 via ISC UE1 IUT AS1 UE2 Step Direction Message IF 1 200 response P-Charging-Vector header access-network-charging-info parameter 2 200 response P-Charging-Vector header access-network-charging-info parameter ISC ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 216 Annex A (normative): TPLan code The test purposes defined in the present document have been automatically generated from the text files in the archive file ts_10279002v020101p0.zip which accompanies the present document. The raw text file has been converted to a table format to allow better readability. The two formats shall be considered equivalent. In the event that there appears to be syntactical or semantic differences between the two then the textual TPlan representation takes precedence over the table format. ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 217 Annex B (informative): Bibliography IETF RFC 3261: "SIP: Session Initiation Protocol". ISO/IEC 9646-2: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 2: Abstract Test Suite specification". ETSI EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework". ETSI ETSI TS 102 790-2 V2.1.1 (2013-02) 218 History Document history V1.1.1 March 2010 Publication V2.1.1 February 2013 Publication
|
826622ff296a7ac42c61883366502019
|
102 790-1
|
1 Scope
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5]. The supplier of a protocol implementation which is claimed to conform to TS 124 229 [1] is required to complete a copy of the PICS proforma provided in annex A of the present document and is required to provide the information necessary to identify both the supplier and the implementation.
|
826622ff296a7ac42c61883366502019
|
102 790-1
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
826622ff296a7ac42c61883366502019
|
102 790-1
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 229 (V10.7.0): "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 version 10.7.0 Release 10)". [2] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [5] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [6] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)". [7] IETF RFC 5009: "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media". [8] ETSI TS 133 203: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Access security for IP-based services (3GPP TS 33.203)". ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 6
|
826622ff296a7ac42c61883366502019
|
102 790-1
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
|
826622ff296a7ac42c61883366502019
|
102 790-1
|
3 Definitions and abbreviations
| |
826622ff296a7ac42c61883366502019
|
102 790-1
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 229 [1] and the following apply: PICS proforma: document, in the form of a questionnaire, designed by the protocol specifier or conformance test suite specifier, which, when completed for an OSI implementation or system, becomes the PICS NOTE: See ISO/IEC 9646-1 [3]. Protocol Implementation Conformance Statement (PICS): statement made by the supplier of an Open Systems Interconnection (OSI) implementation or system, stating which capabilities have been implemented for a given OSI protocol NOTE: See ISO/IEC 9646-1 [3]. static conformance review: review of the extent to which the static conformance requirements are met by the IUT, accomplished by comparing the PICS with the static conformance requirements expressed in the relevant standard(s) NOTE: See ISO/IEC 9646-1 [3].
|
826622ff296a7ac42c61883366502019
|
102 790-1
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 229 [1] apply.
|
826622ff296a7ac42c61883366502019
|
102 790-1
|
4 Conformance
|
A PICS proforma which conforms to this PICS proforma specification shall be technically equivalent to annex A, and shall preserve the numbering and ordering of the items in annex A. A PICS which conforms to this PICS proforma specification shall: a) describe an implementation which claims to conform to TS 124 229 [1]; b) be a conforming ICS proforma which has been completed in accordance with the instructions for completion given in clause A.1; c) include the information necessary to uniquely identify both the supplier and the implementation. ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 7 Annex A (normative): 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 annex so that it can be used for its intended purposes and may further publish the completed PICS. A.1 Guidance for completing the ICS proforma A.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 relevant specifications may provide information about the implementation in a standardised 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 protocol; - PICS proforma tables (for example: Major capabilities, etc). A.1.2 Abbreviations and conventions This annex does not reflect dynamic conformance requirements but static ones. In particular, a condition for support of a PDU parameter does not reflect requirements about the syntax of the PDU (i.e. the presence of a parameter) but the capability of the implementation to support the parameter. In the sending direction, the support of a parameter means that the implementation is able to send this parameter (but it does not mean that the implementation always sends it). In the receiving direction, it means that the implementation supports the whole semantic of the parameter that is described in the main part of the present document. As a consequence, PDU parameter tables in this annex are not the same as the tables describing the syntax of a PDU in the reference specification. The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [4]. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". Reference column The reference column gives reference to the relevant sections in core specifications. ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 8 Status column The various status used in this annex are in accordance with the rules in table A.1. Table A.1: Key to status codes Status code Status name Meaning m mandatory The capability shall be supported. It is a static view of the fact that the conformance requirements related to the capability in the reference specification are mandatory requirements. This does not mean that a given behaviour shall always be observed (this would be a dynamic view), but that it shall be observed when the implementation is placed in conditions where the conformance requirements from the reference specification compel it to do so. For instance, if the support for a parameter in a sent PDU is mandatory, it does not mean that it shall always be present, but that it shall be present according to the description of the behaviour in the reference specification (dynamic conformance requirement). o optional The capability may or may not be supported. It is an implementation choice. n/a not applicable It is impossible to use the capability. No answer in the support column is required. c.<integer> conditional The requirement on the capability ("m", "o" and "n/a") depends on the support of other optional or conditional items. <integer> is the identifier of the conditional expression. o.<integer> qualified optional For mutually exclusive or selectable options from a set. <integer> is the identifier of the group of options, and the logic of selection of the options. Mnemonic column The Mnemonic column contains mnemonic identifiers for each item. 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 [4], are used for the support column: Y or y supported by the implementation N or n not supported by the implementation N/A, n/a or- no answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status) References to items For each possible item answer (answer in the support column) within the PICS proforma there exists a unique reference, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. EXAMPLE: A.5/4 is the reference to the answer of item 4 in table A.5. A.1.3 Instructions for completing the PICS proforma The supplier of the implementation may complete the PICS proforma in each of the spaces provided. More detailed instructions are given at the beginning of the different clauses of the PICS proforma. ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 9 A.2 Identification of the Network Equipment Identification of the Network Equipment should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person. A.2.1 Date of the statement ......................................................................................................................................................................................... A.2.2 Network Equipment Under Test identification Name: ......................................................................................................................................................................................... ......................................................................................................................................................................................... Hardware configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Software configuration: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.3 Product supplier Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 10 Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.4 Client Name: ......................................................................................................................................................................................... Address: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ......................................................................................................................................................................................... A.2.5 PICS contact person Name: ......................................................................................................................................................................................... Telephone number: ......................................................................................................................................................................................... Facsimile number: ......................................................................................................................................................................................... E-mail address: ......................................................................................................................................................................................... Additional information: ......................................................................................................................................................................................... ......................................................................................................................................................................................... ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 11 A.3 Identification of the protocol This PICS proforma applies to the following specification: TS 124 229 [1]. A.4 Global statement of conformance The implementation described in this PICS meets all the mandatory requirements of the referenced standard? [ ] Yes [ ] No NOTE: Answering "No" to this question indicates non-conformance to the protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming. Explanations may be entered in the comments field at the bottom of each table or on attached pages. In the tabulations which follow, all references are to TS 124 229 [1] unless another numbered reference is explicitly indicated. A.5 PICS proforma tables A.5.1 Roles Table A.2: Roles Item Roles Reference Status Support 1 P-CSCF Clause 5.2 o.1 2 I-CSCF Clause 5.3 o.1 3 S-CSCF Clause 5.4 o.1 4 IBCF Clause 5.10 o.1 5 E-CSCF Clause 5.11 o.1 o.1 At least one of these capabilities shall be supported. A.5.2 P-CSCF Role The tables provided in this clause need only to be completed for P-CSCF implementations, where item A.2/1 above is supported. ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 12 A.5.2.1 P-CSCF Capabilities Table A.3: P-CSCF Capabilities Item Major capability: Does the implementation support... Reference Status Support General Capabilities (clause 4) 1.1 The proxy role with IMS related exceptions and additional capabilities to SIP? Clauses 4.1, 5.2 m 1.2 The proxy role with IMS related exceptions and additional capabilities to SDP? Clauses 4.1, 6.2 m 1.3 The proxy role with IMS related exceptions and additional capabilities to SigComp? Clauses 4.1, 8.2 m 2 the UA role in providing application level gateway functionality (IMS-ALG) (clause 4.1) ... 2.1 ... for subscribing to or the receiving of event information? Clauses 4.1, 5.2 m 2.2 ... for performing P-CSCF initiated dialog-release? Clauses 4.1, 5.2 m 2.3 ... for performing NAT traversal procedures? Clause 4.1, annexes F, G, K m 2.4 ... for performing media plane security procedures? Clauses 4.1, 5.2 m 3 The access technology specific procedures? Clauses 4.1, 3A, 9.2.2 m 4 signalling security using (Clause 4.2B.1) ... 4.1 IMS AKA plus IPsec ESP? Clauses 4.2B.1, table 4-1, TS 133 203 [8], clause 6 m 4.2 SIP digest plus check of IP association? Clause 4.2B.1, table 4-1, TS 133 203 8], annex S o 4.3 SIP digest plus Proxy Authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8], annex N o 4.4 SIP digest with TLS? Clause 4.2B.1, table 4-1, TS 133 203 [8], annexes N, O o 4.5 NASS-IMS bundled authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex R o 4.6 GPRS-IMS-Bundled authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8], annex S o 5 End-to-access-edge media security using SDES? Clause 4.2B.2, table 4-2 m 6.1 The loose routeing policy? Clause 4.3, RFC 3261 [2] m 6.2 Interoperability with strict routers? Clause 4.3, RFC 3261 [2] Clauses 12.2.1.1, 16.4 m 7 Procedures related to charging? Clause 4.5 m 8 Procedures related to emergency services? Clauses 4.7, 5.2.10 m 9 Tracing of signalling? Clause 4.8 o 10 Priority mechanisms? Clause 4.11 m P-CSCF specific application usage of SIP (clause 5.2) 11 Provision of priority to emergency and priority transactions? Clause 5.2.1 m Registration general (clause 5.2.1) ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 13 Item Major capability: Does the implementation support... Reference Status Support 12.1 Selection of the security mechanism based on the content of the REGISTER request (Security-Client header field and the Require and Proxy-Require header fields set to "sec-agree") received from the UE? Clause 5.2.2.1, first numbered list item 1 m 12.2 Selection of the security mechanism based on the access type when the REGISTER request received from the UE does not contain a Security-Client header field, or contains a Security-Client header field and the Require and Proxy-Require header fields do not contain "sec-agree"? Clause 5.2.2.1, first numbered list item 2 m 13 General procedures that apply on receipt of a REGISTER request from the UE? Clause 5.2.2.1, second numbered list m 14 General procedures that apply on receipt of a 200OK response to a REGISTER request? Clause 5.2.2.1, third numbered list m Registration when IMS AKA as a security mechanism applies (clause 5.2.2) 15.1 Specific procedures that apply on receipt of a unprotected REGISTER request from the UE when IMS AKA as a security mechanism applies? Clause 5.2.2.2, first numbered list items 1, 2 m 15.2 Specific procedures that apply on receipt of a protected REGISTER request from the UE when IMS AKA as a security mechanism applies? Clause 5.2.2.2, first numbered list items 1, 3 m 15.2.1 Rejection of the protected REGISTER request in case of failure of the verification of the content of the Security-Verify headers and Security-Client headers? Clause 5.2.2.2, first numbered list item 3 a) o 15.3 Procedures that apply on receipt of a 401 response to a (unprotected) REGISTER request? Clause 5.2.2.2, second numbered list m 15.4 Procedures that apply on receipt of a 200OK response to a (protected) REGISTER request? Clause 5.2.2.2, third numbered list m 15.5 Parallel management of old and newly established security associations? Clause 5.2.2.2, fourth and fifth numbered lists, table 5.2.2-1 m Registration without TLS as a security mechanism (clause 5.2.3) 16.1 Specific procedures that apply on receipt of a REGISTER request from the UE when no TLS security mechanism applies? Clause 5.2.2.3, first numbered list m 16.2 Procedures that apply on receipt of a 500 response to a REGISTER request? Clause 5.2.2.3 m 16.3 Procedures that apply on receipt of a 200OK response to a REGISTER request? Clause 5.2.2.3, first alphabetic list m Registration when TLS as a security mechanism applies (clause 5.2.2.4) 17 TLS as a security mechanism? Clause 5.2.2.4 o 17.1 Specific procedures that apply on receipt of a unprotected REGISTER request from the UE when TLS as a security mechanism applies? Clause 5.2.2.4, first numbered list items 1 c.1 17.2 Specific procedures that apply on receipt of a protected REGISTER request from the UE when IMS AKA as a security mechanism applies? Clause 5.2.2.4, first numbered list item 2 c.1 17.2.1 Rejection of the protected REGISTER request in case of failure of the verification of the content of the Security-Verify headers and Security-Client headers? Clause 5.2.2.4, first numbered list items 2 b) and 3 b) c.2 17.3 Procedures that apply on receipt of a 401 response to a (unprotected) REGISTER request? Clause 5.2.2.4, second numbered list c.1 17.4 Procedures that apply on receipt of a 200OK response to a (protected) REGISTER request? Clause 5.2.2.4, dashed list c.1 Registration when NASS-IMS bundled authentication as a security mechanism applies (clause 5.2.2.5) 18.1 Specific procedures that apply on receipt of a request from the UE when NASS-IMS bundled Clause 5.2.2.5, numbered list m ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 14 Item Major capability: Does the implementation support... Reference Status Support authentication as a security mechanism applies? 18.2 Procedures that apply on receipt of a 200OK response to a REGISTER request? Clause 5.2.2.5, alphabetic list m Registration when GPRS-IMS bundled authentication as a security mechanism applies (clause 5.2.2.6) 19.1 Specific procedures that apply on receipt of a REGISTER request from the UE when GPRS-IMS bundled authentication as a security mechanism applies? Clause 5.2.2.6 m 19.2 Procedures that apply on receipt of a 200OK response to a REGISTER request? Clause 5.2.2.6, numbered list m Subscription, registration of additional identities, de-registration(clauses 5.2.3 – 5.2.5) 20 Subscription procedures to a user’s registration state event package? (see note 1) Clause 5.2.3 m 21 Subscription procedures to a user’s debug event package? (see note 2) Clause 5.2.3A m 22 Procedures of registering additional public user identities? (see note 3) Clause 5.2.4 m 23.1 Procedures for user-initiated deregistration? Clause 5.2.5.1 m 23.2 Procedures for network-initiated deregistration? Clause 5.2.5.2 m Handling of requests other than REGISTER (clause 5.2.6) Requests initiated by the UE (clause 5.2.6.3) 24.1 General handling of initial requests for a dialog or requests for a standalone transaction from a UE? Clause 5.2.6.3.1 m 24.1.1 Handling of initial request for a dialog or a request for a standalone transaction from a UE that is not considered as privileged sender? Clause 5.2.6.3.1 dashed list m 24.1.2 Handling of initial request for a dialog or a request for a standalone transaction from a UE that is considered as privileged sender? Clause 5.2.6.3.1 alphabetic and numbered list m 24.2 General handling of responses from a UE? Clause 5.2.6.3.2 m 24.3 Rejection of requests with restoration procedures? Clause 5.2.6.3.2A o 24.4 Handling of initial requests for a dialog? Clause 5.2.6.3.3 m 24.4.1 In case of failure of the verification of the URIs in the Route headers (clause 5.2.6.3.3 item 2)) … 24.4.1.1 Rejection of the request? Clause 5.2.6.3.3 item 2) a) o.1 24.4.1.2 Replacement of the Route headers with stored values? Clause 5.2.6.3.3 item 2) b) o.1 24.4.2 When building the Via header (clause 5.2.6.3.3 item 4)) … 24.4.2.1 Insertion of the P-CSCF FQDN that resolves to the IP address? Clause 5.2.6.3.3 item 4) a) o.2 24.4.2.2 Insertion of the P-CSCF IP address? Clause 5.2.6.3.3 item 4) b) o.2 24.4.3 When building the Record-Route header (clause 5.2.6.3.3 item 5)) … 24.4.3.1 Insertion of the P-CSCF FQDN that resolves to the IP address? Clause 5.2.6.3.3 item 5) a) o.3 24.4.3.2 Insertion of the P-CSCF IP address? Clause 5.2.6.3.3 item 5) b) o.3 24.5 Handling of 1xx and 2xx responses to initial requests? Clause 5.2.6.3, second numbered list m 24.5.1 In case a security association or a TLS session exists, when rewriting its own Record Route entry (clause 5.2.6.3.4 item 4)) … 24.5.1.1 Insertion of the P-CSCF FQDN that resolves to the IP address of the security association or the TLS session? Clause 5.2.6.3.4 item 4) a) o.4 24.5.1.2 Insertion of the P-CSCF IP address of the security association or the TLS session? Clause 5.2.6.3.4 item 4) b) o.4 24.6 Handling of target refresh requests? Clause 5.2.6.3.5 m 24.6.1 In case of failure of the verification of the URIs in the Route headers (clause 5.2.6.3.5 item 2)) … 24.6.1.1 Rejection of the request? Clause 5.2.6.3.5 item 2) a) o.5 24.6.1.2 Replacement of the Route headers with stored values? Clause 5.2.6.3.5 item 2) b) o.5 24.6.2 When building the Via header (clause 5.2.6.3.5 item 3)) … 24.6.2.1 Insertion of the P-CSCF FQDN that resolves to the Clause 5.2.6.3.5 o.6 ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 15 Item Major capability: Does the implementation support... Reference Status Support IP address? item 3) a) 24.6.2.2 Insertion of the P-CSCF IP address? Clause 5.2.6.3.5 item 3) b) o.6 24.7 Handling of responses to target refresh requests? Clause 5.2.6.3.6 m 24.8 Handling of requests for a standalone transaction? Clause 5.2.6.3.7 m 24.8.1 In case of failure of the verification of the URIs in the Route headers (clause 5.2.6.3 item 2)) … 24.8.1.1 Rejection of the request? Clause 5.2.6.3.7 item 2) a) o.7 24.8.1.2 Replacement of the Route headers with stored values? Clause 5.2.6.3.7 item 2) b) o.7 24.9 Handling of responses to standalone requests? Clause 5.2.6.3.8 m 24.10 Handling of subsequent (other than target refresh) requests? Clause 5.2.6.3.9 m 24.10.1 In case of failure of the verification of the URIs in the Route headers (clause 5.2.6.3.9 item 2)) … 24.10.1.1 Rejection of the request? Clause 5.2.6.3.9 item 2) a) o.8 24.10.1.2 Replacement of the Route headers with stored values? Clause 5.2.6.3.9 item 2) b) o.8 24.11 Handling of requests for unknown method that do not relate to an existing dialog? Clause 5.2.6.3.11 m 24.11.1 In case of failure of the verification of the URIs in the Route headers (clause 5.2.6.3.11 item 1)) … 24.11.1.1 Rejection of the request? Clause 5.2.6.3.11 item 1) a) o.9 24.11.1.2 Replacement of the Route headers with stored values? Clause 5.2.6.3.11 item 1) b) o.9 Requests terminated by the UE (clause 5.2.6.4) 25.1 General handling of initial requests for a dialog or requests for a standalone transaction terminated by the UE? Clause 5.2.6.4.1 m 25.2 General handling of responses destined to a UE? Clause 5.2.6.4.2 m 25.3 Handling of initial requests for a dialog destined for a UE? Clause 5.2.6.4.3 m 25.3.1 When building the Record-Route header (clause 5.2.6.4.3 item 4)) … 25.3.1.1 Insertion of the P-CSCF FQDN that resolves to the IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.3 item 4) a) o.10 25.3.1.2 Insertion of the P-CSCF IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.3 item 4) b) o.10 25.3.2 When building the Via header (clause 5.2.6.4.3 item 6)) … 25.3.2.1 Insertion of the P-CSCF FQDN that resolves to the IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.3 item 6) a) o.11 25.3.2.2 Insertion of the P-CSCF IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.3 item 6) b) o.11 25.4 Handling of 1xx and 2xx responses to initial requests? Clause 5.2.6.4.4 m 25.4.1 In case of failure of the verification of the Via headers (clause 5.2.6.4.4 item 2)) … 25.4.1.1 Discarding the response? Clause 5.2.6.4.4 item 2) a) o.12 25.4.1.2 Replacement of the Via header values with stored values? Clause 5.2.6.4.4 item 2) b) o.12 25.4.2 In case of failure of the verification of the URIs in the Route headers (clause 5.2.6.4.4 item 3)) … 25.4.2.1 Discarding the response? Clause 5.2.6.4.4 item 3) first a) o.13 25.4.2.2 Replacement of the Record-Route header values with stored values? Clause 5.2.6.4.4 item 3) first b) o.13 25.4.2.2 When replacing build the Record-Route header with (clause 5.2.6.4.4 item 3) first b)) … 25.4.2.2.1 The P-CSCF FQDN that resolves to its IP address? Clause 5.2.6.4.4 item 3) first b) c.1 25.4.2.2.2 The P-CSCF IP address? Clause 5.2.6.4.4 item 3) first b) c.1 25.4.3 When building the Record-Route header in case of success of the verification of the URIs in the Route headers (clause 5.2.6.4.4 item 3) second alphabetic list) … ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 16 Item Major capability: Does the implementation support... Reference Status Support 25.4.3.1 The P-CSCF FQDN that resolves to its IP address? Clause 5.2.6.4.4 item 3) second a) o.14 25.4.3.2 The P-CSCF IP address? Clause 5.2.6.4.4 item 3) second b) o.14 25.5 Handling of responses (other than 1xx and 2xx) to initial requests? Clause 5.2.6.4, third numbered list m 25.5.1 In case of failure of the verification of the Via headers (clause 5.2.6.4.4 third alphabetic list) … 25.5.1.1 Discarding the response? Clause 5.2.6.4.4 third a) o.15 25.5.1.2 Replacement of the Via header values with stored values? Clause 5.2.6.4.4 third b) o.15 25.6 Handling of target refresh requests? Clause 5.2.6.4.5 m 25.6.1 When building the Via header (clause 5.2.6.4.5 item 1)) … 25.6.1.1 Insertion of the P-CSCF FQDN that resolves to the IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.5 item 1) a) o.16 25.6.1.2 Insertion of the P-CSCF IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.5 item 1) b) o.16 25.6.2 When building the Record-Route header (clause 5.2.6.4.5 item 3)) … 25.6.2.1 Insertion of the P-CSCF FQDN that resolves to the IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.5 item 3) a) o.17 25.6.2.2 Insertion of the P-CSCF IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.5 item 3) b) o.17 25.7 Handling of 1xx and 2xx responses to target refresh requests? Clause 5.2.6.4.6, first numbered list m 25.7.1 In case of failure of the verification of the Via headers (clause 5.2.6.4.6 first 1)) … 25.7.1.1 Discarding the response? Clause 5.2.6.4.6 first 1) a) o.18 25.7.1.2 Replacement of the Via header values with stored values? Clause 5.2.6.4.6 first 1) b) o.18 25.8 Handling of responses (other than 1xx and 2xx) to target refresh requests? Clause 5.2.6.4.6, second numbered list m 25.8.1 In case of failure of the verification of the Via headers (clause 5.2.6.4.6 second 1)) … 25.8.1.1 Discarding the response? Clause 5.2.6.4 second 1) a) o.19 25.8.1.2 Replacement of the Via header values with stored values? Clause 5.2.6.4 second 1) b) o.19 25.9 Handling of requests for standalone transactions or unknown methods? Clause 5.2.6.4.7 m 25.9.1 When building the Via header (clause 5.2.6.4.7 item 2)) … 25.9.1.1 Insertion of the P-CSCF FQDN that resolves to the IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.7 item 2) a) o.20 25.9.1.2 Insertion of the P-CSCF IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4 item 2) b) o.20 25.10 Handling of all responses to requests for standalone transactions or unknown methods? Clause 5.2.6.4.8 m 25.10.1 In case of failure of the verification of the Via headers (clause 5.2.6.4.8 item 1)) … 25.10.1.1 Discarding the response? Clause 5.2.6.4.8 item 1) a) o.21 25.10.1.2 Replacement of the Via values with stored values? Clause 5.2.6.4.8 item 1) b) o.21 25.11 Handling of subsequent (other than target refresh) requests? Clause 5.2.6.4.9 m 25.11.1 When building the Via header (clause 5.2.6.4.9 item 1)) … 25.11.1.1 Insertion of the P-CSCF FQDN that resolves to the IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.9 item 1) a) o.22 ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 17 Item Major capability: Does the implementation support... Reference Status Support 25.11.1.2 Insertion of the P-CSCF IP address of the security association or TLS session established from the UE to the P-CSCF? Clause 5.2.6.4.9 item 1) b) o.22 25.12 Handling of 1xx and 2xx responses to subsequent requests? Clause 5.2.6.4.10 m 25.12.1 In case of failure of the verification of the Via headers (clause 5.2.6.4.10 item 1)) … 25.12.1.1 Discarding the response? Clause 5.2.6.4.10 item 1) a) o.23 25.12.1.2 Replacement of the Via header values with stored values? Clause 5.2.6.4.10 item 1) b) o.23 Additional requirements for INVITE Request, session termination and subsequent requests (clauses 5.2.7, 5.2.8, 5.2.9) 26.1 Additional requirements for UE-originated INVITE requests? Clause 5.2.7.2 m 26.1.1 Application of periodic session refreshment on receipt of UE-originated INVITE requests? Clause 5.2.7.2 o 26.2 Additional requirements for UE-terminated INVITE requests? Clause 5.2.7.3 m 26.2.1 Application of periodic session refreshment on receipt of UE-terminated INVITE requests? Clause 5.2.7.3 o 27.1 P-CSCF initiated call release (clause 5.2.8.1) ... 27.1.1 Cancellation of a session currently being established? Clause 5.2.8.1.1 m 27.1.2 Release of an existing session? Clause 5.2.8.1.2 m 27.2 Call release initiated by other entities? Clause 5.2.8.2 m 27.3 Call release due to session expiry? Clause 5.2.8.3 m 28.1 Additional requirements for subsequent requests (UE-originating case)? Clause 5.2.9.1 m 28.2 Additional requirements for subsequent requests (UE-terminating case)? Clause 5.2.9.2 m Emergency service (clause 5.2.10) (see note 4) 29.1 Handling of emergency session establishment within a non-emergency registration? Clause 5.2.10.1 m 29.2 Emergency registrations? Clause 5.2.10.1 m 29.3 Requests for all dialogs and standalone transactions (other than REGISTER) from an unregistered user? Clause 5.2.10.2 m 29.3.1 When building the URI (clause 5.2.10.2 item 1)) … 29.3.1.1 Inclusion of the URI received from the UE? Clause 5.2.10.2 item 1) first dash o.24 29.3.1.2 Inclusion of a URI deduced from the URI received from the UE? Clause 5.2.10.2 item 1) second dash o.24 29.4 Delivery of responses for all dialogs and standalone transactions (other than REGISTER) to an unregistered user? Clause 5.2.10.2 m 29.5 Treatment for all dialogs and standalone transactions (other than REGISTER) related to requests to an unregistered user? Clause 5.2.10.2.A m 29.6 Requests for all dialogs and standalone transactions (other than REGISTER) from an emergency-registered user? Clause 5.2.10.3 m 29.6.1 When building the URI (clause 5.2.10.3 item 1)) … 29.6.1.1 Inclusion of the URI received from the UE? Clause 5.2.10.3 item 1) first dash o.25 29.6.1.2 Inclusion of a URI deduced from the URI received from the UE? Clause 5.2.10.3 item 1) second dash o.25 29.7.1 Requests for all dialogs and standalone transactions (other than REGISTER) from an non-emergency-registered user? Clause 5.2.10.4 m 29.7.1.1 When building the URI (clause 5.2.10.4 item 1)) … 29.7.1.1.1 Inclusion of the URI received from the UE? Clause 5.2.10.4 item 1) first dash o.26 29.7.1.1.2 Inclusion of a URI deduced from the URI received from the UE? Clause 5.2.10.4 item 1) second dash o.26 29.8 Abnormal and rejection cases? Clause 5.2.10.5 m P-CSCF specific application usage of SDP (clause 6.2) ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 18 Item Major capability: Does the implementation support... Reference Status Support 30.1 Handling of requests including SDP offers? Clause 6.2 second and third paragraphs m 30.1.1 Rejection of requests including encrypted SDP offers? Clause 6.2, third paragraph o 30.2 Handling of responses (other than 200OK) including SDP offers? Clause 6.2, fifth paragraph m 30.2.1 Rejection of requests following non-200OK responses including encrypted SDP offers? Clause 6.2, fifth paragraph o 30.3 Handling of 200OK responses including SDP offers? Clause 6.2, sixth paragraph m 30.3.1 Session termination on receipt of encrypted SDP offers in 200OK responses? Clause 6.2, sixth paragraph o 30.4 Inspection of b=RS and b=RR lines within an SDP offer? Clause 6.2, ninth paragraph o IMS-ALG in P-CSCF (clause 6.7.2) 31 IMS-ALG functionality within the P-CSCF? Clause 6.7.2 o 31.1 General procedures for the support of SDP in IMS-ALG within the P-CSCF? Clause 6.7.2.1 c.2 31.2 IMS-ALG in P-CSCF procedures for media plane security? Clause 6.7.2.2 c.2 31.3 IMS-ALG in P-CSCF procedures for explicit congestion control support? Clause 6.7.2.3 c.2 31.4 IMS-ALG in P-CSCF procedures for Optimal Media Routeing (OMR)? Clause 6.7.2.4 c.2 31.5 IMS-ALG in P-CSCF procedures for NA(P)T and NA(P)T-PT controlled by the P-CSCF? Clause 6.7.2.5 c.2 31.6 IMS-ALG in P-CSCF procedures for support of hosted NAT? Clause 6.7.2.6 c.2 31.7 IMS-ALG in P-CSCF procedures for support of ICE? Clause 6.7.2.7 c.2 31.8 IMS-ALG in P-CSCF procedures for transcoding? Clause 6.7.2.8 c.2 SIP compression (clause 8.2) 32 SIP compression? Clauses 8.2.1, 8.2.2 m 32.1 The negative acknowledgement mechanism for compression? Clause 8.2.1 o 32.3 The presence specific dictionary for compression? Clause 8.2.1 o 32.4 Compression of requests and responses to a UE? Clause 8.2.2 o 32.4 Decompression of requests and responses from a UE? Clause 8.2.3 m IP-Connectivity Access Network specific concepts when using GPRS to access IM CN subsystem (Annex B) 33 Application usage of SIP when using GPRS to access IM CN subsystem? Clause B.3.2 m IP-Connectivity Access Network specific concepts when using xDSL to access IM CN subsystem (Annex E) 34 Application usage of SIP when using xDSL access to IM CN subsystem? Clause E.3.2 m 34.1 Insertion of the P-Access-Network-Info header for location information handling? Clause E.3.2.2 o Additional procedures in support for hosted NAT (Annex F) 35 Additional procedures in support for hosted NAT? Annex F o 35.1 Usage of SIP in support for hosted NAT? Clause F.2.2 c.3 35.1.1 Rejection of integrity protected REGISTER requests in case the comparison of the Security-Verify header and the Security-Server header with stored values fails? Clause F.2.2, item (3 (b, third dash o 35.2 Usage of SIP in support for hosted NAT in case UDP encapsulated IPsec is not employed? Clause F.4 c.3 IP-Connectivity Access Network specific concepts when using DOCSIS to access IM CN subsystem (Annex H) 36 Usage of SIP when DOCSIS to access to the IM CN subsystem was requested? Clause H.3.2 m 36.1 Insertion of the P-Access-Network-Info header for location information handling? Clause H.3.2.2 o Additional procedures in support of UE managed NAT traversal (Annex K) 37 Application usage of SIP for UE managed NAT traversal? Clause K.2.2 m ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 19 Item Major capability: Does the implementation support... Reference Status Support 37.1 Additional procedures to registration with security association set-up for UE managed NAT traversal? Clause K.2.2.2 m 37.2 Additional procedures to handling of requests (other than REGISTER) initiated or terminated by a UE for UE managed NAT traversal? Clause K.2.2.3 m 37.3 Additional procedures to the emergency service for UE managed NAT traversal? Clause K.2.2.5 m 38 Application usage of SDP for UE managed NAT traversal? Clause K.3.2 m 39 Application usage of ICE for UE managed NAT traversal? Clause K.5.3 m IP-Connectivity Access Network specific concepts when using EPS to access IM CN subsystem (Annex L) 40 Application usage of SIP when using EPS access to IM CN subsystem? Clause L.3.2 m IP-Connectivity Access Network specific concepts when using cdma2000® packet data subsystem to access IM CN subsystem (Annex M) 41 Application usage of SIP when using cdma2000® packet data subsystem access to IM CN subsystem? Clause M.3.2 m IP-Connectivity Access Network specific concepts when using the EPC via cdma2000® HRPD to access IM CN subsystem (Annex O) 42 Application usage of SIP when using the EPC via cdma2000® HRPD access to IM CN subsystem? Clause O.3.2 m IP-Connectivity Access Network specific concepts when using cdma2000® 1x Femtocell Network to access IM CN subsystem (Annex Q) 43 Application usage of SIP when using cdma2000® 1x Femtocell Network access to IM CN subsystem? Clause Q.3.2 m NOTE 1: The P-CSCF has to send a SUBSCRIBE request to the home domain in which the user’s public user identity resides upon receipt of a 200OK response to the first initial REGISTER request. NOTE 2: The P-CSCF has to send a SUBSCRIBE request to the home domain in which the user’s public user identity resides upon receipt of a 2xx response to a registration that contained an empty P-Debug-ID header field. NOTE 3: The P-CSCF is informed of additional public user identities by the registrar via NOTIFY requests. NOTE 4: See also PICS item A.3/8. o.n At least one of these capabilities shall be supported. c.1 o, if A.3/25.4.2.2 is supported, else n/a c.2 o, if A.3/31 is supported, else n/a c.3 m, if A.3/35 is supported, else n/a ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 20 A.5.2.2 P-CSCF header handling Table A.4: P-CSCF Header Handling Item Header handling: Does the implementation support... Reference Status Support 1 Insertion or modification of the Resource-Priority header to give priority to emergency or priority transactions? Clause 5.2.1, RFC 4412 [6] c.1 2 The Path header in REGISTER request and related 200OK response messages? Clause 5.2.1 m 3 The Service-Route header in 200OK response messages to REGISTER requests? Clause 5.2.1 m 4.1 Removal of the P-Charging-Function-Addresses header from requests and responses to be sent to the UE? Clause 5.2.1 m 4.2 Removal of the P-Charging-Vector header from requests and responses to be sent to the UE? Clause 5.2.1 m 5.1.1 Removal of the P-Charging-Function-Addresses header from requests and responses received from the UE? Clause 5.2.1, numbered item 1 m 5.1.2 Insertion of saved P-Charging-Function- Addresses header into requests and responses from the UE to be forwarded? Clause 5.2.1 numbered item 2 o 5.2.1 Removal of the P-Charging-Vector header from requests and responses received from the UE? Clause 5.2.1 numbered item 1 m 5.2.2 Insertion of saved P-Charging-Vector header into requests and responses from the UE to be forwarded? Clause 5.2.1 numbered item 2 o 5.3.1 Removal of the P-Access-Network header with "network provided" parameter? Clause 5.2.1 numbered item 3 m 5.3.2 Insertion of the P-Access-Network header with parameters set to the appropriate (access technology dependent) values? Clause 5.2.1 numbered item 4 o 6 Removal of the P-Media-Authorization header from requests and responses to be sent to the UE? Clause 5.2.1 m 7 Removal, insertion and modification of the P-Early-Media header? Clause 5.2.1, RFC 5009 [7] o c.1 o, if A.3/11 is supported, else n/a A.5.3 I-CSCF Role The tables provided in this clause need only to be completed for I-CSCF implementations, where item A.2/2 above is supported. A.5.3.1 I-CSCF Capabilities Table A.5: I-CSCF Capabilities Item Major capability: Does the implementation support... Reference Status Support General Capabilities (clause 4) 1.1 The proxy role with IMS related exceptions and additional capabilities to SIP? Clauses 4.1, 5.3 m 1.2 The UA role when providing server functionality to return a final response? Clause 4.1 o 2 Signalling security using (Clause 4.2B.1) ... 2.1 IMS AKA plus IPsec ESP? Clause 4.2B.1, table 4-1, TS 133 203 [8] clause 6 m ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 21 Item Major capability: Does the implementation support... Reference Status Support 2.2 SIP digest plus check of IP association? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex S o 2.3 SIP digest plus Proxy Authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex N o 2.4 SIP digest with TLS? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex N, O o 2.5 NASS-IMS bundled authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex R o 2.6 GPRS-IMS-Bundled authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex S o 2.7 Trusted node authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex U o 3.1 The loose routeing policy? Clause 4.3, RFC 3261 [2] m 3.2 Interoperability with strict routers? Clause 4.3, RFC 3261 [2] Clauses 12.2.1.1, 16.4 m 4 Procedures related to charging? Clause 4.5 m 5 Tracing of signalling? Clause 4.8 o 6 Procedures related to overlap sending? Clause 4.9 m I-CSCF specific application usage of SIP (clause 5.3) 7.1 Procedures that apply on receipt of a REGISTER request? (see note 1) Clause 5.3.1.2 m 7.2 Procedures that apply on receipt of a user registration status query response? (see note 2) Clause 5.3.1.2 first and second numbered list m 7.2.1 Insertion of the Redirect-Host AVP into the P-User-Database header of the REGISTER request to be sent to the S-CSCF? Clause 5.3.1.2 first 2), second 3) o 7.3.1 Procedures that apply in case the user registration status query procedure fails? Clause 5.3.1.3 m 7.3.2 Procedures that apply on receipt of no response or a response other than 200OK from the S-CSCF? Clause 5.3.1.3 m 8.1 Stateful proxy behaviour for initial requests? Clause 5.3.2.1 first sentence o.1 8.2 Stateless proxy behaviour for initial requests? Clause 5.3.2.1 complement of first sentence o.1 8.3 Handling of initial requests not containing the "orig" parameter in the topmost Route header? Clause 5.3.2.1 m 8.3.1 Application of periodic session refreshment on receipt of INVITE requests? Clause 5.3.2.1 o 8.3.2 Insertion of the Redirect-Host AVP into the P-User-Database header of INVITE requests to be forwarded to the S-CSCF? Clause 5.3.2.1 second 3) o 8.4 Originating procedures for requests containing the "orig" parameter in the topmost Route header? Clause 5.3.2.1A m 8.4.1 Application of periodic session refreshment on receipt of INVITE requests? Clause 5.3.2.1A o 8.4.2 Insertion of the Redirect-Host AVP into the P-User-Database header of INVITE requests to be forwarded to the S-CSCF? Clause 5.3.2.1A first 3) o ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 22 Item Major capability: Does the implementation support... Reference Status Support 8.5 Abnormal cases related to Initial requests (clause 5.3.2.2) ... 8.5.1 Procedures for successful user location query when the S-CSCF cannot be contacted? Clause 5.3.2.2 m 8.5.2 Procedures for unsuccessful outcome of request processing? Clause 5.3.2.2 m Additional routeing capabilities in support of transit and interconnection traffics in IM CN subsystem (Annex I) 9 Additional routeing capabilities? Annex I o NOTE 1: The I-CSCF has to start the user registration status query procedure on receipt of the REGISTER request from the P-CSCF. The I-CSCF shall behave as a stateful proxy. NOTE 2: If the user registration status query procedure succeeds, the I-CSCF has to forward the REGISTER request to the S-CSCF. The 200OK response from the S-CSCF has to be proxied to the P-CSCF. o.n At least one of these capabilities shall be supported. A.5.4 S-CSCF Role The tables provided in this clause need only to be completed for S-CSCF implementations, where item A.2/3 above is supported. A.5.4.1 S-CSCF Capabilities Table A.6: S-CSCF Capabilities Item Major capability: Does the implementation support... Reference Status Support General Capabilities (clause 4) 1.1 The proxy role with IMS related exceptions and additional capabilities to SIP? Clauses 4.1, 5.4 m 1.2 The proxy role with IMS related exceptions and additional capabilities to SDP? Clauses 4.1, 6.3 m 2 The UA role with IMS related exceptions and additional capabilities? (see note 1) Clauses 4.1, 5.4 m 3 Signalling security using (Clause 4.2B.1) ... 3.1 IMS AKA plus IPsec ESP? Clause 4.2B.1, table 4-1, TS 133 203 [8] clause 6 m 3.2 SIP digest plus check of IP association? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex S o 3.3 SIP digest plus Proxy Authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex N o 3.4 SIP digest with TLS? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex N, O o 3.5 NASS-IMS bundled authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex R o 3.6 GPRS-IMS-Bundled authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex S o 3.7 Trusted node authentication? Clause 4.2B.1, table 4-1, TS 133 203 [8] annex U o 4.1 The loose routeing policy? Clause 4.3, RFC 3261 [2] m ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 23 Item Major capability: Does the implementation support... Reference Status Support 4.2 Interoperability with strict routers? Clause 4.3, RFC 3261 [2] Clauses 12.2.1.1, 16.4 m 5 Procedures related to charging? Clause 4.5 m 6 Procedures related to emergency services? Clauses 4.7, 5.4.8 m 7 Tracing of signalling? Clause 4.8 o 8 Procedures related to overlap sending? Clause 4.9 m 9 Priority mechanisms? Clause 4.11 m S-CSCF specific application usage of SIP (clause 5.4) 10 Provision of priority to emergency registrations and calls? Clauses 5.4.0, 5.4.1.1 m Registration general (clause 5.4.1) 11 Selection of the authentication mechanism based on the contents of the REGISTER request (Authorization header and/or P-Access-Network- Info header)? Clause 5.4.1.1 m Unprotected REGISTER and challenges (clause 5.4.1.2.1) 11.1 Procedures that apply on receipt of an unprotected REGISTER request for an already registered public user identity? Clause 5.4.1.2.1 first numbered list m 11.2 Procedures that apply on receipt of an unprotected REGISTER request for a not yet registered public user identity? Clause 5.4.1.2.1 second numbered list m 12.1 Provision of challenges with IMS AKA as security mechanism in the 401 response? Clause 5.4.1.2.1A m 12.2 Provision of challenges with SIP digest as security mechanism in the 401 response? Clause 5.4.1.2.1B c.1 12.3 Provision of challenges with SIP digest with TLS as security mechanism in the 401 response? Clause 5.4.1.2.1C c.2 13.1 Procedures for initial registration and user-initiated reregistration for NASS-IMS bundled authentication? Clause 5.4.1.2.1D c.3 13.2 Procedures for initial registration and user-initiated reregistration for GPRS-IMS bundled authentication? Clause 5.4.1.2.1E c.4 Protected REGISTER (clause 5.4.1.2.2) 14.1 Procedures that apply on receipt of a protected REGISTER request when IMS AKA as security mechanism applies? Clauses 5.4.1.2.2, 5.4.1.2.2F m 14.2 Procedures that apply on receipt of a protected REGISTER request when SIP digest as security mechanism applies? Clauses 5.4.1.2.2A, 5.4.1.2.2F c.1 14.3 Procedures that apply on receipt of a protected REGISTER request when SIP digest with TLS as security mechanism applies? Clauses 5.4.1.2.2B, 5.4.1.2.2F c.2 14.4 Procedures that apply on receipt of a protected REGISTER request for which authentication is already performed? Clauses 5.4.1.2.2E, 5.4.1.2.2F m Registration abnormal cases (clause 5.4.1.2.3) 15.1 General procedures for handling of abnormal cases related to initial registration and user-initiated re-registration? Clause 5.4.1.2.3 m 15.2 Procedures for handling of abnormal cases related to initial registration and user-initiated re-registration when IMS AKA as security mechanism applies? Clause 5.4.1.2.3A m 15.2.1 On receipt of a REGISTER request, indicating that the SQN was deemed to be out of range by the UE (clause 5.4.1.2.3A, second dashed list) ... 15.2.1.1 Sends a 401 response? Clause 5.4.1.2.3A, second dashed list, first dash o.1 15.2.1.2 Sends a 403 response? Clause 5.4.1.2.3A, second dashed list, second dash o.1 ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 24 Item Major capability: Does the implementation support... Reference Status Support 15.3 Procedures for handling of abnormal cases related to initial registration and user-initiated re-registration when SIP digest as security mechanism applies? Clause 5.4.1.2.3B c.1 15.3.1 On receipt of a REGISTER request, that contains the authentication challenge response from the UE that does not match with the expected REGISTER request (clause 5.4.1.2.3B, first dashed list) ... 15.3.1.1 Sends a 403 response? Clause 5.4.1.2.3B, first dashed list, first dash o.2 15.3.1.2 Sends a 401 response? Clause 5.4.1.2.3B, first dashed list, second dash o.2 15.4 Procedures for handling of abnormal cases related to initial registration and user-initiated re-registration when SIP digest with TLS as security mechanism applies? Clauses 5.4.1.2.3C c.2 15.4.1 On receipt of a REGISTER request, that contains the authentication challenge response from the UE that does not match with the expected REGISTER request (clause 5.4.1.2.3B, first dashed list) ... 15.4.1.1 Sends a 403 response? Clause 5.4.1.2.3B, first dashed list, first dash o.3 15.4.1.2 Sends a 401 response? Clause 5.4.1.2.3B, first dashed list, second dash o.3 Deregistration, re-authentication, registration status notification, service profile updates (clauses 5.1.4 - 5.1.8) 16.1 Procedures for handling of normal cases related to user-initiated deregistration? Clause 5.4.1.4.1 m 16.2 Procedures for handling of abnormal cases related to user-initiated deregistration when IMS AKA as security mechanism applies? Clause 5.4.1.4.2 m 16.3 Procedures for handling of abnormal cases related to user-initiated deregistration when SIP digest as security mechanism applies? Clause 5.4.1.4.3 c.1 16.4 Procedures for handling of abnormal cases related to user-initiated deregistration when SIP digest with TLS as security mechanism applies? Clause 5.4.1.4.4 c.2 17 Network-initiated deregistration? Clause 5.4.1.5 m 18 Network-initiated re-authentication? Clause 5.4.1.6 m 19 Notification of AS about registration status? Clauses 5.4.1.7, 5.4.1.7A m 19.1 When building the To header of the REGISTER request to the AS (clause 5.4.1.7 c)) … 19.1.2 Insertion of a public user identity as contained in the REGISTER request received from the UE? Clause 5.4.1.7 c) o.4 19.1.2 Insertion of an implicitly registered public user identities from the service profile? Clause 5.4.1.7 c) o.4 20 Service profile updates? Clause 5.4.1.8 m 20.1 When receiving a service profile modifying Push-Profile-Request (clause 5.4.1.8, item 4)) … 20.1.1 Procedures for notification of the reg-event subscribers about the registration state? Clause 5.4.1.8, item 4) first dash o.5 20.1.2 Shortening the life time of the current registration? Clause 5.4.1.8, item 4) second dash o.5 Subscription and notification (clause 5.4.2) 21 Subscriptions to S-CSCF events? Clause 5.4.2.1 m 21.1 Procedures that apply on receipt of SUBSCRIBE request related to event providing registration state? Clause 5.4.2.1.1 m 21.2 Transmission of notifications about the event providing registration state? Clause 5.4.2.1.2 m 21.3 Procedures that apply on receipt of SUBSCRIBE request related to event providing debug state? Clause 5.4.2.1.3 m 21.4 Transmission of notifications about the debug configuration? Clause 5.4.2.1.4 m 22 Other subscriptions? Clause 5.4.2.2 o ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 25 Item Major capability: Does the implementation support... Reference Status Support Handling of requests for all dialogs and standalone transactions (clause 5.4.3) 23.1 General handling of requests initiated by the served user? Clause 5.4.3.2, before first numbered list m 23.2 Handling of the receipt of initial requests for a dialog or a standalone transaction from the served user? Clause 5.4.3.2, first numbered list m 23.3 Handling of the receipt of initial requests for a dialog or a standalone transaction from an AS acting on behalf of an unregistered user? Clause 5.4.3.2, second numbered list m 23.4 Rejection with retention procedure of initial requests for a dialog or a standalone transaction from the served user (without or with untrusted profile) upon failure of profile retrieval? Clause 5.4.3.2 third numbered list o 23.5 Handling of the responses (or the absence of responses) to initial requests for a dialog or a standalone transaction? Clause 5.4.3.2, all text between third and fifth numbered list m 23.6 Handling of the receipt of target refresh requests from the served user? Clause 5.4.3.2, fifth numbered list m 23.7 Handling of the 1xx and 2xx responses to target refresh requests? Clause 5.4.3.2, sixth and seventh numbered list m 24.1 General handling of requests terminated by the served user? Clause 5.4.3.3, before first numbered list m 24.2 Handling of the receipt of initial requests for a dialog or a standalone transaction for a registered user? Clause 5.4.3.3, first numbered list m 24.3 Specific handling of the responses (or the absence of responses) to initial requests for a registered user? Clause 5.4.3.3, all text between first and third numbered list m 24.4 Handling of the receipt of initial requests for a dialog or a standalone transaction for an unregistered user? Clause 5.4.3.3, third numbered list m 24.5 General handling of the responses to initial requests for a registered or unregistered user? Clause 5.4.3.3, fourth numbered list m 24.6 General handling of the responses to requests for standalone transaction for a registered or unregistered user? Clause 5.4.3.3, fifth and sixth numbered list m 24.7 Handling of the receipt of target refresh requests for the served user? Clause 5.4.3.3, seventh numbered list m 24.8 General handling of the 1xx and 2xx responses to target refresh requests for a registered or unregistered user? Clause 5.4.3.3, eighth numbered list m 24.6 Handling of the receipt of subsequent requests (other than target refresh) for the served user? Clause 5.4.3.3, ninth numbered list m 24.7 Handling of the 1xx and 2xx responses to subsequent requests? Clause 5.4.3.3, tenth numbered list m 25 Encoding of the original dialog identifier? Clause 5.4.3.4 m SIP digest authentication procedures 26 General procedures for SIP digest authentication for all requests other than REGISTER? Clause 5.4.3.6.1 c.5 26.1 Rejection of requests with a 400 response in case of mismatching public user identity? Clause 5.4.3.6.1, first numbered list, item 2) c.6 26.2 In case of receipt of a mismatching challenge response (clause 5.4.3.6.1, second numbered list) ... ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 26 Item Major capability: Does the implementation support... Reference Status Support 26.2.1 Rechallenging of requests with a 407 response? Clause 5.4.3.6.1, second numbered list, item 1) c.7 26.2.2 Rejection of requests with a 403 response? Clause 5.4.3.6.1, second numbered list, item 2) c.7 26.2.3 Rejection of requests without a response? Clause 5.4.3.6.1, second numbered list, item 3) c.7 27 Procedures for abnormal cases within SIP digest authentication for all requests other than REGISTER? Clause 5.4.3.6.2 m Call initiation (clause 5.4.4) 28.1 Additional requirements for INVITE requests from the served user? Clause 5.4.4.1 m 28.2 Additional requirements for INVITE requests for the served user? Clause 5.4.4.1 m 28.2.1 Application of periodic session refreshment on receipt of INVITE requests? Clause 5.4.4.1 o 28.2.2 Examination of the contents of the SDP offer within the INVITE requests for the served user? Clause 5.4.4.1, alphabetic list o 28.2.2.1 On detection of an unsupported IP address type (clause 5.4.4.1, dashed list)… 28.2.2.1.1 Rejection of the requests with a 305 response towards the I-CSCF? Clause 5.4.4.1, first dash c.8 28.2.2.1.2 Acceptance and forwarding of the request towards the IBCF? Clause 5.4.4.1, second dash c.8 29.1 Additional requirements for subsequent requests (UE-originating case)? Clause 5.4.4.2.1 m 29.1.1 Insertion of previously saved values into the P-Charging-Vector header and P-Charging-Function-Addresses header of requests and responses (other than ACK and CANCEL)? Clause 5.4.4.2.1, third paragraph o 29.2 Additional requirements for subsequent requests for the served user (UE-terminating case)? Clause 5.4.4.2.2 m 29.2.1 Insertion of previously saved values into the P-Charging-Vector header and P-Charging-Function-Addresses header of requests and responses (other than ACK and CANCEL)? Clause 5.4.4.2.2, third paragraph o Call release (clause 5.4.5) 30.1 S-CSCF initiated call release (clause 5.4.5.1) ... 30.1.1 Of sessions currently being established? Clause 5.4.5.1.1 m 30.1.2 Of existing sessions? Clause 5.4.5.1.2 m 30.1.3 Of existing dialogs due to registration expiration? Clause 5.4.5.1.2A m 30.1.4 Including abnormal cases? Clause 5.4.5.1.3 m 30.2 Call release initiated by other entities? Clause 5.4.5.2 m 30.3 Call release due to session expiry? Clause 5.4.5.3 m Call-related requests (clause 5.4.6) 31.1 Additional requirements for ReINVITE and UPDATE requests (UE-originating case)? Clause 5.4.6.1.2 m 31.2 Additional requirements for ReINVITE and UPDATE requests for the served user (UE-terminating case)? Clause 5.4.6.1.3 m GRUU management (clause 5.4.7A) 32 GRUU management? Clause 5.4.7A m 32.1 Construction of public GRUUs? Clause 5.4.7A.2 m 32.2 Construction of temporary GRUUs? Clause 5.4.7A.3 m 32.2.1 Temporary GRUUs without the need for extra states? Clause 5.4.7A.3 o.8 32.2.2 Stateful representation of temporary GRUUs? Clause 5.4.7A.3 o.8 32.3 GRUU recognition and validity checking? Clause 5.4.7A.4 m ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 27 Item Major capability: Does the implementation support... Reference Status Support Emergency service (clause 5.4.8) (see note 2) 33.1 Additional procedures for requests for initial emergency registration or user-initiated emergency reregistration? Clause 5.4.8.2 m 33.2 Rejection of user-initiated emergency deregistration requests? Clause 5.4.8.3 S-CSCF specific application usage of SDP (clause 6.3) 34.1 Handling of requests including SDP offers? Clause 6.3 m 34.1.1 Rejection of requests including encrypted SDP offers? Clause 6.3, first paragraph o 34.2 Handling of responses (other than 200OK) including SDP offers? Clause 6.2, second paragraph m 34.2.1 Rejection of requests following non-200OK responses including encrypted SDP offers? Clause 6.3, second paragraph o 34.3 Handling of 200OK responses including SDP offers? Clause 6.2, third paragraph m 34.3.1 Session termination on receipt of encrypted SDP offers in 200OK responses? Clause 6.2, third paragraph o Additional routeing capabilities in support of transit and interconnection traffics in IM CN subsystem (Annex I) 35 Additional routeing capabilities? Annex I o IP-Connectivity Access Network specific concepts when using cdma2000® packet data subsystem to access IM CN subsystem (Annex M) 36 Additional procedures for notification of the AS about the registration status? Clause M.3.3.1 m IP-Connectivity Access Network specific concepts when using the EPC via cdma2000® HRPD to access IM CN subsystem (Annex O) 37 Additional procedures for notification of the AS about the registration status? Clauses O.3.3, M.3.3.1 m NOTE 1: The S-CSCF shall provide the UA role when acting as registrar or notifier of event information, when providing a messaging mechanism by sending the MESSAGE method and when performing S-CSCF initiated dialog release. NOTE 2: See also PICS item A.6/6. o.n At least one of these capabilities shall be supported. c.1 m, if A.6/3.2 or A.6/3.3 is supported, else o c.2 m, if A.6/3.4 is supported, else o c.3 m, if A.6/3.5 is supported, else o c.4 m, if A.6/3.6 is supported, else o c.5 o, if 6/3.2 or A.6/3.3 or A.6/3.4 is supported, else n/a c.6 o, if 6/3.26 is supported, else n/a c.7 o.6, if 6/3.26 is supported, else n/a c.8 o.7, if A.6/28.2.2 is supported, else n/a A.5.4.2 S-CSCF header handling Table A.7: S-CSCF Header Handling Item Header handling: Does the implementation support... Reference Status Support 1 The Path header in REGISTER request and related 200OK response messages? Clause 5.4.1.1 m 2 The Service-Route header in 200OK response messages to REGISTER requests? Clause 5.4.1.1 m 3 The Require header? Clause 5.4.1.1 m 4 The Supported header? Clause 5.4.1.1 m ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 28 A.5.5 IBCF Role The tables provided in this clause need only to be completed for IBCF implementations, where item A.2/4 above is supported. A.5.5.1 IBCF Capabilities Table A.8: IBCF Capabilities Item Major capability: Does the implementation support... Reference Status Support General Capabilities (clause 4) 1 The proxy role with IMS related exceptions and additional capabilities to SIP? Clauses 4.1, 5.10 m 2 Provision of application level gateway functionality? Clause 4.1 o 3 Provision of screening functionality? Clause 4.1 o 4.1 The UA role with IMS related exceptions and additional capabilities to SIP? Clauses 4.1, 5.10 c.1 4.2 The UA role with IMS related exceptions and additional capabilities to SDP? Clauses 4.1, 6.7 c.2 5.1 The loose routeing policy? Clause 4.3, RFC 3261 [2] m 5.2 Interoperability with strict routers? Clause 4.3, RFC 3261 [2] and clauses 12.2.1.1, 16.4 m 6 Procedures related to emergency services? Clause 4.7 m 7 Tracing of signalling? Clause 4.8 o 8 Priority mechanisms? Clause 4.11 m IBCF specific application usage of SIP (clause 5.10) 9 Procedures when acting as exit point (clause 5.10.2) ... 9.1 Procedures that apply on receipt of a REGISTER request when acting as exit point? Clause 5.10.2.1 m 9.2 Provision of priority over other transactions or dialogs based on the Resource-Priority header for all request types when acting as exit point? Clause 5.10.2.1A c.3 9.3 Procedures that apply on receipt of initial requests, standalone requests (other than REGISTER) and unknown method requests when acting as exit point? Clause 5.10.2.2 m 9.3.1 Application of periodic session refreshment on receipt of INVITE requests when acting as exit point? Clause 5.10.2.2 o 9.4 Procedures that apply on receipt of a responses to initial requests when acting as exit point? Clause 5.10.2.2 m 9.5 Procedures that apply on receipt of subsequent requests when acting as exit point? Clause 5.10.2.3 m 9.6 Procedures that apply on receipt of responses to subsequent requests when acting as exit point? Clause 5.10.2.3 m 9.7 Provision of transport plane control functionality when acting as exit point? Clause 5.10.2.4 o 9.7.1 IBCF-initiated call release in case of receipt of an indication of a transport plane related error when acting as exit point? Clause 5.10.2.4 c.4 10 Procedures when acting as entry point (clause 5.10.3) ... 10.1 Procedures that apply on receipt of a REGISTER request when acting as entry point? Clause 5.10.3.1 m 10.2.1 Provision of priority over other transactions or dialogs based on the Resource-Priority header for all request types when acting as entry point? Clause 5.10.3.1A c.3 10.2.1 Provision of priority over other transactions or dialogs based on the alternative mechanism to recognize the need for priority treatment for all request types when acting as entry point? Clause 5.10.3.1A c.3 ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 29 Item Major capability: Does the implementation support... Reference Status Support 10.3 Procedures that apply on receipt of initial requests, standalone requests (other than REGISTER) and unknown method requests when acting as entry point? Clause 5.10.3.2 m 10.3.1 Application of periodic session refreshment on receipt of INVITE requests when acting as entry point? Clause 5.10.3.2 o 10.4 Procedures that apply on receipt responses to initial requests when acting as entry point? Clause 5.10.3.2 m 10.5 Procedures that apply on receipt of subsequent requests when acting as entry point? Clause 5.10.2.3 m 10.6 Procedures that apply on receipt of responses to subsequent requests when acting as entry point? Clause 5.10.3.3 m 10.7 Provision of transport plane control functionality? Clause 5.10.3.4 o 10.7.1 IBCF-initiated call release in case of receipt of an indication of a transport plane related error? Clause 5.10.3.4 c.5 11 Procedures for network topology hiding? Clause 5.10.4 m 11.1 Inclusion of a direction identifier to an IBCF-inserted SIP URI? Clauses 5.10.4.1, 5.10.2.1 and 5.10.3.1 o 11.2 Encryption for network topology hiding? Clause 5.10.4.2 m 11.3 Decryption for network topology hiding? Clause 5.10.4.3 m 12 IMS-ALG functionality? Clauses 5.10.5, 6.7 o 13 Screening of SIP signalling? Clause 5.10.6 m 13.1 B2BUA functionality when performing screening of the SIP signalling? Clauses 5.10.6.1, 5.10.5 o 13.2 Omission or modification of received SIP headers prior to forwarding SIP messages? (see note) Clause 5.10.6.2 o 13.3 Omission or modification of received SDP bodies prior to forwarding SIP messages? Clause 5.10.6.3 o 14 Media transcoding control? Clause 5.10.7 o 14.1 Addition one or more codecs at the end of the codec list in the selected media of request before forwarding the request to the answerer? Clause 5.10.7.1 c.6 14.2 Inspection and treatment of codec entries in responses received from the answerer? Clause 5.10.7.1 c.7 15 Privacy protection at the trust domain boundary? Clause 5.10.8 m 16 procedures for the support of ICE in IMS-ALG within the IBCF? Clause 6.7.1.2 c.8 16.1 Procedures for the support of ICE in IMS-ALG within the IBCF? Clause 6.7.1.2.1 c.9 16.1.1 Procedures when no TrGW is inserted? Clause 6.7.1.2.1 c.9 16.1.2 Procedures when a TrGW is attached? Clause 6.7.1.2.1 c.9 16.2 IMS-ALG in IBCF full ICE procedures for UDP based streams? Clause 6.7.1.2.2 c.9 16.3 IMS-ALG in IBCF lite ICE procedures for UDP based streams? Clause 6.7.1.2.3 c.9 16.4 IMS-ALG in IBCF ICE procedures for TCP based streams? Clause 6.7.1.2.4 c.9 Additional routeing capabilities in support of transit and interconnection traffics in IM CN subsystem (Annex I) 17 Additional routeing capabilities? Annex I o NOTE: The modification of the following headers is discouraged by TS 124 229 [1]: Authorization, WWW-Authenticate, Path and Service-Route headers. c.1 m, if A.8/2 is supported, else o c.2 m, if A.8/2 is supported, else n/a c.3 m, if A.8/8 is supported, else o c.4 o, if A.8/9.7 is supported, else n/a c.5 o, if A.8/10.7 is supported, else n/a c.6 o, if A.8/14 is supported, else n/a c.7 m, if A.8/14 is supported, else n/a c.8 o, if A.8/12 is supported, else n/a c.9 o, if A.8/16.1 is supported, else n/a ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 30 A.5.6 E-CSCF Role The tables provided in this clause need only to be completed for E-CSCF implementations, where item A.2/5 above is supported. A.5.6.1 E-CSCF Capabilities Table A.9: E-CSCF Capabilities Item Major capability: Does the implementation support... Reference Status Support General Capabilities (clause 4) 1.1 The proxy role with IMS related exceptions and additional capabilities to SIP? Clauses 4.1, 5.11 m 1.2 The UA role when providing server functionality to return a final response? Clause 4.1 m 2.1 The loose routeing policy? Clause 4.3, RFC 3261 [2] m 2.2 Interoperability with strict routers? Clause 4.3, RFC 3261 [2] and clauses 12.2.1.1, 16.4 m 3 Procedures related to charging? Clause 4.5 m 6 Procedures related to emergency services? Clauses 4.7, 5.11 m 7 Tracing of signalling? Clause 4.8 o E-CSCF specific application usage of SIP (clause 5.11) 8 General procedures related to emergency services? Clause 5.11.1 m 8.1 Acceptance and onwards routeing of requests (initial requests for a dialog, for a standalone transaction, or for an unknown method) for emergency services? (see note) Clause 5.11.2 m 8.2 Rejection of requests for non-emergency services? (see note) Clause 5.11.2 m 8.3 Insertion of previously saved values into the P-Charging-Vector and P-Charging-Function header of requests and responses (other than CANCEL and ACK) to be forwarded? Clause 5.11.2 o 8.4 Procedures that apply on receipt of responses to requests (initial requests for a dialog, for a standalone transaction, or for an unknown method) for emergency services? Clause 5.11.2 m 8.5 Application of periodic session refreshment on receipt of INVITE requests? Clause 5.11.2 o 9 Emergency services procedures that require the use of an LRF? Clause 5.11.3 m 10 Procedures for subscriptions to E-CSCF events? Clause 5.11.4 m 10.1 Processing of subscriptions to the event providing dialog state? Clause 5.11.4.1 m 10.2 Provision of notifications about dialog states? Clause 5.11.4.2 m NOTE: Request for emergency services contain an URN with a top-level service type of "sos". ETSI ETSI TS 102 790-1 V2.1.1 (2012-11) 31 History Document history V1.1.1 March 2010 Publication V2.1.1 November 2012 Publication
|
2d8a87bbce8161354cc3b7cef0fdf7f5
|
102 710-2
|
1 Scope
|
The present document specifies the Test Suite Structure and Test Purposes for SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks based on TS 129 163 [1] (Release 8).
|
2d8a87bbce8161354cc3b7cef0fdf7f5
|
102 710-2
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced 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.
|
2d8a87bbce8161354cc3b7cef0fdf7f5
|
102 710-2
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 163: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 Release 8)". [2] ETSI TS 102 710-1: "IMS Network Testing (INT); Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (Release 8); Part 1: Protocol Implementation Conformance Statement (PICS)". [3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [4] Recommendation ITU-T T.38: "Procedures for real-time Group 3 facsimile communication over IP networks". [5] Recommendation ITU-T Q.850: "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN user part".
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.