Abstract
A telecommunications device comprises a transceiver (33); a radio link control entity (50); and a radio link control (RLC) buffer memory (150). The transceiver (33) which enables the device to communicate over an air interface (32). The radio link control entity (50) forms uplink RLC protocol data units (PDUs) for transmission over the air interface (32) and receives downlink RLC protocol data units (PDUs) over the air interface (32). The radio link control (RLC) buffer memory (150) is configured to include a transmitter buffer for storing the uplink RLC protocol data units (PDUs) and a receiver buffer for storing the downlink RLC protocol data units (PDUs). The radio link control entity includes RLC reconfiguration logic means (200) which reconfigures at least one of a size of a transmitter buffer window and a size of a receiver buffer window. In performing the reconfiguration the RLC reconfiguration logic means implements a strategy for handling at least one of (1) downlink RLC protocol data units (PDUs) which are outside a new receiver buffer window; and (2) uplink RLC protocol data units (PDUs) which are either outside a new transmitter window or whose receipt by the radio access network has not been positively acknowledged.
| Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Number | ||||||
| 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
| 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | 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 | |||||||
| EP1614248A1 | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Basis Patent | ||||
| EP1614248A1 | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Basis Patent | ||||
| EP1614248A1 | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
| EP1614248A1 | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
| EP1614248B1 | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Basis Patent | ||||
| EP1614248B1 | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Basis Patent | ||||
| EP1614248B1 | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
| EP1614248B1 | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
| EP1614248B2 | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Basis Patent | ||||
| EP1614248B2 | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Basis Patent | ||||
| EP1614248B2 | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
| EP1614248B2 | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
| AT427597T | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| AT427597T | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| AT427597T | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
| AT427597T | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | No | Family Member | ||||
| CN1771686B | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| CN1771686B | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| CN1771686B | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
| CN1771686B | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
| KR101051595B1 | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| KR101051595B1 | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| KR101051595B1 | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
| KR101051595B1 | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
| KR20050119683A | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| KR20050119683A | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| KR20050119683A | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
| KR20050119683A | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
| US2009221242A1 | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| US2009221242A1 | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| US2009221242A1 | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Basis Patent | ||||
| US2009221242A1 | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Basis Patent | ||||
| US7729719B2 | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| US7729719B2 | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | Yes | Family Member | ||||
| US7729719B2 | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Basis Patent | ||||
| US7729719B2 | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Basis Patent | ||||
| JP2006522560A | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| JP2006522560A | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| JP2006522560A | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | No | Family Member | ||||
| JP2006522560A | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | No | Family Member | ||||
| CN1771686A | 3G | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| CN1771686A | Not Available | 15/12/2005 | ISLD-200602-001 | ERICSSON INC | No | Family Member | ||||
| CN1771686A | 3G | 12/08/2014 | ISLD-201410-018 | OPTIS | Yes | Family Member | ||||
| CN1771686A | 3G | 26/06/2017 | ISLD-201712-010 | OPTIS | Yes | Family Member | ||||
| PL1614248T5 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| 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
Protocol Stack
Product
Use Cases
Wireless communication
Services
Claim
1. A telecommunications device comprising: a transceiver (33) which enables the device (30, 26) to communicate over an air interface (32); a radio link control entity (50) which forms uplink RLC protocol data units', '(PDUs) for transmission over the air interface (32) and which receives downlink RLC protocol data units (PDUs) over the air interface (32); a radio link control (RLC) buffer memory (150) configured to include a transmitter buffer for storing the uplink RLC protocol data units (PDUs) and a receiver buffer for storing the downlink RLC protocol data units (PDUs); and characterized by:', 'RLC reconfiguration logic means which is arranged to reconfigure at least one of a size of a transmitter buffer window and a size of a receiver buffer window by implementing a strategy for handling at least one of (1) downlink RLC protocol data units (PDUs) which are outside a new receiver buffer window; and (2) uplink RLC protocol data units (PDUs) which are either outside a new transmitter window or whose receipt by the radio access network has not been positively acknowledged.
2. The apparatus of claim 1, wherein the telecommunications device is a user equipment unit, and wherein the RLC reconfiguration logic means is arranged to implement the strategy of:', '(A) discarding any downlink RLC protocol data units (PDUs) which were received as being within old receiver buffer window but which are outside the new receiver buffer window;', '(B) retaining in the radio link control (RLC) buffer memory (150) any uplink RLC protocol data units (PDUs) whose receipt by the radio access network has not been positively acknowledged.
3. The apparatus of claim 2, wherein the radio link control entity (50) is further arranged to retransmit after the reconfiguration the uplink RLC protocol data units (PDUs) which were negatively acknowledged by the radio access network.
4. The apparatus of claim 2, wherein the radio link control entity (50) is further arranged not to require segmentation of a service data unit (SDU) received from a higher layer when, after the reconfiguration, the radio link control (RLC) buffer memory (150) experiences a memory size constraint.
5. The apparatus of claim 2, wherein the radio link control entity (50) does not negatively acknowledge the downlink RLC protocol data units (PDUs) that were received in the old receiver buffer window but which are outside the new receiver buffer window.
6. The apparatus of claim 1, wherein the telecommunications device is a user equipment unit, and wherein the RLC reconfiguration logic means is arranged to implement the strategy of: (A) retaining all downlink RLC protocol data units (PDUs) stored in the receiver buffer even if outside the new receiver buffer window until the receiver buffer window can be advanced;', '(B) retaining any uplink RLC protocol data units (PDUs) stored in the transmitter buffer, whose receipt by the radio access network has not been positively acknowledged, even if outside the new transmitter buffer window.
7. The apparatus of claim 6, wherein the radio link control entity (50) is further arranged to check whether receipt of a Service Data Unit (SDU) from a high layer would exceed capacity of the radio link control (RLC) buffer memory (150).
8. The apparatus of claim 7, wherein the radio link control entity (50) is further arranged to check for acknowledge mode RLC entities whether the buffer memory is sufficient to store acknowledge mode RLC protocol data units (AMD PDUs) having a sequence number SN which satisfies VT(A) < SN < VT(S), wherein VT(A) is a sequence number following the last in-sequence acknowledged AMD PDU; and VT(S) is a sequence number for a next AMD PDU to be transmitted for a first time.
9. The apparatus of claim 6, wherein the radio link control entity (50) is further arranged to check whether receipt of a Protocol Data Unit (PDU) from the radio access network would exceed capacity of the radio link control (RLC) buffer memory (150)
10. The apparatus of claim 9, wherein the radio link control entity (50) is further arranged to check for acknowledge mode RLC entities whether the buffer memory is sufficient to store acknowledge mode RLC protocol data units (AMD PDUs) having a sequence number SN which satisfies VR(R) < SN < VR(H), wherein VR(R) is a sequence number following the last in-sequence AMD PDU received; and VR(H) is a sequence number following a highest sequence number of any received AMD PDU
11. The apparatus of claim 1 , wherein the telecommunications device is a radio access network node, and wherein the RLC reconfiguration logic means is arranged to implement the strategy of:', '(A) retaining all downlink RLC protocol data units (PDUs) upon reconfiguration; (B) retaining all uplink RLC protocol data units (PDUs) upon reconfiguration
12. A method of operating a user equipment unit (30) which communicates over an air interface (32) with a radio access network, the method comprising: using a radio link control entity (50) to form uplink RLC protocol data units (PDUs) for transmission over the air interface (32) and to receive downlink RLC protocol data units (PDUs) over the air interface (32); storing the uplink RLC protocol data units (PDUs) in a transmitter buffer of a radio link control (RLC) buffer memory (150); storing the downlink RLC protocol data units (PDUs) in a receiver buffer of the radio link control (RLC) buffer memory (150); during a RLC reconfiguration wherein the user equipment unit (30) is directed to reconfigure at least one of (1) a size of a transmitter buffer window to form a new transmitter buffer window having a transmitter buffer window size smaller than an old transmitter buffer window; and (2) a size of a receiver buffer window to form a new receiver buffer window having a receiver buffer window size smaller than an old receiver buffer window, the method being characterized by:', '(A) discarding any downlink RLC protocol data units (PDUs) that were received as being within the old receiver buffer window but which are outside the new receiver buffer window;', '(B) retaining in the radio link control (RLC) buffer memory (150) any uplink RLC protocol data units (PDUs) whose receipt by the radio access network has not been positively acknowledged
13. The method of claim 12, further comprising the radio link control entity (50) retransmitting after the reconfiguration the uplink RLC protocol data units (PDUs) which were negatively acknowledged by the radio access network
14. The method of claim 12, further comprising the radio link control entity (50) not requiring segmentation of a service data unit (SDU) received from a higher layer when, after the reconfiguration, the radio link control (RLC) buffer memory (150) experiences a memory size constraint
15. The method of claim 12, further comprising the radio link control entity (50) not negatively acknowledging the downlink RLC protocol data units (PDUs) that were received in the old receiver buffer window but which are outside the new receiver buffer window
16. A method of operating a user equipment unit (30) which communicates over an air interface (32) with a radio access network, the method comprising: using a radio link control entity (50) to form uplink RLC protocol data units (PDUs) for transmission over the air interface (32) and to receive downlink RLC protocol data units (PDUs) over the air interface (32); storing the uplink RLC protocol data units (PDUs) in a transmitter buffer of a radio link control (RLC) buffer memory (150); storing the downlink RLC protocol data units (PDUs) in a receiver buffer of the radio link control (RLC) buffer memory (150); during a RLC reconfiguration wherein the user equipment unit (30) is directed to reconfigure at least one of (1) a size of a transmitter buffer window to form a new transmitter buffer window having a transmitter buffer window size smaller than an old transmitter buffer window; and (2) a size of a receiver buffer window to form a new receiver buffer window having a receiver buffer window size smaller than an old receiver buffer window, the method being characterized by:', '(A) retaining all downlink RLC protocol data units (PDUs) stored in the receiver buffer even if outside the new receiver buffer window until the receiver buffer window can be advanced; (B) retaining any uplink RLC protocol data units (PDUs) stored in the transmitter buffer, whose receipt by the radio access network has not been positively acknowledged, even if outside the new transmitter buffer window.17. The method of claim 16, further comprising the radio link control entity (50) checking whether receipt of a Service Data Unit (SDU) from a high layer would exceed capacity of the radio link control (RLC) buffer memory (150).18. The method of claim 17, further comprising the radio link control entity (50) checking for acknowledge mode RLC entities whether the buffer memory is sufficient to store acknowledge mode RLC protocol data units (AMD PDUs) having a sequence number SN which satisfies VT(A) < SN < VT(S), wherein VT(A) is a sequence number following the last in-sequence acknowledged AMD PDU; and VT(S) is a sequence number for a next AMD PDU to be transmitted for a first time.19. The method of claim 16, further comprising the radio link control entity (50) checking whether receipt of a Protocol Data Unit (PDU) from the radio access network would exceed capacity of the radio link control (RLC) buffer memory (150).
20. The method of claim 19, further comprising the radio link control entity (50) checking for acknowledge mode RLC entities whether the buffer memory is sufficient to store acknowledge mode RLC protocol data units (AMD PDUs) having a sequence number SN which satisfies VR(R) < SN < VR(H), wherein VR(R) is a sequence number following the last in-sequence AMD PDU received; and VR(H) is a sequence number following a highest sequence number of any received AMD PDU.
21. A method of operating a radio access node (26) of a radio access network which communicates over an air interface (32) with a user equipment unit (30), the method comprising: using a radio link control entity (50) to form uplink RLC protocol data units (PDUs) for transmission over the air interface (32) and to receive downlink RLC protocol data units (PDUs) over the air interface (32); storing the uplink RLC protocol data units (PDUs) in a transmitter buffer of a radio link control (RLC) buffer memory (150); storing the downlink RLC protocol data units (PDUs) in a receiver buffer of the radio link control (RLC) buffer memory (150); during a RLC reconfiguration, reconfiguring at least one of a size of a transmitter buffer window and a size of a receiver buffer window by: (A) retaining all downlink RLC protocol data units (PDUs) upon reconfiguration;', '(B) retaining all uplink RLC protocol data units (PDUs) upon reconfiguration.']
Associated Portfolios
Licensor Claim Chart
 Claim Chart |
 Technology |
 Creation Date |
 Download |
|---|---|---|---|
|
Claim charts will soon be available!
|
|||
SUMMARY
ClaimChart-WO2004091130A1-STO
Patent number:WO2004091130A1
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.