7.10 MTSI MT Voice call without preconditions and without SDP offer in MT INVITE / 5GS

34.229-53GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 5: Protocol conformance specification using 5G System (5GS)Release 16TSUser Equipment (UE) conformance specification

7.10.1 Test Purpose (TP)

(1)

with { UE being registered to IMS and configured to not use preconditions }

ensure that {

when { UE receives INVITE for voice call not containing an SDP offer, but indicating support for reliable provisional responses }

then { UE sends 183 Session Progress reliably and containing an SDP offer }

}

(2)

with { UE having sent 183 Session Progress }

ensure that {

when { UE receives PRACK for 183 Session Progress }

then { UE sends 200 OK for PRACK }

}

(3)

with { UE having sent 200 OK for PRACK }

ensure that {

when { UE is ready to start the call }

then { UE sends 180 Ringing followed by 200 OK for INVITE }

}

7.10.2 Conformance Requirements

The conformance requirements covered in the present test case are, unless otherwise stated, Rel-15 requirements.

[TS 24.229, annex U.3.1.4]:

Upon receiving an INVITE request not including the "precondition" option-tag in the Supported header field and not including the "precondition" option-tag in the Require header field, and the IP-CAN performs network-initiated resource reservation for the UE, the UE:

…

2) if the INVITE request does not contain an SDP offer and the INVITE request includes a Supported header field indicating support of reliable provisional responses:

a) shall generate an SDP offer;

b) if the local resources required at the terminating UE for the generated SDP offer are not available:

A) shall not alert the user; and

B) shall reliably send 183 (Session Progress) response to the INVITE request without waiting for resource reservation and without alerting the user. In the 183 (Session Progress) response, the UE shall include the generated SDP offer.

Upon successful reservation of local resources, if the precondition mechanism is not used by the terminating UE, the UE can send 180 (Ringing) response to the INVITE request and can alert the user.

7.10.3 Test description

7.10.3.1 Pre-test conditions

System Simulator:

– 1 NR Cell connected to 5GC, default parameters.

UE:

– The UE contains either ISIM and USIM applications or only USIM application on UICC.

– The UE is configured to register for IMS after switch on.

– The UE is configured to not use preconditions.

Preamble:

– UE is in state 1N-A (38.508-1[21]) and registered to IMS

7.10.3.2 Test procedure sequence

Table 7.10.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Steps 1-8 of generic procedure specified in Table 4.9.16.2.2-1 of TS 38.508-1 [21] are performed.

–

–

–

–

2

Step 1 of Annex A.5.2 happens

(Note: the INVITE message doesn’t include an SDP offer, but includes an option-tag indicating reliable provisional responses.)

<–

INVITE

–

–

3

Step 2 of Annex A.5.2 happens

(Note: this step is optional.)

–>

(Optional) 100 Trying

–

–

4

Check: Does the UE send 183 Session Progress reliably and containing an SDP offer?

(Step 3 of Annex A.5.2 happens)

–>

183 Session Progress

1

P

5

Step 4 of Annex A.5.2 happens

(Note: an SDP answer is included.)

<–

PRACK

–

–

6

Step 5 of Annex A.5.2 happens

(Check: does the UE send 200 OK for PRACK?)

–>

200 OK

2

P

6A-6C

Steps 10-12 of generic procedure specified in Table 4.9.16.2.2-1 of TS 38.508-1 [21] are performed.

–

–

–

–

7

Step 6 of Annex A.5.2 happens

(Check: does the UE send 180 Ringing followed by 200 OK for INVITE?)

–>

180 Ringing

3

P

8

Step 7 of Annex A.5.2 happens

(Conditional step: if UE sent 180 Ringing reliably, SS acknowledges reception of 180 Ringing)

<–

(Conditional) PRACK

–

–

9

Step 8 of Annex A.5.2 happens

(Conditional step: if UE sent 180 Ringing reliably, UE responds to PRACK)

–>

(Conditional) 200 OK

–

–

10

Step 9 of Annex A.5.2 happens

–>

200 OK

–

–

11

Step 10 of Annex A.5.2 happens

<–

ACK

–

–

