6.1.3 Conference Event Package
36.579-23GPPMission Critical (MC) services over LTEPart 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specificationRelease 15TS
6.1.3.1 On-network / Conference Event Package / Subscription to Conference Event Package / Termination of subscription
6.1.3.1.1 Test Purpose (TP)
1)
with { UE (MCPTT Client) registered and authorised for MCPTT Service }
ensure that {
when { the MCPTT User requests the establishment of an MCPTT On-demand Pre-arranged Group Call with Automatic Commencement Mode and implicit floor control }
then { UE (MCPTT Client) requests On-demand Automatic Commencement Mode Pre-arranged Group Call establishment with implicit floor control by sending a SIP INVITE message, and, after indication from the MCPTT Server that the call was established and receiving a Floor Granted message, notifies the user }
}
(2)
with { UE (MCPTT Client) having an ongoing On-demand Pre-arranged Group Call with Automatic Commencement Mode }
ensure that {
when { MCPTT User requests to subscribe to the conference event package for the ongoing group call }
then { UE (MCPTT Client) sends a SIP SUBSCRIBE message with the Expires header field set to 4294967295 and responds to a SIP NOTIFY message with a SIP 200 (OK) message }
}
(3)
with { UE (MCPTT Client) having subscribed to the conference event package for the ongoing group call }
ensure that {
when { MCPTT User requests to terminate the subscription }
then { UE (MCPTT Client) sends a SIP SUBSCRIBE message with the Expires header field set to 0 }
}
(4)
with { UE (MCPTT Client) having an ongoing On-demand Pre-arranged Group Call with Automatic Commencement Mode }
ensure that {
when { the MCPTT User) requests to end the On-demand Pre-arranged Group Call with Automatic Commencement Mode }
then { UE (MCPTT Client) sends a SIP BYE message and leaves the call }
}
6.1.3.1.2 Conformance Requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.379 clauses 10.1.1.2.1.1, 10.1.3.2, 10.1.1.2.3.1. Unless otherwise stated these are Rel-15 requirements.
[TS 24.379, clause 10.1.1.2.1.1]
Upon receiving a request from an MCPTT user to establish an MCPTT prearranged group session 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) if the MCPTT user has requested the origination of an MCPTT emergency group call or is originating an MCPTT prearranged group call and the MCPTT emergency state is already set, the MCPTT client shall comply with the procedures in clause 6.2.8.1.1;
2) if the MCPTT user has requested the origination of an MCPTT imminent peril group call, the MCPTT client shall comply with the procedures in clause 6.2.8.1.9;
3) if the MCPTT user has requested the origination of a broadcast group call, the MCPTT client shall comply with the procedures in clause 6.2.8.2;
4) 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];
5) 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];
6) 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;
7) 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];
8) should include the "timer" option tag in the Supported header field;
9) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";
10) shall set the Request-URI of the SIP INVITE request to the public service identity identifying the participating MCPTT function serving the MCPTT user;
NOTE 1: The MCPTT client is configured with public service identity identifying the participating MCPTT function serving the MCPTT user.
11) 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];
12) if the MCPTT client emergency group state for this group is set to "MEG 2: in-progress" or "MEG 4: confirm-pending", the MCPTT client shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2;
13) if the MCPTT client imminent peril group state for this group is set to "MIG 2: in-progress" or "MIG 4: confirm-pending" shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12;
14) shall contain in an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <session-type> element set to a value of "prearranged";
b) the <mcptt-request-uri> element set to the group identity;
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
NOTE 2: The MCPTT client does not include the MCPTT ID of the originating MCPTT user in the body, as this will be inserted into the body of the SIP INVITE request that is sent from the originating participating MCPTT function.
d) if the group identity can be determined to be a TGI and if the MCPTT client can associate the TGI with a MCPTT group ID, the <associated-group-id> element set to the MCPTT group ID; and
e) if the MCPTT client is aware of active functional-aliases, and an active functional alias is to be included in the initial SIP INVITE request, the <functional-alias-URI> set to the URI of the used functional alias;
NOTE 3: The text "can associate the TGI with a MCPTT group ID" means that the MCPTT client is able to determine that there is a constituent group of the temporary group that it is a member of.
NOTE 4: The MCPTT client is informed about temporary groups and regrouping of MCPTT groups that the user is a member of as specified in 3GPP TS 24.481 [31].
NOTE 5: If the MCPTT user selected a TGI where there are several MCPTT groups where the MCPTT user is a member, the MCPTT client selects one of those MCPTT groups.
NOTE 6: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
15) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.1;
16) if an implicit floor request is required, shall indicate this as specified in clause 6.4; and
17) shall send the SIP INVITE request towards the MCPTT server according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP INVITE request, the MCPTT client:
1) shall interact with the user plane as specified in 3GPP TS 24.380 [5] ;
2) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted" or the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted", the MCPTT client shall perform the actions specified in clause 6.2.8.1.4;
2A) may notify the answer state to the user (i.e. "Unconfirmed" or "Confirmed") if received in the P-Answer-State header field; and
3) may subscribe to the conference event package as specified in clause 10.1.3.1.
[TS 24.379, clause 10.1.3.2]
A MCPTT client may subscribe to the conference event package when a group call is ongoing and the ongoing group call is not initiated as a broadcast group call by sending a SIP SUBSCRIBE request to obtain information of the status of a group session.
When subscribing to the conference event package, the MCPTT client:
1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [26], IETF RFC 4575 [30] and 3GPP TS 24.229 [4];
2) shall set the Request-URI of the SIP SUBSCRIBE request to the MCPTT session identity of the group session;
3) 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];
4) shall include an Accept-Contact header with the media feature tag g.3gpp.icsi-ref with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
5) if the MCPTT client wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 1: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
6) if the MCPTT client wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [26], to zero;
7) shall include an Accept header field containing the application/conference-info+xml"MIME type;
8) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-request-uri> element set to the MCPTT group ID of the group session; and
9) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [4].
The responses to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [26], IETF RFC 4575 [30] and TS 24.229 [4].
Upon receiving a SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request the MCPTT client:
1) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30]; and
2) may display the current state information to the MCPTT client based on the information in the SIP NOTIFY request body.
When needed the MCPTT client shall terminate the subscription and indicate it terminated according to IETF RFC 6665 [26].
NOTE 2: The contents of the received SIP NOTIFY request body is specified in clause 6.3.3.4.
[TS 24.379, clause 10.1.1.2.3.1]
When an MCPTT client wants to leave the MCPTT session that has been established using on-demand session, the MCPTT client shall follow the procedures as specified in clause 6.2.4.1.
6.1.3.1.3 Test description
6.1.3.1.3.1 Pre-test conditions
System Simulator:
– SS (MCPTT server)
– For the underlying "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.
– 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.1.3.1.3.2 Test procedure sequence
Table 6.1.3.1.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Make the MCPTT User request the establishment of an MCPTT on-demand pre-arranged group call using Group A, automatic commencement mode, with implicit floor control. (NOTE 1) |
– |
– |
– |
– |
|
2 |
Check: Does the UE (MCPTT client) perform 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 on-demand pre-arranged group call, automatic commencement mode, applying End-to-end communication security with implicit floor control according to option b.i of NOTE 1 in TS 36.579.1 [2] Table 5.3A.1.3-1? |
– |
– |
1 |
– |
|
3 |
Check: Does the UE (MCPTT client) provide floor granted notification to the MCPTT User? (NOTE 1) |
– |
– |
1 |
P |
|
4 |
Make the MCPTT User request to subscribe to the conference event package for the ongoing group call to receive the current status and later notification (NOTE 1) |
– |
– |
– |
– |
|
5 |
Check: Does the UE (MCPTT Client) send a SIP SUBSCRIBE message with the Expires header field set to 4294967295? |
–> |
SIP SUBSCRIBE |
2 |
P |
|
6 |
The SS (MCPTT Server) responds with a SIP 200 (OK) message. |
<– |
SIP 200 (OK) |
– |
– |
|
7 |
The SS (MCPTT Server) sends conference event package notification via a SIP NOTIFY message. |
<– |
SIP NOTIFY |
– |
– |
|
8 |
Check: Does the UE (MCPTT Client) send a SIP 200 (OK) in response to the SIP NOTIFY message? |
–> |
SIP 200 (OK) |
2 |
P |
|
9 |
The SS (MCPTT Server) sends conference event package notification update via a SIP NOTIFY message. |
<– |
SIP NOTIFY |
– |
– |
|
10 |
Check: Does the UE (MCPTT Client) send a SIP 200 (OK) in response to the SIP NOTIFY message? |
–> |
SIP 200 (OK) |
2 |
P |
|
11 |
Make the MCPTT User request to terminate the subscription to the conference event package. (NOTE 1) |
– |
– |
– |
– |
|
12 |
Check: Does the UE (MCPTT Client) send a SIP SUBSCRIBE message with the Expires header field set to 0? |
–> |
SIP SUBSCRIBE |
3 |
P |
|
13 |
The SS (MCPTT Server) responds with a SIP 200 (OK) message. |
<– |
SIP 200 (OK) |
– |
– |
|
14 |
Make the MCPTT User end the on-demand group call. (NOTE 1) |
– |
– |
– |
– |
|
15 |
Check: Does the UE (MCPTT Client) perform procedure for MCX CO call release as described in TS 36.579-1 [2] Table 5.3.10.3-1 to end the on-demand group call? |
– |
– |
4 |
– |
|
NOTE 1: This is expected to be done via a suitable implementation dependent MMI. |
|||||
6.1.3.1.3.3 Specific message contents
Table 6.1.3.1.3.3-1: SIP INVITE from the UE(step 2, Table 6.1.3.1.3.2-1;
step 2, TS 36.579-1 [2] Table 5.3A.1.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.5.1-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
SDP message |
|||
|
MIME-part-body |
SDP Message as described in Table 6.1.3.1.3.3-2 |
|||
|
MIME body part |
MCPTT Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.3.1.3.3-3 |
|||
Table 6.1.3.1.3.3-2: SDP in SIP INVITE (Table 6.1.3.1.3.3-1)
|
Derivation Path: TS 36.579-1 [2], 5.5.3.1.1-1 condition INITIAL_SDP_OFFER, IMPLICIT_GRANT_REQUESTED |
Table 6.1.3.1.3.3-3: MCPTT-Info in SIP INVITE (Table 6.1.3.1.3.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.1-1 condition GROUP-CALL, INVITE_REFER |
Table 6.1.3.1.3.3-4: SIP 200 (OK) from the SS (step 2, Table 6.1.3.1.3.3-1;
step 4, TS 36.579-1 [2] Table 5.3A.1.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.17.1.2-1 condition INVITE_RSP |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
SDP Message |
As described in Table 6.1.3.1.3.3-5 |
|||
Table 6.1.3.1.3.3-5: SDP in SIP 200 (OK) (Table 6.1.3.1.3.3-4)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.1.2-1 condition SDP_ANSWER, IMPLICIT_GRANT_REQUESTED and IMPLICIT_FLOOR_GRANTED |
Table 6.1.3.1.3.3-6: SIP SUBSCRIBE from the UE (step 5, Table 6.1.3.1.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.14-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Request-Line |
||||
|
Request-URI |
MCPTT session identity of the group session as provided by the SS in the Contact header field of the SIP 200 OK at call establishment |
TS 24.379 [9] clause 10.1.3.2 |
||
|
Accept-Contact |
||||
|
ac-value |
||||
|
feature-param |
"+g.3gpp.icsi-ref=urn:urn-7:3gpp-service.ims.icsi.mcptt" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
req-param |
"require" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
explicit-param |
"explicit" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
Expires |
||||
|
value |
"4294967295" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
Accept |
||||
|
media-range |
"application/conference-info+xml" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
Message-body |
||||
|
MIME body part |
MCPTT Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.3.1.3.3-7 |
|||
Table 6.1.3.1.3.3-7: MCPTT-Info in SIP SUBSCRIBE (Table 6.1.3.1.3.3-6)
|
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-request-uri |
Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCPTT_Group_A_ID |
The URI of the group |
||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-1A |
||||
Table 6.1.3.1.3.3-8: SIP 200 (OK) from the SS (Steps 6, 13, Table 6.1.3.1.3.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.17.1.2-1 condition SUBSCRIBE-RSP |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Contact |
||||
|
addr-spec |
||||
|
user-info and host |
"sip:" & "conference-event-package@cf." & px_MCX_DomainName_Organization_A |
|||
|
port |
not present |
|||
Table 6.1.3.1.3.3-9: SIP NOTIFY from the SS (step 7, Table 6.1.3.1.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
P-Asserted-Identity |
||||
|
addr-spec |
||||
|
user-info and host |
tsc_MCPTT_PublicServiceId_A |
TS 24.379 [9] clause 6.3.3.4 |
||
|
Event |
||||
|
event-type |
"conference" |
TS 24.379 [9] clause 6.3.3.4 |
||
|
Expires |
||||
|
value |
"3600" |
3600 seconds |
TS 24.379 [9] clause 6.3.3.4 |
|
|
Subscription-State |
||||
|
expires |
"3600" |
|||
|
P-Preferred-Service |
||||
|
Service-ID |
"urn:urn-7:3gpp-service.ims.icsi.mcptt" |
TS 24.379 [9] clause 6.3.3.4 |
||
|
Message-body |
||||
|
MIME body part |
MCPTT Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.3.1.3.3-10 |
|||
|
MIME body part |
Conference-Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.3.1.3.3-11 |
|||
Table 6.1.3.1.3.3-10: MCPTT-Info in SIP NOTIFY (Table 6.1.3.1.3.3-9)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.2.2-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
mcpttinfo |
||||
|
mcptt-Params |
||||
|
mcptt-calling-user-id |
not present |
|||
|
mcptt-calling-group-id |
Encrypted (NOTE 1) <mcptt-calling-group-id> with mcpttURI set to px_MCPTT_Group_A_ID |
|||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.2-1A |
||||
Table 6.1.3.1.3.3-11: Conference-Info in SIP NOTIFY (Table 6.1.3.1.3.3-9)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.15-1 |
Table 6.1.3.1.3.3-12: SIP NOTIFY from the SS (step 9, Table 6.1.3.1.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
P-Asserted-Identity |
||||
|
addr-spec |
||||
|
user-info and host |
tsc_MCPTT_PublicServiceId_A |
TS 24.379 [9] clause 6.3.3.4 |
||
|
Event |
||||
|
event-type |
"conference" |
TS 24.379 [9] clause 6.3.3.4 |
||
|
Expires |
||||
|
value |
"3600" |
3600 seconds |
TS 24.379 [9] clause 6.3.3.4 |
|
|
Subscription-State |
||||
|
expires |
"3600" |
|||
|
P-Preferred-Service |
||||
|
Service-ID |
"urn:urn-7:3gpp-service.ims.icsi.mcptt" |
TS 24.379 [9] clause 6.3.3.4 |
||
|
Message-body |
||||
|
MIME body part |
MCPTT Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.3.1.3.3-10 |
|||
|
MIME body part |
Conference-Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.3.1.3.3-13 |
|||
Table 6.1.3.1.3.3-13: Conference-Info in SIP NOTIFY (Table 6.1.3.1.3.3-12)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.15-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
conference-info |
||||
|
users |
||||
|
user [3] |
||||
|
endpoint |
||||
|
status |
disconnected |
|||
Table 6.1.3.1.3.3-14: SIP SUBSCRIBE from the UE (step 12, Table 6.1.3.1.3.2-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.14-1 condition re_SUBSCRIBE |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Accept-Contact |
||||
|
ac-value |
||||
|
feature-param |
"+g.3gpp.icsi-ref=urn:urn-7:3gpp-service.ims.icsi.mcptt" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
req-param |
"require" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
explicit-param |
"explicit" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
Expires |
||||
|
value |
"0" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
Accept |
||||
|
media-range |
"application/conference-info+xml" |
TS 24.379 [9] clause 10.1.3.2 |
||
|
Message-body |
||||
|
MIME body part |
MCPTT Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.3.1.3.3-7 |
|||