hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3.1 DNS | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3.1.1 Relevant Interfaces | The Domain Name Service (DNS) is considered as a supporting entity in this test specification. It is assumed that each IMS has its own local DNS which is connected to the common interconnect DNS. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3.1.2 Node Configuration | The common DNS should be configured for appropriate resource record handling as required to support proper resolution of all SIP URIs in Request URIs and Route headers. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3.2 ENUM | When testing a combination of local and external registries can be used to simulate all functions of the Tier 0, Tier 1 and Tier 2 registries operation plus all national and international interconnect scenarios. It is assumed that each IMS core may access a local ENUM solution and an external ENUM solution with query c... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3.2.1 Local ENUM Solution | Each IMS may access a local ENUM solution with query capabilities which allows retrieval of authoritative stored ENUM data (usually Tier 2 data) or authoritative cached ENUM data (any Tier). |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3.2.2 Common ENUM Solution | An external ENUM registry is provided by the GSMA PRD IR.67 [i.5] to simulate a Tier 0 global root, national Tier 1 registries and off board Tier 2 registries. Depending on the scenario in simulation the registry allows to resolve a TN either directly with the SIP URI of the appropriate interconnection point or indirec... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3.2.3 Node Configuration | The common ENUM solution should be configured to support a proper resolution of E.164 TNs into SIP URIs as defined in GSMA PRD IR.67 [i.5], clause 5.44 with reference to RFC 3761 [i.4] and RFC 3403 [i.6]. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.4 Test Configurations | The following architectural test configurations are referenced in the IMS NNI interoperability TDs in the present document. They are intended to give a general rather than a specific view of the required IMS core network SUT(s) connectivity and associated UE(s), AS(s), and DNS(s). NOTE: Note that in the following figur... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4 Use Cases | Use cases are the basis for interoperability test descriptions. Each use case defines both a generic test sequence, i.e. a set of user stimuli and observations for any number of involved IMS external entities (IMS UE, DNS Server, and AS), and a monitor view of all the resulting messages exchanged at the outer IMS core ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.1 IMS Registration in a Visited Network | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.1.1 Description | UE_B registers in a visiting network. The call flow path and node configuration for this use case corresponds to CF_ROAM_REG. The test sequence typically associated with this use case when an established session is released is as follows (CFW step numbers refer the call flow step numbering). Step Action CF_ROAM_REG 1 U... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.1.2 UC_01_R: SIP message flow for IMS registration with CF ROAM ROAM | The expected call flow sequence is: Step Direction Message Comment U s e r B U E B I M S A I B C F A I B C F B I M S B 1 User B triggers registration to IMS B 2 REGISTER UE_B sends a REGISTER to IMS_A 3 REGISTER IMS_A forwards the REGISTER to IBCF_A 4 REGISTER IBCF_A forwards the REGISTER to IBCF_B 5 REGISTER IBCF_B fo... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.2 User-initiated VoIP call setup and release | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.2.1 Normal Call | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.2.1.1 Description | UE_A places an IMS VoIP call to UE_B. Once the media path is established, the originating user releases the call. The call flow path and node configuration for this use case corresponds to CF_INT_CALL in case of interworking and CF_ROAM_CALL in case of roaming. ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 26 The test sequen... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.2.1.2 UC_02_I: SIP Call Flow "Normal Call" with CF_INT_CALL | The test sequence and expected call flow sequence when user A calls user B in an interworking scenario is: Step Action CF_INT_CALL 1 User A calls User B Step 1 2 User B is informed of incoming call of User A Step 14 3 User A is informed that UE_B is ringing Step 20 4 User B answers call Step 21 5 User A is informed tha... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.2.1.3 UC_02_R: SIP Call Flow "Normal Call" with CF_ROAM_CALL | The expected call flow sequence when user A calls user B in a roaming scenario is: Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired medias and codecs that 3 100 T... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.3 User-initiated call hold and resume | UE_A places an IMS VoIP call to UE_B. Once the media path is established: a) The originating user puts the call on hold, stopping the media stream. The originating user then resumes the call. b) The terminating user puts the call on hold, stopping the media stream. The terminating user then resumes the call. The call f... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.3.1 User-initiated call hold and resume using reINVITE | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.3.1.1 Description | The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_INT_CALL CF_ROAM_CALL 1 User A calls User B 1 1 2 User B is informed of incoming call of User A 14 20 3 User A is informed that UE_B is ringing 20 29 4 User B answers call 21 30 ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.3.2 User-initiated call hold and resume using UPDATE | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.3.2.1 Description | The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_INT_CALL CF_ROAM_CALL 1 User A calls User B 1 1 2 User B is informed of incoming call of User A 14 20 3 User A is informed that UE_B is ringing 20 29 4 User B answers call 21 30 ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.4 IMS message exchange between UEs in different networks | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.4.1 Description | The UE_A sends a MESSAGE to UE_B located in a different network. The test sequence typically associated with this use case when an established session is released is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_INT_CALL CF_ROAM_CALL 1 User A sends an instant message Step 1 Step 1 2 U... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.4.2 UC_05_I: SIP Call flow for IMS Message Exchange with CF_INT_CALL | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 1 User A sends an instant message to user B 2 MESSAGE UE_A sends MESSAGE to IMS_A 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A 5 MESSAGE IMS_A s... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.4.3 UC_05_R: SIP Call Flow for IMS Message Exchange with CF_ROAM_CALL | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 1 User A sends an instant message to user B 2 MESSAGE UE_A sends MESSAGE to IMS_A 3 ENUM IMS_A sends query to ENUM DB 4 ENUM ENUM DB sends response to IMS_A 5 MESSAGE IMS_A s... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.5.1 Description | UE_A makes an IMS VoIP call to UE_B. UE_A is subscribed to OIR service in permanent mode or default presentation restricted temporary mode, UE_B is subscribed to ACR supplementary service. The call flow path and node configuration for this use case corresponds to CF_INT_AS when UE_B is in home network and to CF_ROAM_AS... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.5.2 UC_06_I: SIP message flow for SS ACR with CF_INT_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired 3 100 Trying IMS_A responds with a 100 Trying provisional respons... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.5.3 UC_06_R: SIP message flow for SS ACR with CF_ROAM_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired media and codecs that UE_B supports 3 100 Trying IMS_A responds w... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.6 Supplementary Service Outgoing Communication Barring (OCB) | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.6.1 Description | UE_B places an IMS VoIP call to UE_A. UE_B is subscribed to OCB service and based on the UE_B identity the OCB service is invoked. The call flow path and node configuration for this use case corresponds to CF_INT_AS when UE_B is in home network and to CF_ROAM_AS when UE_B is roaming in IMS_A. The test sequence typicall... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.6.2 UC_07_I: SIP message flow for SS OCB with CF_INT_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S B 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired media and codecs that UE_B supports 3 100 Trying IMS_B responds with a ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.6.3 UC_07_R: SIP message flow for SS OCB with CF_ROAM_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A I B C F A I B C F B E N U M DB I M S B A S B 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired media and codecs that 3 100 Trying IMS_A responds with a 100 Trying pro... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.7 Supplementary Service Originating Identification Presentation (OIP) | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.7.1 Description | UE_A places an IMS VoIP call to UE_B. UE_B is subscribed to OIP service. The call flow path and node configuration for this use case corresponds to CF_INT_AS when UE_B is in home network and to CF_ROAM_AS when UE_B is roaming in IMS_A. The test sequence typically associated with this use case when is as follows (CFW st... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.7.2 UC_08_I: SIP message flow for SS OIP with CF_INT_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 EN... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.7.3 UC_08_R: SIP message flow for SS OIP with CF_ROAM_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB I B C F A I B C F B I M S B A S B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired media and codecs that UE_A supports 3 100 Trying IMS_A responds with a ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.8 Supplementary Service Originating Identification Restriction (OIR) | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.8.1 Description | UE_B places an IMS VoIP call to UE_A. UE_A is subscribed to OIP service, UE_B is subscribed to OIR service in permanent mode or default presentation restricted temporary mode. The call flow path and node configuration for this use case corresponds to CF_INT_AS when UE_B is in home network and to CF_ROAM_AS when UE_B is... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.8.2 UC_09_I: SIP message flow for SS OIR with CF_INT_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired 3 100 Trying IMS_B responds with a 100 Trying provisional respons... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.8.3 UC_09_R: SIP message flow for SS OIR with CF_ROAM_AS | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A A S A I B C F A I B C F B E N U M DB I M S B A S B 1 User B calls User A 2 INVITE UE_B sends INVITE with the first SDP offer indicating all desired media and codecs that UE_B supports 3 100 Trying IMS_A responds w... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.9 Supplementary Service HOLD | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.9.1 Description | UE_A places an IMS VoIP call to UE_B which places the call on HOLD. UE_A will be notified by the AS that the call is on hold. UE_B will resume the call, and UE_A will be informed by the AS that the call is resumed. The test sequence typically associated with this use case when is as follows (CFW step numbers refer the ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.10 Supplementary Service Call Forward Unconditional (CFU) | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.10.1 Description | UE_A places an IMS VoIP call to UE_B which has CFU activated towards user UE_B2 which is located in IMS_A. UE_A may be notified by the AS that the call is forwarded. UE_B2 answers the call without previous ringing indication. The call is released by UE_A. The test sequence typically associated with this use case when i... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.10.1.3 UC_12: SIP Call Flow "Normal Call" with 2 UEs registered to same public identity | The test sequence and expected call flow sequence when user A calls user B with 2 UEs, i.e. UE_B1 and UEB2, in an interworking scenario is: Step Action CF_INT_CALL 1 User A calls User B Step 1 2 User B is informed of incoming call of User A on UE_B1 Step 14 3 User B is informed of incoming call of User A on UE_B2 Step ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.11 Addition of media stream | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.11.1 Description | UE_A and UE_B are in an established session with one or more media streams. While in the established session, UE_A adds a new media stream. It is assumed that both UEs are registered in their respective networks. The test sequence and expected call flow sequence for addition of multimedia stream can be illustrated when... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.11.1.1 UC_13: SIP Call Flow "Addition of media stream using reINVITE" | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 1 User A calls User B 2 INVITE UE_A sends INVITE with the first SDP offer indicating all desired medias and codecs 3 100 Trying IMS_A responds with a 100 Trying provisional r... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.12 Removal of media stream | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.12.1 Description | UE_A and UE_B are in an established session with multiple media streams. While in the established session, UE_A removes a media stream. It is assumed that both UEs are registered in their respective networks. The test sequence and expected call flow sequence for multimedia session handling (when remote user interaction... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.12.1.1 UC_14: SIP Call Flow "Removal of media streams using UPDATE" | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 1 User A initiates a multimedia session with at least two streams with User B 64A User A removes one of the media streams 65A UPDATE UE_A sends UPDATE to IMS_A 66A UPDATE IMS... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.12.1.2 UC_15: SIP Call Flow "Removal of media streams using reINVITE" | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A E N U M DB I B C F A I B C F B I M S B U E B U s e r B 1 User A initiates a multimedia session with at least two streams with User B 64A User A removes one of the media streams 65A INVITE UE_A sends reINVITE to IMS_A 66A 100 Tryi... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.13 Ad-hoc Conferencing service | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.13.1 Description | UE A registered on IMS network A, initiates an ad-hoc conf call via CONF AS, connected over ISC interface to IMS core A, and subsequently invites UE B (registered in IMS B) to join the conf. This Use Case requires support for MRFC and MRFP functionalities on IMS_A. The test sequence when user A initiates an ad-hoc conf... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.13.2 UC_16: SIP Call Flow "Ad-hoc Conference call" | The expected call flow sequence is: Step Direction Message Comment U s e r A U E A U s e r B U E B I M S A E N U M DB A S A I B C F A I B C F B I M S B A S B 1 User A initiates an ad-hoc conference call 2 INVITE UE_A sends INVITE to IMS_A with information for all commonly 3 100 Trying IMS_A responds with a 100 Trying p... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.14 Presence service | The use case for the presence service is defined in TS 102 901 [17]. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15 IPTV service | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.1 Broadcast (BC) Session | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.1.1 Description | UE_A starts a session initiation procedure to join a multicast channel. This test requires the use of application server as specified in [14]. The call flow path and node configuration for this use case corresponds to CF_IPTV. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.1.2 UC_19: BC session | The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_IPTV 1 User A initiates a BC session Step 1 2 User A receives the broadcast content Step 8 3 User A terminates the session Step 9 4 User A is informed that session is terminated ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.2 Content on Demand (CoD) Session | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.2.1 Description | UE_A starts a session initiation procedure for a streaming session of a selected content. TS 183 063 [14] specifies two methods for establishing a streaming session (called RTSP Method 1 and 2). This test requires the use of application server, playing the roles of Service control Function (SCF) and Media Function (MF)... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.3 Request for Network PVR offline capture | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.3.1 Description | UE_A starts a N-PVR offline capture procedure to record a live programme that has not started yet. Once the capture has finished, UE_A establishes a CoD session to receive the streaming content using RTSP Method 1 or RTSP Method 2. The scope of this Use Case is to describe the capturing procedure, since CoD session is ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.15.3.2 UC_22: Request for Network PVR offline capture. | The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_INT_IPTV 1 User A requests to record a live programme that has not started yet Step 1 2 User A is informed that recording has started Step 6 The expected call flow sequence is: S... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.16 IMS-PSTN Interoperability | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.16.1 IMS-to-PSTN call | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.16.1.1 Description | UE_A places an IMS VoIP call to a user that is located in a PSTN environment (UE_B). Once the media path is established, the originating user or the destination user releases the call. The call flow path and node configuration for this use case corresponds to CF_PSTN. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.16.1.2 UC_23: IMS-to-PSTN call | The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CFW 1 User A calls User B Step 1 2 User B is informed of incoming call of User A Step 15 3 User A is informed that UE_B is ringing Step 19 4 User B answers call Step 20 5 User A is ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.16.2 PSTN-to-IMS call | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.16.2.1 Description | UE_B that is located in a PSTN environment places a call towards UE_A that is located in the IMS. Once the media path is established, the originating user or the destination user releases the call. The call flow path and node configuration for this use case corresponds to CF_PSTN. ETSI ETSI TS 186 011-2 V4.1.3 (2012-05... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.4.16.2.2 UC_24: PSTN-to-IMS call | The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CFW 1 User B calls User A Step 1 2 User A is informed of incoming call of User B Step 17 3 User B is informed that UE_A is ringing Step 21 4 User A answers call Step 22 5 User A is ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5 Test Descriptions | This clause introduces interoperability test descriptions (TDs) which realize one or more IMS NNI test purposes of TS 186 011-1 [2]. Each TD is defined on the basis of one of the generic use cases forms presented in the previous clause. Each test sequence step in a TD includes also a reference to a specific call flow s... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.1 General Capabilities | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.1.1 SIP messages longer than 1 500 bytes | Interoperability Test Description Identifier: TD_IMS_MESS_0001 Summary: IMS network shall support SIP messages greater than 1 500 bytes Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_4002_1 TS 124 229 [1], clause 4.2A ¶1 Use Case ref.: UC_05_I Pre-test conditions: • HSS of... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.1.2 ENUM Query - Functionality test | Interoperability Test Description Identifier: TD_IMS_ENUM_0001 Summary: ENUM query should result in return of NAPTR with correct SIP URI Configuration: CF_INT_CALL SUT: ENUM _A and ENUM_DB References: Test Purpose Specification Reference TP_IMS_ENUM_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 10 in 1st numbered list) U... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.2 Registration and De-registration | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.2.1 First time registration in a visited IMS network | Interoperability Test Description Identifier: TD_IMS_REG_0001_AKA Summary: First time registration in a visited IMS network Configuration: CF_ROAM_REG SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5011_01 TS 124 229 [1], clauses 5.2.2.1 ¶16 (2nd numbered list) and 5.2.2.2 TP_IMS_5011_02 T... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.2.2 No response from first entry point on REGISTER without topology hiding | Interoperability Test Description Identifier: TD_IMS_REG_0002 Summary: IMS network chooses a second entry point to the home network of a user that requested registration, if the first entry point does not answer, without topology hiding. Configuration: CF_ROAM_REG SUT: IMS_A References: Test Purpose Specification Refer... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.2.4 Network initiated deregistration by the S-CSCF | Interoperability Test Description Identifier: TD_IMS_REG_0005 Summary: IMS network can initiate user de-registration, e.g., when a user runs out of credit Configuration: CF_ROAM_REG SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5093_01 TS 124 229 [1], clause 5.4.1.5 ¶6 (1st numbered list) Use Case ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.2.5 Network initiated re-authentication by the S-CSCF | Interoperability Test Description Identifier: TD_IMS_REG_0006 Summary: IMS network can initiate user re-authentication Configuration: CF_ROAM_REG SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5094_01 TS 124 229 [1], clause 5.4.1.6 ¶2 Use Case ref.: UC_01_R Pre-test conditions: • HSS of IMS_B is con... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.3 Initial Dialog or Subsequent Procedures | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.3.1 Initial INVITE Dialog Procedures | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.3.1.1 Initial INVITE Request Procedures - Originating | 4.5.3.1.1.1 Default SIP URI with DNS/ENUM lookup procedure Interoperability Test Description Identifier: TD_IMS_CALL_0001 Summary: IMS network can handle establishment of dialogs for users with default SIP URIs and resolve Tel URI E.164 numbers Configuration: CF_INT_CALL SUT: IMS_A and IMS_B References: Test Purpose Sp... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.3.1.2 Dialogue Procedures with Roaming | 4.5.3.1.2.1 Normal call Interoperability Test Description Identifier: TD_IMS_CALL_0007 Summary: IMS network handles normal call while UE_B is roaming without topology hiding correctly Configuration: CF_ROAM_CALL SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5046_01 TS 124 229 [1], clause 5.2.6.3.3 ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.3.1.3 Subsequent Request Procedures - Originating Network | 4.5.3.1.3.1 Call CANCEL by calling user Interoperability Test Description Identifier: TD_IMS_CALL_0014 Summary: IMS network handles correctly calling user cancelling call before its establishment Configuration: CF_INT_CALL SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5107_03 TS 124 229 [1], clause... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.3.1.4 Dialogue Procedures - Topology Hiding | 4.5.3.1.4.1 Normal call Interoperability Test Description Identifier: TD_IMS_CALL_0024 Summary: IMS network handles basic call with topology hiding correctly Configuration: CF_INT_CALL SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_5135_01 TS 124 229 [1], clause 5.10.4.1 ¶7 (after note 4) TP_IMS_513... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4 Messaging | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.1 Messaging with ENUM lookup procedure | Interoperability Test Description Identifier: TD_IMS_MESS_0004 Summary: IMS network handles messaging with DNS/ENUM lookup procedure correctly Configuration: CF_INT_CALL SUT: IMS_A References: Test Purpose Specification Reference TP_IMS_ENUM_01 TS 124 229 [1], clause 5.4.3.2 ¶11 (item 10 in 1st numbered list) TP_IMS_50... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.2 Messaging with SIP URI public identities | Interoperability Test Description Identifier: TD_IMS_MESS_0002 Summary: IMS network handles messaging with SIP identity correctly without topology hiding Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5097_05 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5097_06 TS 124 229 [1],... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.3 Messaging with TEL URI identities | Interoperability Test Description Identifier: TD_IMS_MESS_0003 Summary: IMS network handles messaging with TEL URI identities correctly Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5097_07 TS 124 229 [1], clause 5.4.3.2 ¶1 TP_IMS_5117_02 TS 124 229 [1], clause 5.4.3.3 ¶1... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.4 Messaging when roaming | Interoperability Test Description Identifier: TD_IMS_MESS_0005 Summary: IMS network handles messaging while roaming correctly Configuration: CF_ROAM_CALL SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5108_02 TS 124 229 [1], clause 5.4.3.3 ¶5 (1st numbered list) TP_IMS_5118_01 TS 124 229 [... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.5 Messaging with receiving user not registered | Interoperability Test Description Identifier: TD_IMS_MESS_0006 Summary: IMS network handles messaging correctly when receiving user is not registered Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5114_02 TS 124 229 [1], clause 5.4.3.3 ¶85 (item 3 in 3rd numbered list) Use... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.4.6 Messaging with receiving user barred | Interoperability Test Description Identifier: TD_IMS_MESS_0007 Summary: IMS network handles messaging correctly when receiving user has been barred Configuration: CF_INT_CALL SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5108_06 TS 124 229 [1], clause 5.4.3.3 ¶6 (item 1 in1st numbered list) Use Cas... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5 Supplementary Services | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.1 Supplementary Service HOLD with AS | Interoperability Test Description Identifier: TD_IMS_SS_0001 Summary: IMS network supports properly application services based on the example of the HOLD supplementary service Configuration: CF_INT_AS SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5310_01 TS 124 229 [1], clause 5.4.6.1.2 ¶1 TP_IMS_5... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.2 Supplementary Service HOLD with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0002 Summary: IMS network supports properly application services based on the example of the HOLD supplementary service Configuration: CF_ROAM_AS SUT: IMS_B References: Test Purpose Specification Reference TP_IMS_5310_01 TS 124 229 [1], clause 5.4.6.1.2 ¶1 TP_IMS_... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.3 Supplementary Service OIP with AS | Interoperability Test Description Identifier: TD_IMS_SS_0003 Summary: IMS network supports properly application services based on the example of the OIP supplementary service Configuration: CF_INT_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5097_02 TS 124 229 [1], clause 5.4.3.2 ¶11 ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.5.5.4 Supplementary Service OIP with AS in roaming | Interoperability Test Description Identifier: TD_IMS_SS_0004 Summary: IMS network supports properly application services based on the example of the OIP supplementary service Configuration: CF_ROAM_AS SUT: IMS_A and IMS_B References: Test Purpose Specification Reference TP_IMS_5097_02 TS 124 229 [1], clause 5.4.3.2 ¶11... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.