hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 5 Test Suite Structure (TSS) | The Test Suite Structure is in close alignment with ES 283 027 [1]. |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 5.1 Interworking from SIP to ISUP (outgoing call) | SIP-ISUP Basic call Sending of the Initial address message (IAM) 101xxx Sending of the Subsequent address message (SAM) 102xxx Sending of COT 103xxx Receipt of the Address complete message (ACM) 104xxx Receipt of the Call progress message (CPG) 105xxx Receipt of the answer message (ANM) 106xxx Receipt of the Connect me... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 5.2 Interworking from ISUP to SIP (incoming call) | ISUP-SIP Basic call Sending of the INVITE message 301xxx Receipt of the Subsequent address message (SAM) 302xxx Sending of the Address complete message (ACM) 303xxx Sending of the Call progress message (CPG) 304xxx Sending of the answer message (ANM) 305xxx Sending of the Connect message (CON) 306xxx Receipt of the Rel... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6 Test purposes (TP) | |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.1 Introduction | For each test requirement a Test Purpose (TP) is defined. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 12 |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.1.1 Test purpose (TP) naming convention | For each test requirement a Test Purpose (TP) is defined. All test purposes belong to the main group ISUP_SIP_Interworking. Groups are organized according to the test suite structure (TSS). Each test purpose is presented in a separate table. The first row of the table contains the following items: TP Identifier of the ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.1.2 Source of test purpose definition | The test purposes have been developed based on ES 283 027 [1] as an endorsement of TS 129 163 [2]. |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.1.3 Test purpose structure | The test purpose structure is according to the test suite structure (TSS). |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2 Test purposes for the basic call | |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1 Interworking from SIP to ISUP (Outgoing Call) | |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.1 Sending of the Initial Address Message (IAM) | TP101001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.1 TSS reference: SIP-ISUP/Basic call/ Sending of the Initial Address message (IAM)/ SIP selection criteria: ISUP selection criteria: Test purpose: Normal call setup without precondition requirement Ensure that if the SIP precondition ex... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.2 Overlap procedure at the I-MGCF | TP102001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.1 TSS reference: SIP-ISUP/Basic call/Sending of the Subsequent address message (SAM)/ SIP selection criteria: ISUP selection criteria: Test purpose: Overlap sending successful at the I-MGCF Ensure that the SUT receives an INVITE with ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.3 Sending of COT | TP103001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.3 TSS reference: SIP-ISUP/Basic call/ COT SIP selection criteria: PICS 4/4 AND PICS 4/5 ISUP selection criteria: PICS 1/5 AND PICS 4/1 Test purpose: COT is sent after precondition met If the IAM has already been sent, the Continuity mes... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.4 Receipt of the Address Complete Message (ACM) | TP104001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.4 TSS reference: SIP-ISUP/Basic call/ Receipt of the Address complete message (ACM)/ SIP selection criteria: NOT PICS 4/15 ISUP selection criteria: Test purpose: Early ACM not interworked Ensure that the SUT on receipt of an ACM message... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.5 Receipt of the Call progress message (CPG) | TP105001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.4 TSS reference: SIP-ISUP/Basic call/ Receipt of the Call progress message (CPG). SIP selection criteria: NOT PICS 4/15 ISUP selection criteria: Test purpose: CPG Alerting is mapped into a 180 ringing Ensure that the SUT, having receive... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.6 Receipt of the Answer message (ANM) | TP106001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.5 ETS 300 356-1 [28], clause 2.1.7 TSS reference: SIP-ISUP/Basic call/ Receipt of the Answer message (ANM). SIP selection criteria: ISUP selection criteria: Test purpose: ANM received, a 200 OK INVITE is sent Ensure that the SUT, having... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.7 Receipt of the Connect message (CON) | TP107001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.5 TSS reference: SIP-ISUP/Basic call/ Receipt of the CONNECT message (CON). SIP selection criteria: PICS 4/1 AND PICS 4/4 AND PICS 4/5 ISUP selection criteria: Test purpose: CON received, 200 OK INVITE is sent after Preconditions are me... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.8 Receipt of the REL message | TP108001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: SIP-ISUP /Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: REL received after IAM was sent. Mapping into final response containing a Reason header Ensure t... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.9 Autonomous release at I-MGCF | TP109001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8.10 TSS reference: SIP-ISUP/Basic call/ Autonomous release at I-MGCF SIP selection criteria: ISUP selection criteria: PICS 3/3 AND NOT PICS 3/4 Test purpose: Overlap not supported, 484 is sent if insufficient digits received in the INV... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.10 Receipt of the Release message BYE / CANCEL | TP110001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.6 TSS reference: SIP-ISUP/Basic call/ Receipt of the BYE message SIP selection criteria: ISUP selection criteria: Test purpose: BYE with Reason header received, sending of REL Ensure that the SUT on receipt of SIP BYE, the SUT shall sen... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.12 Receipt of the Suspend message (SUS) network initiated | Void. |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.1.13 Receipt of the Resume message (RES) network initiated | Void. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 95 |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2 Interworking from ISUP to SIP | |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.1 Sending of the INVITE message | TP301001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.1.4 TSS reference: ISUP-SIP /Basic call/Sending of the INVITE message SIP selection criteria: ISUP selection criteria: Test purpose: IAM contains the complete Called party number and the sending complete indication, sending of INVITE En... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.2 Receipt of the SAM message after INVITE has been send | TP302001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.1.4 TSS reference: ISUP-SIP/Basic call/Receipt of SAM after INVITE has been sent SIP selection criteria: PICS 3/1 ISUP selection criteria: PICS 3/5 AND NOT PICS 3/8 Test purpose: Overlap procedure not supported, SAM is ignored Ensure if... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.3 Sending of the ACM message | TP303001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clauses 7.2.3.2.1.4, 7.2.3.2.4 and 7.2.3.2.5 TSS reference: ISUP-SIP /Basic call/Sending of the ACM message SIP selection criteria: PICS 3/1 ISUP selection criteria: PICS 4/9 AND NOT PICS 4/17 Test purpose: ACM is sent after the determination of addre... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.4 Sending of the CPG message | TP304001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.6 TSS reference: ISUP-SIP /Basic call/ Sending of the CPG message SIP selection criteria: PICS 3/1 ISUP selection criteria: PICS 4/9 Test purpose: 180 received, a CPG is sent when an ACM was sent before Ensure that the SUT, having sent ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.5 Sending of the ANM message | TP305001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.7a TSS reference: ISUP-SIP/Basic call/ Sending of the Answer Message (ANM)/ SIP selection criteria: ISUP selection criteria: Test purpose: An ANM is sent after a 200 OK INVITE is received Ensure that the SUT having sent the ACM message,... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.6 Sending of the CON message | TP306001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.5 TSS reference: ISUP-SIP/Basic call/ Sending of the Connect Message (CON)/ SIP selection criteria: ISUP selection criteria: NOT PICS 4/9 Test purpose: CON is sent after 200 was received Ensure that the SUT, having not sent the ACM mess... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.7 Receipt of the Release message (REL) | TP307001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.8 TSS reference: ISUP-SIP/Basic call/ Receipt of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: REL received before INVITE was sent Ensure that the SUT after receiving the IAM but before an INV... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.8 Sending of a REL message / receipt of a backward BYE | TP308001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.7 TSS reference: ISUP-SIP /Basic call/ Sending of the Release message (REL)/ SIP selection criteria: ISUP selection criteria: Test purpose: BYE received, REL cause #16 is sent Ensure that the SUT after receiving the IAM sends out an INV... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.9 Autonomous release at O-MGCF | TP309001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.12.1 TSS reference: ISUP-SIP/Basic call/Autonomous release/ SIP selection criteria: PICS 3/2 ISUP selection criteria: Test purpose: Overlap supported, REL is sent when 404/484 received and Ti/w3 is expired Ensure that the SUT on receipt... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.10.1 Receipt of Reset Circuit message (RSC) | TP310001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Reset circuit message (RSC) SIP selection criteria: ISUP selection criteria: Test purpose: RSC received while an INVITE was not sent Ensure that the SUT after receiving the IAM but befor... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.10.2 Receipt of Circuit group reset message (GRS) | TP311001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group reset message (GRS) SIP selection criteria: ISUP selection criteria: Test purpose: GRS received while an INVITE was not sent Ensure that the SUT after receiving the IAM but... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.2.2.10.3 Receipt of Circuit group blocking message (CGB) | TP312001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.2.15 TSS reference: ISUP-SIP/Basic call/ Receipt of Circuit group blocking message (CGB) with the indication hardware failure oriented SIP selection criteria: ISUP selection criteria: Test purpose: CGB received while an INVITE was not sen... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3 Interworking of supplemetary services | |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1 Interworking from SIP to ISUP (Incoming Call) | |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.1 Calling Line Identification (CLI) | TP501001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: SIP-ISUP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: P-Asserted-Identity not in E.164 format and From header not in the E.164 Format, no Privacy header. Send Calling party number Ensure that... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.2 Call Hold (HOLD) | TP502001 SIP reference: RFC 3261 [6] ISUP reference: clause 7.4.10/ [14] TSS reference: SIP-ISUP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Each party can hold and retrieve the remote party in the confirmed state Ensure that a party can put the other party on hold at any ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.3 Terminal portability (TP) | Void. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 233 |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.4 Conference calling (CONF) | TP504001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.14 TSS reference: SIP-ISUP/SS/CONF/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/10 Test purpose: Generic notification Conference established and Conference disconnected and SIP procedure Ensure that the SUT does not stop... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.5 Three Party service (3PTY) | TP505001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.15 TSS reference: SIP-ISUP/SS/3PTY/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/5 AND PICS 5/18 Test purpose: Notification procedure supported Ensure that the SUT stop the temporarily sending one or more unicast media st... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.6 Connected line identification (COL) | TP506001 ISUP reference: [2], clause 7.4.2 TSS reference: SIP-ISUP/SS/COL/ SIP selection criteria: NOT PICS 5/22 ISUP selection criteria: Test purpose: Mapping of connected number not supported Ensure that the SUT, if a connected number is received in an ANM, does not disrupt the SIP signalling procedure. The connected... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.7 Malicious call identification MCID | TP507001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.4 TSS reference: SIP-ISUP/SS/MCID/ SIP selection criteria: PICS 9/1 ISUP selection criteria: Test purpose: No interworking MGCF sends IRS Ensure that the SUT if an IDR is received returns an IRS message. The MCID response indicator is set t... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.8 Sub-addressing (SUB) | TP508001 SUB Reference: ES 283 027 [1], clause 7.4.5 Selection criteria: PICS 5/8 TSS reference: SIP-ISUP/SS/SUB/ Preconditions: Test purpose: The isub parameter of the P-Asserted-Identity header in an INVITE is mapped in the calling party subaddress in the IAM Ensure that the isub parameter in the P-Asserted-Identity ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.9 Call diversion (CDIV) | TP509001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.6 TSS reference: SIP-ISUP/SS/CDIV/ SIP selection criteria: ISUP selection criteria: Test purpose: OBCI "call diversion may occur" in ACM received no mapping Ensure that the SUT if an ACM is received with and call diversion may occur indicat... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.10 Call waiting (CW) | TP510001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.9 TSS reference: SIP-ISUP/SS/CW/ SIP selection criteria: ISUP selection criteria: Test purpose: No mapping of Call Waiting indication in the ACM at the I-MGCF Ensure that the indication for Call Waiting contained in an ACM, Generic notifica... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.11 User to user signalling (UUS) | TP511001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec. Q.1912.5 [32], annex B.21 ITU-T Rec. Q.737.1 [33], clause 1.3.7.2 TSS reference: SIP-ISUP/SS/UUS/ SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: Explicit request supported, a FAR user-to-user service 3 request (not e... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.12 Explicit call transfer (ECT) | TP512001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: SIP-ISUP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 12/1 Test purpose: Loop prevention procedure supported, a LOP response "insufficient information" is sent Ensure that the SUT if a LOP(request) is recei... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.13 Completion of Call to Busy Subscriber (CCBS) | TP513001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.11 TSS reference: SIP-ISUP/SS/CCBS/ SIP selection criteria: ISUP selection criteria: Test purpose: CCBS possible in the Diagnostics field received Ensure that the SUT if a REL is received contained a Diagnostic field and the CCBS indicator ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.14 Completion of Calls on No reply (CCNR) | TP514001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.11 TSS reference: SIP-ISUP/SS/CCNR/ SIP selection criteria: ISUP selection criteria: Test purpose: CCNR possible in the ACM received Ensure that the SUT if an ACM is received and a CCNR Possible Indicator is included: • continue without dis... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.15 Anonymous Call Rejection (ACR) | TP515001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.23 TSS reference: SIP-ISUP/SS/ACR/ SIP selection criteria: ISUP selection criteria: Test purpose: Mapping of cause value #24 Ensure that the SUT, if a destination user has subscribed the ACR supplementary service: • the call attempt is reje... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.1.16 Closed user group (CUG) | TP516001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.1.1 TSS reference: SIP-ISUP/SS/CUG/ SIP selection criteria: ISUP selection criteria: PICS 5/7 Test purpose: Mapping of <cug> XML element in the received INVITE cugCommunicationIndicator value "00" Ensure that the <cugCommunicationIndicator>... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2 Interworking from ISUP to SIP (Outgoing Call) | |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.1 Calling Line Identification (CLI) | TP601001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.2.3.1.2.6 TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: No calling party number and no additional calling party number received Ensure that when the SUT has received an IAM message whereby Call... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.2 Call Hold (HOLD) | TP602001 SIP reference: RFC 3261 [6] ISUP reference: [14], clause 7.4.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: PICS 8/4 ISUP selection criteria: PICS 5/22 Test purpose: Each party can hold and retrieve the remote party in the confirmed state Ensure that a party can put the other party on hold at any ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.3 Terminal portability (TP) | Void. ETSI ETSI TS 186 009-2 V2.2.1 (2011-03) 316 |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.4 Conference calling (CONF) | TP604001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.14 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/10 Test purpose: Establish and disconnect a Conference Ensure that the SUT does not stop the temporarily sending one or more unicast media s... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.5 Three Party service (3PTY) | TP605001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [1], clause 7.4.15 TSS reference: ISUP-SIP/SS/3PTY/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/5 AND PICS 5/18 Test purpose: The media stream is resumed if a 3PTY is established Ensure that the SUT resumes the media stream put on hold ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.6 Connected line identification (COL) | TP606001 SIP reference: RFC 3261 [6] ES 283 027 [1], clause 7.4.2 TSS reference: ISUP-SIP/SS/COL / SIP selection criteria: NOT PICS 5/3 ISUP selection criteria: Test purpose: IAM with OFCI "connected line request" received, no mapping Ensure that the SUT if the IAM is received with an optional forward call indicator, c... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.7 Sub-addressing (SUB) | TP607001 CW Reference: ES 283 027 [1], clause 4.7.4.5.2 Selection criteria: PICS 5/8 TSS reference: ISUP-SIP/SS/SUB/ Preconditions: Test purpose: The calling party subaddress is mapped in the isub parameter of the P-Asserted-Identity Ensure that the calling party subaddress in the ATP parameter of the received IAM is i... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.8 Closed user group (CUG) | TP608001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.16 TSS reference: ISUP-SIP/SS/CUG/ SIP selection criteria: NOT PICS 5/7 ISUP selection criteria: Test purpose: SIP network does not support CUG, CUG with outgoing access allowed is interworked in a normal call Ensure that the SUT if an IAM ... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.9 Call diversion (CDIV) | TP609001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.6 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: NOT PICS 5/12 AND NOT PICS 5/13 AND NOT PICS 5/14 AND NOT PICS 5/15 ISUP selection criteria: Test purpose: CDIV parameter not mapped Ensure that the SUT if the IAM is received wit... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.10 User to user signalling (UUS) | TP610001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.21 ITU-T Rec. Q.737.1 [33], clause 1.1.7 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: Test purpose: User-to-user service 1 implicit request not supported, User-to-user information discarded by the netwo... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.11 Explicit call transfer (ECT) | TP611001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [1], clause 7.4.8 TSS reference: ISUP-SIP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 12/1 AND NOT PICS 13/3 Test purpose: Loop prevention procedure supported, interworking of "call transfer" indication not supported Ensure that the SUT i... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.12 Anonymous Call Rejection (ACR) | TP612001 ACR-CB Reference: ES 283 027 [1], clause 4.7.1.3.1 Selection criteria: TSS reference: ISUP-SIP/SS/ACR Preconditions: Test purpose: Mapping of 433 Anonymity Disallowed to REL cause 24 Ensure that the 433 Anonymity Disallowed final response received to due the ACR service is mapped into a REL cause 24 "call reje... |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.13 Call waiting (CW) | FFS |
f837441d0decd0bfe6419bfc72a0ce86 | 186 009-2 | 6.3.2.14 Malicious call identification (MCID) | TP614001 MCID Reference: clause 4.7.1.2 Selection criteria: PICS 1/6 TSS reference: ISUP-SIP/SS/MCID/ Preconditions: Test purpose: Mapping of XML mcid request (McidRequestIndicator) Ensure that the XML mcid McidRequestIndicator contained in a received INFO request mapped into the MCID request indicator requested in the... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 1 Scope | The present document describes the performance benchmark methology for the IMS based services MMTel, Video Telephony and IMS - PES. The terminology and concepts are described in TR 101 577 [i.11]. The present document is the first part of the multi-part deliverable which consists of four parts. The present document con... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-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 ar... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 101 563 (V1.2.1): "Speech and multimedia Transmission Quality (STQ); IMS/PES exchange performance requirements". [2] ETSI TS 123 002 (V11.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobi... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 186 008-2: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 2: Subsystem Configurations and Benchmarks". [i.2] ETSI TS 186 008-... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 3 Definitions and abbreviations | |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 3.1 Definitions | The IMS benchmarking definitions are described in TR 101 577 [i.11]. For the purposes of the present document, the following terms and definitions apply: background load: workload applied to an SUT during a benchmark test, for the purpose of consuming SUT resources during a benchmark test and changing the traffic inten... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 121 905 [i.7] and the following apply: AGCF Access Gateway Control Function ATCA Advanced Telecom Architecture BYE BYE message CDMA Code Division Multiple Access CN Core Network CPU Central Processor Unit CS Circuit Switched DO Design Objective DOC... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4 Benchmark information model | In this clause, "benchmark information model" refers to the structure of the information elements that define the benchmark. This information model is depicted in figure 2. The information model consists of three primary elements: use-cases, which describe the behaviour of an individual user, and which in turn define s... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1 Use-case | The top level of the individual behavioural model is the use-case. A use-case describes the goal that a user has in interacting with a system, the various actors (e.g. other users, network elements) that participate in the use-case, the basic course of events that are carried out by the user and the SUT, the design obj... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1.1 Call Flow | The calls flows define the characteristic message flows, the tones and announcement for a specific interface. |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1.2 Load Profile | To facilitate the calculation of processing capacity and the appropriate load profile the concept of workload factor has been defined based on the reference call for each combination of traffic case and traffic signalling interface. The reference call (RC) is defined as a basic ISUP to ISUP call connected through two M... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1.3 Metrics | The metrics of a use-case describe the measurements collected from the execution of a scenario attempt. Typical metrics include response times and message rates. If a scenario is selected for execution in a benchmark test, its metrics are collected. See clause 7 for more detail. |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1.4 Use-case outcomes | A use-case outcome is a set of possible outcomes of the scenarios of a use-case. An outcome may be simply "correct", it may reflect an error or failure condition; or it may reflect a correct behaviour that took an excessive amount of time to occur. An instance of a scenario that experiences an error, failure, or timeou... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1.5 Scenarios and scenario attempts | A scenario is a trace of a path through a use-case. It is analogous to "call attempt", but applies to all interactions within an IMS/PES network, different Bearer, and application interactions. A scenario may succeed, fail, or succeed functionally. The terms "scenario attempt" and "scenario attempts per second" are use... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1.6 Design Objective (DO) | The Design Objective (DO) describes the maximal acceptable rate handled scenario attempts for a use-case. |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.1.7 Scenario | A scenario describes a single interaction sequence among the actors of a use-case. It is documented by a set of preconditions on its actors (typically specified by parameter values). In case of IMS/PES the scenario is defined as a set of different Bearer Capabilities (e.g. speech, 3,1 kHz audio, UDI, UDI/TA), services ... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.2 Benchmark test | A benchmark by definition measures the behaviour of a population of users. To accomplish this, the behaviours of individual users shall be aggregated into input traffic to the SUT. The input traffic shall be realistic, in the sense that a population of users would perform such actions in the real world, and in the sens... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.2.1 Traffic set | The traffic set is a collection of scenarios which are determined to be likely to co-occur in a real-world scenario. The scenarios do not need to come from the same use-case. Within a traffic set, each scenario has an associated relative occurrence frequency, interpreted as the probability with which it would occur in ... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.2.2 Background load | Background load is a workload presented to the SUT in order to consume its resources. It may consist of a stream of traffic presented to the SUT by an external system apart from the test system; or it may be a workload presented to the processing elements, network, or storage subsystem of the SUT. The purpose of backgr... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.2.3 Traffic-time profile | The traffic-time profile is a function describing the average scenario attempt arrival rate as a function of elapsed time during a benchmark test. A traffic-time profile should be chosen in such a manner that, for a given scenario attempt arrival rate, sufficient samples are generated that metrics can be collected with... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.2.4 Test parameters | The benchmark test parameters are used to control the behaviour of the test script. The data elements required to configure the test system are listed in table 1. Table 1 is a non-exhaustive list of test parameters defined for the benchmark standard. The list is expected to grow over time, as additional subsystems and ... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 4.3 Benchmark report | A test report is a document, with accompanying data files, that provides a full description of an execution of a benchmark test on a test system. The SUT and test system, as well as their parameters, are described in sufficient detail that an independent test site can replicate the test. The results of the test include... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 5 System Under Test (SUT) | The IMS performance benchmark covers benchmark tests for the MMTel, Video Telephony, and MMTel - IMS PES. Figure 3 depicts the IMS Reference Architecture. The components of the architecture are the primary building blocks, which are either defined by the IMS standard, or defined by external standards and referenced by ... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 5.1 Creation of subscriber data base | The subscriber data base is the data-set required to configure the SUT in order to execute a benchmark test. Using the same data, the test system should be able to generate correct traffic. The present document does not try to specify a complete set, but rather just the subset that will ensure comparable results. All o... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 6 Test system | The test system is used to generate the appropriate load on the SUT. The present document does not mandate any specific test system to be used, although the details of the test system shall be reported in the benchmark report. The test system should have two main functions: • Traffic generation: the test system shall b... |
ce6ebf51ec076d886e2cd294039516a9 | 186 008-1 | 7 Benchmark metrics examples | The metrics reported by a benchmark test is measured in real time during the execution of the test, or may be computed after completion of the test from event logs collected during the execution. Enclosed is a benchmark matrix based on the TS 101 563 [1]. ETSI ETSI TS 186 008-1 V1.2.2 (2013-06) 20 Table 2: Benchmark me... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 1 Scope | The present document describes the protocols used for the reference points internal to the Customer Premises Network (CPN), between the Customer Network Gateway (CNG) and the Customer Network Devices (CNDs). This description is based on the architecture and stage 2 information flows contained in TS 185 003 [1] and TS 1... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 185 003 (V2.y.z): "Telecommunications and Int... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] "UPnP Remote Access Transport Agent (RATA) Confi... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 3 Definitions and abbreviations | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: announcement: service related message sent to a user that can be of any type of media e.g. a voice message or a video-clip transfer target: party which the communication is transferred to and which replaces the transferor in the commun... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.