7.10.3.3 Specific message contents

Table 7.10.3.3-1: INVITE (step 2, table 7.10.3.2-1)

Derivation Path: TS 34.229-1 [2], Table in subclause A.2.9, Conditions A1, A3, and A4

Header/param

Cond

Value/remark

Rel

Reference

Content-Type

Not present

Content-Length

0

Message-body

Not present

Table 7.10.3.3-2: 183 Session Progress with an SDP offer (step 4, table 7.10.3.2-1)

Derivation Path: TS 34.229-1 [2], Table in annex A.2.3, condition A2

Header/param

Cond

Value/remark

Rel

Reference

Message-body

NOTE: the following SDP offer is identical to the SDP offer shown in Annex A.4.2, Step 1, apart from video media: the UE may include addition video media description. These shall be accepted but not checked.

Session description:

v=0

o=(username) (sess-id) (sess-version) IN (addrtype) (unicast-address for UE)

s=(session name)

c=IN (addrtype) (connection-address for UE) [Note 1]

b=AS: (bandwidth-value)

Time description:

t= (start-time) (stop-time)

Media description:

m=audio (transport port) RTP/AVP (fmt)

c=IN (addrtype) (connection-address for UE) [Note 1]

b=AS: (bandwidth-value)

b=RS: (bandwidth-value) [Note 2]

b=RR: (bandwidth-value) [Note 2]

Attributes for media:

a=rtpmap: (payload type) EVS/16000 [Note 3, 9, 10, 12]

a=fmtp: (format) br=5.9-13.2; bw=nb-swb; max-red= (att-field) [Note 4, 5, 10, 12]

a=rtpmap: (payload type) EVS/16000 [Note 3, 9, 10, 13]

a=fmtp: (format) br=5.9-24.4; bw=nb-swb; max-red= (att-field) [Note 4, 5, 10, 13]

a=rtpmap: (payload type) EVS/16000 [Note 3, 9, 10, 14]

a=fmtp: (format) br=13.2; bw=swb; max-red= (att-field) [Note 4, 5, 10, 14]

a=rtpmap: (payload type) EVS/16000 [Note 3, 9, 10, 15]

a=fmtp: (format) br=9.6-13.2; bw=swb; max-red= (att-field) [Note 4, 5, 10, 15]

a=rtpmap: (payload type) EVS/16000 [Note 3, 9, 10, 16]

a=fmtp: (format) br=9.6-24.4; bw=swb; max-red= (att-field) [Note 4, 5, 10, 16]

a=rtpmap: (payload type) EVS/16000 [Note 3, 9, 11]

a=fmtp: (format) bw=nb-swb; max-red= (att-field) [Note 4, 5, 11]

a=rtpmap: (payload type) AMR-WB/16000 [Note 3, 9]

a=fmtp: (format) mode-change-capability=2; max-red= (att-field) [Note 4, 6]

a=rtpmap: (payload type) telephone-event/16000

a=fmtp: (format)

a=rtpmap: (payload type) AMR/8000 [Note 3, 9]

a=fmtp: (format) mode-change-capability=2; max-red= (att-field) [Note 4, 6]

a=rtpmap: (payload type) telephone-event/8000

a=fmtp: (format)

a=ecn-capable-rtp: leap ect=0 [Note 7]

a=rtcp-fb:* nack ecn [Note 7]

a=rtcp-xr:ecn-sum [Note 7]

a=rtcp-rsize [Note 7]

a=ptime:20

a=maxptime:240

Attributes for media security mechanism:

a=3ge2ae: requested [Note 8]

a=crypto:1 AES_CM_128_HMAC_SHA1_80inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|

1:4FEC_ORDER=FEC_SRTP" [Note 8]

Note 1: At least one "c=" field shall be present.

Note 2: The RR value shall be greater than 0. The RS value can be any value.

Note 3: The channel number shall be "/1" or omitted.

Note 4: The max-red values from 0 to 220 are allowed.

Note 5: The parameters dtx, dtx-recv and evs-mode-switch shall not be present.

Note 6: The parameters mode-set, mode-change-period, mode-change-neighbour, crc, robust-sorting and interleaving shall not be included.

