Abstract:
To mitigate re-syncs, RLP sync control frames associated with a packet data session can be sequence numbered. A single sequence number can be assigned for an entire sync procedure associated with the initiation of a packet data session. For example, the sequence number can remains the same on all sync control frames (SYNC, SYNC/ACK, ACK) of a particular packet data session. When a sync frame is received out of order within a single sequence, it can be ignored under certain conditions. For example, if a SYNC frame with a sequence number 0 is received out of order after an ACK frame with sequence number 0 is received, the mobile station can ignore the out of order SYNC frame. Thus, an RLP re-sync is avoided due to out of order RLP sync packets.
Abstract:
Commonly, when a mobile device tethers to a computer, one Internet Protocol address is provided. When an embedded application runs continuously, such as with a Internet Protocol Multimedia Subsystem application, tethered applications can be prohibited from operating. If the continuous application is not active, then the continuous application can be disconnected and thus the tethered application can function.
Abstract:
To mitigate re-syncs, RLP sync control frames associated with a packet data session can be sequence numbered. A single sequence number can be assigned f or an entire sync procedure associated with the initiation of a packet data session. For example, the sequence number can remains the same on all sync control frames (SYNC, SYNC/ACK, ACK) of a particular packet data session. Wh en a sync frame is received out of order within a single sequence, it can be ignored under certain conditions. For example, if a SYNC frame with a sequen ce number 0 is received out of order after an ACK frame with sequence number 0 is received, the mobile station can ignore the out of order SYNC frame. Thus, a n RLP re-sync is avoided due to out of order RLP sync packets.
Abstract:
To mitigate re-syncs, RLP sync control frames associated with a packet data session can be sequence numbered. A single sequence number can be assigned for an entire sync procedure associated with the initiation of a packet data session. For example, the sequence number can remains the same on all sync control frames (SYNC, SYNC/ACK, ACK) of a particular packet data session. When a sync frame is received out of order within a single sequence, it can be ignored under certain conditions. For example, if a SYNC frame with a sequence number 0 is received out of order after an ACK frame with sequence number 0 is received, the mobile station can ignore the out of order SYNC frame. Thus, an RLP re-sync is avoided due to out of order RLP sync packets.
Abstract:
Techniques for maintaining an always-on data session for an access terminal are described. Messages to keep alive the data session may be sent using non-traffic channels to avoid bringing up traffic channels just to send these messages. In one design, an access network may send a first message (e.g., a RouteUpdateRequest message) on a first non-traffic channel (e.g., a control channel) to the access terminal. The access terminal may return a second message (e.g., a RouteUpdate message) on a second non-traffic channel (e.g., an access channel) to the access network. The access network may then send a third message (e.g., for an Echo-Request) on the first non-traffic channel over a smaller area covering an approximate location of the access terminal, which may be determined based on the second message. The access terminal may return a fourth message (e.g., for an Echo-Reply) on the second non-traffic channel to the access network.
Abstract:
Techniques to detect for end of service using dynamic inactivity timer thresholds are described. An access terminal establishes a radio connection for one or more applications. Data and signaling for the application(s) may be sent on one or more first flows (e.g., RLP flows) that may carry any number of second flows (e.g., IP flows). The access terminal determines a dynamic inactivity timer threshold for each first flow, e.g., based on at least one inactivity timer threshold for at least one second flow mapped to that first flow. The access terminal determines whether each first flow is inactive based on the inactivity timer threshold for that first flow, e.g., declares each first flow to be inactive if no activity is detected on that first flow for a period exceeding the inactivity timer threshold. The access terminal closes the radio connection when all first flow(s) are determined to be inactive.
Abstract:
To mitigate re-syncs, RLP sync control frames associated with a packet data session can be sequence numbered. A single sequence number can be assigned for an entire sync procedure associated with the initiation of a packet data session. For example, the sequence number can remains the same on all sync control frames (SYNC, SYNC/ACK, ACK) of a particular packet data session. When a sync frame is received out of order within a single sequence, it can be ignored under certain conditions. For example, if a SYNC frame with a sequence number 0 is received out of order after an ACK frame with sequence number 0 is received, the mobile station can ignore the out of order SYNC frame. Thus, an RLP re-sync is avoided due to out of order RLP sync packets.