6.1.4 Remote change of selected group

36.579-63GPPMission Critical (MC) services over LTEPart 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specificationRelease 15TS

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

6.1.4.1 On-network / Remote Change of Selected Group / Selected Group Change of Targeted User / Client Originated (CO)

6.1.4.1.1 Test Purpose (TP)

(1)

with { UE (MCVideo Client) registered and authorised for MCVIDEO Service }

ensure that {

when { the MCVideo User requests to send a group selection change request to change the selected group of a targeted MCVIDEO user to a specific MCVideo group }

then { UE (MCVideo Client) sends a SIP MESSAGE message and responds to a SIP MESSAGE message with a SIP 200 (OK) message }

}

6.1.4.1.2 Conformance Requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.281 clause 9.2.4.2.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.281, clause 9.2.4.2.1]

Upon receiving a request from the MCVideo user to send a group selection change request to change the selected group of a targeted MCVideo user to a specific MCVideo group, the MCVideo client:

1) if:

a) the <RemoteGroupSelectionURIList> element does not exist in the MCVideo user profile document with one or more <entry> elements (see the MCVideo user profile document in 3GPP TS 24.484 [25]); or

b) the <RemoteGroupSelectionURIList> element exists in the MCVideo user profile document and the MCVideo ID of the targeted MCVideo user does not match with one of the <entry> elements of the <RemoteGroupSelectionURIList> element of the MCVideo user profile document (see the MCVideo user profile document in 3GPP TS 24.484 [25]);

then:

a) should indicate to the requesting MCVideo user that they are not authorised to change the selected MCVideo group of the targeted MCVideo user; and

b) shall skip the rest of the steps of the present clause;

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

a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcvideo" (coded as specified in 3GPP TS 24.229 [11]), in a P-Preferred-Service header field according to IETF RFC 6050 [14] 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.mcvideo" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [20];

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 [11]; and

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

i) the <mcvideo-request-uri> set to the MCVideo group identity to be selected by the targeted MCVideo user; and

ii) an <anyExt> element containing the <request-type> element set to a value of "group-selection-change-request"; and

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

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

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

Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the MCVideo user the failure of the sent group selection change request and not continue with the rest of the steps.

Upon receiving a "SIP MESSAGE request for group selection change response for terminating client", the MCVideo client:

1) shall determine the success or failure of the sent group selection change request from the value of the <selected-group-change-outcome> element contained in the <anyExt> element of the <mcvideo-Params> element of the <mcvideoinfo> element of the application/vnd.3gpp.mcvideo-info+xml MIME body included in the received SIP MESSAGE request; and

2) should indicate to the MCVideo user the success or failure of the sent group selection change request.

6.1.4.1.3 Test description

6.1.4.1.3.1 Pre-test conditions

Same pre-test conditions as for MCPTT test case 6.1.4.1 (TS 36.579-2 [24]) with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo"

6.1.4.1.3.2 Test procedure sequence

Same test procedure sequence as for MCPTT test case 6.1.4.1 (TS 36.579-2 [24]) with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo"

6.1.4.1.3.3 Specific message contents

Same specific message contents as for MCPTT test case 6.1.4.1 (TS 36.579-2 [24]) with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo"

– Condition MCVIDEO is used for all messages.

6.1.4.2 On-network / Remote Change of Selected Group / Selected Group Change of Targeted User / Client Terminated (CT)

6.1.4.2.1 Test Purpose (TP)

(1)

with { UE (MCVideo Client) registered and authorised for MCVideo Service }

ensure that {

when { MCVideo User requests group to discover which groups the MCVideo User is affiliated to and to subscribe to affiliation status changes for the MCVideo User }

then { UE (MCVideo Client) sends a SIP SUBSCRIBE message and responds to a SIP NOTIFY message with a SIP 200 (OK) message }

}

(2)

with { UE (MCVideo Client) having subscribed to affiliation status changes }

ensure that {

when { MCVideo User requests to de-affiliate from a group }

then { UE (MCVideo Client) sends a SIP PUBLISH message and responds to a SIP NOTIFY message with a SIP 200 (OK) message }

}

(3)

with { UE (MCVideo Client) having subscribed to affiliation status changes }

