Data transmission method for hybrid ARQ type II/III downlink of a wide-band radio communication system
Claim Score by NHIP
Abstract
A data processing method for a hybrid ARQ type II/III downlink of a wide-band radio communication system, wherein SRNC and CRNC are located on the same radio network, includes the steps of: a) generating RLC-PDU in a RLC layer of the SRNC and generating a PDU having RLC-PDU information needed for supporting the hybrid ARQ type II/III based on a header of the RLC-PDU (HARQ-RLC-Control-PDU); b) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU to a MAC-D, treating a general user part of a MAC layer through a logical channel; c) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU from the MAC-D to a MAC-C/SH, treating common/shared channel part of the MAC layer; d) transforming the PLC-PDU and the HARQ-RLC-Control-PDU to MAC-PDU and the HARQ-MAC-Control-PDU, respectively, in the MAC-C/SH, and allocating a format TFI1 of the MAC-PDU and TFI2 of the HARQ-MAC-Control-PDU, and transmitting the TFI1 and TFI2 to the MAC-D, and transmitting the MAC-PDU and the HARQ-MAC-Control-PDU to a physical layer of BTS, through a transport channel; and e) forming the TFI1 and the TFI2 in the MAC-D to a TFCI, then transmitting the TFCI to the user equipment through a first physical channel, and transforming the MAC-PDU and the HARQ-MAC-Control-PDU to a radio frame, then transmitting the radio frame to the mobile station through a second physical channel.

