Method for transmitting status report of pdcp layer in mobile telecommunications system and receiver of mobile telecommunications

<u>TECHNICAL FIELD</u>

0001The present invention relates to a method for transmitting a PDCP status report for reporting to another party a reception status of a PDCP SDU in a PDCP layer in Long Term Evolution (LTE) system.

<u>BACKGROUND ART</u>

0002<figref idref="f0001">Figure 1</figref> shows an exemplary network structure of a Long Term Evolution (LTE) system as a related art mobile communication system. The LTE system is a system that has evolved from the existing UMTS system, and its standardization work is currently being performed by the 3GPP standards organization.

0003The LTE network can roughly be divided into an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) and a Core Network (CN). The E-UTRAN generally comprises a terminal (i.e., User Equipment (UE)), a base station (i.e., eNode B), an Access Gateway (aGW) that is located at an end of the network and connects with one or more external networks. The aGW may be divided into a portion for handling user traffic and a portion for processing control traffic. In this case, the access gateway part that processes the user traffic and the access gateway part that processes the control traffic may communicate with a new interface. One or more cells may exist in a single eNB. An interface may be used for transmitting user traffic or control traffic between eNBs. The CN may include the access gateway and a node or the like for user registration of the UE. An interface for discriminating the E-UTRAN and the CN may be used.

0004<figref idref="f0002">Figure 2</figref> shows an exemplary control plane architecture of a radio interface protocol between a terminal and an E-UTRAN according to the 3GPP radio access network standard. <figref idref="f0003">Figure 3</figref> shows an exemplary user plane architecture of a radio interface protocol between a terminal and an E-UTRAN according to the 3GPP radio access network standard.

0005Hereinafter, structures of radio interface protocols between a terminal and an E-UTRAN will be described with reference to <figref idref="f0002">Figs. 2</figref> and <figref idref="f0003">3</figref>.

0006The radio interface protocol is horizontally comprised of a physical layer, a data link layer, and a network layer, and vertically comprised of a user plane for transmitting user data and a control plane for transferring control signaling. The protocol layer as shown in <figref idref="f0002">Figs. 2</figref> and <figref idref="f0003">3</figref> may be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based upon the lower three layers of the Open System Interconnection (OSI) standards model that is widely known in the field of communication systems. These radio protocol layers exist as pairs between the terminal and the E-UTRAN and handle a data transmission over a radio interface.

0007Hereinafter, particular layers of the radio protocol control plane of <figref idref="f0002">Fig. 2</figref> and of the radio protocol user plane of <figref idref="f0003">Fig. 3</figref> will be described below.

0008The physical layer (Layer 1) uses a physical channel to provide an information transfer service to a higher layer. The physical layer is connected with a medium access control (MAC) layer located thereabove via a transport channel, and data is transferred between the physical layer and the MAC layer via the transport channel. The transport channel is divided into a dedicated transport channel and a common channel according to whether or not a channel is shared. Also, between respectively different physical layers, namely, between the respective physical layers of the transmitting side (transmitter) and the receiving side (receiver), data is transmitted via a physical channel.

0009The second layer includes various layers. First, a medium access control (MAC) layer performs mapping various logical channels to various transport channels and performs logical channel multiplexing by mapping several logical channels to a single transport channel. The MAC layer is connected to an upper layer called a radio link control (RLC) layer by a logical channel. The logical channel is divided into a control channel that transmits information of the control plane and a traffic channel that transmits information of the user plane according to a type of transmitted information.

0010An RLC (Radio Resource Control) layer of the second layer segments and/or concatenates data received from an upper layer to adjust the data size so as for a lower layer to suitably transmit the data to a radio interface. In addition, in order to guarantee various QoSs (Quality of services) required by each radio bearer RB, the RLC layer provides three operational modes: a TM (Transparent Mode); a UM (Unacknowledged Mode); and an AM (Acknowledged Mode). In particular, the RLC layer operating in the AM (referred to as an 'AM RLC layer', hereinafter) performs a retransmission function through an automatic repeat and request (ARQ) function for a reliable data transmission.

0011A packet data convergence protocol (PDCP) layer of the second layer performs a function called header compression that reduces the size of a header of an IP packet, which is relatively large and includes unnecessary control information, in order to effectively transmit the IP packet such as an IPv4 or IPv6 in a radio interface having a narrow bandwidth. The header compression increases transmission efficiency between radio interfaces by allowing the header part of the data to transmit only the essential information.

0012The RRC layer located at the lowermost portion of the third layer is defined only in the control plane, and controls a logical channel, a transport channel and a physical channel in relation to configuration, reconfiguration, and the release of radio bearers (RBs). In this case, the RBs refer to a logical path provided by the first and second layers of the radio protocol for data transmission between the UE and the UTRAN. In general, configuration (or setup) of the RB refers to the process of stipulating the characteristics of a radio protocol layer and a channel required for providing a particular data service, and setting the respective detailed parameters and operational methods.

0013<figref idref="f0004">Figure 4</figref> shows an exemplary structure of a PDCP entity. Hereinafter, description of the PDCP entity will be given in detail. It should be noted that blocks as shown in <figref idref="f0004">Fig. 4</figref> are functional blocks, therefore there may have a difference when actually implementing such blocks.

0014The PDCP entity is upwardly connected to the RRC layer or a user application, and downwardly to the RLC layer. Detailed structure thereof is described as below.

