C.30b Generic test procedure for UE Initiated Deregistration – Fixed Broadband Access to EPC
34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification
The generic test procedure:
IMS deregistration is initiated on the UE. SS waits for the UE sending a REGISTER request, in accordance with 3GPP TS 24.229 [10], clause 5.1.1.6.
Expected sequence:
Same as described in Annex C.30
Specific message contents
The default messages contents in Annex C.30 are used with condition “SIP Digest without TLS for Fixed Broadband Access” when applicable
C.31 Generic test procedure for media re-establishment after unsuccessful SRVCC handover – EPS
Test procedure:
1) UE sends a re-INVITE request to the SS.
2) SS responds to the INVITE request with a 100 Trying response.
3) SS responds to the INVITE request with a 200 OK.
4) SS waits for the UE to send an ACK to acknowledge receipt of the 200 OK for INVITE.
Expected sequence:
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
🡪 |
INVITE |
UE sends INVITE with audio re-established. |
|
|
2 |
🡨 |
100 Trying |
SS sends a 100 Trying provisional response. |
|
|
3 |
🡨 |
200 OK |
SS responds to INVITE with a 200 OK final response. |
|
|
4 |
🡪 |
ACK |
UE acknowledges the receipt of 200 OK for INVITE. |
|
Specific Message Contents
INVITE (Step 1)
Use the default message “INVITE for MO Call” in annex A.2.1 with condition A5 (re-INVITE within a dialog) and the following exceptions:
|
Header/param |
Value/Remark |
Rel |
|
Request-Line |
||
|
Method |
INVITE |
|
|
Request-URI |
Same value as the URI from the Contact header of the original INVITE request as sent by SS |
|
|
SIP-Version |
SIP/2.0 |
|
|
Reason |
Reason header field with Protocol "SIP" and reason parameter "cause" with value "487" |
|
|
reason-text set to "handover cancelled" or “failure to transition to CS domain” |
Rel-10 |
|
|
Message Body |
The following SDP types and values. Session description:
Time description:
Media description:
Attributes for media:
Note 1: At least one "c=" field shall be present. Note 2: "o=" line identical to previous SDP sent by UE, except that sess-version is incremented by one if the SDP is not identical to the previous SDP sent by the UE |
200 OK (Step 3)
Use the default message “200 OK” in annex A.3.1 with the following exceptions:
|
Header/param |
Value/Remark |
|
Contact addr-spec |
Same value as the URI from the Contact header of the original INVITE request as sent by SS |
|
Content-Type |
|
|
media-type |
application/sdp |
|
Content-Length |
|
|
value |
length of message-body |
|
Message Body |
The following SDP types and values. Session description:
Time description:
Media description:
Attributes for media:
a=fmtp:(format) mode-change-capability=2; max-red=220 [Note 1] Attributes for preconditions:
Note 1: The value for fmt, payload type (AMR) and format is copied from step 1 Note 2: The bandwidth-value is copied from step 1. Note 3: sess-version incremented by one if SDP changed compared to last SDP sent by SS. |
ACK (Step 4)
Use the default message "ACK" in annex A.2.7 with condition A5 and the following exceptions:
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
ACK |
|||
|
Request-URI |
Same value as the URI from the Contact header of the original INVITE request as sent by SS |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
To addr-spec tag |
Same value as used in the INVITE of step 1 Same value as used in the INIVTE of step 1 |
RFC 3261 [15] |
NOTE 1: when A.2.7 refers to "INVITE", the re-INVITE of step 1 is meant.