20 Customized Alerting Tones (CAT)
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
20.1 Mobile Originating CAT – Forking Model
20.1.1 Definition
Test to verify that the UE support Customized Alerting Tones according to the forking model. This process is described in 3GPP TS 24.182 [127].
20.1.2 Conformance requirement
[TS 24.182, clause 4.5.5.1.1]:
The UE shall follow the procedures specified in 3GPP TS 24.229 for session initiation and termination.
[TS 24.628, clause 4.7.2.1]:
Procedures according to 3GPP TS 24.229 shall apply.
Certain services require the usage of the Alert-Info header field, Call-Info header field and Error-Info header field according to procedures specified by IETF RFC 3261.
If the UE detects that in-band information is received from the network as early media, the in-band information received from the network shall override locally generated communication progress information.
The UE shall not generate the locally generated communication progress information if an early dialog exists where the last received P-Early-Media header field as described in IETF RFC 5009 contains "sendrecv" or "sendonly".
NOTE: if an early dialog exists where a SIP 18x response to the SIP INVITE request other than 183 (Session Progress) response was received, no early dialog exists where the last received P-Early-Media header field as described in IETF RFC 5009 contained "sendrecv" or "sendonly" and in-band information is not received from the network, then the UE is expected to render the locally generated communication progress information.
If the UE supports the P-Early-Media header field as defined in IETF RFC 5009, and a P-Early-Media header field has been received, then the UE shall send any available user generated media, e.g. speech or DTMF, on media stream(s) associated with the early dialog for which the most recent P-Early-Media header field, as described in IETF RFC 5009, contained a "sendrecv" or a "recvonly" header field value. If there is more than one such early dialog, the UE shall use the early dialog where the P-Early-Media header field was most recently received.
If the UE receives a re-INVITE request containing no SDP offer, the UE shall send a 200 (OK) response containing an SDP offer according to 3GPP TS 24.229 indicating the directionality used by UE as
– "sendonly" if the re-INVITE request is received on a dialog where the associated communication session has been put on hold by the user; and
– "sendrecv" otherwise.
Reference(s)
3GPP TS 24.182 [127], clause 4.5.5.1.1 and 3GPP TS 24.628 [128], clause 4.7.2.1.
20.1.3 Test purpose
1) To verify that when initiating MO call, with Customized Alerting Tones according to the forking model, the UE performs correct exchange of SIP protocol signalling messages for setting up the session; and
2) To verify that within SIP signalling the UE performs the correct exchange of SDP messages for negotiating early media and indicating preconditions for resource reservation (as described by 3GPP TS 24.229 [10], clause 6.1).
20.1.4 Method of test
Initial conditions
UE contains either ISIM and USIM applications or only USIM application on UICC. UE has discovered P-CSCF, and registered to IMS services.
SS is configured with the shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE. SS has performed AKAv1-MD5 authentication with the UE and accepted the registration.
Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)
1-13) UE executes the procedures described in TS 36.508 [94] table 4.5A.21.3-1 steps 1 to14.
14) SS responds to the INVITE sent by the UE in step 2 with a 200 OK to create dialog 1.
15) UE sends ACK to acknowledge receipt of the 200 OK for INVITE.
16) UE is triggered by MMI to release the call
17) UE sends a BYE request to the SS in order to release the call.
18) SS responds to the BYE request with a valid 200 OK response.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1-8 |
Perform steps 1 to 8 of the procedure detailed in C.21 |
Setup dialog 1 |
||
|
9-13 |
Perform steps 4 to 8 of the procedure detailed in C.21 |
Setup dialog 2 (CAT) |
||
|
14 |
🡨 |
200 OK |
The SS sends 200 OK for INVITE sent in step 2 above (dialog 1) |
|
|
15 |
🡪 |
ACK |
The UE sends ACK for the 200 OK |
|
|
16 |
The UE is triggered by MMI to release the call |
|||
|
17 |
🡪 |
BYE |
The UE releases the call with BYE |
|
|
18 |
🡨 |
200 OK |
The SS sends 200 OK for BYE |
|
NOTE: The default messages contents in annex A are used with condition “IMS security” or “GIBA” when applicable
Specific Message Contents
Steps 1 – 8 and 9-13 as specified in annex C.21 with the exceptions detailed below
INVITE (Step 2)
Use the default message “INVITE” in step 2 of annex C.21
183 Session Progress (Step 9)
Use the default message "183 Session Progress" in step 4 of annex C.21 with the following exceptions:
|
Header/param |
Value/Remark |
|
To |
|
|
tag |
Any value different from what is used in steps 1-8 |
|
Contact |
|
|
addr-spec |
<sip:cat-as.home1.net;+g.3gpp.icsi_ref="urn%3Aurn-7%3gpp-service.ims.icsi.mmtel"> |
|
P-Early-Media |
|
|
em-param |
sendonly |
|
Message-body |
Session description: – v=0 – o=- 1111111112 1111111111 IN (addrtype) (unicast-address for SS for early-media) – s=- – c=IN (addrtype) (connection-address for SS for early-media) – b=AS:37 Attributes for preconditions: – a=curr:qos local sendrecv – a=curr:qos remote none – a=des:qos mandatory local sendrecv – a=des:qos mandatory remote sendrecv – a=conf:qos remote sendrecv Other attributes: – a=content:g.3gpp.cat |
PRACK (Step 10)
Use the default message “PRACK” in step 5 of annex C.21 with the following exceptions:
|
Header/param |
Value/Remark |
|
Message-body |
Header optional Contents if present is copied from step 5 of annex C.21 with the following exceptions: Attributes for preconditions: – a=curr:qos local sendrecv – a=curr:qos remote sendrecv – a=des:qos mandatory local sendrecv – a=des:qos optional remote sendrecv or a=des:qos mandatory remote sendrecv |
200 OK for PRACK (Step 11)
Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1 with the following exceptions:
|
Header/param |
Value/remark |
|
To |
|
|
tag |
Same value as used in step 9 |
|
Content-Type |
Header optional Contents if present: |
|
media-type |
application/sdp |
|
Content-Length |
Contents if header Content-Type is present: |
|
Value |
length of message-body |
|
Message-body |
Header present if PRACK in step 10 contained a SDP. Contents if present: SDP body of the 200 OK response copied from the received PRACK and modified as follows: – IP address on "c=" lines and transport port on "m=" lines changed to indicate to which IP address and port the UE should start sending the media (same as used in step 9 above); – "o=" line identical to previous SDP sent by SS except that sess-version is incremented. Attributes for preconditions:
|
200 OK for UPDATE (Step 13)
Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1 with the following exceptions:
|
Header/param |
Value/remark |
|
To |
|
|
tag |
Same value as used in step 9 |
|
Content-Type |
Header optional Contents if present: |
|
media-type |
application/sdp |
|
Content-Length |
Contents if header Content-Type is present: |
|
Value |
length of message-body |
|
Message-body |
SDP body of the 200 response copied from the received UPDATE and modified as follows: – IP address on "c=" lines and transport port on "m=" lines changed to indicate to which IP address and port the UE should start sending the media (same as used in step 9 above); – “o=” line identical to previous SDP sent by SS except that sess-version is incremented. Attributes for preconditions:
|
200 OK (Step 14)
Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1 with the following exceptions:
|
Header/param |
Value/remark |
|
Content-Type |
Header optional Contents if present: |
|
media-type |
application/sdp |
|
Content-Length |
Contents if header Content-Type is present: |
|
Value |
length of message-body |
|
Message-body |
Header present if Prack (step 5) contained SDP. Contents if present: SDP body of the 200 OK response copied from the received PRACK and modified as follows: – IP address on "c=" lines and transport port on "m=" lines changed to indicate to which IP address and port the UE should start sending the media; – "o=" line identical to previous SDP sent by SS except that sess-version is incremented. Attributes for preconditions:
|
BYE (Step 17)
Use the default message “BYE” in annex A.2.8.
200 OK for BYE (Step 18)
Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1.
20.1.5 Test requirements
SS must check that the if the UE uses full IMS security, it sends all the requests over the security associations set up during registration, in accordance to 3GPP TS 24.229 [10], clause 5.1.1.5.1.
The UE shall send requests and responses as described in clause 20.1.4.