CONTENTION-BASED TRANSMISSION WITH CONTENTION-FREE FEEDBACK FOR REDUCING LATENCY IN LTE ADVANCED NETWORKS AND ENHANCED PUCCH

• US 20140140304A1
• Filed: 01/27/2014
• Published: 05/22/2014
• Est. Priority Date: 03/05/2010
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Yang, Xiangying, Zhu, Yuan, Li, Qinghua
• Granted Patent: US 9,578,659 B2
• Time in Patent Office: Days
• US Class Current: 370/329
• CPC Class Codes: H03M 13/09 Error detection only, e.g. using cyclic redundancy check [CRC] codes or single parity bit
• CPC Class Codes: H03M 13/29 combining two or more codes or code structures, e.g. product codes, generalised product codes, concatenated codes, inner and outer codes
• CPC Class Codes: H04L 1/0041 Arrangements at the transmitter end
• CPC Class Codes: H04L 1/0061 Error detection codes
• CPC Class Codes: H04L 1/0073 Special arrangements for feedback channel
• CPC Class Codes: H04L 2001/125 Arrangements for preventing errors in the return channel
• CPC Class Codes: H04L 2463/061 applying further key derivation, e.g. deriving traffic keys from a pair-wise master key cryptographic mechanisms or cryptographic arrangements for generation of secret information including derivation or calculation of cryptographic keys or passwords H04L9/0861
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04W 12/062 Pre-authentication
• CPC Class Codes: H04W 28/04 Error control
• CPC Class Codes: H04W 36/0038 of security context information
• CPC Class Codes: H04W 72/21 in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 74/0833 Random access procedures, e.g. with 4-step access
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

Methods for contention-based transmission with contention-free feedback for reduced latency in LTE Advanced networks and an enhanced PUCCH are generally disclosed herein. User equipment (UE) may transmit a contention sequence on a physical uplink control channel (PUCCH) to an enhanced-Node B (eNB) and may concurrently transmit data requesting uplink resources on a physical uplink shared channel (PUSCH) to the eNB. The contention sequence is transmitted on the PUCCH in accordance with a format that is assigned by the eNB. The contention sequence is either randomly selected by the UE or assigned by the eNB. When the contention sequence and data are not successfully received by the eNB, the UE may fall back to a more conventional random access channel (RACH) procedure for uplink resource allocation.

Claims

1. (canceled)

7. The method of claim 1 wherein the user does not include a request for channel resources.

8. The method of claim 1 further comprising transmitting the user data on the allocated PUSCH channel resources directly to another UE in accordance with power constraint information provided by the eNB,

wherein the allocated PUSCH channel resources are within licensed spectrum.

2. A method performed by user equipment (UE) for random access transmission of user data, the method comprising:

receiving an allocation of physical uplink shared channel (PUSCH) resources from an enhanced or evolved is B (eNB) for random access; and

transmitting a contention sequence and user data on the allocated resources in accordance with a random-access technique.

3. The method of claim 2 further comprising:

performing a procedure for grant of PUSCH resources for use in accordance with a non-random access technique when the user data is not successfully received; and

refraining from performing a procedure for grant of PUSCH resources for use in accordance with a non-random access technique when the user data is successfully received.

4. The method of claim 3 wherein the procedure for grant of PUSCH resources is a random-access channel (RACH) procedure.

5. The method of claim 3 wherein the procedure for grant of PUSCH resources is a scheduling request (SR) procedure,

wherein the scheduling request procedure is performed to receive a grant of exclusive PUSCH resources for use in accordance with the non-random access technique.

6. The method of claim 5 wherein a scheduling request procedure is performed when the contention sequence had been successfully received and when the user data was not successfully received.

9. A method performed by user equipment (UE) comprising:

receiving an allocation of physical uplink shared channel (PUSCH) resources from an enhanced or evolved Node B (eNB); and

transmitting a sequence and a payload within the allocated PUSCH resources for receipt by another UE.

10. The method of claim 9 wherein the sequence comprises an uplink reference signal that is transmitted within a reference signal portion of the allocated PUSCH resources,

wherein the payload is transmitted with a data portion of the allocated PUSCH resources, and

wherein the user data does not include a request for channel resources.

11. The method of claim 9 wherein the sequence is a demodulation reference sequence (DM-RS).

12. The method of claim 9 wherein the sequence is a contention sequence.

13. The method of claim 9 wherein the allocation of PUSCH resources is a non-exclusive allocation, and

wherein the sequence and the payload are transmitted in accordance with a random-access technique.

14. The method of claim 9 wherein the allocation of PUSCH resources is received for use in device-to-device UE discovery and communication, and

wherein the sequence and the payload are transmitted within the allocated PUSCH resources for receipt directly by another UE without involvement of the eNB.

15. The method of claim 9 further comprising communicating with the another UE within additional allocated PUSCH resources.

16. The method of claim 14 further comprising performing a device discovery process to identify the another UE

17. The method of claim 16 further comprising performing proximity sensing to identify the another UE.

18. The method of claim 9 wherein transmitting the user data comprises transmitting the user data on the allocated PUSCH resources directly to another UE in accordance with power constraint information provided by the eNB, and

wherein the allocated PUSCH resources are within licensed spectrum.

19. The method of claim 9 wherein prior to receiving the allocation of PUSCH resources, the method includes:

performing a procedure for grant of PUSCH resources in accordance with a random-access channel (RACH) procedure.

20. The method of claim 9 wherein prior to receiving the allocation of PUSCH resources, the method includes performing a procedure for grant of PUSCH resources in accordance with a scheduling request (SR) procedure.

21. The method of claim 9 further comprising receiving a second sequence within a reference signal portion and a second payload within a data portion of the allocated PUSCH resources from another UE,

wherein the second sequence is a demodulation reference sequence (DM-RS).

22. User equipment (UE) comprising a transceiver arranged to:

receive an allocation of physical uplink shared channel (PUSCH) resources from an enhanced or evolved Node B (eNB); and

transmit a sequence and a payload within the allocated PUSCH resources for receipt by another UE.

23. The UE of claim 22 wherein the sequence comprises an uplink reference signal that is transmitted within a reference signal portion of the allocated PUSCH resources,

wherein the payload is transmitted with a data portion of the allocated PUSCH resources, and

wherein the user data does not include a request for channel resources.

24. The UE of claim 22 wherein the sequence is a demodulation reference sequence (DM-RS).

25. The LIE of claim 22 wherein the allocation of PUSCH resources is a non-exclusive allocation, and

wherein the sequence and the payload are transmitted in accordance with a random-access technique.

26. The UE of claim 25 wherein the allocation of PUSCH resources is received for use in device-to-device UE discovery and communication, and

wherein the sequence and the payload are transmitted within the allocated PUSCH resources for receipt directly by another UE without involvement of the eNB.

27. The UE of claim 26 wherein the user data is transmitted on the allocated PUSCH resources directly to another UE in accordance with power constraint information provided by the eNB, and

wherein the allocated PUSCH resources are within licensed spectrum.