hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.2 Protocols, Security and Points of Observation | The IMS-EPC IOP tests employ SIP and Diameter protocol signalling, as well as transparent media (e.g. RTP). Figure 4: Points of Observation for Test Protocols User Plane data as SIP and media is to be transported transparently between the UE and the P-CSCF, respectively MGW/correspondent-UE. The Point of Observation (P... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.3 Test Infrastructure | This clause covers the list of relevant components and interfaces used for testing interoperability between EPC and AF represented by IMS. For components that are not present, standard functionality is assumed. |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.3.1 HSS/SPR | Subscriber data (TS 123 008 [i.4]) such as profile, location and subscriptions are located for IMS in the central database Home Subscriber Server/Universal Profile Server Function (HSS/UPSF), while EPC uses as a central database the Subscription Profile Repository (SPR). The data between the HSS and SPR has to be corre... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.3.3 PCRF (EPC) | The Policy and Charging Control (PCC) is ensured through the Policy Decision Point, namely the Policy Charging and Rules Function (PCRF) and several Policy Enforcement Points located in the EPC gateways (TS 123 203 [i.5]). The PCRF interfaces with the AF (P-CSCF in our IMS case) over the Rx reference point. The service... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.3.4 P-GW (EPC) | The Packet Data Network (PDN) Gateway provides transparent IP connectivity between the AF over multiple gateways and a radio link to the UE. The P-GW acts as IPv6 mobility anchor between trusted and un-trusted 3GPP and non-3GPP technologies and performs packet filtering, charging as well as IP address allocation. |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.3.5 User Endpoints | The test infrastructure must contain also User Endpoints. These are represented by client devices or simulators, capable of performing the EPC and IMS procedures. The Use Cases and Test Descriptions have been developed such that during execution, only one client dev ice has to be observed. The counterpart UE in calls f... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.4 Reference Points and Protocols | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.4.1 The SGi reference point (IP) | The SGi reference point, performs User-Plane generic IP interfacing, breaking out the user IP data from the EPC plane towards the Application Functions (IMS, Internet, etc). Towards the UTRAN/E-UTRAN or non-3GPP access, this data is transported always as tunnelled and not merely routed on IP principles, such that the S... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.4.1.1 The Gm reference point (SIP) | The Gm reference point represents the 1st hop in SIP signalling between the UE and the IMS network represented by the P-CSCF. Its scope is to provide a secure SIP signalling channel, independent of the access network level security. As such, with the exception of initial security negotiations, all signalling should be ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.4.1.2 The Mb reference point between PDN and MGW (IP/UDP/RTP) | The Media Gateway (MGW) interconnects the circuit with the packet switched domain by converting RTP into CS correspondents and vice versa. The MGW is able to adapt the service rate and to change the used codec based on changes in the network. For the interoperability purposes here, only the correct exchange of the pack... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.4.2 The Rx reference point between AF and PCRF (Diameter) | As the policy signalling interface, the Rx interface will be monitored for correct signalling as derived from the specific test described SIP signalling. For the purpose of charging event notifications and bearer level event notifications, the Rx signalling will be monitored for correct activity as well as for correct ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 5.5 Applicable 3GPP Release Number | The targeted 3GPP TS version for applicable procedures is Release 10, with the latest published versions. However, considering the purposes of these tests to attest base IOP between two different systems from potentially different vendors, much of the functionality has been kept to a minimum, while exhaustive conforman... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6 Use Cases (Conformance Criteria) | This clause will present the main Use Cases to be tested. The Use Cases are general Test Purposes and as such are defined more or less abstract. These Use Cases are then used as blueprints for generating groups of Test Descriptions, which describe scenario instantiations of the Use Cases. |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.1 Network Attachment and Default Bearer Operations | The attachment to the EPC system is customized based on the specific Access Network types. For the purposes of the IMS-EPC interoperability, the Network Attachment procedures will be considered as the procedures for UTRAN, E-UTRAN, WiMAX or Wi-Fi/ePDG attachments. In all (or in subsequent) tests, any of these attachmen... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.1.1 Initial Network Attachment and Establishment of the Default Bearer | Figure 5: Initial Network Attachment The test assumes that the UE has been provisioned with the proper credentials for performing network authentication and attachment(e.g in the USIM application). Correspondent provisioning is also assumed on the SPR in the EPC, such that network attachments can be successfully conduc... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.2 IMS Registration and AF Signalling Bearer Operations | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.2.1 IMS Initial Registration | PCRF P‐CSCF PGw UE A EPC IMS 4. 401 Unauthorized (challenge) 5. REGISTER (response) 8a. 200 OK 8b. AAR 11. RAR 12. Installation of the IMS Signaling Bearer 13. RAA 10. AAA S‐CSCF 2. REGISTER 3. 401 Unauthorized (challenge) 6. REGISTER (response) 7. 200 OK 1. REGISTER 14. IMS Signaling Possible over Dedicated Bearer 9. ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.2.2 IMS De-registration | Figure 8: IMS De-registration The test assumes that the UE has been previously registered to IMS. The test procedure will follow an IMS de-registration initiated by the UE. The P-CSCF should trigger a termination of the IMS signalling bearer in the EPC. Signalling between the UE and the P-CSCF should still be possible,... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.2.3 IMS De-registration with Active Sessions | Figure 9: IMS UE De-registration with Active Session The test assumes that an UE has been previously attached to EPC, performed and IMS registration and established a SIP session. The session is considered to be active at the moment of the test. The test procedure will trigger an UE-initiated de-registration. On this e... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.2.4 IMS Administrative De-Registration | PCRF P‐CSCF PGw UE A EPC IMS 6b. STR 8. RAR 9. Removal of the IMS Signaling Bearer 10. RAA 7. STA S‐CSCF 1. NOTIFY {UE} Event: reg {de‐registration} 4. 200 OK (NOTIFY UE) 2. NOTIFY {UE} Event: reg {de‐registration} 3. 200 OK (NOTIFY UE) 5. NOTIFY {P‐CSCF} Event: reg {de‐registration} 6a. 200 OK (NOTIFY P‐CSCF) Figure 1... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.2.5 IMS Registration Expiration | Figure 11: IMS Registration Expiration The test assumes that the UE has been previously attached to EPC and registered to IMS. The test procedure will follow the registration expiration in the P-CSCF, which will trigger the termination of the IMS signalling session in EPC. The test will verify that: 1) The P-CSCF will ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3 SIP Session and Session Bearer Operations | The SIP Session and Session Bearer Operations cover the allocation, modification and deletion of EPC bearers for the media data between two UEs. As long as the bearers are present, media can be transported in both direction. The respective bearers will have QoS and charging characteristics according to the EPC's operat... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.1 SIP Session Establishment | The test assumes that the UE A for originating cases and UE B for terminating cases have been previously attached to EPC and registered to IMS. The test procedure will follow the IMS call setup procedures. The test will verify that: 1) The P-CSCF will act on successful call establishment and trigger creation of call be... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.1.1 Originating Leg | PCRF P‐CSCF PGw UE A EPC A IMS A S‐CSCF 1.INVITE (SDP Offer) 2.INVITE (SDP Offer) 3.INVITE (SDP Offer) 4.200 OK (SDP Answer) 5.200 OK (SDP Answer) 12. 200 OK (SDP Answer) 6. AAR 8. RAR 10. RAA 7. Policy Decision 9. Installation of the Session Bearer 11. AAA UE B Not Possible Not Possible Media Exchange Figure 12: SIP S... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.1.2 Terminating Leg | Figure 13: SIP Session Establishment - Terminating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 36 Test Purpose Identifier: TP_IMSEPC_Session_Establishment_Terminating Summary: On successful call setup, the P-CSCF should derive from the SDP offer and answer, descriptions of the Service Data Flow. These are pushed towards ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.2 SIP Session Modification | There are multiple reasons for session modifications, like for example adding or removing video to an audio call. For exemplification, here we will consider the simple case of a Call-Hold scenario, for muting the audio stream. Additional scenarios can be built and presented in the Test Descriptions. The test assumes th... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.2.1 Originating Leg | PCRF P‐CSCF PGw UE A EPC A IMS A S‐CSCF 1. Re‐INVITE (SDP Call‐on‐Hold) 2. Re‐INVITE (SDP Call‐on‐Hold) 3. Re‐INVITE (SDP Call‐on‐Hold) 4.200 OK 5.200 OK 11. 200 OK 6. AAR 7. RAR 9. RAA 8. Modification of the Session Bearer 10. AAA UE B Not Possible Not Possible Audio Media Exchange Figure 14: SIP Session Modification ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.2.2 Terminating Leg | PCRF P‐CSCF PGw UE B EPC B IMS B S‐CSCF 1. Re‐INVITE (SDP Call‐on‐Hold) 2. Re‐INVITE (SDP Call‐on‐Hold) 3. Re‐INVITE (SDP Call‐on‐Hold) 4.200 OK 10. 200 OK 5. AAR 6. RAR 8. RAA 7. Modification of the Session Bearer 9. AAA 11. 200 OK UE A Not Possible Not Possible Audio Media Exchange Figure 15: SIP Session Modification... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.3 SIP Session Release | This Use Case follows the removal of the session bearers during the normal release procedures of an already established session. The test assumes that the UE A/B has been previously attached to EPC and registered to IMS. A call is assumed to have been successfully established. The test procedure will follow the Call Re... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.3.1 Originating Leg | Figure 16: SIP Session Tear-down - Originating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 42 Test Purpose Identifier: TP_IMSEPC_Session_Release_Originating Summary: On call release, the P-CSCF should trigger the removal of all relevant previously created bearers. EPC removes the bearers for media. Media transport is no ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.3.2 Terminating Leg | Figure 17: SIP Session Tear-down - Terminating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 43 Test Purpose Identifier: TP_IMSEPC_Session_Release_Terminating Summary: On call release, the P-CSCF should trigger the removal of all relevant previously created bearers. EPC removes the bearers for media. Media transport is no ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.4 SIP Session Abort/Reject | This Use Case follows the unsuccessful session setup. Either the call is aborted in the originating side or rejected in the terminating side. The test assumes that the UE A/B has been previously attached to EPC and registered to IMS. The test procedure will follow the initiation of a session. Early-Media can be establi... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.4.1 SIP Session Abort | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.4.1.1 Originating Case | PCRF P‐CSCF PGw UE A EPC A IMS A S‐CSCF 1.INVITE (SDP Offer) 2.INVITE (SDP Offer) 3.INVITE (SDP Offer) 4.180 Ringing 5. 180 Ringing 11.180 Ringing 12. CANCEL 14. CANCEL 13. CANCEL 15a. 200 OK (CANCEL) 15b. 487 Req. Term. (INVITE) 16a. 200 OK (CANCEL) 16bb. 487 Req. Term. (INVITE) 22. 487 Req. Term. (INVITE) 17a.200 OK ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.4.1.2 Terminating Leg | PCRF P‐CSCF PGw UE B EPC B IMS B S‐CSCF 1. INVITE (SDP Offer) 2. INVITE (SDP Offer) 3. INVITE (SDP Offer) 15a.200 OK (CANCEL) 16a. 200 OK (CANCEL) 17a. 200 OK (CANCEL) 12. CANCEL 13. CANCEL 14. CANCEL 15b. 487 Req. Term. (INVITE) 21. 487 Req. Term. (INVITE) 22b. 487 Req. Term. (INVITE) 16ba. ACK 22a. ACK 23. ACK 5. AAR... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.4.2 SIP Session Reject | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.4.2.1 Originating Case | PCRF P‐CSCF PGw UE A EPC A IMS A S‐CSCF 1.INVITE (SDP Offer) 2.INVITE (SDP Offer) 3.INVITE (SDP Offer) 11.486 Busy Here 12b. 486 Busy Here 18. 486 Busy Here 19. ACK 12a. ACK 13a. ACK 4.180 Ringing 5. 180 Ringing 6. AAR 7. RAR 9. RAA 8. Installation of Early‐media Bearer 10. AAA 13b. STR 14. RAR 16. RAA 15. Removal of t... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.4.2.2 Terminating Leg | PCRF P‐CSCF PGw UE B EPC B IMS B S‐CSCF 1. INVITE (SDP Offer) 2. INVITE (SDP Offer) 3. INVITE (SDP Offer) 12. 486 Busy Here 18. 486 Busy Here 19b. 486 Busy Here 13a. ACK 19a. ACK 20. ACK 5. AAR 6. RAR 8. RAA 7. Installation of Early‐media Bearer 9. AAA 4.180 Ringing 10. 180 Ringing 11. 180 Ringing 13b. STR 14. RAR 16. ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 6.3.5 EPC Initiated Bearer Modification | Administrative termination of SIP sesion PCRF P‐CSCF PGw UE A EPC IMS 4. ASR 3. CCA 7. STA S‐CSCF 2. CCR 1. Bearer Release Event 5. ASA 6. STR 8b. BYE 9a. 200 OK 8a. BYE 9b. 200 OK Media Exchange UE B Media Exchange Not Possible Media Exchange Not Possible Figure 22: EPC Initiated Bearer Modification This Use Case foll... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7 Test Descriptions | The Test Descriptions present individual scenario instantiations of the Use Cases, which are no longer abstract, but present a definitive signalling and procedural flow through the test's execution. As a very high number of scenarios can be generated, for all possible outcomes and options of an Use Case, here only the ... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.1 Network Attachment and Default Bearer Operations | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.1.1 Initial Network Attachment and Establishment of the Default Bearer | Interoperability Test Description Identifier: TD_IMSEPC_Network_Attachment Summary: On successful initial network attachment, the UE should discover the P-CSCF IP address. The EPC will create the Default Bearers which will allow communication only between the UE and the P-CSCF. Config.: CF_IMSEPC SUT: IMS and EPC Ref.:... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2 IMS Registration and AF Signalling Bearer Operations | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2.1 IMS Initial Registration | Besides the successful registration, a secondary abnormal case is considered, of a failed registration. The outcome will be that the signalling bearer is or is not established. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 58 |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2.1.1 IMS Initial Registration - Successful | Interoperability Test Description Identifier: TD_IMSEPC_Registration_Initial_Successful Summary: On successful initial registration, the P-CSCF shall request at the PCRF the allocation of a bearer for SIP signalling. The PCRF should act on the request and allocate the bearer. Subsequent signalling should make use of th... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2.1.2 IMS Initial Registration - Failed | Interoperability Test Description Identifier: TD_IMSEPC_Registration_Initial_Failed Summary: On failed UE Registration to IMS, IMS will not trigger the creation of a bearer for the transport of the subsequent SIP signalling. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment Use Case Ref.: TP_IMSEPC... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2.2 IMS De-registration | Interoperability Test Description Identifier: TD_IMSEPC_DeRegistration_UE Summary: On UE_A de-registration, P-CSCF signals to PCRF the termination of the IMS signalling session. EPC removes the IMS signalling bearer. Initial registration are still possible, but traffic will be categorized in the Default Bearer. Config.... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2.3 IMS De-registration with Active Sessions | Interoperability Test Description Identifier: TD_IMSEPC_DeRegistration_UE_Active_Session Summary: On UE A de-registration, the S-CSCF performs S-CSCF-initiated termination of active session. P-CSCF will act on this event and signals to PCRF termination of the SIP session bearers. EPC removes the SIP Session bearer. Med... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2.4 IMS Administrative De-Registration | Interoperability Test Description Identifier: TD_IMSEPC_DeRegistration_Administrative Summary: On administrative de-registration, S-CSCF notifies the UE A and P-CSCF about the event. P-CSCF signals to PCRF the termination of the IMS signalling session. EPC removes the IMS signalling bearer. Initial registration are sti... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.2.5 IMS Registration Expiration | Interoperability Test Description Identifier: TD_IMSEPC_DeRegistration_Expiration Summary: On registration expiration, P-CSCF signals to PCRF the termination of the IMS signalling session. EPC removes the IMS signalling bearer. Initial registration are still possible, but traffic will be categorized in the Default Bear... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3 SIP Session and Session Bearer Operations | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1 SIP Session Establishment | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.1 Originating Leg | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.1.1 With SDP Negotiation in INVITE/200 OK | Interoperability Test Description Identifier: TD_IMSEPC_Session_Establishment_Originating_1 Summary: On successful call setup, the P-CSCF should derive from the SDP offer and answer, descriptions of the Service Data Flow. These are pushed towards EPC as request for creation of adequate bearers. EPC creates based on the... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.1.2 With SDP Negotiation in 200 OK/ACK | Interoperability Test Description Identifier: TD_IMSEPC_Session_Establishment_Originating_2 Summary: On successful call setup, the P-CSCF should derive from the SDP offer and answer, descriptions of the Service Data Flow. These are pushed towards EPC as request for creation of adequate bearers. EPC creates based on the... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.1.3 Without SDP Negotiation in the initial SIP transaction | Interoperability Test Description Identifier: TD_IMSEPC_Session_Establishment_Originating_3 Summary: On successful call setup without SDP negotiation (no SDP-offer/answer in the initial SIP INVITE Request / 200 OK Response / ACK Request), there is no request for establishing media bearers from the P-CSCF towards EPC. M... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.2 Terminating Leg | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.2.1 With SDP Negotiation in INVITE/200 OK | Interoperability Test Description Identifier: TD_IMSEPC_Session_Establishment_Terminating_1 Summary: On successful call setup, the P-CSCF should derive from the SDP offer and answer, descriptions of the Service Data Flow. These are pushed towards EPC as request for creation of adequate bearers. EPC creates based on the... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.2.2 With SDP Negotiation in 200 OK/ACK | Interoperability Test Description Identifier: TD_IMSEPC_Session_Establishment_Terminating_2 Summary: On successful call setup, the P-CSCF should derive from the SDP offer and answer, descriptions of the Service Data Flow. These are pushed towards EPC as request for creation of adequate bearers. EPC creates based on the... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.1.2.3 Without SDP Negotiation in the initial SIP transaction | Interoperability Test Description Identifier: TD_IMSEPC_Session_Establishment_Terminating_3 Summary: On successful call setup without SDP negotiation (no SDP-offer/answer in the initial SIP INVITE Request / 200 OK Response / ACK Request), there is no request for establishing media bearers from the P-CSCF towards EPC. M... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.2 SIP Session Modification | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.2.1 Originating Leg | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.2.1.1 With removal of SDF (e.g. Call-Hold) | Interoperability Test Description Identifier: TD_IMSEPC_Session_Modification_Originating_1 Summary: On successful call hold, the P-CSCF should derive from the SDP offer and answer, updates for the Service Data Flows. These are pushed towards EPC as request for modification of the previously created bearers. EPC modifie... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.2.1.2 With addition of SDF (e.g. Call-Resume) | Interoperability Test Description Identifier: TD_IMSEPC_Session_Modification_Originating_2 Summary: On successful call resume, the P-CSCF should derive from the SDP offer and answer, updates for the Service Data Flows. These are pushed towards EPC as request for modification of the previously created bearers. EPC modif... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.2.2 Terminating Leg | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.2.2.1 With removal of SDF (e.g. Call-Hold) | Interoperability Test Description Identifier: TD_IMSEPC_Session_Modification_Terminating_1 Summary: On successful call hold, the P-CSCF should derive from the SDP offer and answer, updates for the Service Data Flows. These are pushed towards EPC as request for modification of the previously created bearers. EPC modifie... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.2.2.2 With addition of SDF (e.g. Call-Resume) | Interoperability Test Description Identifier: TD_IMSEPC_Session_Modification_Terminating_2 Summary: On successful call resume, the P-CSCF should derive from the SDP offer and answer, updates for the Service Data Flows. These are pushed towards EPC as request for modification of the previously created bearers. EPC modif... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.3 SIP Session Release | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.3.1 Originating Leg | Interoperability Test Description Identifier: TD_IMSEPC_Session_Release_Originating Summary: On call release, the P-CSCF should trigger the removal of all relevant previously created bearers. EPC removes the bearers for media. Media transport is no longer possible, after the session release. Config.: CF_IMSEPC SUT: IMS... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.3.2 Terminating Leg | Interoperability Test Description Identifier: TD_IMSEPC_Session_Release_Terminating Summary: On call release, the P-CSCF should trigger the removal of all relevant previously created bearers. EPC removes the bearers for media. Media transport is no longer possible, after the session release. Config.: CF_IMSEPC SUT: IMS... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.4 SIP Session Abort/Reject | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.4.1 SIP Session Abort | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.4.1.1 Originating Leg | Interoperability Test Description Identifier: TD_IMSEPC_Session_Abort_Originating Summary: On session abort, the P-CSCF should trigger the removal of all relevant previously created early-media bearers. EPC removes the bearers for early-media. Media transport is no longer possible, after the session abort. Config.: CF_... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.4.1.2 Terminating Leg | Interoperability Test Description Identifier: TD_IMSEPC_Session_Abort_Terminating Summary: On session abort, the P-CSCF should trigger the removal of all relevant previously created early-media bearers. EPC removes the bearers for early-media. Media transport is no longer possible, after the session abort. Config.: CF_... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.4.2 SIP Session Reject | |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.4.2.1 Originating Leg | Interoperability Test Description Identifier: TD_IMSEPC_Session_Reject _Originating Summary: On session reject, the P-CSCF should trigger the removal of all relevant previously created early-media bearers. EPC removes the bearers for early-media. Media transport is no longer possible, after the session reject. Config.:... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.4.2.2 Terminating Leg | Interoperability Test Description Identifier: TD_IMSEPC_Session_Reject _Terminating Summary: On session reject, the P-CSCF should trigger the removal of all relevant previously created early-media bearers. EPC removes the bearers for early-media. Media transport is no longer possible, after the session reject. Config.:... |
f007f46b47c7aca93cf16c00c4eb9e20 | 103 029 | 7.3.5 EPC Initiated Bearer Modification | Interoperability Test Description Identifier: TD_IMSEPC_Bearer_Modification Summary: On removal of all bearers, EPC PCRF will notify IMS P-CSCF that Rx session should be aborted. IMS will take action and terminate all ongoing SIP sessions and the IMS registration. Configuration: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSE... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 1 Scope | The present document specifies interoperability Test Descriptions (TDs) for Inter-IMS Network to Network Interface (II-NNI) interoperability testing for the Rich Communication Suite (RCS) related services based on RCS-e Advanced Communications Services and Client Specification [11]. The Stage 3 Session Initiation Proto... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 229 (V8.10.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project AS (IMS) Application Server CF (Test) ConFiguration CFW Call FloW CN Core Network CSCF Call Session Control Function DNS Domain Name System FQDN Full Qualified Domain Name HSS Home Subscriber Server IBCF... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4 IMS NNI Interoperability Test Specification | |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.1 Introduction | The IMS NNI Interoperability Test Descriptions (TDs) defined in the following clauses are derived from the Test Purposes (TPs) specified in TS 186 011-1 [2]. The TDs cover the services (instant messaging, content sharing and presence) as defined in RCS-e specification [8]. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.2 Test Prerequisites | The test prerequisites as described in TS 186 011-2 [9], clause 4.2, apply. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3 Test Infrastructure | The test infrastructure as described in TS 186 011-2 [9], clause 4.3, applies with the following additions. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.1 Core IMS Nodes | |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.2 External IMS core Nodes | |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.2.1 HSS | Table 1 of TS 186 011-2 [9], clause 4.3.1.5.2, has to be extended by the following users for RCS services. Table 1: Additional HSS sample user profiles for RCS Private Identity Public Identity 1 (SIP URI) Public Identity 2 (Tel URI) Default Public Identity Filter criteria userPRES_priv userPRES na 1 contact Presence AS... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.2.2 Specific Application Servers for RCS-e | Interworking between external Application Servers (AS) and the IMS core is under the scope of the present document. The ISC interface between the S-CSCF and the AS is used as a Point of Observation (PO) for NNI interoperability tests. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.2.2.1 Presence Server | The presence server is an optional AS that acts as an intermediate for the user to provide Social Presence information to other users and other users to subscribe or get Social Presence information of a certain user, i.e. Presentity. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.2.2.2 IM Server | The IM server is an AS within the IMS architecture that provides the IM service for the subscribers. It is responsible for a set of functions such as the control of the session setup, the enforcement of policies related to incoming or outgoing IM, the provision of information related to group members. Optionally the IM... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.2.2.3 Node Configuration | The AS should be configured to support the pre-requisites outlined in TS 186 011-2 [9], clause 4.2. The test descriptions in the present document assume that an AS supports the use of the IM/chat service and the following optional services: Social Presence, RCS-e services during a call and File transfer (see RCS-e desc... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.3.3 Test Configurations | The test configurations as described in TS 186 011-2 [9] clause 4.3.4 apply. It should be mentioned that test configurations for roaming scenarios are considered as optional. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.4 Use Cases | In addition to the Use Cases in the present clause the Use Cases as described in TS 186 011-2 [9], clause 4.4 apply. It should be mentioned that Use Cases for roaming scenarios are considered as optional. |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.4.1 Capability discovery | |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.4.1.1 General description | According to the RCS-e specification [8] the capability or service discovery mechanism as the main process for retrieving the subset RCS-e services available for other contacts is based on two methods: • capability discovery process through OPTIONS message; • capability discovery via presence. Capability discovery proc... |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.4.2 Social Presence service | |
8cd5b88eda99ed076f2e555b906d5fdc | 102 901 | 4.4.2.1 General description | According to RCS-e specification [11] the Social Presence service is assumed to be optional. If the Social Presence service is implemented on the network there could be also provided the capability discovery mechanism via presence as mentioned in the clause 4.4.1. In all Social Presence service Use Cases provided below... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.