U.S. patent application number 14/735557 was filed with the patent office on 2015-10-01 for method and apparatus for generating radio link control protocol data units.
This patent application is currently assigned to InterDigital Patent Holdings, Inc.. The applicant listed for this patent is InterDigital Patent Holdings, Inc.. Invention is credited to Christopher R. Cave, Paul Marinier, Diana Pani, Stephen E. Terry.
Application Number | 20150282007 14/735557 |
Document ID | / |
Family ID | 40512424 |
Filed Date | 2015-10-01 |
United States Patent
Application |
20150282007 |
Kind Code |
A1 |
Pani; Diana ; et
al. |
October 1, 2015 |
METHOD AND APPARATUS FOR GENERATING RADIO LINK CONTROL PROTOCOL
DATA UNITS
Abstract
A method and apparatus are used to generate radio link control
(RLC) protocol data units (PDUs). A data request for a logical
channel is received as part of an enhanced dedicated channel
(E-DCH) transport format combination (E-TFC) selection procedure in
a medium access control (MAC). Upon determining the data field
size, an RLC PDU is generated such that it matches the requested
data from the E-TFC selection. The size of the RLC PDU generated
can be greater than or equal to the minimum configured RLC PDU size
(if data is available) and less than or equal to the maximum RLC
PDU size. The data is then transmitted in the RLC PDU in a current
transmission time interval (TTI).
Inventors: |
Pani; Diana; (Montreal,
CA) ; Marinier; Paul; (Brossard, CA) ; Cave;
Christopher R.; (Dollard-des-Ormeaux, CA) ; Terry;
Stephen E.; (Northport, NY) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
InterDigital Patent Holdings, Inc. |
Wilmington |
DE |
US |
|
|
Assignee: |
InterDigital Patent Holdings,
Inc.
Wilmington
DE
|
Family ID: |
40512424 |
Appl. No.: |
14/735557 |
Filed: |
June 10, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13313847 |
Dec 7, 2011 |
9078158 |
|
|
14735557 |
|
|
|
|
12238638 |
Sep 26, 2008 |
8094682 |
|
|
13313847 |
|
|
|
|
60975995 |
Sep 28, 2007 |
|
|
|
60976319 |
Sep 28, 2007 |
|
|
|
60982596 |
Oct 25, 2007 |
|
|
|
61013173 |
Dec 12, 2007 |
|
|
|
61026912 |
Feb 7, 2008 |
|
|
|
61038515 |
Mar 21, 2008 |
|
|
|
61038682 |
Mar 21, 2008 |
|
|
|
61044765 |
Apr 14, 2008 |
|
|
|
Current U.S.
Class: |
370/330 |
Current CPC
Class: |
H04W 28/065 20130101;
H04W 80/02 20130101; H04L 47/36 20130101; H04W 72/0446 20130101;
H04W 28/06 20130101; H04W 72/044 20130101; H04L 1/1812
20130101 |
International
Class: |
H04W 28/06 20060101
H04W028/06; H04W 72/04 20060101 H04W072/04 |
Claims
1. A method comprising: determining a data field size for a radio
link control (RLC) protocol data unit (PDU) based on a current
enhanced dedicated channel (E-DCH) transport format combination
(E-TFC) selection, a minimum RLC PDU size and an amount of data to
be transmitted; and generating the RLC PDU based on the determined
data field size.
2. The method of claim 1, wherein the data field size for the RLC
PDU is determined such that an RLC PDU size of the RLC PDU matches
data requested for a logical channel by the E-TFC selection.
3. The method of claim 1, wherein the data field size for the RLC
PDU is determined such that an RLC PDU size of the RLC PDU is less
than the minimum RLC PDU size when the data to be transmitted is
insufficient to create an RLC PDU of the minimum RLC PDU size.
4. The method of claim 1, wherein the data field size for the RLC
PDU is determined such that an RLC PDU size of the RLC PDU is
greater than or equal to the minimum RLC PDU size when the data to
be transmitted is sufficient to create an RLC PDU of the minimum
RLC PDU size or greater.
5. The method of claim 1 further comprising: sending the RLC PDU in
a current transmission time interval.
6. The method of claim 1 further comprising: receiving an
indication of the minimum RLC PDU size via radio resource control
signaling.
7. The method of claim 1, wherein the data field size for the RLC
PDU is determined such that an RLC PDU size accounts for an
addition of a media access control (MAC) header to be added by a
MAC entity when the RLC PDU is generated.
8. A wireless transmit/receive unit (WTRU) comprising: a processor
configured to: determine a data field size for a radio link control
(RLC) protocol data unit (PDU) based on a current enhanced
dedicated channel (E-DCH) transport format combination (E-TFC)
selection, a minimum RLC PDU size and an amount of data to be
transmitted; and generate the RLC PDU based on the determined data
field size.
9. The WTRU of claim 8, wherein the data field size for the RLC PDU
is determined such that an RLC PDU size of the RLC PDU matches data
requested for a logical channel by the E-TFC selection.
10. The WTRU of claim 8, wherein the data field size for the RLC
PDU is determined such that an RLC PDU size of the RLC PDU is less
than the minimum RLC PDU size when the data to be transmitted is
insufficient to create an RLC PDU of the minimum RLC PDU size.
11. The WTRU of claim 8, wherein the data field size for the RLC
PDU is determined such that an RLC PDU size of the RLC PDU is
greater than or equal to the minimum RLC PDU size when the data to
be transmitted is sufficient to create an RLC PDU of the minimum
RLC PDU size or greater.
12. The WTRU of claim 8, wherein the processor is configured to:
send the RLC PDU in a current transmission time interval.
13. The WTRU of claim 8, wherein the processor is configured to:
receive an indication of the minimum RLC PDU size via radio
resource control signaling.
14. The WTRU of claim 8, wherein the data field size for the RLC
PDU is determined such that an RLC PDU size accounts for an
addition of a media access control (MAC) header to be added by a
MAC entity when the RLC PDU is generated.
15. A wireless transmit/receive unit (WTRU) comprising: a processor
configured to: determine a data field size for a radio link control
(RLC) protocol data unit (PDU), the determining comprising: setting
an available requested data size to match a data request from an
enhanced dedicated channel (E-DCH) transport format combination
(E-TFC) selection procedure when there is data for transmission, on
a condition that the available requested data size is greater than
or equal to a minimum RLC PDU size, determining the data field size
such that an RLC PDU size of the RLC PDU corresponds to a minimum
of: the available requested data size, an available data size and a
maximum RLC PDU size, and on a condition that the available
requested data size is determined to be less than the minimum RLC
PDU size, determining the data field size such that the RLC PDU
size of the RLC PDU corresponds to a minimum of: the available data
size and the minimum RLC PDU size; and generate the RLC PDU based
on the determined data field size.
16. The WTRU of claim 15, wherein the processor is further
configured to: subtract a media access control (MAC) header size
value from the available requested data size when generating at
least one RLC PDU.
17. The WTRU of claim 15, wherein the processor is further
configured to: subtract a media access control (MAC) header size
value from the available requested data size prior to generating at
least one RLC PDU.
18. The WTRU of claim 15, wherein the processor is further
configured to: perform a data retransmission, wherein the data
retransmission is transmitted as at least one full RLC PDU; and
decrease the available requested data size by a size of the
retransmitted RLC PDU.
19. The WTRU of claim 18, wherein the processor is further
configured to: subtract a media access control (MAC) header size
value from the available requested data size when retransmitting an
RLC PDU.
20. The WTRU of claim 18, wherein the processor is further
configured to: subtract a media access control (MAC) header size
value multiplied by the number of retransmitted RLC PDUs when
decreasing the available requested data size.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 13/313,847 filed on Dec. 7, 2011; which is a
continuation of U.S. patent application Ser. No. 12/238,638 filed
on Sep. 26, 2008, now U.S. Pat. No. 8,094,682, issued Jan. 10,
2012; which claims the benefit of U.S. Provisional Application Nos.
60/975,955 filed on Sep. 28, 2007, 60/976,319 filed on Sep. 28,
2007, 60/982,596 filed on Oct. 25, 2007, 61/013,173 filed on Dec.
12, 2007, 61/026,912 filed on Feb. 7, 2008, 61/038,515 filed on
Mar. 21, 2008, 61/038,682 filed on Mar. 21, 2008, 61/044,765 filed
on Apr. 14, 2008, and, each of which is incorporated by reference
as if fully set forth.
TECHNOLOGY FIELD
[0002] This application is related to wireless communications.
BACKGROUND
[0003] The Third Generation Partnership Project (3GPP) is a
collaboration between groups of telecommunications associations to
make a globally applicable third generation (3G) wireless
communications system. FIG. 1 is an overview of the system
architecture for a conventional Universal Mobile Telecommunications
System (UMTS) network.
[0004] The UMTS network architecture includes a Core Network (CN),
a UMTS Terrestrial Radio Access Network (UTRAN), and at least one
user equipment (UE). The CN is interconnected with the UTRAN via an
Iu interface.
[0005] The UTRAN is configured to provide wireless
telecommunication services to UEs, referred to as wireless
transmit/receive units (WTRUs) in this application, via a Uu radio
interface. A commonly employed air interface defined in the UMTS
standard is wideband code division multiple access (W-CDMA). The
UTRAN comprises one or more radio network controllers (RNCs) and
base stations, referred to as Node Bs by 3GPP, which collectively
provide for the geographic coverage for wireless communications
with the at least one UE. One or more Node Bs are connected to each
RNC via an Iub interface. The RNCs within the UTRAN communicate via
an Iur interface.
[0006] FIG. 2 is a block diagram of an example UE 200. The UE 200
may include an RRC entity 205, an RLC entity 210, a MAC entity 215
and a physical (PHY) layer 1 (L1) entity 220. The RLC entity 210
includes a transmitting side subassembly 225 and a receiving side
subassembly 230. The transmitting side subassembly 225 includes a
transmission buffer 235.
[0007] FIG. 3 is a block diagram of an example UTRAN 300. The UTRAN
300 may include an RRC entity 305, an RLC entity 310, a MAC entity
315 and PHY L1 entity 320. The RLC entity 310 includes a
transmitting side subassembly 325 and a receiving side subassembly
330. The transmitting side subassembly 325 includes a transmission
buffer 335.
[0008] 3GPP Release 6 introduced high-speed uplink packet access
(HSUPA) to provide higher data rates for uplink transmissions. As
part of HSUPA, a new transport channel, the enhanced dedicated
channel (E-DCH), was introduced to carry uplink (UL) data at higher
rates.
[0009] FIG. 4 shows an overview of the RLC sub-layers. The RLC
sub-layer consists of RLC entities, of which there are three types:
Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged
Mode (AM) RLC entities. A UM and a TM RLC entity may be configured
to be a transmitting RLC entity or a receiving RLC entity. The
transmitting RLC entity transmits RLC PDUs and the receiving RLC
entity receives RLC PDUs. An AM RLC entity consists of a
transmitting side for transmitting RLC PDUs and a receiving side
for receiving RLC PDUs.
[0010] Each RLC entity is defined as a sender or as a receiver
depending on elementary procedures. In UM and TM, the transmitting
RLC entity is a sender and a peer RLC entity is a receiver. An AM
RLC entity may be either a sender or a receiver depending on the
elementary procedure. The sender is the transmitter of acknowledged
mode data (AMD) PDUs and the receiver is the receiver of AMD PDUs.
A sender or receiver may be at either the UE or the UTRAN.
[0011] There is one transmitting RLC entity and one receiving RLC
entity for each TM and UM service. However, there is one combined
transmitting and receiving RLC entity for the AM service.
[0012] Both a UM RLC entity and a TM RLC entity use one logical
channel to send data PDUs and one logical channel to receive data
PDUs. An AM RLC entity may be configured to use one or two logical
channels to send or receive both data PDUs and control PDUs. If
only one logical channel is configured, then the transmitting AM
RLC entity transmits both data PDUs and control PDUs on the same
logical channel.
[0013] The AM or UM RLC entity may be configured to generate either
fixed size PDUs or flexible size PDUs. If a fixed RLC PDU size is
configured, the RLC PDU size is the same for both data PDUs and
control PDUs. If a flexible RLC PDU size is configured, the data
PDU size is variable. Unfortunately, the determination of a proper
flexible RLC PDU size is not defined.
[0014] Currently, an RLC entity is radio unaware, (i.e. not aware
of current radio conditions). When the RLC entity is designed to be
radio unaware, the RLC entity generates RLC PDUs of a maximum size.
Depending on current radio conditions and a given grant, this may
result in the generation of more than one PDU per TTI.
Unfortunately, if the generated RLC PDU is larger than a selected
E-DCH transport format combination (E-TFC) size, then the generated
RLC PDU may be segmented.
[0015] One disadvantage of the radio unaware RLC is that a large L2
overhead is results when a small fixed RLC PDU size is used.
Another disadvantage is that large error rates result from residual
HARQ errors where MAC segmentation is used with a large fixed RLC
PDU size. (Note: residual HARQ error=the transmission of the
improved MAC (MAC-i/is) PDU has failed. If there is a large number
of segments, the chance that any of the MAC-i/is PDU carrying a
segment fails is larger, thus the RLC PDU error rate
increases.)
[0016] However, in the UL direction, an RLC entity may be radio
aware, (i.e. aware of current radio conditions), because both RLC
and MAC protocols are located in the same node. As a result, an RLC
PDU size may be determined based on an instantaneous available data
rate.
[0017] A radio aware RLC entity may generate RLC PDUs according to
the available bit rate. There is minimal overhead and low error
rates due to residual hybrid automatic repeat request (HARQ) error
rates. However, a radio aware RLC entity may not be able to
generate an RLC PDU at a given TTI because the generation of the
RLC PDU within a short amount of time may require too much
processing power. For example, a radio aware RLC entity requires
that a ciphering function be performed on the generated RLC PDUs.
Additionally, a radio aware RLC entity has a higher overhead for
small E-TFC sizes and a lower overhead for large transport block
sizes.
[0018] A radio aware RLC entity generates RLC PDUs that match a
transport block size configured for low HARQ residual error rates.
Because a radio aware RLC generates a large RLC PDU when there is a
large E-TFC selection, there are problems when the large RLC PDU
needs to be retransmitted and the E-TFC selection decreases in
size. Further, the retransmission of the large RLC PDU requires the
generation of a large number of MAC segments. As a result, there
may be an increase of RLC PDU error rates due to residual HARQ
residual errors.
[0019] Accordingly, there exists a need for a method for use in an
RLC entity that generates RLC PDUs such that RLC overhead and HARQ
residual error rates are reduced.
SUMMARY
[0020] A method and apparatus are used to generate radio link
control (RLC) protocol data units (PDUs). A data request for a
logical channel is received as part of an enhanced dedicated
channel (E-DCH) transport format combination (E-TFC) selection
procedure in a medium access control (MAC). Upon determining the
data field size, an RLC PDU is generated such that it matches the
requested data from the E-TFC selection. The size of the RLC PDU
generated can be greater than or equal to the minimum configured
RLC PDU size (if data is available) and less than or equal to the
maximum RLC PDU size. The data is then transmitted in the RLC PDU
in a current transmission time interval (TTI).
BRIEF DESCRIPTION OF THE DRAWINGS
[0021] A more detailed understanding may be had from the following
description, given by way of example in conjunction with the
accompanying drawing wherein:
[0022] FIG. 1 shows an overview of the system architecture for a
conventional Universal Mobile Telecommunications System (UMTS)
network;
[0023] FIG. 2 is a block diagram of an example UE;
[0024] FIG. 3 is a block diagram of an example UTRAN;
[0025] FIG. 4 shows an overview of the RLC sub-layers;
[0026] FIG. 5 is a flow diagram of an RLC PDU generation
procedure;
[0027] FIG. 6 is a flow diagram of an RLC PDU generation procedure
with a maximum PDU size limit; and
[0028] FIG. 7 is a flow diagram of a hybrid RLC procedure for
implementing minimum and maximum RLC PDU restrictions.
DETAILED DESCRIPTION
[0029] When referred to hereafter, the terminology "wireless
transmit/receive unit (WTRU)" includes but is not limited to a user
equipment (UE), a mobile station, a fixed or mobile subscriber
unit, a pager, a cellular telephone, a personal digital assistant
(PDA), a computer, or any other type of user device capable of
operating in a wireless environment. When referred to hereafter,
the terminology "base station" includes but is not limited to a
base station, a site controller, an access point (AP), or any other
type of interfacing device capable of operating in a wireless
environment. When referred to hereafter, UTRAN includes but is not
limited to a cell, a base station, an RNC, or a network node.
[0030] Various methods are disclosed herein for generating RLC PDUs
such that RLC overhead and RLC PDU error rates due to HARQ residual
errors are reduced. Although the methods are described for a WTRU,
they are equally applicable to a collapsed architecture Node B+,
where a radio network controller (RNC) and a Node-B are located in
one node. When applying the concept to the Node B+, the terminology
WTRU may be interchanged with the terminology Node B+.
[0031] Hereinafter, the terminology "transport block" may refer to
any of the following: a MAC-e PDU, MAC-i PDU, MAC-es PDU, a MAC-is
PDU, or a MAC PDU. The terminology "number of bits in a transport
block" or "selected transport block (TB)" is used to refer to any
of the following quantities: the total size of the transport block
(or "transport block size"); the total size of the transport block
minus the number of bits required for MAC header; the number of
bits available to the MAC-d flow or logical channel to which the
RLC PDU belongs according to the E-DCH transport format combination
(E-TFC) selection procedure; the number of bits available to a
combination of MAC-d flows or logical channels according to the
E-TFC selection procedure; and the number of bits requested from
the given logical channel as part of the E-TFC selection
procedure.
[0032] Referring to FIG. 1, the UTRAN may be modified to also
include a target Node-B, a source Node-B, a controlling RNC (CRNC)
and a serving RNC (SRNC). The RNC may include an RLC unit and an
RRC unit (not shown). Alternatively, the RNC functionalities are
included in the Node-B and thus no controlling RNC or serving RNC
is present.
[0033] The UTRAN may be modified to receive at least one RLC
service data unit (SDU). The UTRAN may also be configured to reduce
RLC overhead and residual HARQ error rates using at least one
technique described below. The UTRAN may further be configured to
generate an RLC PDU between a minimum and a maximum RLC PDU size
when RLC data is available.
[0034] Referring to FIG. 2, the UE 200 may be modified to transmit
data in at least one RLC PDU in a current TTI. The RLC entity 225
of the UE 200 may be configured to receive a data request for a
logical channel from the MAC entity 215 as part of an E-TFC
selection procedure. The UE 200 may also be configured to determine
a data field size and generate at least one RLC PDU based on the
determined data field size corresponding to the data request. The
UE 200 may also be configured to generate an RLC PDU between a
maximum RLC PDU size and a minimum RLC PDU size when RLC data is
available.
[0035] Referring again to FIG. 2, the RLC entity 210 in the UE 200
may be modified to generate RLC PDUs on a TTI basis. In order to do
so, the RLC entity 210 relies on a data request provided by the MAC
entity 215 as part of the E-TFC selection procedure. The data
request provided by the MAC entity 215 allows the RLC entity 210 to
become aware of a channel condition, a grant, and a supported E-TFC
size for a given TTI. The E-TFC selection function in the MAC
entity 215 transmits a data request to the RLC entity 210 for a
logical channel. This data request corresponds to the available
space for this logical channel in the transport block, taking into
account the applicable MAC-is header and the data in the
corresponding MAC segmentation entity. The RLC entity 210 may
generate one or more RLC PDUs of a predetermined size based on the
data request from the E-TFC selection. To avoid the generation of
both small RLC PDUs or large RLC PDUs, the RLC entity 210 may have
radio aware capabilities with a number of restrictions. The RLC PDU
size may not be greater than maximum RLC PDU size and may not be
smaller than minimum RLC PDU size if data is available.
[0036] FIG. 5 is a flow diagram of an RLC PDU generation procedure
500. Referring to FIG. 5, upon receiving a data request for a
logical channel by the E-TFC selection function of the MAC (step
505), a data field size is determined based on the data request
(step 510). The data field size is determined such that the RLC PDU
(i.e., the data field size plus the RLC header) is equal to the
data request. An RLC PDU is then generated based on the determined
data field size (step 515). The data is transmitted in an RLC PDU
in a current TTI (step 520). Optionally, the MAC-i PDU header can
also be taken into account when determining the data field
size.
[0037] FIG. 6 is a flow diagram of an RLC PDU generation procedure
with a maximum PDU size limit 600. Once the E-TFC selection
procedure is performed, a data request for a logical channel is
sent by the E-TFC selection function of the MAC (step 605). If it
is determined that the requested data size is larger than the
maximum RLC PDU size (step 610), the RLC entity 210 may generate at
least one RLC PDU of the maximum RLC PDU size. The RLC entity 210
may continue generating RLC PDUs of the maximum RLC PDU size, or
less than the maximum RLC PDU size, until there is no more space
available from the data request or no more data is available in the
RLC entity. If there is no space available from the data request or
if there is no additional data to transmit, the RLC entity 210 does
not generate any more RLC PDUs. Alternatively, if the RLC is
restricted to only send one RLC PDU per TTI, the RLC entity 210 may
send the PDU of the maximum RLC PDU size and stop generating RLC
PDUs.
[0038] FIG. 7 shows a flow diagram of a hybrid RLC procedure 700
for implementing a fully radio aware RLC with both minimum and
maximum RLC PDU size restrictions.
[0039] The RLC PDU size may be less than or equal to the maximum
RLC PDU size and greater than or equal to the minimum RLC PDU size
(if data is available). In one embodiment, the UTRAN 300 determines
the maximum RLC PDU size and communicates the maximum RLC PDU size
value to the UE 200 using L2 or L3 signaling. The signaling of the
maximum RLC PDU size value may occur upon radio bearer
configuration/setup or radio bearer reconfiguration. Further, the
signaling of the maximum RLC PDU size value may occur upon
transport channel configuration or transport channel
reconfiguration. Upon receipt of the signaled maximum RLC PDU size
value, the UE 200 is configured to generate RLC PDUs that are less
than or equal to the maximum RLC PDU size value. A MAC PDU for a
current TTI may contain more than one RLC PDU or segments of RLC
PDUs if the requested data size or requested number of bits from
the MAC is greater than the maximum RLC PDU size.
[0040] In another embodiment, the UTRAN 300 broadcasts the maximum
RLC PDU size to all UEs 200 in a particular cell. The UTRAN 300
broadcasts the maximum RLC PDU size using a common channel such as
the enhanced random access channel (E-RACH).
[0041] The minimum RLC PDU size may be configured in any one, or a
combination, of the following ways. The minimum RLC PDU size may be
configured using RRC layer signaling. For example, the UTRAN 300
may configure the UE 200 to use a minimum RLC PDU size using the
RRC information element (IE) "RLC info." Then again, the minimum
RLC PDU size may be derived from a minimum allowed MAC segment
size. For example, the minimum RLC PDU size may be a multiple of a
minimum MAC segment size. Alternatively, the minimum RLC PDU size
may be a static value that is preconfigured in the UE 200. Further,
the minimum RLC PDU size may be a dynamic value that is determined
based on the average value of the smallest selected E-TFCs or the
average of requested data sizes. If the number of bits requested
from the given logical channel as part of the E-TFC selection
procedure is lower than the minimum RLC PDU size, then RLC PDUs
with a size equal to the minimum RLC PDU size are still created and
are sent to the lower layers if data is available. Additionally, if
the requested data size from the given logical channel as part of
the E-TFC selection procedure is lower than the minimum RLC PDU
size, an RLC PDU with a size less than the minimum RLC PDU size may
be created and sent to the lower layers thereby maintaining the
benefits of not padding at the RLC level.
[0042] In another embodiment, if the requested data size from the
given logical channel as part of the E-TFC selection procedure is
lower than the minimum RLC PDU size, no RLC PDUs are sent to the
lower layers.
[0043] For purposes of the following discussion, the function
MIN(A, B) provides the minimum value from among the parameters A
and B. Referring to FIG. 7, if there is data available for
transmission, and the MAC is requesting data for this logical
channel (step 705), an available requested data size may be
determined based on the data requested or allowed for transmission
by the MAC for this logical channel, selected by the E-TFC
selection procedure (step 710). The available requested data size
corresponds to the number of bits requested for the given logical
channel as part of the E-TFC selection.
[0044] If the available requested data size is determined to be
greater than the minimum RLC PDU size (step 715), then at least one
RLC PDU of a size equal to the smaller of the available data,
available requested data size, or maximum RLC PDU size is generated
(step 720).
[0045] The available requested data size is then set to the
available requested data size minus the size of the generated RLC
PDU (step 725). If the available requested data size is greater
than zero and data is still available in the logical channel (step
730) and if available requested data size is greater than minimum
RLC PDU size (step 715) then an additional RLC PDU of a size equal
to the smaller of the available data, available requested data
size, or maximum RLC PDU size is generated (step 720). This process
is repeated until there is no more space available, (i.e.,
available requested data size is zero), or until there no more data
available in this logical channel, or until the available requested
data size is less than the minimum RLC PDU size. This is equivalent
to the UE creating N RLC PDUs of maximum RLC PDU size, where N is
equivalent to the integer value of the smaller of available
requested data size or available data divided by the maximum RLC
PDU size. The UE can then create on additional RLC PDU of size X,
where X is equivalent to the remainder of the smaller of the
available requested data or available data divided by the maximum
RLC PDU size. If X is smaller than the minimum RLC PDU size, the UE
then creates an RLC PDU of minimum RLC PDU size if data is
available.
[0046] If the available requested data size is equal to or less
than zero or no more data is available (step 730), the generated
RLC PDU(s) are sent to lower layers (step 735) and the procedure
ends.
[0047] Still referring to FIG. 7, if the available requested data
size is determined to be not greater than the minimum RLC PDU size
(step 715), an RLC PDU of a size equal to the smaller value of
minimum RLC PDU size or available data is generated (step 740) and
all the generated RLC PDUs are sent to lower layers (step 735). The
generated RLC PDUs may contain padding bits or multiple
concatenated RLC SDUs. Optionally, the RLC entity may also take
into account the MAC-i header part to be added for every RLC PDU to
be generated. For the purpose of this description, the MAC-i header
is equivalent to h2, where h2 may be 16 bits. More specifically,
when determining the available requested data size, the UE may
subtract h2 every time an RLC PDU is generated or prior to
generating the RLC PDU. For example, in step 710 the available
requested data size may equal the data requested by the E-TFC
selection--h2. One other option would be to perform this step by
the E-TFC selection function in the MAC entity. Once an RLC PDU is
generated (step 720), then in 725, the available requested data
size may be updated by subtracting the size of the generated RLC
PDU and h2.
[0048] In a first alternative embodiment, if the available
requested data size is determined to be less than the minimum RLC
PDU size (step 715), an RLC of a size smaller than the minimum RLC
PDU size may be generated. As a result, the use of padding bits at
the RLC level may be avoided.
[0049] In a second alternative embodiment, if the available
requested data size is determined to be less than the minimum RLC
PDU size (step 715), an RLC PDU of size N times the requested data
size is generated such that the size of the generated RLC PDU is
greater than or equal to the minimum RLC PDU size. The value of N
may be preconfigured or determined at the time of transmission to
account for changes to channel conditions.
[0050] In a third alternative embodiment, if the available
requested data size is determined to be less than the minimum RLC
PDU size (step 715), then no RLC PDUs are sent to the lower
layers.
[0051] The RLC PDU generation procedure 700 of FIG. 7 is an example
that applies to a first transmission of new data where
retransmissions are not taken into account in the RLC PDU creation.
In the RLC generation procedure 700, only a first transmission of
new data may be radio aware and data retransmissions may not be
modified because an RLC PDU is already created. In an alternate
embodiment, the RLC generation procedure 700 may only be applicable
to a first transmission of new data. All data retransmissions may
be sent to lower layers as full RLC PDUs even if the data field
size based on the data request for a logical channel by the E-TFC
selection function is smaller or larger than the data
retransmission.
[0052] If the available requested data size based on the data
request for a logical channel by the E-TFC selection function is
larger than the sum of retransmitted RLC PDU(s) and there is more
new data is available for transmission, one or a combination of the
following may be performed.
[0053] The RLC entity 210 of FIG. 2 may be modified to send the
retransmitted RLC PDU(s) and generate one or more RLC PDUs to be
sent to the MAC entity 215. The size of the new RLC PDUs to
generate may be determined based on the available requested data
size, wherein the available requested data size is determined by
subtracting the size of the retransmitted RLC PDUs from the
original available requested data size, determined in step 710 of
FIG. 7. Once the updated available requested data size is
determined, and if it is not equivalent to zero or less than zero,
the UE may continue with the steps 715 and on in FIG. 7. The MAC-i
header part may also be taken into account for retransmissions. As
mentioned above, h2 may be subtracted in 710. When the size of the
retransmitted RLC PDUs is subtracted from the available data size
determined in 710, h2*Y may also be subtracted, where Y is
equivalent the number of retransmitted RLC PDUs.
[0054] Alternatively, the RLC entity 210 may be modified to send
both the retransmitted RLC PDU and a new RLC PDU generated based on
the size of a remaining E-TFC selection size with the option of
applying lower and upper boundary restrictions to the RLC PDU size.
After performing E-TFC selection, if RLC PDUs need to be
retransmitted, the available requested data size is decreased by
the size of the RLC PDUs needing retransmission.
[0055] As stated above, an RLC SDU may be segmented to fit into a
selected RLC PDU size. The remaining RLC SDU segment may be handled
in any or a combination of the following ways.
[0056] The remaining RLC SDU segment may be stored in the
transmission buffer 235 in the RLC entity 210. Then again, the
remaining RLC SDU segment may be stored in a SDU segmentation
buffer in the RLC entity 210 until a next transmission opportunity.
In the next transmission opportunity, the RLC SDU segment may be
sent as a single RLC PDU or concatenated to another RLC SDU so that
that the remaining RLC SDU segment fits into the selected RLC PDU
size.
[0057] Alternatively, the RLC entity 210 may be modified to
generate another RLC PDU or X number of RLC PDUs having the same
size as a current requested data size. The number X is equivalent
to the integer value of the remaining RLC PDU segment divided by
the current requested data size. The at least one created RLC PDU
is then stored in the transmission buffer 235 for transmission in a
next TTI alone or in combination with other RLC PDUs.
[0058] Although features and elements are described above in
particular combinations, each feature or element can be used alone
without the other features and elements or in various combinations
with or without other features and elements. The methods or flow
charts provided herein may be implemented in a computer program,
software, or firmware incorporated in a computer-readable storage
medium for execution by a general purpose computer or a processor.
Examples of computer-readable storage mediums include a read only
memory (ROM), a random access memory (RAM), a register, cache
memory, semiconductor memory devices, magnetic media such as
internal hard disks and removable disks, magneto-optical media, and
optical media such as CD-ROM disks, and digital versatile disks
(DVDs).
[0059] Suitable processors include, by way of example, a general
purpose processor, a special purpose processor, a conventional
processor, a digital signal processor (DSP), a plurality of
microprocessors, one or more microprocessors in association with a
DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs)
circuits, any other type of integrated circuit (IC), and/or a state
machine.
[0060] A processor in association with software may be used to
implement a radio frequency transceiver for use in a wireless
transmit receive unit (WTRU), user equipment (UE), terminal, base
station, radio network controller (RNC), or any host computer. The
WTRU may be used in conjunction with modules, implemented in
hardware and/or software, such as a camera, a video camera module,
a videophone, a speakerphone, a vibration device, a speaker, a
microphone, a television transceiver, a hands free headset, a
keyboard, a Bluetooth.RTM. module, a frequency modulated (FM) radio
unit, a liquid crystal display (LCD) display unit, an organic
light-emitting diode (OLED) display unit, a digital music player, a
media player, a video game player module, an Internet browser,
and/or any wireless local area network (WLAN) or Ultra Wide Band
(UWB) module.
* * * * *