US20150282007A1 - Method and apparatus for generating radio link control protocol data units - Google Patents
Method and apparatus for generating radio link control protocol data units Download PDFInfo
- Publication number
- US20150282007A1 US20150282007A1 US14/735,557 US201514735557A US2015282007A1 US 20150282007 A1 US20150282007 A1 US 20150282007A1 US 201514735557 A US201514735557 A US 201514735557A US 2015282007 A1 US2015282007 A1 US 2015282007A1
- Authority
- US
- United States
- Prior art keywords
- rlc pdu
- size
- data
- rlc
- minimum
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000005540 biological transmission Effects 0.000 claims abstract description 21
- 238000010187 selection method Methods 0.000 claims abstract description 13
- 230000011664 signaling Effects 0.000 claims description 6
- 230000007423 decrease Effects 0.000 claims description 2
- 230000003247 decreasing effect Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 8
- 230000011218 segmentation Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
- H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
Definitions
- This application is related to wireless communications.
- FIG. 1 is an overview of the system architecture for a conventional Universal Mobile Telecommunications System (UMTS) network.
- UMTS Universal Mobile Telecommunications System
- 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.
- 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.
- WTRUs wireless transmit/receive units
- 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.
- RNCs radio network controllers
- 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.
- 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 .
- 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 .
- HSUPA high-speed uplink packet access
- E-DCH enhanced dedicated channel
- 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.
- TM Transparent Mode
- UM Unacknowledged Mode
- AM Acknowledged Mode
- 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.
- Each RLC entity is defined as a sender or as a receiver depending on elementary procedures.
- 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.
- 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.
- 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.
- an RLC entity is radio unaware, (i.e. not aware of current radio conditions).
- the RLC entity 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.
- E-TFC E-DCH transport format combination
- 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.
- an RLC PDU size may be determined based on an instantaneous available data rate.
- 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.
- HARQ hybrid automatic repeat request
- 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.
- a radio aware RLC entity requires that a ciphering function be performed on the generated RLC PDUs.
- a radio aware RLC entity has a higher overhead for small E-TFC sizes and a lower overhead for large transport block sizes.
- 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.
- a method and apparatus are used to generate radio link control (RLC) protocol data units (PDUs).
- RLC radio link control
- 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).
- E-DCH enhanced dedicated channel
- E-TFC transport format combination
- MAC medium access control
- 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).
- TTI current transmission time interval
- FIG. 1 shows an overview of the system architecture for a conventional Universal Mobile Telecommunications System (UMTS) network
- FIG. 2 is a block diagram of an example UE
- FIG. 3 is a block diagram of an example UTRAN
- FIG. 4 shows an overview of the RLC sub-layers
- FIG. 5 is a flow diagram of an RLC PDU generation procedure
- FIG. 6 is a flow diagram of an RLC PDU generation procedure with a maximum PDU size limit.
- FIG. 7 is a flow diagram of a hybrid RLC procedure for implementing minimum and maximum RLC PDU restrictions.
- wireless transmit/receive unit 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.
- 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.
- UTRAN includes but is not limited to a cell, a base station, an RNC, or a network node.
- RLC PDUs such that RLC overhead and RLC PDU error rates due to HARQ residual errors are reduced.
- RLC radio network controller
- 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.
- 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.
- E-TFC E-DCH transport format combination
- 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).
- the RNC functionalities are included in the Node-B and thus no controlling RNC or serving RNC is present.
- 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.
- 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.
- the RLC entity 210 in the UE 200 may be modified to generate RLC PDUs on a TTI basis.
- 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.
- 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.
- FIG. 5 is a flow diagram of an RLC PDU generation procedure 500 .
- 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 ).
- the MAC-i PDU header can also be taken into account when determining the data field size.
- FIG. 6 is a flow diagram of an RLC PDU generation procedure with a maximum PDU size limit 600 .
- a data request for a logical channel is sent by the E-TFC selection function of the MAC (step 605 ).
- 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.
- 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.
- 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.
- 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).
- 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.
- the UE 200 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.
- 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).
- E-RACH enhanced random access channel
- 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.
- the UTRAN 300 may configure the UE 200 to use a minimum RLC PDU size using the RRC information element (IE) “RLC info.”
- IE RRC information element
- the minimum RLC PDU size may be derived from a minimum allowed MAC segment size.
- the minimum RLC PDU size may be a multiple of a minimum MAC segment size.
- the minimum RLC PDU size may be a static value that is preconfigured in the UE 200 .
- 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.
- 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.
- the function MIN(A, B) provides the minimum value from among the parameters A and B.
- 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.
- step 715 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 ).
- 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.
- 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.
- step 730 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.
- 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.
- the RLC entity may also take into account the MAC-i header part to be added for every RLC PDU to be generated.
- the MAC-i header is equivalent to h2, where h2 may be 16 bits.
- 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.
- the available requested data size may be updated by subtracting the size of the generated RLC PDU and h2.
- step 715 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.
- 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.
- step 715 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.
- 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.
- 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.
- the E-TFC selection function 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.
- 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 .
- 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.
- h2 may be subtracted in 710 .
- h2*Y may also be subtracted, where Y is equivalent the number of retransmitted RLC PDUs.
- 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.
- 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.
- 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.
- 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.
- ROM read only memory
- RAM random access memory
- 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).
- 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.
- DSP digital signal processor
- ASICs Application Specific Integrated Circuits
- FPGAs Field Programmable Gate Arrays
- 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® 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.
- WLAN wireless local area network
- UWB Ultra Wide Band
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).
Description
- 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.
- This application is related to wireless communications.
- 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. - 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.
- 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.
-
FIG. 2 is a block diagram of an example UE 200. The UE 200 may include anRRC entity 205, an RLCentity 210, aMAC entity 215 and a physical (PHY) layer 1 (L1)entity 220. TheRLC entity 210 includes a transmittingside subassembly 225 and a receiving side subassembly 230. The transmittingside subassembly 225 includes atransmission buffer 235. -
FIG. 3 is a block diagram of an example UTRAN 300. The UTRAN 300 may include anRRC entity 305, anRLC entity 310, aMAC entity 315 and PHYL1 entity 320. TheRLC entity 310 includes a transmittingside subassembly 325 and a receivingside subassembly 330. The transmittingside subassembly 325 includes atransmission buffer 335. - 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.
-
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. - 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.
- 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.
- 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.
- 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.
- 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.
- 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.)
- 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.
- 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.
- 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.
- 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.
- 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).
- A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawing wherein:
-
FIG. 1 shows an overview of the system architecture for a conventional Universal Mobile Telecommunications System (UMTS) network; -
FIG. 2 is a block diagram of an example UE; -
FIG. 3 is a block diagram of an example UTRAN; -
FIG. 4 shows an overview of the RLC sub-layers; -
FIG. 5 is a flow diagram of an RLC PDU generation procedure; -
FIG. 6 is a flow diagram of an RLC PDU generation procedure with a maximum PDU size limit; and -
FIG. 7 is a flow diagram of a hybrid RLC procedure for implementing minimum and maximum RLC PDU restrictions. - 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.
- 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+.
- 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.
- 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. - 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.
- Referring to
FIG. 2 , theUE 200 may be modified to transmit data in at least one RLC PDU in a current TTI. TheRLC entity 225 of theUE 200 may be configured to receive a data request for a logical channel from theMAC entity 215 as part of an E-TFC selection procedure. TheUE 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. TheUE 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. - Referring again to
FIG. 2 , theRLC entity 210 in theUE 200 may be modified to generate RLC PDUs on a TTI basis. In order to do so, theRLC entity 210 relies on a data request provided by theMAC entity 215 as part of the E-TFC selection procedure. The data request provided by theMAC entity 215 allows theRLC 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 theMAC entity 215 transmits a data request to theRLC 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. TheRLC 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, theRLC 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. -
FIG. 5 is a flow diagram of an RLCPDU generation procedure 500. Referring toFIG. 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. -
FIG. 6 is a flow diagram of an RLC PDU generation procedure with a maximumPDU 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), theRLC entity 210 may generate at least one RLC PDU of the maximum RLC PDU size. TheRLC 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, theRLC entity 210 does not generate any more RLC PDUs. Alternatively, if the RLC is restricted to only send one RLC PDU per TTI, theRLC entity 210 may send the PDU of the maximum RLC PDU size and stop generating RLC PDUs. -
FIG. 7 shows a flow diagram of ahybrid RLC procedure 700 for implementing a fully radio aware RLC with both minimum and maximum RLC PDU size restrictions. - 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 theUE 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, theUE 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. - In another embodiment, the
UTRAN 300 broadcasts the maximum RLC PDU size to allUEs 200 in a particular cell. TheUTRAN 300 broadcasts the maximum RLC PDU size using a common channel such as the enhanced random access channel (E-RACH). - 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 theUE 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 theUE 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. - 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.
- 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. - 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).
- 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.
- 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.
- 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, instep 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. - 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.
- 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.
- 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.
- The RLC
PDU generation procedure 700 ofFIG. 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 theRLC 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, theRLC 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. - 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.
- The
RLC entity 210 ofFIG. 2 may be modified to send the retransmitted RLC PDU(s) and generate one or more RLC PDUs to be sent to theMAC 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 instep 710 ofFIG. 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 thesteps 715 and on inFIG. 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. - 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. - 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.
- The remaining RLC SDU segment may be stored in the
transmission buffer 235 in theRLC entity 210. Then again, the remaining RLC SDU segment may be stored in a SDU segmentation buffer in theRLC 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. - 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 thetransmission buffer 235 for transmission in a next TTI alone or in combination with other RLC PDUs. - 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).
- 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.
- 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® 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.
Claims (20)
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.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/735,557 US20150282007A1 (en) | 2007-09-28 | 2015-06-10 | Method and apparatus for generating radio link control protocol data units |
Applications Claiming Priority (12)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US97595507P | 2007-09-28 | 2007-09-28 | |
US97631907P | 2007-09-28 | 2007-09-28 | |
US97599507P | 2007-09-28 | 2007-09-28 | |
US98259607P | 2007-10-25 | 2007-10-25 | |
US1317307P | 2007-12-12 | 2007-12-12 | |
US2691208P | 2008-02-07 | 2008-02-07 | |
US3851508P | 2008-03-21 | 2008-03-21 | |
US3868208P | 2008-03-21 | 2008-03-21 | |
US4476508P | 2008-04-14 | 2008-04-14 | |
US12/238,638 US8094682B2 (en) | 2007-09-28 | 2008-09-26 | Method and apparatus for generating radio link control protocol data units |
US13/313,847 US9078158B2 (en) | 2007-09-28 | 2011-12-07 | Method and apparatus for generating radio link control protocol data units |
US14/735,557 US20150282007A1 (en) | 2007-09-28 | 2015-06-10 | Method and apparatus for generating radio link control protocol data units |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/313,847 Continuation US9078158B2 (en) | 2007-09-28 | 2011-12-07 | Method and apparatus for generating radio link control protocol data units |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150282007A1 true US20150282007A1 (en) | 2015-10-01 |
Family
ID=40512424
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/239,023 Active 2030-06-11 US8879534B2 (en) | 2007-09-28 | 2008-09-26 | Method and apparatus for selecting a radio link control protocol data unit size |
US12/238,638 Active 2030-06-29 US8094682B2 (en) | 2007-09-28 | 2008-09-26 | Method and apparatus for generating radio link control protocol data units |
US13/313,847 Active 2028-12-09 US9078158B2 (en) | 2007-09-28 | 2011-12-07 | Method and apparatus for generating radio link control protocol data units |
US14/490,741 Active 2028-11-07 US9609548B2 (en) | 2007-09-28 | 2014-09-19 | Method and apparatus for selecting a radio link control protocol data unit size |
US14/735,557 Abandoned US20150282007A1 (en) | 2007-09-28 | 2015-06-10 | Method and apparatus for generating radio link control protocol data units |
US15/432,118 Abandoned US20170156145A1 (en) | 2007-09-28 | 2017-02-14 | Method and apparatus for selecting a radio link control protocol data unit size |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/239,023 Active 2030-06-11 US8879534B2 (en) | 2007-09-28 | 2008-09-26 | Method and apparatus for selecting a radio link control protocol data unit size |
US12/238,638 Active 2030-06-29 US8094682B2 (en) | 2007-09-28 | 2008-09-26 | Method and apparatus for generating radio link control protocol data units |
US13/313,847 Active 2028-12-09 US9078158B2 (en) | 2007-09-28 | 2011-12-07 | Method and apparatus for generating radio link control protocol data units |
US14/490,741 Active 2028-11-07 US9609548B2 (en) | 2007-09-28 | 2014-09-19 | Method and apparatus for selecting a radio link control protocol data unit size |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/432,118 Abandoned US20170156145A1 (en) | 2007-09-28 | 2017-02-14 | Method and apparatus for selecting a radio link control protocol data unit size |
Country Status (13)
Country | Link |
---|---|
US (6) | US8879534B2 (en) |
EP (2) | EP2203996B1 (en) |
JP (7) | JP5211169B2 (en) |
KR (7) | KR20140144309A (en) |
CN (4) | CN101809917B (en) |
AR (2) | AR068295A1 (en) |
AU (2) | AU2008308969B2 (en) |
BR (1) | BRPI0816008A2 (en) |
IL (1) | IL204294A (en) |
MX (2) | MX2010003342A (en) |
MY (1) | MY151258A (en) |
TW (8) | TWI474653B (en) |
WO (2) | WO2009045882A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018086693A1 (en) * | 2016-11-10 | 2018-05-17 | Huawei Technologies Co., Ltd. | Transmitting device, receiving device and methods thereof |
Families Citing this family (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1641189B1 (en) * | 2004-09-27 | 2010-05-19 | Panasonic Corporation | Error ratio measurement in the radio link control layer for quality of service control in a wireless communication system |
US8014359B2 (en) * | 2006-10-27 | 2011-09-06 | Interdigital Technology Corporation | Method and apparatus for assigning radio resources and controlling transmission parameters on a random access channel |
EP3419198B1 (en) * | 2007-02-05 | 2020-07-22 | Telefonaktiebolaget LM Ericsson (publ) | Adjustments of iub load measurements |
CN101809917B (en) * | 2007-09-28 | 2013-10-09 | 交互数字专利控股公司 | Method and apparatus for selecting a radio link control protocol data unit size |
US8179877B2 (en) | 2007-09-28 | 2012-05-15 | Interdigital Patent Holdings, Inc. | Method and apparatus for creating an enhanced medium access control packet data unit for enhanced transport format combination selection in wireless communications |
KR101375936B1 (en) | 2008-02-01 | 2014-03-18 | 엘지전자 주식회사 | Method of a downlink harq operation at an expiry of time alignment timer |
WO2009096746A2 (en) * | 2008-02-01 | 2009-08-06 | Lg Electronics Inc. | Method for sending rlc pdu and allocating radio resource in mobile communications system and rlc entity of mobile communications |
KR101531419B1 (en) | 2008-02-01 | 2015-06-24 | 엘지전자 주식회사 | Method of an uplink harq operation at an expiry of time alignment timer |
US8396083B2 (en) * | 2008-03-31 | 2013-03-12 | Qualcomm Incorporated | Determinative segmentation resegmentation and padding in radio link control (RLC) service data units (SDU) |
KR101666388B1 (en) * | 2008-04-30 | 2016-10-14 | 삼성전자 주식회사 | System and method for data size adaptation in a ue |
US9226195B2 (en) * | 2008-06-30 | 2015-12-29 | Htc Corporation | Method for determining RLC Data PDU size in wireless communications system according to control data |
US8050292B2 (en) * | 2008-06-30 | 2011-11-01 | Htc Corporation | Method of performing transmission and prioritization for radio link control packets for a medium access control layer of a wireless communications system |
US8250425B2 (en) * | 2008-08-15 | 2012-08-21 | Apple Inc. | Management of ARQ detection threshold in communication networks |
US8130667B2 (en) | 2008-09-19 | 2012-03-06 | Texas Instruments Incorporated | Preamble group selection in random access of wireless networks |
KR101546751B1 (en) * | 2008-11-05 | 2015-08-24 | 삼성전자주식회사 | An efficient RLF detection mechanism in a wireless system |
EP2351449B1 (en) * | 2008-11-24 | 2013-01-02 | Telefonaktiebolaget L M Ericsson (PUBL) | Improved uplink segmentation |
US8514779B2 (en) * | 2009-04-13 | 2013-08-20 | Qualcomm Incorporated | Radio link control protocol data unit size selection in dual carrier HSUPA |
CN102428725B (en) * | 2009-04-24 | 2015-05-13 | 交互数字专利控股公司 | Method and apparatus for generating a radio link control protocol data unit for multi-carrier operation |
US8862141B2 (en) * | 2009-05-18 | 2014-10-14 | Nokia Corporation | Systems, methods, and apparatuses for facilitating allocation of a common resource to a terminal |
US8238244B2 (en) * | 2009-08-10 | 2012-08-07 | Micron Technology, Inc. | Packet deconstruction/reconstruction and link-control |
KR20110020195A (en) * | 2009-08-21 | 2011-03-02 | 엘지전자 주식회사 | Apparatus and method of transmitting data block on uplink frequencies |
CN102035634B (en) * | 2009-09-27 | 2015-01-28 | 中兴通讯股份有限公司 | Method and device for determining hybrid automatic retransmission request profile information |
EP2520056A4 (en) * | 2009-12-30 | 2014-09-17 | Ericsson Telefon Ab L M | Method of and node b and user equipment for power control in case of segmentation |
US8483238B2 (en) * | 2010-02-02 | 2013-07-09 | Qualcomm Incorporated | Radio link control protocol data unit size selection |
US8339970B2 (en) * | 2010-04-02 | 2012-12-25 | Clearwire IP Holdings | System and method for network optimization |
EP2578039A4 (en) * | 2010-05-26 | 2016-11-16 | Ericsson Telefon Ab L M | A method and a device for increased bit rate |
KR101708786B1 (en) * | 2010-09-03 | 2017-02-21 | 에스케이텔레콤 주식회사 | Apparatus and Method for transmitting data in Radio Link Control Layer |
US9042930B1 (en) * | 2010-09-13 | 2015-05-26 | Sprint Spectrum L.P. | Method and system for reducing forward link transmission power |
CN102014432B (en) * | 2010-11-18 | 2015-07-22 | 中兴通讯股份有限公司 | Downlink resource allocation method and base station |
US8917636B2 (en) * | 2011-06-30 | 2014-12-23 | Intel Mobile Communications GmbH | Transmitter circuit and method |
KR20130047862A (en) | 2011-11-01 | 2013-05-09 | 삼성전자주식회사 | Method and apparatus for estimating available bandwidth of each of user equipments in a communication system |
US9614606B2 (en) * | 2011-12-28 | 2017-04-04 | Qualcomm Incorporated | Method and apparatus for power aware receive diversity control |
WO2013120245A1 (en) * | 2012-02-13 | 2013-08-22 | St-Ericsson Sa | Method and apparatus for uplink data transmission, user equipment, computer program and storage medium |
GB2503469A (en) * | 2012-06-27 | 2014-01-01 | Renesas Mobile Corp | Limiting the size of protocol data units (PDUs) containing new data in a repeat transmission system |
WO2014019131A1 (en) * | 2012-07-31 | 2014-02-06 | 华为技术有限公司 | Method and device for recovering link failure |
JP6079121B2 (en) * | 2012-10-11 | 2017-02-15 | 富士通株式会社 | COMMUNICATION SYSTEM, MANAGEMENT DEVICE, BASE STATION, COMMUNICATION DEVICE, AND COMMUNICATION PATH CONTROL METHOD |
WO2015096047A1 (en) * | 2013-12-24 | 2015-07-02 | 华为技术有限公司 | Method for uplink scheduling, user equipment and base station |
US10075381B2 (en) * | 2014-01-28 | 2018-09-11 | Mediatek Inc. | Buffer status report and logical channel prioritization for dual connectivity |
JP6933979B2 (en) * | 2015-03-31 | 2021-09-08 | 株式会社大阪ソーダ | Electrochemical capacitors |
US10470210B2 (en) * | 2015-05-11 | 2019-11-05 | Lg Electronics Inc. | Method for performing RLC retransmission based on contention-based PUSCH in a wireless communication system and a device therefor |
CN106301705A (en) * | 2015-05-27 | 2017-01-04 | 北京信威通信技术股份有限公司 | A kind of method triggering rlc layer re-transmission |
US9705803B1 (en) | 2015-06-10 | 2017-07-11 | Sprint Communications Company L.P. | Negotiated radio link properties among wireless access nodes |
US10505783B2 (en) * | 2015-06-30 | 2019-12-10 | Lg Electronics Inc. | Terminal and V2X communication method thereof in V2X communication system |
FR3043522A1 (en) * | 2015-11-10 | 2017-05-12 | Orange | TRANSMITTING VARIABLE VOLUME DATA IN A MOBILE COMMUNICATION NETWORK |
US10021596B2 (en) * | 2016-03-30 | 2018-07-10 | Industrial Technology Research Institute | Communication system, communication device, base station and method thereof for D2D communications |
US11419004B2 (en) * | 2016-11-08 | 2022-08-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Optimization of logical channel processing for multiple transport blocks |
CN110140316B (en) | 2017-01-04 | 2020-11-17 | Oppo广东移动通信有限公司 | Method for transmitting RLC layer status report control PDU and related equipment |
CN108282273B (en) * | 2017-01-05 | 2024-03-08 | 华为技术有限公司 | Method and device for segment retransmission |
US10678637B2 (en) * | 2017-01-10 | 2020-06-09 | Qualcomm Incorporated | Techniques to improve data transfer reliability |
WO2018174764A1 (en) * | 2017-03-24 | 2018-09-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatus and method for transmitting packet data units |
CN108809563B (en) * | 2017-05-03 | 2021-01-01 | 普天信息技术有限公司 | Service data preprocessing method and system |
CN110677878B (en) * | 2017-05-05 | 2021-04-09 | 华为技术有限公司 | Data transmission method, device, equipment and system |
KR102366376B1 (en) * | 2017-06-15 | 2022-02-23 | 삼성전자 주식회사 | Method and apparatus for header processing in mac layer |
CN109151909A (en) * | 2017-06-16 | 2019-01-04 | 华为技术有限公司 | Data processing method and device |
CN109729554B (en) * | 2017-10-30 | 2022-03-01 | 展讯通信(上海)有限公司 | Uplink enhanced data transmission method and device and user equipment |
TWI689218B (en) | 2017-11-08 | 2020-03-21 | 財團法人資訊工業策進會 | Base station, user equipment, and method for early data transmission |
EP4037218A1 (en) * | 2018-01-07 | 2022-08-03 | LG Electronics Inc. | Communication device, processing device and method for transmitting data unit |
CN110474854B (en) * | 2018-05-11 | 2021-08-31 | 华为技术有限公司 | Resource allocation method and device |
CN111245556A (en) * | 2018-11-28 | 2020-06-05 | 普天信息技术有限公司 | TBS (transport block size ratio) calculation method of 5GNR (generalized maximum likelihood ratio) and MACPDU (machine Access data Unit) multiplexing method and equipment |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6904016B2 (en) * | 2001-11-16 | 2005-06-07 | Asustek Computer Inc. | Processing unexpected transmission interruptions in a wireless communications system |
US20060106924A1 (en) * | 2004-11-12 | 2006-05-18 | Canon Kabushiki Kaisha | Data-processing device, communication method, and computer program |
US20090036061A1 (en) * | 2006-02-07 | 2009-02-05 | Sung-Duck Chun | Method for operating enhanced rlc entity and rnc entity for wcdma and system thereof |
US20090268706A1 (en) * | 2006-04-18 | 2009-10-29 | Motorola, Inc. | Optimised packet data transmission protocol in a communication system employing a transmission window |
US8094682B2 (en) * | 2007-09-28 | 2012-01-10 | Interdigital Patent Holdings, Inc. | Method and apparatus for generating radio link control protocol data units |
Family Cites Families (66)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6370169B1 (en) * | 1998-04-22 | 2002-04-09 | Nippon Telegraph & Telephone Corporation | Method and apparatus for controlling optical wavelength based on optical frequency pulling |
KR100619598B1 (en) * | 1998-10-01 | 2006-12-01 | 엘지전자 주식회사 | Signal Format Method in Mobile Communication System |
FI106504B (en) | 1998-10-06 | 2001-02-15 | Nokia Networks Oy | Data segmentation method in a communication system |
EP1104216A1 (en) * | 1999-11-23 | 2001-05-30 | Lucent Technologies Inc. | Mobile telecommunications systems |
FR2809577B1 (en) * | 2000-05-25 | 2002-10-18 | Mitsubishi Electric Inf Tech | DATA TRANSMISSION METHOD COMBATING THE DEGRADATION OF QUALITY OF SERVICE |
KR100447162B1 (en) * | 2000-08-19 | 2004-09-04 | 엘지전자 주식회사 | Method for length indicator inserting in protocol data unit of radio link control |
US6853994B1 (en) | 2000-08-30 | 2005-02-08 | International Business Machines Corporation | Object oriented based, business class methodology for performing data metric analysis |
DE10107700A1 (en) | 2001-02-19 | 2002-08-29 | Siemens Ag | Method and device for multiplexing and / or demultiplexing as well as corresponding computer programs and a corresponding computer program product |
US7242670B2 (en) * | 2001-07-07 | 2007-07-10 | Lg Electronics Inc. | Method for controlling retransmission of information using state variables in radio communication system |
US7254143B2 (en) | 2001-11-19 | 2007-08-07 | Innovative Sonic Limited | Local suspend scheme for wireless communication systems |
KR100876730B1 (en) * | 2002-07-08 | 2008-12-31 | 삼성전자주식회사 | Efficient Initial Transmission Format Coupling Factor Setting Method for Wideband Code Division Multiple Access |
SE0301048D0 (en) | 2003-04-07 | 2003-04-07 | Ericsson Telefon Ab L M | RLC window reconfiguration |
US20040252719A1 (en) | 2003-06-10 | 2004-12-16 | Iqbal Jami | Radio telecommunications network, a station, and a method of sending packets of data |
DE10345638A1 (en) | 2003-09-29 | 2005-06-02 | Siemens Ag | Method for data transmission |
KR100520146B1 (en) * | 2003-12-22 | 2005-10-10 | 삼성전자주식회사 | Method for processing data in high speed downlink packet access communication system |
KR100712608B1 (en) | 2003-12-24 | 2007-05-02 | 니폰덴신뎅와 가부시키가이샤 | Dynamic band allocation circuit, dynamic band allocation method, and recording medium |
JP4417733B2 (en) | 2004-01-15 | 2010-02-17 | ソニー・エリクソン・モバイルコミュニケーションズ株式会社 | Transmission method and apparatus |
KR100713442B1 (en) | 2004-02-14 | 2007-05-02 | 삼성전자주식회사 | Method of transmitting scheduling information an enhanced uplink dedicated channel in a mobile communication system |
US7584397B2 (en) | 2004-06-10 | 2009-09-01 | Interdigital Technology Corporation | Method and apparatus for dynamically adjusting data transmission parameters and controlling H-ARQ processes |
US7813754B2 (en) | 2004-06-17 | 2010-10-12 | Ntt Docomo, Inc. | Transfer rate control method, transmission power control method, transmission power ratio control method, mobile communication system, mobile station, and radio base station |
US7885245B2 (en) | 2004-07-19 | 2011-02-08 | Interdigital Technology Corporation | Method and apparatus for enhanced uplink multiplexing |
CN2857338Y (en) * | 2004-07-19 | 2007-01-10 | 美商内数位科技公司 | Radio transmitting/receiving unit of carrying out reinforced upper chain multiple tasks |
US7391758B2 (en) | 2004-09-29 | 2008-06-24 | Intel Corporation | UMTS radio link control with full concatenation |
AU2005302888B2 (en) | 2004-11-09 | 2008-05-22 | Samsung Electronics Co., Ltd. | Method and apparatus for signaling control information of uplink packet data service in mobile communication system |
CN1330162C (en) | 2004-12-02 | 2007-08-01 | 华为技术有限公司 | Method for data segment cascade and recombination |
US8189615B2 (en) | 2004-12-23 | 2012-05-29 | Nokia Corporation | Method and apparatus for communicating scheduling information from a UE to a radio access network |
CN100574174C (en) | 2005-01-26 | 2009-12-23 | 华为技术有限公司 | The control method that radio link control layer buffer area overflows |
DE102005005251A1 (en) | 2005-02-04 | 2006-08-10 | Infineon Technologies Ag | Data protection layer-protocol device for universal mobile telecommunication system mobile radio device, has data protection layer-protocol buffer memory selection unit selecting intermediately stored data using memories prioritization |
KR101141645B1 (en) | 2005-03-29 | 2012-05-17 | 엘지전자 주식회사 | Method for Controlling Transmission of Data Block |
US8179836B2 (en) | 2005-04-20 | 2012-05-15 | Interdigital Technology Corporation | Method and apparatus for controlling transmissions via an enhanced dedicated channel |
TWI423632B (en) | 2005-04-20 | 2014-01-11 | Interdigital Tech Corp | Method and apparatus for scheduling transmissions via an enhanced dedicated channel |
US8116292B2 (en) * | 2005-04-29 | 2012-02-14 | Interdigital Technology Corporation | MAC multiplexing and TFC selection procedure for enhanced uplink |
KR100913900B1 (en) * | 2005-05-04 | 2009-08-26 | 삼성전자주식회사 | A method and apparatus for transmitting/receiving packet data using predefined length indicator in mobile communication system |
US8204007B2 (en) * | 2005-08-01 | 2012-06-19 | Interdigital Technology Corporation | Method and apparatus for control of enhanced dedicated channel transmissions |
JP4751673B2 (en) | 2005-08-29 | 2011-08-17 | 株式会社エヌ・ティ・ティ・ドコモ | Transmission rate control method and mobile station |
JP4503513B2 (en) | 2005-08-31 | 2010-07-14 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile terminal device, topology management device, communication method, and communication network |
WO2007032649A1 (en) | 2005-09-15 | 2007-03-22 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting and receiving status report comprising received status of packet data in a mobile communication system |
ATE410874T1 (en) | 2005-09-20 | 2008-10-15 | Matsushita Electric Ind Co Ltd | METHOD AND DEVICE FOR PACKET SEGMENTATION AND LINK SIGNALING IN A COMMUNICATIONS SYSTEM |
KR101020239B1 (en) | 2005-09-29 | 2011-03-08 | 노키아 코포레이션 | Apparatus, method and computer program product to request a data rate increase based on ability to transmit at least one more selected data unit |
US8284777B2 (en) | 2005-10-17 | 2012-10-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Uplink cell changes in a mobile communication network |
KR100912784B1 (en) | 2006-01-05 | 2009-08-18 | 엘지전자 주식회사 | Data transmission method and data retransmission method |
KR101319870B1 (en) * | 2006-01-05 | 2013-10-18 | 엘지전자 주식회사 | Method for handover in mobile communication system |
WO2007091964A2 (en) | 2006-02-06 | 2007-08-16 | Abb Research Ltd. | Press line system and method |
EP1982454B1 (en) | 2006-02-07 | 2015-07-08 | Telefonaktiebolaget L M Ericsson (publ) | A method and node for providing adaptive segmentation |
KR100879613B1 (en) | 2006-02-27 | 2009-01-21 | 삼성전자주식회사 | Method and apparatus for non-schedule transmission of packet service in mobile telecommunication system |
EP3048849B1 (en) | 2006-03-07 | 2017-06-21 | Panasonic Corporation | Overhead reduction of uplink control signaling in a mobile communication system |
CN101479982A (en) | 2006-05-01 | 2009-07-08 | 株式会社Ntt都科摩 | Base station, mobile station, and communication method |
EP1853014B1 (en) | 2006-05-02 | 2017-08-02 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting/receiving packet in mobile communication system |
CN102801512B (en) | 2006-07-06 | 2013-08-07 | 广东新岸线计算机系统芯片有限公司 | Method and device for selecting enhanced type uplink transmission format combination |
US8208474B2 (en) * | 2006-07-31 | 2012-06-26 | Samsung Electronics Co., Ltd | Method and apparatus for transmitting/receiving packet in a mobile communication system |
ATE549898T1 (en) | 2006-08-21 | 2012-03-15 | Interdigital Tech Corp | METHOD AND APPARATUS FOR TRANSMITTING SCHEDULING INFORMATION IN A WIRELESS COMMUNICATIONS SYSTEM |
US8374621B2 (en) | 2006-09-29 | 2013-02-12 | Qualcomm Incorporated | Methods and apparatus for reducing the likelihood of deadlock in a wireless communication system |
US8254315B2 (en) | 2006-10-31 | 2012-08-28 | Research In Motion Limited | Method and apparatus for resegmentation of packet data for retransmission on HARQ transmission failure |
CN101222415B (en) | 2007-01-09 | 2011-07-13 | 中兴通讯股份有限公司 | Method for implementing descending protocol data unit of media access control layer |
US7738369B2 (en) | 2007-01-17 | 2010-06-15 | Agere Systems Inc. | Data structure caching for PDU re-generation and transmission in a 3G wireless network |
WO2008115448A1 (en) | 2007-03-15 | 2008-09-25 | Interdigital Technology Corporation | Flexible pdu sizes for unacknowledged mode radio link control |
EP2153569B1 (en) | 2007-05-01 | 2019-05-22 | Nokia Technologies Oy | Uplink transport format selection |
JP2008301178A (en) | 2007-05-31 | 2008-12-11 | Fujitsu Ltd | Packet data communication method, radio base station, and control station |
TW200901689A (en) | 2007-06-12 | 2009-01-01 | Interdigital Tech Corp | Transmission of radio blocks in reduced transmission time interval (RTTI) mode |
US7949012B2 (en) | 2007-08-01 | 2011-05-24 | Broadcom Corporation | High-speed uplink packet access (HSUPA) cipher multiplexing engine |
KR101415201B1 (en) | 2007-08-28 | 2014-07-04 | 삼성전자주식회사 | Apparatus and method for scheduling high speed video stream service |
US8179877B2 (en) | 2007-09-28 | 2012-05-15 | Interdigital Patent Holdings, Inc. | Method and apparatus for creating an enhanced medium access control packet data unit for enhanced transport format combination selection in wireless communications |
US7792031B2 (en) | 2008-07-03 | 2010-09-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Optimal fragmentation of multicast packets |
EP2351449B1 (en) | 2008-11-24 | 2013-01-02 | Telefonaktiebolaget L M Ericsson (PUBL) | Improved uplink segmentation |
US8514779B2 (en) | 2009-04-13 | 2013-08-20 | Qualcomm Incorporated | Radio link control protocol data unit size selection in dual carrier HSUPA |
CN102428725B (en) | 2009-04-24 | 2015-05-13 | 交互数字专利控股公司 | Method and apparatus for generating a radio link control protocol data unit for multi-carrier operation |
-
2008
- 2008-09-26 CN CN2008801089903A patent/CN101809917B/en active Active
- 2008-09-26 TW TW97137315A patent/TWI474653B/en active
- 2008-09-26 TW TW101107764A patent/TWI484783B/en not_active IP Right Cessation
- 2008-09-26 EP EP08836255.3A patent/EP2203996B1/en active Active
- 2008-09-26 WO PCT/US2008/077812 patent/WO2009045882A2/en active Application Filing
- 2008-09-26 AU AU2008308969A patent/AU2008308969B2/en active Active
- 2008-09-26 CN CN2008801089886A patent/CN101809916B/en active Active
- 2008-09-26 JP JP2010527197A patent/JP5211169B2/en active Active
- 2008-09-26 TW TW97137294A patent/TWI467988B/en active
- 2008-09-26 US US12/239,023 patent/US8879534B2/en active Active
- 2008-09-26 MX MX2010003342A patent/MX2010003342A/en active IP Right Grant
- 2008-09-26 KR KR1020147033268A patent/KR20140144309A/en not_active Application Discontinuation
- 2008-09-26 TW TW103145090A patent/TW201515488A/en unknown
- 2008-09-26 TW TW103133815A patent/TW201531120A/en unknown
- 2008-09-26 AU AU2008309000A patent/AU2008309000B2/en active Active
- 2008-09-26 EP EP08835626A patent/EP2206258A2/en not_active Withdrawn
- 2008-09-26 TW TW101107754A patent/TW201251404A/en unknown
- 2008-09-26 KR KR1020107010569A patent/KR20100072354A/en active IP Right Grant
- 2008-09-26 KR KR1020107009404A patent/KR101163875B1/en active IP Right Grant
- 2008-09-26 TW TW097217489U patent/TWM350931U/en not_active IP Right Cessation
- 2008-09-26 TW TW097217483U patent/TWM351564U/en not_active IP Right Cessation
- 2008-09-26 KR KR1020137031623A patent/KR101609433B1/en not_active IP Right Cessation
- 2008-09-26 CN CN201310168159.XA patent/CN103260189B/en active Active
- 2008-09-26 KR KR1020107010243A patent/KR101381895B1/en not_active IP Right Cessation
- 2008-09-26 US US12/238,638 patent/US8094682B2/en active Active
- 2008-09-26 KR KR1020107008617A patent/KR101129131B1/en not_active IP Right Cessation
- 2008-09-26 CN CN201310392653.4A patent/CN103490853B/en active Active
- 2008-09-26 MY MYPI20101329 patent/MY151258A/en unknown
- 2008-09-26 MX MX2010003340A patent/MX2010003340A/en active IP Right Grant
- 2008-09-26 WO PCT/US2008/077918 patent/WO2009045913A2/en active Application Filing
- 2008-09-26 JP JP2010527166A patent/JP5159890B2/en active Active
- 2008-09-26 BR BRPI0816008-2A patent/BRPI0816008A2/en not_active IP Right Cessation
- 2008-09-26 KR KR1020137026579A patent/KR20130122013A/en active Search and Examination
- 2008-09-29 AR ARP080104245A patent/AR068295A1/en not_active Application Discontinuation
- 2008-09-30 AR ARP080104257A patent/AR068582A1/en active IP Right Grant
-
2010
- 2010-03-04 IL IL204294A patent/IL204294A/en not_active IP Right Cessation
-
2011
- 2011-12-07 US US13/313,847 patent/US9078158B2/en active Active
-
2012
- 2012-12-11 JP JP2012270816A patent/JP5703280B2/en not_active Expired - Fee Related
-
2013
- 2013-02-25 JP JP2013034451A patent/JP5746239B2/en not_active Expired - Fee Related
-
2014
- 2014-09-19 US US14/490,741 patent/US9609548B2/en active Active
-
2015
- 2015-02-23 JP JP2015033102A patent/JP5945612B2/en not_active Expired - Fee Related
- 2015-05-07 JP JP2015095255A patent/JP6062997B2/en active Active
- 2015-06-10 US US14/735,557 patent/US20150282007A1/en not_active Abandoned
-
2016
- 2016-05-30 JP JP2016107403A patent/JP2016174399A/en active Pending
-
2017
- 2017-02-14 US US15/432,118 patent/US20170156145A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6904016B2 (en) * | 2001-11-16 | 2005-06-07 | Asustek Computer Inc. | Processing unexpected transmission interruptions in a wireless communications system |
US20060106924A1 (en) * | 2004-11-12 | 2006-05-18 | Canon Kabushiki Kaisha | Data-processing device, communication method, and computer program |
US20090036061A1 (en) * | 2006-02-07 | 2009-02-05 | Sung-Duck Chun | Method for operating enhanced rlc entity and rnc entity for wcdma and system thereof |
US20090268706A1 (en) * | 2006-04-18 | 2009-10-29 | Motorola, Inc. | Optimised packet data transmission protocol in a communication system employing a transmission window |
US8094682B2 (en) * | 2007-09-28 | 2012-01-10 | Interdigital Patent Holdings, Inc. | Method and apparatus for generating radio link control protocol data units |
US9078158B2 (en) * | 2007-09-28 | 2015-07-07 | Interdigital Patent Holdings, Inc. | Method and apparatus for generating radio link control protocol data units |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018086693A1 (en) * | 2016-11-10 | 2018-05-17 | Huawei Technologies Co., Ltd. | Transmitting device, receiving device and methods thereof |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9078158B2 (en) | Method and apparatus for generating radio link control protocol data units | |
TWI434544B (en) | Method and apparatus for data security and automatic repeat request implementation in a wireless communication system | |
US9059875B2 (en) | Method and apparatus for creating an enhanced medium access control packet data unit for enhanced transport format combination selection in wireless communications | |
AU2013201919A1 (en) | Method and apparatus for selecting a radio link control protocol data unit size | |
AU2012211380A1 (en) | Method and apparatus for generating radio link control protocol data units |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |