Datasets:

OrganizedProgrammers
/

ETSISpecContent

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 194k rows

hash stringlengths 32 32	doc_id stringlengths 7 13	section stringlengths 3 121	content stringlengths 0 3.58M
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.2 Identification of the implementation	Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. ETSI ETSI TS 186 022-1 V2.1.1 (2009-07) 8 A person who can answer queries regarding information supplied in the PICS should be named as the contact person.
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.2.1 Date of the statement	Date of the statement:
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.2.2 Implementation Under Test (IUT) identification	IUT name: IUT version:
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.2.3 System Under Test (SUT) identification	SUT name: Hardware configuration: Operating system:
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.2.4 Product supplier	Name: Address: Telephone number: Facsimile number: Additional information:
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.2.5 Client	Name: Address: Telephone number: Facsimile number: Additional information:
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.2.6 PICS contact person	Name: Telephone number: Facsimile number: Additional information:
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.3 PICS proforma tables
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.3.1 Global statement of conformance	(Yes/No) Are all mandatory capabilities implemented? ETSI ETSI TS 186 022-1 V2.1.1 (2009-07) 9
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	4.3.2 Roles and network capabilities	Table 1: Roles and network capabilities Item Item description Reference Status Support 1 Is the CW condition determined by the AS based on the receipt of a 180 (Ringing) response with a Alert-Info header field set to "urn:alert:service:call-waiting"? 4.5.5.2 o1 2 Is the CW condition determined by the AS based on validation of the "approaching NDUB" condition? 4.5.5.2 o1 3 Does the AS initiate the procedures for the provision of an announcement to the calling? 4.5.5.2 o 4 Does the Application Server starts the timer TAS-CW timer? 4.5.5.2 o o1: At least one of the these options shall be used. Table 2: User Equipment capabilities Item Item description Reference Status Support 1 Does the User Equipment of the user B indicate to the user that the outgoing communication is being treated as a waiting communication? 4.5.5.3.2 o 2 Does the User Equipment of the user C indicate to the user that the outgoing communication is being treated as a waiting communication? 4.5.5.3.4 o 3 Is the User Equipment of the user B able to send a Communication Waiting indication in a 180 Ringing and send the Alert-Info header with the value <urn:alert:service:call- waiting>? 4.5.5.3.2 o 4 Does the User Equipment accept and understand the XML CW MIME attachment and notify the user? 4.5.5.3.2 o Table 3: Timer Item Item description Reference Status Support Values allowed Supported [sec] 1 Timer TAS-CW 4.7/ [1] o Service provider option 2 Timer TUE-CW 4.5.5.3.2/ [1] o manufacturer option
ddb59b31e71d0b43ef511bd6f8fa3d65	186 022-1	5 Additional informations for PICS	If necessary, the supplier may provide additional comments in this clause. ETSI ETSI TS 186 022-1 V2.1.1 (2009-07) 10 History Document history V2.1.1 July 2009 Publication
c3a4d3373dcd3bb825d55317d4ec4738	186 021-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 description is specified using the IP-Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	2.1 Normative references	The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 042 (V2.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Simulation Services; Completion of Communications to Busy Subscriber (CCBS), Completion of Communications by No Reply (CCNR); Protocol Specification". [2] ETSI TS 186 021-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Completion of Communications to Busy Subscriber (CCBS) Completion of Communications by No Reply (CCNR); Part 1: Protocol Implementation Conformance Statement (PICS)".
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	2.2 Informative references	The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 6
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	3 Definitions and abbreviations
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	3.1 Definitions	For the purposes of the present document, the terms and definitions given in [1] apply.
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	3.2 Abbreviations	For the purposes of the present document, the abbreviations given in [1] apply.
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	4 Test Suite Structure (TSS)	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 CDIV CC_N08_xxx
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	4.1 Configuration	The scope of the current specification is to test the signalling and procedural aspects of the stage 3 requirements as described in [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 addressed to satisfy the test of the different entities. Therefore to test the appropriate entities the configurations below are applicable: Testing of the Application Server: This entity is responsible to perform the service. Hence the ISC interface is the appropriate access point. Figure 1 points to this. Figure 1: Applicable interface to test AS functionalities If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 7 CSCF (and/or AS) Implementation under Test Test System Test System Mw, Mg, Mx Mw, Mg, Mx Figure 2: Applicable interfaces to test using the (generic) NNI interface Figure 3 illustrates the usage of any NNI interface. Testing of User Equipment: There are several requirements regarding to the end devices. Therefore a special configuration appears. User Equipment Implementation under Test Test System Gm Figure 3: Applicable configuration to test the User Equipment Testing of the IBCF functionality: The IBCF is the division between the trusted and the untrusted networks. Figure 3: Applicable configuration to test the IBCF If the Mx interface is not accessible it is also applicable to perform the test of the IBCF using any NNI (Mw, Mg, Mx) interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 8
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5 Test Purposes (TP)
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.1 Introduction	For each test requirement a TP is defined.
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.1.1 TP naming convention	TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "CC" <iut> = type of IUT: U User - equipment N Network <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001 to 999)
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.1.2 Test strategy	As the base standard TS 183 042 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 186 021-1 [2]. The criteria applied include the following: • whether or not a test case can be built from the TP is not considered. ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 9
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.2 Actions at the originating AS
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.2.1 CC Invocation	TSS CC/originating_AS/Invocation TP CC_N01_001 Reference 4.5.4.2.1 Selection expression Test purpose Successful CCBS request. A 486 (Busy Here) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to BS. Ensure that the AS withholds the 486 and sends a 183 Session Progress and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCBS call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful 486 (Busy Here) ACK Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_002 Reference 4.5.4.2.1 Selection expression Test purpose CCBS not possible, no CCBS indication received. A 486 (Busy Here) is received from the terminating user containing and no Call-Info header field is contained. The originating AS does not starts announcement to provide the activation of the call completion service and pass thru the 486 response. Preconditions: SIP header values: 486 Busy Here: Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 10 TSS CC/originating_AS/Invocation TP CC_N01_003 Reference 4.5.4.2.1 Selection expression Test purpose CCBS not possible, A CC queue limit has been exceeded. Ensure that the AS does not offer the activation of the call completion service if the user A CCBS queue limit has been exceeded. The 486 is passed thru. Preconditions: CCBS queue limit exceeded SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Set the A queue to limit INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK TSS CC/originating_AS/Invocation TP CC_N01_004 Reference 4.5.4.2.1 Selection expression PICS 1/3 Test purpose CCBS not possible, further identical request (communication parameters). Ensure that the AS does not offer the activation of the CCBS call completion service if a request was activated for an identical communication, determined by the stored basic communication information. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke a successful CCBS request INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) ACK ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 11 TSS CC/originating_AS/Invocation TP CC_N01_005 Reference 4.5.4.2.1 Selection expression Test purpose CCNR successful request. A 180 (Ringing) is received from the terminating AS containing a Call-Info header field a purpose parameter set to call-completion and the m parameter is set to BS. Ensure that the sends a 180 (Ringing) without the Call-Info header and starts to play an announcement to inform the originating user that Call Completion is possible. The originating user activates via inband interaction the CCNR call completion service. Ensure that the AS sends a SUBSCRIBE to the terminating AS. The NOTIFY received from the terminating AS confirms the successful invocation of the CC service. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK Apply post test routine TSS CC/originating_AS/Invocation TP CC_N01_006 Reference 4.5.4.2.1 Selection expression Test purpose CCNR not possible, no CCBS indication received. Ensure that the originating AS does not offer the call completion service if a 180 (Ringing) is received and a Call-Info header is not present. The 180 (Ringing) is passed unchanged. Preconditions: SIP header values: Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 180 Ringing CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 12 TSS CC/originating_AS/Invocation TP CC_N01_007 Reference 4.5.4.2.1 Selection expression Test purpose CCNR not possible, A CC queue limit has been exceeded. Ensure that the originating AS does not offered the call completion service if a 180 (Ringing) is received and a Call-Info header with a purpose parameter set to call-completion and a m parameter set to NR is received and the CCBS queue limit is exceeded. Preconditions: CCBS queue limit exceeded SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Set the A queue to limit INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK TSS CC/originating_AS/Invocation TP CC_N01_008 Reference 4.5.4.2.1 Selection expression PICS 1/3 Test purpose CCNR not possible, further identical request (communication parameters). Ensure that the AS does not offer the activation of the CCNR call completion service if a request was activated for an identical communication, determined by the stored basic communication information. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Successful CCNR request INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 No offer to invoke CCNR CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 13 TSS CC/originating_AS/Invocation TP CC_N01_009 Reference 4.5.4.2.1 Selection expression Test purpose Unsuccessful CCBS request. Ensure that the originating AS does not confirm the CCBS request to the originating user, if the request sent to the terminating AS is rejected by the terminating AS indicated in a NOTIFY request and the Subscription-State header is set to terminated. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) ACK 183 Session Progress Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Indication to the caller that the invocation was unsuccessful 486 (Busy Here) ACK ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 14 TSS CC/originating_AS/Invocation TP CC_N01_010 Reference 4.5.4.2.1 Selection expression Test purpose CCNR unsuccessful request. Ensure that the originating AS does not confirm the CCNR request to the originating user, if the request sent to the terminating AS is rejected by the terminating AS indicated in a NOTIFY request and the Subscription-State header is set to terminated. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Indication to the caller that the invocation was unsuccessful CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 15
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.2.2 CC Revocation	TSS CC/originating_AS/Revocation TP CC_N02_001 Reference 4.5.4.2.2 Selection expression PICS 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 request. The revocation is performed by an INVITE request and the userpart of the Request URI is set to the service code command to cancel a CCBS request. Preconditions: SIP header values: INVITE: Request URI= Service Code Command (revoke CCBS request) SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Establish a successful CCBS request Revocation request from the user INVITE 200 OK INVITE ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the revocation was successful BYE 200 OK BYE ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 16 TSS CC/originating_AS/Revocation TP CC_N02_002 Reference 4.5.4.2.2 Selection expression PICS 1/8 Test purpose CCNR 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 CCNR request. The revocation is performed by an INVITE request and the userpart of the Request URI is set to the service code command to cancel a CCNR request. Preconditions: SIP header values: INVITE: Request URI= Service Code Command (revoke CCNR request) SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Establish a successful CCBS request Revocation request from the user INVITE 200 OK INVITE ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the revocation was successful BYE 200 OK BYE TSS CC/originating_AS/Revocation TP CC_N02_003 Reference 4.5.4.2.2 Selection expression Test purpose CCBS revocation caused by timer expiry. Ensure that the originating AS revokes the outstanding CCBS request if the CC service duration timer CC-T3 expires. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Establish a successful CCBS request Start CC-T3 Timeout CC-T3 SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 17 TSS CC/originating_AS/Revocation TP CC_N02_004 Reference 4.5.4.2.2 Selection expression Test purpose CCBS revocation caused by timer expiry. Ensure that the originating AS revokes the outstanding CCNR request if the CC service duration timer CC-T3 expires. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Establish a successful CCBS request Start CC-T3 Timeout CC-T3 SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 18
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.2.3 CC Operation	TSS CC/originating_AS/Operation TP CC_N03_001 Reference 4.5.4.2.3 Selection expression NOT PICS 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 indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". A REFER request is sent to the caller. The m parameter of the Request line is set to BS in the INVITE request sent to the callee as the result of the received INVITE request from the caller. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready REFER: sip: SIP 1; m=BS Refer-To; SIP 2; method=INVITE INVITE 1: sip: SIP 2; m=BS From: SIP 1 To: SIP 2 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY (200) NOTIFY (200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 19 TSS CC/originating_AS/Operation TP CC_N03_002 Reference 4.5.4.2.3 Selection expression NOT PICS 1/4 Test purpose CCNR Recall successful by sending a REFER request to the originating user. Ensure that the originating AS starts the CCNR recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". A REFER request is sent to the caller. The m parameter of the Request line is set to NR in the INVITE request sent to the callee as the result of the received INVITE request from the caller. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready REFER: sip: SIP 1; m=NR Refer-To; SIP 2; method=INVITE INVITE 1: sip: SIP 2; m=NR From: SIP 1 To: SIP 2 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 202 Accepted 202 Accepted NOTIFY (100) NOTIFY (100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE INVITE 1 180 Ringing 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK NOTIFY (200) NOTIFY (200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 20 TSS CC/originating_AS/Operation TP CC_N03_003 Reference 4.5.4.2.3 Selection expression PICS 1/4 Test purpose CCBS Recall successful by using the special REFER interworking. Sending an INVITE 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 indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". An INVITE request is sent to the caller. When the session with the caller is answered, an INVITE request is sent to the callee and the m parameter in the Request line is set to BS. When the callee answers the session, caller and callee are connected. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready INVITE 2: sip: SIP 2; m=BS From: SIP 1 To: SIP 2 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 1 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE ACK ACK INVITE 2 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 21 TSS CC/originating_AS/Operation TP CC_N03_004 Reference 4.5.4.2.3 Selection expression PICS 1/4 Test purpose CCNR Recall successful by using the special REFER interworking. Sending an INVITE request to the originating user. Ensure that the originating AS starts the CCNR recall procedure when the indication that the callee is available to recall indicated in a NOTIFY request and the state header in the call-completion MIME body is set to "ready". An INVITE request is sent to the caller. When the session with the caller is answered, an INVITE request is sent to the callee and the m parameter in the Request line is set to NR. When the callee answers the session, caller and callee are connected. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready INVITE 2: sip: SIP 2; m=NR From: SIP 1 To: SIP 2 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 1 180 Ringing 180 Ringing 200 OK INVITE 200 OK INVITE INVITE 2 ACK ACK 180 Ringing NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 22 TSS CC/originating_AS/Operation TP CC_N03_005 Reference 4.5.4.2.3 Selection expression Test purpose CCBS Recall not accepted by originating user. CC-T4 expires. Ensure that the originating AS revokes the outstanding CCBS request after having received the notification that the CCBS recall to the callee is possible and the caller does not accept the recall offer. A SUBCRIBE is sent to the terminating AS and the Expires header is set to zero. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready REFER: sip: SIP 1; m=BS Refer-To; SIP 2; method=INVITE SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 202 Accepted 202 Accepted Start Timer CC-T4 ↓ Timeout Timer CC-T4 SUBSCRIBE SUBSCRIBE 202 Accepted 202 Accepted NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 23 TSS CC/originating_AS/Operation TP CC_N03_006 Reference 4.5.4.2.3 Selection expression Test purpose CCNR Recall not accepted by originating user. Ensure that the originating AS revokes the outstanding CCNR request after having received the notification that the CCNR recall to the callee is possible and the caller does not accept the recall offer. A SUBCRIBE is sent to the terminating AS and the Expires header is set to zero. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready REFER: sip: SIP 1; m=NR Refer-To; SIP 2; method=INVITE SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 202 Accepted 202 Accepted Start Timer CC-T4 ↓ Timeout Timer CC-T4 SUBSCRIBE SUBSCRIBE 202 Accepted 202 Accepted NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 24 TSS CC/originating_AS/Operation TP CC_N03_007 Reference 4.5.4.2.3.2.2 Selection expression Test purpose CCBS Caller is found to be busy, when a CC recall notification has been received. Ensure that when the caller is found to be busy, when a CCBS CC recall notification has been received, then the originating AS shall suspend the CC request until the caller becomes not busy. The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "closed". The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "open" when the caller is not longer busy. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready REFER: sip: SIP 1; m=BS Refer-To; SIP 2; method=INVITE PUBLISH 1: sip T-AS To: SIP 2 Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>closed</basic> NOTIFY 2 sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention PUBLISH 2: sip T-AS To: SIP 2 Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>open</basic> Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Terminating user available for recall Establish a session to SIP 2 NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Disconnect session to SIP 2 PUBLISH 2 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 25 TSS CC/originating_AS/Operation TP CC_N03_008 Reference 4.5.4.2.3.2.2 Selection expression Test purpose CCNR Caller is found to be busy, when a CC recall notification has been received. Ensure that when the caller is found to be busy, when a CCNR CC recall notification has been received, then the originating AS shall suspend the CC request until the caller becomes not busy. The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "closed". The originating AS shall send a PUBLISH request to the terminating AS containing a presence XML body status set to "open" when the caller is not longer busy. Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Content-Type: application/call-completion state: ready REFER: sip: SIP 1; m=NR Refer-To; SIP 2; method=INVITE PUBLISH 1: sip T-AS To: SIP 2 Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>closed</basic> NOTIFY 2 sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention PUBLISH 2: sip T-AS To: SIP 2 Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>open</basic> Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS Terminating user available for recall Establish a session to SIP 2 NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY REFER REFER 486 (Busy Here) 486 (Busy Here) PUBLISH 1 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Disconnect session to SIP 2 PUBLISH 2 PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 1 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 26 TSS CC/originating_AS/Operation TP CC_N03_009 Reference 4.5.4.2.3.2.3 Selection expression NOT PICS 1/3 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCBS again. The two communications are identical. The AS discards the current request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCBS) again then the originating AS retain the original request and discards the current request and informs the caller that the request has not been accepted because a CC request had already been stored against the requested callee. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) 183 Session Progress 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation Announcement that CCBS is not invoked Apply post test routine TSS CC/originating_AS/Operation TP CC_N03_010 Reference 4.5.4.2.3.2.3 Selection expression NOT PICS 1/3 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCNR again. The two communications are identical. The AS discards the current request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCNR) again then the originating AS retain the original request and discards the current request and informs the caller that the request has not been accepted because a CC request had already been stored against the requested callee. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation Announcement that CCBS is not invoked CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 27 TSS CC/originating_AS/Operation TP CC_N03_011 Reference 4.5.4.2.3.2.3 Selection expression PICS 1/3 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCBS again. The two communications are identical. The AS treat this as a new CC request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCBS) again, the originating AS shall treat this as a new CC request, A SUBSRIBE request is sent to the terminating AS indicating a CCBS request - a m parameter set to "BS" is attached at the Request line. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 486 (Busy Here) 183 Session Progress 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 28 TSS CC/originating_AS/Operation TP CC_N03_012 Reference 4.5.4.2.3.2.3 Selection expression PICS 1/4 Test purpose The caller initiates another communication to the same destination B and activates the same CC service CCNR again. The two communications are identical. The AS treat this as a new CC request. Ensure that the caller initiates another communication to the same destination B and activates the same CC service (CCNR) again, the originating AS shall treat this as a new CC request, A SUBSRIBE request is sent to the terminating AS indicating a CCBS request - a m parameter set to "NR" is attached at the Request line. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCNR is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Confirm to the caller that the invocation was successful CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 29 TSS CC/originating_AS/Operation TP CC_N03_013 Reference 4.8.1 Selection expression Test purpose CCBS request. Timeout CC-T2. Ensure that the CC request operation timer CC-T2 is started after CCBS request is received from caller. When the timer CC-T2 is expired because no NOTIFY is received from the terminating user as an confirmation that the CCBS request was successful at the terminating AS the CCBS request is rejected. The caller is informed. Preconditions: SIP header values: 486 Busy Here: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 183 Session Progress ACK Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted Start Timer CC-T2 ↓ Timeout Timer CC-T2 Confirm to the caller that the invocation was not successful 486 (Busy Here) ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 30 TSS CC/originating_AS/Operation TP CC_N03_014 Reference 4.8.1 Selection expression Test purpose CCNR request. Timeout CC-T2. Ensure that the CC request operation timer CC-T2 is started after CCNR request is received from caller. When the timer CC-T2 is expired because no NOTIFY is received from the terminating user as an confirmation that the CCBS request was successful at the terminating AS the CCNR request is rejected. The caller is informed. Preconditions: SIP header values: 180 Ringing 2: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing 2 Announcement that CCBS is possible Inband-interaction procedures for the CC activation SUBSCRIBE 202 Accepted Start Timer CC-T2 ↓ Timeout Timer CC-T2 Confirm to the caller that the invocation was not successful CANCEL CANCEL 200 OK CANCEL 200 OK CANCEL 487 Request Terminated 487 Request Terminated ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 31 TSS CC/originating_AS/Operation TP CC_N03_015 Reference 4.8.1 Selection expression Test purpose CCBS request. Timeout CC-T3. Ensure that the CC service duration timer CC-T3 is started. When CC-T3 expires, the call completion request is deleted. The CCBS request is revoked indicated by sending a SUBSCRIBE request containing an Expires header set to zero. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request CCBS request confirmed by AS Start Timer CC-T3 ↓ Timeout Timer CC-T3 SUBSCRIBE SUBSCRIBE 202 Accepted 202 Accepted NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/originating_AS/Operation TP CC_N03_016 Reference 4.8.1 Selection expression Test purpose CCNR request. Timeout CC-T3. Ensure that the CC service duration timer CC-T3 is started. When CC-T3 expires, the call completion request is deleted. The CCNR request is revoked indicated by sending a SUBSCRIBE request containing an Expires header set to zero. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request CCNR request confirmed by AS Start Timer CC-T3 ↓ Timeout Timer CC-T3 SUBSCRIBE SUBSCRIBE 202 Accepted 202 Accepted NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 32
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.3 Actions at the terminating AS
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.3.1 CC possible indication	TSS CC/terminating_AS/possibleIndication TP CC_N04_001 Reference 4.5.4.3.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-completion and the mparameter is set to BS in the 486 (Busy Here) received from the callee and forwards to the originating AS. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_002 Reference 4.5.4.3.1 Selection expression Test purpose The terminating AS inserts a Call-Info header in the 486 final response in case of NDUB. Ensure that the terminating AS in case of NDUB sends a 486 (Busy Here) containing a Call-Info header and the purpose parameter is set to call-completion and the mparameter is set to BS to the originating AS. Preconditions: Callee is network determined user busy SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE 100 Trying 486 (Busy Here) 1 ACK Apply post test routine TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_003 Reference 4.5.4.3.1 Selection expression Test purpose The terminating AS inserts a Call-Info header in the 180 provisional response. Ensure that the terminating AS inserts a Call-Info header in the 180 (Ringing) and the purpose parameter is set to call-completion and the mparameter is set to NR received from the callee and forwards to the originating AS. Preconditions: SIP header values: 180 (Ringing) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 33 TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_004 Reference 4.5.4.3.1.1 Selection expression Test purpose Terminating user does not subscribe to the CCBS service. No Call-Info header field included. Ensure that no Call-Info header is included in the 486 (Busy Here) If the terminating AS knows that the CC is not possible on destination B (callee). Preconditions: Terminating user does not subscribe to the CC service SIP header values: 486 (Busy Here) 1: Call-Info not included Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/terminating_AS_AS/possibleIndication TP CC_N04_005 Reference 4.5.4.3.1.1 Selection expression Test purpose Terminating user does not subscribe to the CCNR service. No Call-Info header field included. Ensure that no Call-Info header is included in the 180 (Ringing) If the terminating AS knows that the CC is not possible on destination B (callee). Preconditions: Terminating user does not subscribe to the CC service SIP header values: 180 (Ringing) 1: Call-Info not included Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 34
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.3.2 CC Invocation	TSS CC/terminating_AS/Invocation TP CC_N05_001 Reference 4.5.4.3.2 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 NOTIY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 35 TSS CC/terminating_AS/Invocation TP CC_N05_002 Reference 4.5.4.3.2 Selection expression Test purpose CCNR service invocation successful at the terminating AS. Ensure that the terminating AS is able to queue the CCNR request received in a SUBSCRIBE request from the originating AS and responds with a NOTIY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/terminating_AS/Invocation TP CC_N05_003 Reference 4.5.4.3.2 Selection expression Test purpose CCBS service invocation unsuccessful at the terminating AS. Maximum number of queue entries is reached. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCBS invoke received from the originating AS with a 480 (Temporarily Unavailable) if the callee's B queue limit is reached. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Set the B queue to limit INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 480 Temporarily Unavailable Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 36 TSS CC/terminating_AS/Invocation TP CC_N05_004 Reference 4.5.4.3.2 Selection expression Test purpose CCBS service invocation unsuccessful at the terminating AS. To header of the SUBSCRIBE is not available for the service request. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCBS invoke received from the originating AS with a 403 Forbidden if the URI in the To header field of the SUBSCRIBE request is not available for the requested CC service at the terminating AS. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<other URI (PIXIT)> Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 403 Forbidden TSS CC/terminating_AS/Invocation TP CC_N05_005 Reference 4.5.4.3.2 Selection expression Test purpose CCNR service invocation unsuccessful at the terminating AS. Maximum number of queue entries is reached. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCNR invoke received from the originating AS with a 480 (Temporarily Unavailable) if the callee's B queue limit is reached. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Set the B queue to limit INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing SUBSCRIBE 480 Temporarily Unavailable Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 37 TSS CC/terminating_AS/Invocation TP CC_N05_006 Reference 4.5.4.3.2 Selection expression Test purpose CCNR service invocation unsuccessful at the terminating AS. To header of the SUBSCRIBE is not available for the service request. Ensure that the terminating AS responds to the SUBSCRIBE request containing the CCNR invoke received from the originating AS with a 403 Forbidden if the URI in the To header field of the SUBSCRIBE request is not available for the requested CC service at the terminating AS. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<other URI (PIXIT)> Contact:<O-AS> Event:call-completion Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 403 Forbidden TSS CC/terminating_AS/Invocation TP CC_N05_007 Reference 4.5.4.3.2 Selection expression PICS 1/2 Test purpose CCBS service invocation successful at the terminating AS. Retain option supported. 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 NOTIY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is present. Preconditions: SIP header values: 486 (Busy Here) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=BS SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 38 TSS CC/terminating_AS/Invocation TP CC_N05_008 Reference 4.5.4.3.2 Selection expression NOT PICS 1/2 Test purpose CCNR service invocation successful at the terminating AS. Retain option not supported. 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 NOTIY request. In the NOTIFY request the state header of the call-completion MIME body is set to queued and the service-retention header is not present. Preconditions: SIP header values: 180 Ringing 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion NOTIFY sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 Ringing 1 180 Ringing SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.3.3 CC Revocation	TSS CC/terminating_AS/Revocation TP CC_N06_001 Reference 4.5.4.3.3 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 rejected for a CCBS queue entry if a SUBSCRIBE request is received and the Expires header is set to zero. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=BS From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 39 TSS CC/terminating_AS/Revocation TP CC_N06_002 Reference 4.5.4.3.3 Selection expression Test purpose CCNR 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 rejected for a CCNR queue entry if a SUBSCRIBE request is received and the Expires header is set to zero. Preconditions: SIP header values: SUBSRIBE sip:T-AS;m=NR From:<UE-A> To:<UE-B> Contact:<O-AS> Event:call-completion Expires=0 NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request SUBSCRIBE 202 Accepted NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/terminating_AS/Revocation TP CC_N06_003 Reference 4.5.4.3.3 Selection expression Test purpose CCBS service revocation at the terminating AS. CC-T7 expires. Ensure that the terminating AS is able to revoke a CCBS queue entry if the CC service duration timer CC-T7 expires. A NOTIFY request is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Start CC-T7 ↓ CC-T7 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 40 TSS CC/terminating_AS/Revocation TP CC_N06_004 Reference 4.5.4.3.3 Selection expression Test purpose CCNR service revocation at the terminating AS. CC-T7 expires. Ensure that the terminating AS is able to revoke a CCNR queue entry if the CC service duration timer CC-T7 expires. A NOTIFY request is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Start CC-T7 ↓ CC-T7 expires NOTIFY 200 OK NOTIFY Apply post test routine
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.3.4 CC Operation	TSS CC/terminating_AS/CCOperation TP CC_N07_001 Reference 4.5.4.3.4.1.1 Selection expression Test purpose Callee becomes not busy, CC recall procedure performed. Retain option is not supported. Ensure that the terminating AS starts the call completion recall procedure if the callee becomes not busy. The terminating AS starts the Destination B idle guard timer CC-T8. When the timer CC-T8 expires, a NOTIFY request is sent to the originating AS. The state header in the call-completion MIME body is set to "ready", the service-retention header is not present. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 41 TSS CC/terminating_AS/CCOperation TP CC_N07_002 Reference 4.5.4.3.4.1.1 Selection expression PICS 1/2 Test purpose Callee becomes not busy after having initiated an activity, CC recall procedure performed. Retain option is not supported. Ensure that the terminating AS starts the call completion recall procedure if the callee is having initiated an activity. The terminating AS starts the Destination B idle guard timer CC-T8. When the timer CC-T8 expires, a NOTIFY request is sent to the originating AS. The state header in the call-completion MIME body is set to "ready", the service-retention header is not present. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/terminating_AS/CCOperation TP CC_N07_003 Reference 4.5.4.3.4.1.1 Selection expression PICS 1/2 Test purpose Callee becomes not busy, CC recall procedure performed. Retain option is supported. Ensure that the terminating AS starts the call completion recall procedure if the callee becomes not busy. The terminating AS starts the Destination B idle guard timer CC-T8. When the timer CC-T8 expires, a NOTIFY request is sent to the originating AS. The state header in the call-completion MIME body is set to "ready", the service-retention header is present. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 42 TSS CC/terminating_AS/CCOperation TP CC_N07_004 Reference 4.5.4.3.4.1.1 Selection expression PICS 1/2 Test purpose Callee becomes not busy after having initiated an activity, CC recall procedure performed. Retain option is supported. Ensure that the terminating AS starts the call completion recall procedure if the callee having initiated an activity. The terminating AS starts the Destination B idle guard timer CC-T8. When the timer CC-T8 expires, a NOTIFY request is sent to the originating AS. The state header in the call-completion MIME body is set to "ready", the service-retention header is present. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ CC-T8 expires NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 43 TSS CC/terminating_AS/CCOperation TP CC_N07_005 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression Test purpose CCBS: An INVITE request received while a CC recall is processed. CC call indicator present in the Request line. Ensure that when an INVITE request is received from the originating AS while CC-T9 is running and in the Request line the m parameter is present set to "BS", this INVITE is processed to the callee. An INVITE is sent to the callee and the m parameter is not present in the Request line. When a 180 (Ringing) is received from the callee a NOTIFY request is sent to the originating AS and Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2; m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 44 TSS CC/terminating_AS/CCOperation TP CC_N07_006 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression Test purpose CCNR: An INVITE request received while a CC recall is processed. CC call indicator present in the Request line. Ensure that when an INVITE request is received from the originating AS while CC-T9 is running and in the Request line the m parameter is present set to "NR", this INVITE is processed to the callee. An INVITE is sent to the callee and the m parameter is not present in the Request line. When a 180 (Ringing) is received from the callee a NOTIFY request is sent to the originating AS and Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2; m=NR NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 45 TSS CC/terminating_AS/CCOperation TP CC_N07_007 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression PICS 1/9 Test purpose CCBS: An INVITE request received while a CC recall is processed. CC call indicator not present in the Request line. Service requirements and destination selection information are identical to the stored values. The call is offered. Ensure that the terminating AS has sent a NOTIFY request and the state parameter in the call-completion MIME body was set to "ready" after the terminating AS receives an INVITE request and there is no m parameter in the Request line the terminating AS compares the destination selection information and service requirements with the stored value received in the CCBS request. If the match is true the call is offered to the callee. When a 180 (Ringing) is received from the callee a NOTIFY request is sent to the originating AS and Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2 destination selection information and Service requirements as used in the dialogue as CCBS was requested NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 46 TSS CC/terminating_AS/CCOperation TP CC_N07_008 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression PICS 1/9 Test purpose CCNR: An INVITE request received while a CC recall is processed. CC call indicator not present in the Request line. Service requirements and destination selection information are identical to the stored values. The call is offered. Ensure that the terminating AS has sent a NOTIFY request and the state parameter in the call-completion MIME body was set to "ready" after the terminating AS receives an INVITE request and there is no m parameter in the Request line the terminating AS compares the destination selection information and service requirements with the stored value received in the CCNR request. If the match is true the call is offered to the callee. When a 180 (Ringing) is received from the callee a NOTIFY request is sent to the originating AS and Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2 destination selection information and Service requirements as used in the dialogue as CCNR was requested NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY 200 OK INVITE 200 OK INVITE ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 47 TSS CC/terminating_AS/CCOperation TP CC_N07_009 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression NOT PICS 1/9 Test purpose CCBS: An INVITE request received while a CC recall is processed. CC call indicator not present in the Request line. Service requirements and destination selection information are not identical to the stored values. The call is rejected. Ensure that the terminating AS has sent a NOTIFY request to a CCBS entry and the state parameter in the call-completion MIME body was set to "ready" after the terminating AS receives an INVITE request and there is no m parameter in the Request line the terminating rejects the call. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE: sip: SIP 2 destination selection information and Service requirements not identical as used in the dialogue as CCBS was requested NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE 4xx ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 48 TSS CC/terminating_AS/CCOperation TP CC_N07_010 Reference 4.5.4.3.4.1.3, 4.5.4.3.4.1.4 Selection expression NOT PICS 1/9 Test purpose CCNR: An INVITE request received while a CC recall is processed. CC call indicator not present in the Request line. Service requirements and destination selection information are not identical to the stored values. The call is rejected. Ensure that the terminating AS has sent a NOTIFY request to a CCNR entry and the state parameter in the call-completion MIME body was set to "ready" after the terminating AS receives an INVITE request and there is no m parameter in the Request line the terminating rejects the call. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE: sip: SIP 2 destination selection information and Service requirements not identical as used in the dialogue as CCNR was requested NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE 4xx ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 49 TSS CC/terminating_AS/CCOperation TP CC_N07_011 Reference 4.5.4.3.4.2 Selection expression Test purpose CCBS: Terminating user becomes busy while CC-T8 is running. If in case of CCBS, upon expiry of the destination B idle guard timer CC-T8, the callee is busy (e.g. the callee has initiated an outgoing communication), then the terminating AS shall defer servicing of the destination B CC queue until the callee becomes not busy again. After the callee is not busy, the terminating AS starts the recall procedure again. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 (S2) Event:call-completion Content-Type: application/call-completion state: ready Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ INVITE (S1) INVITE 200 OK INVITE 200 OK INVITE ACK ACK CC-T8 expires BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 50 TSS CC/terminating_AS/CCOperation TP CC_N07_012 Reference 4.5.4.3.4.2 Selection expression Test purpose CCNR: Terminating user becomes busy while CC-T8 is running. If in case of CCNR, upon expiry of the destination B idle guard timer CC-T8, the callee is busy (e.g. the callee has initiated an outgoing communication), then the terminating AS shall defer servicing of the destination B CC queue until the callee becomes not busy again. After the callee is not busy, the terminating AS starts the recall procedure again. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 (S2) Event:call-completion Content-Type: application/call-completion state: ready service-retention Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ INVITE (S1) INVITE 200 OK INVITE 200 OK INVITE ACK ACK CC-T8 expires BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 51 TSS CC/terminating_AS/CCOperation TP CC_N07_013 Reference 4.5.4.3.4.2 Selection expression NOT PICS 1/2 Test purpose CCBS: The callee is busy upon arrival of the CC call. Retain option not supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is not supported at the terminating AS, the terminating AS shall cancel the corresponding CCBS request; the terminating AS shall send a 486 (Busy Here) response with an Call-Info header field with a "purpose" header field parameter set to "call-completion" and a m parameter set to "BS" to the originating AS. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2; m=BS 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) 486 (Busy Here) ACK BYE BYE 200 OK BYE 200 OK BYE Terminating user is not monitored, CC-T8 is not started Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 52 TSS CC/terminating_AS/CCOperation TP CC_N07_014 Reference 4.5.4.3.4.2 Selection expression NOT PICS 1/2 Test purpose CCNR: The callee is busy upon arrival of the CC call. Retain option not supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is not supported at the terminating AS, the terminating AS shall cancel the corresponding CCNR request; the terminating AS shall send a 486 (Busy Here) response with an Call-Info header field with a "purpose" header field parameter set to "call-completion" and a m parameter set to "BS" to the originating AS. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2; m=NR 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) 486 (Busy Here) ACK BYE BYE 200 OK BYE 200 OK BYE Terminating user is not monitored, CC-T8 is not started Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 53 TSS CC/terminating_AS/CCOperation TP CC_N07_015 Reference 4.5.4.3.4.2 Selection expression PICS 1/2 Test purpose CCBS: The callee is busy upon arrival of the CC call. Retain option supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is supported at the terminating AS, the terminating AS shall retain the original CCBS request in the queue; in this case the terminating AS shall continue to monitor destination B, shall not restart the timer CCBS-T7, shall stop timer CC-T9 and shall send a 486 (Busy Here) response with an Call-Info header field with a "purpose" header field parameter set to "call-completion" and the m parameter set to "BS" to the originating AS. After the callee becomes not busy, the recall procedure is started again. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready service-retention INVITE 1: sip: SIP 2; m=BS 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) 486 (Busy Here) ACK BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 54 TSS CC/terminating_AS/CCOperation TP CC_N07_016 Reference 4.5.4.3.4.2 Selection expression PICS 1/2 Test purpose CCNR: The callee is busy upon arrival of the CC call. Retain option supported. Ensure that if the callee is busy upon arrival of the CC call and the retain option is supported at the terminating AS, the terminating AS shall retain the original CCNR request in the queue; in this case the terminating AS shall continue to monitor destination B, shall not restart the timer CCBS-T7, shall stop timer CC-T9 and shall send a 486 (Busy Here) response with an Call-Info header field with a "purpose" header field parameter set to "call-completion" and the m parameter set to "BS" to the originating AS. After the callee becomes not busy, the recall procedure is started again. Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready service-retention INVITE 1: sip: SIP 2; m=NR 486 (Busy Here): Call-Info: <sip:UE-B>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY INVITE INVITE (S1) 200 OK INVITE 200 OK INVITE ACK ACK INVITE 1 (S2) 486 (Busy Here) ACK BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 55 TSS CC/terminating_AS/CCOperation TP CC_N07_017 Reference 4.5.4.3.4.2 Selection expression Test purpose CCBS: Recall does not apply, CC-T9 expires. Ensure that the terminating As revokes the CCBS request after the Recall timer. CC-T9 is expired. The terminating AA sends a NOTIFY request to the originating AS and the Subscription-State header is set to "terminated" and the reason header is set to "rejected". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Start CC-T9 ↓ CC-T9 expires NOTIFY 2 200 OK NOTIFY ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 56 TSS CC/terminating_AS/CCOperation TP CC_N07_018 Reference 4.5.4.3.4.2 Selection expression Test purpose CCNR: Recall does not apply, CC-T9 expires. Ensure that the terminating As revokes the CCNR request after the Recall timer. CC-T9 is expired. The terminating AA sends a NOTIFY request to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "rejected". Preconditions: SIP header values: NOTIFY sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK Start CC-T8 ↓ CC-T8 expires NOTIFY 1 200 OK NOTIFY Start CC-T9 ↓ CC-T9 expires NOTIFY 2 200 OK NOTIFY Apply post test routine TSS CC/terminating_AS/CCOperation TP CC_N07_019 Reference 4.8.2 Selection expression Test purpose CCBS: Service duration timer, CC-T7 expires. Ensure that the terminating AS revoke the CCBS request after the CC service duration timer CC-T7 expires. A NOTIFY is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "rejected". Preconditions: SIP header values: NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Start CC-T7 Callee is busy ↓ CC-T7 expires NOTIFY 2 200 OK NOTIFY ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 57 TSS CC/terminating_AS/CCOperation TP CC_N07_020 Reference 4.8.2 Selection expression Test purpose CCNR: Service duration timer, CC-T7 expires. Ensure that the terminating AS revoke the CCNR request after the CC service duration timer CC-T7 expires. A NOTIFY is sent to the originating AS and the Subscription-State header is set to "terminated" and the reason parameter is set to "rejected". Preconditions: SIP header values: NOTIFY 1 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Start CC-T7 Callee is idle ↓ CC-T7 expires NOTIFY 1 200 OK NOTIFY ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 58 TSS CC/terminating_AS/CCOperation TP CC_N07_021 Reference 4.5.4.3.4.2 Selection expression Test purpose CCBS: Caller becomes busy while CC recall procedure. Ensure that the terminating AS after expiry of the B idle guard timer CC-T8 sends again the remote user free indication after the caller indicates no longer busy. A NOTIFY is sent an den MIME body contains the state parameter set to "queued". Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready PUBLISH 1 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>closed</basic> PUBLISH 2 sip:T-AS Event: presence Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?> <presence <status> <basic>copen</basic> NOTIFY 2 sip:O-AS Event:call-completion Content-Type: application/call-completion state: queued Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY PUBLISH PUBLISH 200 OK PUBLISH 200 OK PUBLISH NOTIFY 2 NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Start CC-T8 ↓ CC-T8 expires NOTIFY 1 NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 59
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.4 Interaction of Call-Completion with other services
c3a4d3373dcd3bb825d55317d4ec4738	186 021-2	5.4.1 Communication diversion services (CDIV)	TSS CC/Interaction/CDIV TP CC_N08_001 Reference 4.6.8.2 Selection expression PICS 1/7 Test purpose CCBS: indication is sent if the original call was unconditional diverted. In case of a callee is busy and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCBS is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion unconditional occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=302>;index=1.1 486 (Busy Here) 1: Call-Info: <sip:SIP 2>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_002 Reference 4.6.8.2 Selection expression PICS 1/7 Test purpose CCNR: indication is sent if the original call was unconditional diverted. In case of a callee does not answer the communication request and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCNR is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion unconditional occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=302>;index=1.1 180 (Ringing) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 60 TSS CC/Interaction/CDIV TP CC_N08_003 Reference 4.6.8.2 Selection expression NOT PICS 1/7 Test purpose CCBS: indication is not sent if the original call was unconditional diverted. In case of a callee is busy and the callee has subscribed the call completion service, ensure that terminating AS does not inform the caller that CCBS is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion unconditional occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=302>;index=1.1 486 (Busy Here) 1: Call-Info: not present Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_004 Reference 4.6.8.2 Selection expression Test purpose CCNR: indication is not sent if the original call was unconditional diverted. In case of a callee does not answer the communication request and the callee has subscribed the call completion service, ensure that terminating AS does not inform the caller that CCNR is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion unconditional occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=302>;index=1.1 180 (Ringing) 1: Call-Info: not present Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_005 Reference 4.6.8.2 Selection expression Test purpose CCBS request is cancelled after the callee activates CFU. Ensure that the terminating AS revokes the outstanding CCBS request if the callee activates Communication Forwarding unconditional. Preconditions: SIP header values: NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Terminating user activates CFU NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 61 TSS CC/Interaction/CDIV TP CC_N08_006 Reference 4.6.8.2 Selection expression Test purpose CCNR request is cancelled after the callee activates CFU. Ensure that the terminating AS revokes the outstanding CCNR request if the callee activates Communication Forwarding unconditional. Preconditions: SIP header values: NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCNR request Terminating user activates CFU NOTIFY NOTIFY 200 OK NOTIFY 200 OK NOTIFY Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_007 Reference 4.6.8.3 Selection expression Test purpose CCBS indication is sent if the original call was diverted on Busy. In case of a callee is busy and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCBS is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion busy occurred. Preconditions: Communication Forwarding Busy is activated SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=486>;index=1.1 486 (Busy Here) 1: Call-Info: <sip:SIP 2>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_008 Reference 4.6.8.3 Selection expression Test purpose CCNR indication is sent if the original call was diverted on Busy. In case of a callee does not answer the communication request and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCNR is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion Busy occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=486>;index=1.1 180 (Ringing) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 62 TSS CC/Interaction/CDIV TP CC_N08_009 Reference 4.6.8.3 Selection expression Test purpose CCBS indication is not sent if the original call was diverted on Busy. In case of a callee is busy and the callee has subscribed the call completion service, ensure that terminating AS does not inform the caller that CCBS is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion busy occurred. Preconditions: Communication Forwarding Busy is activated SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=486>;index=1.1 486 (Busy Here) 1: Call-Info: not present Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_010 Reference 4.6.8.3 Selection expression Test purpose CCBS recall after the callee activates CFB. Recall is considered as being busy. Ensure that the terminating AS considers a CCBS recall to a busy callee that has activated CFB as being busy. The entry is removed from the queue and a CCBS possible indication is sent to the caller. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready 486 (Busy Here) 2 Call-Info: <sip:UE-B>;purpose=call-completion;m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request BYE BYE 200 OK BYE 200 OK BYE NOTIFY NOTIFY 1 200 OK NOTIFY 200 OK NOTIFY Terminating user activates CFB INVITE INVITE 200 OK INVITE 200 OK INVITE ACK ACK INVITE INVITE 486 (Busy Here) 2 486 (Busy Here) ACK ACK NOTIFY NOTIFY 2 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 63 TSS CC/Interaction/CDIV TP CC_N08_011 Reference 4.6.8.2 Selection expression Test purpose CCBS: indication is sent if the original call was diverted on no Reply. In case of a callee is busy and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCBS is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion on No Reply occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=408>;index=1.1 486 (Busy Here) 1: Call-Info: <sip:SIP 2>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_012 Reference 4.6.8.3 Selection expression Test purpose CCNR indication is sent if the original call was diverted on no Reply. In case of a callee does not answer the communication request and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCNR is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion on No Reply occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=408>;index=1.1 180 (Ringing) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 64 TSS CC/Interaction/CDIV TP CC_N08_013 Reference 4.6.6 Selection expression Test purpose CCBS: Recall after CCNR was activated. Ensure that the CC AS applies the procedures for CCNR when the callee activates CFNR after the CCBS recall procedure was started by the CC AS. After the 180 was sent to the caller AS, a NOTIFY is sent to indicate the CCBS request is removed from the queue. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2; m=BS NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is busy BYE BYE 200 OK BYE 200 OK BYE NOTIFY 1 200 OK NOTIFY Callee activates CCNR INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 65 TSS CC/Interaction/CDIV TP CC_N08_014 Reference 4.6.6 Selection expression Test purpose CCNR: Recall after CCNR was activated. Ensure that the CC AS applies the procedures for CCNR when the callee activates CFNR after the CCNR recall procedure was started by the CC AS. After the 180 was sent to the caller AS, a NOTIFY is sent to indicate the CCNR request is removed from the queue. Preconditions: SIP header values: NOTIFY 1 sip:O-AS From: Sip 2 To: SIP 1 Event:call-completion Content-Type: application/call-completion state: ready INVITE 1: sip: SIP 2; m=NR NOTIFY 2 sip:O-AS Event:call-completion Subscription-State: terminated; reason=rejected Comments: SIP 1 (ISC) SUT SIP 2 (ISC) Invoke CCBS request Callee is idle INVITE INVITE 486 Busy Here 486 Busy Here ACK ACK NOTIFY 1 200 OK NOTIFY Callee activates CCNR INVITE 1 INVITE 180 Ringing 180 Ringing NOTIFY 2 200 OK NOTIFY Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_015 Reference 4.6.8.2 Selection expression Test purpose CCBS: indication is sent if the original call was diverted on not Logged-in. In case of a callee is busy and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCBS is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion on Not Logged-in occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=404>;index=1.1 486 (Busy Here) 1: Call-Info: <sip:SIP 2>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 66 TSS CC/Interaction/CDIV TP CC_N08_016 Reference 4.6.8.3 Selection expression Test purpose CCNR indication is sent if the original call was diverted on not Logged-in. In case of a callee does not answer the communication request and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCNR is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication diversion on Not Logged-in occurred. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=404>;index=1.1 180 (Ringing) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_017 Reference 4.6.8.2 Selection expression Test purpose CCBS: indication is sent if the original call was deflected. In case of a callee is busy and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCBS is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication is deflected. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=487>;index=1.1 486 (Busy Here) 1: Call-Info: <sip:SIP 2>;purpose=call-completion;m=BS Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 486 (Busy Here) 1 486 (Busy Here) ACK ACK Apply post test routine TSS CC/Interaction/CDIV TP CC_N08_018 Reference 4.6.8.3 Selection expression Test purpose CCNR indication is sent if the original call was deflected. In case of a callee does not answer the communication request and the callee has subscribed the call completion service, ensure that terminating AS inform the caller that CCNR is possible at the callee if the INVITE request contains a History-Info header that indicates that a communication is deflected. Preconditions: SIP header values: INVITE: sip SIP 2 History-Info: <SIP 1>;index=1, <SIP 2; cause=487>;index=1.1 180 (Ringing) 1: Call-Info: <sip:UE-B>;purpose=call-completion;m=NR Comments: SIP 1 (ISC) SUT SIP 2 (ISC) INVITE INVITE 100 Trying 100 Trying 180 (Ringing) 1 180 (Ringing) Apply post test routine ETSI ETSI TS 186 021-2 V2.1.1 (2009-07) 67 History Document history V2.1.1 July 2009 Publication
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	1 Scope	The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) of the Explicit Communication transfer (ECT) simulation service, based on stage one and two of the ISDN ECT supplementary service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), TS 183 029 [1]. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document. Within the TISPAN NGN, the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	2.1 Normative references	The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 029: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification". [2] ETSI TS 186 015-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Part 1: Protocol Implementation conformance Statement (PICS)".
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	2.2 Informative references	The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 6
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	3 Definitions and abbreviations
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	3.1 Definitions	For the purposes of the present document, the terms and definitions specified in [1] apply.
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	3.2 Abbreviations	For the purposes of the present document, the abbreviations specified in [1] apply.
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-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 1: Test suite structure
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	4.1 Configuration	The scope of the current specification is to test the signalling and procedural aspects of the stage 3 requirements as described in [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 addressed to satisfy the test of the different entities. Therefore to test the appropriate entities the configurations below are applicable: Testing of the Application Server: This entity is responsible to perform the service. Hence the ISC interface is the appropriate access point. Figure 2 points to this. Figure 2: Applicable interface to test AS functionalities ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 7 If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx) interface (consider figure 3). In case only the Gm interface is accessible this shall be used instead. In this case, be aware that the verification of several requirements is impeded. CSCF (and/or AS) Implementation under Test Test System Test System Mw, Mg, Mx Mw, Mg, Mx Figure 3: Applicable interfaces to test using the (generic) NNI interface Figure 4 illustrates the usage of any NNI interface. Testing of User Equipment: There are several requirements regarding to the end devices. Therefore a special configuration appears. User Equipment Implementation under Test Test System Gm Figure 4: Applicable configuration to test the User Equipment
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5 Test Purposes (TP)
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.1 Introduction	For each test requirement a TP is defined.
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.1.1 TP naming convention	TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite and whether it applies to the network or the user (see table 1). ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 8 Table 1: TP identifier naming convention scheme Identifier: <ss>_<iut><group>_<nnn> <ss> = supplementary service: e.g. "ECT" <iut> = type of IUT: U User N Network <group> = group 2 digit field representing group reference according to TSS <nnn> = sequential number (001-999)
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.1.2 Test strategy	As the base standard TS 183 029 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification TS 186 015-1 [2]. ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 9
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2 Signalling requirements
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.1 Actions at the Transferor AS	TSS Netw/TransferorAS TP ECT_N01_001 Reference 4.5.2.4 [1] Selection expression PICS 1/2 1 AND NOT (PICS 1/4 OR PICS 1/5) Test purpose Communication transfer: Assured transfer. Transferor was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the communication between the Transferee and the Transfer Target is confirmed, the communication between Transferor and Transferee is terminated. The Transferor was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 BYE BYE 2 BYE BYE 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 10 TSS Netw/TransferorAS TP ECT_N01_002 Reference 4.5.2.4 [1] Selection expression PICS 1/2 AND NOT (PICS 1/4 OR PICS 1/5) Test purpose Communication transfer: Assured transfer. Transferee was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the communication between the Transferee and the Transfer Target is confirmed, the communication between Transferor and Transferee is terminated. The Transferee was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 SC#3 Establishment of session #1 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 BYE BYE 2 BYE BYE 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 11 TSS Netw/TransferorAS TP ECT_N01_003 Reference 4.5.2.4 [1] Selection expression PICS 1/1 AND NOT (PICS 1/4 OR PICS 1/5) Test purpose Communication transfer: Blind transfer. Transferor was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the REFER request to the Transferee is sent, the communication between Transferor and Transferee is terminated. The Transferor was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains SC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Communication ISC#2 with ISC#3 BYE BYE 2 BYE BYE 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 12 TSS Netw/TransferorAS TP ECT_N01_004 Reference 4.5.2.4 [1] Selection expression PICS 1/1 AND NOT (PICS 1/4 OR PICS 1/5) Test purpose Communication transfer: Blind transfer. Transferee was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. After the REFER request to the Transferee is sent, the communication between Transferor and Transferee is terminated. The Transferee was the initiator of the originating communication. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ECT Session Identifier URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Communication ISC#2 with ISC#3 BYE BYE 2 BYE BYE 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 13 TSS Netw/TransferorAS TP ECT_N01_005 Reference 4.5.2.4 [1] Selection expression PICS 1/3 AND NOT (PICS 1/4 OR PICS 1/5) Test purpose Communication transfer: Consultative transfer. Transferor was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. The Transferor has a session with Transferee and the Transfer target set on hold. The Transferor refers the Transferee to establish a session to the Transfer target. After the successful session between Transferee and Transfer target, the sessions of the Transferor are released by the Transferor. The Transferor was the initiator of the originating communication. SIP header values: REFER 1: Require=replaces; Refer-To contains ISC#3 URI?Replaces=call-id1%3B to-tag=S1%3Bfrom-tag=S1; method=invite Referred-By contains ISC#1 URI REFER 2: Require=replaces; Refer-To contains ECT Session Identifier URI?Replaces=call-id1%3B to-tag=S1%3Bfrom-tag=S1; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI; Replaces=call-id1;to-tag=S1; from-tag=S1 INVITE 4: Request URI = ISC#3 URI; Replaces=call-id1;to-tag=S1;from-tag=S1 NOTIFY(100): Event contains refer; message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer; message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE 1 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK Establishment of session #2 INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 transfers ISC#3 to ISC#2 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 14 TSS Netw/TransferorAS TP ECT_N01_005 Reference 4.5.2.4 [1] Selection expression PICS 1/3 AND NOT (PICS 1/4 OR PICS 1/5) BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 BYE BYE 2 BYE BYE 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) TSS Netw/TransferorAS TP ECT_N01_006 Reference 4.5.2.4 [1] Selection expression PICS 1/3 AND NOT (PICS 1/4 OR PICS 1/5) Test purpose Communication transfer: Consultative transfer. Transferee was originator of the originating call. Ensure that a Transferor can successfully transfer the communication with the transferee set on hold before and the Transferor is notified about the processing. The Transferor has a session with Transferee and the Transfer target. The Transferor refers the Transferee to establish a session to the Transfer target. After the successful session between Transferee and Transfer target set on hold, the sessions of the Transferor are released by the Transferor. The Transferee was the initiator of the originating communication. SIP header values: REFER 1: Require=replaces; Refer-To contains ISC#3 URI?Replaces=call-id1%3B to-tag=S1%3Bfrom-tag=S1; method=invite Referred-By contains ISC#1 URI REFER 2: Require=replaces; Refer-To contains ECT Session Identifier URI?Replaces=call-id1%3B to-tag=S1%3Bfrom-tag=S1; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ECT Session Identifier URI; Replaces=call-id1; to-tag=S1; from-tag=S1 INVITE 4: Request URI = ISC#3 URI; Replaces=call-id1;to-tag=S1; from-tag=S1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK Establishment of session #2 INVITE 2 INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 15 TSS Netw/TransferorAS TP ECT_N01_006 Reference 4.5.2.4 [1] Selection expression PICS 1/3 AND NOT (PICS 1/4 OR PICS 1/5) 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) Communication ISC#2 with ISC#3 BYE BYE 2 BYE BYE 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) TSS Netw/TransferorAS TP ECT_N01_007 Reference 4.5.2.4.1.2.2 [1] Selection expression Test purpose The method in the Refer-To header is not the INVITE method. Ensure that the REFER request is rejected if the Method in the Refer-To header used in this dialogue is not the INVITE method e.g. BYE. SIP header values: REFER: :Refer-To contains ISC#3 URI; method=BYE Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER REFER 4xx or 5xx Response 4xx or 5xx Response Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 16 TSS TP ECT_N01_008 Reference 4.5.2.4.1.2.2 [1] Selection expression Test purpose The request-URI is not targeted at the same UE instance that is involved in the dialog. Ensure that the ECT simulation service does not apply if the Request URI is not the Transferee URI. The REFER request is rejected. SIP header values: REFER: Request URI contained the other URI (PIXIT) Refer-To contains the URI of ISC#3, method=invite Referred-By contains SIP or tel URI of ISC#1 Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK REFER REFER 4xx or 5xx Response 4xx or 5xx Response Apply post test routine TSS Netw/TransferorAS TP ECT_N01_009 Reference 4.5.2.4.1.2.2 [1] Selection expression Test purpose There is no method parameter contained in the Refer-To header. Ensure that the REFER request is rejected if there is no Method parameter contained in the Refer-To header. SIP header values: REFER: Refer-To To contains ISC#3 URI (no method parameter) Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER REFER 4xx or 5xx Response 4xx or 5xx Response Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 17 TSS Netw/TransferorAS TP ECT_N01_010 Reference 4.5.2.4.2.3 [1] Selection expression NOT (PICS 1/4 OR PICS 1/5) Test purpose In the REFER request, the Referred-By header does not contain the valid identity of the served user. A Referred-By header is available in the REFER request, the AS verifies if the provided Referred-By header contains a valid identity of the served user. If not it will replace the Referred-By header with a valid value matching the REFER request's P-Asserted-Identity. SIP header values: REFER 1: Request URI: ISC#2 Referred-By contains ISC#x URI P-Asserted-Identity=ISC#1 REFER 1: Request URI: ISC#2 Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 18 TSS Netw/TransferorAS TP ECT_N01_011 Reference 4.5.2.4.2.3 [1] Selection expression NOT (PICS 1/4 OR PICS 1/5) Test purpose The REFER request does not contain a Referred-By header. If no Referred-By header is available in the REFER request a Referred-By header is added that matches the REFER method's P-Asserted-Identity. SIP header values: REFER 1: Request URI: ISC#2 Referred-By not present P-Asserted-Identity=ISC#1 REFER 1: Request URI: ISC#2 Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 19 TSS Netw/TransferorAS TP ECT_N01_012 Reference 4.5.2.4.2.1 [2] Selection expression NOT (PICS 1/4 OR PICS 1/5) Test purpose The Referred-By header in the received INVITE does not contain the valid identity of the served user. If a Referred-By header is available in the INVITE request, the AS verifies if the provided Referred-By header contains a valid identity of the served user. If not it will replace the Referred-By header with a valid value matching the REFER request's P-Asserted-Identity. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite P-Asserted-Identity=ISC#1 INVITE 3: Request URI = ECT Session Identifier URI Referred-By contains ISC#x URI INVITE 4: Request URI = ISC#3 URI Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 20 TSS Netw/TransferorAS TP ECT_N01_013 Reference 4.5.2.4.2.1 [2] Selection expression NOT (PICS 1/4 OR PICS 1/5) Test purpose The received INVITE does not contain a Referred-By header. If no Referred-By header is available in the INVITE request a Referred-By header is added that matches the REFER request's P-Asserted-Identity. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite P-Asserted-Identity=ISC#1 INVITE 3: Request URI = ECT Session Identifier URI Referred-By not present INVITE 4: Request URI = ISC#3 URI Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 21 TSS Netw/TransferorAS TP ECT_N01_014 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose Assured transfer. The AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted 3 party call control applies NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 22 TSS Netw/TransferorAS TP ECT_N01_015 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/1 AND PICS 1/4 Test purpose Blind transfer. The AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies NOTIFY(100) 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 23 TSS Netw/TransferorAS TP ECT_N01_016 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/3 AND PICS 1/4 Test purpose Consultative transfer. The AS receives a 403 Forbidden indicating the Transferee does not support the REFER method. Ensure that three party call control applies when a 403 Forbidden is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Establishment of session #2 Session #1 on hold REFER 1 REFER REFER REFER 403 Forbidden 403 Forbidden 202 Accepted 202 Accepted 3 party call control applies NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 24 TSS Netw/TransferorAS TP ECT_N01_017 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/2 AND PICS 1/4 Test purpose Assured transfer. The AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted 3 party call control applies NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 25 TSS Netw/TransferorAS TP ECT_N01_018 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/1 AND PICS 1/4 Test purpose Blind transfer. The AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies NOTIFY(100) 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 26 TSS Netw/TransferorAS TP ECT_N01_019 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/3 AND PICS 1/4 Test purpose Consultative transfer. The AS receives a 501 Not implemented indicating the Transferee does not support the REFER method. Ensure that three party call control applies when a 501 Not implemented is received upon a REFER was sent to the Transferee: • A 202 Accepted for the REFER is sent. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 REFER 1 REFER REFER REFER 501 Not implemented 501 Not implemented 202 Accepted 202 Accepted 3 party call control applies NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 27 TSS Netw/TransferorAS TP ECT_N01_020 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/2 AND PICS 1/5 Test purpose Assured transfer. The AS initiate the special REFER handling procedures directly. Ensure that three party call control applies directly when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER 202 Accepted 202 Accepted 3 party call control applies NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 28 TSS Netw/TransferorAS TP ECT_N01_021 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/1 AND PICS 1/5 Test purpose Blind transfer. The AS initiate the special REFER handling procedures directly. Ensure that three party call control applies directly when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • An INVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold REFER 1 REFER 202 Accepted 202 Accepted BYE 200 OK (BYE) 3 party call control applies NOTIFY(100) 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 29 TSS Netw/TransferorAS TP ECT_N01_022 Reference 4.5.2.4.1.2.3 [1] Selection expression PICS 1/3 AND PICS 1/5 Test purpose Consultative transfer. The AS initiate the special REFER handling procedures directly. Ensure that three party call control applies directly when the AS has prior knowledge that the Transferee is not allowed to receive or does not support the REFER method: • A 202 Accepted for the REFER is sent. • A reINVITE is sent to the Transfer Target containing the P-Asserted_identity of the Transferee and the Referred-By header with the identity of the Transferor. • After the 200 OK is received, a reINVITE is sent to the Transferee containing the P-Asserted_identity of the Transfer Target and the Referred-By header with the identity of the Transferor. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3, P-Asserted-Identity=ISC#2, Referred-By=ISC#1 INVITE 4: Request URI = ISC#2, P-Asserted-Identity=ISC#3, Referred-By=ISC#1 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 REFER 1 REFER 202 Accepted 202 Accepted 3 party call control applies NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 180 Ringing 180 Ringing 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY INVITE 4 INVITE 200 OK 200 OK ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 30
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.2 Action at the Transferee AS	TSS Netw/TransfereeAS TP ECT_N02_001 Reference 4.5.2.7/ [1] Selection expression 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 transferred as an assured transfer. SIP header values: REFER 1: Refer-To ISC#2 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To ISC#2 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (S2 inactive) INVITE (inactive) 200 OK (inactive) 200 OK (S2 inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 (S2) INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 31 TSS Netw/TransfereeAS TP ECT_N02_002 Reference 4.5.2.7 [1] Selection expression Test purpose Communication transfer: Blind 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 transferred as a blind transfer. SIP header values: REFER 1: Refer-To ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3 URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 32 TSS Netw/TransfereeAS TP ECT_N02_003 Reference 4.5.2.7 [1] Selection expression Test purpose Communication transfer: Consultative 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 transferred as a Consultative transfer. SIP header values: REFER 1: Refer-To ISC#3 URI; method=invite Referred-By contains ISC#1 URI REFER 2: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI INVITE 3: Request URI = ISC#3 URI INVITE 4: Request URI = ISC#3 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (S2 inactive) INVITE (inactive) 200 OK (inactive) 200 OK (S2 inactive) ACK ACK BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) BYE BYE BYE BYE 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 33 TSS Netw/TransfereeAS TP ECT_N02_004 Reference 4.5.2.7.3 [1] Selection expression PICS 1/7 Test purpose The Referred-By header in the received INVITE does not contain the valid identity of the served user. Value is replaced. If a Referred-By header is available in the INVITE request sent to the Transfer Target, the AS verifies if the provided Referred-By header contains with the value stored in the received REFER request. If no match is found, the value of the Referred-By header is replaced by the value of the Referred-By header received in the REFER request. SIP header values: REFER 2: Refer-To URI; method=invite Referred-By ISC#1 INVITE 3: Referred-By other URI (PIXIT) INVITE 4: Referred-By ISC#1 Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (S2 inactive) INVITE (inactive) 200 OK (inactive) 200 OK (S2 inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 34 TSS Netw/TransfereeAS TP ECT_N02_005 Reference 4.5.2.7.3 [1] Selection expression PICS 1/6 Test purpose The Referred-By header in the received INVITE does not contain the valid identity of the served user. Request is rejected. If a Referred-By header is available in the INVITE request sent to the Transfer Target, the AS verifies if the provided Referred-By header contains with the value stored in the received REFER request. If no match is found, the value of the Referred-By header is replaced by the value of the Referred-By header received in the REFER request. SIP header values: REFER 2: Refer-To URI; method=invite Referred-By ISC#1 INVITE 3: Referred-By other URI (PIXIT) Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (S2 inactive) INVITE (inactive) 200 OK (inactive) 200 OK (S2 inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE 4xx 4xx ACK ACK Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 35 TSS Netw/TransfereeAS TP ECT_N02_006 Reference 4.5.2.7.3 [1] Selection expression PICS 1/8 Test purpose The received INVITE does not contain a Referred-By header. If no Referred-By header is available in the INVITE request sent to the Transfer Target, the AS inserts a Referred- By header and the value is equal to the value stored in the received REFER request. SIP header values: REFER 2: Refer-To URI; method=invite Referred-By ISC#1 INVITE 3: (no Referred-By header) INVITE 4: Referred-By ISC#1 Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 REFER REFER 2 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (S2 inactive) INVITE (inactive) 200 OK (inactive) 200 OK (S2 inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE 3 INVITE INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK ACK ACK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 36 TSS Netw/TransfereeAS TP ECT_N02_007 Reference 4.5.2.7.3 [1] Selection expression PICS 1/6 Test purpose The method in the Refer-To header is not the INVITE method. Ensure that the REFER request is rejected if the Method in the Refer-To header used in this dialogue is not the INVITE method e.g. BYE. SIP header values: REFER 2: Refer-To ISC#2URI; method=BYE Referred-By ISC#1 Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 4xx 4xx Apply post test routine TSS Netw/TransfereeAS TP ECT_N02_008 Reference 4.5.2.7.3 [1] Selection expression PICS 1/6 Test purpose The request-URI is not targeted at the same UE instance that is involved in the dialog. Ensure that the ECT simulation service does not apply if the Request URI is not the Transferee URI. The REFER request is rejected. SIP header values: REFER 2: Refer-To other URI (PIXIT); method=invite Referred-By ISC#1 Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 4xx 4xx Apply post test routine TSS Netw/TransfereeAS TP ECT_N02_009 Reference 4.5.2.7.3 [1] Selection expression PICS 1/6 Test purpose There is no method parameter contained in the Refer-To header. Ensure that the REFER request is rejected if there is no Method parameter contained in the Refer-To header. SIP header values: REFER 2: Refer-To ISC#2URI Referred-By ISC#1 Comments: ISC#2 AS Transferee ISC#3 ISC#1 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER REFER 1 4xx 4xx Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 37
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.3 Action at the User equipment
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.3.1 Actions at the Transferor UE	TSS User/Transferor TP ECT_U01_001 Reference 4.5.2.1 [1] Selection expression PICS 2/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, put on hold before, to the Transfer Target using the blind transfer method. The session with user Transferee is terminated before information about the progress of the transfer is received. SIP header values: REFER: Request URI: Gm#2 Refer-To contains Gm#3 URI; method=invite Referred-By contains Gm#1 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE (Gm#1) Test equipment (Gm#2) Establishment of session #1 Session #1 on hold REFER REFER 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 38 TSS User/Transferor TP ECT_U01_002 Reference 4.5.2.1 [1] Selection expression PICS 2/2 Test purpose The UE transfers a communication with a Transferee to the Transfer Target (Transferor, assured transfer). Ensure that the UE is able to transfer a communication with the Transferee, put on hold before, to the Transfer Target using the assured transfer method. The session with Transferee is terminated after information about the progress of the transfer is received. SIP header values: REFER: Request URI: Gm#2 Refer-To contains Gm#3 URI; method=invite Referred-By contains Gm#1 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE ( Gm#1) Test equipment ( Gm#2) Establishment of session #1 Session #1 on hold REFER REFER 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine TSS User/Transferor TP ECT_U01_003 Reference 4.5.2.1 [1] Selection expression PICS 2/3 Test purpose The UE transfers a communication with a Transferee to the Transfer Target (Transferor, consultative transfer). Ensure that the UE is able to transfer a communication with the Transferee, put on hold before, to the Transfer Target, having an active session, using the consultative transfer method. The Transfer Target receives a replaces header to request the termination of the session between Transferor and Transfer Target. SIP header values: REFER 1: Request URI: Gm#2 Require=replaces; Refer-To contains Gm#3 URI?Replaces=call-id1%3Bto-tagSession1%3Bfrom-tagSession1; method=invite Referred-By contains Gm#1 URI NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE ( Gm#1) Test equipment (ISC#2) ( Gm#3) Establishment of session #1 Session #1 on hold Establishment of session #2 REFER REFER 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 39
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.3.2 Actions at the Transferee UE	TSS User/Transferee TP ECT_U02_001 Reference 4.5.2.5 [1] Selection expression PICS 2/1 AND PICS 2/5 Test purpose UE establishes s session with the Transfer target in blind transfer modus (Transferee). Ensure that UE set on hold is able to establish a session with the Transfer target after a REFER referring this session was received. The session with the Transferor is terminated by the Transferor before information about the success of the session to the Transfer target was sent. SIP header values: REFER: Request URI=Gm#1, Refer-To contains Gm#3 URI; method=invite Referred-By contains Gm#2 URI INVITE: Request URI= Gm#3, Referred-By=Gm#2 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE ( Gm#1) Test equipment (Gm#2) Test equipment (Gm#3) Establishment of session #1 Session #1 on hold REFER REFER 202 Accepted 202 Accepted BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) NOTIFY(S1 100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE (S2) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY(S1 200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 40 TSS User/Transferee TP ECT_U02_002 Reference 4.5.2.5 [1] Selection expression PICS 2/2 AND PICS 2/5 Test purpose UE establishes s session with the Transfer target in assured transfer modus (Transferee). Ensure that UE set on hold is able to establish a session with the Transfer target after a REFER referring this session was received. The session with the Transferor is terminated by the Transferor after information about the success of the session to the Transfer target was sent. SIP header values: REFER: Request URI=Gm#1, Refer- Gm#3 URI; method=invite Referred-By Gm#2 URI INVITE: Request URI= Gm#3, Referred-By=Gm#2 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE (Gm#1) Test equipment (Gm#2) Test equipment (Gm#3) Establishment of session #1 Session #1 on hold REFER REFER 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE (S2) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 41 TSS User/Transferee TP ECT_U02_003 Reference 4.5.2.5 [1] Selection expression PICS 2/1 AND PICS 2/5 Test purpose UE establishes s session with the Transfer target in consultative transfer modus (Transferee). Ensure that UE set on hold is able to establish a session with the Transfer target after a REFER referring this session was received. The session with the Transferor is terminated by the Transferor after information about the success of the session to the Transfer target was sent. SIP header values: REFER: Request URI=Gm#1, Refer-To=Gm#3; method=INVITE, Referred-By=Gm#2 INVITE: Request URI= Gm#3, Referred-By=Gm#2 NOTIFY(100): Event contains refer message/sipfrag contains SIP/2.0 100 Trying NOTIFY(200): Event contains refer message/sipfrag contains SIP/2.0 200 OK Comments: UE (Gm#1) Test equipment (Gm#2) Test equipment (Gm#3) Establishment of session #1 Session #1 on hold REFER REFER 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE (S2) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S1) 200 OK (BYE) 200 OK (BYE) Apply post test routine TSS User/Transferee TP ECT_U02_004 Reference 4.5.2.5 [1] Selection expression NOT PICS 2/5 Test purpose UE has not the capability to handle the REFER request. Ensure that the UE is able to send a 403 Forbidden or 501 Not implemented unsuccessful final response if the REFER handling is not implemented. SIP header values: REFER: Request URI=Gm#1, Refer-To other URI (PIXIT); method=invite Referred-By contains Gm#2 URI Comments: UE ( Gm#1) Test equipment (Gm#2) Establishment of session #1 Session #1 on hold REFER REFER CASE A 403 Forbidden 403 Forbidden CASE A 501 Not implemented 501 Not implemented Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 42
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.3.3 Actions at the Transfer target UE	TSS User/TransferTarget TP ECT_U03_001 Reference 4.5.2.17 [1] Selection expression PICS 2/1 OR PICS 2/2 Test purpose Transfer Target is in communication with user Gm#2 (Transferee) in Blind/Assured mode. Ensure that the UE in a session with the (Transferee). is transferred and receives a Referred-By header in the received INVITE identifying the Transferor. SIP header values: INVITE: Request URI = UE (Gm#1) ReferredBy=URI x (PIXIT) BYE Comments: UE C (Gm#1) Test equipment (Gm#2) INVITE INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Apply post test routine TSS User/TransferTarget TP ECT_U03_002 Reference 4.5.2.17 [1] Selection expression PICS 2/3 Test purpose Transfer Target is in communication with the Transferor and the Transferee in consultative transfer mode. Ensure that the UE in a session with the Transferor) and the Transferee can be transferred in a session with the Transferee. In order to terminate the session with the Transferor a Replaces header containing the session information of the session with the Transferor is received in the INVITE received from the Transferee, the session with the Transferor is terminated by UE. SIP header values: INVITE: Replaces=call-id1; to-tag=S1; from-tag=S1 Referred-By= URI x (PIXIT) Comments: UE C (Gm#1) Test equipment (Gm#2) Test equipment (Gm#3) Establishment of session #1 (S1) INVITE INVITE (S2) 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK BYE (S1) BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 43
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.4 Interaction with other services
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.4.1 Originating identification restriction (OIR)	TSS Interaction/OIR TP ECT_N03_001 Reference 4.6.5 Selection expression Test purpose Referred-By header is removed from the INVITE to the Transfer Target due to the OIR service. Ensure that a Referred-By header is removed from the INVITE request to the Transfer Target if a Privacy header that contains the value "user" received from the Transferor regarding the OIR service of the served user. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI Privacy contains "user" INVITE 3: Referred-By contains ISC#1 URI INVITE 4: (no Referred-By header) Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 44 TSS Interaction/OIR TP ECT_N03_002 Reference 4.6.5 Selection expression Test purpose No Referred-By header is sent in the INVITE to the Transfer Target due to the OIR service. Ensure that a Referred-By header is not sent in the INVITE request to the Transfer Target if a Privacy header that contains the value "id" received from the Transferor regarding the OIR service of the served user. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI Privacy contains "id" INVITE 3: (no Referred-By header) INVITE 4: (no Referred-By header) Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 3 INVITE 4 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 45 5.2.4.2 Anonymous Communication Rejection and Communication Barring (ACR/CB) TSSInteraction/ACR-CB TP ECT_N04_001 Reference 4.6.9 Selection expression Test purpose transfer requests with a Transfer Target that is barred by the served users Outgoing Communication Barring (OCB) rules. Ensure that the As does not accept a transfer requests with a transfer Target that is barred by the Transferor's Outgoing Communication Barring (OCB) rules. Precondition: The Transfer Target is barred by the Transferor's Outgoing Communication Barring rules. SIP header values: REFER 1: Refer-To contains ISC#3 URI; method=invite Referred-By contains ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 Establishment of session #1 INVITE INVITE 1 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK INVITE 2 (sendonly) INVITE (sendonly) 200 OK (recvonly) 200 OK (recvonly) ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER 403 Forbidden 403 Forbidden Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 46
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.4.3 CONFerence Calling (CONF)	TSS Interaction/CONF TP ECT_N05_001 Reference 4.6.6 [1] Selection expression PICS 1/1 Test purpose ECt does not apply if the Refer-To header of the REFER request contains the "isfocus" parameter.Ensure that ECt does not apply if the "Isfocue" parameter is present in the Refer-To header in the received REFER request. The ECT AS does not replace the value of the Refer-To header with a created ECT session identifier. The request line of the INVITE destined for the Transfer Target is passed unchanged. SIP header values: INVITE 1: Request URI=conference factory URI 200 OK (INVITE) 1: Contact: conference URI; isfocus REFER 1: Request URI=ISC#2 Refer-To conference URI; isfocus; method=invite Referred-By ISC#1 URI REFER 2: Request URI=ISC#2 Refer-To conference URI; isfocus; method=invite Referred-By ISC#1 URI INVITE 2: Request URI = conference URI; isfocus Referred-By ISC#1 URI INVITE 3: Request URI = conference URI; isfocus Referred-By ISC#1 URI Comments: ISC#ISC#1 AS Transferor ISC#ISC#2 ISC#ISC#3 Establishment of session #1 Session #1 on hold Establishment of session #2 INVITE 1 (S3) INVITE 200 OK (INVITE) 200 OK (INVITE) 1 ACK ACK ISC#1 transfers ISC#2 to ISC#3 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) INVITE INVITE 2 (S2) INVITE 3 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 47
a7de3d0e3c5d31b277b14cb1bef346fd	186 015-2	5.2.4.4 Explicit Communication Transfer (ECT)	TSS Interaction/ECT TP ECT_N06_001 Reference 4.6.10.2, 4.6.10.3 [1] Selection expression PICS 1/1 Test purpose Interaction with ECT: Blind transfer. Ensure that if the INVITE dialog on which the REFER is received is a previously transferred communication indicated by the presence of a Referred-By header in the INVITE request the • REFER is forwarded and the value of the Refer-To header is replaced by the ECT session Identifier. • The Request URI of the INVITE request received to forward to the Transfer Target is replaced with the value of the Transfer Target. SIP header values: INVITE 1: Request URI = ISC#2; Referred-By=other URI (PIXIT) REFER 1: Refer-To ISC#3 URI; method=invite Referred-By ISC#1 URI REFER 2: Refer-To ECT Session Identifier URI; method=invite Referred-By ISC#1 URI INVITE 2: Request URI = ECT Session Identifier URI Referred-By ISC#1 URI INVITE 3: Request URI = ISC#3 URI Referred-By ISC#1 URI Comments: ISC#ISC#1 AS Transferor ISC#ISC#2 ISC#ISC#3 INVITE 1 (S1) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Session #1 on hold REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted BYE BYE 200 OK (BYE) 200 OK (BYE) INVITE INVITE 2 (S2) INVITE 3 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 48 TSS Interaction/ECT TP ECT_N06_002 Reference 4.6.10.2, 4.6.10.3 [1] Selection expression PICS 1/2 Test purpose Interaction with ECT: Assured transfer. Ensure that if the INVITE dialog on which the REFER is received is a previously transferred communication indicated by the presence of a Referred-By header in the INVITE request the • REFER is forwarded and the value of the Refer-To header is replaced by the ECT session Identifier. • The Request URI of the INVITE request received to forward to the Transfer Target is replaced with the value of the Transfer Target. SIP header values: INVITE 1: Request URI = ISC#2; Referred-By=other URI (PIXIT) REFER 1: Refer-To ISC#3 URI; method=invite Referred-By ISC#1 URI REFER 2: Refer-To ECT Session Identifier URI; method=invite Referred-By ISC#ISC#1 URI INVITE 2: Request URI = ECT Session Identifier URI Referred-By ISC#1 URI INVITE 3: Request URI = ISC#3 URI Referred-By ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE 1 (S1) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Session #1 on hold REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted INVITE INVITE 2 (S2) INVITE 3 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 49 TSS Interaction/ECT TP ECT_N06_003 Reference 4.6.10.2, 4.6.10.3 [1] Selection expression PICS 1/3 Test purpose Interaction with ECT: Consultative transfer. Ensure that if the INVITE dialog on which the REFER is received is a previously transferred communication indicated by the presence of a Referred-By header in the INVITE request the • REFER is forwarded and the value of the Refer-To header is replaced by the ECT session Identifier. • The Request URI of the INVITE request received to forward to the Transfer Target is replaced with the value of the Transfer Target. SIP header values: INVITE 1: Request URI = ISC#2; Referred-By=other URI (PIXIT) REFER 1: Require=replaces Refer-To ISC#3 URI?Replaces=call-id-S2; to-tag=S2; from-tag=S2; method=invite Referred-By ISC#1 URI REFER 2: Require=replaces; Refer-To contains ECT Session Identifier URI?Replaces=call-id-S2; to-tag=S2; from-tag=S2; method=invite Referred-By contains ISC#1 URI INVITE 2: Request URI = ECT Session Identifier URI Replaces=call-id-S2; to-tag=S2; from-tag=S2 Referred-By ISC#1 URI INVITE 3: Request URI = ISC#3 URI Replaces=call-id-S2; to-tag=S2; from-tag=S2 Referred-By ISC#1 URI Comments: ISC#1 AS Transferor ISC#2 ISC#3 INVITE 1 (S1) INVITE 180 Ringing 180 Ringing 200 OK (INVITE) 200 OK (INVITE) ACK ACK Session #1 on hold Establishment of session #2 REFER 1 REFER REFER 2 REFER 202 Accepted 202 Accepted 202 Accepted 202 Accepted INVITE (inactive) INVITE (inactive) 200 OK (inactive) 200 OK (inactive) ACK ACK NOTIFY(100) NOTIFY(100) 200 OK NOTIFY 200 OK NOTIFY INVITE INVITE 2 (S3) INVITE 3 INVITE 180 Ringing 180 Ringing 180 Ringing 180 Ringing 200 OK 200 OK 200 OK 200 OK ACK ACK NOTIFY(200) NOTIFY(200) 200 OK NOTIFY 200 OK NOTIFY BYE BYE (S2) 200 OK (BYE) 200 OK (BYE) BYE (S1) BYE 200 OK (BYE) 200 OK (BYE) Apply post test routine ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 50 Annex A (informative): Bibliography ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 8.9.0 Release 8)". ETSI ETSI TS 186 015-2 V2.1.1 (2009-07) 51 History Document history V2.1.1 July 2009 Publication
6c20142db410ff122a3cb510f7a6cc43	186 015-1	1 Scope	The present document specifies the Protocol conformance Implementation Statement of the Explicit Communication transfer (ECT) simulation service, based on stage one and two of the ISDN ECT supplementary service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) based on TS 183 029 [1]. A further part of the present document specifies the Test Suite Structure and Test Purposes (TSS&TP), the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document. Within the TISPAN NGN Release 2 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The service provides a party involved in a communication to transfer that communication to a third party.
6c20142db410ff122a3cb510f7a6cc43	186 015-1	2 References	T References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
6c20142db410ff122a3cb510f7a6cc43	186 015-1	2.1 Normative references	The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 183 029: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification". [2] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 8.8.0 Release 8)".". [3] ISO/IEC 9646-7: "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements". ETSI ETSI TS 186 015-1 V2.1.1 (2009-07) 6
6c20142db410ff122a3cb510f7a6cc43	186 015-1	2.2 Informative references	The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
6c20142db410ff122a3cb510f7a6cc43	186 015-1	3 Definitions and abbreviations
6c20142db410ff122a3cb510f7a6cc43	186 015-1	3.1 Definitions	For the purposes of the present document, the terms and definitions specified in [1] apply.
6c20142db410ff122a3cb510f7a6cc43	186 015-1	3.2 Abbreviations	For the purposes of the present document, the abbreviations specified in [1] apply. 4 Protocol Implementation Conformance Statement proforma
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.1 Instructions for completing the PICS proforma	4.1.1 More detailed instructions are given at the beginning of the different subclauses of the PICS proforma. The supplier of the implementation shall complete the PICS proforma in each of the spaces provided, if necessary.
6c20142db410ff122a3cb510f7a6cc43	186 015-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 specification [1] to [2] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into subclauses for the following categories of information: • instructions for completing the PICS proforma; • identification of the implementation; • product supplier; • client; • PICS contact person; • PICS proforma tables (containing the global statement of conformance). ETSI ETSI TS 186 015-1 V2.1.1 (2009-07) 7
6c20142db410ff122a3cb510f7a6cc43	186 015-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 [3]. Item column It contains a number that identifies the item in the table. Item description column It describes each respective item (e.g. parameters, timers, etc.). Reference column It gives reference to the CDIV specification [1], except where explicitly stated otherwise. 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. n/a not applicable - in the given context, it is impossible to use the capability. No answer in the support column is required. o optional - the capability may be supported or not. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression that is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE n/a" shall be implied. NOTE: Support of a capability means that the capability is implemented in conformance to the specification(s) [1] to [2]. 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 or n/a no answer required (allowed only if the status is N/A, directly or after evaluation of a conditional status).
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.2 Identification of the implementation	Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if they are different. A person who can answer queries regarding information supplied in the ICS should be named as the contact person. ETSI ETSI TS 186 015-1 V2.1.1 (2009-07) 8
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.2.1 Date of the statement	Date of the statement:
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.2.2 Implementation Under Test (IUT) identification	IUT name: IUT version:
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.2.3 System Under Test (SUT) identification	SUT name: Hardware configuration: Operating system:
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.2.4 Product supplier	Name: Address: Telephone number: Facsimile number: Additional information:
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.2.5 Client	Name: Address: Telephone number: Facsimile number: Additional information:
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.2.6 PICS contact person	Name: Telephone number: Facsimile number: Additional information:
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.3 PICS proforma tables
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.3.1 Global statement of conformance	(Yes/No) Are all mandatory capabilities implemented? ETSI ETSI TS 186 015-1 V2.1.1 (2009-07) 9
6c20142db410ff122a3cb510f7a6cc43	186 015-1	4.3.2 Terminal and network capabilities	Table 1: Network capabilities Item Item description Reference Status Support 1 Is the blind transfer supported? 5.11.6 [2] o.11 2 Is the assured transfer supported? 5.11.6 [2] o.11 3 Is the consultative transfer supported? 5.11.6 [2] o.11 4 The AS initiate the special REFER handling procedures when a 403 Forbidden or 501 Not implemented is received after the REFERrequest is forwarded to the Transferee? 4.5.2.4.1.2.3 [1] o 5 The AS of the initiator of the REFER request that has prior knowledge that the remote party is not allowed to receive or does not support the REFER method, initiates the special REFER handling procedures directly? 4.5.2.4.1.2.3 [1] o 6 Does the Transferee AS reject the INVITE request sent to the Transfer Target if the Referred-By header does not match the stored Referred-By header of the received REFER? 4.5.2.7.3 [1] c21 7 Does the Transferee AS replaces the URI of the Referred-By header in the INVITE sent to the Transfer Target with the URI stored from the received REFER request, if there is no match? 4.5.2.7.3 [1] c22 8 Does the Transferee AS inserts a Referred-By header in the INVITE request sent to the Transfer Target if the Referred-By header is absent and the value is equal to the stored value received in the REFER request. 4.5.2.7.3 [1] o o.11: It is mandatory to support at least one of these items. c21: IF NOT 1/7 THEN o ELSE n/a. c22: IF NOT 1/6 THEN o ELSE n/a. Table 2: User Equipment capabilities Item Item description Reference Status Support 1 Is the blind transfer supported? 5.11.6 [2] o.21 2 Is the assured transfer supported? 5.11.6 [2] o.21 3 Is the consultative transfer supported? 5.11.6 [2] o.21 4 [Transferor] Is the UE able to Issue a REFER request in the original communications dialog to invoke the transfer of the session? 4.5.2.1 [1] c21 5 [Transferee] Is the UE able to handle a received REFER to transfer the current session? 4.5.2.5 [1] o o.21: It is mandatory to support at least one of these items. c21: IF 2.1 OR 2.2 OR 2.3 THEN m ELSE n/a. ETSI ETSI TS 186 015-1 V2.1.1 (2009-07) 10 History Document history V2.1.1 July 2009 Publication
057e018c19a0f5b48f5c34a406bf0790	188 005-1	1 Scope	The present document identifies the requirements for the NGN Network Resource Model (NRM). This NRM is an information model of the NGN Resources defined in the NGN specified by ETSI TISPAN which captures the management aspects (i.e. the management view of the NGN). Clause 4 of the present document captures the general requirements for the NRM. Clause 5 identifies the NGN subsystems and entities which are modelled in the NGN NRM. Annex A captures agreed Use Cases and annex B is an informative annex capturing proposed Use Cases. This version of the document is based on the TISPAN Release 1 architecture and may be updated to reflect changes in subsequent releases.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	2 References	References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	2.1 Normative references	The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 188 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); OSS requirements; OSS definition of requirements and priorities for further network management specifications for NGN". [2] ETSI TS 132 150: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Integration Reference Point (IRP) Concept and definitions (3GPP TS 32.150 version 6.5.0 Release 6)". [3] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1". [4] ETSI ES 282 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [5] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 6 [6] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture". [7] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
057e018c19a0f5b48f5c34a406bf0790	188 005-1	2.2 Informative references	The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 180 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Release 1; Release definition". [i.2] ETSI TS 182 012: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Subsystem; Functional architecture".
057e018c19a0f5b48f5c34a406bf0790	188 005-1	3 Abbreviations	For the purposes of the present document, the following abbreviations apply: AF Application Function AGCF Access Gateway Control Function AGF Access Gateway Function AMF Access Management Function A-MGF Access Media Gateway Function A-RACF Access Resource and Admission Control Function ARF Access Relay Function ASF Type 1 Application Server Function Type 1 ASF Type 2 Application Server Function Type 2 ASF Application Server Function BGCF Border Gateway Control Function BGF Border Gateway Function C-BGF Core Border Gateway Function CLF Connectivity session Location and repository Function CNGCF Customer Network Gateway Configuration Function FQDN Fully Qualified Domain Name IBCF Interconnection Border Control Function I-BGF Interconnection Border Gateway Function I-CSCF Interrogating Call Server Control Function IMS IP Multimedia System ISDN Integrated Services Digital Network IWF InterWorking Function L2TF Layer 2 Termination Function MGCF Media Gateway Control Function MRFC Multimedia Resource Function Controller MRFP Multimedia Resource Function Processor NACF Network Access Configuration Function NASS Network Attachment SubSystem NAT Network Address Translation NGN Next Generation Network NRM Network Resource Module OSS Operations Support Team P-CSCF Proxy Call Server Control Function PDBF Profile Data Base Function PES PSTN/ISDN Emulation Subsystem PSTN Public Switched Telephony Network ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 7 RACS Resource Admission Control Subsystem RCEF Resource Control Enforcement Function RGF Residential Gateway Function R-MGF Residential Media Gateway Function S-CSCF Serving Call Server Control Function SGF Signalling Gateway Function SLF Subscription Locator Function SPDF Service Policy Decision Function TE Terminal Equipment TISPAN Telecommunications and Internet Converged Services and Protocols for Advanced Networking TMF TeleManagement Team T-MGF Trunking Media Gateway Function UAAF User Access Authorization Function UE User Equipment UPSF User profile Service Function
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4 General requirements	The following general and high-level requirements apply for the NRM: • NRM related requirements in TR 180 001 [i.1]. The present document provides a description of the content and capabilities of NGN Release 1 which need to be supported by the NRM. • NRM related requirements in TS 188 003 [1]. The present document provides high level requirements for the NRM. • The use of the IRP Methodology in TS 132 150 [2]. The present document provides the documentation structure and concept for the NRM. • NGN Overall Functional Architecture ES 282 001 [3]. The present document identifies the subsystems and functional entities which make up the NGN.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4.1 Reuse of specifications	To avoid overlap and duplication, the Network Resource Model should import relevant definitions (e.g. Object classes, attributes, etc.) from the 3GPP, TMF, ITU-T etc. where appropriate.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4.2 Granularity of Managed Objects	This clause states requirements on the level of granularity for managed entities.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4.2.1 Motivation, remarks, or examples	Based on, (see ES 282 001 [3]), the TISPAN NGN overall architecture (see figure 2) is the starting point for decomposition of the TISPAN NGN. Entities of this overall architecture are further decomposed recursively. This decomposition is performed in three dimensions: • Decomposition into layer entities e.g. Service Layer, Transport Layer (see figure 2), or Transport Control Sublayer (see ES 282 001 [3]). A layer need not map to a manageable entity. Therefore this kind of decomposition does not motivate a requirement. • Decomposition into subsystems e.g. Core IMS, PSTN/ISDN Emulation Subsystem. This kind of decomposition motivates Requirement 1. • Decomposition into functional entities e.g. User Profile Service Function, UPSF (see figure 3), Transfer functions (see figure 2). This kind of decomposition motivates Requirement 2. ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 8
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4.2.2 Requirements	Requirement 1: • Each subsystem that has manageable aspects which are agreed on the basis of documented technical analysis performed on existing TISPAN specifications or are documented within an agreed Use case for an NGN management interface shall map to one manageable model element of the NGN Network Resource Model. Requirement 2: • Each functional entity that has manageable aspects which are agreed on the basis of documented technical analysis performed on existing TISPAN specifications or are documented within an agreed Use case for an NGN management interface shall map to one manageable model element of the NGN Network Resource Model.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4.3 Inter Domain Management
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4.3.1 Motivation, remarks, or examples	According to the NGN functional architecture (see ES 282 001 [3]), functional entities or subsystems may be distributed over network/service provider domain borders. E.g. a network attachment subsystem, an I-BGF, or a service-layer subsystem that supports nomadism may be distributed between a visited and a home network. Figure 1 is taken from ES 282 001 [3]. It illustrates this multi-domain context. Core Networks (transfer) Access Network (transfer) UE Visited Network Home Network Core Networks (transfer) Core Network (control) Core Network (control) Distributed Subsystem Figure 1: Example for a distributed Subsystem
057e018c19a0f5b48f5c34a406bf0790	188 005-1	4.3.2 Requirements	Requirement 1: • The Network Resource Model shall allow management of resources which are shared between administrative domains.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5 NGN Managed Entities	ES 282 001 [3] describes the overall TISPAN NGN functional architecture, its subsystems and the relationships between them. The present document, together with the Functional Architectures of the IMS (see ES 282 007 [7]), PES (see ES 282 002 [4]), IMS based PES (see TS 182 012 [i.2]), NAS (see ES 282 004 [5]), and RACS (see ES 282 003 [6]), identifies the entities with the NGN subsystems and the relationships between them. The requirement to manage these entities is documented in clause 4.3 (requirements A2 and A8) of TS 188 003 [1]. ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 9 Other networks Other subsystems Core IMS PSTN/ISDN Emulation subsystem User Equipment Service Layer Transport Layer Transfer Functions Resource and Admission Control Subsystem Network Attachment Subsystem Applications User profiles Figure 2: TISPAN NGN overall architecture The NGN functional architecture is split into 2 layers, "Service Layer" and "Transport Layer". The Functional Entities which form part of the Service Layer are described in clause 5.1, the Entities which form part of the Transport Layer are described in clause 5.2.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5.1 Analysis of Service Layer
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5.1.1 Common Managed Entities	The following entities are defined in ES 282 001 [3]. IBCF IWF Transfer Functions Transport control To/From other IP networks Service Control Subsystems Transport Layer Service Layer ASF (type 2) UPSF ASF (type 1) Data Collection Charging mediation Mediation to other management applications … SLF Figure 3: Common components overview ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 10 As a result of analysis, the following entities are required to be modelled in the NRM. TISPAN Entity Remark User profile service Function (UPSF) see note Subscription Locator Function (SLF) see note Application Server Function (ASF) Type 1 see note Application Server Function (ASF) Type 2 see note Interworking Function (IWF) see note Interconnection Border Control Function (IBCF) see note NOTE: This entity meets Requirement 2 of clause 4.2.2 because it is well defined and it is it should be able to generate alarms. See clause 5.1.2 for Entities within the IP Multimedia Subsystem (IMS). See clause 5.1.3 for Entities within the PSTN/ISDN Emulation Subsystem (PES). The inclusion of the following entities in the NRM is for further study. Proposed TISPAN Entity Remark Charging and Data Collection Function -
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5.1.2 The IMS	The following Core IMS entities are defined in ES 282 007 [7]. Other IP Networks IP Transport (Access and Core) T-MGF I-BGF AS UPSF P-CSCF I/S-CSCF BGCF SLF Charging Functions IWF « Core IMS» Mw Mw/Mk/Mm Mr Mg Mj Mi Mp Mn Gm Gq' ISC Cx Dx Dh Sh Ic Rf/Ro Rf/Ro Ib Iw Gq' PSTN/ISDN SGF MRFC MGCF MRFP Resource and Admission Control Subsystem Network Attachment Subsystem e2 Ie Mw IBCF Mk Mk UE Ut Figure 4: TISPAN IMS Components ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 11 As a result of analysis, the following entities are required to be modelled in the NRM. TISPAN Entity Remark BGCF see note 1 MRFC see note 1 MGCF see note 1 I-CSCF see note 1 S-CSCF see note 1 P-CSCF see note 1 NOTE 1: This entity meets Requirement 2 of clause 4.2.2 because it is well defined and it is able to generate alarms. NOTE 2: Modelling of interfaces (e.g. Cx, Mi, etc.) is for further study.
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5.1.3 PSTN/ISDN Emulation Subsystem	The following entities are defined in ES 282 002 [4]. Distributor Service A Service B Service C Master Customer Data Customer Location Trunk Routing Service 1 Service 2 Service 3 PSTN/ISDN Services AGCF TGCF SGCF AGF AGF S/T Z AS MGF e A - BGF I - BGF RACS IN PSTN / ISDN RG Gq’ Topology Hiding Gateway Other NGN’s Other NGN’s PSTN/ISDN Emulation Subsystem Transport b a a c f g h j i AGCF : Local Data NOTE: Lines inside the grey area are purely illustrative. Information flows may be through the Distributor or direct as an implementation option. Figure 5: PES Managed Components The inclusion of the following entities in the NRM is for further study. TISPAN Entity Remark Trunk Routing - Customer Location - Access Gateway Function (AGF) - Residential Gateway Function (RGF) - Media Gateway Function - ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 12
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5.1.4 IMS-based PSTN/ISDN Emulation Subsystem	The following entities are defined in TS 182 012 [i.2]. Other IP Networks IP Transport (Access and Core) T-MGF I-BGF UPSF BGCF Charging Functions IWF IMS-based PES Mw Mx Mr Mg Mj Mi Mp Mn Gm Gq' ISC/Ma Cx Dx Dh Sh Ic Rf/Ro Rf/Ro Ib Iw Gq' PSTN/ISDN SGF MRFC MGCF MRFP Resource and Admission Control Subsystem Ie Mw IBCF Mx Mk Other types of service logic PSTN/ISDN Emulation logic Application Servers Rf/Ro MG ZZ ZZ AGCF Gq' P1 Mw P3 Ut Ut Network Attachment Subsystem e2 e2 Mx P-CSCF VGW Ut I/S-CSCF SLF Figure 6: IMS Based PES Managed Components As a result of analysis, the following entities are required to be modelled in the NRM. TISPAN Entity Remark Access Gateway Control Function (AGCF) see note NOTE: The other FEs in IMS-based PES are already covered in clause 5.1.2. ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 13
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5.2 Analysis of Transport Layer
057e018c19a0f5b48f5c34a406bf0790	188 005-1	5.2.1 Transfer Functions	The following entities are defined in ES 282 001 [3]. T-MGF I-BGF C-BGF MRFP Transfer Functions SGF ARF RCEF Other networks User Equipment Service Layer A-MGF NASS RACS L2TF Figure 7: Transport Layer Managed Components As a result of analysis, the following entities are required to be modelled in the NRM. TISPAN Entity Remark A-MGF (Access) see note T-MGF (Trunking) see note C-BGF see note I-BGF see note RCEF see note ARF see note SGF see note MRFP see note NOTE: This entity meets Requirement 2 of clause 4.2.2 because it is well defined and should be able to generate alarms. The inclusion of the following entities in the NRM is for further study. TISPAN Entity Remark BGF - L2TF - R-MGF NOTE 1: See clause 5.2.2 for Entities within the NASS. NOTE 2: See clause 5.2.3 for Entities within the RACS. ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 14

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.