Term
Term ended
Projected expiry passed 18 October 2022, 3.9 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
19 claims: 2 independent, 17 dependent
- 1Broadest claimClaim Score 18, narrow(NHIP)A data processing method for a hybrid ARQ type II/III downlink of a wide-band radio communication system, wherein a serving radio network controller (hereinafter, referred to as a SRNC) which is directly connected to a user equipment to allocate wireless resources to the user equipment and provides services by interlocking with a wireless communication core network in case of a call connection and a controlling radio network controller (hereinafter, referred to as a CRNC) which controls a sharing channel of a radio network are located on the same radio network, comprising the steps of:a) generating a radio link control-protocol data unit (hereinafter, referred to as a RLC-PDU) in a radio link control (hereinafter, referred to as a RLC) layer of the SRNC and generating a ptotocol data unit having RLC-PDU information needed for supporting the hybrid ARQ type II/III based on a header of the RLC-PDU (hereinafter, referred to as a HARQ-RLC-Control-PDU);b) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU to a medium access control dedicated (hereinafter, referred to as a MAC-D), treating a general user part of a MAC layer, through a logical channel;c) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU of the MAC-D to a medium access control common/shared (hereinafter, referred to as a MAC-C/SH), treating a common/shared channel part of the MAC layer;d) transforming the RLC-PDU and the HARQ-RLC-Control-PDU to MAC-PDU and the HARQ-MAC-Control-PDU, respectively, in the MAC-C/SH and allocating a transport format indicator 1 (TFI1) of the MAC-PDU and a transport format indicator 2 (TFI2) of the HARQ-MAC-Control-PDU and transmitting the TFI1 and TFI2 to the MAC-D, and transmitting the MAC-PDU and the HARQ-MAC-Control-PDU to a physical layer of BTS, through a transport channel;and e) forming the TFI1 and the TFI2 in the MAC-D to a transport format combination set (TFC1), then transmitting the TFC1 to the user equipment through a first physical channel, and transforming the MAC-PDU and the HARQ-MAC-Control-PDU to a radio frame, then transmitting the radio frame to the mobile station through a second physical channel.
- 17A computer readable data recording media having instructions for implementing a method for a hybrid ARQ type II/III on a downlink of a wide-band radio communication system, wherein a serving radio network controller (hereinafter, referred to as a SRNC) which is directly connected to a user equipment to allocate wireless resources to the user equipment and provides services by interlocking with a wireless communication core network in case of a call connection and a controlling radio network controller (hereinafter, referred to as a CRNC) which controls a sharing channel of a radio network are located on the same radio network, comprising the functions of:a) generating a radio link control-protocol data unit (hereinafter, referred to as a RLC-PDU) in a radio link control (hereinafter, referred to as a RLC) layer of the SRNC and generating a protocol data unit having RLC-PDU information needed for supporting the hybrid ARQ type II/III based on a header of the RLC-PDU (hereinafter, referred to as a HARQ-RLC-Control-PDU);b) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU to a medium access control dedicated (hereinafter, referred to as a MAC-D) treating a general user part of a MAC layer through a logical channel;c) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU of the MAC-D to a medium access control common/shared (hereinafter, referred to as a MAC-C/SH), treating a common/shared channel part of the MAC layer;d) transforming the RLC-PDU and the HARQ-RLC-Control-PDU to MAC-PDU and the HARQ-MAC-Control-PDU, respectively, in the MAC-C/SH and allocating a transport format indicator 1 (TFI1) of the MAC-PDU and a transport format indicator 2 (TFI2) of the HARQ-MAC-Control-PDU and transmitting the TFI1 and TFI2 to the MAC-D, and transmitting the MAC-PDU and the HARQ-MAC-Control-PDU to a physical layer of BTS, through a transport channel;and e) forming the TFI1 and the TFI2 in the MAC-D to a transport format combination set (TFCI), then transmitting the TFCI to the user equipment through a first physical channel, and transforming the MAC-PDU and the HARQ-MAC-Control-PDU to a radio frame, then transmitting the radio frame to the mobile station through a second physical channel.
Independent claims2
121 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
[0001] The present invention relates to a data processing method for hybrid automatic repeat for request (hereinafter, referred to as an ARQ) type II/III on a downlink of a wide-band radio communication system; and, more particularly, to a method for processing a radio link control protocol data unit (RLC-PDU) and a HARQ-RLC-Control-PDU, which is extracted from the RLC-PDU, by using a transport channel such as a downlink shared channel (DSCH), wherein the RLC-PDU is used in W-CDMA based on a next generation mobile communication network, such as an international mobile telecommunication (IMT)-2000 and a universal mobile telecommunications system (UMTS), and to a recording media having a computer readable program for carrying out the method.
DESCRIPTION OF THE PRIOR ART
[0002] Terms used in this specification will be described.
[0003] “A radio network controller-radio link control (RNC-RLC)” is a radio link control protocol level entity of a radio network controller (RNC).
[0004] “A radio network controller-medium access control dedicated entity (RNC-MAC-D)” is a medium access control protocol level dedicated entity of a radio network controller (RNC).
[0005] “A radio network controller-medium access control common/shared entity (RNC-MAC-C/SH)” is a medium access control protocol level terminal common/shared entity of a radio network controller (RNC).
[0006] “Node B-L1” is a physical channel layer entity of a node B. The node B represents a base transceiver station (BTS) in an asynchronous IMT-2000 system. In this specification, the node B is used as the same meaning as the base transceiver station (BTS).
[0007] “User equipment-L1 (UE-L1)” is a physical channel level entity of a user equipment (UE) (or a mobile station).
[0008] “User equipment-medium access control common/shared dedicated entity (UE-MAC-C/SH)” is a medium access control protocol level terminal common/shared entity of a user equipment (UE) (or a mobile station).
[0009] “User equipment-medium access control dedicated entity (UE-MAC-D)” is a medium access control protocol level terminal dedicated entity of a user equipment (UE) (or a mobile station).
[0010] “User equipment-radio link control (UE-RLC)” is a radio link control protocol level entity of a user equipment (UE) (or a mobile station).
[0011] “User equipment-radio resource control (UE-RRC)” is a radio resource control protocol level entity of a user equipment (UE) (or a mobile station).
[0012] “Iub” denotes an interface between the RNC and the Node B (BTS).
[0013] “Iur” denotes an interface between the RNC and another RNC.
[0014] “Uu” denotes an interface between the Node B and the UE.
[0015] “Logical channel” is a logical channel used for transmitting and receiving data between the RLC protocol entity and MAC protocol entity.
[0016] “Transport channel” is a logical channel used for transmitting and receiving data between the MAC protocol entity and a physical layer.
[0017] “Physical channel” is a practical channel used for transmitting and receiving data between a mobile station and a BTS.
[0018] When transporting the data from a radio network of a UMTS terrestrial radio access network (UTRAN) to the mobile station (MS), a Hybrid ARQ type II/III which has superior throughput than a Hybrid ARQ type I may be used.
[0019]FIG. 2 is a diagram showing a general wide-band radio communication network (WCDMA). A UTRAN environment is used as an example in this drawing.
[0020] As described in FIG. 2, the UTRAN includes a user equipment (UE) <b>10</b>, an asynchronous radio network <b>20</b> and a radio communication core network <b>30</b>, such as a GSM-MAP core network.
[0021] A Hybrid ARQ type II/III is adapted between the UE and the asynchronous radio network <b>200</b>. When a received data has an error, a receiving part requests a transmission part to re-transmit the received data.
[0022] A protocol stack structure in the above-referenced interlocking structure is illustrated in FIG. 4.
[0023]FIG. 3 is a diagram showing a general UTRAN. In FIG. 3, the In is an interface between the radio communication core network <b>300</b> and the asynchronous radio network <b>200</b>, and, the Iur means a logical interface between radio network controllers (RNC) of the asynchronous radio networks <b>200</b> and the lub shows an interface between the RNC and the Node B. Meanwhile, the Uu shows a radio interface between the UTRAN and the UE.
[0024] In here, the Node B is a logical node, which is responsible for a radio transmission/receiving from one or more cell to the UE.
[0025] Generally in the UTRAN, if a received data has an error, the receiving part requests re-transmission of the data to the transmission part by using an automatic repeat request (ARQ) method. The ARQ method is divided to ARQ type I, II and III, and technical characteristics of each type are described below.
[0026] The ARQ is an error control protocol, which automatically senses an error during transmission and then requests re-transmission of the error-containing block. That is, the ARQ is one of data transmission error control methods, and when an error is detected, automatically generates a re-transmission request signal to cause re-transmission of the data.
[0027] The ARQ method is used in the UTRAN for a transmission packet data. The receiving part requests the transmission part to re-transmit an error-containing packet. However, when using the ARQ method, if the number of re-transmission requests are increased, then the throughput, which is amount of data transmitted in a predetermined period, is decreased. To solve the problem, the ARQ can be used along with a forward error correction coding (FEC) method, which is called as a hybrid ARQ.
[0028] The hybrid ARQ has three types I, II and III.
[0029] In case of type I, one coding rate is selected, for example, one coding rate selected from no coding, rate 1/2 and rate 1/3 of convolutional codings, according to channel environment or required quality of service (QoS) and the selected coding rate is continuously used. If there is a re-transmit request, the receiving part removes pre-received data and the transmission part re-transmits the data with the pre-transmitted coding rate. In this case, the coding rate is not changed according to changeable channel environment, so, when compared with the type II and III the throughput may be decreased.
[0030] In case of type II ARQ, if the receiving part requests data re-transmission, then the data is stored onto a buffer at the receiver and the stored data is combined with the retransmitted data. That is, at first, the data is transmitted with a high coding rate and in case of re-transmitting, the data is transmitted with a lower coding rate and it is combined with the pre-received stored data to increase efficiency compared to the type I. For example, a convolutional coding rate 1/4, which is a mother code, may generates coding rates 8/9, 2/3 or 1/4 by puncturing, and it is called a rate compatible punctured convolutional (RCPC) code. The RCPC code is illustrated in FIG. 1.
[0031] Meanwhile, a rate compatible punctured turbo (RCPT) code is obtained by puncturing a turbo code. Referring to FIG. 1, at first, a data is transmitted with a coding rate of 8/9, and this version of the data is called as ver(0), an error is detected in the data by checking a cyclic redundancy check (CRC) and the data is stored to a buffer and re-transmission is requested. At this time, the re-transmission is performed with a coding rate 2/3 and the re-transmission version is designated ver(1).
[0032] The receiving part combines the ver(0) data stored in the buffer and the ver(1) data, then the combined data is decoded and checked by the CRC. The above-referenced process is repeated until no error is detected, then, the last transmitted ver(n) is combined with a pre-transmitted ver(n−a)(0<a<n).
[0033] The type III ARQ is similar to the type II ARQ. It is different in that the re-transmitted ver(n) data is decoded before combined with the ver(n−a) data, and checked by the CRC then, if there is no error, the ver(n) data is transmitted to an upper layer. If an error is detected, the retransmitted ver(n) data is combined with ver(n−a) and checked by the CRC to determine if further data re-transmission is necessary.
[0034] Accordingly, the hybrid ARQ type II/III is used for efficient data transmission in the UTRAN.
[0035] The hybrid ARQ type II/III combines a first data which is encoded with a high coding rate and a re-transmit data which is encoded with a low coding rate in the receiver to increase the throughput. Therefore, relational information between a sequence number and a retransmitted version of a protocol data unit (PDU) is needed to be known in advance. The relation information should be transmitted with a low coding rate, regardless of the retransmission coding rate, thereby ensuring its quality of communication.
[0036] However, for the hybrid ARQ type II/III in the UTRAN, the data is transmitted with the high coding rate, thereby increasing the possibility of an error of a header of a RLC-PDU. Therefore, a method of stably transmitting the RLC-PDU header is required.
SUMMARY OF THE INVENTION
[0037] It is, therefore, an object of the present invention to provide a data delivery method for hybrid ARQ type II/III on the downlink of wide-band radio communication system and a computer readable recording media for having instructions for performing the method.
[0038] In accordance with an aspect of the present invention, there is provided a data processing method for a hybrid ARQ type II/III on a downlink of a wide-band radio communication system, wherein a serving radio network controller (hereinafter, referred to as a SRNC) which is directly connected to a user equipment to allocate wireless resources to the user equipment and provides services by interlocking with a wireless communication core network in case of a call connection and a controlling radio network controller (hereinafter, referred to as a CRNC) which controls a sharing channel of a radio network are located on the same radio network, comprising the steps of: a) generating a radio link control-protocol data unit (hereinafter, referred to as a RLC-PDU) in a radio link control (hereinafter, referred to as a RLC) layer of the SRNC, and generating a part having RLC-PDU information needed for supporting the hybrid ARQ type II/III based on a header of the RLC-PDU (hereinafter, referred to as a HARQ-RLC-Control-PDU); b) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU to a medium access control dedicated (hereinafter, referred to as a MAC-D) treating a general user part of a MAC layer through a logical channel; c) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU from the MAC-D to a medium access control common/shared (hereinafter, referred to as a MAC-C/SH) treating common/shared channel part of the MAC layer; d) transforming the PLC-PDU and the HARQ-RLC-Control-PDU to MAC-PDU and the HARQ-MAC-Control-PDU, respectively, in the MAC-C/SH and allocating a transport format indicator 1 (TFI1) of the MAC-PDU and a transport format indicator 2 (TFI2) of the HARQ-MAC-Control-PDU and transmitting the TFI1 and TFI2 to the MAC-D, and transmitting the MAC-PDU and the HARQ-MAC-Control-PDU to a physical layer of BTS, through a transport channel; and e) forming the TFI1 and the TFI2 of the MAC-D to a transport format combination set (TFCI) then transmitting the TFCI to the user equipment through a first physical channel, and transforming the MAC-PDU and the HARQ-MAC-Control-PDU to a radio frame, then transmitting the radio frame to the mobile station through a second physical channel.
[0039] Also, the present invention may further comprising the step of: f) storing the RLC-PDU to a buffer, extracting the RLC-PDU of the buffer by using the HARQ-RLC-Control-PDU, transmitting the RLC-PDU to an upper layer after interpreting and transmitting the response to the radio network.
[0040] In accordance with another aspect of the present invention, there is provided a computer readable data recording media embodying instructions for the hybrid ARQ type II/III on a downlink of a wide-band radio communication system, wherein a serving radio network controller (hereinafter, referred to as a SRNC) which is directly connected to a user equipment to allocate wireless resources to the user equipment and provides services by interlocking with a wireless communication core network in case of a call connection and a controlling radio network controller (hereinafter, referred to as a CRNC) which controls a sharing channel of a radio network are located on the same radio network, comprising the functions of: a) generating a radio link control-protocol data unit (hereinafter, referred to as a RLC-PDU) in a radio link control (hereinafter, referred to as a RLC) layer of the SRNC and generating a part having RLC-PDU information needed for supporting the hybrid ARQ type II/III based on a header of the RLC-PDU (hereinafter, referred to as a HARQ-RLC-Control-PDU); b) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU to a medium access control dedicated (hereinafter, referred to as a MAC-D) treating a general user part of a MAC layer through a logical channel; c) transmitting the RLC-PDU and the HARQ-RLC-Control-PDU of the MAC-D to a medium access control common/shared (hereinafter, referred to as a MAC-C/SH) treating common/shared channel part of the MAC layer; d) transforming the PLC-PDU and the HARQ-RLC-Control-PDU to MAC-PDU and the HARQ-MAC-Control-PDU, respectively, in the MAC-C/SH and allocating a transport format indicator 1 (TFI1) of the MAC-PDU and a transport format indicator 2 (TFI2) of the HARQ-MAC-Control-PDU and transmitting the TFI1 and TFI2 to the MAC-D, and transmitting the MAC-PDU and the HARQ-MAC-Control-PDU to a physical layer of BTS, through a transport channel; and e) forming the TFI1 and the TFI2 of the MAC-D to a transport format combination set (TFCI) then transmitting the TFCI to the user equipment through a first physical channel, and transforming the MAC-PDU and the HARQ-MAC-Control-PDU to a radio frame, then transmitting the radio frame to the mobile station through a second physical channel.
[0041] Also, the present invention further comprising the step of: f) storing the RLC-PDU to a buffer, extracting the RLC-PDU of the buffer by using the HARQ-RLC-Control-PDU, transmitting the RLC-PDU to an upper layer after interpreting and transmitting the response to the radio network.
[0042] The present invention is a method for realizing the hybrid ARQ type II/III on the downlink of an asynchronous mobile communication system which includes the CRNC and the SRNC, and may be adapted in a technical field where packet data service is used.
[0043] In an asynchronous communication system which has the CRNC and the SRNC on a same asynchronous network, the present invention of using the hybrid ARQ type II/III may increase system efficiency by combining a changeable coding rate, a pre-transmitted data and a re-transmitted data.
[0044] To perform the combining on the hybrid ARQ type II/III, the receiving part may know information of the current receiving RLC-PDU, and the information composing part of the RLC-PDU should be transmitted more stably than transmitted data.
[0045] For the above, the present invention generates the HARQ-RLC-Control-PDU referring to the RLC-PDU, wherein the HARQ-RLC-Control-PUD has information of the RLC-PDU which is used for supporting the hybrid ARQ type II/III. At this time, the HARQ-RLC-Control-PDU includes sequence number of the RLC-PDU and a version number.
[0046] The RLC-PDU and the HARQ-RLC-Control-PUD are transmitted from a RLC protocol entity to a MAC-D protocol entity by using a different or same logical channel and transmitted from a MAC-C/SH protocol entity to a physical layer by using a downlink shared channel (DSCH) and transmitted to a receiving part through a physical channel, such as a physical downlink shared channel (PDSCH).
BRIEF DESCRIPTION OF THE DRAWINGS
[0047] Other objects and aspects of the invention will become apparent from the following description of the embodiments with reference to the accompanying drawings, in which:
[0048]FIG. 1 is a diagram illustrating a general RCPC or RCPT code;
[0049]FIG. 2 is a diagram showing a general W-CDMA network;
[0050]FIG. 3 is a diagram showing a general UTRAN;
[0051]FIG. 4 is a diagram showing protocol stacks in UTRAN;
[0052]FIG. 5A is a diagram showing a UTRAN when RNC has both of SRNC and CRNC function in accordance with the present invention;
[0053]FIG. 5B is a diagram showing UTRAN when RNC has CRNC function and other RNC has SRNC function in accordance with the present invention;
[0054]FIG. 6 is a diagram showing relations among conventional RLC-PU, RLC-PDU, MAC-PDU and transport block;
[0055]FIG. 7 is a diagram showing a data processing method of a transmitting part in accordance with the present invention;
[0056]FIG. 8 is a diagram showing a data processing method of a receiving part in accordance with the present invention; and
[0057]FIG. 9 is a flowchart showing a data processing method in accordance with the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0058] Hereinafter, a data processing method for hybrid ARQ type II/III on a downlink of a wide-band radio communication system according to the present invention will be described in detail referring to the accompanying drawings.
[0059] Referring to FIG. 5, an asynchronous mobile communication system having an interlocking structure is described. Under the interlocking structure, a UMS terrestrial radio access network (UTRAN) <b>200</b> may have one or more radio network controller (RNC). The RNC can perform a serving radio network controller (SRNC) function, a controlling radio network controller (CRNC) function or both functions.
[0060] In here, the SRNC function is directly connected to a mobile station <b>100</b> and allocates radio resources to the mobile station <b>100</b>, and in case of call connecting, the RNC interlocks with a radio communication core network <b>300</b> to provide service to the mobile station <b>100</b>. Only one CRNC function exists in the whole UTRAN <b>200</b> and the CRNC is a kind of RNC that controls a logical channel over the whole UTRAN <b>200</b>.
[0061] Referring to FIGS. 5A and 5B, the interlocking structure and the logical interface are illustrated. In FIG. 5A, one RNC performs both of the SRNC and the CRNC functions. In FIG. SB, one RNC performs the CRNC function and another RNC performs the SRNC function.
[0062] The present invention applies to a hybrid ARQ type II/III method in which there is one RNC having the CRNC and the SRNC functions in the UTRAN <b>200</b> and uses a transport channel, such as a downlink shared channel (DSCH), in an interlocking structure as FIG. 5A.
[0063] That is, as a preferred embodiment, the present embodiment assumes the CRNC and the SRNC exists on the same asynchronous radio network.
[0064]FIG. 6 is a diagram showing relations among conventional RLC-PU, RLC-PDU, MAC-PDU and a transport block.
[0065] As described in FIG. 6, a RLC-PDU includes one or more RLC-PU. The RLC-PDU is mapped to the MAC-PDU. The MAC-PDU is mapped to a transport block of a physical layer, and then CRC is added thereto.
[0066] In the physical layer, data is transmitted through an encoding unit, a rate matching unit, an interleaver and a modulating unit. Tin the receiving part, the CRC of the data is checked after the data passes through a demodulating unit, a deinterleaver, and decoding unit, to determine whether an error exists or not. If the error exists in the data, then the receiving part requests re-transmission of the data and stores the error-generating data in a buffer. At this time, the re-transmitted RLC-PDU is combined with the error-generating RLC-PDU to carry out a decoding, and then the CRC is checked. In this case, the sequence number and the version of currently received RLC-PDU neet to be known to carry out combining.
[0067] To solve the problem, a HARQ-RLC-Control-PDU, which has information about a header of the RLC-PDU is generated. The HARQ-RLC-Control-PDU is transmitted along with the RLC-PDU. That is, a RLC protocol entity generates the RLC-PDU and generates the HARQ-RLC-Control-PDU referring to the information on the header of the RLC-PDU.
[0068] The RLC protocol entity transmits the RLC-PDU and the HARQ-RLC-Control-PDU to a MAC-D protocol entity. At this time, the RLC-PDU and the HARQ-RLC-Control-PDU can be transmitted through a different or the same type of logical channel.
[0069] In case of using a different type of logical channel, the RLC-PDU and the HARQ-RLC-Control-PDU may use logical channels, such as a dedicated traffic channel (DTCH) and a dedicated control channel (DCCH), respectively, and MAC-Data-REQ is used as a primitive.
[0070] In case of using the same type of logical channel, the RLC-PDU and the HARQ-RLC-Control-PDU may use a logical channel such as DTCH and the MAC-Data-REQ is used as a primitive.
[0071] The MAC-D protocol entity transmits the received RLC-PDU and the HARQ-RLC-Control-PDU to a MAC-C/SH entity, and the MAC-C/SH transforms the RLC-PDU and the HARQ-RLC-Control-PDU to MAC-PDU and HARQ-MAC-Control-PDU, respectively. The data is then transmitted to the physical layer in a transport block form using a transport channel, such as the DSCH, and PHY-Data-REQ is used as a primitive.
[0072] In the physical layer, CRC is added to the transport block, received through a transport channel such as the DSCH, and the transport block is transmitted to the receiving part through a physical channel, after passing an encoding unit, a rate matching unit, an interleaver and a modulating unit.
[0073]FIG. 7 is a flow diagram showing a data processing method in a transmitter in accordance with the present invention.
[0074] As shown in FIG. 7, a RLC protocol entity, a MAC-D protocol entity, a MAC-C/SH protocol entity and a physical layer entity are initialized at step <b>701</b> by a RRC protocol entity.
[0075] After that, the RLC protocol receives data, which is to be transmitted to the receiving part, from an upper layer at step <b>702</b>. At this time, the RLC protocol entity converts the received data to RLC-PDU and generates HARQ-RLC-Control-PDU used for the hybrid ARQ type II/III based on header information of the RLC-PDU. The RLC protocol entity transmits the RLC-PDU and the HARQ-RLC-Control-PDU to the MAC-D protocol entity through a different or the same logical channel at steps <b>703</b> and <b>704</b>.
[0076] In case of using the different type of the logical channel, the RLC protocol entity transmits the RLC-PDU to the MAC-D protocol entity through a logical channel, such as the DTCH at step <b>703</b> and the HARQ-RLC-Control-PDU is transmitted to the MAC-D protocol entity through a logical channel, such as the DCCH at step <b>704</b>.
[0077] Meanwhile, in case of using the same type of the logical channel, the RLC protocol entity transmits the RLC-PDU and the HARQ-RLC-Control-PDU to the MAC-D protocol entity through a logical channel, such as the DTCH.
[0078] In this specification, for simplification, we describe the process transmitting the RLC-PDU and the HARQ-RLC-Control-PDU from the RLC protocol entity to the MAC-D protocol entity of the SRNC through different logical channels. In the RLC-protocol entity operation, a relation indicator is generated to maintain association between the RLC-PDU and the HARQ-RLC-Control-PDU, and when the RLC-PDU and the HARQ-RLC-Control-PDU are transmitted, the relation indicator may be transmitted along with each PDU.
[0079] Next, the MAC-D protocol entity that receives the RLC-PDU and the HARQ-RLC-Control-PDU from the RLC protocol entity transmits them to the MAC-C/SH protocol entity at steps <b>705</b> and <b>706</b>.
[0080] In here, the MAC-C/SH protocol entity, which receives the RLC-PDU from the MAC-D protocol entity, transforms the RLC-PDU to the MAC-PDU and schedules the DSCH transport channels to transmit the MAC-PDU through the transport channel, such as the DSCH. Then the MAC-PDU is transmitted to the physical layer of the node B through the DSCH channel at step <b>707</b>.
[0081] Moreover, the MAC-C/SH protocol entity transforms the HARQ-RLC-Control-PDU received from the MAC-D protocol entity to HARQ-MAC-Control-PDU. (To differentiate the MAC-PDUs which are transformed from the RLC-PDU and the HARQ-RLC-Control-PDU, respectively, in this specification, the former is called the MAC-PDU and the latter the HARQ-MAC-Control-PDU.) Then, the MAC-C/SH schedules the DSCH transport channels to transmit the HARQ-MAC-Control-PDU. The MAC-C/SH protocol entity transmits the HARQ-MAC-Control-PDU to the physical layer of the node B through the DSCH transport channel at step <b>708</b>.
[0082] In here, if the MAC-C/SH protocol entity receives the relation indicator from the RLC protocol entity, wherein the relation indicator denotes a relation between the RLC-PDU and the HARQ-RLC-Control-PDU, with each PDU, the MAC-C/SH protocol entity operates processes at steps <b>707</b> and <b>708</b> to the RLC-PDU and the HARQ-RLC-Control-PDU to assure that each of them has the same relation indicator value.
[0083] The MAC-C/SH protocol entity transmits a transport format indicator 1 (TFI1) and a transport format indicator 2 (TFI2) of the MAC-PDU and the HARQ-MAC-Control-PDU, respectively to the MAC-D at step <b>709</b>. The MAC-D protocol entity transmits the TFI1 and the TFI2 to the physical layer of the node B at step <b>710</b>.
[0084] After that, the physical layer of the node B which receives the MAC-PDU and the HARQ-MAC-Control-PDU carries out an encoding, a rate matching and an interleaving and modulation, then transforms the MAC-PDU and the HARQ-MAC-Control-PDU to a radio frame and transmits it to the receiver through a physical channel, such as PDSCH at step <b>712</b>.
[0085] The node B that receives TFI1, TFI2 and TFI of DCH from the MAC-D forms a transport format combination set (TFCI) and transmits the TFCI to the receiver through a physical channel, such as DPCH at step <b>711</b>.
[0086]FIG. 8 is a diagram showing a data processing method of a receiving part in accordance with the present invention.
[0087] As illustrated in FIG. 8, a RLC protocol entity, a MAC-D protocol entity, a MAC-C/SH protocol entity and a physical layer are initialized by a RRC protocol entity.
[0088] The physical layer of the receiver receives the radio frame having the RLC-PDU and the HARQ-RLC-Control-PDU transmitted through the physical channel, such as the PDSCH. The physical layer of the receiver also receives the TFCI, which is essential information to carry out the physical layer operation on the RLC-PDU and the HARQ-RLC-Control-PDU at step <b>803</b>.
[0089] Next, the physical layer of the receiving part transmits the received data to the MAC-C/SH protocol entity through the physical channel, such as the DPCH at step <b>804</b>.
[0090] The physical layer acquires the TFI2 of the HARQ-RLC-Control-PDU received through the physical channel, such as the PDSCH, from the TFCI received from the physical channel, such as the DPCH, and transforms the TFI2 to the HARQ-MAC-Control-PDU through a demodulation, a deinterleaving and a decoding process, then transmits the HARQ-MAC-Control-PDU to the MAC-C/SH protocol entity through the transport channel, such as the DSCH at step <b>804</b>.
[0091] The MAC-C/SH protocol entity receives the HARQ-MAC-Control-PDU having the HARQ-RLC-Control-PDU, and data identifier, and transforms the HARQ-MAC-Control-PDU to the HARQ-RLC-Control-PDU then transmits the HARQ-RLC-Control-PDU and the data identifier to the MAC-D protocol entity at step <b>805</b>.
[0092] Then, the MAC-D protocol entity, which receives the HARQ-RLC-Control-PDU and the data identifier, transmits them to the RLC protocol entity by using the logical channel such as the DCCH at step <b>806</b>. At this time, in case of using the same type of the logical channel, the MAC-D protocol entity, which receives the HARQ-RLC-Control-PDU and the data identifier from the MAC-C/SH protocol entity, transmits the HARQ-RLC-Control-PDU and the data identifier to the RLC protocol entity by using the logical channel, such as the DTCH.
[0093] After that, the RLC protocol entity extracts a sequence number and a version number by interpreting the received HARQ-RLC-Control-PDU and transmits CRLC-HARQ-IND primitive, which has the sequence number, the version number and the data identifier as parameters, to the RRC protocol entity, through a control SAP at step <b>807</b>.
[0094] Next, the RRC protocol entity transmits a CPHY-HARQ-REQ primitive, which has a parameter of the CRLC-HARQ-IND primitive such as the sequence number and the version number, to the physical layer through the control SAP of the RRC and L1 at step <b>808</b>.
[0095] The physical layer of the receiving part extracts the radio frame, which has the RLC-PDU stored in the buffer, and the TFI1 by using the received data identifier, then transforms the radio frame to MAC-PDU by the demodulating, the deinterleaving and the decoding process using the TFI1, the sequence number and the version number, and transmits the MAC-PDU to the MAC-C/SH protocol entity through the transport channel, such as the DSCH at step <b>809</b>.
[0096] Subsequently, the MAC-C/SH protocol entity interprets the received MAC-PDU and transforms it to the RLC-PDU, then transmits the RLC-PDU to the MAC-D protocol entity at step <b>810</b>.
[0097] The MAC-D protocol entity transmits the received RLC-PDU to the RLC protocol entity through the logical channel such as the DTCH at step <b>811</b>. The RLC protocol entity interprets the received RLC-PDU and transmits it to an upper layer at step <b>812</b>.
[0098]FIG. 9 is a flowchart showing a data processing method in accordance with the present invention.
[0099] First, RNC-RLC, which receives data from the upper layer, transforms the received data to the RLC-PDU and transmits the RLC-PDU to RNC-MAC-D protocol entity through the logical channel (MAC-D-Data-REQ primitive), such as the DTCH at step <b>901</b>.
[0100] The RNC-RLC protocol entity generates the HARQ-RLC-Control-PDU by using information in a header of the RLC-PDU. At this time, the HARQ-RLC-Control-PDU includes a sequence number and a version number. The RNC-RLC protocol entity transmits the HARQ-RLC-Control-PDU to the RNC-MAC-D protocol entity through a logical channel (MAC-D-Data-REQ primitive), such as the DCCH at step <b>902</b>.
[0101] In case of using the same type of the logical channel, the RNC-RLC protocol entity transmits the HARQ-RLC-Control-PDU to the RNC-MAC-D protocol entity through the logical channel (MAC-D-Data-REQ primitive), such as the DTCH.
[0102] Next, the RNC-MAC-D protocol entity that receives the RLC-PDU through the logical channel (MAC-D-Data-REQ primitive), such as the DTCH, transmits the RLC-PDU by using MAC-C/SH-Data-REQ primitive at step <b>903</b>.
[0103] The RNC-MAC-D protocol entity that receives the HARQ-RLC-Control-PDU through the logical channel (MAC-D-Data-REQ primitives), such as the DCCH, transmits the HARQ-RLC-Control-PDU protocol entity to the RNC-MAC-C/SH protocol entity by using the MAC-C/SH-Data-REQ primitive at step <b>904</b>.
[0104] In case of using the same type of the logical channel, the RNC-MAC-D protocol entity that receives the HARQ-RLC-Control-PDU through the logical channel (MAC-D-Data-REQ primitive), such as the DTCH, transmits the HARQ-RLC-Control-PDU to the RNC-MAC-C/SH protocol entity by using the MAC-C/SH-Data-REQ primitive.
[0105] Meanwhile, the RNC-MAC-C/SH protocol entity carries out DSCH transmission scheduling to transmit the RLC-PDU and the HARQ-RLC-Control-PDU by the transport channel, such as the DSCH, and transforms the RLC-PDU and the HARQ-RLC-Control-PDU to the MAC-PDU and the HARQ-MAC-Control-PDU, respectively, and then allocates TFL1 and TFI2, respectively at step <b>905</b>.
[0106] The RNC-MAC-C/SH protocol entity transmits the TFI1 and the TFI2 to the MAC-D protocol entity at step <b>906</b>. Then, the MAC-D protocol entity transmits the TFI1 and the TFI2 to the physical layer through a transport channel (PHY-Data-REQ primitive), such as DCH at step <b>909</b>.
[0107] Also, the RNC-MAC-C/SH protocol entity transmits the MAC-PDU to the physical layer of the node B through the transport channel (PHY-Data-REQ primitive), such as the DSCH. At this time, the transmission form is defined by an lub interface that defines an interface between the RNC and the node B.
[0108] Moreover, the RNC-MAC-C/SH protocol entity transmits the HARQ-MAC-Control-PDU to the physical layer of the node B through the transport channel (PHY-Data-REQ primitive), such as the DSCH at step <b>908</b>. At this time, the transmission form is defined by an Iub interface that defines an interface between the RNC and the node B.
[0109] After that, the physical layer of the node B transmits the received MAC-PDU and the HARQ-MAC-Control-PDU to a user equipment (UE) after transforming them to a PDSCH radio frame through the coding, the interleaving and the modulating process at step <b>910</b>.
[0110] The physical layer of the node B generates TFCI from the received TFI1 and the TFI2 and transmits the TFCI to the UE through the physical channel, such as the DPCH at step <b>911</b>.
[0111] UE-L1 of the receiving part receives the radio frame having the RLC-PDU and the HARQ-RLC-Control-PDU, through the physical channel, such as the PDSCH, and receives the TFI1 and the TFI2 through the physical channel, such as the DPCH, then carries out the demodulating, the deinterleaving and the decoding process to the radio frame having the TFI2 and the HARQ-RLC-Control-PDU. The UE-L1 stores the radio frame, which has the received TFI1 and the RLC-PDU, to the buffer and generates a data identifier to identify the radio frame stored in the buffer. After that, the UE-L1 transmits the received HARQ-RLC-Control-PDU and the data identifier to a UE-MAC-C/SH protocol entity through the transport channel (PHY-Data-IND primitive), such as the DSCH at step <b>912</b>.
[0112] After that, the UE-MAC-C/SH protocol entity transmits the HARQ-RLC-Control-PDU and the data identifier to a UE-MAC-D protocol entity by using MAC-C/SH-Data-IND primitive at step <b>913</b>.
[0113] The UE-MAC-D protocol entity transmits the HARQ-RLC-Control-PDU and the data identifier to a UE-RLC protocol entity through the logical channel (MAC-D-Data-IND primitive), such as the DCCH at step <b>914</b>. At this time, in case of using the same type of the logical channel, the UE-MAC-D protocol entity transmits the HARQ-RLC-Control-PDU and the data identifier to the UE-RLC protocol entity through the logical channel (MAC-D-Data-IND primitive), such as the DTCH.
[0114] The UE-RLC protocol entity extracts a sequence number and a version number by interpreting the received HARQ-RLC-Control-PDU. Also, the UE-RLC protocol entity transmits the data identifier, the sequence number and the version number to a UE-RRC protocol entity as a primitive of CRLC-HARQ-IND, by using a control SAP defined between the UE-RLC and the UE-RRC at step <b>915</b>.
[0115] After that, the UE-RRC protocol entity transmits CPHY-HARQ-REQ primitive, which has the received data identifier, the sequence number and the version number as a primitive parameter, to the UE-L1 by using a control SAP defined between the UE-L1 and the UE-RRC at step <b>916</b>.
[0116] Subsequently, the UE-L1 extracts the radio frame, which has the RLC-PDU stored in the buffer, and the TFI1 by using the data identifier and determines whether to perform the decoding process directly to the stored radio frame, or after combining the stored radio frame with the pre-received data based on the TFI1, the sequence number and the version number. Then, after the decoding process, the UE-L1 transmits them to a UE-MAC-C/SH protocol entity through the transport channel (PHY-Data-IND primitive), such as the DSCH at step <b>917</b>.
[0117] The UE-MAC-C/SH protocol entity transmits the received RLC-PDU to the UE-MAC-D protocol entity by using MAC-C/SH-Data-IND at step <b>918</b>.
[0118] Accordingly, the LE-MAC-D protocol entity transmits the received RLC-PDU to the UE-RLC protocol entity through the logical channel (MAC-D-Data-IND primitive), such as the DTCH at step <b>919</b>.
[0119] Finally, the UE-RLC protocol entity interprets the received RLC-PDU and transmits it to an upper layer after transforming the RLC-PDU to the original data form, and then transforms the response to a RNC-RLC protocol entity at step <b>920</b>.
[0120] In the present invention, in case of an asynchronous mobile communication system that uses the hybrid ARQ type II/III, there needs be no changes to a conventional RLC protocol entity operation. That is, the pre-determined kinds and format of the RLC data PDU and the control PDU are not changed and HARQ-RLC-Control-PDU of a new RLC-PDU type are added.
[0121] Although the preferred embodiments of the invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims.
Contents5
11 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2006007874A1 | Cited by | United States of America | Pre-grant |
| US2010246382A1 | Cited by | United States of America | Pre-grant |
| US8588167B2 | Cited by | United States of America | Applicant |
| US2002172208A1 | Cited by | United States of America | Pre-grant |
| US8345611B2 | Cited by | United States of America | Applicant |
| US10368389B2 | Cited by | United States of America | Applicant |
| US8625503B2 | Cited by | United States of America | Applicant |
| US8422510B2 | Cited by | United States of America | Applicant |
| US8711780B2 | Cited by | United States of America | Applicant |
| US7978616B2 | Cited by | United States of America | Applicant |
| US8767606B2 | Cited by | United States of America | Applicant |
| US9072115B2 | Cited by | United States of America | Applicant |
| US2011081868A1 | Cited by | United States of America | Pre-grant |
| US2011216706A1 | Cited by | United States of America | Pre-grant |
| US2011216705A1 | Cited by | United States of America | Pre-grant |
| US2005135291A1 | Cited by | United States of America | Pre-grant |
| US2011019604A1 | Cited by | United States of America | Pre-grant |
| US2008137652A1 | Cited by | United States of America | Pre-grant |
| US2011228746A1 | Cited by | United States of America | Pre-grant |
| US8160012B2 | Cited by | United States of America | Applicant |
| US8271844B2 | Cited by | United States of America | Applicant |
| US2006067364A1 | Cited by | United States of America | Pre-grant |
| US2011223952A1 | Cited by | United States of America | Pre-grant |
| US8743797B2 | Cited by | United States of America | Applicant |
| US2010254480A1 | Cited by | United States of America | Pre-grant |
| US2010182992A1 | Cited by | United States of America | Pre-grant |
| US10038701B2 | Cited by | United States of America | Applicant |
| US2009323646A1 | Cited by | United States of America | Pre-grant |
| US9813427B2 | Cited by | United States of America | Applicant |
| US2005270975A1 | Cited by | United States of America | Pre-grant |
| US8149768B2 | Cited by | United States of America | Applicant |
| US9060238B2 | Cited by | United States of America | Applicant |
| US2010265896A1 | Cited by | United States of America | Pre-grant |
| US2010215013A1 | Cited by | United States of America | Pre-grant |
| US2008220792A1 | Cited by | United States of America | Pre-grant |
| US8665815B2 | Cited by | United States of America | Applicant |
| US9867228B2 | Cited by | United States of America | Search report |
| US2005135284A1 | Cited by | United States of America | Pre-grant |
| US7649907B2 | Cited by | United States of America | Search report |
| US2011158197A1 | Cited by | United States of America | Pre-grant |
| US8411583B2 | Cited by | United States of America | Applicant |
| US8249103B2 | Cited by | United States of America | Applicant |
| USRE49739E | Cited by | United States of America | Applicant |
| WO2005125109A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9584296B2 | Cited by | United States of America | Applicant |
| US8150411B2 | Cited by | United States of America | Search report |
| US8040913B2 | Cited by | United States of America | Applicant |
| US8190144B2 | Cited by | United States of America | Applicant |
| US8687565B2 | Cited by | United States of America | Applicant |
| US2009080380A1 | Cited by | United States of America | Pre-grant |
| WO2005125109A2 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2009203374A1 | Cited by | United States of America | Pre-grant |
| US8681608B2 | Cited by | United States of America | Applicant |
| WO2009054656A2 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9661524B2 | Cited by | United States of America | Applicant |
| US9596058B2 | Cited by | United States of America | Applicant |
| US8520510B2 | Cited by | United States of America | Applicant |
| US2009323592A1 | Cited by | United States of America | Pre-grant |
| US8488523B2 | Cited by | United States of America | Applicant |
| US2009252145A1 | Cited by | United States of America | Pre-grant |
| US10536254B2 | Cited by | United States of America | Applicant |
| US7839888B2 | Cited by | United States of America | Applicant |
| US2010190504A1 | Cited by | United States of America | Pre-grant |
| US9084125B2 | Cited by | United States of America | Applicant |
| US9100896B2 | Cited by | United States of America | Applicant |
| US2008253346A1 | Cited by | United States of America | Pre-grant |
| US2009245282A1 | Cited by | United States of America | Pre-grant |
| US8027356B2 | Cited by | United States of America | Applicant |
| US2010135202A1 | Cited by | United States of America | Pre-grant |
| US8422385B2 | Cited by | United States of America | Applicant |
| US11159280B2 | Cited by | United States of America | Applicant |
| US9668282B2 | Cited by | United States of America | Applicant |
| US8537857B2 | Cited by | United States of America | Applicant |
| US2005135403A1 | Cited by | United States of America | Pre-grant |
| US2010208597A1 | Cited by | United States of America | Pre-grant |
| US7639659B2 | Cited by | United States of America | Search report |
| US8509167B2 | Cited by | United States of America | Applicant |
| US2016021701A1 | Cited by | United States of America | Pre-grant |
| US2009245281A1 | Cited by | United States of America | Pre-grant |
| US2005135318A1 | Cited by | United States of America | Pre-grant |
| CN102308503A | Cited by | China | Search report |
| US8315641B2 | Cited by | United States of America | Applicant |
| US8437328B2 | Cited by | United States of America | Applicant |
| US2010128669A1 | Cited by | United States of America | Pre-grant |
| US2010142457A1 | Cited by | United States of America | Pre-grant |
| US7286563B2 | Cited by | United States of America | Search report |
| US9699778B2 | Cited by | United States of America | Applicant |
| USRE48836E | Cited by | United States of America | Applicant |
| US9094203B2 | Cited by | United States of America | Applicant |
| US8270348B2 | Cited by | United States of America | Applicant |
| US9565699B2 | Cited by | United States of America | Applicant |
| US2005243831A1 | Cited by | United States of America | Pre-grant |
| US10567119B2 | Cited by | United States of America | Search report |
| US2009232058A1 | Cited by | United States of America | Pre-grant |
| WO2004043018A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8582430B2 | Cited by | United States of America | Search report |
| US8243931B2 | Cited by | United States of America | Applicant |
| US8824376B2 | Cited by | United States of America | Applicant |
| US9264160B2 | Cited by | United States of America | Applicant |
| US9008006B2 | Cited by | United States of America | Applicant |
30 members in 3 offices
Priority claims28
| Document | Office | Kind | Date |
|---|---|---|---|
| 20000018646 | Republic of Korea | A | |
| 20000018646 | Republic of Korea | A | |
| 20000025966 | Republic of Korea | A | |
| 20000025966 | Republic of Korea | A | |
| 20000035455 | Republic of Korea | A | |
| 20000035455 | Republic of Korea | A | |
| 20000035456 | Republic of Korea | A | |
| 20000035456 | Republic of Korea | A | |
| 20000045162 | Republic of Korea | A | |
| 20000045162 | Republic of Korea | A | |
| 20000048435 | Republic of Korea | A | |
| 20000048435 | Republic of Korea | A | |
| 20000063613 | Republic of Korea | A | |
| 20000063613 | Republic of Korea | A | |
| 200018646 | – | – | – |
| 200025966 | – | – | – |
| 200035455 | – | – | – |
| 200035456 | – | – | – |
| 200045162 | – | – | – |
| 200048435 | – | – | – |
| 200063613 | – | – | – |
| KR20000018646 | – | – | – |
| KR20000025966 | – | – | – |
| KR20000035455 | – | – | – |
| KR20000035456 | – | – | – |
| KR20000045162 | – | – | – |
| KR20000048435 | – | – | – |
| KR20000063613 | – | – | – |
Members30
| Document | Office | Kind | |
|---|---|---|---|
| KR20010095517A | Republic of Korea | A | |
| KR20010104823A | Republic of Korea | A | |
| JP2001352315A | Japan | A | |
| JP2001359173A | Japan | A | |
| US2002001296A1 | United States of America | A1 | |
| KR20020000650A | Republic of Korea | A | |
| KR20020001174A | Republic of Korea | A | |
| JP2002009742A | Japan | A | |
| JP2002009743A | Japan | A | |
| US2002009999A1 | United States of America | A1 | |
| US2002015416A1 | United States of America | A1 | |
| KR20020012100A | Republic of Korea | A | |
| KR20020012101A | Republic of Korea | A | |
| KR20020012102A | Republic of Korea | A | |
| KR20020012103A | Republic of Korea | A | |
| US2002021698A1 | United States of America | A1 | |
| KR20020015297A | Republic of Korea | A | |
| JP3469560B2 | Japan | B2 | |
| JP3507809B2 | Japan | B2 | |
| JP3507810B2 | Japan | B2 | |
| US6731623B2 | United States of America | B2 | |
| JP3569724B2 | Japan | B2 | |
| KR100624617B1 | Republic of Korea | B1 | |
| KR100624618B1 | Republic of Korea | B1 | |
| KR100624619B1 | Republic of Korea | B1 | |
| KR100641766B1 | Republic of Korea | B1 | |
| KR100641767B1 | Republic of Korea | B1 | |
| KR100641768B1 | Republic of Korea | B1 | |
| KR100696336B1 | Republic of Korea | B1 | |
| KR100703106B1 | Republic of Korea | B1 |
35 transactions on the USPTO file
Allowed without a rejection on record.
- Non-final rejections
- 0
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | |
|---|---|
| Change in Power of Attorney (May Include Associate POA) | |
| Correspondence Address Change | |
| Change in Power of Attorney (May Include Associate POA) | |
| Correspondence Address Change | |
| Recordation of Patent Grant Mailed | |
| Patent Issue Date Used in PTA CalculationAllowed | |
| Issue Notification MailedAllowed | |
| Receipt into Pubs | |
| Application Is Considered Ready for Issue | |
| Receipt into Pubs | |
| Issue Fee Payment Verified | |
| Issue Fee Payment Received | |
| Receipt into Pubs | |
| Workflow - File Sent to Contractor | |
| Receipt into Pubs | |
| Dispatch to Publications | |
| Mail Notice of AllowanceAllowed | |
| Notice of Allowance Data Verification CompletedAllowed | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Application Dispatched from OIPE | |
| Application Is Now Complete | |
| Information Disclosure Statement (IDS) Filed | |
| Information Disclosure Statement (IDS) Filed | |
| Request for Foreign Priority (Priority Papers May Be Included) | |
| Notice Mailed--Application Incomplete--Filing Date Assigned | |
| Correspondence Address Change | |
| IFW Scan & PACR Auto Security Review | |
| Workflow - Drawings Finished | |
| Workflow - Drawings Matched with File at Contractor | |
| Initial Exam Team nn |
19 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Fee payment procedurePAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee payment procedurePAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee reminder mailedREMI | REMI | |
| Fee paymentFPAY | FPAY | |
| Fee payment procedurePAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2002009999
- Publication, EPODOC
- US2002009999
- Application
- 9832250
- Application, DOCDB
- 83225001
- Application, EPODOC
- US20010832250
Titles
- English
- Data transmission method for hybrid ARQ type II/III downlink of a wide-band radio communication system
Patent term adjustment
- A delay
- +596 daysthe office missed an examination deadline
- Applicant delay
- −40 days
- Net adjustment
- 556 days
Classification
- CPC, 7
- H04L1/0069
- H04L1/0059
- H04L1/0066
- H04L1/1819
- H04L1/1896
- H04W4/18
- H04W88/12
- IPC, 7
- H04L1 16
- H04L1 00
- H04L1 18
- H04L12 28
- H04L29 10
- H04W28 04
- H04W84 12
- USPC, 2
- 455454000
- 455455000