Note 7: Attributes for ECN Capability may be present if the UE supports Explicit Congestion Notification.

Note 8: Attributes for media plane security are present if the use of end-to-access-edge security is supported by UE.

Note 9: The ordering of payload types shall be as listed, i.e., EVS before AMR-WB before AMR.

Note 10: The EVS payload type shall carry at least one of the five EVS configurations according to NG.114 [31] clause 3.2.2.3. In addition, if there is no further EVS payload type according to the criteria of Note 11, the following rules shall be checked:
IF the first EVS payload type is configuration B0 or B1 THEN
there shall be a second EVS payload type with configuration A1
ELSE IF the first EVS payload type is configuration B2 THEN

there shall be a second EVS payload type with configuration A2
(NOTE: if the first EVS payload type is configuration A1 or A2 there does not need to be any further EVS payload type)

Note 11: Further EVS payload type according to NG.114 [31] clause 3.2.2.3 with bandwidth up to super-wideband, no br parameter and no mode-set parameter.

Note 12: EVS payload type with EVS Configuration A1 (NG.114 [31] clause 3.2.2.3).

Note 13: EVS payload type with EVS Configuration A2 (NG.114 [31] clause 3.2.2.3).

Note 14: EVS payload type with EVS Configuration B0 (NG.114 [31] clause 3.2.2.3).

Note 15: EVS payload type with EVS Configuration B1 (NG.114 [31] clause 3.2.2.3).

Note 16: EVS payload type with EVS Configuration B2 (NG.114 [31] clause 3.2.2.3).

TS 24.229 [7]

Table 7.10.3.3-3: PRACK with an SDP answer (step 5, table 7.10.3.2-1)

Derivation Path: TS 34.229-1 [2], Table in annex A.2.4, condition A3

Header/param

Cond

Value/remark

Rel

Reference

Message-body

NOTE: the following SDP offer is identical to the SDP offer shown in Annex A.4.2, Step 3, apart from the video media: if the UE included such lines, SS copies the video media description and changes the port number to zero.

Session description:

v=0

o=- 1111111111 1111111111 IN (addrtype) (unicast-address for SS)

s=-

c=IN (addrtype) (connection-address for SS)

b=AS:65

Time description:

t=0 0

Media description:

m=audio (transport port) RTP/AVP (fmt) [Note 1, 2]

b=AS:65

b=RS: (bandwidth-value) [Note 3]

b=RR: (bandwidth-value) [Note 3]

Attributes for media:

a=rtpmap: (payload type) EVS/16000/1 [Note 1, 8]

a=fmtp: (format) br=13.2; bw=swb; mode-set=0,1,2; max-red=220 [Note 8]

a=rtpmap: (payload type) EVS/16000/1 [Note 1, 9]

a=fmtp: (format) br=5.9-13.2; bw=nb-swb; mode-set=0,1,2; max-red=220 [Note 9]

a=ecn-capable-rtp: leap ect=0 [Note 6]

a=rtcp-fb:* nack ecn [Note 6]

a=rtcp-xr:ecn-sum [Note 6]

a=ptime:20

a=maxptime:240

Attributes for media security mechanism:

a=3ge2ae: requested [Note 7]

a=crypto:1 AES_CM_128_HMAC_SHA1_80inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR|2^20|1:4 [Note 7]

Note 1: The values for fmt, payload type and format are copied from step 3.

Note 2: Transport port is the port number of the SS (see RFC 3264 clause 6).

Note 3: The bandwidth-value is copied from step 4.

Note 4: All present br, br-send and br-recv parameter=value pairs are copied from step 4.

Note 5: bw, bw-send and bw-recv parameter are copied from bw at step 4.

Note 6: Attributes for ECN Capability are present if the UE supports Explicit Congestion Notification.

Note 7: Attributes for media plane security are present if the use of end-to-access-edge security is supported by UE.

Note 8: This EVS configuration is sent if UE sent it as the first of its EVS configurations in previous SDP offer.

Note 9: This EVS configuration is sent if UE did not send "br=13.2; bw=swb" as the first of its EVS configurations in previous SDP offer.

TS 24.229 [7]