hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in [1] and the following apply: ACR-CB Anonymous Communication Rejection- Communication Barring ISC IM-CN Service Control IUT Implementation Under Test NNI Network Network Interface PIXIT Protocol Implementation eXtra Information for Testing SIP Session ... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 4 Test Suite Structure (TSS) and configuration | Netw TransferorAS ECT_N01_xxx TransfereeAS ECT_N02_xxx User Transferor ECT_U01_xxx Transferee ECT_U02_xxx TransferTarget ECT_U03_xxx Interaction OIR ECT_N03_xxx ACR-CB ECT_N04_xxx CONF ECT_N05_xxx ECT ECT_N06_xxx Figure 4.1: Test suite structure |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 4.1 Configuration | The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as described in [1]. The stage 3 description respects the requirements to several network entities and also to requirements regarding to end devices. Therefore several interfaces (reference points) are address... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5 Test Purposes (TP) | |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.1 Introduction | For each test requirement a TP is defined. |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 5.1.1). Table 5.1.1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> ... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.1.2 Test strategy | As the base standard [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification [2]. ETSI ETSI TS 101 594-2 V5.1.1 (2012-10) 9 |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2 Signalling requirements | |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.1 Actions at the Transferor UE | TSS User/Transferor TP ECT_U01_001 Reference 4.5.2.1 Selection expression PICS 4.5.1/1 AND PICS 4.6.1/1 Test purpose The UE transfers a communication with a Transferee to the Transfer Target (Transferor, blind transfer). Ensure that the UE is able to transfer a communication with the Transferee, optionally put on hold ... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.2 Actions at the Transferor AS | TSS Netw/TransferorAS TP ECT_N01_001 Reference 4.5.2.4 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/2 AND NOT (PICS 4.7.1/4 OR PICS 4.7.1/5) Test purpose Communication transfer: Assured transfer. Transferor was originator of the originating call. Ensure that a Transferor can successfully transfer the communication ... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.3 Actions at the Transferee UE | TSS User/Transferee TP ECT_U02_001 Reference 4.5.2.5 Selection expression PICS 4.5.1/1 AND (PICS 4.6.1/1 OR PICS 4.6.1/2) AND PICS 4.6.1/5 Test purpose The User Equipment receives the request to establish a communication to the transfer target (Transferee Blind/assured transfer) Ensure that the UE establishes a session... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.4 Action at the Transferee AS | TSS Netw/TransfereeAS TP ECT_N02_001 Reference 4.5.2.7 Selection expression PICS 4.5.1/2 Test purpose Communication transfer: Assured transfer applicable at the Transferee AS. Ensure that the Transferee AS can act as a proxy when receives the REFER request, the INVITE request and the BYE request for the call that is tr... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.5 Actions at the transfer target's UE | TSS User/TransferTarget TP ECT_U03_001 Reference 4.5.2.17 Selection expression PICS 4.5.1/1 AND Test purpose The User Equipment receives the request to terminate a communication to the transferor. Ensure that a User Equipment in a confirmed session receives an INVITE request to establish a new session that and a Replac... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.6 Interaction with other services | |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.6.1 Originating identification restriction (OIR) | TSS Interaction/OIR TP ECT_N03_001 Reference 4.6.5 Selection expression PICS 4.5.1/2 AND PICS 7.7.2/1 Test purpose Referred-By header Privacy regarding the requested privacy for the P-Asserted-Identity. Ensure that a Privacy header is present and the value 'user' is included in addition if the Privacy header was receiv... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.6.3 CONFerence Calling (CONF) | TSS Interaction/CONF TP ECT_N05_001 Reference 4.6.6 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 AND PICS 7.7.2/3 Test purpose ECT does not apply if the Refer-To header of the REFER request dialogue contains the URI targeted a conference invited by REFER. Ensure that ECT does not apply if the "Isfocue" parameter ... |
9c9040046fb0b6b58964d63a2286c73c | 101 594-2 | 5.2.6.4 Explicit Communication Transfer (ECT) | TSS Interaction/ECT TP ECT_N06_001 Reference 4.6.10.2, 4.6.10.3 Selection expression PICS 4.5.1/2 AND PICS 4.7.1/1 Test purpose Interaction with ECT: Blind transfer. A session between ISC#1 and ISC#2 exists and was transferred before. Ensure that if the INVITE dialog on which the REFER is received is a previously trans... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the protocol specification as defined in ETSI TS 124 629 [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 [2]. |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-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 referenced document (including any amendments) applies. Referenced documents which a... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 629: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; P... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 124 607: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Originating Identific... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 3 Definitions, symbols and abbreviations | |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 629 [1], ETS 300 406 [2], ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system claimed to conform to a given specificat... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in [1] apply. |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in [1] and the following apply: ICS Implementation Conformance Statement IUT Implementation Under Test PICS Protocol ICS SUT System Under Test UE User Equipment URI Uniform Resource Identifier |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4 PICS proforma for TS 124 629 | Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PICS proforma in this clause so that it can be used for its intended purposes and may further publish the completed PICS. |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.1 Guidance for completing the PICS proforma | |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.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 629 [1] may provide information about the implementation in a standardized manner. ETSI ETSI TS 101 594-1 V5.1.1 (2012-10) 7 The PICS proforma is subdivided into clauses for the foll... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.1.2 Abbreviations and conventions | The PICS proforma contained in this clause 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 ... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.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 4.1.2. However, the tables containing in "user role" clause shall only be completed... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.2 Identification of the implementation | Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if ... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.2.1 Date of the statement | ......................................................................................................................................................................................... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: ......................................................................................................................................................................................... ............................................................................................................................... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.2.3 System Under Test (SUT) identification | SUT name: ......................................................................................................................................................................................... ............................................................................................................................... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.2.4 Product supplier | Name: ......................................................................................................................................................................................... Address: .......................................................................................................................... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.2.5 Client (if different from product supplier) | Name: ......................................................................................................................................................................................... Address: .......................................................................................................................... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.2.6 PICS contact person | (A person to contact if there are any queries concerning the content of the ICS) Name: ......................................................................................................................................................................................... Telephone number: ................................ |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.3 Identification of the TS 124 629 | This PICS proforma applies to the following standard: ETSI TS 124 629 (2011-05): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.4 Global statement of conformance | Are all mandatory capabilities implemented? (Yes/No) ..................... NOTE: Answering "No" to this question indicates non-conformance to the <reference specification type> specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conf... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.5 Roles | Table 4.5.1: Roles Item Role Reference Status Support 1 User Equipment 4.4 o.1 2 Network (Application Server) 4.5 o.1 o..1: It is mandatory to support exactly one of these items. Comments: |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.6 User Equipment role | This clause contains the PICS proforma tables related to the User Equipment role. They need to be completed only for user implementations: Prerequisite: 4.5.1/1 -- user role |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.6.1 Major capabilities | Table 4.6.1: Major capabilities Item Item description Reference Status Support 1 Is the blind transfer supported? 5.11.6 [5] o.11 2 Is the assured transfer supported? 5.11.6 [5] o.11 3 Is the consultative transfer supported? 5.11.6 [5] o.11 4 [Transferor] Is the UE able to Issue a REFER request in the original communic... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.7 Network role | This clause contains the PICS proforma tables related to the Application Server role. They need to be completed only for network implementations: Prerequisite: 4.5.1/2 -- network role |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.7.1 Major capabilities | Table 4.7.1: Major capabilities Item Item description Reference Status Support 1 Is the blind transfer supported? 5.11.6 [5] o.21 2 Is the assured transfer supported? 5.11.6 [5] o.21 3 Is the consultative transfer supported? 5.11.6 [5] o.21 4 The AS initiate the special REFER handling procedures when a 403 Forbidden or... |
d7be5559bd20fb33f9aa3cf72a47f0b9 | 101 594-1 | 4.7.2 Supplementary service capabilities | Table 4.7.2: Supplementary service capabilities Item Item description Reference Status Support 1 Does the network supports the Originating Identification Restriction (OIR) supplementary services? [i.1] o 2 Does the Network supports the Anonymous Communication Rejection (ACR) and Communication Barring (CB) supplementary... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 1 Scope | The present document specifies the test suite structure and test purposes of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service, based on stage three of the IMS simulation services. Within the Next Generation Network (NGN) the stage 3 descri... |
e871d60fd728df1e61851585ff9b650b | 101 588-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 ar... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 642: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No... |
e871d60fd728df1e61851585ff9b650b | 101 588-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. Not applicable. |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 3 Definitions, symbols and abbreviations | |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 642 [1] apply. ETSI ETSI TS 101 588-2 V5.1.1 (2012-10) 6 |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in TS 124 642 [1] apply. |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 642 [1] apply. |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 4 Test Suite Structure (TSS) | Table 4-1: Test Suite Structure CC originating_AS Invocation CC_N01_xxx Revocation CC_N02_xxx Operation CC_N03_xxx terminating_AS possibleIndication CC_N04_xxx Invocation CC_N05_xxx Revocation CC_N06_xxx CCOperation CC_N07_xxx Interaction TIR CC_N08_xxx CDIV CC_N09_xxx |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 4.1 Configuration | The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as described in [1]. The stage 3 description respects the requirements to several network entities and also to requirements regarding to end devices. Therefore several interfaces (reference points) are address... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5 Test Purposes (TP) | |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.1 Introduction | For each test requirement a TP is defined. |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.1.1 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 5-1). Table 5-1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss>... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.1.2 Test strategy | As the base standard TS 124 642 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 101 588-1 [2]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered. |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.2 Actions at the originating AS | |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.2.1 CC Invocation | TSS CC/originating_AS/Invocation TP CC_N01_001 Reference 4.5.4.2.1.1.1, 4.5.4.2.1.1.3 Selection expression PICS 4.3.2-1/9 Test purpose Detecting CCNL is possible. Ensure that when an originating user establishes a session to a terminating user not logged in, a 183 (Session Progress) response is forwarded to the origina... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.2.2 CC Revocation | TSS CC/originating_AS/Revocation TP CC_N02_001 Reference 4.5.4.2.2.1.2 Selection expression PICS 4.3.2-1/8 Test purpose CCBS revocation request received from the user. Ensure that the originating AS sends a SUBCRIBE request and the Expires header is set to zero when the originating user revokes the outstanding CCBS req... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.2.3 CC Operation | TSS CC/originating_AS/Operation TP CC_N03_001 Reference 4.5.4.2.3.1 Selection expression NOT PICS 4.3.2-1/4 Test purpose CCBS Recall successful by sending a REFER request to the originating user. Ensure that the originating AS starts the CCBS recall procedure when the indication that the callee is available to recall i... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.3 Actions at the terminating AS | |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.3.1 CC possible indication | TSS CC/terminating_AS/possibleIndication TP CC_N04_001 Reference 4.5.4.3.1.1 Selection expression Test purpose The terminating AS inserts a Call-Info header in the 486 final response received from the terminating user. Ensure that the terminating AS inserts a Call-Info header and the purpose parameter is set to call-co... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.3.2 CC Invocation | TSS CC/terminating_AS/Invocation TP CC_N05_001 Reference 4.5.4.3.2.1 Selection expression Test purpose CCBS service invocation successful at the terminating AS. Ensure that the terminating AS is able to queue the CCBS request received in a SUBSCRIBE request from the originating AS and responds with a NOTIFY request. In... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.3.3 CC Revocation | TSS CC/terminating_AS/Revocation TP CC_N06_001 Reference 4.5.4.3.3.1 Selection expression Test purpose CCBS service revocation successful at the terminating AS. Ensure that the terminating AS is able to respond a NOTIFY request and the Subscription-State header is set to terminated and the reason parameter is set to ti... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.3.4 CC Operation | TSS CC/terminating_AS/CCOperation TP CC_N07_001 Reference 4.5.4.3.4.1.1, 4.5.4.3.4.1.2 Selection expression Test purpose Callee becomes not busy, CCBS recall procedure performed. Ensure that the terminating AS starts the call completion recall procedure if the callee becomes not busy. The terminating AS starts the Dest... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.4 Interaction of Call-Completion with other services | |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.4.1 Terminating Identification Restriction (TIR) | TSS CC/ Interaction/TIR TP CC_N08_001 Reference 4.6.4 Selection expression PICS 4.3.2-1/4 Test purpose CCBS, CCNR, CCNL Recall successful by using the special REFER interworking. TIR settings considered in the CC recall. Ensure that the originating AS starts the CCBS recall procedure and in the 200 OK INVITE from the o... |
e871d60fd728df1e61851585ff9b650b | 101 588-2 | 5.4.2 Communication diversion services (CDIV) | TSS CC/Interaction/CDIV TP CC_N09_001 Reference 4.6.8.2 Selection expression Test purpose Detecting CCBS is possible. Ensure that when an originating user establishes a session to User B and the user B has activated communication diversion unconditional to user C, the terminating user C is busy, a 486 (Busy Here) respo... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 1 Scope | The present document specifies the protocol implementation conformance statement of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service, based on stage three of the IMS simulation services. Within the Next Generation Network (NGN) the stage 3... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-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 referenced document (including any amendments) applies. Referenced documents which ar... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 642: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-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. ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 6 |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 3 Definitions, symbols and abbreviations | |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 642 [1], ETS 300 406 [2], ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or system claimed to conform to a given specificat... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in TS 124 642 [1] apply. |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 642 [1] and the following apply: ICS Implementation Conformance Statement IUT Implementation Under Test SCS System Conformance Statement SUT System Under Test PICS Protocol ICS 4 Protocol Implementation Conformance Statement proforma Notwithsta... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.1 Instructions for completing the PICS proforma | 4.1.1 More detailed instructions are given at the beginning of the different clauses of the PICS proforma The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5. |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.1.1.1 Purposes and structure | The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in reference specification [1] may provide information about the implementation in a standardized manner. ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 7 The PICS proforma is subdivided into clauses... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.1.2 Abbreviations and conventions | The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [4]: Item column It contains a number that identifies the item in the table. Item description column It describes each respective item (e.g. parameters, timers, etc.). Reference column It gives ref... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.2 Identification of the implementation | Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if ... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.2.1 Date of the statement | Date of the statement: |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 9 |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.3 PICS proforma tables | |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.3.1 Global statement of conformance | Table 4.3.1-1: Global statement of conformance (Yes/No) Are all mandatory capabilities implemented? |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 4.3.2 Network capabilities | Table 4.3.2-1: Network capabilities Item Item description Reference Status Support 1 Is the CCBS/CCNR request retention option supported? 4.5.4.2.3.2.4/ [1] o 2 Is the retain option supported? 4.5.4.3.4.2/ [1] o 3 Is it possible to activate a further CCBS or CCNR request for an identical communication, determined by th... |
49ab0451e991beb8c5c85fc26ebffe7a | 101 588-1 | 5 Additional informations for PICS | If necessary, the supplier may provide additional comments in this clause. ETSI ETSI TS 101 588-1 V5.1.1 (2012-10) 11 History Document history V5.1.1 October 2012 Publication |
7f110eeff44cca5c59b5fc967e08482a | 101 585 | 1 Scope | The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for IMS interconnection tests at the Ic Interface to verify the overall compatibility of SIP, ISDN and non-ISDN (PSTN) over the national or international networks when using End Devices. The TSS&TP specification covers the procedures des... |
7f110eeff44cca5c59b5fc967e08482a | 101 585 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
7f110eeff44cca5c59b5fc967e08482a | 101 585 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Inter-IMS Network to Network Interface (NNI) (3GPP TS 29.165 Release 10)". [2] ETSI TS 124 22... |
7f110eeff44cca5c59b5fc967e08482a | 101 585 | 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 EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer... |
7f110eeff44cca5c59b5fc967e08482a | 101 585 | 3 Definitions and abbreviations | |
7f110eeff44cca5c59b5fc967e08482a | 101 585 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: BICC or ISUP specific terminology, references to Recommendation ITU-T Q.1902.2 [i.4]. For SIP and SDP specific terminology, references to RFC 3261 [4] and RFC 4566 [3] respectively. Definitions for additional terminology used in this i... |
7f110eeff44cca5c59b5fc967e08482a | 101 585 | 3.1.1 Conventions for representation of SIP/SDP information | 1) All letters of SIP method names are in capital. EXAMPLE 1: INVITE, INFO. 2) SIP header fields are identified by the unabbreviated header field name as defined in the relevant RFC, including capitalization and enclosed hyphens but excluding the following colon. EXAMPLE 2: To, From, Call-ID. 3) Where it is necessary t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.