6.2.25 On-network / Private call / Remotely initiated private call / On-demand 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.25.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 on-demand 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, 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 on-demand session, and, does not notify the user that a remotely initiated private call request to call the identified MCPTT user has been received, and, when a SIP 180 (Ringing) response is received to the sent SIP INVITE request, 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 on-demand 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 }
then { UE (MCPTT Client) initiates private call establishment to the requested identified MCPTT user using on-demand session, and, sends SIP MESSAGE back to the MCPTT user requesting the call initiation to confirm the private call initiation }
}
6.2.25.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.1.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;
3) if according to local policy on-demand sessions are to be used for remotely initiated private calls, shall invoke the procedures of sclause 11.1.1.2.1.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) if a SIP 180 (Ringing) response or SIP 183 (Session Progress) response is received to the to the sent SIP INVITE request, shall not give any indication to the remote MCPTT user that the remotely initiated private call origination is in progress; and
…
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.1.1]
Upon receiving a request from an MCPTT user to establish an MCPTT private call the MCPTT client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client:
1) shall set the Request-URI of the SIP INVITE request to a public service identity of the participating MCPTT function serving the MCPTT user;
…
4) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [4];
5) shall include the g.3gpp.mcptt media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [16];
6) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
7) 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 INVITE request;
8) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref contain with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
9) for the establishment of a private call shall insert in the SIP INVITE request a MIME resource-lists body with the MCPTT ID of the invited MCPTT user, according to rules and procedures of IETF RFC 5366 [20];
…
11) if an end-to-end security context needs to be established and if the MCPTT user is initiating a private call then:
a) 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];
b) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [78];
c) 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];
d) 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];
e) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78]; and
g) 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
f) 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];
12) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarification given in clause 6.2.1 and with a media stream of the offered media-floor control entity;
13) if implicit floor control is required, shall comply with the conditions specified in clause 6.4 and:
a) if the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
b) if location information has not yet been included in the SIP re-INVITE 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;
14) if the MCPTT user is initiating a private call then:
a) if force of automatic commencement mode at the invited MCPTT client is requested by the MCPTT user, shall include in the SIP INVITE request 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 in the SIP INVITE request an Answer-Mode header field with the value "Auto" according to the 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 in the SIP INVITE request an Answer-Mode header field with the value "Manual" according to the rules and procedures of IETF RFC 5373 [18]; and
c) shall contain an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <session-type> element set to a value of "private";
…
17) shall send SIP INVITE request towards the MCPTT server according to 3GPP TS 24.229 [4].
6.2.25.3 Test description
6.2.25.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".
– 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.25.3.2 Test procedure sequence
Table 6.2.25.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1a1 |
Void |
– |
– |
– |
– |
|
2-3A |
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 "false". |
– |
– |
– |
– |
|
4 |
Void |
– |
– |
– |
– |
|
5-7 |
Check: Does the UE (MCPTT Client) perform steps 2 – 4 of the procedure for MCPTT CO private call establishment, manual commencement as described in TS 36.579-1 [2] Table 5.3A.2.3-1 requesting the establishment of an MCPTT call? NOTE: Any SIP INVITE content in regard to Automatic Commencement Mode, Force of automatic commencement, and Floor Control shall be accepted. |
–> |
SIP INVITE |
1 |
P |
|
8 |
Check: Does the UE (MCPTT client) notify the user that a request for a remotely initiated private call has been received or that a remotely initiated private call origination is in progress? (NOTE 1) |
– |
– |
1 |
F |
|
9-10 |
Check: Does the UE (MCPTT Client) perform steps 5 – 6 of the procedure for MCPTT CO private call establishment, manual commencement as described in TS 36.579-1 [2] Table 5.3A.2.3-1? |
– |
– |
1 |
P |
|
11 |
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 |
|
12 |
The procedure for MCX CT call release as described in TS 36.579-1 [2] Table 5.3.12.3-1 to end the call is performed. |
– |
– |
– |
– |
|
13a1-15 |
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 an 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"Void |
– |
– |
– |
– |
|
16-16C |
Check: Does the UE (MCPTT client) perform steps 2-5 of the procedure for MCPTT CO session establishment/modification without provisional responses other than 100 Trying as described in TS 36.579-1 [2] Table 5.3A.1.3-1 to establish an MCPTT private call, on-demand? |
– |
– |
2 |
– |
|
17 |
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 |
|
18 |
Void |
– |
– |
– |
– |
|
19 |
The procedure for MCX CT call release as described in TS 36.579-1 [2] Table 5.3.12.3-1 to end the private call takes place. |
– |
– |
– |
– |
|
NOTE 1: This is expected to be done via a suitable implementation dependent MMI. |
|||||
6.2.25.3.3 Specific message contents
Table 6.2.25.3.3-1: SIP MESSAGE from the SS (Step 2, Table 6.2.25.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.25.3.3-2 |
||||||||
Table 6.2.25.3.3-2: MCPTT-Info in SIP MESSAGE (Table 6.2.25.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); |
|||
|
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: 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.25.3.3-3: SIP INVITE from the UE (Step 5, 16, Table 6.2.25.3.2-1;
step 2, TS 36.579-1 [2] Table 5.3A.1.3-1;
step 2, TS 36.579-1 [2] Table 5.3A.2.3-1)
|
Derivation Path: TS 36.579-1 [2], table 5.5.2.5.1-1, condition PRIVATE-CALL |
|||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
|
Answer-Mode |
any value if presen |
NOTE 1 |
|||
|
Message-body |
|||||
|
MIME body part |
SDP message |
||||
|
MIME-part-body |
SDP Message as described in Table 6.2.25.3.3-3A |
||||
|
MIME body part |
MCPTT Info |
||||
|
MIME-part-body |
MCPTT-Info as described in Table 6.2.1.3.3-1B |
||||
|
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.25.3.3-3A: SDP message in SIP INVITE (Table 6.2.25.3.3-3)
|
Derivation Path: TS 36.579-1 [2], table 5.5.3.1.1-1 condition PRIVATE-CALL, INITIAL_SDP_OFFER |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Media description[2] |
optional (NOTE 1) |
Media description for media control |
||
|
media attribute |
a= line attribute = fmtp |
|||
|
fmtp |
||||
|
format specific parameters |
||||
|
mc_implicit_request |
optional (NOTE 1) |
|||
|
NOTE 1: Whether the UE (MCPTT Client) requests a call with or without Floor control depends on implementation. The SS shall respect the type of Floor control being requested, if requested (see Table 6.2.25.3.3-3C) |
||||
Table 6.2.25.3.3-3B: MCPTT-Info in SIP INVITE (Table 6.2.25.3.3-3)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-1 condition INVITE_REFER, PRIVATE-CALL |
Table 6.2.25.3.3-3C: SIP 200 (OK) from the SS (Step 9, 16B Table 6.2.25.3.2-1;
step 4, TS 36.579-1 [2] Table 5.3A.1.3-1;
step 4, TS 36.579-1 [2] Table 5.3A.2.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.17.1.2-1 with condition INVITE-RSP |
||||
|---|---|---|---|---|
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
SDP message |
SDP message as described in Table 6.2.25.3.3-3D |
|||
Table 6.2.25.3.3-3D: SDP Message in SIP 200 (OK) (Table 6.2.25.3.3-3B)
|
Derivation Path: TS 36.579-1 [2], table 5.5.3.1.2-1 condition SDP_ANSWER |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Media description [2] |
Media description for media control |
WITH_MEDIACONTROL |
||
|
Condition |
Explanation |
|
WITH_MEDIACONTROL |
The SDP offer sent by the UE at step 5 (Table 6.2.25.3.3-3A) or step 16 (Table 6.2.25.3.3-6) contains a media description for media control. In this case, independent from whether or not the UE implicitly requests a grant, neither IMPLICIT_GRANT_REQUESTED nor IMPLICIT_FLOOR_GRANTED shall be applied |
Table 6.2.25.3.3-4: SIP MESSAGE from the SS (Step 14, Table 6.2.25.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.25.3.3-5 |
||||||||
Table 6.2.25.3.3-5: MCPTT-Info in SIP MESSAGE (Table 6.2.25.3.3-4)
|
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); |
|||
|
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 |
The anyExt field may contain other values – these need not be checked |
||||
|
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: |
|||||
Table 6.2.25.3.3-6: Void
Table 6.2.25.3.3-7: SIP MESSAGE from the UE(Step 17, Table 6.2.25.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 |
|||||||||
|
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.25.3.3-8 |
||||||||
Table 6.2.25.3.3-8: MCPTT-Info in SIP MESSAGE (Table 6.2.25.3.3-7)
|
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.25.3.3-5); 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.25.3.3-9: SIP BYE from the SS (step 19, Table 6.2.25.3.2-1;
step 1, TS 36.579-1 [2] Table 5.3.12.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.2.2-1 condition MO_CALL |