6.1.4 Remote Change of Selected Group
36.579-23GPPMission Critical (MC) services over LTEPart 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specificationRelease 15TS
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 (MCPTT Client) registered and authorised for MCPTT Service }
ensure that {
when { the MCPTT User requests to send a group selection change request to change the selected group of a targeted MCPTT user to a specific MCPTT group }
then { UE (MCPTT 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.379 clause 10.1.4.2.1. Unless otherwise stated these are Rel-15 requirements.
[TS 24.379, clause 10.1.4.2.1]
Upon receiving a request from the MCPTT user to send a group selection change request to change the selected group of a targeted MCPTT user to a specific MCPTT group, the MCPTT client:
1) if:
a) the <RemoteGroupSelectionURIList> element does not exist in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
b) the <RemoteGroupSelectionURIList> element exists in the MCPTT user profile document and the MCPTT ID of the targeted MCPTT user does not match with one of the <entry> elements of the <RemoteGroupSelectionURIList> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
then:
a) should indicate to the requesting MCPTT user that they are not authorised to change the selected MCPTT group of the targeted MCPTT 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 [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]; and
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-request-uri> set to the MCPTT group identity to be selected by the targeted MCPTT user; and
ii) the <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 MCPTT ID of the targeted MCPTT user, according to rules and procedures of IETF RFC 5366 [20];
3) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the MCPTT 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 MCPTT 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 <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 MCPTT 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
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.4.1.3.2 Test procedure sequence
Table 6.1.4.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Make the MCPTT User request to send a group selection change request to change the selected group of a targeted MCPTT user to a specific MCPTT group. (NOTE 1) |
– |
– |
– |
– |
|
2 |
Check: Does the UE (MCPTT Client) correctly perform procedure for MCX SIP MESSAGE Request – Accept CO as described in TS 36.579-1 [2] Table 5.3.30.3-1 to change the selected group of a targeted MCPTT user to a specific MCPTT group? |
– |
– |
1 |
– |
|
NOTE 1: This is expected to be done via a suitable implementation dependent MMI. |
|||||
6.1.4.1.3.3 Specific message contents
Table 6.1.4.1.3.3-1: SIP MESSAGE from the UE (Step 2, Table 6.1.4.1.3.2-1;
Step 2, TS 36.579-1 [2] Table 5.3.30.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 |
TS 24.379 [9] clause F.1 |
||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.4.1.3.3-2 |
|||
|
MIME body part |
Resource lists |
|||
|
MIME-part-body |
Resource-lists as described in Table 6.1.4.1.3.3-3 |
|||
Table 6.1.4.1.3.3-2: MCPTT-Info in SIP MESSAGE (Table 6.1.4.1.3.3-1)
|
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_B_ID |
The MCPTT group identity to be selected by the targeted MCPTT user |
TS 24.379 [9] clause 10.1.4.2.1 |
|
|
anyExt |
||||
|
request-type |
"group-selection-change-request" |
TS 24.379 [9] clause 10.1.4.2.1 |
||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-1A. |
||||
Table 6.1.4.1.3.3-3: Resource lists in SIP MESSAGE (Table 6.1.4.1.3.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.3.1-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
resource-lists |
||||
|
list |
||||
|
entry[1] |
||||
|
uri attribute |
px_MCPTT_ID_User_C |
The targeted MCPTT user |
TS 24.379 [9] clause 10.1.4.2.1 |
|
Table 6.1.4.1.3.3-4: SIP MESSAGE from the SS (Step 2, Table 6.1.4.1.3.2-1;
Step 4, TS 36.579-1 [2] Table 5.3.30.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 |
|
P-Asserted-Identity |
||||
|
name-addr |
px_MCX_SIP_PublicUserId_C |
TS 24.379 [9] clause 10.1.4.4 |
||
|
Message-body |
||||
|
MIME body part |
MCPTT Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.4.1.3.3-5 |
|||
Table 6.1.4.1.3.3-5: MCPTT-Info in SIP MESSAGE (Table 6.1.4.1.3.3-4)
|
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-request-uri |
Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A |
TS 24.379 [9] clause 10.1.4.4 |
||
|
mcptt-calling-user-id |
Encrypted (NOTE 1) <mcptt-calling-user-id> with mcpttURI set to px_MCPTT_ID_User_C |
|||
|
mcptt-calling-group-id |
Encrypted (NOTE 1) <mcptt-calling-group-id> with mcpttURI set to px_MCPTT_Group_B_ID |
|||
|
anyExt |
||||
|
response-type |
"group-selection-change-response" |
TS 24.379 [9] clause 10.1.4.4 |
||
|
selected-group-change-outcome |
"success" |
|||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-1A. |
||||
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 (MCPTT Client) registered and authorised for MCPTT Service }
ensure that {
when { MCPTT User requests group to discover which groups the MCPTT User is affiliated to and to subscribe to affiliation status changes for the MCPTT User }
then { UE (MCPTT Client) sends a SIP SUBSCRIBE message and responds to a SIP NOTIFY message with a SIP 200 (OK) message }
}
(2)
with { UE (MCPTT Client) having subscribed to affiliation status changes }
ensure that {
when { MCPTT User requests to de-affiliate from a group }
then { UE (MCPTT Client) sends a SIP PUBLISH message and responds to a SIP NOTIFY message with a SIP 200 (OK) message }
}
(3)
with { UE (MCPTT Client) having subscribed to affiliation status changes }
ensure that {
when { UE (MCPTT Client) receives to send a group selection change request to change the selected group of a targeted MCPTT user to a specific MCPTT group via a SIP MESSAGE message }
then { UE (MCPTT 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 (MCPTT Client) having received a SIP MESSAGE message indicating a group selection change request }
ensure that {
when { UE (MCPTT Client) determines that the group selection change is successful }
then { UE (MCPTT 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.379 clause 9.2.1.2, 9.2.1.3, 10.1.4.2.2. Unless otherwise stated these are Rel-15 requirements.
[TS 24.379, clause 9.2.1.2]
In order:
– to indicate that an MCPTT user is interested in one or more MCPTT group(s) at an MCPTT client;
– to indicate that the MCPTT user is no longer interested in one or more MCPTT group(s) at the MCPTT client;
– to refresh indication of an MCPTT user interest in one or more MCPTT group(s) at an MCPTT client due to near expiration of the expiration time of an MCPTT group with the affiliation status set to the "affiliated" state received in a SIP NOTIFY request in clause 9.2.1.3;
– to send an affiliation status change request in mandatory mode to another MCPTT user; or
– any combination of the above;
the MCPTT client shall generate a SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37], and IETF RFC 3856 [51].
In the SIP PUBLISH request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include the <mcptt-request-uri> element set to the MCPTT ID of the MCPTT user;
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) if the targeted MCPTT user is interested in at least one MCPTT group at the targeted MCPTT client, shall set the Expires header field according to IETF RFC 3903 [37], 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].
5) if the targeted MCPTT user is no longer interested in any MCPTT group at the targeted MCPTT client, shall set the Expires header field according to IETF RFC 3903 [37], to zero; and
6) shall include an application/pidf+xml MIME body indicating per-user affiliation information according to clause 9.3.1. In the MIME body, the MCPTT client:
a) shall include all MCPTT groups where the targeted MCPTT user indicates its interest at the targeted MCPTT client;
b) shall include the MCPTT client ID of the targeted MCPTT 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 MCPTT client shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4].
[TS 24.379, clause 9.2.1.3]
NOTE 1: The MCPTT UE also uses this procedure to determine which MCPTT groups the MCPTT user successfully affiliated to.
In order to discover MCPTT groups:
1) which the MCPTT user at an MCPTT client is affiliated to; or
2) which another MCPTT user is affiliated to;
the MCPTT client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include the <mcptt-request-uri> element set to the MCPTT ID of the targeted MCPTT user;
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) 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 2: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) 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; and
6) shall include an Accept header field containing the application/pidf+xml MIME type; and
7) if requesting MCPTT groups where the MCPTT user is affiliated to at the MCPTT client, shall include an application/simple-filter+xml MIME body indicating per-client restrictions of presence event package notification information according to clause 9.3.2, indicating the MCPTT client ID of the MCPTT client.
In order to re-subscribe or de-subscribe, the MCPTT client shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]. In the SIP SUBSCRIBE request, the MCPTT client:
1) 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 3: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
2) if the MCPTT client wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [26], 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 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26], if SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-user affiliation information constructed according to clause 9.3.1, then the MCPTT client shall determine affiliation status of the MCPTT user for each MCPTT group at the MCPTT 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.379, clause 10.1.4.2.2]
Upon receiving a "SIP MESSAGE request for group selection change request for terminating client", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing an <affiliation-required> element set to a value of "true":
a) shall invoke the procedures of clause 9.2.1.2 to affiliate to the MCPTT group identified by the contents of the <mcptt-calling-group-id> included in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) if the MCPTT client has not already invoked the procedures of clause 9.2.1.3, shall invoke the procedures of clause 9.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 9.2.1.3, shall determine if the affiliation procedure to the MCPTT group identified by the contents of the <mcptt-calling-group-id> in the received SIP MESSAGE request was successful;
2) if the received SIP MESSAGE request contained an application/vnd.3gpp.mcptt-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 MCPTT client’s selected group to the MCPTT group identified by the contents of the <mcptt-calling-group-id> element contained in the application/vnd.3gpp.mcptt-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 [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 <response-type> element set to a value of "group-selection-change-response"; and
ii) the <anyExt> element containing:
- the <response-type> element set to a value of "group-selection-change-response";
B) if the MCPTT client was able to successfully change the selected group as determined in step 2) b) above, then a <selected-group-change-outcome> element set to a value of "success"; and
C) if the MCPTT client:
I) was required to affiliate to the MCPTT group identified by the contents of the <mcptt-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 MCPTT 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 MCPTT function serving the MCPTT user; and
6) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
6.1.4.2.3 Test description
6.1.4.2.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.4.2.3.2 Test procedure sequence
Table 6.1.4.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Make the MCPTT User request to discover which groups the MCPTT User is affiliated to and to subscribe to affiliation status changes for the MCPTT User. (NOTE 1) |
– |
– |
– |
– |
|
2 |
Check: Does the UE (MCPTT Client) correctly perform procedure for MCX Subscription and Notification as described in TS 36.579-1 [2] table 5.3.29.3-1 to subscribe to its own affiliation status changes? |
– |
– |
1 |
P |
|
3 |
Make the MCPTT User request to de-affiliate from an MCPTT group, GROUP A. (NOTE 1) |
– |
– |
– |
– |
|
4 |
Check: Does the UE (MCPTT Client) correctly perform procedure for MCX Group Affiliation Status Change as described in TS 36.579-1 [2] table 5.3.34.3-1 to de-affiliate with GROUP A? |
– |
– |
2 |
P |
|
5-7 |
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 containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <affiliation-required> element set to a value of "true" asking the UE (MCPTT Client) to change the selected group to Group A are performed. |
– |
– |
– |
– |
|
8-12A |
Check: Does the UE (MCPTT Client) correctly perform steps 2-7 of the procedure for MCX Group Affiliation Status Change as described in TS 36.579-1 [2] table 5.3.34.3-1 to affiliate with GROUP A? |
– |
– |
3 |
P |
|
13-15 |
Check: Does the UE (MCPTT Client) correctly perform steps 2 to 4 of the procedure for MCX SIP MESSAGE CO as described in TS 36.579-1 [2] table 5.3.32.3-1 indicating that change of selected group has been successful? |
– |
– |
4 |
P |
|
NOTE 1: This is expected to be done via a suitable implementation dependent MMI. |
|||||
6.1.4.2.3.3 Specific message contents
Table 6.1.4.2.3.3-1: SIP SUBSCRIBE from the UE (step 2, Table 6.1.4.2.3.2-1;
step 2, TS 36.579-1 [2] Table 5.3.29.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.14-1 |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Expires |
||||
|
delta-seconds |
"4294967295" |
|||
|
Message-body |
||||
|
MIME body part |
MCPTT-Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.4.2.3.3-2 |
|||
Table 6.1.4.2.3.3-2: MCPTT-Info in SIP SUBSCRIBE (Table 6.1.4.2.3.3-1)
|
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_ID_User_A |
|||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-1A. |
||||
Table 6.1.4.2.3.3-3: SIP NOTIFY from the SS (step 2, Table 6.1.4.2.3.2-1;
step 4, TS 36.579-1 [2] Table 5.3.29.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1 with condition PRESENCE-EVENT |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
PIDF |
|||
|
MIME-part-body |
PIDF as described in Table 6.1.4.2.3.3-4 |
|||
Table 6.1.4.2.3.3-4: PIDF in SIP NOTIFY (Table 6.1.4.2.3.3-3)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.5.2-1 condition AFFILIATION |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
presence |
||||
|
tuple |
||||
|
status |
||||
|
affiliation |
||||
|
status |
affiliated |
|||
Table 6.1.4.2.3.3-5: SIP PUBLISH from the UE (step 4 Table 6.1.4.2.3.2-1;
step 2, TS 36.579-1 [2] Table 5.3.34.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.11-1 with condition PRESENCE-EVENT |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Expires |
||||
|
delta-seconds |
0 |
|||
|
Message-body |
||||
|
MIME body part |
MCPTT-Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.4.2.3.3-6 |
|||
|
MIME body part |
PIDF |
|||
|
MIME-part-body |
PIDF as described in Table 6.1.4.2.3.3-7 |
|||
Table 6.1.4.2.3.3-6: MCPTT-Info in SIP PUBLISH (Table 6.1.4.2.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-request-uri |
Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A |
|||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-1A. |
||||
Table 6.1.4.2.3.3-7: PIDF in SIP PUBLISH (Table 6.1.4.2.3.3-5)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.5.1-1 condition AFFILIATION |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
presence |
||||
|
tuple |
||||
|
status |
not present |
|||
|
..p-id |
any allowed value |
p-id shall be present acc. to TS 24.379 [9] clause 9.2.2.2.5 and clause 9.2.2.3.5 |
||
Table 6.1.4.2.3.3-8: SIP NOTIFY from the SS (step 4, Table 6.1.4.2.3.2-1;
step 4, TS 36.579-1 [2] Table 5.3.34.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1 with condition PRESENCE-EVENT |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
PIDF |
|||
|
MIME-part-body |
PIDF as described in Table 6.1.4.2.3.3-9 |
|||
Table 6.1.4.2.3.3-9: PIDF in SIP NOTIFY (Table 6.1.4.2.3.3-8)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.5.2-1 condition AFFILIATION |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
presence |
||||
|
tuple |
||||
|
status |
||||
|
affiliation |
||||
|
status |
deaffiliating |
|||
|
..p-id |
same value as received in corresponding SIP PUBLISH |
|||
Table 6.1.4.2.3.3-10: SIP NOTIFY from the SS (step 4, Table 6.1.4.2.3.2-1;
step 6, TS 36.579-1 [2] Table 5.3.34.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1 with condition PRESENCE-EVENT |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
PIDF |
|||
|
MIME-part-body |
PIDF as described in Table 6.1.4.2.3.3-11 |
|||
Table 6.1.4.2.3.3-11: PIDF in SIP NOTIFY (Table 6.1.4.2.3.3-10)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.5.2-1 condition AFFILIATION |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
presence |
||||
|
tuple id |
||||
|
status |
not present |
|||
|
..p-id |
same value as received in the corresponding SIP PUBLISH |
|||
Table 6.1.4.2.3.3-12: SIP MESSAGE from the SS (Step 6, Table 6.1.4.2.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 |
TS 24.379 [9] clause F.1 |
||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.4.2.3.3-13 |
|||
Table 6.1.4.2.3.3-13: MCPTT-Info in SIP MESSAGE (Table 6.1.4.2.3.3-12)
|
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-request-uri |
Encrypted (NOTE 1) <mcptt-request-uri> with mcpttURI set to px_MCPTT_ID_User_A |
TS 24.379 [9] clause 10.1.4.4 |
||
|
mcptt-calling-group-id |
Encrypted (NOTE 1) <mcptt-calling-group-id> with mcpttURI set to px_MCPTT_Group_A_ID |
|||
|
anyExt |
||||
|
request-type |
"group-selection-change-request" |
TS 24.379 [9] clause 10.1.4.4 |
||
|
affiliation-required |
"true" |
TS 24.379 [9] clause 10.1.4.4 |
||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.2-1A. |
||||
Table 6.1.4.2.3.3-14: SIP PUBLISH from the UE (step 8, Table 6.1.4.2.3.2-1;
step 2, TS 36.579-1 [2] Table 5.3.34.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.11-1 with condition PRESENCE-EVENT |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
MCPTT-Info |
|||
|
MIME-part-body |
MCPTT-Info as described in Table 6.1.4.2.3.3-15 |
|||
|
MIME body part |
PIDF |
|||
|
MIME-part-body |
PIDF as described in Table 6.1.4.2.3.3-16 |
|||
Table 6.1.4.2.3.3-15: MCPTT-Info in SIP PUBLISH (Table 6.1.4.2.3.3-14)
|
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_ID_User_A |
|||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-1A. |
||||
Table 6.1.4.2.3.3-16: PIDF in SIP PUBLISH (Table 6.1.4.2.3.3-14)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.5.1-1 condition AFFILIATION |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
..p-id |
any allowed value |
p-id shall be present acc. to TS 24.379 [9] clause 9.2.2.2.5 and clause 9.2.2.3.5 |
||
Table 6.1.4.2.3.3-17: SIP NOTIFY from the SS (step 10, Table 6.1.4.2.3.2-1;
step 4, TS 36.579-1 [2] Table 5.3.34.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1 with condition PRESENCE-EVENT |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
PIDF |
|||
|
MIME-part-body |
PIDF as described in Table 6.1.4.2.3.3-18 |
|||
Table 6.1.4.2.3.3-18: PIDF in SIP NOTIFY (Table 6.1.4.2.3.3-17)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.5.2-1 condition AFFILIATION |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
presence |
||||
|
tuple |
||||
|
status |
||||
|
affiliation |
||||
|
status |
affiliating |
|||
|
..p-id |
same value as received in corresponding SIP PUBLISH |
|||
Table 6.1.4.2.3.3-18A: SIP NOTIFY from the SS (step 12, Table 6.1.4.2.3.2-1;
step 6, TS 36.579-1 [2] Table 5.3.34.3-1)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.2.8-1 with condition PRESENCE-EVENT |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
Message-body |
||||
|
MIME body part |
PIDF |
|||
|
MIME-part-body |
PIDF as described in Table 6.1.4.2.3.3-18B |
|||
Table 6.1.4.2.3.3-18B: PIDF in SIP NOTIFY (Table 6.1.4.2.3.3-18A)
|
Derivation Path: TS 36.579-1 [2], Table 5.5.3.5.2-1 condition AFFILIATION |
||||
|
Information Element |
Value/remark |
Comment |
Reference |
Condition |
|
presence |
||||
|
tuple |
||||
|
status |
||||
|
affiliation |
||||
|
status |
affiliated |
|||
|
..p-id |
same value as received in corresponding SIP PUBLISH |
|||
Table 6.1.4.2.3.3-19: SIP MESSAGE from the UE (Step 13, Table 6.1.4.2.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 |
MCPTT-Info as described in Table 6.1.4.2.3.3-20 |
|||
Table 6.1.4.2.3.3-20: MCPTT-Info in SIP MESSAGE (Table 6.1.4.2.3.3-19)
|
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 MCPTT group identity to be selected by the targeted MCPTT user |
TS 24.379 [9] clause 10.1.4.2.2 |
|
|
anyExt |
||||
|
response-type |
"group-selection-change-response" |
TS 24.379 [9] clause 10.1.4.2.2 |
||
|
selected-group-change-outcome |
"success" |
TS 24.379 [9] clause 10.1.4.2.2 |
||
|
NOTE 1: Encrypted element as described in TS 36.579-1 [2] Table 5.5.3.2.1-1A. |
||||