6.2.26 On-network / Private call / Remotely initiated private call / Pre-established session / Client Terminated (CT)

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

6.2.26.1 Test Purpose (TP)

(1)

with { UE (MCPTT Client) registered and authorized for MCPTT Service, including authorized to initiate private calls, and, according to local policy pre-established sessions are to be used for remotely initiated private calls }

ensure that {

when { UE (MCPTT Client) receives a request for establishment of an MCPTT remotely initiated private call with the MCPTT ID of the identified MCPTT user of the remotely initiated private call set to the ID of the MCPTT user requesting the call initiation, and, a pre-established session to this User available, and, the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false" }

then { UE (MCPTT Client) initiates private call establishment to the requesting User using the pre-established session, and, does not notify the user that a remotely initiated private call request to call the identified MCPTT user has been received, and, does not give any indication to the remote MCPTT user that the remotely initiated private call origination is in progress, and, does not sent SIP MESSAGE back to the MCPTT user requesting the call initiation }

}

(2)

with { UE (MCPTT Client) registered and authorized for MCPTT Service, including authorized to initiate private calls, and, according to local policy pre-established sessions are to be used for remotely initiated private calls }

ensure that {

when { UE (MCPTT Client) receives a request for establishment of an MCPTT remotely initiated private call with the MCPTT ID of the identified MCPTT user of the remotely initiated private call set to ID different to the ID of the MCPTT user requesting the call initiation, and, a pre-established session to this User available }

then { UE (MCPTT Client) initiates private call establishment to the requested identified MCPTT user using the pre-established session, and, sends SIP MESSAGE back to the MCPTT user requesting the call initiation to confirm the private call initiation }

}

6.2.26.2 Conformance requirements

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

[TS 24.379, clause 11.1.7.2.2]

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

…

2) shall extract the MCPTT ID of the identified MCPTT user from the <mcptt-called-party-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request;

…

4) if according to local policy pre-established sessions are to be used for remotely initiated private calls and a pre-established session is available, shall invoke the procedures of clause 11.1.1.2.2.1 to originate an MCPTT private call to the identified MCPTT user with the following clarifications:

a) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false":

i) shall not indicate to the remote MCPTT user that a remotely initiated private call request to call the identified MCPTT user has been received; and

ii) shall not give any indication to the remote MCPTT user that the remotely initiated private call origination is in progress.

Upon completion of the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1, the MCPTT client:

1) if:

a) the MCPTT ID of the identified MCPTT user is identical to the <mcptt-calling-user-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request: and

b) the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user;

then:

a) shall skip the remaining steps of the current clause;

NOTE: In this case, it is not necessary to send a response to the sender of the remotely initiated private call request as the sender and the terminating party of the successful private call origination are the same user and will be aware of the request’s outcome.

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 in an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and

e) 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> set to the MCPTT ID of the identified MCPTT user called by the remote MCPTT user; and

ii) an <anyExt> element containing:

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

B) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user, a <remotely-initiated-call-outcome> element set to a value of "success"; and

…

3) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user identified by the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and

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

[TS 24.379, clause 11.1.1.2.2.1]

Upon receiving a request from an MCPTT user to establish an MCPTT private call within a pre-established session the MCPTT client shall generate a SIP REFER request outside a dialog in accordance with the procedures specified in 3GPP TS 24.229 [4], IETF RFC 4488 [22] and IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27], with the clarifications given below.

If the MCPTT user is initiating a private call and an end-to-end security context needs to be established the MCPTT client:

1) if necessary, shall instruct the key management client to request keying material from the key management server as described in 3GPP TS 33.180 [78];

2) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [78];

3) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect private call communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [78];

4) shall encrypt the PCK to a UID associated to the MCPTT client using the MCPTT ID and KMS URI of the invited user as determined by the procedures of clause 6.2.8.3.9 and a time related parameter as described in 3GPP TS 33.180 [78];

5) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78];

6) shall add the MCPTT ID of the originating MCPTT to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]; and

7) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCPTT user’s signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78].

The MCPTT client populates the SIP REFER request as follows:

