Methods for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatuses thereof

0001The present invention relates to methods for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatuses thereof according to the pre-characterizing clauses of claims 1, 6, 11, and 14.

0002A long-term evolution (LTE) system, initiated by the third generation partnership project (3GPP), is now being regarded as a new radio interface and a radio network architecture that provides a high data rate, low latency, packet optimization, and improved system capacity and coverage. In the LTE system, an evolved universal terrestrial radio access network (E-UTRAN) includes a plurality of evolved Node-Bs (eNBs) and communicates with a plurality of mobile stations, also referred as user equipments (UEs).

0003If an RRC connection is disconnected due to radio link failure, an RRC re-establishment procedure needs to be initiated to re-establish the RRC connection. During the RRC re-establishment procedure, a UE resumes a signal radio bearer 1 (SRB1) and configures a lower layer to re-activate security (including integrity protection and ciphering) using the previously configured algorithm immediately when receiving an RRC Connection Re-establishment message from an E-UTRAN. To resume all radio bearers other than the SRB1, the E-UTRAN shall initiate an RRC Connection reconfiguration procedure after the RRC connection is re-established, wherein the RRC Connection reconfiguration procedure is to modify the RRC connection. However, it is not clearly specified how to resume SRBs and data radio bearers (DRBs) after the RRC Connection re-establishment procedure and the subsequent RRC connection reconfiguration in some scenarios. Hence, a mechanism for synchronizing PDCP operations after RRC connection re-establishment needs to be improved.

0004This in mind, the present invention aims at providing methods for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatuses to solve the abovementioned problems.

0005This is achieved by a method used in an E-UTRAN according to claim 1, a method used in a UE according to claim 6, an E-UTRAN according to claim 11, and a UE according to claim 14. The dependent claims pertain to corresponding further developments and improvements.

0006As will be seen more clearly from the detailed description following below, the claimed method used in an E-UTRAN for synchronizing PDCP operations after a RRC connection re-establishment procedure with a user equipment (UE) includes: initiating an RRC reconfiguration procedure to resume all radio bearers other than a signaling radio bearer 1 (SRB1) when an RRC connection is re-established, and re-transmitting a designated group of PDCP Service Data Units (SDUs) to the UE when a data radio bearer (DRB) mapped on Radio Link Control (RLC) Acknowledged Mode (AM) is resumed; the claimed method used in an UE for synchronizing PDCP operations after an RRC connection re-establishment procedure with an E-UTRAN includes: resuming all radio bearers other than an SRB1 when an RRC connection is re-established, and receiving a designated group of PDCP Service Data Units (SDUs) transmitted from the E-UTRAN when a data radio bearer (DRB) mapped on Radio Link Control (RLC) Acknowledged Mode (AM) is resumed; the claimed E-UTRAN for synchronizing PDCP operations after an RRC connection re-establishment procedure with a UE includes: means for initiating an RRC Reconfiguration procedure to resume all radio bearers other than a SRB1 when an RRC connection is re-established, and means for re--transmitting a designated group of PDCP SDUs to the UE when a DRB mapped on RLC AM is resumed; and the claimed UE for synchronizing PDCP operations after an RRC connection re-establishment procedure with an E-UTRAN includes: means for resuming all radio bearers other than an SRB1 when an RRC connection is re-established, and means for receiving a designated group of PDCP SDUs transmitted from the E-UTRAN when a DRB mapped on RLC AM is resumed.

0007In the following, the invention is further illustrated by way of example, taking reference to the accompanying drawings. Thereof <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG.1</figref> is a diagram showing the architecture of the radio interface protocol of an LTE system according to the prior art;</li><li><figref idref="f0002">FIG.2</figref> is a diagram showing an RRC re-establishment procedure of the LTE system according to the prior art;</li><li><figref idref="f0003">FIG.3</figref> is a block diagram showing a wireless communication system according to an embodiment of the present invention;</li><li><figref idref="f0004">FIG.4</figref> is a diagram illustrating PDCP SDUs received by a receiving PDCP entity;</li><li><figref idref="f0005">FIG.5</figref> is a flowchart illustrating a method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system according to an exemplary embodiment of the present invention;</li><li><figref idref="f0006">FIG.6</figref> is a flowchart illustrating a method for synchronizing PDCP operations after RRC Connection re-establishment in a wireless communication system according to another exemplary embodiment of the present invention;</li><li><figref idref="f0007">FIG.7</figref> is a flowchart illustrating a method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system according to another exemplary embodiment of the present invention;</li><li><figref idref="f0008">FIG.8</figref> is a flowchart illustrating a method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system according to another exemplary embodiment of the present invention;</li><li><figref idref="f0009">FIG.9</figref> is a flowchart illustrating a method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system according to another exemplary embodiment of the present invention;</li><li><figref idref="f0010">FIG.10</figref> is a flowchart illustrating a method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system according to another exemplary embodiment of the present invention; and</li><li><figref idref="f0011">FIG.11</figref> is a flowchart illustrating a method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system according to another exemplary embodiment of the present invention.</li></ul>

