12.22 MT MTSI Video call

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

12.22.1 Definition

Test to verify that the UE correctly performs IMS mobile terminated video call setup when using IMS Multimedia Telephony. This process is described in 3GPP TS 24.229 [10], clauses 5.1.3 and 6.1, TS 24.173 [65] and TS 26.114 [66].

12.22.2 Conformance requirement

[TS 24.229, clause 5.1.4.1]

If an initial INVITE request is received the terminating UE shall check whether the terminating UE requires local resource reservation.

NOTE 1: The terminating UE can decide if local resource reservation is required based on e.g. application requirements, current access network capabilities, local configuration, etc.

If local resource reservation is required at the terminating UE and the terminating UE supports the precondition mechanism, and:

a) the received INVITE request includes the "precondition" option-tag in the Supported header or Require header, the terminating UE shall make use of the precondition mechanism and shall indicate a Require header with the "precondition" option-tag in any response or subsequent request it sends towards to the originating UE; or

…

If local resource reservation is not required by the terminating UE and the terminating UE supports the precondition mechanism and:

a) the received INVITE request includes the "precondition" option-tag in the Supported header and:

– the required resources at the originating UE are not reserved, the terminating UE shall use the precondition mechanism; or

[TS 24.229, clause 6.1.3]

If the terminating UE had previously set one or more media streams to inactive mode and the QoS resources for those media streams are now ready, it shall set the media streams to active mode by applying the procedures described in RFC 4566 with respect to setting the direction of media streams.

…

Upon sending a SDP answer to an SDP offer, with the SDP answer including one or more media streams for which the originating side did indicate its local preconditions as not met, if the precondition mechanism is supported by the terminating UE, the terminating UE shall indicate its local preconditions and request the confirmation for the result of the resource reservation at the originating end point.

[TS 26.114 Rel-8, clause 5.2.2]

MTSI clients in terminals offering video communication shall support:

– ITU-T Recommendation H.263 [22] Profile 0 Level 45.

In addition they should support:

– ITU-T Recommendation H.263 [22] Profile 3 Level 45;

– MPEG-4 (Part 2) Visual [23] Simple Profile Level 3with the following constraints:

– Number of Visual Objects supported shall be limited to 1.

– The maximum frame rate shall be 30 frames per second.

– The maximum f_code shall be 2.

– The intra_dc_vlc_threshold shall be 0.

– The maximum horizontal luminance pixel resolution shall be 352 pels/line.

– The maximum vertical luminance pixel resolution shall be 288 pels/VOP.

– If AC prediction is used, the following restriction applies: QP value shall not be changed within a VOP (or within a video packet if video packets are used in a VOP). If AC prediction is not used, there are no restrictions to changing QP value.

– ITU-T Recommendation H.264 / MPEG-4 (Part 10) AVC [24] Baseline Profile Level 1.1 with constraint_set1_flag=1 and without requirements on output timing conformance (annex C of [24]). Each sequence parameter set of H.264 (AVC) shall contain the vui_parameters syntax structure including the num_reorder_frames syntax element set equal to 0.

[TS 26.114 Rel-10, clause 5.2.2]

MTSI clients in terminals offering video communication shall support:

– ITU-T Recommendation H.264 / MPEG-4 (Part 10) AVC [24] Constrained Baseline Profile (CBP) Level 1.2.

In addition they should support:

– ITU-T Recommendation H.264 / MPEG-4 (Part 10) AVC [24] Constrained Baseline Profile Level 3.1.

In addition they may support:

– ITU-T Recommendation H.263 [22] Profile 0 Level 45.

[TS 26.114, clause 6.2.1a3]:

An invited MTSI client should accept using AVPF whenever supported. If AVPF has been offered using SDPCapNeg and is to be used in the session then the MTSI client shall:

– select one configuration out of the potential configurations defined in the SDP offer for using AVPF;

– indicate in the media (m=) line of the SDP answer that the profile to use is AVPF; and

– indicate the selected configuration for using AVPF in the attribute for actual configurations ‘acfg’.

If AVP is to be used then the MTSI shall not indicate any SDPCapNeg attributes for using AVPF in the SDP answer.

[TS 26.114, clause 6.2.3]:

If video is used in a session, the session setup shall determine the bandwidth, RTP profile, video codec, profile and level. The "imageattr" attribute as specified in [76] should be supported.

An MTSI client shall offer AVPF for all media streams containing video. RTP profile negotiation shall be done as described in clause 6.2.1a.

Examples of SDP offers and answers for video can be found in clause A.4.

NOTE: For H.264 / MPEG-4 (Part 10) AVC, the optional max-rcmd-nalu-size receiver-capability parameter of RFC 3984 [25] should be set to the smaller of the MTU size (if known) minus header size or 1 400 bytes (otherwise).

[TS 26.114, clause 6.2.5]

The SDP shall include bandwidth information for each media stream and also for the session in total. The bandwidth information for each media stream and for the session is defined by the Application Specific (AS) bandwidth modifier as defined in RFC 4566.

[TS 26.114, clause 7.3.1]

The bandwidth for RTCP traffic shall be described using the "RS" and "RR" SDP bandwidth modifiers at media level, as specified by RFC 3556.

Reference(s)

3GPP TS 24.229 [10] clauses 5.1.4.1, 6.1.3, TS 26.114 [66] clause 5.2.2, 6.2.1a3,6.2.3, 6.2.5 and 7.3.1.

12.22.3 Test purpose

1) To verify that, when initiating MT MTSI video call and SS needs to reserve resources, the UE performs correct exchange of SIP protocol signalling messages for setting up the session.

2) To verify that within SIP signalling the UE performs the correct exchange of SIP header and parameter contents.

3) To verify that within SIP signalling the UE performs the correct exchange of SDP contents.

4) To verify that the UE is able to release the call.

12.22.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, by executing the generic test procedure in Annex C.2 or C.2a (GIBA only) up to the last step.

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 equipp5ed into the UE. SS has performed AKAv1-MD5 authentication with the UE and accepted the registration (IMS security).

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1-27) UE executes the procedures described in TS 36.508 [94] table 4.5A.9.3-1, steps 1 to 27.

Expected sequence

NOTE: Only the IMS procedure relevant to the test purpose is described below.

Step	Direction		Message	Comment
	UE	SS
1-15			Steps defined in annex C.26	MTSI MT video call. Referred from 36.508 [94] table 4.5A.9.3-1 for a UE with E-UTRA support.

NOTE: The default messages contents in annex A are used with condition “IMS security“ or “GIBA” when applicable

Specific Message Content

None.

12.22.5 Test requirements

The UE shall send requests and responses as described in clause 12.22.4