Abstract
A method in a user equipment for requesting that a base station schedule the user equipment for an uplink data transmission to the base station is provided. The user equipment comprises a buffer. Directly or indirectly responsive to receiving data into the buffer to be transmitted to the base station the user equipment generates a scheduling request trigger. The scheduling request trigger is configured to trigger the sending of a scheduling request to the base station if the trigger is pending at the next scheduling request opportunity and to remain pending until it is cancelled. The user equipment cancels the pending scheduling request trigger when the data is accounted for in a buffer status report which reports the size of the buffer to the base station or when the data is included directly in a scheduled uplink data transmission whichever occurs first.
| Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Number | ||||||
| 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | Yes | Basis Patent | ||||
Specification Information
Specification Information
Technologies
Family Information
| All Granted Patents In Patent Family : | ---- |
| All Pending Patents In Patent Family : | ---- |
| Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Number | |||||||
| WO2010128927A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | Yes | Basis Patent | ||||
| WO2010128927A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| US2010284354A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| US2010284354A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | Yes | Basis Patent | ||||
| TW201116122A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| TW201116122A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| TWI477176B | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| TWI477176B | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| CA2760962A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| CA2760962A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| CA2760962C | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| CA2760962C | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| AU2010245353A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| AU2010245353A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| AU2010245353B2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| AU2010245353B2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| EP2428091A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| EP2428091A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| EP2428091A4 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| EP2428091A4 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| EP2428091B1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| EP2428091B1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| MX2011010865A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| MX2011010865A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| KR101582708B1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| KR101582708B1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| KR20120027220A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| KR20120027220A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| MA33263B1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| MA33263B1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| JP2012526450A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| JP2012526450A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| JP5667167B2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| JP5667167B2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| CN102422699A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| CN102422699A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| CN102422699B | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| CN102422699B | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| RU2011149331A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| RU2011149331A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| RU2517434C2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| RU2517434C2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| CN104320857A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| CN104320857A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| HK1169540A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| HK1169540A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| HK1206532A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| HK1206532A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| IL215207A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| IL215207A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| JP2015084564A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| JP2015084564A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| JP6018165B2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| JP6018165B2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| NZ595244A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| NZ595244A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| SG174863A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| SG174863A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| US2015063278A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| US2015063278A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| US9307553B2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| US9307553B2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| DK2428091T3 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| DK2428091T3 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| ES2568219T3 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| ES2568219T3 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| BRPI1014593A2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| BRPI1014593A2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| US2016165633A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| US2016165633A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| US9844071B2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| US9844071B2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| ZA201106850B | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| ZA201106850B | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| EP3094148A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| HUE028634T2 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| US2018098344A1 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| US2018098344A1 | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| MY164920A | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| MY164920A | 5G | 18/05/2017 | ISLD-201705-002 | ERICSSON INC | No | Family Member | ||||
| EP3094148B1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| BRPI1014593B1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| CN104320857B | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| DK3681234T3 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| EP3681234B1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| ES2784476T3 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| ES2891586T3 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| HUE049123T2 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| PL2428091T3 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| PL3094148T3 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| PL3681234T3 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| PT3094148T | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| US10375721B2 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| US2019327758A1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| US10904911B2 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| US2021219323A1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | Status | National Phase Entries | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Information | |||||||||
| ----- | ----- | ----- | ----- | ----- |
S1
|
----- | ----- | ----- | ----- | |||
Technologies
Resource configuration Scheduling
Product
User Equipment (UE/Terminal)
Use Cases
Wireless communication
Services
Transmitting/receiving data in uplink
Claim
1. A method in a user equipment for requesting that a base station schedule the user equipment for an uplink data transmission to the base station, the user equipment comprising a buffer, the method comprising:
receiving data into said buffer that is to be transmitted to the base station via a scheduled uplink data transmission; and
sending a scheduling request to the base station when a next scheduling request opportunity occurs, only if the buffer contains data that has both not been accounted for in a buffer status report, which reports the size of said buffer to the base station, and will not be included directly in a currently scheduled uplink data transmission.', 'receiving data into said buffer that is to be transmitted to the base station via a scheduled uplink data transmission; and', 'sending a scheduling request to the base station when a next scheduling request opportunity occurs, only if the buffer contains data that has both not been accounted for in a buffer status report, which reports the size of said buffer to the base station, and will not be included directly in a currently scheduled uplink data transmission.
2. The method of claim 1, wherein the sending a scheduling request to the base station comprises:
generating a scheduling request trigger directly, or indirectly, responsive to the arrival of said data into said buffer, the scheduling request trigger configured to trigger the sending of a scheduling request to the base station if the trigger is pending at the next scheduling request opportunity and to remain pending until it is cancelled, and
cancelling the pending scheduling request trigger when said data is accounted for in a buffer status report, or when said data will be included directly in a currently scheduled uplink data transmission, whichever occurs first; and
sending a scheduling request to the base station when a next scheduling request opportunity occurs, only if a scheduling request trigger is pending at that next scheduling request opportunity.', 'generating a scheduling request trigger directly, or indirectly, responsive to the arrival of said data into said buffer, the scheduling request trigger configured to trigger the sending of a scheduling request to the base station if the trigger is pending at the next scheduling request opportunity and to remain pending until it is cancelled, and', 'cancelling the pending scheduling request trigger when said data is accounted for in a buffer status report, or when said data will be included directly in a currently scheduled uplink data transmission, whichever occurs first; and', 'sending a scheduling request to the base station when a next scheduling request opportunity occurs, only if a scheduling request trigger is pending at that next scheduling request opportunity.
3. The method of claim 2, wherein generating a scheduling request trigger directly, or indirectly, responsive to the arrival of said data into said buffer comprises:
generating a buffer status report trigger responsive to the arrival of said data into said buffer, the buffer status report trigger configured to trigger the generation of a buffer status report; and
generating the scheduling request trigger indirectly responsive to the arrival of said data, by generating the scheduling request trigger responsive to the generation of said buffer status report trigger.', 'generating a buffer status report trigger responsive to the arrival of said data into said buffer, the buffer status report trigger configured to trigger the generation of a buffer status report; and', 'generating the scheduling request trigger indirectly responsive to the arrival of said data, by generating the scheduling request trigger responsive to the generation of said buffer status report trigger.
4. The method of claim 3, wherein cancelling the pending scheduling request trigger comprises cancelling the buffer status report trigger, which in turn triggers the canceling of the scheduling request trigger.
5. The method of claim 1, wherein the sending a scheduling request to the base station comprises:
tracking what data in said buffer has been accounted for in a buffer status report and what data in said buffer has been included directly in a currently scheduled uplink data transmission; and
tracking what data has both not been accounted for in said buffer status report and will not be included directly in said currently scheduled uplink data transmission.', 'tracking what data in said buffer has been accounted for in a buffer status report and what data in said buffer has been included directly in a currently scheduled uplink data transmission; and', 'tracking what data has both not been accounted for in said buffer status report and will not be included directly in said currently scheduled uplink data transmission.
6. The method of claim 1, wherein sending a scheduling request to the base station comprises sending a scheduling request to the base station only if the buffer contains data that has both not been accounted for in a buffer status report and will not be included directly in a packet data unit that is currently scheduled to be transmitted to the base station.
7. A user equipment configured to request that a base station schedule the user equipment for an uplink data transmission to the base station, the user equipment comprising:
a buffer configured to receive data to be transmitted to a base station via a scheduled uplink transmission; and
a sending circuit configured to send a scheduling request to the base station when a next scheduling request opportunity occurs only if the buffer contains data that has both not been accounted for in a buffer status report, which reports the size of said buffer to the base station, and will not be included directly in a currently scheduled uplink data transmission.', 'a buffer configured to receive data to be transmitted to a base station via a scheduled uplink transmission; and', 'a sending circuit configured to send a scheduling request to the base station when a next scheduling request opportunity occurs only if the buffer contains data that has both not been accounted for in a buffer status report, which reports the size of said buffer to the base station, and will not be included directly in a currently scheduled uplink data transmission.
8. The user equipment of claim 7:
further comprising a generating circuit configured to generate a scheduling request trigger directly, or indirectly, responsive to the arrival of said data into said buffer, the scheduling request trigger configured to trigger the sending of a scheduling request to the base station if the trigger is pending at the next scheduling request opportunity and to remain pending until it is cancelled, and
further comprising a cancelling circuit configured to cancel the pending scheduling request trigger when said data is accounted for in a buffer status report, or when said data will be included in a currently scheduled uplink data transmission, whichever occurs first; and
wherein the sending circuit is configured to send a scheduling request to the base station when a next scheduling request opportunity occurs, if and only if a scheduling request trigger is pending at that next scheduling request opportunity.', 'further comprising a generating circuit configured to generate a scheduling request trigger directly, or indirectly, responsive to the arrival of said data into said buffer, the scheduling request trigger configured to trigger the sending of a scheduling request to the base station if the trigger is pending at the next scheduling request opportunity and to remain pending until it is cancelled, and', 'further comprising a cancelling circuit configured to cancel the pending scheduling request trigger when said data is accounted for in a buffer status report, or when said data will be included in a currently scheduled uplink data transmission, whichever occurs first; and', 'wherein the sending circuit is configured to send a scheduling request to the base station when a next scheduling request opportunity occurs, if and only if a scheduling request trigger is pending at that next scheduling request opportunity.', '9. The user equipment of claim 8, wherein the generation circuit is configured to generate a scheduling request trigger indirectly responsive to the arrival of said data into said buffer, by:
generating a buffer status report trigger responsive to the arrival of said data into said buffer, the buffer status report trigger configured to trigger the generation of a buffer status report; and
generating the scheduling request trigger responsive to the generation of said buffer status report trigger.', 'generating a buffer status report trigger responsive to the arrival of said data into said buffer, the buffer status report trigger configured to trigger the generation of a buffer status report; and', 'generating the scheduling request trigger responsive to the generation of said buffer status report trigger.', '10. The user equipment of claim 9, wherein the cancellation circuit is configured to cancel the pending scheduling request trigger by cancelling the buffer status report trigger, which in turn triggers the canceling of the scheduling request trigger.', '11. The user equipment of claim 7:
further comprising a cancellation circuit configured to track what data in said buffer has been accounted for in a buffer status report and what data in said buffer will be included directly in a currently scheduled uplink data transmission, and to track what data has both not been accounted for in said buffer status report and will not be included directly in said currently scheduled uplink data transmission; and
wherein the sending circuit is configured to send a scheduling request to the base station when a next scheduling request opportunity occurs, only if the buffer contains data that has both not been accounted for in a buffer status report and will not be included directly in a currently scheduled uplink data transmission, as indicated by said tracking in said cancellation circuit.', 'further comprising a cancellation circuit configured to track what data in said buffer has been accounted for in a buffer status report and what data in said buffer will be included directly in a currently scheduled uplink data transmission, and to track what data has both not been accounted for in said buffer status report and will not be included directly in said currently scheduled uplink data transmission; and', 'wherein the sending circuit is configured to send a scheduling request to the base station when a next scheduling request opportunity occurs, only if the buffer contains data that has both not been accounted for in a buffer status report and will not be included directly in a currently scheduled uplink data transmission, as indicated by said tracking in said cancellation circuit.', '12. The user equipment of claim 7, wherein the sending circuit is configured to send a scheduling request to the base station when a next scheduling request opportunity occurs only if the buffer comprises data that has both not been accounted for in a buffer status report and will not be included directly in a packet data unit that is currently scheduled to be transmitted to the base station.']
Associated Portfolios
Licensor Claim Chart
 Claim Chart |
 Technology |
 Creation Date |
 Download |
|---|---|---|---|
|
Claim charts will soon be available!
|
|||
SUMMARY
ClaimChart-US8913565B2-STO
Patent number:US8913565B2
Claim Chart Type : SEP Claim Chart
Price: 200 €
To view claim charts you must become a Gold or Platinum Member.
Upgrade your subscriptionYou have reached the maximum number of patents which can be associated to your account per your subscription. If you wish to associate more patents
Please upgrade your subscription.Note:
The information in blue was extracted from the third parties (Standard Setting Organisation, Espacenet)
The information in grey was provided by the patent holder
The information in purple was extracted from the FrandAvenue
Explicitly disclosed patent:openly and comprehensibly describes all details of the invention in the patent document.
Implicitly disclosed patent:does not explicitly state certain aspects of the invention, but still allows for these to be inferred from the information provided.
Basis patent:The core patent in a family, outlining the fundamental invention from which related patents or applications originate.
Family member:related patents or applications that share a common priority or original filing.