ensure that {

when { UE (MCVideo Client) receives to send a group selection change request to change the selected group of a targeted MCVideo user to a specific MCVideo group via a SIP MESSAGE message }

then { UE (MCVideo Client) responds with a SIP 200 (OK) message and initiates affiliation to the group by sending a SIP PUBLISH message and responds to a SIP NOTIFY message with a SIP 200 (OK) message }

}

(4)

with { UE (MCVideo Client) having received a SIP MESSAGE message indicating a group selection change request }

ensure that {

when { UE (MCVideo Client) determines that the group selection change is successful }

then { UE (MCVideo Client) sends the group selection determination via a SIP MESSAGE message }

}

6.1.4.2.2 Conformance Requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.281 clause 8.2.1.2, 8.2.1.3, 9.2.4.2.2. Unless otherwise stated these are Rel-15 requirements.

[TS 24.281, clause 8.2.1.2]

In order:

– to indicate that an MCVideo user is interested in one or more MCVideo group(s) at an MCVideo client;

– to indicate that the MCVideo user is no longer interested in one or more MCVideo group(s) at the MCVideo client;

– to refresh indication of an MCVideo user interest in one or more MCVideo group(s) at an MCVideo client due to near expiration of the expiration time of an MCVideo group with the affiliation status set to the "affiliated" state received in a SIP NOTIFY request in clause 8.2.1.3;

– to send an affiliation status change request in mandatory mode to another MCVideo user; or

– any combination of the above;

the MCVideo client shall generate a SIP PUBLISH request according to 3GPP TS 24.229 [11], IETF RFC 3903 [12], and IETF RFC 3856 [13].

In the SIP PUBLISH request, the MCVideo client:

1) shall set the Request-URI to the public service identity identifying the originating participating MCVideo function serving the MCVideo user;

2) shall include an application/vnd.3gpp.mcvideo-info+xml MIME body. In the application/vnd.3gpp.mcvideo-info+xml MIME body, the MCVideo client shall include the <mcvideo-request-uri> element set to the MCVideo ID of the MCVideo user;

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

4) if the targeted MCVideo user is interested in at least one MCVideo group at the targeted MCVideo client, shall set the Expires header field according to IETF RFC 3903 [12], to 4294967295;

NOTE 1: 4294967295, which is equal to 2³²-1, is the highest value defined for Expires header field in IETF RFC 3261 [15].

5) if the targeted MCVideo user is no longer interested in any MCVideo group at the targeted MCVideo client, shall set the Expires header field according to IETF RFC 3903 [12], to zero; and

6) shall include an application/pidf+xml MIME body indicating per-user affiliation information according to clause 8.3.1. In the MIME body, the MCVideo client:

a) shall include all MCVideo groups where the targeted MCVideo user indicates its interest at the targeted MCVideo client;

b) shall include the MCVideo client ID of the targeted MCVideo client;

c) shall not include the "status" attribute and the "expires" attribute in the <affiliation> element; and

d) shall set the <p-id> child element of the <presence> root element to a globally unique value.

The MCVideo client shall send the SIP PUBLISH request according to 3GPP TS 24.229 [11].

[TS 24.281, clause 8.2.1.3]

NOTE 1: The MCVideo UE also uses this procedure to determine which MCVideo groups the MCVideo user successfully affiliated to.

In order to discover MCVideo groups:

1) which the MCVideo user at an MCVideo client is affiliated to; or

2) which another MCVideo user is affiliated to;

the MCVideo client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 3856 [13], and IETF RFC 6665 [16].

In the SIP SUBSCRIBE request, the MCVideo client:

1) shall set the Request-URI to the public service identity identifying the originating participating MCVideo function serving the MCVideo user;

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

4) if the MCVideo client wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [16], to 4294967295;

NOTE 2: 4294967295, which is equal to 2³²-1, is the highest value defined for Expires header field in IETF RFC 3261 [15].

5) if the MCVideo client wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [16], to zero; and

6) shall include an Accept header field containing the application/pidf+xml MIME type; and

7) if requesting MCVideo groups where the MCVideo user is affiliated to at the MCVideo client, shall include an application/simple-filter+xml MIME body indicating per client restrictions of presence event package notification information according to clause 8.3.2.