0015One PDCP entity as shown in <figref idref="f0004">Fig. 4</figref> is comprised of a transmitting side and a receiving side. The transmitting side at the left may configure an SDU received from an upper layer as a PDU or configure control information generated by the PDCP entity itself as a PDU, and transmit the same to a peer PDCP entity as a receiving side. The receiving side at the right, the peer PDCP entity, abstracts PDCP SDU or control information from the PDCP PDU received from the transmitting side.

0016As described above, the PDU generated by the transmitting side of the PDCP entity may have two types of a Data PDU and a Control PDU. First, the PDCP Data PDU is a data block formed by processing the SDU received from the upper layer by the PDCP entity, and the PDCP Control PDU is a data block generated by the PDCP entity itself to deliver control information to the peer entity.

0017The PDCP Data PDU is generated in RBs of the user plane (U-plane) and the control plane (C-plane), and some functions of the PDCP entity are selectively applied according to the type of a used plane. That is, the header compression function is applied only to U-plane data, and an integrity protection function among the security functions is applied only to C-plane data. In addition to the integrity protection function, a ciphering function for data security may also be included in the security functions. Here, the ciphering function is applied to both the U-plane data and the C-plane data.

0018The PDCP Control PDU is generated in a U-plane RB only, and may be roughly divided into two types: a 'PDCP status report' for notifying a PDCP entity receiving buffer status to the transmitting side; and a 'Header Compression (HC) feedback packet' for notifying a status of a receiving side header decompressor to a transmitting side header compressor.

0019<figref idref="f0005">Figure 5</figref> is a block diagram illustrating processing steps of each PDCP PDU in a PDCP entity.

0020In particular, <figref idref="f0005">Fig. 5</figref> shows processing steps of the three types of PDCP PDUs (i. e., the PDCP Data PDU, the PDCP control PDU for PDCP status report, and the PDCP Control PDU for header compression feedback) in the PDCP entity through paths ① to ⑧. Descriptions of the processing paths of the PDCP entity for each type of PDUs will be given as below. <ol id="ol0001" compact="compact"><li>1. The process of handling the PDCP Data PDU in the PDCP entity is related to the paths ①, ⑧, ③ and ⑦. Hereinafter, each path will be described. <ul id="ul0001" list-style="none" compact="compact"><li>Path ①: The transmitting side PDCP performs the header compression and security on a SDU received from an upper layer, and then generates a PDCP Data PDU by adding a PDCP Sequence Number (SN), a D/C field indicating whether it is Data PDU or Control PDU, etc. into a header, thereby transmitting the same to the receiving side PDCP entity (i.e., the peer PDCP entity). Here, the header compression may be performed by a header compressor.</li><li>Path ⑧: The receiving side PDCP entity removes the header from the PDCP Data PDU delivered from the lower layer, and decompresses the PDCP SDU by performing the security check and header decompression, thereby delivering the same to the upper layer. The PDCP SDU is delivered in sequence to the upper layer. If the PDCP SDU is received out of sequence, it is reordered in a receiving buffer and then delivered to the upper layer. Here, the header decompression may be performed by a header decompressor.</li><li>Path ③: The transmitting PDCP entity may piggyback a HC feedback packet on the PDCP Data PDU (e.g., the HC feedback packet is transmitted by being added or included in the PDCP Data PDU). Here, the HC feedback packet receives information from the header decompression of the receiving side PDCP entity which is co-located to the transmitting side PDCP entity, and generates a packet by piggybacking such information on the PDCP SDU when performing the header compression on the PDCP SDU received from the upper layer. Then, the security is performed on the PDCP SDU and the piggybacked HC feedback packet, and the PDCP SN, D/C field, etc. are added into the header so as to generate the PDCP Data PDU, and thusly to be transmitted to the receiving side PDCP entity from the transmitting side PDCP entity.</li><li>Path ⑦: Upon reception of the PDCP Data PDU, the receiving side PDCP entity removes the header first, and performs the security check and the header decompression so as to decompress the PDCP SDU. Here, if the piggybacked HC feedback packet is present, it is abstracted and delivered to the header compression of the co-located transmitting side PDCP entity. Upon receiving the HC feedback packet, the header compression of the transmitting side PDCP entity may determine whether the next packet should be delivered in a full header or a compressed header according to the feedback information.</li></ul></li><li>2. The process of handling the PDCP control PDU for PDCP status report in the PDCP entity is related to the paths ② and ⑤. Hereinafter, each path will be described. <ul id="ul0002" list-style="none" compact="compact"><li>Path ②: The receiving side PDCP entity may check the receiving buffer to request a retransmission of PDCP SDU having not been received from the transmitting side PDCP entity. Here, the receiving buffer status is configured as a PDCP status report, and the configured PDCP status report is transmitted to the co-located transmitting side PDCP entity in the form of the Control PDU. Meanwhile, the header of the PDCP Control PDU may include a D/C field indicating whether the PDU is the Data PDU or the Control PDU, a Control PDU Type (CPT) field indicating whether the Control PDU includes the PDCP status report or the HC feedback packet, and the like.</li><li>Path ⑤: Upon receiving the PDCP Control PDU including the PDCP status report, the receiving side PDCP entity delivers the received PDCP status report to the co-located transmitting side PDCP entity. Based on the PDPC status report, the co-located transmitting side PDCP entity retransmits the PDCP SDU having not been received by the receiving side PDCP entity.</li></ul></li><li>3. The process of handling the PDCP Control PDU for HC feedback in the PDCP entity is related to the paths ④ and ⑥. Hereinafter, each path will be described. <ul id="ul0003" list-style="none" compact="compact"><li>Path ④: The transmitting side PDCP entity may transmit the PDCP Control PDU by independently including the HC feedback packet therein, without piggybacking the HC feedback packet on the PDCP Data PDU. Here, the HC feedback packet receives information from the header decompression of the receiving side PDCP entity which is co-located to the transmitting side PDCP entity. The HC feedback packet is configured as the PDCP Control PDU by adding the D/C field, the CPT field, etc. into the header, and then transmitted to the receiving side PDCP entity as a peer entity.</li><li>Path ⑥: Upon receiving the PDPC Control PDU including the HC feedback, the receiving side PDCP entity delivers the same to the header compression of the co-located transmitting side PDCP entity. Upon receiving the PDPC Control PDU, the header compression of the transmitting side PDCP entity may determine, according to the feedback information, whether, the next packet should be delivered in a full header or a compressed header.</li></ul></li></ol>

