14 Enhanced Status (ES)

24.2823GPPMission Critical Data (MCData) signalling controlProtocol specificationRelease 18TS

14.1 General

14.2 On-network ES

14.2.1 MCData client procedures

14.2.1.1 MCData client originating procedures

Upon receiving a request from the MCData user to send an enhanced status to an MCData group and the <mcdata-allow-enhanced-status> element under the <list-service> element as defined in 3GPP TS 24.481 [11] is set to "true", the MCData client:

1) shall use the "id" attribute of the MCData user selected operation value from <mcdata-enhanced-status-operational-values> element under <list-service> element as defined in 3GPP TS 24.481 [11], to generate a group standalone SDS message by following the procedure described in clause 9.2.2.2.1.

14.2.1.2 MCData client terminating procedures

Upon receiving a "SIP MESSAGE request for standalone SDS for terminating MCData client", the MCData client:

1) shall follow the procedure defined in clause 9.2.2.2.2;

2) shall match the received value with an "id" attribute of the operational values from the <mcdata-enhanced-status-operational-values> element of the MCData group document as defined in 3GPP TS 24.481 [11]; and

3) if a match is found, shall render the operational value as enhanced status to the MCData user. Otherwise shall discard the received message.

14.2.2 Participating MCData function procedures

14.2.2.1 Originating participating MCData function procedures

Upon receipt of a "SIP MESSAGE request for standalone SDS for originating participating MCData function", the participating MCData function should follow the procedure described in clause 9.2.2.3.1.

14.2.2.2 Terminating participating MCData function procedures

Upon receipt of a "SIP MESSAGE request for standalone SDS for terminating participating MCData function", the participating MCData function should follow the procedure described in clause 9.2.2.3.2.

14.2.3 Controlling MCData function procedures

14.2.3.1 Originating controlling MCData function procedures

Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the controlling MCData function should follow the procedure described in clause 9.2.2.4.1.1.

14.2.3.2 Terminating controlling MCData function procedures

Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the controlling MCData function should follow the procedure described in clause 9.2.2.4.2.

14.3 Off-network ES

14.3.1 Sending enhanced status message

Upon receiving request from MCData user to share enhanced for selected group:

1) if the value of "/<x>/<x>/Common/MCData/AllowedEnhSvc" leaf node present in the group configuration as specified in 3GPP TS 24.483 [4] is set to "true" for the MCData group, the MCData client:

a) shall use "/<x>/<x>/Common/MCData/EnhSvcOpValues/<x>/EnhSvcOpID" leaf node associated with user selected enhanced status operation value present in the group configuration as specified in 3GPP TS 24.483 [2] to generate a group standalone SDS message by following the procedure described in clause 9.3.2.2.

14.3.2 Receiving enhanced status message

Upon receipt of a SDS OFF-NETWORK MESSAGE message, the MCData client:

1) shall follow the procedure defined in clause 9.3.2.4;

2) shall attempt to match the received value with a "/<x>/<x>/Common/MCData/EnhSvcOpValues/<x>/EnhSvcOpID" leaf node present in the group configuration as specified in 3GPP TS 24.483 [2]; and

3) if a match is found, shall render the associated operational value from "/<x>/<x>/Common/MCData/EnhSvcOpValues/<x>/EnhSvcOpValue" leaf node as enhanced status to the MCData user.