Abnormal case handling for acknowledged mode transmission and unacknowledged mode transmission

• US 20030223385A1
• Filed: 05/02/2003
• Published: 12/04/2003
• Est. Priority Date: 05/06/2002
• Status: Active Grant

• Current Assignee: Innovative Sonic Limited
• Original Assignee: Innovative Sonic Limited
• Inventors: Jiang, Sam Shiaw-Shiang
• Granted Patent: US 7,388,883 B2
• Time in Patent Office: Days
• US Class Current: 370/324
• CPC Class Codes: H04L 1/1628 List acknowledgements, i.e. the acknowledgement message consisting of a list of identifiers, e.g. of sequence numbers H04L1/1614 takes precedence
• CPC Class Codes: H04L 1/1664 the supervisory signal being transmitted together with payload signals; piggybacking
• CPC Class Codes: H04L 1/1685 the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
• CPC Class Codes: H04L 1/1809 Selective-repeat protocols
• CPC Class Codes: H04L 1/1832 Details of sliding window management
• CPC Class Codes: H04L 1/187 Details of sliding window management
• CPC Class Codes: H04W 99/00 Subject matter not provided for in other groups of this subclass

Abstract

Whenever the Receiver of this invention receives an AMD PDU or a UMD PDU with its “Length Indicator” having an invalid or a reserved value, the Receiver discards such a PDU and treats it as never received. The Receiver may report its receiving status accordingly if a report is required. This invention avoids invoking unnecessary RLC reset procedures and reduces the chance of losing HFN synchronization during AM or UM data transmissions.

Claims

1. A method to reduce the occurrences of RLC reset or the chance of losing HFN synchronization during data block transmission between the sender and the receiver in a wireless communication system, wherein data blocks may contain different status related fields, wherein the method comprising the steps of:

At the receiver;

receiving data block from the sender while the data transmission operation is in a particular mode;

determining the status of status related fields of the received data block; and

discarding the received data block and treating the discarded data block as if it has never been received if one particular status related field matches one of a plurality of abnormal conditions.

2. The method as claimed in claim 1, wherein the data transmission operation is in an Acknowledge mode.

3. The method as claimed in claim 1, wherein the data transmission operation is in an Unacknowledge mode.

4. The method as claimed in claim 2, wherein one particular status related field is the “

Length Indicator”

field.

5. The method as claimed in claim 4, wherein if one particular status related field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having an invalid value.

6. The method as claimed in claim 4, wherein if one particular status related field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having a reserved value.

7. The method as claimed in claim 4, wherein treating the data block as if it has never been received further comprising the steps of:

checking the “

Polling Bit”

field of the discarded received data block; and

if the “

Polling Bit”

indicates that a status report is requested, reporting a receiving status with the content set as the discarded data block has never been received.

8. The method as claimed in claim 3, wherein one particular status related field is the “

Length Indicator”

field.

9. The method as claimed in claim 8, wherein if one particular status related field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having an invalid value.

10. The method as claimed in claim 8, wherein if one particular status field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having a reserved value.

11. A receiver for reducing the occurrences of RLC reset or the chance of losing HFN synchronization during data block transmission between the sender and the receiver in a wireless communication system, wherein data blocks may contain different status related fields, wherein the receiver comprising:

means for receiving data block from the sender while the data transmission operation is in a particular mode;

means for determining the status of status related fields of the received data block; and

means for discarding the received data block and treating the discarded data block as if it has never been received if one particular status related field matches one of a plurality of abnormal conditions.

12. The receiver as claimed in claim 11, wherein the data transmission operation is in an Acknowledge mode.

13. The receiver as claimed in claim 11, wherein the data transmission operation is in an Unacknowledge mode.

14. The receiver as claimed in claim 12, wherein one particular status related field is the “

Length Indicator”

field.

15. The receiver as claimed in claim 14, wherein if one particular status related field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having an invalid value.

16. The receiver as claimed in claim 14, wherein if one particular status related field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having a reserved value.

17. The receiver as claimed in claim 14, wherein treating the data block as if it has never been received further comprising:

means for checking the “

Polling Bit”

field of the discarded received data block; and

if the “

Polling Bit”

indicates that a status report is requested, means for reporting a receiving status with the content set as the discarded data block has never been received.

18. The receiver as claimed in claim 13, wherein one particular status related field is the “

Length Indicator”

field.

19. The receiver as claimed in claim 18, wherein if one particular status related field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having an invalid value.

20. The receiver as claimed in claim 18, wherein if one particular status field matches one of a plurality of abnormal conditions further comprising of the “

Length Indicator”

having a reserved value.