Method and device for scheduling request in NB IoT systems
Abstract
A method and device for reporting scheduling request are provided. The method includes the operations of acquiring a dedicated physical resource of a random access channel (RACH) configured to report a scheduling request, when the scheduling request is triggered, transmitting the RACH on the dedicated physical resource. The dedicated physical resource includes a plurality of periodic physical resources. Through this dedicated physical resource, the user equipment (UE) can report scheduling request in a contention-free random access way, and the capacity of a preamble sequence is improved and inter-cell interference is reduced.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1. A method for reporting a scheduling request, the method comprising:
generating modulation symbols a i b i , based on multiplication of hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback a i with a codeword b i for the scheduling request; and
transmitting the modulation symbols on a narrowband physical uplink shared channel (NPUSCH),
wherein in case that the scheduling request is to be transmitted using NPUSCH format 2, the codeword for the scheduling request is b i ,i=0,1, . . . , 15.
2. The method of claim 1 , further comprising generating the HARQ-ACK feedback a i for the NPUSCH.
3. The method of claim 1 , wherein the method for reporting the scheduling request is provided in a narrowband IoT) system.
4. A method for receiving a scheduling request, the method comprising:
receiving modulation symbols on a narrowband physical uplink shared channel (NPUSCH), and
identifying hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback a and a codeword b, for the scheduling request, from the received modulation symbols,
wherein the modulation symbols, a i b i , are generated based on multiplication of the HARQ-ACK feedback a i with the codeword b i for the scheduling request,
in case that the scheduling request is to be transmitted using NPUSCH format 2, the codeword for the scheduling request is b i ,i=0,1, . . . , 15.
5. The method of claim 4 , wherein a method for receiving the scheduling request is provided in a narrowband IoT system.
6. A user equipment (UE) for reporting a scheduling request, the UE comprising:
a transceiver; and
a processor coupled with the transceiver and configured to:
generate modulation symbols a i b i , based on multiplication of hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback ca i with a codeword b i for the scheduling request, and
transmit the modulation symbols on a narrowband physical uplink shared channel (NPUSCH),
wherein in case that the scheduling request is to be transmitted using NPUSCH format 2, the codeword for the scheduling request is b i ,i=0,1, . . . , 15.
7. The UE of claim 6 , wherein the processor is further configured to generate the HARQ-ACK feedback a i for the NPUSCH.
8. The UE of claim 6 , wherein the UE for reporting the scheduling request is included in a narrowband IoT system.
9. An evolved node B (eNB) for receiving a scheduling request, the eNB comprising:
a transceiver; and
a processor coupled with the transceiver and configured to:
receive modulation symbols on a narrowband physical uplink shared channel (NPUSCH), and
identify hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback a i and a codeword b i for the scheduling request, from the received modulation symbols, wherein the modulation symbols, a i b i , are generated based on multiplication of the HARQ-ACK feedback a i with the codeword b i for the scheduling request, in case that the scheduling request is to be transmitted using NPUSCH format 2, the codeword for the scheduling request is b i ,i=0,1, . . . , 15.
10. The eNB of claim 9 , wherein the eNB for receiving the scheduling request is included in a narrowband IoT system.Join the waitlist — get patent alerts
Track US11824698B2 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.