0021"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification (Release 8)", 3GPP TS 36.323 V8.1.0, discloses a description of the Packet Data Convergence Protocol (PDCP).

0022"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence protocol (PDCP) specification (Release 8)", 3GPP TS 36.323 V8.2.1, discloses a description of the Packet Data Convergence Protocol (PDCP).

0023<patcit id="pcit0001" dnum="WO2006118418A2"><text>WO-A2-2006118418</text></patcit> discloses a method of transmitting control information in a wireless communication system and transmission window updating method using the same are disclosed, by which transmission efficiency in a transmitting side can be enhanced. It includes the steps of receiving a first control information block including a first status report information from a receiving side, the first status information providing reception acknowledge information for a plurality of data blocks transmitted to the receiving side, receiving a second control information block including a second status report information placed as a last status report information in the second control information block, and updating the transmission window using the reception acknowledge information in the first status report information.

0024<patcit id="pcit0002" dnum="EP1626518A2"><text>EP-A2-1626518</text></patcit> discloses a bitmap structure which enables the size of a bitmap field containing reception result information to be significantly reduced while fully performing its acknowledgment function. To this end, a message region for recording indicators, which enables reception success or failure for the maximum allowable SN level packets treatable by block ACK to be confirmed, is assigned. A message region for recording only the reception results for unsuccessfully received packets is also assigned. A receiving party confirms the unsuccessfully received packets through the indicators, and retransmits the unsuccessfully received packets. Also, a transmitting party provides the number of SN level packets and the maximum number of fragmentation packets to the receiving party. The receiving party determines an optimized bitmap configuration scheme, and transmits the reception results for the respective fragmentation packets to the transmitting party based on the determined bitmap configuration scheme.

0025<patcit id="pcit0003" dnum="WO2007078142A1"><text>WO-A1-2007078142</text></patcit> discloses a method which can reduce loss in data transmission is provided. A data block is prepared in a high-level layer and the data block is transmitted in a low-level layer. Status report information associated with reception or non-reception of the data block is received through the low-level layer. When a receiver fails to receive data transmitted from a transmitter, the transmitter can rapidly recognize the reception failure and can retransmit the data.

0026<patcit id="pcit0004" dnum="WO0178286A2"><text>WO-A2-0178286</text></patcit> discloses a method and a telecommunication system for data packet numbering in packet-switched data transmission in connection with a handover, in which the responsibility for a connection is transferred from the connection between a mobile station and a first wireless telecommunication network to the connection between said mobile station and a second wireless telecommunication network. In the first wireless telecommunication network a data packet number space available for data packet numbering is bigger than a data packet number space of the second wireless telecommunication network. Data packet numbering is restricted in the first wireless telecommunication network such that the numbers of the data packets of the first wireless telecommunication network do not exceed the maximum value of the data packet number space of the second wireless telecommunication network.

0027<nplcit id="ncit0001" npl-type="s"><text>NEC in "Lower PDCP layer for Mobility", R2-061344 from TSG-RAN Working Group 2 #53, 8-12 May 2006</text></nplcit>, discloses a lossless mechanism for intra EUTRAN handover, they propose an in-sequence delivery mechanism during loseless handover.

<u>DISCLOSURE OF THE INTENTION</u>

0028As described above, the receiving side PDCP entity may use the PDCP status report to request the retransmission of the PDCP SDU having not been received from the transmitting side PDCP entity. For this, the PDCP entity should generate a PDCP Control PDU in an appropriate form and transmit the same to another party. However, the type of the format to be used for transmission has not been decided yet.

0029Therefore, it is an object of the present invention to define a format of a PDCP Control PDU which the receiving side PDCP entity uses to transmit the PDCP status report to the transmitting side PDCP entity as a peer entity. For this, the present invention is to provide a method of informing, by the PDCP entity, a receiving buffer status in the form of a bitmap.

0030The present invention provides a method for transmitting a receiving buffer status report about a Packet Data Convergence Protocol, PDCP, Service Data Unit, SDU, from a receiving side of a PDCP layer, to a transmitting side PDCP layer in a mobile communications system according to Claim 1.