0008Please refer to <figref idref="f0001">FIG.1. FIG.1</figref> is a diagram showing the architecture of the radio interface protocol of a LTE system according to the prior art. As shown in <figref idref="f0001">FIG.1</figref>, the radio interface protocol of the LTE system includes three layers: the Physical Layer (L1), the Data Link Layer (L2), and the Network Layer (L3), wherein a control plane of L3 is a Radio Resource Control (RRC) layer, and L2 is further divided into a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer.

0009<figref idref="f0002">FIG.2</figref> is a diagram showing an RRC re-establishment procedure of the LTE system according to the prior art. As can be seen from <figref idref="f0002">FIG.2</figref>, if an RRC connection is disconnected due to radio link failure, an RRC re-establishment procedure needs to be initiated to re-establish the RRC connection. In the beginning, the UE 110 sends an RRC Connection Re-establishment request message to the E-UTRAN 120. Upon reception of the RRC Connection re-establishment request message, the E-UTRAN 120 responds by sending an RRC Connection Re-establishment message to the UE 110. When receiving the RRC Connection Re-establishment message, the UE resumes a signal radio bearer 1 (SRB1) and configures a lower layer to re-activate security (including integrity protection and ciphering) using the previously configured algorithm immediately. In other words, integrity protection and ciphering shall be applied to all subsequent messages received and sent by the UE 110. After that, the UE 110 sends an RRC Connection re-establishment complete message to notify the E-UTRAN 120 that the RRC connection is connected again. To resume all radio bearers other than the SRB1, the E-UTRAN 120 shall initiate an RRC Connection reconfiguration procedure after the RRC connection is re-established, wherein the RRC Connection reconfiguration procedure is to modify the RRC connection.

0010However, it is not clearly specified how to resume SRBs and data radio bearers (DRBs) after the RRC Connection re-establishment procedure and the subsequent RRC connection reconfiguration in some scenarios. For example, if the UE 110 is handed over from a first eNodeB to a second eNodeB, the compressor's context in a transmitting PDCP entity has been updated while the decompressor's context in a receiving PDCP entity has not been updated. Therefore, header decompressions in the receiving PDCP entity cannot decompress the PDCP SDUs correctly after resumption. Hence, a mechanism for synchronizing PDCP operations after RRC connection re-establishment needs to be improved.

0011Please refer to <figref idref="f0003">FIG.3. FIG.3</figref> is a block diagram showing a wireless communication system 300 according to an embodiment of the present invention. The wireless communication system 300 can be an LTE system, but this should not be a limitation of the present invention, and can be wireless communication systems of other types. The wireless communication system 300 includes, but is not limited to, a UE 310 and an E-UTRAN 350. The UTRAN E-350 includes a transmitting PDCP entity 360, and the UE 310 includes a receiving PDCP entity 320. Operations of the transmitting PDCP entity 360 and the receiving PDCP entity 320 will be detailed in the embodiments below.

0012Please note that In the following embodiments, <figref idref="f0004 f0005 f0006 f0007 f0008">FIG.4-FIG.8</figref> are examples for resumption of DRBs mapped on Radio Link Control Acknowledged Mode (RLC AM), <figref idref="f0009 f0010">FIG.9-FIG.10</figref> are examples for resumption of DRBs mapped on RLC UM, and <figref idref="f0011">FIG.11</figref> is an example for resumption of an SRB1 and an SRB2.

