Description
Waiting Time eXtension (WTX) is a specific mechanism defined within the Wireless Application Protocol (WAP) Push framework, which is part of the Push Access Protocol (PAP). It is not a standalone protocol but a parameter or feature used during a push transaction. The primary scenario involves a Push Initiator (e.g., a content server) sending a push message, specifically a Service Indication (SI), to a WAP client via a Push Proxy Gateway (PPG). An SI typically contains a short message and a URI; upon receipt, the client device notifies the user (e.g., via a pop-up or sound) and waits for the user to decide whether to activate (fetch) the content from the provided URI.
The core issue WTX addresses is the management of the 'waiting time' during this user interaction. The original push submission from the Push Initiator to the PPG includes a parameter called 'Push Expiration Time,' which defines the maximum lifetime of the push message within the network. Separately, when the PPG delivers the SI to the client, it includes a 'Client Wait Time' parameter, instructing the client on how long it should wait for the user to respond to the notification before considering the push interaction expired. If the user does not respond within this Client Wait Time, the client may discard the notification. However, a user might see the notification but need more time to decide or to get to a stable connection before activating it.
The WTX mechanism allows the WAP client to request an extension of this waiting period from the PPG. When the initial Client Wait Time is about to expire and the user has still not acted, but the client wishes to keep the notification active (e.g., the user has seen it but not dismissed it), the client can send a WTX request message back to the PPG. This request asks for a specific time extension. The PPG, upon receiving a valid WTX request, can grant the extension by responding with a new, later expiration time. This process effectively renews the lease on the push transaction, preventing the premature expiration of the service indication and giving the user more time to act without the server-side Push Initiator needing to resend the entire push message. It is a user-centric feature that enhances the usability of push services in mobile environments where user attention may be intermittent.
Purpose & Motivation
WTX was created to solve a specific usability problem in the WAP Push service model, particularly for Service Indications. In early mobile devices, processing power and screen real estate were limited, and users might be interrupted during other tasks. The standard push model had a rigid timing structure: the network (PPG) would hold the message for a certain time, and the client would display a notification for a fixed, client-side timer duration. If the user was notified but needed more time to decide (e.g., during a meeting, while driving, or due to a temporary loss of signal), the notification could disappear, and the opportunity to easily access the pushed content would be lost, potentially requiring the server to re-push the message.
This limitation degraded the user experience for time-sensitive but not instant push services like news alerts, score updates, or email notifications. The WTX mechanism provided a graceful way to extend the interactive window without involving the original Push Initiator, reducing network signaling and server load. It acknowledged the mobile usage context where immediate action is not always possible or desirable. By allowing the client to negotiate more time directly with the PPG, it made the push service more flexible and user-friendly, increasing the likelihood of user engagement with pushed content. It addressed the mismatch between network-level expiration timers and real-world human response times.
Key Features
- Allows a WAP client to request an extension of the Client Wait Time for a pending Service Indication
- Negotiation occurs directly between the client and the Push Proxy Gateway (PPG), without involving the Push Initiator
- Prevents premature expiration of user notifications, improving service usability
- Uses specific control messages within the WAP Push protocol framework
- Helps conserve network resources by avoiding unnecessary retransmissions of push messages from the server
- Enhances the user experience for interactive push services on constrained mobile devices
Evolution Across Releases
Introduced the Waiting Time eXtension (WTX) mechanism as part of the WAP Push specifications. Defined the WTX request and response message formats within the Push Access Protocol (PAP) and client-PPG interaction. Established the use case for extending the client-side waiting period for Service Indications to improve user interaction.
Mechanism maintained for backward compatibility. The relevance of WTX decreased as smartphone operating systems developed their own, more sophisticated push notification systems (e.g., Apple Push Notification service, Google Cloud Messaging) that managed timing and persistence differently.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |