US Patent Application 18018825. SEMI-PERSISTENT SCHEDULING IN LATENCY-SENSITIVE SYSTEMS simplified abstract
Contents
SEMI-PERSISTENT SCHEDULING IN LATENCY-SENSITIVE SYSTEMS
Organization Name
Inventor(s)
Kao-Peng Chou of Taoyuan City (TW)
SEMI-PERSISTENT SCHEDULING IN LATENCY-SENSITIVE SYSTEMS - A simplified explanation of the abstract
This abstract first appeared for US patent application 18018825 titled 'SEMI-PERSISTENT SCHEDULING IN LATENCY-SENSITIVE SYSTEMS
Simplified Explanation
The patent application describes techniques for processing data using semi-persistent scheduling. Here is a simplified explanation of the abstract:
- The techniques involve receiving transmissions and retransmissions of data associated with a periodically-scheduled occasion.
- If the data cannot be recovered from these transmissions, it is considered as undelivered.
- The undelivered data is then persisted in a buffer corresponding to the occasion for future recovery attempts.
- The persisted payload information is stored in the buffer for a longer period of time than the periodicity of the occasion.
- A retransmission timer prevents the persisted payload information from being overwritten or cleared.
- The persisted payload information can be reallocated to another buffer for better management.
Bullet points to explain the patent/innovation:
- Techniques for processing data in semi-persistent scheduling.
- Automatic retransmission of undelivered data is used.
- Failed data recovery results in persisting the transmission payload in a buffer.
- The persisted payload is stored for a longer time than the periodicity of the occasion.
- A retransmission timer prevents overwriting or clearing of the persisted payload.
- The persisted payload information can be reallocated to another buffer for better management.
Original Abstract Submitted
Techniques for processing data in accordance with semi-persistent scheduling include receiving, in accordance with a mechanism for automatic retransmission of undelivered data, one or more transmissions and/or retransmissions of data associated with a periodically-scheduled occasion (), failing to recover data from the (re)transmissions (), and persisting the (re)transmission payload(s) (e.g., in a combined form) in a buffer corresponding to the occasion for use in future attempts at recovering the data (), e.g., persisting the payload(s) over a length of time greater than a periodicity of the occurrences of the occasion. For example, the UE may utilize a retransmission timer () which, while activated, prevents the persisted payload information from being overwritten or cleared, and/or the UE may reallocate the persisted payload information from being maintained in the buffer initially associated with occasion to being maintained/persisted in another buffer ().