0031The present invention also provides a receiving apparatus in a mobile communications system according to Claim 8.

<u>Effect</u>

0032Embodiments of the present invention has an effect of, when transmitting a PDCP status report so as to re-transmit a PDCP SDU having not been received in the PDCP layer, reducing a size of a header by effectively generating a status report as well as preventing the waste of radio resources.

<u>BRIEF DESCRIPTION OF THE DRAWINGS</u>

0033<ul id="ul0004" list-style="none" compact="compact"><li><figref idref="f0001">Figure 1</figref> shows an exemplary network structure of a Long Term Evolution (LTE) system as a related art mobile communication system;</li><li><figref idref="f0002">Figure 2</figref> shows an exemplary control plane architecture of a radio interface protocol between a terminal and an E-UTRAN according to the 3GPP radio access network standard;</li><li><figref idref="f0003">Figure 3</figref> shows an exemplary user plane architecture of a radio interface protocol between a terminal and an E-UTRAN according to the 3GPP radio access network standard;</li><li><figref idref="f0004">Figure 4</figref> is a block diagram showing a method of transmitting, by a receiving side, a status report to a transmitting side as a timer expires according to one embodiment of the present invention;</li><li><figref idref="f0005">Figure 5</figref> is a block diagram showing a method of stopping a timer as a PDU, for which the timer has been started, is received according to one embodiment of the present invention;</li><li><figref idref="f0006">Figure 6</figref> shows L2 protocol architecture and a sequential order in processing data by a transmitting side;</li><li><figref idref="f0007">Figure 7</figref> shows an exemplary format of a PDCP Control PDU for a PDCP status report according to a first embodiment of the present invention; and</li><li><figref idref="f0008">Figure 8</figref> shows an exemplary format of a PDCP Control PDU for a PDCP status report according to a second embodiment of the present invention.</li></ul>

<u>MODES FOR CARRYING OUT THE PREFERRED EMBODIMENTS</u>

0034The present invention is applied to the Long Term Evolution (LTE) system of a mobile telecommunications system, and more particularly, to an Evolved Universal Mobile Telecommunications System (E-UMTS) that has evolved from UMTS. However, without being limited thereto, the present invention may be also applied to any mobile telecommunications system and communication protocol to which technical features of the present invention is applicable.

0035Various modifications and embodiments can be made in the present invention, and reference will be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

0036However, it should also be understood that embodiments are not limited by any of the details of the foregoing description, but rather should be construed broadly within its scope and it is intended that the present invention cover modifications and variations of this invention provided they come within the scope of the appended claims.

0037Through terms including ordinal numbers such as a first, a second, etc. may be used to explain various components, the components are not limited to the terms.

0038The terms are used only for the purposed of distinguishing one component from another component. For instance, a first component may be referred to as a second component, or similarly, the second component may be referred to as the first component, without departing from the scope of the present invention. A term 'and/or' is used to include a combination of a plurality of disclosed items or one of the items.

0039In case it is mentioned that a certain component is "connected" or "accessed" to another component, it may be understood that the certain component is directly connected or accessed to the another component or that a component is interposed between the components. On the contrary, in case it is mentioned that a certain component is "directly connected" or "directly accessed" to another component, it should be understood that there is no component therebetween.

0040Terms used in the present invention is to merely explain specific embodiments, thus it is not meant to be limiting. A singular expression includes a plural expression except that two expressions are contextually different from each other. In the present invention, a term "include" or "have" is intended to indicate that characteristics, figures, steps, operations, components, elements disclosed on the specification or combinations thereof exist. Rather, the term "include" or "have" should be understood so as not to pre-exclude existence of one or more other characteristics, figures, steps, operations, components, elements or combinations thereof or additional possibility.

0041Except that they are not differently defined, all terms used in the present invention including technical or scientific terms have the same meanings with terms that are generally understood by those skilled in the art related to the field of the present invention. The terms same as those of which are defined in a general dictionary should be understood that the terms have meanings same as contextual meanings of the related art. And, as long as the terms are not definitely defined in the present invention, the terms are not interpreted as ideal or excessively formal meanings.

0042The present invention has recognized that there is no appropriate format of a PDCP Control PDU when the receiving side PDCP entity uses the PDCP status report to request the retransmission of the PDCP SDU having not been received from the transmitting side PDCP entity as a peer entity.

0043Considering such point, the present invention conceptually relates to 1) notify, by the PDCP entity, a status of a receiving buffer in the form of a bitmap, and 2) define a format of a PDCP Control PDU in the form of the bitmap to notify to the transmitting side PDCP entity as a peer entity. 3) That is, the receiving side PDCP entity expresses the reception status of each PDCP SDU in 1 bit such that reception success is set to 1 and reception failure is set to 0. 4) In particular, the presence of the reception success is not determined by whether or not the PDCP PDU has successfully been received, but by whether or not the PDCP SDU has been received. That is, if the PDCP SDU obtained by performing deciphering and header decompression on the received PDCP PDU does not have any error, it is determined to be the reception success.

0044Among the terms used in the present invention, the Sequence Number (SN) of the PDCP PDU and the Sequence Number (SN) of the PDCP SDU are distinguished from each other. Hereinafter, referring to <figref idref="f0006">Fig. 6</figref>, the difference between the PDCP PDU and the PDCP SDU, and the difference between the SN of the PDCP PDU and the SN of the PDCP SDU will be described. It should be noted that the contents in <figref idref="f0006">Fig. 6</figref> has cited from the contents related to <figref idref="f0005">Fig. 5</figref> in the specification of "Korean Patent Application No. <patcit id="pcit0005" dnum="KR1020080021112"><text>10-2008-0021112 (filed on Mar. 06, 2008</text></patcit>) (<patcit id="pcit0006" dnum="US60895720B"><text>US provisional application No. 60/895720 on Mar. 19, 2007</text></patcit>)" applied by the applicant of this invention. Meanwhile, other portions in the above application may also be cited for explanation of the present invention.

0045<figref idref="f0006">Figure 6</figref> shows L2 protocol architecture and a sequential order in processing data by a transmitting side.

0046<figref idref="f0006">Figure 6</figref> shows the sequential order in processing and transmitting data which has been received by the transmitting side of the RLC and PDCP layers in an LTE from an upper layer. The sequential order is as follows.

0047Among the terms used in the present invention, an SDU refers to data received from an upper layer and PDU refers to data transmitted to a lower layer after being received from an upper layer and processed.

0048The terms required for the explanation of the present invention, i.e., the difference between the PDCP PDU and the PDCP SDU, and the difference between the SN of the PDCP PDU and the SN of the PDCP SDU, will now be described with reference to <figref idref="f0006">Fig. 6</figref>. <ul id="ul0005" list-style="none" compact="compact"><li>S11: As shown in <figref idref="f0006">Fig. 6</figref>, the PDCP layer receives data (PDCP SDUs) to be transmitted to a lower layer, from an upper layer. The PDCP layer sets a virtual SN (Sequence Number) with respect to each PDCP SDU. In this case, the PDCP SDU SNs are sequentially set to discriminate the respective PDCP SDUs. The step S11 is performed by a first setting module. In S11 in <figref idref="f0006">Fig. 6</figref>, the SNs are not actually added to the PDCP SDUs but the respective PDCP SDUs are managed by sort of pointers (not shown) which are discriminated by each different SN. For this reason, the SNs in step S11 are expressed as virtual SNs. Furthermore, this reason makes implicit expression in step S11 in <figref idref="f0006">Fig. 6</figref> wherein each SN (i.e., virtual SN) of the PDCP SDUs is drawn by dotted lines.</li><li>S12: The PDCP layer stores the respective PDCP SDUs in a PDCP SDU buffer. This is for a source base station (i.e., source NodeB) to forward a PDCP SDU whose reception has been unconfirmed by a terminal (UE) to target base station by the source NodeB to the target NodeB during handover. When the PDCP SDUs are forwarded or re-transmitted during handover, only the PDCP SDUs that have not been properly received by the receiving side according to a status report of the RLC layer or the PDCP layer are forwarded or re-transmitted. This is called a selective forwarding/retransmission. The step 12 is performed by the PDCP SDU buffer. The 2-times virtual SN setting processes and the 3-times PDCP SDU buffering may be simultaneously performed. If the PDCP layer does not support the selective forwarding/retransmission, the PDCP SDU buffer may not be provided. </li><li>S13: A header compressor (or header compression module) sequentially performs header compression on the PDCP SDUs. In this case, the header compressor may generate a header compression feedback packet or a PDCP STATUS PDU, etc., which are unrelated to the PDCP SDUs, by itself.</li><li>S14: The PDCP layer sequentially ciphers the header-compressed PDCP SDUs. In this case, the PDCP layer performs ciphering by using virtual PDCP SNs which were set when the PDCP SDUs were stored in the buffer. Namely, the PDCP SNs act as input parameters in a ciphering algorithm to serve to generate each different ciphering mask for each SDU. The step S14 is performed by the ciphering module. Besides the ciphering operation, the PDCP layer may perform a security function including an integrity protection function. Also, in case of the integrity protection, the PDCP SDUs are integrity-protected by using virtual PDCP SNs. The PDCP layer may include packets generated by the PDCP layer itself, such as a feedback packet generated by the header compressor itself and the PDCP STATUS PDU, etc., generated by the PDCP layer itself. The feedback packet or the PDCP STATUS PDU, etc. are not ciphered because they do not have any corresponding PDCP SDUs or any set virtual PDCP SNs.</li><li>S15: The virtual PDCP SNs (i.e., the SNs set in step S11) corresponding to the respective header-compressed and ciphered PDCP SDUs through the above steps (S13 and S14) are attached to the PDCP PDU headers to form PDCP PDUs. Namely, when the PDCP PDUs are transferred to the RLC layer, the virtual PDCP SNs set in step S11 are explicitly attached to the respective SDUs as PDCP SNs. The step S15 is performed by a second setting module. In this case, because there is no virtual PDCP SN set for the feedback packet generated by the header compressor itself or the PDCP STATUS PDU generated by the PDCP layer itself, etc., the feedback packet or the PDCP STATUS PDU, etc., configure a PDCP PDU by itself without the PDCP SN. The PDCP layer transfers the thusly configured PDCP PDUs to the lower RLC layer. </li><li>S16: Upon receiving the RLC SDUs, namely, the PDCP PDUs, from the PDCP layer, the RLC layer stores them in the RLC SDU buffer. This is to flexibly support the PDU size of the RLC layer.</li><li>S17: The RLC layer stores the RLC SDUs in the SDU buffer, and when a lower MAC layer requests transmission of them at every transmission time, the RLC layer segments and/or concatenates the RLC SDUs as many as required according to the requested size. The step S17 is performed by a segmentation and concatenation module.</li><li>S18: The RLC layer sequentially attaches RLC SNs to the segmented and/or concatenated data blocks. In this case, the RLC layer may generate an RLC control PDU by itself irrespective of the RLD SDUs. The RLC SN-attached data blocks or the RLC SN-free RLC control PDU constitute RLC PDUs. The step S18 is performed by a third setting module.</li><li>S19: Because the AM RLC layer supports re-transmission, the AMC RLC layer stores the constructed RLC PDUs in an RLC PDU buffer. This is for a re-transmission that may be necessary afterwards.</li></ul>