1) shall include the Request-URI set to the public service identity identifying the pre-established session on the MCPTT server serving the MCPTT user;

2) shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];

3) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22];

4) shall include the option tag "multiple-refer" in the Require header field;

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

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

7) shall set the Refer-To header field of the SIP REFER request as specified in IETF RFC 3515 [25] with a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists MIME body as specified in IETF RFC 5366 [20], and with the Content-ID header field set to this "cid" URL.

8) for the initiation of a private call, shall include in the application/resource-lists MIME body a single <entry> element containing a "uri" attribute set to the MCPTT ID of the called user, extended with the following URI header fields:

NOTE 1: Characters that are not formatted as ASCII characters are escaped in the following URI header fields

a) if force of automatic commencement mode at the invited MCPTT client is requested by the MCPTT user, shall include a Priv-Answer-Mode header field with the value "Auto" according to the rules and procedures of IETF RFC 5373 [18];

b) if force of automatic commencement mode at the invited MCPTT client is not requested by the MCPTT user and:

i) if automatic commencement mode at the invited MCPTT client is requested by the MCPTT user, shall include an Answer-Mode header field with the value "Automatic" according to rules and procedures of IETF RFC 5373 [18]; and

ii) if manual commencement mode at the invited MCPTT client is requested by the MCPTT user, shall include an Answer-Mode header field with the value "Manual" according to rules and procedures of IETF RFC 5373 [18]; and

c) shall include in a hname "body" URI header field:

i) if the SDP parameters of the pre-established session do not contain a media-level section of a media-floor control entity or if end-to-end security is required for the private call, an application/sdp MIME body containing the SDP parameters of the pre-established session according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.1. If implicit floor control is required and the pre-established session was not established with an implicit floor request, then the application/sdp MIME body shall contain an implicit floor request as specified in clause 6.4; and

ii) an application/vnd.3gpp.mcptt-info MIME body with the <session-type> element set to "private";

…

12) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session; and

13) if:

a) implicit floor control is required;

b) the pre-established session was not established with an implicit floor request; and

c) location information has not yet been included in the SIP REFER request;

then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element.

The MCPTT client shall send the SIP REFER request towards the MCPTT server according to 3GPP TS 24.229 [4].

6.2.26.3 Test description

6.2.26.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 private calls: the <allow-private-call> element of the <ruleset> element is present in the MCPTT user profile document and is set to "true".

– The MCPTT User performs the procedure for MCPTT pre-established session establishment CO as specified in TS 36.579-1 [2], subclause 5.3.3.

– 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.26.3.2 Test procedure sequence

Table 6.2.26.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1a1

Void

–

–

–

–

2-3A

Steps 1a1-3 of the procedure for MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 requesting the establishment of MCPTT Remotely initiated private call are performed;

the MCPTT ID of the identified MCPTT user of the remotely initiated private call set to the ID of the MCPTT user requesting the call initiation; the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body is set to a value of "false".

–

–

–

–

4

Void

–

–

–

–

5-5C

Check: Does the UE (MCPTT client) perform steps 2-5 of the procedure for MCPTT CO call establishment using a pre-established session as described in TS 36.579-1 [2] table 5.3A.3.3-1 to establish a remotely initiated MCPTT private call?

–

–

1

–

6

Check: Does, in the next 5 sec, the UE (MCPTT Client) send a SIP MESSAGE confirming the progress of the MCPTT remotely initiated private call?

–>

SIP MESSAGE

1

F

6A

Check: Has there been any notification that a request for a remotely initiated private call has been received or that a remotely initiated private call is in progress? (NOTE 1)

–

–

1

F

7

Make the MCPTT User leave the MCPTT session. (NOTE 1)

–

–

–

–

8

The UE (MCPTT Client) performs procedure for MCPTT CO call release keeping the pre-established session as described in TS 36.579-1 [2] table 5.3A.4.3-1 to end the remotely initiated private call.

–

–

–

–

9-11

Steps 1a1 to 3 of the procedure for MCX SIP MESSAGE CT as described in TS 36.579-1 [2] Table 5.3.33.3-1 requesting the establishment of MCPTT Remotely initiated private call are performed;

the MCPTT ID of the identified MCPTT user of the remotely initiated private call set to the ID of the MCPTT user requesting the call initiation; the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body is set to a value of "true".

–

–

–

–

12-12C

Check: Does the UE (MCPTT client) perform steps 2-5 of the procedure for MCPTT CO call establishment using a pre-established session as described in TS 36.579-1 [2] table 5.3A.3.3-1 to establish a remotely initiated MCPTT private call?

–

–

2

–

13

Check: Does the UE (MCPTT Client) correctly perform procedure for MCX SIP MESSAGE CO as described in TS 36.579-1 [2] Table 5.3.32.3-1 confirming the progress of the MCPTT remotely initiated private call?

–

–

2

P

14

Void

–

–

–

–

15

Make the MCPTT User leave the MCPTT session. (NOTE 1)

–

–

–

–

16

The UE (MCPTT Client) perform procedure for MCPTT CO call release keeping the pre-established session as described in TS 36.579-1 [2] table 5.3A.4.3-1 to end the remotely initiated private call.

–

–

–

–

NOTE 1: This is expected to be done via a suitable implementation dependent MMI.

Table 6.2.26.3.2-2: Void

6.2.26.3.3 Specific message contents

