F.2 On-network timers
24.2823GPPMission Critical Data (MCData) signalling controlProtocol specificationRelease 18TS
F.2.1 Timers in the participating MCData function
Table F.2.1-1: Participating MCData function timers
Timer |
Timer value |
Cause of start |
Normal stop |
On expiry |
---|---|---|---|---|
TDP1 (SDS re-delivery timer) (NOTE) |
Default value: 60 seconds Configurable. |
On reception of a "SIP MESSAGE request for SDS disposition notification for MCData server" containing an SDS disposition notification type set to a value of "UNDELIVERED", |
On reception of a "SIP MESSAGE request for SDS disposition notification for MCData server" containing an SDS disposition notification type set to a value of "DELIVERED", "READ" or "DELIVERED AND READ" |
Re-deliver the SDS message to the MCData user. |
NOTE: More than one instance of this timer can be running in the participating MCData function, each instance associated with a specific SDS message. |
F.2.2 Timers in the controlling MCData function
Table F.2.2-1: Controlling MCData function timers
Timer |
Timer value |
Cause of start |
Normal stop |
On expiry |
---|---|---|---|---|
TDC1 (disposition notification timer) (NOTE 1) |
Default value: 5 seconds Configurable. |
On reception of a "SIP MESSAGE request for SDS disposition notification for MCData server" from a group member and aggregation of dispositions is required. |
On reception of a "SIP MESSAGE request for SDS disposition notification for MCData server" from a group member where aggregation of disposition notifications is required and all other disposition notifications have been received from all other group members |
Send the aggregated disposition notifications to the MCData user. |
TDC2 (file availability timer) (NOTE 2) |
(NOTE 3) |
On reception of an FD request using HTTP or using media plane. |
On reception of a "SIP MESSAGE request for FD disposition notification for MCData server" from all the invited member(s) and the FD disposition notification type IE is set to "FILE DOWNLOAD REQUEST REJECTED" |
Recipients are informed that the file is not available to download any longer as specified in clause 12.4.2.1 |
TDC3 (request for extension) |
Default value: 15 seconds Configurable. |
Upon receiving SIP 200 (OK) from MCData client for the SIP INFO / SIP MESSAGE message sent as intent to release communication |
Upon receiving request for extension of MCData communication from MCData client. |
Release the MCData communication immediately. |
NOTE 1: More than one instance of this timer can be running in the controlling MCData function, each instance associated with a specific group SDS message. NOTE 2: More than one instance of this timer can be running in the controlling MCData function associated with each file. Each timer for the file is associated uniquely to a Conversation ID and Message ID. NOTE 3: An FD request can contain metadata with "file availability" information. If the FD request contains "file availability", then the controlling MCData function uses this information to derive the timer value. If the FD request does not contain "file availability" information, then the controlling MCData function sets a value for the timer based upon local policy. |
F.2.3 Timers in the MCData UE
Table F.2.3-1: MCData UE timers
Timer |
Timer value |
Cause of start |
Normal stop |
On expiry |
---|---|---|---|---|
TDU1 (delivery and read) (NOTE) |
Default value: 120 milliseconds Configurable. |
When the client receives a SDS message with Disposition request type IE set to "DELIVERY AND READ". |
When a SDS message display indication is received. |
Send a SDS notification with Disposition type IE set to "DELIVERED" and when the MCData client has displayed the message to the MCData user, send a SDS notification with Disposition type IE set to "READ" |
TDU2 (FD non-mandatory download timer) (NOTE) |
Default value: 60 seconds Configurable. |
On reception of an FD request not indicating mandatory download as specified in clause 10.2.1.2.3 |
When the MCData user performs the action to accept, reject or defer the FD request as specified in clause 10.2.1.2.3 |
No specific action by the MCData UE. |
NOTE: Value of timer TDU1 (delivery and read) should be configured such that, when a consolidated "DELIVERED AND READ" notification is not feasible, the MCData client is able to send the "DELIVERED" disposition notification without delay. |