0049The PDCP SNs in steps S11 and S15 and the RLC SN in step S18 have different properties as described above. Namely, the PDCP SNs are used for ciphering in the PDCP layer and eventually used for forwarding or re-transmitting only the PDCP data whose reception has not been confirmed by the receiving side. Meanwhile, the RLC SNs are used at the RLC layer and have a different purpose from that of the PDCP SNs. That is, in the present invention, when the SDUs are received by the PDCP layer from an upper layer, the PDCP SNs are attached to the SDUs, and when the PDCP SN-attached SDUs are transferred to the RLC layer, the RLC SNs are additionally attached thereto.

0050Reference will now be given in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts, and the same descriptions thereof are omitted.

0051The present invention defines the format of the PDCP Control PDU which the receiving side PDCP entity uses to transmit the PDCP status report to the transmitting side PDCP entity as a peer entity. For this, the present invention proposes a method for notifying, by the PDPC entity, a status of a receiving buffer in the form of a bitmap.

0052Hereinafter, description of the format (or configuration) of a bitmap in PDCP Control PDU corresponding to the PDCP status report will be given. The bitmap is comprised of one or more bits. Each bit of the bitmap includes information about a reception status report, i.e., whether or not the PDCP SDUs have successfully been received.

0053That is, the receiving side PDCP entity expresses the reception status of each PDCP SDU in 1 bit such that reception success is set to "1" and reception failure is set to "0." Here, the presence of the reception success is not determined by whether or not the PDCP PDU has successfully been received, but by whether or not the PDCP SDU has been received, i.e., if the PDCP SDU obtained by performing deciphering and header decompression on the received PDCP PDU does not have any error. That is, each bit of the bitmap of the PDCP status report acts as an indicator informing the presence of a successful reception of a single PDCP SDU.

0054Bits adjacent to each other based on a certain bit (this indicates the presence of the reception success of the PDCP SDU having the certain SN) in the bitmap include information regarding whether or not the PDCP SDUs having adjacent sequence numbers have been successfully received. Accordingly, all bitmaps serve as status reports indicating the reception status (i.e., reception success or reception failure) of all PDCP SDUs having sequence numbers within a certain range.

0055However, accurate sequence numbers of each PDCP SDU cannot be recognized by the bitmap only. In order to notify such accurate sequence numbers, a sequence number corresponding to the first or last SDU of the bitmap should be added into the PDCP Control PDU and then transmitted. In other words, if the receiving side PDCP entity transmits the reception status of the PDCP SDUs in the form of a bitmap to the transmitting side PDCP entity through the PDCP Control PDU, the transmitting side PDCP entity as a peer entity cannot determine, by using the bitmap only, whether or not PDCP SDUs have been successfully received from the received PDCP Control PDU. Therefore, information informing whether or not each bit of the bitmap indicates the PDCP SDU is needed. For this, SN information of the PDCP SDU indicated by the first or the last bit of the bitmap should be included in the PDCP Control PDU. Such SN information of the PDCP SDU may be the SN of a PDCP SDU corresponding to the first bit of the bitmap ('FSN 'in <figref idref="f0008">Fig. 8</figref>) or the SN of a PDCP SDU corresponding to the last bit ('LSN' in <figref idref="f0007">Fig. 7</figref>).

0056In addition, when there is a need to notify a length of the bitmap, the Length field indicating the length is also needed.

0057Hereinafter, description of a format of a PDCP Control PDU for the PDCP status report according to the present invention will be given with reference to <figref idref="f0007">Figs. 7</figref> and <figref idref="f0008">8</figref>.

0058<figref idref="f0007">Figure 7</figref> shows an exemplary format of a PDCP Control PDU for a PDCP status report according to a first embodiment of the present invention. Here, <figref idref="f0007">Fig. 7</figref> shows an embodiment including the 'LSN' field.

0059The format of the PDCP Control PDU in <figref idref="f0007">Fig. 7</figref> may include a LENGTH field, a LSN field and a BITMAP field, in addition to the D/C field and the Control PDU type field. Here, the LENGTH field is an optional field, and may or may not be included in the PDCP Control PDU.

0060The LENGTH field is added into the PDCP Control PDU when the length of the bitmap should be notified. When there is no need to notify the length of the bitmap, such as if the length of the bitmap is fixed or if the length of the bitmap can be derived from the length of the PDCP Control PDU, the LENGTH field is not required.

