6.2.24 On-network / Private call / Remotely initiated private call / Client Originated (CO)

36.579-23GPPMission Critical (MC) services over LTEPart 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specificationRelease 15TS

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

6.2.24.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client) registered and authorized for MCPTT Service, including authorized to initiate Remotely initiated private call and to participate in private calls }

ensure that {

when { UE (MCPTT User) requests the establishment of a remotely initiated private call to a third party }

then { UE (MCPTT Client) sends a SIP MESSAGE message requesting the establishment of a remotely initiated private call }

}

(2)

with { UE (MCPTT Client) registered and authorized for MCPTT Service, including authorized to initiate Remotely initiated private call and to participate in private calls, and, having requested the establishment of a remotely initiated private call }

ensure that {

when { UE (MCPTT User) receives a SIP MESSAGE message indicating the outcome of the requested establishment of a remotely initiated private call }

then { UE (MCPTT Client) sends a SIP OK message to confirm the reception of the SIP MESSAGE }

}

6.2.24.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.379 clauses 11.1.7.2.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.379, clause 11.1.7.2.1]

Upon receiving a request from the MCPTT to send a remotely initiated private call request to the remote MCPTT user to originate a private call to an identified MCPTT user, the MCPTT client:

1) if:

a) the <allow-request-remote-init-private-call> element of the <ruleset> element is not present in the requesting MCPTT user’s MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";

…

2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:

a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;

b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];

c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];

d) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:

i) the <mcptt-called-party-id> element set to the MCPTT ID of the identified MCPTT user of the remotely initiated private call; and

ii) an <anyExt> element containing:

A) the <request-type> element set to a value of "remotely-initiated-private-call-request";

B) the <notify-remote-user> element set to a value of "true" if the requesting MCPTT user has indicated that the remote MCPTT user be notified of the remotely initiated private call request; and

C) the <notify-remote-user> element set to a value of "false" if the requesting MCPTT user has indicated that the remote MCPTT user not be notified of the remotely initiated private call request;

e) shall insert in the SIP MESSAGE request a MIME resource-lists body with the MCPTT ID of the remote MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; and

f) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and

3) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].

…

Upon receiving a "SIP MESSAGE request for remotely initiated private call response for terminating client", the MCPTT client:

1) shall determine the success or failure of the sent remotely initiated private call request from the value of the <remotely-initiated-call-outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and

2) should indicate to the requesting MCPTT user the success or failure of the sent remotely initiated private call request.

6.2.24.3 Test description

6.2.24.3.1 Pre-test conditions

System Simulator:

– SS (MCPTT server)

– For the underlining "transport bearer" over which the SS and the UE will communicate Parameters are set to the default parameters for the basic E-UTRA Single cell network scenarios, as defined in TS 36.508 [24] clause 4.4. The simulated Cell 1 shall belong to PLMN1 (the PLMN specified for MCPTT operation in the MCPTT configuration document).

IUT:

– UE (MCPTT client)

– The test USIM set as defined in TS 36.579-1 [2], subclause 5.5.10 is inserted.

Preamble:

– The UE has performed the Generic Test Procedure for MCPTT UE registration as specified in TS 36.579-1 [2], subclause 5.4.2.

– The MCPTT User performs the procedure for MCPTT Authorization/Configuration and Key Generation as specified in TS 36.579-1 [2], subclause 5.3.2.

– The MCPTT User is authorized to initiate Remotely initiated private call: the <allow-request-remote-init-private-call> element of the <ruleset> element is present in the MCPTT user profile document and is set to "true".

– The MCPTT User is authorized to participate in private calls: the <allow-private-call-participation> element of the <ruleset> element is present in the MCPTT user profile document and is set to "true".

– UE States at the end of the preamble

– The UE is in E-UTRA Registered, Idle Mode state.

– The MCPTT Client Application has been activated and User has registered-in as the MCPTT User with the Server as active user at the Client.

6.2.24.3.2 Test procedure sequence

Table 6.2.24.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Make the UE (MCPTT User) request the establishment of an MCPTT remotely initiated private call to a third party (i.e. not to itself). (NOTE 1)	–	–	–	–
2-4	Check: Does the UE (MCPTT Client) correctly perform steps 1a1 to 3 of procedure for MCX SIP MESSAGE CO as described in TS 36.579-1 [2] Table 5.3.32.3-1 to request the establishment of an MCPTT remotely initiated private call?	–	–	1	P
5	Wait for 3 sec (an arbitrary value to simulate the time needed for the establishment of the remote private call).	–	–	–	–
6-8	Check: Are steps 2 to 4 of the procedure for MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 confirming the progress of the MCPTT remotely initiated private call, correctly performed? (NOTE 2)	–	–	2	P
NOTE 1: This is expected to be done via a suitable implementation dependent MMI. NOTE 2: The UE is expected to determine the success or failure of the sent remotely initiated private call request. Following this the UE client may indicate to the requesting MCPTT user the success or failure of the sent remotely initiated private call request. This is not verified because the indication to the User is not mandated.

6.2.24.3.3 Specific message contents

Table 6.2.24.3.3-1: SIP MESSAGE from the UE (Step 3, Table 6.2.24.3.2-1;
Step 2, TS 36.579-1 [2], Table 5.3.32.3-1)

Derivation Path: TS 36.579-1 [2], table 5.5.2.7.1-1 condition RESOURCE_LISTS
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCPTT-Info
MIME-part-body	As described in Table 6.2.24.3.3-2

Table 6.2.24.3.3-2: MCPTT-Info in SIP MESSAGE (Table 6.2.24.3.3-1)

Derivation Path: TS 36.579-1 [2], table 5.5.3.2.1-1, condition PRIVATE-CALL
Information Element	Value/remark	Comment	Reference	Condition
mcpttinfo
mcptt-Params
mcptt-called-party-id	Encrypted <mcptt-called-party-id> with mcpttURI set to px_MCPTT_ID_User_C	Encrypted according to NOTE 2 of Table 5.5.3.2.1-1 in TS 36.579-1 [2]
anyExt		The anyExt field may contain other values – these need not be checked
request-type	"remotely-initiated-private-call-request"
notify-remote-user	Any allowed value

Table 6.2.24.3.3-3: SIP MESSAGE from the SS (Step 6, Table 6.2.24.3.3-1;
step 2, TS 36.579-1 [2], Table 5.3.33.3-1)

Derivation Path: TS 36.579-1 [2], table 5.5.2.7.2-1 condition ACCEPT-CONTACT-WITH-MEDIA-FEATURE-TAG
Information Element	Value/remark	Comment	Reference	Condition
Message-body
MIME body part		MCPTT-Info
MIME-part-body	MCPTT-Info as described in Table 6.2.24.3.3-4

Table 6.2.24.3.3-4: MCPTT-Info in SIP MESSAGE (Table 6.2.24.3.3-3)

Derivation Path: TS 36.579-1 [2], table 5.5.3.2.2-1, condition PRIVATE-CALL
Information Element	Value/remark	Comment	Reference	Condition
mcpttinfo
mcptt-Params
mcptt-called-party-id	Encrypted <mcptt-called-party-id> with mcpttURI set to px_MCPTT_ID_User_C	Encrypted according to NOTE 1 of Table 5.5.3.2.2-1 in TS 36.579-1 [2]
anyExt
response-type	"remotely-initiated-private-call-response"
remotely-initiated-call-outcome	"success"