8.3 Originating 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.3.1 Test Purpose (TP)

(1)

with { UE is registered to IMS and OIR in temporary mode is activated }

ensure that {

when { UE is made to initiate a voice call }

then { UE sends INVITE with "Anonymous" in the From header }

}

8.3.2 Conformance Requirements

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

[TS 24.607 clause 4.5.2.1]:

If the originating user wishes to override the default setting of "presentation not restricted" of the OIR service in temporary mode:

– The originating UE shall include an "anonymous" From header field. The convention for configuring an anonymous From header field described in IETF RFC 3323 [6] should be followed; i.e. From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag= xxxxxxx.

– If only the P‑Asserted‑Identity needs to be restricted the originating UE shall include a Privacy header field [6] set to "id" in accordance with IETF RFC 3325 [7].

– If all headers containing private information that the UE cannot anonymize itself need to be restricted, the originating UE shall include a Privacy header field set to "header" in accordance with IETF RFC 3323 [6].

NOTE 2: The Privacy header field value "header" does not apply to the identity in the From header field.

8.3.3 Test description

8.3.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 Telephony Originating Identification Restriction in temporary mode

Preamble:

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

8.3.3.2 Test procedure sequence

Table 8.3.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an IMS speech call with originating identification restriction.

–

–

–

–

2-7

Steps 2-7 of generic procedure specified in Table 4.9.15.2.2-1 of TS 38.508-1 [21] are performed.

–

–

–

–

–

EXCEPTION: In parallel with Step 8, parallel behaviour defined in table 8.3.3.2-2 takes place

–

–

–

–

8

Check: Does the UE sends INVITE with first SDP offer with including an "Anonymous" From header field?

–>

INVITE

1

P

9-12

Steps 2-5 of Annex A.4.1a are perfomed

–

–

–

–

12A

Step 10 of generic procedure specified in Table 4.9.15.2.2-1 of TS 38.508-1 [21] is performed.

–

–

–

–

–

EXCEPTION: In parallel to steps 12B and 12C below, step 13 occurs.

–

–

–

–

12B-12C

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

–

–

–

–

13-19

Steps 6-12 of Annex A.4.1a happen.

–

–

–

–

20

Make the UE release the IMS speech call.

–

–

–

–

21-22

Steps 1-2 defined in annex A.7 are performed to MO release the IMS speech call.

–

–

–

–

Table 8.3.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

8.3.3.3 Specific message contents

Table 8.3.3.3-1: INVITE (step 8, Table 8.3.3.2-1)

Derivation Path: Step 1 of A.4.1a

Header/param

Cond

Value/remark

Rel

Reference

From

addr-spec

“Anonymous" <sip:anonymous@anonymous.invalid>

Privacy

id or header (mutually exclusive)

RFC 3323[50] RFC 3325[51]