In order to re-subscribe or de-subscribe, the MCVideo client shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [11], IETF RFC 3856 [13], and IETF RFC 6665 [16]. In the SIP SUBSCRIBE request, the MCVideo client:

1) if the MCVideo client wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [16], to 4294967295;

NOTE 3: 4294967295, which is equal to 2³²-1, is the highest value defined for Expires header field in IETF RFC 3261 [15].

2) if the MCVideo client wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [16], to zero; and

3) shall include an Accept header field containing the application/pidf+xml MIME type.

Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [11], IETF RFC 3856 [13], and IETF RFC 6665 [16], if SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-user affiliation information constructed according to clause 8.3.1, then the MCVideo client shall determine affiliation status of the MCVideo user for each MCVideo group at the MCVideo client(s) in the MIME body. If the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request is included, the <p-id> element value indicates the SIP PUBLISH request which triggered sending of the SIP NOTIFY request.

[TS 24.281, clause 9.2.4.2.2]

Upon receiving a "SIP MESSAGE request for group selection change request for terminating client", the MCVideo client:

1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <affiliation-required> element set to a value of "true":

a) shall invoke the procedures of clause 8.2.1.2 to affiliate to the MCVideo group identified by the contents of the <mcvideo-calling-group-id> included in the application/vnd.3gpp.mcvideo-info+xml MIME body;

b) if the MCVideo client has not already invoked the procedures of clause 8.2.1.3, shall invoke the procedures of clause 8.2.1.3; and

c) upon receiving a SIP NOTIFY request including a <p-id> element set to a value matching the <p-id> value included in the SIP PUBLISH request sent in step 1) a) above as specified in clause 8.2.1.3, shall determine if the affiliation procedure to the MCVideo group identified by the contents of the <mcvideo-calling-group-id> in the received SIP MESSAGE request was successful;

2) if the received SIP MESSAGE request contained an application/vnd.3gpp.mcvideo-info+xml MIME body containing an <affiliation-required> element set to a value of "true" and the affiliation was successful as determined in step 1) c) above, or if the <affiliation-required> element was not present in the received SIP MESSAGE request:

a) shall change the MCVideo client’s selected group to the MCVideo group identified by the contents of the <mcvideo-calling-group-id> element contained in the application/vnd.3gpp.mcvideo-info+xml MIME body included in the received SIP MESSAGE request; and

b) shall determine the success or failure of the change of selected group action;

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

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 [11];

d) shall include in an application/resource-lists+xml MIME body, the MCVideo ID contained in the <mcvideo-calling-user-id> element in the application/ vnd.3gpp.mcvideo-info+xml MIME body of the received SIP MESSAGE request; and

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

i) the <mcvideo-request-uri> set to the MCVideo group identity identified by the contents of the <mcvideo-calling-group-id> element contained in the received SIP MESSAGE request; and

ii) an <anyExt> element containing:

A) the <response-type> element set to a value of "group-selection-change-response";

B) if the MCVideo client was able to successfully change the selected group as determined in step 2) b) above, a <selected-group-change-outcome> element set to a value of "success"; and

C) if the MCVideo client:

I) was required to affiliate to the MCVideo group identified by the contents of the <mcvideo-calling-group-id> in the received SIP MESSAGE request and the affiliation failed as determined in step 1) c); or

II) failed to change the selected group as determined in step 2) b);

then a <selected-group-change-outcome> element set to a value of "fail";

4) should indicate to the MCVideo user the success or failure of the requested change of selected group action;

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

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

6.1.4.2.3 Test description

6.1.4.2.3.1 Pre-test conditions

Same pre-test conditions as for MCPTT test case 6.1.4.2 (TS 36.579-2 [24]) with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo"

6.1.4.2.3.2 Test procedure sequence

Same test procedure sequence as for MCPTT test case 6.1.4.2 (TS 36.579-2 [24]) with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo"

6.1.4.2.3.3 Specific message contents

Same specific message contents as for MCPTT test case 6.1.4.2 (TS 36.579-2 [24]) with the following exception(s):

– The term "MCPTT" is replaced with "MCVideo"

– Condition MCVIDEO is used for all messages.