0013Please refer to <figref idref="f0004">FIG.4. FIG.4</figref> is a diagram illustrating PDCP SDUs received by the receiving PDCP entity 320 shown in <figref idref="f0003">FIG.3</figref>. As shown in <figref idref="f0004">FIG.4</figref>, five PDCP SDUs 410-450 are in-sequence transmitted by the transmitting PDCP entity 360. In this embodiment, the PDCP SDUs 410-450 are transmitted in RLC AM, thus the receiving PDCP entity 320 needs to send an RLC acknowledgement to confirm the reception of the PDCP SDUs. After a DRB mapped on RLC AM is resumed, the PDCP SDUs 420 and 450 are successfully received while the PDCP SDUs 410, 430, and 440 are not successfully received by the receiving PDCP entity 320 due to radio link failure. Actually, the PDCP SDU 410 is successfully received but has not been confirmed yet by a lower layer of the receiving PDCP entity 320. To recover the missing PDCP SDUs, three solutions are proposed below.

0014[Solution-1]: After the DRB mapped on RLC AM is resumed, the transmitting PDCP entity 360 retransmits all the PDCP SDUs 410-450 from the first PDCP SDU 410 of which a successful delivery of corresponding PDCP PDUs have not been confirmed by the lower layer. This solution can solve the PDCP SDU missing issue above, but wastes radio resource due to re-transmission.

0015[Solution-2]: After the DRB mapped on RLC AM is resumed, the transmitting PDCP entity 360 retransmits the PDCP SDUs of which the successful delivery of the corresponding PDCP PDUs has not been confirmed by the lower layer. In other words, the PDCP SDUs 410, 430, and 440 are re-transmitted. This solution can improve the method mentioned in the first solution, but still wastes radio resource due to re-transmission.

0016[Solution-3]: After the DRB mapped on RLC AM is resumed, the receiving PDCP entity 320 transmits a PDCP status report configured by RRC to the transmitting PDCP entity 360. After that, the transmitting PDCP entity 360 re-transmits the PDCP SDUs negatively acknowledged in the PDCP status report. In other words, the PDCP SDUs 430 and 440 are re-transmitted according to the PDCP status report. If an in-sequence delivery of upper layer PDUs is needed in the second solution and the third solution, the receiving PDCP entity 320 needs to decipher the received out-of sequence PDCP SDUs and reorder them. A timer is started for reordering the received PDCP SDUs when the DRB mapped on RLC AM is resumed. When the timer expires, the reordering is done and the received PDCP SDUs are delivered to an upper layer.

0017The abovementioned solutions 1-3 are shown in <figref idref="f0005">FIG.5</figref>, which is a flowchart illustrating a method for synchronizing PDCP operations after RRC Connection Re-establishment in a wireless communication system according to an exemplary embodiment of the present invention. The method includes the following steps: <ul id="ul0002" list-style="none" compact="compact"><li>Step 502: A DRB mapped on RLC AM is resumed.</li><li>Step 504: A designated group of PDCP SDUs are not successfully received due to radio link failure.</li><li>Step 510: Re-transmitting all the PDCP SDUs from the first PDCP SDU of which the successful delivery of the corresponding PDCP PDUs have not been confirmed by the lower layer.</li><li>Step 520: Re-transmitting the PDCP SDUs of which the successful delivery of the corresponding PDCP PDUs have not been confirmed by the lower layer.</li><li>Step 530: Transmitting a PDCP status report configured by RRC to the transmitting PDCP entity.</li><li>Step 532: Re-transmitting the PDCP SDUs negatively acknowledged in the PDCP status report.</li></ul>

0018For a DRB mapped on RLC AM, header decompression in the receiving PDCP entity 320 may not work after resumption. For example, five compressed PDCP SDUs are not transmitted successfully by the transmitting PDCP entity 360 due to radio link failure. The compressor's context in the transmitting PDCP entity 360 has been updated but the decompressor's context in the receiving PDCP entity 320 has not been updated. To solve this problem, two solutions are proposed as below.

0019[Solution-4]: After a DRB mapped on RLC AM is resumed, the header compression protocol is reset by the transmitting PDCP entity 360 and the de-compression protocol is reset by the receiving PDCP entity 320.

0020[Solution-5]: After a DRB mapped on RLC AM is resumed, header compression and decompression protocols are not reset. The receiving PDCP entity 320 does not perform a header decompression on the received out-of-sequence PDCP SDUs in a reordering buffer if the out-of-sequence PDCP SDUs are received due to RLC re-establishment. The UE 310 further includes a timer Discard_Timer associated with the received PDCP SDUs, wherein the timer Discard_Timer is started to reorder the received out-of-sequence PDCP SDUs in the reordering buffer to generate received in-sequence PDCP SDUs when a DRB mapped on RLC AM is resumed. When the timer Discard_Timer expires, the receiving PDCP entity 320 performs a header decompression on the received in-sequence PDCP SDUs in the reordering buffer and then delivers the PDCP SDUs to the upper layer after decompression.

