hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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 packets between the UE and the MGW will be observed, according to the requested session parameters. Besides measurements for checking the correct delivery and enforcement of traffic QoS, priority levels and charging, negative testing is to be employed to verify that once the session bearers are removed, further media traffic is being filter out by the EPC.
|
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 actions on the involved nodes. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 17 For practical test reasons, as with the Gm interface, security is to be disabled on this interface for the scope of interoperability monitoring. Interoperability with the security features enabled can be verified by re-executing the scenarios in scope and verifying only the end-events and not the Rx interface data.
|
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 conformance testing is out of the scope of the present document. As such, Release 9 implementations should still be able to perform most of the tests without major difficulties.
|
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 attachment procedures can be employed, considering the characteristics of the respective Radio Access Technologies (RAT) to provide bearer-based services. The specific network attachment procedure themselves, employed by the UE to attach to EPC, are out of scope of these tests and will not be presented. Only the common and minimalistic set of operations between all of them is considered to be provided by the EPC system: • the presence of a BBERF inside the specific AN-GW (e.g. S-GW, ePDG) with a Gxx interface to the PCRF; • the presence of a PCEF inside the P-GW with a Gx interface to the PCRF. The Gx and Gxx flows are also out of scope, only their resulting effects as triggered by the Network Attachments, Bearer Modifications, IP-CAN changes, RAT Type changes and Network Detachments will be investigated, as being transmitted over the Rx interface to the P-CSCF and as such influencing the IMS system. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 18
|
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 conducted. The Initial Attachment procedures used as a reference are those from TS 129 212 [6], clause 4.5.1, 1 for Gx, respectively clause 4a.5.1 1 for Gxx, as well as from TS 124 229 [2], clause L.2.2.1 for UE initiated procedures. PCC policies for the creation of Default Bearers are assumed as pre-provisioned in the PCRF, such that the aforementioned procedures will result in the creation and acceptance of a Default Bearer allowing communication only between the UE and the P-CSCF. Communication between UE and other IP endpoints outside of the EPC network (UE - ANDSF communication over the S14 interface may still be allowed for functional reasons) will be denied (the default PCC gating policy will be set to "Deny"). Such a policy will allow for easier identification of correct bearer allocation and usage during the tests. In case the EPC system supports the delivery to the UE of a network-provided P-CSCF address (e.g. DHCPv6 options), this is also assumed to be provisioned in the EPC system. Otherwise, the P-CSCF address should be provisioned in the alternative mechanisms (e.g. ISIM stored, DNS), such that in any situation, at the end of the network attachment procedure, the UE can exchange the initial SIP REGISTER request with the P-CSCF. The test procedure will perform an Initial Attachments to the EPC system, sequentially verifying the request and allocation of: 1) an IPv4 APN context 2) an IPv6 APN context 3) a dual IPv4 and IPv6 APN context ETSI ETSI TS 103 029 V3.1.1 (2011-11) 19 The test will verify the following outcomes: 1) The network attachment is successful and the UE receives IP addresses according to the requested APN contexts. 2) The P-CSCF address is discovered by the UE (optional, if this is network provided). 3) A default bearer is established, allowing the exchange of a SIP REGISTER request and answer between the UE and the P-CSCF. 4) IP communication to other IP endpoints than the P-CSCF is denied (optional). Test Purpose Identifier: TP_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 IUT Role: EPC Ref.: TS 124 229 [2], clause 9.2.1 (Connecting to the IP-CAN and P-CSCF discovery) TS 124 229 [2], clause L.2.2.1 (EPS bearer context activation and P-CSCF discovery) TS 129 212 [6], clause 4.5.1-1) (PCC procedures over Gx reference point / Request for PCC Rules) TS 129 212 [6], clause 4a.5.1-1) (PCC procedures over Gx reference point / Gateway control and QoS Rules Request) Entities Condition UE A EPC IMS UE B ✓ ✓ Network attachment credential provisioned in UE A and EPC ✓ ✓ EPC and UE A provisioned with selectable APN configurations for IPv4, IPv6 or IPv4&IPv6 PDN types ✓ P-CSCF address provisioned in the EPC for the purpose of delivery to UE A on attachment ✓ Default Bearer PCRF policies set to allow UE A - P-CSCF communication Default EPC Gating Policy set to “deny” UE A not attached to network and EPC UE A EPC IMS UE B Step Direction Message 1 UE A attachment to RAN requests parameter containing APN according to the required IPv4 and/or IPv6 attachment 2 UE A attachment to RAN responses, including the P-CSCF address one or two parameters containing UE A IPv4 and/or IPv6 address parameter containing P-CSCF IP address or P-CSCF FQDN 3 Establishment of Default Bearers Service-Data-Flow (Uplink) “permit in ip from <ue_ip> to <pcscf_ip>” Service-Data-Flow (Downlink) “permit out ip from <pcscf_ip> to <ue _ip>” Default Gating Policy “deny” 4 SIP REGISTER Request Contact header 5 SIP REGISTER Response 6 || IP packet from UE A to UE B || not delivered to UE B 7 || IP packet from UE B to UE A || not delivered to UE A ETSI ETSI TS 103 029 V3.1.1 (2011-11) 20 6.1.2 Network Detachment with Previously Established IMS Registration and sessions Administrative termination of the SIP Registration Administrative termination of SIP sesion PCRF P‐CSCF PGw UE A EPC IMS 4b. ASR 3. CCA 4a. Removal of all User Bearers 7b. STA S‐CSCF 2. CCR 1. Remove IP‐CAN Session Request 5b. ASA 6b. STR 8b. BYE 9b. 200 OK 5a. Remove IP‐CAN Session Response 8c. REGISTER Expires: 0 9c. 200 OK 4c. ASR 7c. STA 5c. ASA 6c. STR Figure 6: Network Detachment The test assumes that the UE has previously been attached to network and EPC, with a single attachment, such that a detach command will result in a complete disconnection of the UE. The UE has registered to IMS. The UE has one active IMS session (call). A complete UE network detachment will be triggered, without previously triggering and orderly IMS de-registration and session termination. In case the UE employed in the test will not support this partial operation, an administrative network detachment should be triggered from the EPS. The test will verify the following outcomes: 1) The event is sent over the Rx interface to the P-CSCF in the IMS system. 2) The session bearers are removed in EPC. 3) The IMS signalling bearer is removed in EPC. 4) The Default Bearer is removed and any communication with the UE is interrupted. 5) The IMS system will perform administrative termination of ongoing sessions belonging to the UE. 6) The IMS system will perform IMS de-registration of the UE. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 21 Test Purpose Identifier: TP_IMSEPC_Network_Detachment Summary: On UE A network detachment EPC will inform the IMS about the IP-CAN session termination. EPC will remove all bearers related to the respective UE A. IMS will take action and terminate all ongoing SIP sessions and the IMS registration. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.8.1.2 (P-CSCF-initiated call release / Release of an existing session) TS 129 214 [5], clause 4.4.6.1 (IP-CAN Session Termination) Entities Condition UE A EPC IMS ✓ ✓ UE A attached to EPC, with a single attachment ✓ ✓ UE A registered in IMS ✓ ✓ UE A has an active SIP session established UE A EPC IMS Step Direction Message 1 UE A or EPC triggers complete network detachment 2a EPC removes the SIP session related bearer 2a.1a Diameter Abort-Session-Request Session-Id AVP session for active SIP Session Abort-Cause AVP BEARER_RELEASED (0) 2a.2a Diameter Abort-Session-Answer Session-Id AVP session for active SIP Session Result-Code AVP DIAMETER_SUCCESS(2001) 2a.3a Diameter Session-Termination-Request Session-Id AVP session for active SIP session 2a.4a Diameter Session-Termination-Answer Session-Id AVP session for active SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 2a.1b SIP BYE Request Request-URI stored Contact header field provided by UE B To header To header field value as received in the 200 (OK) response for initial INVITE request From header From header field value as received in initial INVITE request Call-ID header Call-Id header field value as received in initial INVITE request CSeq header current CSeq value stored for direction from calling to called user, incremented by one Route header routeing information towards called user as stored for dialog Reason header 503 (Service Unavailable) response code 2a.1c SIP BYE Response 2b EPC removes the IMS signalling bearer 2b.1a Diameter Abort-Session-Request Session-Id AVP session for IMS Signalling Abort-Cause AVP BEARER_RELEASED (0) 2b.2a Diameter Abort-Session-Answer Session-Id AVP session for IMS Signalling Result-Code AVP DIAMETER_SUCCESS(2001) ETSI ETSI TS 103 029 V3.1.1 (2011-11) 22 2b.3a Diameter Session-Termination-Request Session-Id AVP session for IMS Signalling 2b.3a Diameter Session-Termination-Answer Session-Id AVP session for IMS Signalling Result-Code AVP DIAMETER_SUCCESS(2001) 3 SIP REGISTER Request Request-URI stored domain URI for affected IMPU To header affected IMPU From header affected IMPU Contact header affected contacts Authorization header scheme “Digest” username as storred IMPI for initial registration realm as stored realm for initial registration uri as stored domain for initial registration “integrity-protected=yes” Expires header “0” Reason header 503 (Service Unavailable) response code 4 SIP BYE Response ETSI ETSI TS 103 029 V3.1.1 (2011-11) 23
|
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. Policy Decision Figure 7: IMS Initial Registration The test assumes that a network attachment has been previously performed and the P-CSCF address has been discovered, such that the UE can send the initial REGISTER request to the P-CSCF. The test procedure will perform an IMS initial registration of the UE to the IMS system. On successful completion, the IMS should trigger the provisioning of the AF signalling flow information, for the purpose of reserving a communication bearer in the EPC for transporting the subsequent IMS signalling. The test will verify the following outcomes: 1) IMS correctly produces the Media-Component-Description AVP for IMS signalling between UE and P-CSCF 2) An IMS signalling bearer is created in the EPC 3) The IMS signalling is transported between the UE and the P-CSCF (PO_UE and PO_Gm) 4) The IMS signalling bearer is used to transport the IMS signalling between the UE and IMS with the following parameters ( see TS 123 203 [i.5]): QoS Class Identifier Resource- Type Priority Packet Delay Budget Packet Error Loss Rate Example Services 5 Non-GBR 1 100 ms 10-6 IMS Signalling ETSI ETSI TS 103 029 V3.1.1 (2011-11) 24 Test Purpose Identifier: TP_IMSEPC_Registration_Initial 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 the respective bearer's QoS and priority characteristics. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.4.1.2 (Initial registration and user-initiated re-registration) TS 129 214 [5], clause 4.4.5a (Provisioning of AF Signalling Flow Information) TS 129 214 [5], clause A.8 (Provision of Signalling Flow Information at P-CSCF) TS 129 214 [5], annex B (Flow identifiers: Format definition and examples) Entities Condition UE A EPC IM S ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE and IMS ✓ UE A provisioned in IMS UE A not registered with IMS UE A EPC IM S Step Direction Message 1 SIP REGISTER Request 2 SIP 2xx Response 3 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE_A IP Media-Component-Description AVP Media-Component-Number AVP “0” one or more Media-Sub-Component AVP Flow-Number AVP Flow-Description AVP (Uplink) “permit in ip from <ue_a_ip> <ue_a_port> to <pcscf_ip> <pcscf_port>” Flow-Description AVP (Downlink) “permit out ip from <pcscf_ip> <pcscf_port> to <ue_a_ip> <ue_a_port>” Flow-Usage AVP AF_SIGNALING(0) Flow-Status AVP ENABLED(2) AF-Signalling-Protocol AVP SIP(1) 4 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP Observations: 1) In the Flow-Description AVP, instead of protocol "ip", alternative values as "udp" or "tcp" can be used. These are more specific, but might require the use of multiple Media-Sub-Component AVP. 2) The Flow-Number AVP is derived according to the respective rules in TS 129 214 [5], annex B. 3) The IP address and port of the UE A and P-CSCF should mirror the values "on wire" used by the SIP protocol. Special attention has to be taken for situations when these might differ from the values in the SIP Contact header (e.g. 3GPP-IPsec security on Gm). ETSI ETSI TS 103 029 V3.1.1 (2011-11) 25
|
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, yet the traffic should be classified in the Default Bearer, which should still be active. The test will verify the following outcomes: 1) The UE de-registration will trigger the termination of the Rx session for IMS signalling. 2) The EPC will remove the bearer for IMS signalling between the UE and the P-CSCF. 3) An initial IMS registration is still possible, yet the remaining Default Bearer will be used. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 26 Test Purpose Identifier: TP_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.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.4.1.4.1 (User-initiated de-registration / Normal cases) TS 129 214 [5], clause 4.4.5a (Provisioning of AF Signalling Flow Information) TS 129 214 [5], clause 4.4.4 (AF Session Termination) TS 129 214 [5], clause A.8 (Provision of Signalling Flow Information at P-CSCF) Entities Condition UE A EPC IM S ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for the UE A UE A EPC IM S Step Direction Message 1 SIP REGISTER Request Expires header “0” Contact header all currently registered contact addresses 2 SIP 2xx Response 3 Diameter Session-Termination-Request Session-Id AVP session for IMS signalling session 4 Diameter Session-Termination-Answer Session-Id AVP session for IMS signalling session Result-Code AVP DIAMETER_SUCCESS(2001) 4 SIP REGISTER Request Contact header 5 SIP REGISTER Response ETSI ETSI TS 103 029 V3.1.1 (2011-11) 27
|
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 event the S-CSCF will perform a S-CSCF initiated call release. On receiving the call release, the P-CSCF will act and trigger the termination of the SIP session bearers in the EPC. As a result, SIP session media will be filtered and should no longer pass the EPC, in either direction. Eventually the S-CSCF will also respond to the IMS de-registration. On receipt of the response, the P-CSCF will trigger the termination of the IMS signalling bearer. The test will verify the following outcomes: 1) Active SIP sessions and their associated bearers are removed. 2) Session's media will be filtered-out by EPC, as the session bearers have been removed and the Default Bearer has a default policy of "deny". 3) The IMS signalling bearer is removed. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 28 Test Purpose Identifier: TP_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. Media cannot be exchange any longer on previous SIP Session bearer. The S-CSCF answers to the de-registration. The P-CSCF signals to PCRF the termination of IMS signalling session. EPC removes IMS signalling bearer. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.4.1.4.1 (User-initiated de-registration) TS 124 229 [2], clause 5.4.5.1 (S-CSCF-initiated call release) TS 129 214 [5], clause 4.4.5a (Provisioning of AF Signalling Flow Information) TS 129 214 [5], clause 4.4.4 (AF Session Termination) TS 129 214 [5], clause A.8 (Provision of Signalling Flow Information at P-CSCF) Entities Condition UE A EPC IM S UE B ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for the UE A ✓ ✓ ✓ UE A in an active SIP session with UE B ✓ ✓ ✓ ✓ A SIP session bearer established between UE A and other communication endpoint Default EPC gating policy set to “deny” UE A EPC IM S UE B Step Direction Message 1 Session Media from UE A to UE B delivered to UE B 2 Session Media from UE B to UE A delivered to UE A 3 SIP REGISTER Request Expires header “0” Contact header all currently registered contact addresses 4 SIP BYE Request Request-URI contact address from stored Contact header To header From or To header as received in initial INVITE request To header From or To header as received in initial INVITE request Call-ID header stored Call-ID header CSeq header stored value for respective direction, incremented by one Route header routeing information for respective direction Reason header 5 SIP 2xx Response 6 Diameter Session-Termination-Request Session-Id AVP session for SIP session 7 Diameter Session-Termination-Answer Session-Id AVP session for SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 8 || Session Media from UE A to UE B || not delivered to UE B 9 || Session Media from UE B to UE A || not delivered to UE A ETSI ETSI TS 103 029 V3.1.1 (2011-11) 29 10 Diameter Session-Termination-Request Session-Id AVP session for IMS signalling session 11 Diameter Session-Termination-Answer Session-Id AVP session for IMS signalling session Result-Code AVP DIAMETER_SUCCESS(2001) Observations: 1) The actual use of the Default Bearer for an eventual IMS initial registration is no longer tested, as TD_IMSEPC_DeRegistration_UE should be sufficient to check this functionality. 2) It is not relevant what the other endpoint of the active SIP session is. However, care should be taken such that the media will not fall-back on the Default Bearer when removing the SIP session bearer, but be filtered-out by the default gating policy of "Deny".
|
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 10: IMS Administrative De-Registration The test assumes that the UE has been previously attached to EPC and registered to IMS. As part of the IMS registration, both the UE and the P-CSCF have subscribed to the "reg" event at the S-CSCF, such that they are following the registration status of the UE in the S-CSCF. The test procedure will trigger an administrative de-registration of the UE, in the HSS or S-CSCF. This will trigger "reg" event notifications to the be sent. When the P-CSCF receives this, it will delete the respective entries from its internal registrar and it will terminate the IMS signalling session towards EPC. The EPC will then delete the respective bearers, such that signalling will no longer be possible, but by using the Default Bearer. The test will verify that: 1) The P-CSCF will act on the de-registration notification and will terminate the IMS signalling session 2) The EPC will remove the IMS signalling bearer 3) UE signalling is still possible by using the Default Bearer ETSI ETSI TS 103 029 V3.1.1 (2011-11) 30 Test Purpose Identifier: TP_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 still possible, but traffic will be categorized in the Default Bearer. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.4.1.5 (Network-initiated de-registration) TS 129 214 [5], clause 4.4.5a (Provisioning of AF Signalling Flow Information) TS 129 214 [5], clause 4.4.4 (AF Session Termination) TS 129 214 [5], clause A.8 (Provision of Signalling Flow Information at P-CSCF) Entities Condition UE A EPC IMS ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for the UE A UE A EPC IMS Step Direction Message 1 SIP NOTIFY Request Request-URI UE contact address for SUBSCRIBE dialog Event header “reg” Body indicating complete de-registration of all relevant UE contacts and identities 2 SIP 2xx Response 3 SIP NOTIFY Request Request-URI P-CSCF contact address for SUBSCRIBE dialog Event header “reg” Body indicating complete de-registration of all relevant UE contacts and identities 4 SIP 2xx Response 5 Diameter Session-Termination-Request Session-Id AVP session for IMS signalling session 6 Diameter Session-Termination-Answer Session-Id AVP session for IMS signalling session Result-Code AVP DIAMETER_SUCCESS(2001) 7 SIP REGISTER Request Contact header 8 SIP REGISTER Response ETSI ETSI TS 103 029 V3.1.1 (2011-11) 31
|
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 act on the registration expiration and will terminate the IMS signalling session 2) The EPC will remove the IMS signalling bearer 3) UE signalling is still possible by using the Default Bearer ETSI ETSI TS 103 029 V3.1.1 (2011-11) 32 Test Purpose Identifier: TP_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 Bearer. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 129 214 [5], clause 4.4.5a (Provisioning of AF Signalling Flow Information) TS 129 214 [5], clause 4.4.4 (AF Session Termination) TS 129 214 [5], clause A.8 (Provision of Signalling Flow Information at P-CSCF) Entities Condition UE A EPC IMS ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for the UE A UE A EPC IMS Step Direction Message 1 Registration timer expiration 2 Diameter Session-Termination-Request Session-Id AVP session for IMS signalling session 3 Diameter Session-Termination-Answer Session-Id AVP session for IMS signalling session Result-Code AVP DIAMETER_SUCCESS(2001) 4 SIP REGISTER Request Contact header 5 SIP REGISTER Response
|
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 operator profiles and preferences. For verifying the different characteristics, both audio and video media can be exchanged, each with different bearer policies. As the bearers are modified or deleted, media traffic will be filtered-out by EPC. To achieve this effect, the same default EPC gateway policy set to "Deny" will be employed, like in the previous Use Cases. To simplify the signalling, the 2nd endpoint of the communication can be an IMS network service (e.g. gateway to a PSTN phone, media server, etc), such that the operations will only be triggered on a single side of the communication. Alternatively, two UEs can be employed and the originating and terminating Use Cases merged into common tests. In any situation though, the Use Case will assume that just the UE in scope for the respective originating/terminating case will be attached to and using EPC services. It has to be considered that the SDP negotiation during the SIP session establishment, can happen in various ways: • SDP offer in INVITE and SDP answer in 200 OK; • SDP offer in INVITE and SDP answer in 183 Progress; • SDP offer in INVITE and SDP offer in 180 Ringing; • SDP offer in 200 OK and SDP answer in ACK; • no SDP negotiation in the initial transaction. The relevant scenario paths are described in individual Test Descriptions of the same SIP Session Establishment Use Case. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 33 The tests are following in principle the IMS call setup, modification and release procedures. They are not named as "calls" as the "SIP Session" term will encompass broader Use Cases, beyond the use of IMS for telephony purposes. Each Use Case is described both for the originating and terminating situations.
|
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 bearers. 2) Media is only transported after the call setup is successfully completed (tests will start media before call setup and verify that the default EPC gating policy of "Deny" will initially stop the media). 3) The EPC will create new bearers for transporting call's media. 4) The media bearer is used to transport the media between the UEs with the following parameters (see TS 123 203 [i.5]): QoS Class Identifier Resource- Type Priority Packet Delay Budget Packet Error Loss Rate Example Services 1 GBR 2 100 ms 10-2 Conversational Voice 2 GBR 4 150 ms 10-3 Conversational Video (Live Streaming)
|
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 Session Establishment - Originating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 34 Test Purpose Identifier: TP_IMSEPC_Session_Establishment_Originating 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 EPC's operator policies the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible only after the successful establishment of the session. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.7.2 (Initial INVITE / Originating Case) TS 129 214 [5], clause 4.4.1 (Initial Provisioning of Session Information) TS 129 214 [5], clause A.1 (Provision of Service Information at the P-CSCF) TS 129 214 [5], clause A.2 (Enabling of IP Flows) TS 129 214 [5], annex B (Flow identifiers: Format definition and examples) Entities Condition UE A EPC IMS UE B ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE A UE A EPC IMS UE B Step Direction Message 1 || Session Media from UE A to UE B || not delivered to UE B 2 || Session Media from UE B to UE A || not delivered to UE A 3 SIP INVITE Request Body SDP offer 4 SIP 2xx Response Body SDP answer 5 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 2xx Response Body SDP answer 8 Session Media from UE A to UE B delivered to UE B 9 Session Media from UE B to UE A delivered to UE A ETSI ETSI TS 103 029 V3.1.1 (2011-11) 35
|
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 EPC as request for creation of adequate bearers. EPC creates based on the EPC's operator policies the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible only after the successful establishment of the session. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.7.3 (Initial INVITE / Terminating Case) TS 129 214 [5], clause 4.4.1 (Initial Provisioning of Session Information) TS 129 214 [5], clause A.1 (Provision of Service Information at the P-CSCF) TS 129 214 [5], clause A.2 (Enabling of IP Flows) TS 129 214 [5], annex B (Flow identifiers: Format definition and examples) Entities Condition UE B EPC IMS UE A ✓ ✓ UE B attached to EPC and pre-provisioned a default bearer for enabling communication between UE B and IMS ✓ ✓ UE B registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for the UE B UE B EPC IMS UE A Step Direction Message 1 || Session Media from UE B to UE A || not delivered to UE A 2 || Session Media from UE A to UE B || not delivered to UE B 3 SIP INVITE Request Body SDP offer 4 SIP 2xx Response Body SDP answer 5 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 2xx Response Body SDP answer 8 Session Media from UE B to UE A delivered to UE A 9 Session Media from UE A to UE B delivered to UE B ETSI ETSI TS 103 029 V3.1.1 (2011-11) 37
|
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 that the UE A/B have been previously attached to EPC and registered to IMS. A call has been successfully established, and both audio and video media are flowing. The test procedure will follow the Call-Hold procedures, removing the audio media from the call. The test will verify that: 1) The P-CSCF will act on successful call session modification and trigger modification of call bearer. 2) The EPC will modify the call's media bearers accordingly. 3) Audio media will not be transported after the session modification. Tests will continue transmitting audio media after the session modification and verify that the default EPC gating policy of "Deny" will stop (only) the audio media.
|
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 - Originating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 38 Test Purpose Identifier: TP_IMSEPC_Session_Modification_Originating 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 modifies, based on the EPC's operator policies, the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible, after the successful modification of the session, only on the remaining active Service Data Flows. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.9.1 (Subsequent requests / UE-originating Case) TS 129 214 [5], clause 4.4.2 (Modification of Session Bearers) TS 129 214 [5], clause A.1 (Provision of Service Information at the P-CSCF) TS 129 214 [5], clause A.2 (Enabling of IP Flows) TS 129 214 [5], annex B (Flow identifiers: Format definition and examples) Entities Condition UE A EPC IMS UE B ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE A ✓ ✓ ✓ ✓ An IMS call/session established between UE A and UE B, with 2 media components - audio and video UE A EPC IMS UE B Step Direction Message 1 Session Audio Media from UE A to UE B delivered to UE B 2 Session Audio Media from UE B to UE A delivered to UE A 3 SIP re-INVITE Request Body SDP update for removing audio 4 SIP 2xx Response Body SDP update answer 5 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 2xx Response Body SDP update answer 8 || Session Audio Media from UE A to UE B || not delivered to UE B 9 || Session Audio Media from UE B to UE A || not delivered to UE A ETSI ETSI TS 103 029 V3.1.1 (2011-11) 39
|
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 - Terminating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 40 Test Purpose Identifier: TP_IMSEPC_Session_Modification_Terminating 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 modifies, based on the EPC's operator policies, the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible, after the successful modification of the session, only on the remaining active Service Data Flows Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.9.2 (Subsequent requests / UE-terminating Case) TS 129 214 [5], clause 4.4.2 (Modification of Session Bearers) TS 129 214 [5], clause A.1 (Provision of Service Information at the P-CSCF) TS 129 214 [5], clause A.2 (Enabling of IP Flows) TS 129 214 [5], annex B (Flow identifiers: Format definition and examples) Entities Condition UE B EPC IMS UE A ✓ ✓ UE B attached to EPC and pre-provisioned a default bearer for enabling communication between UE B and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE B ✓ ✓ ✓ ✓ An IMS call/session established between UE B and UE A, with 2 media components - audio and video UE B EPC IMS UE A Step Direction Message 1 Session Audio Media from UE B to UE A delivered to UE A 2 Session Audio Media from UE A to UE B delivered to UE B 3 SIP re-INVITE Request Body SDP update for removing audio 4 SIP 2xx Response Body SDP update answer 5 Diameter AA-Request Session-Id AVP respective Rx session attached to this SIP session Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Session-Id AVP respective Rx session attached to this SIP session Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 2xx Response Body SDP update answer 8 || Session Audio Media from UE B to UE A || not delivered to UE A 9 || Session Audio Media from UE A to UE B || not delivered to UE B ETSI ETSI TS 103 029 V3.1.1 (2011-11) 41
|
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 Release procedures, terminating any bearer that have been previously created as part of the call. The test will verify that: 1) The P-CSCF will act on call release and trigger release of call bearers. 2) The EPC will remove the call's media bearers accordingly. 3) Audio media will not be transported after the session termination. Tests will continue transmitting media after the session release and verify that the default EPC gating policy of "Deny" will stop all media.
|
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 longer possible, after the session release. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.8.2 (Call release initiated by any other entity) TS 129 214 [5], clause 4.4.4 (AF Session Termination) Entities Condition UE A EPC IMS UE B ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE A ✓ ✓ ✓ ✓ An IMS call/session established between UE A and UE B UE A EPC IMS UE B Step Direction Message 1 Session Media from UE A to UE B delivered to UE B 2 Session Media from UE B to UE A delivered to UE A 3 SIP BYE Request 5 Diameter Session-Termination-Request Session-Id AVP respective Rx session attached to this SIP session 6 Diameter Session-Termination-Answer Session-Id AVP respective Rx session attached to this SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 7 || Session Media from UE A to UE B || not delivered to UE B 8 || Session Audio Media from UE B to UE A || not delivered to UE A
|
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 longer possible, after the session release. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.8.2 (Call release initiated by any other entity) TS 129 214 [5], clause 4.4.4 (AF Session Termination) Entities Condition UE B EPC IMS UE A ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE B and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE B ✓ ✓ ✓ ✓ An IMS call/session established between UE B and UE A UE B EPC IMS UE A Step Direction Message 1 Session Audio Media from UE B to UE A delivered to UE A 2 Session Audio Media from UE A to UE B delivered to UE B 3 SIP BYE Request 4 Diameter Session-Termination-Request Session-Id AVP respective Rx session attached to this SIP session 5 Diameter Session-Termination-Answer Session-Id AVP respective Rx session attached to this SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 6 || Session Audio Media from UE B to UE A || not delivered to UE A 7 || Session Audio Media from UE A to UE B || not delivered to UE B
|
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 established optionally, as result of a 180 Ringing response, based on the individual test configuration. Following Call Abort or respectively Call Reject procedures, if bearers for early-media were established, they will be terminated. The test will verify that: 1) Only early-media will be transported during the session establishment phase. 2) The P-CSCF will act on call abort/reject and trigger release of the optionally established early-media bearer. 3) Audio media will not be transported after the session abort/reject. Tests will continue transmitting media after the session release and verify that the default EPC gating policy of "Deny" will stop all media. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 44
|
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 (CANCEL) 16ba. ACK 17ba. CANCEL 6. AAR 7. RAR 9. RAA 8. Installation of Early‐media Bearer 10. AAA 17bb. STR 18. RAR 20. RAA 19. Removal of the Early‐media Bearer 21. STA UE B Not Possible Early‐Media Not Possible Not Possible Not Possible Not Possible Figure 18: SIP Session Abort - Originating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 45 Test Purpose Identifier: TP_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_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.7.2 (Initial INVITE / Originating Case) No better section found TS 129 214 [5], clause 4.4.4 (AF Session Termination) Entities Condition UE A EPC IMS UE B ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE A UE A EPC IMS UE B Step Direction Message 1 || Session Media from UE A to UE B || not delivered to UE B 2 || Session Media from UE B to UE A || not delivered to UE A 3 SIP INVITE Request Body SDP offer 4 SIP 180 Ringing Response Body SDP answer Early Media 5 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 180 Ringing Response Body SDP answer Early media 8 Session Early-Media from UE B to UE A delivered to UE A 9 SIP CANCEL Request 10 SIP 200 OK Response (CANCEL) 11 SIP 487 Request Terminated (INVITE) 12 SIP ACK Request 13 Diameter Session-Termination-Request Session-Id AVP respective Rx session attached to this SIP session 14 Diameter Session-Termination-Answer Session-Id AVP respective Rx session attached to this SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 15 SIP 487 Request Terminated (INVITE) 16 SIP ACK Request 17 || Session Early-Media from UE B to UE A || not delivered to UE A ETSI ETSI TS 103 029 V3.1.1 (2011-11) 46
|
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 6. RAR 8. RAA 7. Installation of Early‐media Bearer 9. AAA 4.180 Ringing 10. 180 Ringing 11. 180 Ringing 16bb. STR 17bb. RAR 19. RAA 18. Removal of the Early‐media Bearer 20. STA UE A Not Possible Not Possible Early‐Media Not Possible Not Possible Not Possible Figure 19: SIP Session Abort - Terminating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 47 Test Purpose Identifier: TP_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_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.7.3 (Initial INVITE / Terminating Case) No better section found TS 129 214 [5], clause 4.4.4 (AF Session Termination) Entities Condition UE B EPC IMS UE A ✓ ✓ UE B attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE B registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE B UE B EPC IMS UE A Step Direction Message 1 || Session Media from UE B to UE A || not delivered to UE A 2 || Session Media from UE A to UE B || not delivered to UE B 3 SIP INVITE Request Body SDP offer 4 SIP 180 Ringing Response Body SDP answer Early Media 5 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 180 Ringing Response Body SDP answer Early media 8 Session Early-Media from UE B to UE A delivered to UE A 9 SIP CANCEL Request 10 SIP 200 OK Response (CANCEL) 11 SIP 487 Request Terminated (INVITE) 12 SIP ACK Request 13 Diameter Session-Termination-Request Session-Id AVP respective Rx session attached to this SIP session 14 Diameter Session-Termination-Answer Session-Id AVP respective Rx session attached to this SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 15 SIP 487 Request Terminated (INVITE) 16 SIP ACK Request 17 || Session Early-Media from UE B to UE A || not delivered to UE A ETSI ETSI TS 103 029 V3.1.1 (2011-11) 48
|
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 the Early‐media Bearer 17. STA UE B Not Possible Not Possible Early‐Media Not Possible Not Possible Not Possible Figure 20: SIP Session Reject - Originating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 49 Test Purpose Identifier: TP_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.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.7.2 (Initial INVITE / Originating Case) No better section found TS 129 214 [5], clause 4.4.4 (AF Session Termination) Entities Condition UE A EPC IMS UE B ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE A UE A EPC IMS UE B Step Direction Message 1 || Session Media from UE A to UE B || not delivered to UE B 2 || Session Media from UE B to UE A || not delivered to UE A 3 SIP INVITE Request Body SDP offer 4 SIP 180 Ringing Response Body SDP answer Early Media 5 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 180 Ringing Response Body SDP answer Early media 8 Session Early-Media from UE B to UE A delivered to UE A 9 SIP 486 Busy Here Response 10 SIP ACK Request 11 Diameter Session-Termination-Request Session-Id AVP respective Rx session attached to this SIP session 12 Diameter Session-Termination-Answer Session-Id AVP respective Rx session attached to this SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 13 SIP 486 Busy Here Request 14 SIP ACK Request 15 || Session Early-Media from UE B to UE A || not delivered to UE A ETSI ETSI TS 103 029 V3.1.1 (2011-11) 50
|
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. RAA 15. Removal of the Early‐media Bearer 17. STA UE A Not Possible Not Possible Early‐Media Not Possible Not Possible Not Possible Figure 21: SIP Session Reject - Terminating Leg ETSI ETSI TS 103 029 V3.1.1 (2011-11) 51 Test Purpose Identifier: TP_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 abort. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 124 229 [2], clause 5.2.7.3 (Initial INVITE / Terminating Case) No better section found TS 129 214 [5], clause 4.4.4 (AF Session Termination) Entities Condition UE B EPC IMS UE A ✓ ✓ UE B attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE B registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE B UE B EPC IMS UE A Step Direction Message 1 || Session Media from UE B to UE A || not delivered to UE A 2 || Session Media from UE A to UE B || not delivered to UE B 3 SIP INVITE Request Body SDP offer 4 SIP 180 Ringing Response Body SDP answer Early Media 5 Diameter AA-Request Framed-IP-Address AVP or Framed-IPv6-Prefix AVP UE IP one or more Media-Component-Description AVP Media-Component-Number AVP suitable value as derived from SDP one or more Media-Sub-Component AVP as derived from SDP 6 Diameter AA-Answer Result-Code AVP DIAMETER_SUCCESS(2001) Acceptable-Service-Info AVP Media-Component-Description AVP similar value to what was requested in Diameter AA-Request IP-CAN-Type AVP RAT-Type AVP 7 SIP 180 Ringing Response Body SDP answer Early media 8 Session Early-Media from UE B to UE A delivered to UE A 9 SIP 486 Busy Here Response 10 SIP ACK Request 11 Diameter Session-Termination-Request Session-Id AVP respective Rx session attached to this SIP session 12 Diameter Session-Termination-Answer Session-Id AVP respective Rx session attached to this SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 13 SIP 486 Busy Here Response 14 SIP ACK Request 15 || Session Early-Media from UE B to UE A || not delivered to UE B ETSI ETSI TS 103 029 V3.1.1 (2011-11) 52
|
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 follows the EPC initiated modification of bearers for a session. All bearers for a given established session will be removed, which will trigger an administrative termination of the SIP session. The test assumes that the UE has been previously attached to EPC and registered to IMS. Also UE A will be involved in an active SIP session with UE B. The test procedure will follow a bearer release operation. The P-CSCF will be informed that, as no bearers are left or are no longer available for the session, the Rx session will be aborted. The P-CSCF will trigger an administrative termination of the related SIP session. The test will verify that: 1) The P-CSCF will act on Rx session abort and administratively terminate the SIP session. 2) Audio media will not be transported after the session abort/termination. Tests will continue transmitting media after the session release and verify that the default EPC gating policy of "Deny" will stop all media. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 53 Test Purpose Identifier: TP_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. Config.: CF_IMSEPC IUT Role: IMS, EPC Ref: TS 129 214 [5], clause 4.4.6.1 (IP-CAN Session Termination) TS 124 229 [2], clause 5.2.8.1.2 (P-CSCF-initiated call release / Release of an existing session) Entities Condition UE A EPC IMS UE B ✓ ✓ UE A attached to EPC and pre-provisioned a default bearer for enabling communication between UE A and IMS ✓ ✓ UE A registered in IMS ✓ ✓ An IMS signalling bearer established between IMS and EPC for UE A ✓ ✓ ✓ ✓ An IMS call/session established between UE A and UE B UE A EPC IMS UE B Step Direction Message 1 Session Media from UE A to UE B delivered to UE B 2 Session Media from UE B to UE A delivered to UE A 3 EPC triggers removal of all bearers related to respective SIP session 9 Diameter Abort-Session-Request Session-Id AVP session for active SIP Session Abort-Cause AVP BEARER_RELEASED (0) 10 Diameter Abort-Session-Answer Session-Id AVP session for active SIP Session Result-Code AVP DIAMETER_SUCCESS(2001) 11 Diameter Session-Termination-Request Session-Id AVP session for active SIP session 12 Diameter Session-Termination-Answer Session-Id AVP session for active SIP session Result-Code AVP DIAMETER_SUCCESS(2001) 13 SIP BYE Request Request-URI stored Contact header field provided UE A To header To header field value as received in the 200 (OK) response for initial INVITE request From header From header field value as received in initial INVITE request Call-ID header Call-Id header field value as received in initial INVITE request CSeq header current CSeq value stored for direction from calling to called user, incremented by one Route header routeing information towards called user as stored for dialog Reason header 503 (Service Unavailable) response code SIP BYE Response ETSI ETSI TS 103 029 V3.1.1 (2011-11) 54 14 SIP BYE Request Request-URI stored Contact header field provided by UE B To header To header field value as received in the 200 (OK) response for initial INVITE request From header From header field value as received in initial INVITE request Call-ID header Call-Id header field value as received in initial INVITE request CSeq header current CSeq value stored for direction from calling to called user, incremented by one Route header routeing information towards called user as stored for dialog Reason header 503 (Service Unavailable) response code 15 SIP BYE Response 16 || Session Media from UE A to UE B || not delivered to UE B 17 || Session Media from UE B to UE A || not delivered to UE A
|
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 most common scenarios are approached. Each Test Description can be then reconfigured to test various aspects (e.g. IPv4 and IPv6 IMS registrations). Yet these configurations are to be regarded only as specific to the individual test executions as they should not affect the test descriptions.
|
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.: Use Case Ref.: TP_IMSEPC_Network_Attachment Pre-test conditions: • Network attachment credential provisioned in UE_A and EPC • EPC and UE_A provisioned with selectable APN configurations for IPv4, IPv6 or IPv4&IPv6 PDN types • P-CSCF address provisioned in the EPC for the purpose of delivery to UE on attachment • Default Bearer PCRF policies set to allow UE A - P-CSCF communication • Default EPC Gating Policy set to “Deny” • UE_A not attached to network and EPC ETSI ETSI TS 103 029 V3.1.1 (2011-11) 55 Interoperability Test Description Test Sequence: Step 1 UE A starts initial network attachment to EPC 2 Verify that UE_A attached successfully and received the following information: • suitable IPv4 and/or IPv6 address(es) • DNS configuration information • P-CSCF IP address or FQDN 3 Verify that EPC establishes Default Bearer for allowing UE_A - P-CSCF communication, by starting at UE_A an IMS registration 4 Verify that arbitrary IP packets from UE_A to arbitrary node UE_B, other than the P-CSCF, are filtered-out by EPC and not visible on PO_SGi 5 Verify that arbitrary IP packets from UE B sent over PO_SGi to UE_A, are filtered-out by EPC and not visible on PO_UE_A Conformance Criteria: Check 1 TP_EPC_6001_01 ensure that { when { UE_A completes initial network_attachment to EPC } then { receives IP_configuration_data ( containing IPv4_address of UE_A or containing IPv6_address of UE_A or containing (IPv4_address and IPv6_address) of UE_A ) containing DNS_information containing P-CSCF_information ( indicating the P-CSCF-IP_address or indicating the P-CSCF-FQDN_address ) } } 2 TP_EPC_6002_01 ensure that { when { UE_A sends REGISTER to IMS_P-CSCF } then { IMS_P-CSCF receives REGISTER } when { IMS_P-CSCF sends response on REGISTER to UE_A } then { UE_A receives response on REGISTER } } 3 TP_EPC_6003_01 ensure that { when { UE_A sends IP_packets to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends IP_packets to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 7.1.2 Network Detachment with Previously Established IMS Registration and sessions Interoperability Test Description Identifier: TD_IMSEPC_Network_Detachment Summary: On complete network detachment, without previous termination of IMS sessions and registration, the EPC informs the IMS about the event. EPC removes all relevant bearers. IMS terminates all the ongoing IMS sessions and the IMS registration. Configuration: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment Use Case Ref.: TP_IMSEPC_Network_Detachment Pre-test conditions: • UE_A previously attached to EPC with a single attachment • UE_A previously registered to IMS • UE_A previously established SIP session with UE B ETSI ETSI TS 103 029 V3.1.1 (2011-11) 56 Interoperability Test Description Test Sequence: Step 1 UE_A starts complete network detachment, without previously triggering IMS de- registration; or EPC starts administrative complete network detachment of UE_A. 2 Verify that EPC removes affected SIP session and IMS signalling bearers 3 Verify that EPC aborts all affected Rx sessions with IMS 4 Verify that IMS performs P-CSCF-initiated call release on affected SIP session 5 Verify that IMS performs P-CSCF-initiated administrative de-registration on affected IMS signalling session Conformance Criteria: Check 1 TP_EPC_6004_01 ensure that { when { UE_A starts_complete_network_detachment from EPC } then { EPC_PCRF removes_relevant_bearers } then { EPC_PCRF triggers_termination of SIP_session } then { EPC_PCRF triggers_termination of IMS_signalling } } 2 TP_EPC_6005_01 ensure that { when { EPC_PCRF triggers_termination of SIP_session } then { EPC_PCRF sends Abort-Session-Request to IMS_P-CSCF containing Session-Id_AVP indicating session of SIP_session containing Abort-Cause_AVP indicating BEARER_RELEASED (0) } } 3 TP_EPC_6006_01 ensure that { when { IMS_P-CSCF receives Abort-Session-Request for SIP_session } then { IMS_P-CSCF sends Abort-Session-Answer to EPC_PCRF ( containing Session-Id_AVP indicating value_received in Abort-Session-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) ) and IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF ( containing Session-Id_AVP indicating value_received in Abort-Session-Request ) and IMS_P-CSCF triggers_call_release } } 4 TP_EPC_6005_02 ensure that { when { EPC_PCRF triggers_termination of IMS_signalling } then { EPC_PCRF sends Abort-Session-Request to IMS_P-CSCF containing Session-Id_AVP indicating session of SIP_session containing Abort-Cause_AVP indicating BEARER_RELEASED (0) } } 5 TP_EPC_6006_02 ensure that { when { IMS_P-CSCF receives Abort-Session-Request for IMS_signalling } then { IMS_P-CSCF sends Abort-Session-Answer to EPC_PCRF ( containing Session-Id_AVP indicating value_received in Abort-Session-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) ) and IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF ( containing Session-Id_AVP indicating value_received in Abort-Session-Request ) and IMS_P-CSCF triggers_call_release } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 57 Interoperability Test Description 6 TP_EPC_6009_01 ensure that { when { EPC_PCRF receives Session-Termination-Request from IMS_P- CSCF containing Session-Id_AVP indicating session for SIP_session } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating SIP_session value_received in Session- Termination-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001)} 7 TP_EPC_6010_01 ensure that { when { IMS_P-CSCF triggers_call_release} then { IMS_P-CSCF sends BYE to UE_A containing Request_URI indicating contact_address from Contact_header of UE_A and containing To_header indicating the initial 200_OK_From_value and containing From_header indicating the initial INVITE_To_value and containing Call-ID_header indicating the initial INVITE_Call_Id_value and containing CSeq_header including an incremented Sequence_Number and containing Route_header indicating specific_routing_information for UE_A and containing Reason_header indicating 503_service_unavailable } } 8 TP_EPC_6011_01 ensure that { when { IMS_P-CSCF triggers_administrative_de-registration } then { IMS_P-CSCF sends REGISTER to IMS_S-CSCF containing Request_URI indicating stored_domain_URI for affected_IMPU of UE_A containing To_header indicating affected_IMPU --IP Multimedia Public Identity containing From_header indicating affected_IMPU containing Contact_header indicating Contact_header_value containing Authorization_header indicating an integrity-protected_parameter indicating yes containing Expires_header indicating 0 containing Reason_header indicating 503_service_unavailable } } 9 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } }
|
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 the respective bearer's QoS and priority characteristics. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment Use Case ref.: TP_IMSEPC_Registration_Initial Pre-test conditions: • UE_A previously attached to EPC, but not registered to IMS • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • HSS of IMS provisioned with UE_A' subscription • UE_A discovered the P-CSCF address Test Sequence: Step 1 UE_A triggers IMS registration 2 Verify that, in Diameter AA-Request/Answer, IMS included a Media Description for signalling according to UE_A.IP_Address, UE_A.SIP_Port, PCSCF.IP_Address, PCSCF.SIP_Port. 3 Verify that IMS requested media description was found acceptable by EPC 4 Verify that UE_A can exchange subsequent signalling with IMS 5 Verify that UE_A subsequent signalling is transported with appropriate PCC characteristics Conformance Criteria: Check 1 TP_EPC_6012_01 ensure that { when { IMS_P-CSCF receives 2xx_Response on REGISTER from IMS_S- CSCF } then { UE_A receives 2xx_Response } } 2 TP_EPC_6013_01 ensure that { when { IMS_P-CSCF receives 2xx_Response on REGISTER from IMS_S- CSCF } then { IMS_P-CSCF sends AA-Request to EPC_PCRF containing framed IPv4_Address AVP (indicating IPv4_Address of UE_A or containing framed IPv6_Address AVP indicating IPv6_Address of UE_A) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating value 0 containing Flow-Description_AVP ( indicating permit_in_ip from (UE_A-IP_address and UE_A_port_number) to (P-CSCF-IP_address and P-CSCF_port_number) or indicating permit_in_udp from (UE_A-IP_address and UE_A_port_number) to (P-CSCF-IP_address and P-CSCF_port_number) or indicating permit_in_tcp from (UE_A-IP_address and UE_A_port_number) to (P-CSCF-IP_address and P-CSCF_port_number) ) and containing Flow-Description_AVP ( indicating permit_out_ip from (P-CSCF-IP_address P- CSCF_port_number) to UE_A-IP_address or indicating permit_out_udp from (P-CSCF-IP_address P- CSCF_port_number) to UE_A-IP_address or indicating permit_out_tcp from (P-CSCF-IP_address P- CSCF_port_number) to UE_A-IP_address ) and containing Flow-Usage_AVP indicating AF_SIGNALING(0) containing Flow-Status_AVP indicating ENABLED(2) containing AF-Signalling-Protocol_AVP indicating SIP(1) ) } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 59 Interoperability Test Description 3 TP_EPC_6014_01 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP( containing Media-Component-Number_AVP indicating 0 and containing Flow-Description_AVP ( indicating permit_in_ip from (UE_A-IP_address and UE_A_port_number) to (P-CSCF-IP_address and P- CSCF_port_number) or indicating permit_in_udp from (UE_A- IP_address and UE_A_port_number) to (P-CSCF-IP_address and P- CSCF_port_number) or indicating permit_in_tcp from (UE_A- IP_address and UE_A_port_number) to (P-CSCF-IP_address and P- CSCF_port_number) ) and containing Flow-Description_AVP ( indicating permit_out_ip from (P-CSCF- IP_address P-CSCF_port_number) to UE_A-IP_address or indicating permit_out_udp from (P-CSCF- IP_address P-CSCF_port_number) to UE_A-IP_address or indicating permit_out_tcp from (P-CSCF- IP_address P-CSCF_port_number) to UE_A-IP_address ) and containing Flow-Usage_AVP indicating AF_SIGNALING(0) and containing Flow-Status_AVP indicating ENABLED(2) and containing AF-Signalling-Protocol_AVP indicating SIP(1) ) ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_A and containing RAT-Type_AVP indicating Current_RAT_Type of UE_A } } 4 TP_EPC_6015_01 ensure that { when { UE_A sends SUBSCRIBE to IMS } then { EPC uses_correct_Uplink bearer } then { IMS receives SUBSCRIBE delivered over IMS_signalling bearer } when { IMS sends SUBSCRIBE to UE_A } then { EPC uses_correct_Downlink bearer } then { UE_A receives SUBSCRIBE delivered over IMS_signalling bearer } }
|
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_Registration_Initial Pre-test conditions: • UE_A previously attached to EPC, but not registered to IMS • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • HSS of IMS not provisioned with UE_A's subscription • UE_A discovered the P-CSCF address ETSI ETSI TS 103 029 V3.1.1 (2011-11) 60 Interoperability Test Description Test Sequence: Step 1 UE_A triggers IMS registration with invalid identity 2 Verify that the IMS registration has been rejected 3 Verify that an IMS signalling bearer has not been created Conformance Criteria: Check 1 TP_EPC_6016_01 ensure that { when { IMS_P-CSCF receives 4xx_Response on REGISTER from IMS_S- CSCF } then { UE_A receives 4xx_Response from IMS_P-CSCF} } 2 TP_EPC_6016_02 ensure that { when { IMS_P-CSCF receives 4xx_Response on REGISTER from IMS_S- CSCF } then { IMS_P-CSCF not send AA-Request to EPC_PCRF } }
|
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.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case Ref.: TP_IMSEPC_DeRegistration_UE Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer allowing UE_A - P-CSCF IP communication with AF Signalling QoS characteristics Test Sequence: Step 1 UE_A triggers IMS de-registration, removing all registered contacts at respective P-CSCF 2 Verify that P-CSCF signals termination of IMS signalling bearer 3 Verify that signalling between UE_A and P-CSCF is still possible, by using a registration status pull (no contacts in SIP REGISTER request). Verify that this signalling is transported in the still active Default Bearer. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 61 Interoperability Test Description Conformance Criteria: Check 1 TP_EPC_6017_01 ensure that { when { UE_A sends REGISTER for de-registration to IMS_P-CSCF } then { UE_A receives 2xx_Response from IMS_P-CSCF } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for IMS_signalling session } } 2 TP_EPC_6009_02 ensure that { when { EPC_PCRF receives Session-Termination-Request from IMS_P- CSCF containing Session-Id_AVP indicating session for IMS_signalling session } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating IMS_signalling value_received in Session- Termination-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } then { EPC_PCRF removes_relevant_bearers } -- IMS_signalling } 3 TP_EPC_6018_01 ensure that { when { UE_A sends REGISTER to IMS_P-CSCF } then { IMS_P-CSCF receives REGISTER delivered over default bearer containing no Contact_header } then { IMS_P-CSCF sends Response to UE_A } } 4 TP_EPC_6019_01 ensure that { when { IMS_P-CSCF sends Response on REGISTER to UE_A } then { UE_A receives Response on REGISTER from IMS_P-CSCF delivered over default bearer } }
|
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. Media cannot be exchange any longer on previous SIP Session bearer. The S-CSCF answers to the de-registration. The P-CSCF signals to PCRF the termination of IMS signalling session. EPC removes IMS signalling bearer. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_DeRegistration_UE Use Case Ref.: TP_IMSEPC_DeRegistration_UE_Active_Session ETSI ETSI TS 103 029 V3.1.1 (2011-11) 62 Interoperability Test Description Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer • UE_A initiated/received a SIP session request such that a SIP session is active with UE_B • EPC established a SIP session bearer for media • Default EPC gating policy set to “Deny” Test Sequence: Step 1 Verify that media between UE_A and UE_B is successfully forwarded 2 UE_A triggers IMS de-registration, removing all registered contacts at respective P-CSCF 3 Verify that S-CSCF triggers S-CSCF-initiated call release 4 Verify that P-CSCF signals termination of active SIP session media bearers 5 Verify that EPC removes SIP session media bearers and as such media packets are no longer forwarded between UE_A and UE_B, in either direction 6 Verify that P-CSCF signals termination of IMS signalling bearer 7 Verify that media between UE_A and UE_B is not delivered in any direction after termination of SIP session bearers Conformance Criteria: Check 1 TP_EPC_6020_01 ensure that { when { UE_A sends media to UE_B } then { UE_B receives the media delivered over SIP_Session media bearer } when { UE_B sends media to UE_A } then { UE_A receives the media delivered over SIP_Session media bearer } } 2 TP_EPC_6021_01 ensure that { when { UE_A sends REGISTER for de-registration to IMS_P-CSCF } then { IMS_S-CSCF sends BYE to IMS_P-CSCF containing Request_URI including contact_address from Contact_header of UE_B and containing To_header including From_header or To_header from initial INVITE and containing From_header including From_header or To_header from initial INVITE and containing Call-ID_header indicating the initial INVITE_Call_Id_value and containing CSeq_header including an incremented Sequence_Number and containing Route_header including specific_routing_information containing Reason_header } } 3 TP_EPC_6022_01 ensure that { when { IMS_P-CSCF receives BYE from IMS_S-CSCF } then { IMS_P-CSCF sends BYE to UE_A } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session of SIP_session } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 63 Interoperability Test Description 4 TP_EPC_6009_01 ensure that { when { EPC_PCRF receives Session-Termination-Request from IMS_P-CSCF containing Session-Id_AVP indicating session for SIP_session } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating SIP_session value_received in Ses sion-Termination-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } } 5 TP_EPC_6023_01 ensure that { when { UE_A sends media to UE_B } then { EPC does not send media to UE_B } when { UE_B sends media to UE_A } then { EPC does not send media to UE_A } } 6 TP_EPC_6012_02 ensure that { when { IMS_P-CSCF receives 2xx_Response on REGISTER from IMS_S- CSCF } then { IMS_P-CSCF sends 2xx_Response to UE_A } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for IMS_signalling session } } 7 TP_EPC_6009_02 ensure that { when { EPC_PCRF receives Session-Termination-Request from IMS_P- CSCF containing Session-Id_AVP indicating session for IMS_signalling session } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating IMS_signalling value_received in Session- Termination-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } then { EPC_PCRF removes_relevant_bearers } } 8 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } }
|
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 still possible, but traffic will be categorized in the Default Bearer. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case Ref.: TP_IMSEPC_DeRegistration_Administrative ETSI ETSI TS 103 029 V3.1.1 (2011-11) 64 Interoperability Test Description Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer Test Sequence: Step 1 S-CSCF/HSS triggers administrative de-registration, removing all registered contacts of UE_A 2 Verify that S-CSCF signals de-registration to the P-CSCF 3 Verify that P-CSCF signals termination of the IMS signalling bearer 4 Verify that signalling between UE_A and P-CSCF is still possible, by using a registration status pull (no contacts in SIP REGISTER request). Verify that this signalling is transported in the still active Default Bearer. Conformance Criteria: Check 1 TP_EPC_6024_01 ensure that { when { IMS_S-CSCF triggers_administrative_de-registration for UE_A } then { IMS_S-CSCF sends NOTIFY to IMS_P-CSCF containing Request_URI indicating IMS_P-CSCF contact_address for SUBSCRIBE dialog and containing Event_header indicating the reg_event_package and containing Message_Body indicating de-registration of all UE_A registered_public_identities } } 2 TP_EPC_6025_01 ensure that { when { IMS_P-CSCF receives NOTIFY for UE_A de-registration from IMS_S-CSCF } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for IMS_signalling session } } 3 TP_EPC_6009_02 ensure that { when { EPC_PCRF receives Session-Termination-Request from IMS_P- CSCF containing Session-Id_AVP indicating session for IMS_signalling session } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating IMS_signalling value_received in Session- Termination-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } then { EPC_PCRF removes_relevant_bearers } } 4 TP_EPC_6018_01 ensure that { when { UE_A sends REGISTER to IMS_P-CSCF } then { IMS_P-CSCF receives REGISTER delivered over default bearer containing no Contact_header } then { IMS_P-CSCF sends Response to UE_A } } 5 TP_EPC_6019_01 ensure that { when { IMS_P-CSCF sends Response on REGISTER to UE_A } then { UE_A receives Response on REGISTER from IMS_P-CSCF delivered over default bearer } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 65
|
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 Bearer. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case Ref.: TP_IMSEPC_DeRegistration_Expiration Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer Test Sequence: Step 1 UE_A registration expires at P-CSCF, for all contacts of UE_A 2 Verify that P-CSCF signals termination of IMS signalling bearer 3 Verify that signalling between UE_A and P-CSCF is still possible, by using a registration status pull (no contacts in REGISTER request). Verify that this signalling is transported in the still active Default Bearer. Conformance Criteria: Check 1 TP_EPC_6026_01 ensure that { when { IMS_P-CSCF triggers_registration_expiration for UE_A } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for IMS_signalling session } } 2 TP_EPC_6009_02 ensure that { when { EPC_PCRF receives Session-Termination-Request from IMS_P- CSCF containing Session-Id_AVP indicating session for IMS_signalling session } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating IMS_signalling value_received in Session- Termination-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } then { EPC_PCRF removes_relevant_bearers } } 3 TP_EPC_6018_01 ensure that { when { UE_A sends REGISTER to IMS_P-CSCF } then { IMS_P-CSCF receives REGISTER delivered over default bearer containing no Contact_header } then { IMS_P-CSCF sends Response to UE_A } } 4 TP_EPC_6019_01 ensure that { when { IMS_P-CSCF sends Response on REGISTER to UE_A } then { UE_A receives Response on REGISTER from IMS_P-CSCF delivered over default bearer } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 66
|
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 EPC's operator policies the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible only after the successful establishment of the session. Media negotiation happens during INVITE/200 OK (UE A sends SDP-offer, UE B responds with SDP-answer) Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case ref.: TP_IMSEPC_Session_Establishment_Originating Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer • UE_B ready to accept the session establishment Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction before call establishment 2 UE_A calls UE_B and establishes a communication session 3 Verify that, in Diameter AA-Request/Answer, the IMS produced a Media Description for the session according to SDP-offer in SIP INVITE Request and SDP-answer in SIP 2xx INVITE Answer 4 Verify that IMS requested media description was found acceptable by EPC 5 Verify that media between UE_A and UE_B is successfully routed 6 Verify that media between UE_A and UE_B is transported with appropriate PCC characteristics Conformance Criteria: Check 1 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 67 Interoperability Test Description 2 TP_EPC_6027_01 ensure that { when { IMS_P-CSCF receives 2xx_response on INVITE from IMS_P-CSCF } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_address of UE_A or containing Framed-IPv6-Address_AVP indicating IPv6_address of UE_A ) and containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP ) } } 3 TP_EPC_6028_01 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_A and containing RAT-Type_AVP indicating Current_RAT_Type of UE_A } } 4 TP_EPC_6029_01 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 2xx_Response on INVITE to UE_A } } 5 TP_EPC_6030_01 ensure that { when { UE_A sends media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } }
|
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 EPC's operator policies the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible only after the successful establishment of the session. Media negotiation happens during 200 OK / ACK (UE B sends SDP-offer, UE A responds with SDP-answer) Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case ref.: TP_IMSEPC_Session_Establishment_Originating Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer • UE_B ready to accept the session establishment ETSI ETSI TS 103 029 V3.1.1 (2011-11) 68 Interoperability Test Description Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction before call establishment 2 UE_A calls UE_B and establishes a communication session 3 Verify that, in Diameter AA-Request/Answer, IMS produced a Media Description for the session according to SDP-offer in SIP 200 OK INVITE Response and SDP-answer in SIP ACK Request 4 Verify that IMS requested media description was found acceptable by EPC 5 Verify that media between UE_A and UE_B is successfully routed 6 Verify that media between UE_A and UE_B is transported with appropriate PCC characteristics Conformance Criteria: Check 1 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6027_03 ensure that { when { IMS_P-CSCF receives ACK from UE_A } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_Address of UE_A or containing Framed-IPv6-Address_AVP indicating IPv6_Address of UE_A) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } 3 TP_EPC_6028_01 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_A and containing RAT-Type_AVP indicating Current_RAT_Type of UE_A } } 4 TP_EPC_6029_04 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends ACK to IMS_S-CSCF } } 5 TP_EPC_6030_01 ensure that { when { UE_A sends media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 69
|
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. Media transport is not possible either before or after this empty session setup. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case ref.: TP_IMSEPC_Session_Establishment_Originating Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer • UE_B ready to accept the session establishment Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction before call establishment 2 UE_A calls UE_B and establishes a communication session 3 Verify that, as there was no SDP negotiation, there is no AA-Request/Answer exchange between P-CSCF and PCRF 4 Verify that media between UE_A and UE_B is still not delivered in any direction Conformance Criteria: Check 1 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6033_01 ensure that { when { IMS_P-CSCF receives INVITE with no SDP from UE_A } then { IMS_P-CSCF does not send AA-Request to EPC_PCRF } when { IMS_P-CSCF receives 200_response on INVITE with no SDP from IMS_S-CSCF } then { IMS_P-CSCF does not send AA-Request to EPC_PCRF } when { IMS_P-CSCF receives ACK with no SDP from UE_A } then { IMS_P-CSCF does not send AA-Request to EPC_PCRF } } 3 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 70
|
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 EPC's operator policies the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible only after the successful establishment of the session. Media negotiation happens during INVITE/200 OK (UE A sends SDP-offer, UE B responds with SDP-answer) Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case ref.: TP_IMSEPC_Session_Establishment_Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer • UE_A ready to initiate the session establishment Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction before call establishment 2 UE_B receives a call request and establishes a communication session 3 Verify that, in Diameter AA-Request/Answer, the IMS produced a Media Description for the session according to SDP-offer in SIP INVITE Request and SDP-answer in SIP 2xx INVITE Answer 4 Verify that IMS requested media description was found acceptable by EPC 5 Verify that media between UE_A and UE_B is successfully routed 6 Verify that media between UE_A and UE_B is transported with appropriate PCC characteristics Conformance Criteria: Check 1 TP_EPC_6003_03 ensure that { when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6027_02 ensure that { when { IMS_P-CSCF receives 2xx_response on INVITE from UE_B } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_address of UE_B or containing Framed-IPv6-Address_AVP indicating IPv6_address of UE_B) and containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 71 Interoperability Test Description 3 TP_EPC_6028_02 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_B and containing RAT-Type_AVP indicating Current_RAT_Type of UE_B } } 4 TP_EPC_6029_02 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends SIP 2xx_Response on INVITE to IMS_S- CSCF } } 5 TP_EPC_6030_01 ensure that { when { UE_A sends media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } }
|
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 EPC's operator policies the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible only after the successful establishment of the session. Media negotiation happens during 200 OK / ACK (UE B sends SDP-offer, UE A responds with SDP-answer) Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case ref.: TP_IMSEPC_Session_Establishment_Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer • UE_A ready to initiate the session establishment Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction before call establishment 2 UE_B receives a call request and establishes a communication session 3 Verify that, in Diameter AA-Request/Answer, IMS produced a Media Description for the session according to SDP-offer in SIP 200 OK Response and SDP-answer in SIP ACK Response 4 Verify that IMS requested media description was found acceptable by EPC 5 Verify that media between UE_A and UE_B is successfully routed 6 Verify that media between UE_A and UE_B is transported with appropriate PCC characteristics ETSI ETSI TS 103 029 V3.1.1 (2011-11) 72 Interoperability Test Description Conformance Criteria: Check 1 TP_EPC_6003_03 ensure that { when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6027_04 ensure that { when { IMS_P-CSCF receives ACK from IMS_S-CSCF } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_Address of UE_B or containing Framed-IPv6-Address_AVP indicating IPv6_Address of UE_B) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } 3 TP_EPC_6028_02 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_B and containing RAT-Type_AVP indicating Current_RAT_Type of UE_B } } 4 TP_EPC_6029_03 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends ACK to UE_B } } 5 TP_EPC_6030_01 ensure that { when { UE_A sends media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 73
|
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. Media transport is not possible either before or after this empty session setup. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial Use Case ref.: TP_IMSEPC_Session_Establishment_Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer • UE_A ready to initiate the session establishment Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction before call establishment 2 UE_B receives a call request and establishes a communication session 3 Verify that, as there was no SDP negotiation, there is no AA-Request/Answer exchange between P-CSCF and PCRF 4 Verify that media between UE_A and UE_B is still not delivered in any direction Conformance Criteria: Check 1 TP_EPC_6003_03 ensure that { when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6033_02 ensure that { when { IMS_P-CSCF receives INVITE with no SDP from IMS_S-CSCF } then { IMS_P-CSCF does not send AA-Request to EPC_PCRF } when { IMS_P-CSCF receives 200_response on INVITE with no SDP from UE_B } then { IMS_P-CSCF does not send AA-Request to EPC_PCRF } when { IMS_P-CSCF receives ACK with no SDP from IMS_S-CSCF } then { IMS_P-CSCF does not send AA-Request to EPC_PCRF } } 3 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 74
|
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 modifies, based on the EPC's operator policies, the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible, after the successful modification of the session, only on the remaining active Service Data Flows. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Originating Use Case ref.: TP_IMSEPC_Session_Modification _Originating Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer • UE_A previously established a call with UE_B, encompassing both audio and video media Test Sequence: Step 1 Verify that media between UE_A and UE_B is delivered in both directions and for both media stream types after call establishment 2 UE_A initiates Call-Hold operation and removes audio media from the communication session 3 Verify that, in Diameter AA-Request/Answer, IMS produced a Media Description for session modification according to SDP-offer in SIP INVITE Request and SDP- answer in SIP 2xx INVITE Answer 4 Verify that IMS requested media description update was found acceptable by EPC 5 Verify that video media between UE_A and UE_B is still successfully exchanged 6 Verify that audio media between UE_A and UE_B can no longer be exchanged and is filtered out by EPC Conformance Criteria: Check 1 TP_EPC_6030_02 ensure that { when { UE_A sends audio_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends audio_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives the media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 75 Interoperability Test Description 2 TP_EPC_6027_01 ensure that { when { IMS_P-CSCF receives 2xx_response on INVITE from IMS_P-CSCF } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_address of UE_A or containing Framed-IPv6-Address_AVP indicating IPv6_address of UE_A ) and containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP ) } } 3 TP_EPC_6028_01 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_A and containing RAT-Type_AVP indicating Current_RAT_Type of UE_A } } 4 TP_EPC_6029_01 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 2xx_Response on INVITE to UE_A } } 5 TP_EPC_6031_01 ensure that { when { UE_A sends audio_media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends audio_media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on UE_A } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } }
|
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 modifies, based on the EPC's operator policies, the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible, after the successful modification of the session, on any new and also on the remaining active Service Data Flows. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Originating Use Case ref.: TP_IMSEPC_Session_Modification _Originating ETSI ETSI TS 103 029 V3.1.1 (2011-11) 76 Interoperability Test Description Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer • UE_A previously established a call with UE_B, encompassing video media only Test Sequence: Step 1 Verify that only video media between UE A and UE B is delivered in both directions after call establishment 2 UE_A initiates a Call-Resume operation and adds audio media to the communication session 3 Verify that, in Diameter AA-Request/Answer, IMS produced a Media Description for the session modification according to SDP-offer in SIP INVITE Request and SDP-answer in SIP 2xx Answer 4 Verify that IMS requested media description update was found acceptable by EPC 5 Verify that video media between UE A and UE B is still successfully exchanged 6 Verify that audio media between UE A and UE B is also successfully exchanged Conformance Criteria: Check 1 TP_EPC_6031_01 ensure that { when { UE_A sends audio_media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends audio_media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on UE_A } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } } 2 TP_EPC_6027_01 ensure that { when { IMS_P-CSCF receives 2xx_response on INVITE from IMS_P-CSCF } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_address of UE_A or containing Framed-IPv6-Address_AVP indicating IPv6_address of UE_A ) and containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP ) } } 3 TP_EPC_6028_01 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_A and containing RAT-Type_AVP indicating Current_RAT_Type of UE_A } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 77 Interoperability Test Description 4 TP_EPC_6029_01 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 2xx_Response on INVITE to UE_A } } 5 TP_EPC_6030_02 ensure that { when { UE_A sends audio_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends audio_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives the media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } }
|
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 modifies, based on the EPC's operator policies, the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible, after the successful modification of the session, only on the remaining active Service Data Flows. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Terminating Use Case ref.: TP_IMSEPC_Session_Modification _Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer • UE_A or another endpoint ready to accept the session establishment • UE_B previously established a call with UE_A or another endpoint, encompassing both audio and video media Test Sequence: Step 1 Verify that media between UE_A and UE_B is delivered in both directions and for both media stream types after call establishment 2 UE_A initiates a Call-Hold operation and removes audio media from the communication session 3 Verify that, in Diameter AA-Request/Answer, IMS produced a Media Description for the session modification according to SDP-offer in SIP INVITE Request and SDP-answer in SIP 2xx INVITE Answer 4 Verify that IMS requested media description update was found acceptable by EPC 5 Verify that video media between UE_A and UE_B is still successfully exchanged 6 Verify that audio media between UE_A and UE_B can no longer be exchanged and is filtered out by EPC ETSI ETSI TS 103 029 V3.1.1 (2011-11) 78 Interoperability Test Description Conformance Criteria: Check 1 TP_EPC_6030_02 ensure that { when { UE_A sends audio_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends audio_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives the media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } } 2 TP_EPC_6027_07 ensure that { when { IMS_P-CSCF receives 2xx_Response on INVITE from UE_B } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_Address of UE_A or containing Framed-IPv6-Address_AVP indicating IPv6_Address of UE_A) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } 3 TP_EPC_6028_02 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_B and containing RAT-Type_AVP indicating Current_RAT_Type of UE_B } } 4 TP_EPC_6029_02 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends SIP 2xx_Response on INVITE to IMS_S- CSCF } } 5 TP_EPC_6031_01 ensure that { when { UE_A sends audio_media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends audio_media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on UE_A } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 79
|
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 modifies, based on the EPC's operator policies, the bearers for media. When transporting media, the EPC will employ the respective bearer's characteristics. Media transport is possible, after the successful modification of the session, on any new and also on the remaining active Service Data Flows. Config.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Terminating Use Case ref.: TP_IMSEPC_Session_Modification _Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer • UE_B previously established a call with UE A, encompassing video media only Test Sequence: Step 1 Verify that only video media between UE_A and UE_B is delivered in both directions after call establishment 2 UE_A initiates a call-resume operation and adds audio media to the communication session 3 Verify that, in Diameter AA-Request/Answer, IMS produced a Media Description for the session modification according to SDP-offer in SIP INVITE Request and the SDP-answer in SIP 2xx INVITE Answer 4 Verify that the IMS requested media description update was found acceptable by EPC 5 Verify that the video media between UE_A and UE_B is still successfully exchanged 6 Verify that the audio media between UE_A and UE_B is also successfully exchanged Conformance Criteria: Check 1 TP_EPC_6031_01 ensure that { when { UE_A sends audio_media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends audio_media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on UE_A } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } } 2 TP_EPC_6027_02 ensure that { when { IMS_P-CSCF receives 2xx_response on INVITE from UE_B } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_address of UE_B or containing Framed-IPv6-Address_AVP indicating IPv6_address of UE_B) and containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 80 Interoperability Test Description 3 TP_EPC_6028_02 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_B and containing RAT-Type_AVP indicating Current_RAT_Type of UE_B } } 4 TP_EPC_6029_01 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 2xx_Response on INVITE to UE_A } } 5 TP_EPC_6030_02 ensure that { when { UE_A sends audio_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends audio_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } when { UE_A sends video_media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives the media } when { UE_B sends video_media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives the media } }
|
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 and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Originating Use Case ref.: TP_IMSEPC_Session_Release _Originating Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer • UE_A previously established a call with UE_B Test Sequence: Step 1 Verify that media between UE_A and UE_B is delivered in both directions and for both media stream types after the call establishment 2 UE_A initiates a Call-Release operation, ending the session 3 Verify that P-CSCF terminates the Rx session, triggering removal of all session related bearers 4 Verify that EPC removes all session related bearers ETSI ETSI TS 103 029 V3.1.1 (2011-11) 81 Interoperability Test Description 5 Verify that media between UE_A and UE_B can no longer be exchanged and is filtered out by EPC Conformance Criteria: Check 1 TP_EPC_6030_01 ensure that { when { UE_A sends media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } } 2 TP_EPC_6034_01 ensure that { when { IMS_P-CSCF receives SIP BYE Response from UE_A } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for SIP_session } } 3 TP_EPC_6009_03 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating session for IMS_signalling session containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } } 4 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } }
|
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 and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Terminating Use Case ref.: TP_IMSEPC_Session_Release _Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer • UE_B previously established a call with UE_A, encompassing both audio and video media ETSI ETSI TS 103 029 V3.1.1 (2011-11) 82 Interoperability Test Description Test Sequence: Step 1 Verify that media between UE_A and UE_B is delivered in both directions and for both media stream types after call establishment 2 UE_B receives a Call-Release operation, ending the session 3 Verify that P-CSCF terminates the Rx session, triggering the removal of all session related bearers 4 Verify that EPC removes all session related bearers 5 Verify that the media between UE_A and UE_B can no longer be exchanged and is filtered out by EPC Conformance Criteria: Check 1 TP_EPC_6030_01 ensure that { when { UE_A sends media to UE_B } then { EPC uses_correct_bearers for the service_data_flows } then { UE_B receives media } when { UE_B sends media to UE_A } then { EPC uses_correct_bearers for the service_data_flows } then { UE_A receives media } } 2 TP_EPC_6034_01 ensure that { when { IMS_P-CSCF receives SIP BYE Response from UE_A } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for SIP_session } } 3 TP_EPC_6009_03 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating session for IMS_signalling session containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } } 4 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi }
|
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_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Originating Use Case ref.: TP_IMSEPC_Session_Abort _Originating ETSI ETSI TS 103 029 V3.1.1 (2011-11) 83 Interoperability Test Description Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction 2 UE_A initiates a session establishment operation 3 UE_B answers with SIP 180 Ringing INVITE Response and starts sending early- media 4 Verify that early-media is delivered from UE_B to UE_A 5 UE_A cancels the session establishment 6 Verify that P-CSCF terminates the Rx session, triggering removal of all early- media related bearers 7 Verify that EPC removes all early-media related bearers 8 Verify that media between UE_B and UE_A can no longer be exchanged and is filtered out by EPC Conformance Criteria: Check 1 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6027_06 ensure that { when { IMS_P-CSCF receives SIP 180_response from IMS_S-CSCF } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_Address of UE_A or containing Framed-IPv6-Address_AVP indicating IPv6_Address of UE_A) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } 3 TP_EPC_6028_01 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_A and containing RAT-Type_AVP indicating Current_RAT_Type of UE_A } } 4 TP_EPC_6029_05 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 180_Response to UE_A } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 84 Interoperability Test Description 5 TP_EPC_6032_01 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends early_media to UE_A } then { EPC uses_correct_bearers for service_data_flows } then { UE_A receives media } } 6 TP_EPC_6034_02 ensure that { when { IMS_P-CSCF receives CANCEL from UE_A } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for SIP_session } } 7 TP_EPC_6009_03 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating session for IMS_signalling session containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } } 8 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } }
|
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_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Terminating Use Case ref.: TP_IMSEPC_Session_Abort _Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction 2 UE_A initiates a session establishment operation 3 UE_B answers with SIP 180 Ringing INVITE Response and starts sending early- media 4 Verify that early-media is delivered from UE_B to UE_A 5 UE_A cancels the session establishment 6 Verify that P-CSCF terminates the Rx session, triggering removal of all early- media related bearers 7 Verify that EPC removes all early-media related bearers 8 Verify that media between UE_B and UE_A can no longer be exchanged and is filtered out by EPC ETSI ETSI TS 103 029 V3.1.1 (2011-11) 85 Interoperability Test Description Conformance Criteria: Check 1 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6027_05 ensure that { when { IMS_P-CSCF receives 180_response from UE_B } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_Address of UE_B or containing Framed-IPv6-Address_AVP indicating IPv6_Address of UE_B) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } 3 TP_EPC_6028_02 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_B and containing RAT-Type_AVP indicating Current_RAT_Type of UE_B } } 4 TP_EPC_6029_06 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 180_Response to IMS_S-CSCF } } 5 TP_EPC_6032_01 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends early_media to UE_A } then { EPC uses_correct_bearers for service_data_flows } then { UE_A receives media } } 6 TP_EPC_6034_03 ensure that { when { IMS_P-CSCF receives CANCEL from IMS_S-CSCF } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for SIP_session } } 7 TP_EPC_6009_03 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating session for IMS_signalling session containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 86 Interoperability Test Description 8 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } }
|
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.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Originating Use Case ref.: TP_IMSEPC_Session_Reject _Originating Pre-test conditions: • UE_A previously attached to EPC • EPC established a Default Bearer allowing UE_A - P-CSCF IP communication • UE_A previously registered to IMS • EPC established an IMS signalling bearer Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction 2 UE_A initiates a session establishment operation 3 UE_B answers with SIP 180 Ringing INVITE Response and starts sending early- media 4 Verify that early-media is delivered from UE_B to UE_A 5 UE_B rejects session establishment 6 Verify that P-CSCF terminates the Rx session, triggering the removal of all early- media related bearers 7 Verify that EPC removes all early-media related bearers 8 Verify that media between UE_B and UE_A can no longer be exchanged and is filtered out by EPC Conformance Criteria: Check 1 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 87 Interoperability Test Description 2 TP_EPC_6027_06 ensure that { when { IMS_P-CSCF receives SIP 180_response from IMS_S-CSCF } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_Address of UE_A or containing Framed-IPv6-Address_AVP indicating IPv6_Address of UE_A) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } 3 TP_EPC_6028_01 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_A and containing RAT-Type_AVP indicating Current_RAT_Type of UE_A } } 4 TP_EPC_6029_05 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 180_Response to UE_A } } 5 TP_EPC_6032_01 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends early_media to UE_A } then { EPC uses_correct_bearers for service_data_flows } then { UE_A receives media } } 6 TP_EPC_6034_04 ensure that { when { IMS_P-CSCF receives 486_response on INVITE from UE_B } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for SIP_session } } 7 TP_EPC_6009_03 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating session for IMS_signalling session containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } } 8 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 88
|
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.: CF_IMSEPC SUT: IMS and EPC Ref.: TP_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Terminating Use Case ref.: TP_IMSEPC_Session_Reject _Terminating Pre-test conditions: • UE_B previously attached to EPC • EPC established a Default Bearer allowing UE_B - P-CSCF IP communication • UE_B previously registered to IMS • EPC established an IMS signalling bearer Test Sequence: Step 1 Verify that media between UE_A and UE_B is not delivered in any direction 2 UE_A initiates a session establishment operation 3 UE_B answers with SIP 180 Ringing INVITE Response and starts sending early- media 4 Verify that early-media is delivered from UE_B to UE_A 5 UE_B rejects the session establishment 6 Verify that P-CSCF terminates the Rx session, triggering removal of all early- media related bearers 7 Verify that EPC removes all early-media related bearers 8 Verify that the media between UE_B and UE_A can no longer be exchanged and is filtered out by EPC Conformance Criteria: Check 1 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } 2 TP_EPC_6027_05 ensure that { when { IMS_P-CSCF receives 180_response from UE_B } then { IMS_P-CSCF sends AA-Request to EPC_PCRF (containing Framed-IP-Address_AVP indicating IPv4_Address of UE_B or containing Framed-IPv6-Address_AVP indicating IPv6_Address of UE_B) containing one or more Media-Component-Description_AVP ( containing Media-Component-Number_AVP indicating values_derived from SDP containing one or more Media-Subcomponent-Description_AVP indicating values_derived from SDP) } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 89 Interoperability Test Description 3 TP_EPC_6028_02 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends AA-Answer to IMS_P-CSCF containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) and containing Acceptable-Service-Info_AVP ( containing one or more Media-Component-Description_AVP indicating values_derived from AA-Request ) and containing IP-CAN_AVP indicating Current_IP_CAN_Type of UE_B and containing RAT-Type_AVP indicating Current_RAT_Type of UE_B } } 4 TP_EPC_6029_06 ensure that { when { IMS_P-CSCF receives AA-Answer from EPC_PCRF } then { IMS_P-CSCF sends 180_Response to IMS_S-CSCF } } 5 TP_EPC_6032_01 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends early_media to UE_A } then { EPC uses_correct_bearers for service_data_flows } then { UE_A receives media } } 6 TP_EPC_6034_04 ensure that { when { IMS_P-CSCF receives 486_response on INVITE from UE_B } then { IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF containing Session-Id_AVP indicating session for SIP_session } } 7 TP_EPC_6009_03 ensure that { when { EPC_PCRF receives AA-Request from IMS_P-CSCF } then { EPC_PCRF sends Session-Termination-Answer to IMS_P-CSCF containing Session-Id_AVP indicating session for IMS_signalling session containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) } } 8 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } }
|
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_IMSEPC_Network_Attachment TP_IMSEPC_Registration_Initial TP_IMSEPC_Session_Establishment_Originating TP_IMSEPC_Session_Establishment_Terminating Use Case Ref.: TP_IMSEPC_Bearer_Modification ETSI ETSI TS 103 029 V3.1.1 (2011-11) 90 Interoperability Test Description Pre-test conditions: • UE_A previously attached to EPC with a single attachment • UE_A previously registered to IMS • UE_A previously established SIP session with UE_B Test Sequence: Step 1 EPC triggers removal of all bearers for a given SIP session 2 Verify that EPC aborts affected Rx sessions with IMS 3 Verify that IMS performs P-CSCF-initiated call release on affected SIP session 4 Verify that media is no longer exchanged after these procedures 5 Verify that media between UE and other endpoint can no longer be exchanged and is filtered out by EPC Conformance Criteria: Check 1 TP_EPC_6004_02 ensure that { when { EPC removes_relevant_bearers for SIP_session} then { EPC_PCRF triggers_termination of SIP_session } } 2 TP_EPC_6005_01 ensure that { when { EPC_PCRF triggers_termination of SIP_session } then { EPC_PCRF sends Abort-Session-Request to IMS_P-CSCF containing Session-Id_AVP indicating session of SIP_session containing Abort-Cause_AVP indicating BEARER_RELEASED (0) } } 3 TP_EPC_6006_01 ensure that { when { IMS_P-CSCF receives Abort-Session-Request for SIP_session } then { IMS_P-CSCF sends Abort-Session-Answer to EPC_PCRF ( containing Session-Id_AVP indicating value_received in Abort-Session-Request containing Result-Code_AVP indicating DIAMETER_SUCCESS(2001) ) and IMS_P-CSCF sends Session-Termination-Request to EPC_PCRF ( containing Session-Id_AVP indicating value_received in Abort-Session-Request ) and IMS_P-CSCF triggers_call_release } } 4 TP_EPC_6010_01 ensure that { when { IMS_P-CSCF triggers_call_release} then { IMS_P-CSCF sends BYE to UE_A containing Request_URI indicating contact_address from Contact_header of UE_A and containing To_header indicating the initial 200_OK_From_value and containing From_header indicating the initial INVITE_To_value and containing Call-ID_header indicating the initial INVITE_Call_Id_value and containing CSeq_header including an incremented Sequence_Number and containing Route_header indicating specific_routing_information for UE_A and containing Reason_header indicating 503_service_unavailable } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 91 Interoperability Test Description 5 TP_EPC_6003_02 ensure that { when { UE_A sends media to UE_B } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } when { UE_B sends media to UE_A } then { EPC filters the IP_packets } then { the IP_packets not visible on PO_SGi } } ETSI ETSI TS 103 029 V3.1.1 (2011-11) 92 Annex A (normative): zip file with TPLan code The test purposes used in the present document have been originally generated in the TPLan text files in the archive file ts_103029v030101p0.zip which accompanies the present document. ETSI ETSI TS 103 029 V3.1.1 (2011-11) 93 History Document history V3.1.1 November 2011 Publication
|
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 Protocol (SIP) and Session Description Protocol (SDP) standard, TS 124 229 [1] and Inter-IMS Network to Network Interface, TS 129 165 [7] define the functionalities on which the RCS services are based. TDs have been specified on the basis of the Test Purposes (TPs) and Test Suite Structure (TSS) presented in TS 186 011-1 [2]. TP fragments presented in the present document as part of TDs are defined using the TPLan notation of ES 202 553 [5]. TDs have been written based on the test specification framework described in TS 102 351 [3] and the interoperability testing methodology defined in TS 102 237-1 [4], i.e. interoperability testing with a conformance relation. NOTE: Requirements pertaining to a UE or an AS implementation or IMS core network requirements that can only be observed at the interface between UE and IMS CN are explicitly not within the scope of the present document. The latter requirements have been dealt with from a UE and conformance perspective in TS 134 229-1 [6].
|
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 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.
|
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 Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 8.10.0 Release 8)". [2] ETSI TS 186 011-1 (V3.1.1): "IMS Network Testing (INT); IMS NNI InteroperabilityTest Specifications; Part 1: Test Purposes for IMS NNI Interoperability". [3] ETSI TS 102 351: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [4] ETSI TS 102 237-1: "Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to interoperability testing". [5] ETSI ES 202 553: "Methods for Testing and Specification (MTS); TPLan: A notation for expressing Test Purposes". [6] ETSI TS 134 229-1 (V8.5.0): "Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Part 1: Protocol conformance specification (3GPP TS 34.229-1 version 8.5.0 Release 8)". [7] ETSI TS 129 165 (V8.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Inter-IMS Network to Network Interface (NNI) (3GPP TS 29.165 version 8.4.0 Release 8)". ETSI ETSI TS 102 901 V4.1.1 (2012-05) 8 [8] RCS-e - Advanced Communications: "Services and Client Specification. Version 1.1". [9] ETSI TS 186 011-2 (V3.1.1): "IMS Network Testing (INT); IMS NNI Interoperability Test Specifications; Part 2: Test Description for IMS NNI Interoperability". [10] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)". [11] IETF RFC 4976: "Relay Extensions for the Message Session Relay Protocol (MSRP)". [12] IETF RFC 6135: "An Alternative Connection Model for the Message Session Relay Protocol (MSRP)". [13] IETF RFC 5547: "A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer".
|
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 Interconnection Border Control Gateway II-NNI Inter-IMS Network to Network Interface IM Instant Messaging IMS IP Multimedia Subsystem IOI Inter Operator Identifier IP Internet Protocol ISC IMS Service Control MRFC Multimedia Resource Function Controller MRFP Multimedia Resource Function Processor NNI Network-to-Network Interface P-CSCF Proxy CSCF PO Point of Observation PS Presence Server RCS Rich Communication Suite RLS Resource List Server S-CSCF Serving CSCF SDP Session Description Protocol SIP Session Initiation Protocol SUT System Under Test TD Test Description TP Test Purpose TPLan Test Purpose Notation TSS Test Suite Structure UC Use Case UE User Equipment ETSI ETSI TS 102 901 V4.1.1 (2012-05) 9 URI Uniform Record Identifier XMDS XML Document Management Server
|
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 userIM_priv userIM na 1 contact IM AS for Instant Messaging userFT_priv userFT na 1 contact IM AS for File Transfer userSHARE_priv userSHARE na 1
|
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 server may support "store and forward" feature. ETSI ETSI TS 102 901 V4.1.1 (2012-05) 10
|
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 descriptions in [8]). In the case that an AS does not support one or more of these services, only a selected subset of the test descriptions in the present document should be used for IMS core network interoperability testing, i.e. test descriptions which do not contain any pass criteria related to these supplementary services.
|
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 process through OPTIONS message Use Cases are described in clauses 4.4.1.2 and 4.4.1.3. The use of capability discovery via presence method assumes that user additionally subscribed to an optional Social Presence service. In this case capability discovery should be performed using Social Presence service procedures. Use Cases for Social Presence services including capability discovery issues are described in clause 4.4.2. It should be mentioned that in both capability discovery methods UE A and UE B should be registered on corresponding IMS networks A and B depending on the test scenarios (interworking and roaming). 4.4.1.2 UC_RCS_1_I: SIP message flow for Capability discovery process through OPTIONS message with CF_INT_AS 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_AS 1 User A selects a contact of user B in the phone address book Step 1 2 User B is informed about user A capabilities Step 7 3 User A is informed about user B capabilities Step 13 ETSI ETSI TS 102 901 V4.1.1 (2012-05) 11 The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A 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 selects a contact of user B in the phone address book 2 OPTIONS UE_A sends OPTIONS to IMS_A with Accept- contact header containing user A capabilities (RCS-e services Tags) 3 OPTIONS IMS_A forwards OPTIONS to IBCF_A 4 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 5 OPTIONS IBCF_B forwards OPTIONS to IMS_B 6 OPTIONS IMS_B forwards OPTIONS to UE_B 7 User B is informed about user A capabilities 8 200 OK UE_B responds with 200 OK to IMS_B with Contact header containing user B capabilities (RCS-e services Tags) 9 200 OK IMS_B forwards 200 OK to IBCF_B 10 200 OK IBCF_B forwards 200 OK to IBCF_A 11 200 OK IBCF_A forwards 200 OK to IMS_A 12 200 OK IMS_A forwards 200 OK to UE_A 13 User A is informed about user B capabilities 4.4.1.3 UC_RCS_1_R: SIP message flow for Capability discovery process through OPTIONS message with CF_ROAM_AS (OPTIONAL) 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_AS 1 User A selects a contact of user B in the phone address book Step 1 2 User B is informed about user A capabilities Step 10 3 User A is informed about user B capabilities Step 19 ETSI ETSI TS 102 901 V4.1.1 (2012-05) 12 The expected call flow sequence is: Step Direction Message Comment U s e r A U E A I M S A 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 selects a contact of user B in the phone address book 2 OPTIONS UE_A sends OPTIONS to IMS_A with Accept- contact header containing user A capabilities (RCS-e services Tags) 3 OPTIONS IMS_A forwards OPTIONS to IBCF_A 4 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 5 OPTIONS IBCF_B forwards OPTIONS to IMS_B 6 OPTIONS IMS_B forwards OPTIONS to IBCF_B 7 OPTIONS IBCF_B forwards OPTIONS to IBCF_A 8 OPTIONS IBCF_A forwards OPTIONS to IMS_A 9 OPTIONS IMS_A forwards OPTIONS to UE_B 10 User B is informed about user A capabilities 11 200 OK UE_B responds with 200 OK to IMS_A with Contact header containing user B capabilities (RCS-e services Tags) 12 200 OK IMS_A forwards 200 OK to IBCF_A 13 200 OK IBCF_A forwards 200 OK to IBCF_B 14 200 OK IBCF_B forwards 200 OK to IMS_B 15 200 OK IMS_B forwards 200 OK to IBCF_B 16 200 OK IBCF_B forwards 200 OK to IBCF_A 17 200 OK IBCF_A forwards 200 OK to IMS_A 18 200 OK IMS_A forwards 200 OK to UE_A 19 User A is informed about user B capabilities
|
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 the capability discovery issues are considered. The list of Use Cases for Social Presence service include: • Watcher subscription to presence event notification; • Watcher subscription to resource list. ETSI ETSI TS 102 901 V4.1.1 (2012-05) 13 All of the Use Cases for Social Presence service in the present document include procedures of one user authorizing another user to see its Social Presence information.
|
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.2.2 Watcher subscription to presence event notification
| |
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.2.2.1 Description
|
UE_B is configured to receive notifications with watcher information. UE_B publishes its presence information. UE_A subscribes to presence information state changes of UE_B. This test requires the use of application server in IMS_B (Presence Server). The call flow path and node configuration for this use case corresponds to CF_INT_AS in case of interworking and CF_ROAM_AS (OPTIONAL) in case of roaming. 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_AS CF_ROAM_AS (OPTIONAL) 1 User B publishes presence and capability information including capabilities Step 1 Step 1 2 User B is informed of its presence status update Step 6 Step 12 3 User A selects a contact of user B in the phone address book Step 7 Step 13 4 User B is informed about user A capabilities Step 13 Step 22 5 User A is informed about user B capabilities Step 19 Step 31 6 User A subscribes to presence and capability information from User B Step 20 Step 32 7 SUBSCRIPTION triggers the AS to send a NOTIFY to UE_B indicating the change to the watcher information subscriber Step 39 Step 51 8 User B receives an authorization request from User A to see its own presence and capability information Step 44 Step 62 9 User B authorizes user A to be informed of its own presence and capability information Step 45 Step 63 10 User A is informed of user B presence and capability information Step 54 Step 72 11 User A sees user B presence and capability information Step 59 Step 83 4.4.2.2.2 UC_RCS_2_I: SIP message flow for watcher subscription to presence event notification with CF_INT_AS The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information including capabilities 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence elements and capabilities 3 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 4 200 OK IMS_B AS responds with a 200 OK to IMS_B 5 200 OK IMS_B forwards the 200 OK response to IBCF_B 6 User B is informed of its presence status update 7 User A selects a contact of user B in the phone address book ETSI ETSI TS 102 901 V4.1.1 (2012-05) 14 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 8 OPTIONS UE_A sends OPTIONS to IMS_A with Accept-contact header containing user A capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 9 OPTIONS IMS_A forwards OPTIONS to IBCF_A 10 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 11 OPTIONS IBCF_B forwards OPTIONS to IMS_B 12 OPTIONS IMS_B forwards OPTIONS to UE_B 13 User B is informed about user A capabilities 14 200 OK UE_B responds with 200 OK to IMS_B with Contact header containing user B capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 15 200 OK IMS_B forwards 200 OK to IBCF_B 16 200 OK IBCF_B forwards 200 OK to IBCF_A 17 200 OK IBCF_A forwards 200 OK to IMS_A 18 200 OK IMS_A forwards 200 OK to UE_A 19 User A is informed about user B capabilities 20 User A subscribes to presence and capability information from User B 21 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "User B presence" event with expiry time of 0 to IMS_A 22 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 23 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 24 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 25 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 26 200 OK IMS_B AS responds with a 200 OK to IMS_B 27 200 OK IMS_B forwards the 200 OK response to IBCF_B 28 200 OK IBCF_B forwards the 200 OK response to IBCF_A 29 200 OK IBCF_A forwards the 200 OK response to IMS_A 30 200 OK IMS_A forwards the 200 OK response to UE_A 31 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 32 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 33 NOTIFY IBCF_A forwards NOTIFY to IMS_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 15 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 34 NOTIFY IMS_A forwards the NOTIFY to UE_A 35 200 OK UE_A responds with a 200 OK to IMS_A 36 200 OK IMS_A forwards the 200 OK to IBCF_A 37 200 OK IBCF_A forwards the 200 OK to IBCF_B 38 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 39 SUBSCRIPTION triggers the AS to send a NOTIFY to UE_B indicating the change to the watcher information subscriber 40 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B the change to the watcher information subscriber 41 NOTIFY IMS_B forwards the NOTIFY to UE_B 42 200 OK UE_B responds with a 200 OK to IMS_B 43 200 OK IMS_B forwards the 200 OK response to IMS_B AS 44 User B receives an authorization request from User A to see its own presence and capability information 45 User B authorizes user A to be informed of its own presence and capability information 46 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 47 NOTIFY IBCF_B sends NOTIFY to IBCF_A 48 NOTIFY IBCF_A forwards NOTIFY to IMS_A 49 NOTIFY IMS_A forwards the NOTIFY to UE_A 50 200 OK UE_A responds with a 200 OK to IMS_A 51 200 OK IMS_A forwards the 200 OK response to IBCF_A 52 200 OK IBCF_A forwards the 200 OK response to IBCF_B 53 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 54 User A is informed of user B presence and capability information 55 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B that subscription has been authorized 56 NOTIFY IMS_B forwards the NOTIFY to UE_B 57 200 OK UE_B responds with a 200 OK to IMS_B 58 200 OK IMS_B forwards the 200 OK response to IMS_B AS 59 User A sees user B presence and capability information ETSI ETSI TS 102 901 V4.1.1 (2012-05) 16 4.4.2.2.3 UC_RCS_2_R: SIP message flow for watcher subscription to presence event notification with CF_ROAM_AS (OPTIONAL) The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence elements 3 PUBLISH IMS_A forwards the PUBLISH to IBCF_A 4 PUBLISH IBCF_A forwards the PUBLISH to IBCF_B 5 PUBLISH IBCF_B forwards the PUBLISH to IMS_B 6 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 7 200 OK IMS_B AS responds with a 200 OK to IMS_B 8 200 OK IMS_B forwards the 200 OK response to IBCF_B 9 200 OK IBCF_B forwards the 200 OK response to IBCF_A 10 200 OK IBCF_A forwards the 200 OK response to IMS_A 11 200 OK IMS_A forwards the 200 OK response to UE_B 12 User B is informed of its presence status update 13 User A selects a contact of user B in the phone address book 14 OPTIONS UE_A sends OPTIONS to IMS_A with Accept-contact header containing user A capabilities (RCS-e services Tags and the Tag indicating support of discovery via presence) 15 OPTIONS IMS_A forwards OPTIONS to IBCF_A 16 OPTIONS IBCF_A forwards OPTIONS to IBCF_B 17 OPTIONS IBCF_B forwards OPTIONS to IMS_B 18 OPTIONS IMS_B forwards OPTIONS to IBCF_B 19 OPTIONS IBCF_B forwards OPTIONS to IBCF_A 20 OPTIONS IBCF_A forwards OPTIONS to IMS_A 21 OPTIONS IMS_A forwards OPTIONS to UE_B 22 User B is informed about user A capabilities 23 200 OK UE_B responds with 200 OK to IMS_A with Contact header containing user B capabilities (RCS-e services Tags and the Tag indicating support via presence) 24 200 OK IMS_A forwards 200 OK to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 17 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 25 200 OK IBCF_A forwards 200 OK to IBCF_B 26 200 OK IBCF_B forwards 200 OK to IMS_B 27 200 OK IMS_B forwards 200 OK to IBCF_B 28 200 OK IBCF_B forwards 200 OK to IBCF_A 29 200 OK IBCF_A forwards 200 OK to IMS_A 30 200 OK IMS_A forwards 200 OK to UE_A 31 User A is informed about user B capabilities 32 User A subscribes to presence and capability information from User B 33 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "User B presence" event with expiry time of 0 to IMS_A 34 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 35 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 36 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 37 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 38 200 OK IMS_B AS responds with a 200 OK to IMS_B 39 200 OK IMS_B forwards the 200 OK response to IBCF_B 40 200 OK IBCF_B forwards the 200 OK response to IBCF_A 41 200 OK IBCF_A forwards the 200 OK response to IMS_A 42 200 OK IMS_A forwards the 200 OK response to UE_A 43 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 44 NOTIFY IBCF_B forwards NOTIFY to IBCF_A 45 NOTIFY IBCF_A forwards NOTIFY to IMS_A 46 NOTIFY IMS_A forwards the NOTIFY to UE_A 47 200 OK UE_A responds with a 200 OK to IMS_A 48 200 OK IMS_A forwards the 200 OK to IBCF_A 49 200 OK IBCF_A forwards the 200 OK to IBCF_B 50 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 51 SUBSCRIPTION triggers the AS to send a NOTIFY to UE_B indicating the change to the watcher information subscriber 52 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B the change to the watcher information subscriber ETSI ETSI TS 102 901 V4.1.1 (2012-05) 18 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 53 NOTIFY IMS_B forwards the NOTIFY to IBCF_B 54 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 55 NOTIFY IBCF_A forwards the NOTIFY to IMS_A 56 NOTIFY IMS_A forwards the NOTIFY to UE_B 57 200 OK UE_B responds with a 200 OK to IMS_A 58 200 OK IMS_A forwards the 200 OK response to IBCF_A 59 200 OK IBCF_A forwards the 200 OK response to IBCF_B 60 IBCF_B forwards the 200 OK response to IMS_B 61 200 OK IMS_B forwards the 200 OK response to IMS_B AS 62 User B receives an authorization request from User A to see its own presence and capability information 63 User B authorizes user A to be informed of its own presence and capability information 64 NOTIFY IMS_B AS sends NOTIFY to IBCF_B 65 NOTIFY IBCF_B sends NOTIFY to IBCF_A 66 NOTIFY IBCF_A forwards NOTIFY to IMS_A 67 NOTIFY IMS_A forwards the NOTIFY to UE_A 68 200 OK UE_A responds with a 200 OK to IMS_A 69 200 OK IMS_A forwards the 200 OK response to IBCF_A 70 200 OK IBCF_A forwards the 200 OK response to IBCF_B 71 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 72 User A is informed of user B presence and capability information 73 NOTIFY IMS_B AS sends NOTIFY to IMS_B to indicate UE_B that subscription has been authorized 74 NOTIFY IMS_B forwards the NOTIFY to IBCF_B 75 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 76 NOTIFY IBCF_A forwards the NOTIFY to IMS_A 77 NOTIFY IMS_A forwards the NOTIFY to UE_B 78 200 OK UE_B responds with a 200 OK to IMS_A 79 200 OK IMS_A forwards the 200 OK response to IBCF_A 80 200 OK IBCF_A forwards the 200 OK response to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 19 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 81 200 OK IBCF_B forwards the 200 OK response to IMS_B 82 200 OK IMS_B forwards the 200 OK response to IMS_B AS 83 User A sees user B presence and capability information
|
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.2.3 Watcher subscription to resource list
| |
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.2.3.1 Description
|
UE_B is configured to receive notifications with watcher information. UE_B publishes its presence information. User B has authorized User A to see its presence information. User A is authorized to use resource lists which are considered to be XDMS lists of contacts provisioned in the user client and AS. UE_A subscribes to presence information state changes of a list of users containing UE_B. This test requires the use of application server in IMS_B, having the role of Presence Server (PS), and the use of application server in IMS_A, having the role of Resource List Server (RLS). The call flow path and node configuration for this use case corresponds to CF_INT_AS in case of interworking and CF_ROAM_AS (OPTIONAL) in case of roaming. 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_AS CF_ROAM_AS (OPTIONAL) 1 User B publishes presence and capability information Step 1 Step 1 2 User B is informed of its presence status update Step 6 Step 12 3 User A subscribes to resource list previously stored in the User A client as XDMS list of contacts Step 7 Step 13 4 RLS performs authorization checks to ensure that User A is authorized to use resource lists Step 10 Step 16 5 RLS resolves watcher resource´s address and subscribes for presence event notification for all the presentities represented by the resource list SIP URI Step 17 Step 23 6 PS performs authorization checks on the originator to ensure it is allowed to watch the presentity Step 23 Step 29 7 RLS notifies with presence and capability information for all the presentities represented by the resource list SIP URI Step 37 Step 43 8 User A sees user B presence and capability information Step 42 Step 48 ETSI ETSI TS 102 901 V4.1.1 (2012-05) 20 4.4.2.3.2 UC_RCS_3_I: SIP message flow for watcher subscription to resource list with CF_INT_AS The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence and capability elements 3 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 4 200 OK IMS_B AS responds with a 200 OK to IMS_B 5 200 OK IMS_B forwards the 200 OK response to UE_B 6 User B is informed of its presence status update 7 User A subscribes to resource list previously stored in the User A client as XDMS list of contacts 8 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "presence" event with expiry time of 0 to IMS_A indicating support to "eventlist" to a resource list SIP URI 9 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IMS_A AS (RLS) 10 RLS performs authorization checks to ensure that User A is authorized to use resource lists 11 200 OK IMS_A AS responds with a 200 OK to IMS_A 12 200 OK IMS_A forwards the 200 OK response to UE_A 13 NOTIFY IMS_A AS sends NOTIFY to IMS_A 14 NOTIFY IMS_A forwards the NOTIFY to UE_A 15 200 OK UE_A responds with a 200 OK to IMS_A 16 200 OK IMS_A forwards the 200 OK response to IMS_A AS 17 RLS resolves watcher resource´s address and subscribes for presence event notification for all the presentities represented by the resource list SIP URI 18 SUBSCRIBE IMS_A AS (RLS) sends SUBSCRIBE for "presence" event to IMS_A 19 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 20 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 21 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 22 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) ETSI ETSI TS 102 901 V4.1.1 (2012-05) 21 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 23 PS performs authorization checks on the originator to ensure it is allowed to watch the presentity 24 200 OK IMS_B AS (PS) responds with a 200 OK to IMS_B 25 200 OK IMS_B forwards the 200 OK response to IBCF_B 26 200 OK IBCF_B forwards the 200 OK response to IBCF_A 27 200 OK IBCF_A forwards the 200 OK response to IMS_A 28 200 OK IMS_A forwards the 200 OK response to IMS_A AS (RLS) 29 NOTIFY IMS_B AS sends a NOTIFY to IBCF_B with the presence and capability information of UE_B 30 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 31 IBCF_A forwards the NOTIFY to IMS_A 32 NOTIFY IMS_A forwards the NOTIFY to IMS_A AS (RLS) 33 200 OK IMS_A AS responds with a 200 OK to IMS_A 34 200 OK IMS_A forwards the 200 OK response to IBCF_A 35 200 OK IBCF_A forwards the 200 OK response to IBCF_B 36 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 37 RLS notifies with presence and capability information for all the presentities represented by the resource list SIP URI 38 NOTIFY IMS_A AS sends NOTIFY to IMS_A 39 NOTIFY IMS_A forwards the NOTIFY to UE_A 40 200 OK UE_A responds with a 200 OK to IMS_A 41 200 OK IMS_A forwards the 200 OK response to IMS_A AS 42 User A sees user B presence and capability information ETSI ETSI TS 102 901 V4.1.1 (2012-05) 22 4.4.2.3.3 UC_RCS_3_R: SIP message flow for watcher subscription to resource list with CF_ROAM_AS (OPTIONAL) The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 1 User B publishes presence and capability information 2 PUBLISH UE_B sends PUBLISH with information for all commonly supported presence and capability elements 3 PUBLISH IMS_A forwards the PUBLISH to IBCF_A 4 PUBLISH IBCF_A forwards the PUBLISH to IBCF_B 5 PUBLISH IBCF_B forwards the PUBLISH to IMS_B 6 PUBLISH IMS_B forwards the PUBLISH to IMS_B AS (PS) 7 200 OK IMS_B AS responds with a 200 OK to IMS_B 8 200 OK IMS_B forwards the 200 OK response to IBCF_B 9 200 OK IBCF_B forwards the 200 OK response to IBCF_A 10 200 OK IBCF_A forwards the 200 OK response to IMS_A 11 200 OK IMS_A forwards the 200 OK response to UE_B 12 User B is informed of its presence status update 13 User A subscribes to resource list previously stored in the User A client as XDMS list of contacts 14 SUBSCRIBE UE_A sends ANONYMOUS SUBSCRIBE for "presence" event with expiry time of 0 to IMS_A indicating support to "eventlist" to a resource list SIP URI 15 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IMS_A AS (RLS) 16 RLS performs authorization checks to ensure that User A is authorized to use resource lists 17 200 OK IMS_A AS responds with a 200 OK to IMS_A 18 200 OK IMS_A forwards the 200 OK response to UE_A 19 NOTIFY IMS_A AS sends NOTIFY to IMS_A 20 NOTIFY IMS_A forwards the NOTIFY to UE_A 21 200 OK UE_A responds with a 200 OK to IMS_A 22 200 OK IMS_A forwards the 200 OK response to IMS_A AS 23 RLS resolves watcher resource´s address and subscribes for presence event notification for all the presentities represented by the resource list SIP URI ETSI ETSI TS 102 901 V4.1.1 (2012-05) 23 Step Direction Message Comment U s e r A U E A A S A I M S A I B C F A I B C F B I M S B A S B U E B U s e r B 24 SUBSCRIBE IMS_A AS (RLS) sends SUBSCRIBE for "presence" event to IMS_A 25 SUBSCRIBE IMS_A forwards the SUBSCRIBE to IBCF_A 26 SUBSCRIBE IBCF_A forwards the SUBSCRIBE to IBCF_B 27 SUBSCRIBE IBCF_B forwards the SUBSCRIBE to IMS_B 28 SUBSCRIBE IMS_B forwards the SUBSCRIBE to IMS_B AS (PS) 29 PS performs authorization checks on the originator to ensure it is allowed to watch the presentity 30 200 OK IMS_B AS (PS) responds with a 200 OK to IMS_B 31 200 OK IMS_B forwards the 200 OK response to IBCF_B 32 200 OK IBCF_B forwards the 200 OK response to IBCF_A 33 200 OK IBCF_A forwards the 200 OK response to IMS_A 34 200 OK IMS_A forwards the 200 OK response to IMS_A AS (RLS) 35 NOTIFY IMS_B AS sends a NOTIFY to IBCF_B with the presence and capability information of UE_B 36 NOTIFY IBCF_B forwards the NOTIFY to IBCF_A 37 IBCF_A forwards the NOTIFY to IMS_A 38 NOTIFY IMS_A forwards the NOTIFY to IMS_A AS (RLS) 39 200 OK IMS_A AS responds with a 200 OK to IMS_A 40 200 OK IMS_A forwards the 200 OK response to IBCF_A 41 200 OK IBCF_A forwards the 200 OK response to IBCF_B 42 200 OK IBCF_B forwards the 200 OK response to IMS_B AS 43 RLS notifies with presence and capability information for all the presentities represented by the resource list SIP URI 44 NOTIFY IMS_A AS sends NOTIFY to IMS_A 45 NOTIFY IMS_A forwards the NOTIFY to UE_A 46 200 OK UE_A responds with a 200 OK to IMS_A 47 200 OK IMS_A forwards the 200 OK response to IMS_A AS 48 User A sees user B presence and capability information ETSI ETSI TS 102 901 V4.1.1 (2012-05) 24
|
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.3 IM/chat service
| |
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.3.1 General description
|
IM/chat service session assumes the possibility for users to receive the following types of services: • 1-to-1 chat (including support of notifications and file transfer within 1-to-1 chat); • 1-to-many chat. For all Use Cases it is assumed that UEs registered on the corresponding IMS networks and they have already performed capability discovery procedures. In particular, users subscribed to IM/chat service.
|
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.3.2 1-to-1 chat standard procedure
|
Following there are the expected common call flow sequences for the standard procedures of 1-to-1 chat service between RCS-e users. 4.4.3.2.1 UC_RCS_4_I: SIP message flow for 1-to-1 chat standard procedure with CF_INT_AS 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_AS 1 User A selects User B in the phone address book and sends him an initial message Step 1 2 User B is informed of incoming message Step 20 3 User A is informed that initial message was delivered to user B Step 39 4 User B reads the initial message from user A and opens the 1-to-1 chat Step 49 5 Users perform chatting Step 68 6A User A closes the 1-to-1 chat Step 69A 6B User B closes the 1-to-1 chat Step 69B 7A User A is informed that 1-to-1 chat with user B is closed Step 88A 7B User B is informed that 1-to-1 chat with user A is closed Step 88B The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User A selects User B in the phone address book and sends him an initial message 2 INVITE UE_A sends INVITE to IMS_A with user A initial message in the Subject header, CPIM/IMND headers and the first SDP offer indicating all specific data for MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to AS/IM_A 5 100 Trying AS/IM_A responds with a 100 Trying provisional response 6 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 7 100 Trying IMS_A responds with a 100 Trying provisional response ETSI ETSI TS 102 901 V4.1.1 (2012-05) 25 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 8 INVITE IMS_A forwards INVITE to IBCF_A 9 100 Trying IBCF_A responds with a 100 Trying provisional response 10 INVITE IBCF_A forwards INVITE to IBCF_B 11 100 Trying IBCF_B responds with a 100 Trying provisional response 12 INVITE IBCF_B forwards INVITE to IMS_B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to AS/IM_B 15 100 Trying AS/IM_B responds with a 100 Trying provisional response 16 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 17 100 Trying IMS_B responds with a 100 Trying provisional response 18 INVITE IMS_B forwards INVITE to UE_B 19 100 Trying UE_B optionally responds with a 100 Trying provisional response 20 User B is informed of incoming message 21 180 Ringing UE_B responds to initial INVITE with 180 Ringing to indicate that invitation to a 1-to-1 chat session has reached the invited user 22 180 Ringing IMS_B forwards 180 Ringing response to AS/IM_B 23 180 Ringing AS/IM_B returns, possibly modified, 180 Ringing response to IMS_B 24 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 25 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 26 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 27 180 Ringing IMS_A forwards 180 Ringing response to AS/IM_A 28 180 Ringing AS/IM_A returns, possibly modified, 180 Ringing response to IMS_A 29 180 Ringing IMS_A forwards 180 Ringing response to UE_A 30 MESSAGE UE_B sends MESSAGE to IMS_B with delivery notification of initial message from user A 31 MESSAGE IMS_B forwards MESSAGE to AS/IM_B 32 MESSAGE AS/IM_B returns, possibly modified, MESSAGE to IMS_B 33 MESSAGE IMS_B forwards MESSAGE to IBCF_B 34 MESSAGE IBCF_B forwards MESSAGE to IBCF_A 35 MESSAGE IBCF_A forwards MESSAGE to IMS_A 36 MESSAGE IMS_A forwards MESSAGE to AS/IM_A 37 MESSAGE AS/IM_A returns, possibly modified, MESSAGE to IMS_A 38 MESSAGE IMS_A forwards MESSAGE to UE_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 26 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 39 User A is informed that initial message was delivered to user B 40 200 OK UE_A responds MESSAGE with 200 OK response 41 200 OK IMS_A forwards 200 OK response to AS/IM_A 42 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 43 200 OK IMS_A forwards 200 OK response to IBCF_A 44 200 OK IBCF_A forwards 200 OK response to IBCF_B 45 200 OK IBCF_B forwards 200 OK response to IMS_B 46 200 OK IMS_B forwards 200 OK response to AS/IM_B 47 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 48 200 OK IMS_B forwards 200 OK response to UE_B 49 User B reads the initial message from user A and opens the 1-to-1 chat 50 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform A-side with specific data for MSRP connection set up 51 200 OK IMS_B forwards 200 OK response to AS/IM_B 52 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 53 200 OK IMS_B forwards 200 OK response to IBCF_B 54 200 OK IBCF_B forwards 200 OK response to IBCF_A 55 200 OK IBCF_A forwards 200 OK response to IMS_A 56 200 OK IMS_A forwards 200 OK response to AS/IM_A 57 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 58 200 OK IMS_A forwards 200 OK response to UE_A 59 ACK UE_A acknowledges the receipt of 200 OK for INVITE 60 ACK IMS_A forwards ACK to AS/IM_A 61 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 62 ACK IMS_A forwards ACK to IBCF_A 63 ACK IBCF_A forwards ACK to IBCF_B 64 ACK IBCF_B forwards ACK to IMS_B 65 ACK IMS_B forwards ACK to AS/IM_B 66 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 67 ACK IMS_B forwards ACK to UE_B 68 Users perform chatting (see clause 5.3.1 Chat 1 to 1 via MSRP and use 5.4.1 test description) 69A User A closes the 1-to-1 chat ETSI ETSI TS 102 901 V4.1.1 (2012-05) 27 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 70A BYE UE_A releases the 1-to-1 chat session with BYE 71A BYE IMS_A forwards BYE to AS/IM_A 72A BYE AS/IM_A returns, possibly modified, BYE to IMS_A 73A BYE IMS_A forwards BYE to IBCF_A 74A BYE IBCF_A forwards BYE to IBCF_B 75A BYE IBCF_B forwards BYE to IMS_B 76A BYE IMS_B forwards BYE to AS/IM_B 77A BYE AS/IM_B returns, possibly modified, BYE to IMS_B 78A BYE IMS_B forwards BYE to UE_B 79A 200 OK UE_B sends 200 OK for BYE 80A 200 OK IMS_B forwards 200 OK response to AS/IM_B 81A 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 82A 200 OK IMS_B forwards 200 OK response to IBCF_B 83A 200 OK IBCF_B forwards 200 OK response to IBCF_A 84A 200 OK IBCF_A forwards 200 OK response to IMS_A 85A 200 OK IMS_A forwards 200 OK response to AS/IM_A 86A 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 87A 200 OK IMS_A forwards 200 OK response to UE_A 88A User A is informed that 1-to-1 chat with user B is closed 69B User B close the 1-to-1 chat 70B BYE UE_B releases the 1-to-1 chat session with BYE 71B BYE IMS_B forwards BYE to AS/IM_B 72B BYE AS/IM_B returns, possibly modified, BYE to IMS_B 73B BYE IMS_B forwards BYE to IBCF_B 74B BYE IBCF_B forwards BYE to IBCF_A 75B BYE IBCF_A forwards BYE to IMS_A 76B BYE IMS_A forwards BYE to AS/IM_A 77B BYE AS/IM_A returns, possibly modified, BYE to IMS_A 78B BYE IMS_A forwards BYE to UE_A 79B 200 OK UE_A sends 200 OK for BYE 80B 200 OK IMS_A forwards 200 OK response to AS/IM_A 81B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 82B 200 OK IMS_A forwards 200 OK response to IBCF_A 83B 200 OK IBCF_A forwards 200 OK response to IBCF_B 84B 200 OK IBCF_B forwards 200 OK response to IMS_B 85B 200 OK IMS_B forwards 200 OK response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 28 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 86B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 87B 200 OK IMS_B forwards 200 OK response to UE_B 88B User B is informed that that 1-to-1 chat with user A is closed 4.4.3.2.2 UC_RCS_4_R: SIP message flow for 1-to-1 chat standard procedure with CF_ROAM_AS (OPTIONAL) The test sequence typically associated with this use case is as follows (CFW step numbers refer the call flow step numbering): Step Action CF_ROAM_AS 1 User B selects User A in the phone address book and sends him an initial message Step 1 2 User A is informed of incoming message Step 26 3 User B is informed that initial message was delivered to user A Step 51 4 User A reads the initial message from user B and opens the 1-to-1 chat Step 64 5 Users perform chatting Step 89 6A User B closes the 1-to-1 chat Step 90A 6B User A closes the 1-to-1 chat Step 90B 7A User B is informed that that 1-to-1 chat with user A is closed Step 115A 7B User A is informed that that 1-to-1 chat with user B is closed Step 115B The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 User B selects User A in the phone address book and sends him an initial message 2 INVITE UE_B sends INVITE to IMS_A with user B initial message in the Subject header, CPIM/IMND headers and the first SDP offer indicating all specific data for MSRP connection set up 3 100 Trying IMS_A responds with a 100 Trying provisional response 4 INVITE IMS_A forwards INVITE to IBCF_A 5 100 Trying IBCF_A responds with a 100 Trying provisional response 6 INVITE IBCF_A forwards INVITE to IBCF_B 7 100 Trying IBCF_B responds with a 100 Trying provisional response 8 INVITE IBCF_B forwards INVITE to IMS_B 9 100 Trying IMS_B responds with a 100 Trying provisional response 10 INVITE IMS_B forwards INVITE to AS/IM_B 11 100 Trying AS/IM_B responds with a 100 Trying provisional response 12 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 29 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 13 100 Trying IMS_B responds with a 100 Trying provisional response 14 INVITE IMS_B forwards INVITE to IBCF_B 15 100 Trying IBCF_B responds with a 100 Trying provisional response 16 INVITE IBCF_B forwards INVITE to IBCF_A 17 100 Trying IBCF_A responds with a 100 Trying provisional response 18 INVITE IBCF_A forwards INVITE to IMS_A 19 100 Trying IMS_A responds with a 100 Trying provisional response 20 INVITE IMS_A forwards INVITE to AS/IM_A 21 100 Trying AS/IM_A responds with a 100 Trying provisional response 22 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 23 100 Trying IMS_A responds with a 100 Trying provisional response 24 INVITE IMS_A forwards INVITE to UE_A 25 100 Trying UE_A optionally responds with a 100 Trying provisional response 26 User A is informed of incoming message 27 180 Ringing UE_A responds to initial INVITE with 180 Ringing to indicate that invitation to a 1-to-1 chat session has reached the invited user 28 180 Ringing IMS_A forwards 180 Ringing response to AS/IM_A 29 180 Ringing AS/IM_A returns, possibly modified, 180 Ringing response to IMS_A 30 180 Ringing IMS_A forwards 180 Ringing response to IBCF_A 31 180 Ringing IBCF_A forwards 180 Ringing response to IBCF_B 32 180 Ringing IBCF_B forwards 180 Ringing response to IMS_B 33 180 Ringing IMS_B forwards 180 Ringing response to AS/IM_B 34 180 Ringing AS/IM_B returns, possibly modified, 180 Ringing response to IMS_B 35 180 Ringing IMS_B forwards 180 Ringing response to IBCF_B 36 180 Ringing IBCF_B forwards 180 Ringing response to IBCF_A 37 180 Ringing IBCF_A forwards 180 Ringing response to IMS_A 38 180 Ringing IMS_A forwards 180 Ringing response to UE_B 39 MESSAGE UE_A sends MESSAGE to IMS_A with delivery notification of initial message from user B 40 MESSAGE IMS_A forwards MESSAGE to AS/IM_A 41 MESSAGE AS/IM_A returns, possibly modified, MESSAGE to IMS_A 42 MESSAGE IMS_A forwards MESSAGE to IBCF_A 43 MESSAGE IBCF_A forwards MESSAGE to IBCF_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 30 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 44 MESSAGE IBCF_B forwards MESSAGE to IMS_B 45 MESSAGE IMS_B forwards MESSAGE to AS/IM_B 46 MESSAGE AS/IM_B returns, possibly modified, MESSAGE to IMS_B 47 MESSAGE IMS_B forwards MESSAGE to IBCF_B 48 MESSAGE IBCF_B forwards MESSAGE to IBCF_A 49 MESSAGE IBCF_A forwards MESSAGE to IMS_A 50 MESSAGE IMS_A forwards MESSAGE to UE_B 51 User B is informed that initial message was delivered to user A 52 200 OK UE_B responds MESSAGE with 200 OK response 53 200 OK IMS_A forwards 200 OK response to IBCF_A 54 200 OK IBCF_A forwards 200 OK response to IBCF_B 55 200 OK IBCF_B forwards 200 OK response to IMS_B 56 200 OK IMS_B forwards 200 OK response to AS/IM_B 57 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 58 200 OK IMS_B forwards 200 OK response to IBCF_B 59 200 OK IBCF_B forwards 200 OK response to IBCF_A 60 200 OK IBCF_A forwards 200 OK response to IMS_A 61 200 OK IMS_A forwards 200 OK response to AS/IM_A 62 200 OK AS/IM_A returns, possibly modified, ACK to IMS_A 63 200 OK IMS_A forwards ACK to UE_A 64 User A reads the initial message from user B and opens the 1-to-1 chat 65 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform B-side with specific data for MSRP connection set up 66 200 OK IMS_A forwards 200 OK response to AS/IM_A 67 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 68 200 OK IMS_A forwards 200 OK response to IBCF_A 69 200 OK IBCF_A forwards 200 OK response to IBCF_B 70 200 OK IBCF_B forwards 200 OK response to IMS_B 71 200 OK IMS_B forwards 200 OK response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 31 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 72 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 73 200 OK IMS_B forwards 200 OK response to IBCF_B 74 200 OK IBCF_B forwards 200 OK response to IBCF_A 75 200 OK IBCF_A forwards 200 OK response to IMS_A 76 200 OK IMS_A forwards 200 OK response to UE_B 77 ACK UE_B acknowledges the receipt of 200 OK for INVITE 78 ACK IMS_A forwards ACK to IBCF_A 79 ACK IBCF_A forwards ACK to IBCF_B 80 ACK IBCF_B forwards ACK to IMS_B 81 ACK IMS_B forwards ACK to AS/IM_B 82 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 83 ACK IMS_B forwards ACK to IBCF_B 84 ACK IBCF_B forwards ACK to IBCF_A 85 ACK IBCF_A forwards ACK to IMS_A 86 ACK IMS_A forwards ACK to AS/IM_A 87 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 88 ACK IMS_A forwards ACK to UE_A 89 Users perform chatting (see clause 5.3.1 Chat 1 to 1 via MSRP and use 5.4.1 test description) 90A User B closes the 1-to-1 chat 91A BYE UE_B releases the 1-to-1 chat session with BYE 92A BYE IMS_A forwards BYE to IBCF_A 93A BYE IBCF_A forwards BYE to IBCF_B 94A BYE IBCF_B forwards BYE to IMS_B 95A BYE IMS_B forwards BYE to AS/IM_B 96A BYE AS/IM_B returns, possibly modified, BYE to IMS_B 97A BYE IMS_B forwards BYE to IBCF_B 98A BYE IBCF_B forwards BYE to IBCF_A 99A BYE IBCF_A forwards BYE to IMS_A 100A BYE IMS_A forwards BYE to AS/IM_A 101A BYE AS/IM_A returns, possibly modified, BYE to IMS_A 102A BYE IMS_A forwards BYE to UE_A 103A 200 OK UE_A sends 200 OK for BYE 104A 200 OK IMS_A forwards 200 OK response to AS/IM_A 105A 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 106A 200 OK IMS_A forwards 200 OK response to IBCF_A 107A 200 OK IBCF_A forwards 200 OK response to IBCF_B 108A 200 OK IBCF_B forwards 200 OK response to IMS_B 109A 200 OK IMS_B forwards 200 OK response to AS/IM_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 32 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 110A 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 111A 200 OK IMS_B forwards 200 OK response to IBCF_B 112A 200 OK IBCF_B forwards 200 OK response to IBCF_A 113A 200 OK IBCF_A forwards 200 OK response to IMS_A 114A 200 OK IMS_A forwards 200 OK response to UE_B 115A User B is informed that that 1-to-1 chat with user A is closed 90B User A closes the 1-to-1 chat 91B BYE UE_A releases the 1-to-1 chat session with BYE 92B BYE IMS_A forwards BYE to AS/IM_A 93B BYE AS/IM_A returns, possibly modified, BYE to IMS_A 94B BYE IMS_A forwards BYE to IBCF_A 95B BYE IBCF_A forwards BYE to IBCF_B 96B BYE IBCF_B forwards BYE to IMS_B 97B BYE IMS_B forwards BYE to AS/IM_B 98B BYE AS/IM_B returns, possibly modified, BYE to IMS_B 99B BYE IMS_B forwards BYE to IBCF_B 100B BYE IBCF_B forwards BYE to IBCF_A 101B BYE IBCF_A forwards BYE to IMS_A 102B BYE IMS_A forwards BYE to UE_B 103B 200 OK UE_B sends 200 OK for BYE 104B 200 OK IMS_A forwards 200 OK response to IBCF_A 105B 200 OK IBCF_A forwards 200 OK response to IBCF_B 106B 200 OK IBCF_B forwards 200 OK response to IMS_B 107B 200 OK IMS_B forwards 200 OK response to AS/IM_B 108B 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 109B 200 OK IMS_B forwards 200 OK response to IBCF_B 110B 200 OK IBCF_B forwards 200 OK response to IBCF_A 111B 200 OK IBCF_A forwards 200 OK response to IMS_A 112B 200 OK IMS_A forwards 200 OK response to AS/IM_A 113B 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 114B 200 OK IMS_A forwards 200 OK response to UE_A 115B User A is informed that that 1-to-1 chat with user B is closed ETSI ETSI TS 102 901 V4.1.1 (2012-05) 33
|
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.3.3 File transfer within 1-to-1 chat
|
Following there are the expected common call flow sequences for IM/chat service when the incoming one-to-one IM session requests is not answered by the RCS client. 4.4.3.3.1 UC_RCS_5_I: SIP message flow for file transfer within 1-to-1 chat with CF_INT_AS 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_AS 1 User A selects User B in the phone address book and sends him an initial message UC_RCS_4_I Step 1 2 User B is informed of incoming message UC_RCS_4_I Step 20 3 User A is informed that initial message was delivered to user B UC_RCS_4_I Step 39 4 User B reads the initial message from user A and opens the 1- to-1 chat UC_RCS_4_I Step 49 5 Users perform chatting UC_RCS_4_I Step 68 6 User A initiates a file transfer to user B Step 2 7 User B is informed of incoming file and accepts the transfer Step 21 8 User A is informed that file transfer has been accepted by user B Step 31 9 File transfer starts Step 41 10 File transfer completed (size checked) Step 42 11 User B is informed that file transfer completed Step 52 12 User A is informed that file transfer completed Step 62 13 Users continue chatting Step 63 14A User A closes the 1-to-1 chat UC_RCS_4_I Step 69A 14B User B closes the 1-to-1 chat UC_RCS_4_I Step 69B 15A User A is informed that 1-to-1 chat with user B is closed UC_RCS_4_I Step 88A 15B User B is informed that 1-to-1 chat with user A is closed UC_RCS_4_I Step 88B The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_I (1-68) 2 User A initiates a file transfer to user B 3 INVITE UE_A sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to AS/IM_A 6 100 Trying AS/IM_A responds with a 100 Trying provisional response 7 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 8 100 Trying IMS_A responds with a 100 Trying provisional response 9 INVITE IMS_A forwards INVITE to IBCF_A 10 100 Trying IBCF_A responds with a 100 Trying provisional response 11 INVITE IBCF_A forwards INVITE to IBCF_B 12 100 Trying IBCF_B responds with a 100 Trying provisional response 13 INVITE IBCF_B forwards INVITE to IMS_B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 34 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to AS/IM_B 16 100 Trying AS/IM_B responds with a 100 Trying provisional response 17 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 18 100 Trying IMS_B responds with a 100 Trying provisional response 19 INVITE IMS_B forwards INVITE to UE_B 20 100 Trying UE_B optionally responds with a 100 Trying provisional response 21 User B is informed of incoming file and accepts the transfer 22 200 OK UE_B responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform A-side with specific data for a new MSRP connection set up 23 200 OK IMS_B forwards 200 OK response to AS/IM_B 24 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 25 200 OK IMS_B forwards 200 OK response to IBCF_B 26 200 OK IBCF_B forwards 200 OK response to IBCF_A 27 200 OK IBCF_A forwards 200 OK response to IMS_A 28 200 OK IMS_A forwards 200 OK response to AS/IM_A 29 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 30 200 OK IMS_A forwards 200 OK response to UE_A 31 User A is informed that file transfer has been accepted by user B 32 ACK UE_A acknowledges the receipt of 200 OK for INVITE 33 ACK IMS_A forwards ACK to AS/IM_A 34 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 35 ACK IMS_A forwards ACK to IBCF_A 36 ACK IBCF_A forwards ACK to IBCF_B 37 ACK IBCF_B forwards ACK to IMS_B 38 ACK IMS_B forwards ACK to AS/IM_B 39 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 40 ACK IMS_B forwards ACK to UE_B 41 File transfer starts (see clause 5.3.3 and use 5.4.1 test description) 42 File transfer completed (size checked) 43 BYE UE_A releases the file transfer session with BYE 44 BYE IMS_A forwards BYE to AS/IM_A 45 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 46 BYE IMS_A forwards BYE to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 35 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 47 BYE IBCF_A forwards BYE to IBCF_B 48 BYE IBCF_B forwards BYE to IMS_B 49 BYE IMS_B forwards BYE to AS/IM_B 50 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 51 BYE IMS_B forwards BYE to UE_B 52 User B is informed that file transfer completed 53 200 OK UE_B sends 200 OK for BYE 54 200 OK IMS_B forwards 200 OK response to AS/IM_B 55 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 56 200 OK IMS_B forwards 200 OK response to IBCF_B 57 200 OK IBCF_B forwards 200 OK response to IBCF_A 58 200 OK IBCF_A forwards 200 OK response to IMS_A 59 200 OK IMS_A forwards 200 OK response to AS/IM_A 60 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 61 200 OK IMS_A forwards 200 OK response to UE_A 62 User A is informed that file transfer completed 63 Users continue chatting 64 Continue UC_RCS_4_I (69A-88B) 4.4.3.3.2 UC_RCS_5_R: SIP message flow for file transfer within 1-to-1 chat with CF_ROAM_AS (OPTIONAL) 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_AS 1 User B selects User A in the phone address book and sends him an initial message UC_RCS_4_R Step 1 2 User A is informed of incoming message UC_RCS_4_R Step 26 3 User B is informed that initial message was delivered to user A UC_RCS_4_R Step 51 4 User A reads the initial message from user B and opens the 1-to-1 chat UC_RCS_4_R Step 64 5 Users perform chatting UC_RCS_4_R Step 89 6 User B initiates a file transfer to user A Step 2 7 User A is informed of incoming file and accepts the transfer Step 27 8 User B is informed that file transfer has been accepted by user B Step 40 9 File transfer starts Step 53 10 File transfer completed (size checked) Step 54 11 User A is informed that file transfer completed Step 67 12 User B is informed that file transfer completed Step 80 13 Users continue chatting Step 81 14A User B closes the 1-to-1 chat UC_RCS_4_R Step 90A 14B User A closes the 1-to-1 chat UC_RCS_4_R Step 90B 15A User B is informed that that 1-to-1 chat with user A is closed UC_RCS_4_R Step 115A 15B User A is informed that that 1-to-1 chat with user B is closed UC_RCS_4_R Step 115B ETSI ETSI TS 102 901 V4.1.1 (2012-05) 36 The expected call flow sequence is: Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 1 Follow UC_RCS_4_R (1-89) 2 User B initiates a file transfer to user A 3 INVITE UE_B sends INVITE to IMS_A to establish a new session with the SDP offer indicating all specific data for a new MSRP connection set up 4 100 Trying IMS_A responds with a 100 Trying provisional response 5 INVITE IMS_A forwards INVITE to IBCF_A 6 100 Trying IBCF_A responds with a 100 Trying provisional response 7 INVITE IBCF_A forwards INVITE to IBCF_B 8 100 Trying IBCF_B responds with a 100 Trying provisional response 9 INVITE IBCF_B forwards INVITE to IMS_B 10 100 Trying IMS_B responds with a 100 Trying provisional response 11 INVITE IMS_B forwards INVITE to AS/IM_B 12 100 Trying AS/IM_B responds with a 100 Trying provisional response 13 INVITE AS/IM_B returns, possibly modified, INVITE to IMS_B 14 100 Trying IMS_B responds with a 100 Trying provisional response 15 INVITE IMS_B forwards INVITE to IBCF_B 16 100 Trying IBCF_B responds with a 100 Trying provisional response 17 INVITE IBCF_B forwards INVITE to IBCF_A 18 100 Trying IBCF_A responds with a 100 Trying provisional response 19 INVITE IBCF_A forwards INVITE to IMS_A 20 100 Trying IMS_A responds with a 100 Trying provisional response 21 INVITE IMS_A forwards INVITE to AS/IM_A 22 100 Trying AS/IM_A responds with a 100 Trying provisional response 23 INVITE AS/IM_A returns, possibly modified, INVITE to IMS_A 24 100 Trying IMS_A responds with a 100 Trying provisional response 25 INVITE IMS_A forwards INVITE to UE_A 26 100 Trying UE_A optionally responds with a 100 Trying provisional response 27 User A is informed of incoming file and accepts the transfer 28 200 OK UE_A responds INVITE with 200 OK response with SDP to indicate that the session has been accepted and inform B-side with specific data for a new MSRP connection set up 29 200 OK IMS_A forwards 200 OK response to AS/IM_A 30 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 31 200 OK IMS_A forwards 200 OK response to IBCF_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 37 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 32 200 OK IBCF_A forwards 200 OK response to IBCF_B 33 200 OK IBCF_B forwards 200 OK response to IMS_B 34 200 OK IMS_B forwards 200 OK response to AS/IM_B 35 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 36 200 OK IMS_B forwards 200 OK response to IBCF_B 37 200 OK IBCF_B forwards 200 OK response to IBCF_A 38 200 OK IBCF_A forwards 200 OK response to IMS_A 39 200 OK IMS_A forwards 200 OK response to UE_B 40 User B is informed that file transfer has been accepted by user B 41 ACK UE_B acknowledges the receipt of 200 OK for INVITE 42 ACK IMS_A forwards ACK to IBCF_A 43 ACK IBCF_A forwards ACK to IBCF_B 44 ACK IBCF_B forwards ACK to IMS_B 45 ACK IMS_B forwards ACK to AS/IM_B 46 ACK AS/IM_B returns, possibly modified, ACK to IMS_B 47 ACK IMS_B forwards ACK to IBCF_B 48 ACK IBCF_B forwards ACK to IBCF_A 49 ACK IBCF_A forwards ACK to IMS_A 50 ACK IMS_A forwards ACK to AS/IM_A 51 ACK AS/IM_A returns, possibly modified, ACK to IMS_A 52 ACK IMS_A forwards ACK to UE_A 53 File transfer starts (see clause 5.3.3 and use 5.4.1 test description) 54 File transfer completed (size checked) 55 BYE UE_B releases the file transfer session with BYE 56 BYE IMS_A forwards BYE to IBCF_A 57 BYE IBCF_A forwards BYE to IBCF_B 58 BYE IBCF_B forwards BYE to IMS_B 59 BYE IMS_B forwards BYE to AS/IM_B 60 BYE AS/IM_B returns, possibly modified, BYE to IMS_B 61 BYE IMS_B forwards BYE to IBCF_B 62 BYE IBCF_B forwards BYE to IBCF_A 63 BYE IBCF_A forwards BYE to IMS_A 64 BYE IMS_A forwards BYE to AS/IM_A 65 BYE AS/IM_A returns, possibly modified, BYE to IMS_A 66 BYE IMS_A forwards BYE to UE_A 67 User A is informed that file transfer completed 68 200 OK UE_A sends 200 OK for BYE 69 200 OK IMS_A forwards 200 OK response to AS/IM_A ETSI ETSI TS 102 901 V4.1.1 (2012-05) 38 Step Direction Message Comment U s e r A U E A A S/ I M A I M S A I B C F A I B C F B I M S B A S/ I M B U E B U s e r B 70 200 OK AS/IM_A returns, possibly modified, 200 OK response to IMS_A 71 200 OK IMS_A forwards 200 OK response to IBCF_A 72 200 OK IBCF_A forwards 200 OK response to IBCF_B 73 200 OK IBCF_B forwards 200 OK response to IMS_B 74 200 OK IMS_B forwards 200 OK response to AS/IM_B 75 200 OK AS/IM_B returns, possibly modified, 200 OK response to IMS_B 76 200 OK IMS_B forwards 200 OK response to IBCF_B 77 200 OK IBCF_B forwards 200 OK response to IBCF_A 78 200 OK IBCF_A forwards 200 OK response to IMS_A 79 200 OK IMS_A forwards 200 OK response to UE_B 80 User B is informed that file transfer completed 81 Users continue chatting 82 Continue UC_RCS_4_R (90A-115B)
|
8cd5b88eda99ed076f2e555b906d5fdc
|
102 901
|
4.4.3.4 1-to-many chat
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.