Table 6.2.26.3.3-1: SIP MESSAGE from the SS (Step 2, Table 6.2.26.3.2-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.26.3.3-2

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

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-calling-user-id

Encrypted <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_B

requesting MCPTT user (NOTE 1);
encrypted according to NOTE 1 of Table 5.5.3.2.2-1 in TS 36.579-1 [2]

mcptt-called-party-id

Encrypted <mcptt-called-party-id> with mcpttURI set to px_MCPTT_ID_User_B

identified MCPTT user (NOTE 1);

encrypted according to NOTE 1 of Table 5.5.3.2.2-1 in TS 36.579-1 [2]

anyExt

request-type

"remotely-initiated-private-call-request"

notify-remote-user

"false"

NOTE 1: The MCPTT-Info requests a remotely initiated private call with the following roles terms of TS 24.379 [9] clause 11.1.7.1:
– requesting MCPTT user: px_MCPTT_ID_User_B (SS)
– remote MCPTT user: px_MCPTT_ID_User_A initiating the call (UE)
(contained in the <mcptt-request-uri> perdefault)
– identified MCPTT user: px_MCPTT_ID_User_B (SS; same as requesting MCPTT user)
As requesting and identified MCPTT user are the same, the UE shall not send a SIP MESSAGE at step 11 (TS 24.379 [9] clause 11.1.7.2.2).

Table 6.2.26.3.3-3: SIP MESSAGE from the SS (Step 10, Table 6.2.26.3.2-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.26.3.3-4

Table 6.2.26.3.3-4: MCPTT-Info in SIP MESSAGE (Table 6.2.26.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-calling-user-id

Encrypted <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_C

requesting MCPTT user (NOTE 1);
encrypted according to NOTE 1 of Table 5.5.3.2.2-1 in TS 36.579-1 [2]

mcptt-called-party-id

Encrypted <mcptt-called-party-id> with mcpttURI set to px_MCPTT_ID_User_B

identified MCPTT user (NOTE 1);

encrypted according to NOTE 1 of Table 5.5.3.2.2-1 in TS 36.579-1 [2]

anyExt

request-type

"remotely-initiated-private-call-request"

notify-remote-user

"true"

NOTE 1: The MCPTT-Info requests a remotely initiated private call with the following roles terms of TS 24.379 [9] clause 11.1.7.1:
– requesting MCPTT user: px_MCPTT_ID_User_C (SS)
– remote MCPTT user: px_MCPTT_ID_User_A initiating the call (UE)
(contained in the <mcptt-request-uri> perdefault)
– identified MCPTT user: px_MCPTT_ID_User_B (SS; same as requesting MCPTT user)
As requesting and identified MCPTT user are different, the UE shall send a SIP MESSAGE at step 17 (TS 24.379 [9] clause 11.1.7.2.2)

Table 6.2.26.3.3-5: SIP MESSAGE from the UE (Step 13, Table 6.2.26.3.3-3;
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

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.26.3.3-6

Table 6.2.26.3.3-6: MCPTT-Info in SIP MESSAGE (Table 6.2.26.3.3-5)

Derivation Path: TS 36.579-1 [2], table 5.5.3.2.1-1

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_B

The MCPTT ID of the identified MCPTT user (see NOTE 1, Table 6.2.26.3.3-4); 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

response-type

"remotely-initiated-private-call-response"

remotely-initiated-call-outcome

"success"

Table 6.2.26.3.3-7: SIP REFER from the UE (steps 5, 12, Table 6.2.26.3.3-1;
step 2, TS 36.579-1 [2] Table 5.3A.3.3-1)

Derivation Path: TS 36.579-1 [2], table 5.5.2.12-1, condition PRIVATE-CALL

Information Element

Value/remark

Comment

Reference

Condition

Message-body

MIME body part

Resource list

MIME-part-body

Resource-lists as described in Table 6.2.26.3.3-8

Table 6.2.26.3.3-8: Resource-lists (Table 6.2.26.3.3-7)

Derivation Path: TS 36.579-1 [2], table 5.5.3.2.1-1, condition PRE-ESTABLISH, PRIVATE-CALL with the uri attribute of the entry extended with the SIP URI header fields as specified in Table 6.2.26.3.3-9

Table 6.2.26.3.3-9: SIP header fields extending the uri attribute of the resource-lists’ single entry (Table 6.2.26.3.3-8)

Derivation Path: TS 36.579-1 [2], table 5.5.2.12-2 condition PRIVATE-CALL

Information Element

Value/remark

Comment

Reference

Condition

Answer-Mode

any value if present

NOTE 1

body

MIME body part

SDP Message

MIME-part-headers

Content-Type

“application/sdp”

MIME-part-body

SDP Message as described in Table 6.2.26.3.3-10

MIME body part

MCPTT Info

MIME-part-body

MCPTT-Info as described in Table 6.2.26.3.3-11

NOTE 1: TS 24.379 [9] clause 11.1.7 does not say anything about the commencement mode to be used for remotely initiated private call.

Table 6.2.26.3.3-10: SDP Message in SIP REFER (Table 6.2.26.3.3-9)

Derivation Path: TS 36.579-1 [2], table 5.5.3.1.1-1 condition PRIVATE-CALL, SDP_OFFER, PRE_ESTABLISHED_SESSION, WITHOUT_FLOORCONTROL

Table 6.2.26.3.3-11: MCPTT-Info in SIP REFER (Table 6.2.26.3.3-9)

Derivation Path: TS 36.579-1 [2], table 5.5.3.2.2-1, condition PRIVATE-CALL

Table 6.2.26.3.3-11A: SIP 200 (OK) from the SS (steps 5, 12, Table 6.2.26.3.3-1;
step 3, TS 36.579-1 [2] Table 5.3A.3.3-1)

Derivation Path: TS 36.579-1 [2], table 5.5.2.17.1.2-1 condition REFER-RSP, PRIVATE-CALL

Information Element

Value/remark

Comment

Reference

Condition

Content-Type

media-type

"application/sdp"

Message-body

SDP message

As described in Table 6.2.8.3.3-4

Table 6.2.26.3.3-11B: SDP Message in SIP 200 (OK) (Table 6.2.26.3.3-11A)

Derivation Path: TS 36.579-1 [2], table 5.5.3.1.1-1 condition PRIVATE-CALL, SDP_ANSWER, PRE_ESTABLISHED_SESSION, WITHOUT_FLOORCONTROL

Table 6.2.26.3.3-12: Connect (Step 5B, 12B;
step 4, TS 36.579-1 [2] Table 5.3A.3.3-1)

Derivation Path: 36.579-1 [2], Table 5.5.6.12-1, condition PRIVATE-CALL, WITHOUT_FLOORCONTROL, ACK