0021The abovementioned solutions 4-5 are shown in <figref idref="f0006">FIG.6</figref>, which is a flowchart illustrating a method for synchronizing PDCP operations after RRC Connection Re-establishment in a wireless communication system according to another exemplary embodiment of the present invention. The method includes the following steps: <ul id="ul0003" list-style="none" compact="compact"><li>Step 602: A DRB mapped on RLC AM is resumed.</li><li>Step 604: Header decompression in the receiving PDCP entity cannot work after resumption.</li><li>Step 610: Reset the header compression and de-compression protocols.</li><li>Step 620: Start a timer Discard_Timer to reorder received PDCP SDUs to generate received in-sequence PDCP SDUs after a DRB mapped on RLC AM is resumed.</li><li>Step 622: When the timer expires, perform a header decompression on the received in-sequence PDCP SDUs.</li></ul>

0022A new base-key (KeNB) is always derived corresponding to the RRC Connection Re-establishment procedure. However, the lifetime of the new key is decreased due to waste of usable HFN and Sequence Number space if state variables of Next_PDCP_TX_SN. TX_HFN, Next_PDCP_RX_SN, and RX_HFN are not initiated to zero. The state variable Next_PDCP_TX_SN indicates the PDCP sequence number of the next PDCP SDU. The state variable TX_HFN indicates the HFN value for the generation of the COUNT value used for the PDCP PDUs. The state variable Next_PDCP_RX_SN indicates the next expected PDCP sequence number by the receiving PDCP entity. The state variable RX_HFN indicates the HFN value for the generation of the COUNT value used for the received PDCP PDUs. To avoid the inefficient key usage, one solution is proposed as below.

0023[Solution-6]: After a DRB mapped on RLC AM is resumed, the state variables of Next_PDCP_TX_SN and TX_HFN are reset to initial values by the transmitting PDCP entity 360. The state variables of Next_PDCP_RX_SN and RX_HFN are reset to initial values by the receiving PDCP entity 320.

0024The abovementioned solution 6 is shown in <figref idref="f0007">FIG.7</figref>, which includes the following steps: <ul id="ul0004" list-style="none" compact="compact"><li>Step 702: A DRB mapped on RLC AM is resumed.</li><li>Step 704: The lifetime of a new key KeNB is decreased due to waste of usable HFN and Sequence Number space.</li><li>Step 710: Reset the state variables of Next_PDCP_TX_SN, TX_HFN, Next_PDCP_RX_SN, and RX_HFN to initial values, respectively.</li></ul>

0025As mentioned above, a new base-key (KeNB) is always derived corresponding to the RRC Connection Re-establishment procedure. A new ciphering key is also generated from the new KeNB. However, it is not clear which ciphering key (old or new) is used to cipher and decipher the retransmitted PDCP PDUs proposed in the solutions 1-3. To solve this problem, one solution is proposed as below.

0026[Solution-7]: The retransmitted PDCP PDUs are ciphered with the new ciphering key derived by a new KeNB generated by the RRC Connection Re-establishment procedure.

0027The abovementioned solution 7 is shown in <figref idref="f0008">FIG.8</figref>, which includes the following steps: <ul id="ul0005" list-style="none" compact="compact"><li>Step 802: Perform an RRC Connection Re-establishment procedure.</li><li>Step 804: After a DRB mapped on RLC AM is resumed, re-transmit a designated group of PDCP SDUs being not successfully received.</li><li>Step 806: Generate a new KeNB corresponding to the RRC Connection Re-establishment procedure, and generate a new ciphering key from the new KeNS.</li><li>Step 810: Utilize the new ciphering key to cipher the re-transmitted PDCP PDUs.</li></ul>

0028For a DRB mapped on RLC UM, header decompression in the receiving PDCP entity 320 may not work after resumption. For example, five compressed PDCP SDUs are not transmitted successfully by the transmitting PDCP entity 360 due to radio link failure. The compressor's context in the transmitting PDCP entity 360 has been updated but the decompressor's context in the receiving PDCP entity 320 has not been updated. To solve this problem, one solution is proposed as below.

0029[Solution-8]: After a DRB mapped on RLC UM is resumed, the header compression protocol is reset by the transmitting PDCP entity 360 and the de-compression protocol is reset by the receiving PDCP entity 320.

