Abstract
A method in a user equipment for handling a scheduling request trigger is provided. The user equipment comprises a buffer. After receiving (501) data arriving into the buffer to be transmitted to a base station the user equipment generates (503) a scheduling request trigger. The scheduling request trigger is pending until it is cancelled and is triggered directly or indirectly by the arrived data. The user equipment cancels (504) the pending scheduling request trigger when the data that triggered the generation of the scheduling request trigger is accounted for in a buffer status report to be included in a scheduled data transmission to be transmitted to the base station or when the data that triggered the generation of the scheduling request is included in a scheduled data transmission to be transmitted to the base station whichever occurs first.
A method in a user equipment for handling a scheduling request trigger is provided. The user equipment comprises a buffer. After receiving (501) data arriving into the buffer to be transmitted to a base station the user equipment generates (503) a scheduling request trigger. The scheduling request trigger is pending until it is cancelled and is triggered directly or indirectly by the arrived data. The user equipment cancels (504) the pending scheduling request trigger when the data that triggered the generation of the scheduling request trigger is accounted for in a buffer status report to be included in a scheduled data transmission to be transmitted to the base station or when the data that triggered the generation of the scheduling request is included in a scheduled data transmission to be transmitted to the base station 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 | No | Family Member | ||||
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 | ||||
| US8913565B2 | 4G | 19/12/2010 | ISLD-201101-002 | ERICSSON INC | No | Family Member | ||||
| US8913565B2 | 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 | ||||
| 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 (120) for handling a scheduling request trigger, the user equipment (120) comprising a buffer (900), the method comprising: receiving (501) data to be transmitted to a base station (110), which data arrives into the buffer (900), generating (503) a scheduling request trigger, which scheduling request trigger is pending until it is cancelled, and which generating is triggered directly or indirectly by the arrived data, cancelling (504) the pending scheduling request trigger when the data that triggered the generation of the scheduling request trigger is accounted for in a buffer status report to be included in a scheduled data transmission to be transmitted to the base station (110), or when the data that triggered the generation of the scheduling request is included in a scheduled data transmission to be transmitted to the base station (110), whichever occurs first.
2. Method according to claim 1 , further comprising: generating (502) a buffer status report trigger, which generation of buffer status report trigger is triggered by the arrived data, and wherein the step of generating (503) a scheduling request trigger is performed indirectly by the arrived data, by being triggered by the generation of the buffer status report trigger which in turn was triggered by the arrived data.
3. Method according to claim 2, wherein the step of cancelling (504) is performed by cancelling the buffer status report trigger, which in turn triggers the canceling of the scheduling request trigger.
4. A method in a user equipment (120) for handling a scheduling request trigger, the user equipment (120) comprising a buffer (900), the method comprising: receiving (501) data to be transmitted to a base station (110), which data arrives into the buffer (900), generating (503) a scheduling request trigger, which scheduling request trigger is pending until it is cancelled, and which generating is triggered directly or indirectly by the arrived data, cancelling (505) the pending scheduling request trigger at any time, but keeping track of what data that has either been accounted for in the buffer status report to be included in a scheduled data transmission or included directly in the scheduled data transmission and what data that has not been accounted for in any of these two ways, and when a next scheduling request opportunity appears, sending (506) a scheduling request if and only if the buffer comprises data that has not yet been accounted for in any of the two ways mentioned.
5. Method according to claim 4, further comprising: generating (502) a buffer status report trigger, which generation of buffer status report trigger is triggered by the arrived data, and wherein the step of generating (503) a scheduling request trigger is performed indirectly by the arrived data, by being triggered by the generation of the buffer status report trigger which in turn was triggered by the arrived data.
6. Method according to claim 5, wherein the steps of cancelling (505) is performed by cancelling the buffer status report trigger, which in turn triggers the canceling of the scheduling request trigger.
7. A method in a user equipment (120) for handling a scheduling request trigger, the user equipment (120) comprising a buffer (900), the method comprising: receiving (501) data to be transmitted to a base station (110), which data arrives into the buffer (900), generating (503) a scheduling request trigger, which scheduling request trigger is pending until it is cancelled, and which generating is triggered directly or indirectly by the arrived data, cancelling (504) the pending scheduling request trigger when the data that triggered the generation of the scheduling request trigger is accounted for in a buffer status report to be included in a scheduled data transmission to be transmitted to the base station (110), or when the data that triggered the generation of the scheduling request is included in a scheduled data transmission to be transmitted to the base station (110), whichever occurs first, or alternatively cancelling (505) the pending scheduling request trigger at any time, but keeping track of what data that has been accounted for in the buffer status report to be included in a scheduled data transmission and what data that has not been accounted for, and when a next scheduling request opportunity appears, sending (506) a scheduling request if and only if the buffer comprises data that has not yet been accounted for in the buffer status report.
8. Method according to claim 7, further comprising: generating (502) a buffer status report trigger, which generation of buffer status report trigger is triggered by the arrived data, and wherein the step of generating (503) a scheduling request trigger is performed indirectly by the arrived data, by being triggered by the generation of the buffer status report trigger which in turn was triggered by the arrived data.
9. Method according to claim 8, wherein the steps of cancelling (504,505) are performed by cancelling the buffer status report trigger, which in turn triggers the canceling of the scheduling request trigger
10. A user equipment (120) for handling a scheduling request trigger, the user equipment (120) comprising: a buffer (900) configured to receive data to be transmitted to a base station (110), a generating unit (920) configured to generate a scheduling request trigger, which scheduling request trigger is pending until it is cancelled, and which generating is triggered directly or indirectly by the arrived data, a cancelling unit (930) configured to cancel the pending scheduling request trigger when the data that triggered the generation of the scheduling request trigger is accounted for in a buffer status report to be included in a scheduled data transmission to be transmitted to the base station (110), or when the data that triggered the generation of the scheduling request is included in a scheduled data transmission to be transmitted to the base station (110), whichever occurs first
11. A user equipment (120) for handling a scheduling request trigger, the user equipment (120) comprising: a buffer (900) configured to receive data to be transmitted to a base station (110), a generating unit (920) configured to generate a scheduling request trigger, which scheduling request trigger is pending until it is cancelled, and which generating is triggered directly or indirectly by the arrived data, a cancelling unit (930) configured to cancel the pending scheduling request trigger at any time, but keeping track of what data that has either been accounted for in the buffer status report to be included in a scheduled data transmission or included directly in the scheduled data transmission and what data that has not been accounted for in any of these two ways, and the user equipment (120) further comprising a sending unit (940) configured to, when a next scheduling request opportunity appears, send a scheduling request if and only if the buffer comprises data that has not yet been accounted for in any of the two ways mentioned
12. A user equipment (120) for handling a scheduling request trigger, the user equipment (120) comprising: a buffer (900) configured to receive data to be transmitted to a base station', '(110), which data arrives into the buffer (900), a generating unit (920) configured to generate a scheduling request trigger, which scheduling request trigger is pending until it is cancelled, and which generating is triggered directly or indirectly by the arrived data, a cancelling unit (930) configured to cancel the pending scheduling request trigger when the data that triggered the generation of the scheduling request trigger is accounted for in a buffer status report to be included in a scheduled data transmission to be transmitted to the base station (110), or when the data that triggered the generation of the scheduling request is included in a scheduled data transmission to be transmitted to the base station (110), whichever occurs first, or alternatively the cancelling unit (930) being configured to cancel the pending scheduling request trigger at any time, but keeping track of what data that has been accounted for in the buffer status report to be included in a scheduled data transmission and what data that has not been accounted for, and when a next scheduling request opportunity appears, and the user equipment (120) further comprising a sending unit (940) configured to send a scheduling request if and only if the buffer comprises data that has not yet been accounted for in the buffer status report.']
Associated Portfolios
Licensor Claim Chart
 Claim Chart |
 Technology |
 Creation Date |
 Download |
|---|---|---|---|
|
Claim charts will soon be available!
|
|||
SUMMARY
ClaimChart-EP2428091A1-STO
Patent number:EP2428091A1
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.