0061The bitmap field includes reception status information of each PDCP SDU indicating whether or not the PDCP SDUs received from the transmitting side PDCP and processed by the receiving side PDCP entity have been successfully received without any error. Here, the SN of the first or last PDCP SDU of the bitmap should be added to accurately notify the sequence numbers of respective PDCP SDUs corresponding to each bitmap. In <figref idref="f0007">Fig. 7</figref>, the SN of the last PDCP SDU (i.e., Last Sequence Number (LSN)) is added. In addition, <figref idref="f0007">Fig. 7</figref> shows the format of the PDCP Control PDU when the length of the bitmap should be notified.

0062Hereinafter, descriptions of a setting method for the LSN and the bitmap in <figref idref="f0007">Fig. 7</figref> will be given in detail. <ul id="ul0006" list-style="dash" compact="compact"><li>D/C: a field to indicate whether a corresponding PDCP PDU is Data PDU or Control PDU.</li><li>Control PDU Type: a field to indicate the type of corresponding control information, for instance, indicates whether the corresponding control information is a status report or a HC feedback information.</li><li>LSN field: includes an SN value of a PDCP SDU corresponding to the last bit of the bitmap field. It is an SN value of a PDCP SDU which has been lastly received or failed to receive by the receiving side PDCP entity. That is, by using the SN of the PDCP SDU corresponding to the last bit, the SNs of the PDCP SDUs indicated by each bit in the bitmap field can be recognized. This is because each bit of the bitmap indicates the reception status of sequential PDCP SDUs. Accordingly, since the last bit, i.e., the LSN, is the SN of the PDCP SDU indicated by the last bit (lowermost bit) of the bitmap, each SN of the corresponding PDCP SDUs indicated by bits below the last bit can be recognized. By using this bitmap format, the size of the PDCP Control PDU for the PDCP status report may be reduced as well as efficiency of radio resources may be enhanced.</li><li>BITMAP field: includes reception status report (information) of the PDCP SDUs received from the transmitting side PDCP entity as a peer entity. In the bitmap field including each reception status of the PDCP SDUs, target PDCP SDUs are those of which SNs are [LSN - LENGTH*8 + 1, LSN] which is between 'LSN - LENGTH*8 +1' and 'LSN.' Each bit of each bitmap has reception status information (i.e., PDCP status report) regarding whether or not the PDCP SDUs indicated by each bit have been successfully received. For instance, if an LSN value is '100' and a LENGTH value is '5,' the range of SN of the PDCP SDU as the target of the reception status report would be '61' ∼ '100.'</li></ul>

0063Each bit_position in the bitmap is 1 ∼ LENGTH*8, for instance, if the LENGTH is '5,' each bit_position would be '1' ∼ '40.' That is, the number of bits in the bitmap is 40. In other words, the number of PDCP SDUs which are the targets of the reception status reports (reception success or failure) of corresponding PDCP SDUs is 40. An interpretation method of each bit_position is as follows: <ul id="ul0007" list-style="none" compact="compact"><li>◆ 1: reception success of a PDCP SDU which is PDCP Sequence Number = (LSN - LENGTH*8 + bit_position).</li><li>◆ 0: reception failure of a PDCP SDU which is PDCP Sequence Number = (LSN - LENGTH*8 + bit_position).</li></ul>

0064Meanwhile, if the LENGTH is '0,' the Bitmap field does not exist. In this case, the LSN only is included, considering that all PDCP SDUs have been successfully received.

0065<figref idref="f0008">Figure 8</figref> shows an exemplary format of a PDCP Control PDU for a PDCP status report according to a second embodiment of the present invention. Here, <figref idref="f0008">Fig. 8</figref> shows an embodiment including the 'FSN' field. Hereinafter, the embodiment in <figref idref="f0008">Fig. 8</figref> will describe a difference from that given in <figref idref="f0007">Fig. 7</figref>.

0066When compared to <figref idref="f0007">Fig. 7</figref>, the embodiment in <figref idref="f0008">Fig. 8</figref> uses the First Sequence Number (FSN), instead of the LSN, to notify an accurate sequence number of a PDCP SDU. This FSN corresponds to an SN of a target PDCP SDU indicated by the first bit of a bitmap. That is, the first bit of the bitmap has information about the reception status of the PDCP SDU indicated by the FSN.

0067In addition, similar to <figref idref="f0007">Fig. 7</figref>, when there is no need to notify the length of the bitmap, such as if the length of the bitmap is fixed or if the length of the bitmap can be derived from the length of the PDCP Control PDU, the LENGTH field is not required.

0068The method of setting the FSN and bitmap by using the FSN, instead of the LSN, has a little difference from that described in <figref idref="f0007">Fig. 7</figref>.

- FSN field:

0069A value of the FSN field indicates an SN of a PDCP SDU corresponding to the first bit of the bitmap field.

0070The value of the FSN field corresponds to the SN of a PDCP SDU which has not been firstly received, by the receiving side PDCP entity, among the PDCP SDUs received from the transmitting side PDCP entity.

- BITMAP

0071It includes reception status report (information) of the PDCP SDUs received from the transmitting side PDCP entity as a peer entity.

0072A range of the BITMAP indicates PDCP SDUs whose SNs are between [FSN, FSN + LENGTH*8 -1], and includes information about the reception success or failure.