0030The abovementioned solution 8 is shown in <figref idref="f0009">FIG.9</figref>, which includes the following steps: <ul id="ul0006" list-style="none" compact="compact"><li>Step 902: A DRB mapped on RLC UM is resumed.</li><li>Step 904: Header decompression in the receiving PDCP entity cannot work after resumption.</li><li>Step 910: Reset the header compression and de-compression protocols.</li></ul>

0031In this embodiment, a DRB mapped on RLC UM is resumed. As mentioned above, a new KeNB is always derived corresponding to the RRC Connection Re-establishment procedure. However, the lifetime of the new key is decreased due to waste of usable HFN and Sequence Number space if state variables of Next_PDCP_TX_SN, TX_HFN, Next_PDCP_RX_SN, and RX_HFN are not initiated to zero. To avoid the inefficient key usage, one solution is proposed as below.

0032[Solution-9]: After a DRB mapped on RLC UM is resumed, the state variables of Next_PDCP_TX_SN and TX_HFN are reset to initial values by the transmitting PDCP entity 360. The state variables of Next_PDCP_RX_SN and RX_HFN are reset to initial values by the receiving PDCP entity 320.

0033The abovementioned solution 9 is shown in <figref idref="f0010">FIG.10</figref>, which includes the following steps: <ul id="ul0007" list-style="none" compact="compact"><li>Step 1002: A DRB mapped on RLC UM is resumed.</li><li>Step 1004: The lifetime of a new key KeNB is decreased due to waste of usable HFN and Sequence Number space.</li><li>Step 1010: Reset the state variables of Next_PDCP_TX_SN, TX_HFN, Next_PDCP_RX_SN, and RX_HFN to initial values, respectively.</li></ul>

0034In this embodiment, SRB1 and SRB2 are resumed. As mentioned above, a new KeNB is always derived corresponding to the RRC Connection Re-establishment procedure. However, the lifetime of the new key is decreased due to waste of usable HFN and Sequence Number space if state variables of Next_PDCP_TX_SN. TX-HFN, Next_PDCP_RX_SN, and RX_HFN are not initiated to zero. To avoid the-inefficient key usage, one solution is proposed as below.

0035[Solution-10]: After an SRB1 and an SRB2 are resumed, the state variables of Next_PDCP_TX_SN and TX_HFN are reset to initial values by the transmitting PDCP entity 360. The state variables of Next_PDCP_RX_SN and RX_HFN are reset to initial values by the receiving PDCP entity 320.

0036The abovementioned solution 10 is shown in <figref idref="f0011">FIG.11</figref>, which includes the following steps: <ul id="ul0008" list-style="none" compact="compact"><li>Step 1102: SRB1 and SRB2 are resumed.</li><li>Step 1104: The lifetime of a new key KeNB is decreased due to waste of usable HFN and Sequence Number space.</li><li>Step 1110: Reset the state variables of Next_PDCP_TX_SN. TX_HFN, Next_PDCP_RX_SN, and RX_HFN to initial values.</li></ul>

0037The steps of the methods mentioned above are merely practicable embodiments of the present invention, and in no way should be considered to be limitations of the scope of the present invention. The methods can include other intermediate steps or several steps can be merged into a single step for suitable modifications without departing from the spirit of the present invention.

0038Of course, the abovementioned embodiments are merely examples for illustrating features of the present invention and should not be seen as limitations of the present invention. It will be obvious to those skilled in the art that various modifications on the mechanism for synchronizing PDCP operations after RRC Connection Re-establishment in a wireless communication system may be made without departing from the spirit of the present invention, and this should also belong to the scope of the present invention.

0039The abovementioned embodiments are presented merely for describing features of the present invention, and in no way should be considered to be limitations of the scope of the present invention. In summary, the present invention provides a method for synchronizing PDCP operations after RRC Connection Re-establishment in a wireless communication system and a related device. Through adopting the mechanism disclosed in the present invention, the abovementioned issues raised due to the RRC Connection Re-establishment can be solved. For example, the missing PDCP SDU issue in RLC AM can be solved by adopting the solutions 1-3; the header decompression fail issue can be solved by adopting the solutions 4-5 and 8; the inefficient key usage issue can be solved by adopting the solutions 6, 9, and 10; and the ciphering key issue can be solved by adopting the solution 7. Therefore, the PDCP operations between the UE and the E-UTRAN after RRC Connection Re-establishment can be synchronized to avoid the issues mentioned above.

0040All combinations and sub-combinations of the above-described features also belong to the invention.