8.6 Terminating Identification Restriction / Signalling / 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

8.6.1 Test Purpose (TP)

(1)

with { UE being registered to IMS and TIR in temporary mode being activated }

ensure that {

when { UE receives INVITE for voice call }

then { UE includes the Privacy header in its 183 Session Progress response and in its 180 Ringing response and in its final 200 OK for INVITE response }

}

8.6.2 Conformance Requirements

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

[TS 24.608 clause 4.2.1]:

The Terminating Identification Restriction (TIR) is a service offered to the terminating party which enables the terminating party to prevent presentation of the terminating identity information to originating party.

[TS 24.608 clause 4.5.2.12]:

The destination UE, if the terminating user wishes to override the default setting of "presentation not restricted" of the TIR service in temporary mode, shall include a Privacy header with privacy type of "id" in any non-100 responses it sends upon receipt of a SIP request.

….NOTE: It is assumed that TIR subscribers support IETF RFC 3325.

8.6.3 Test description

8.6.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 use preconditions.

– The UE is configured to use Terminating Identification Restriction in temporary mode.

Preamble:

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

8.6.3.2 Test procedure sequence

Table 8.6.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-8

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

–

–

–

–

9-10

Steps 1-2 of Annex A.5.1 are performed.

–

–

–

–

11

Check: Does the UE send 183 Session Progress response reliably, including a Privacy header with privacy type of "id"?

(Steps 3 of Annex A.5.1))

–>

183 Session Progress

1

P

12-13

Steps 4-5 of Annex A.5.1 are performed.

–

–

–

–

13A-13C

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

–

–

–

–

14-15

Step 6-7 of Annex A.5.1 are performed

–

–

–

–

16

Check: Does the UE send 180 Ringing including a Privacy header with privacy type of "id"?

(Steps 8 of Annex A.5.1)

–>

180 Ringing

1

P

17-19

Steps 9-10A of Annex A.5.1 are performed.

–

–

–

–

20

Check: Does the UE send 200 OK including a Privacy header with privacy type of "id"?

(Steps 11 of Annex A.5.1)

–>

200 OK

1

P

21

Steps 12 of Annex A.5.1 is performed.

<–

ACK

–

–

8.6.3.3 Specific message contents

Table 8.6.3.3-1: 183 Session Progress (step 11, Table 8.6.3.2-1)

Derivation Path: Step 3 of A.5.1

Header/param

Cond

Value/remark

Rel

Reference

Privacy

id

RFC 3323[50] RFC 3325[51]

Table 8.6.3.3-2: 180 Ringing (step 16, Table 8.6.3.2-1)

Derivation Path: Step 8 of A.5.1

Header/param

Cond

Value/remark

Rel

Reference

Privacy

id

RFC 3323[50] RFC 3325[51]

Table 8.6.3.3-3: 200 OK (step 11, Table 8.6.3.2-1)

Derivation Path: Step 11 of A.5.1

Header/param

Cond

Value/remark

Rel

Reference

Privacy

id

RFC 3323[50] RFC 3325[51]