0073In the BITMAP field having each reception status of the PDCP SDUs, target PDCP SDUs are those of which SNs are between 'FSN' and 'FSN + LENGTH*8 -1.' Each bit of the bitmaps has reception status information (i.e., PDCP Status Report) regarding whether or not the PDCP SDUs indicated by each bit have been successfully received. For instance, if a FSN value is '100' and a LENGTH value is '5,' a range of SN of the PDCP SDU as the target of the reception status report would be '100' ∼ '139.'

0074Each bit_position in the bitmap is 1 ∼ LENGTH*8, and for instance, if a LENGTH is '5,' the bit_position would be '1' ∼ '40.' That is, the number of the bits in the bitmap is 40. In other words, the number of PDCP SDUs which are the targets of the reception status reports (reception success or failure) of corresponding PDCP SDUs is 40.

0075An interpretation method of each bit_position is as follows: <ul id="ul0008" list-style="none" compact="compact"><li>◆ 1: reception success of a PDCP SDU which is PDCP Sequence Number = (FSN + bit_position -1).</li><li>◆ 0: reception failure of a PDCP SDU which is PDCP Sequence Number = (FSN + bit_position -1).</li></ul>

0076Meanwhile, if the LENGTH is '0,' the Bitmap field does not exist. In this case, the FSN only is included, considering that all PDCP SDUs have been successfully received.

0077The embodiments in <figref idref="f0007">Figs. 7</figref> and <figref idref="f0008">8</figref> have described the format of the PDCP Control PDU of the reception status information (i.e., the PDCP status report) for a series of data (i.e., PDCP SDUs) in which the receiving side PDCP entity receives from the transmitting side PDCP entity as a peer entity.

0078The method for transmitting the PDCP Control PDU of the reception status information (i.e., PDCP status report) for a series of data (i.e., PDCP SDUs) will be summarized as follows.

0079The receiving side PDCP entity obtains the PDCP SDUs by performing ciphering and header decompression on the PDCP PDUs received from the transmitting side PDCP entity, and then checks whether or not each of the PDCP SDUs has an error and thereby to determine the reception success or failure of each of the PDCP SDUs.

0080The receiving side PDCP entity adds each indicator (each bit of the bitmap) indicating the reception status (i.e., reception success or failure) of each PDCP SDU into the BITMAP field.

0081The receiving side PDCP entity configures the PDCP Control PDU including the BITMAP field and transmits the configured PDCP Control PDU to the transmitting side PDCP entity.

0082Meanwhile, the PDCP Control PDU may include the LENGTH field indicating the size of the BITMAP field.

0083In addition, the PDCP Control PDU may include LSN field or FSN field. Here, the LSN field has SN information of the PDCP SDU corresponding to the last bit of the BITMAP field. The FSN field has SN information of the PDCP SDU corresponding to the first bit (uppermost bit) of the BITMAP field. Thusly, the present invention uses the LSN and FSN fields, thereby not requiring to have SNs of a corresponding PDCP SDUs for all bit_positions of the BITMAP field, thus to reduce the size of the PDCP Control PDU as well as enhancing efficiency of resources.

0084Hereinafter, descriptions of a transmitter (transmitting apparatus) and a receiver (receiving apparatus) according to the present invention will be given.

0085The receiver (receiving apparatus) according to the present invention includes hardware, software, a module having software, and the like that can implement the embodiments of <figref idref="f0007">Figs. 7</figref> and <figref idref="f0008">8</figref>.

0086The apparatus according to the present invention may be called an entity, and the apparatus according to the present invention may be a terminal.

0087The receiver according to the present invention may include a communication module capable of performing functions described in <figref idref="f0007">Figs. 7</figref> and <figref idref="f0008">8</figref>.

0088That is, there is provided the communication module which determines the reception success or failure for each of in-sequence PDCP SDUs received through the PDCP layer, generates a status report for the determined result in the form of a bitmap, and transmits a PDCP Control PDU including the status report generated in the form of the bitmap.

0089The PDCP Control PDU includes the LSN field or FSN field. Here, the LSN field indicates a sequence number (SN) of a PDCP SDU corresponding to the last bit of the bitmap field, and the FSN field indicates a sequence number (SN) of a PDCP SDU corresponding to the first bit of the bitmap field.

0090The transmitter (transmitting apparatus) according to the present invention includes a communication module capable of performing functions described in <figref idref="f0007">Figs. 7</figref> and <figref idref="f0008">8</figref>. Here, functions of such communication module have already been described in <figref idref="f0007">Figs. 7</figref> and <figref idref="f0008">8</figref>, therefore detailed explanations therefor are omitted.

0091As described above, the receiver and transmitter according to the present invention basically include software, hardware required for implementing the technical idea of the present invention, in addition to the above-described elements, such as an output unit (display, speaker, or the like), an input unit (keypad, microphone, and the like), a memory, a microprocessor, a transmission/reception unit (RF module, antenna, and the like). Such elements are obvious to the person in the art, so description for them will be omitted.

0092The method described so far may be implemented by software, hardware or their combination thereof. For example, the method according to the present invention may be implemented by codes or command languages in a software program that can be stored in a storage medium (e.g., an internal memory of a mobile terminal, a flash memory, a hard disk, or the like), and that can be executed by a processor (e.g., an internal microprocessor of a mobile terminal).

0093It will also be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the scope of the invention. Thus, it is intended that the present invention cover modifications and variations of this invention provided they come within the scope of the appended claims.