CN115515180B - Method and device for updating NR RLC receiving window of AM mode - Google Patents
Method and device for updating NR RLC receiving window of AM mode Download PDFInfo
- Publication number
- CN115515180B CN115515180B CN202211042700.8A CN202211042700A CN115515180B CN 115515180 B CN115515180 B CN 115515180B CN 202211042700 A CN202211042700 A CN 202211042700A CN 115515180 B CN115515180 B CN 115515180B
- Authority
- CN
- China
- Prior art keywords
- rlc
- pdcp
- entity
- variable
- window
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 230000001360 synchronised effect Effects 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 13
- 238000012546 transfer Methods 0.000 claims description 11
- 230000005540 biological transmission Effects 0.000 claims description 7
- 239000002699 waste material Substances 0.000 abstract description 4
- 238000005516 engineering process Methods 0.000 description 5
- 238000010295 mobile communication Methods 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1832—Details of sliding window management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for updating an NR RLC receiving window of an AM mode. The first embodiment is: when the reordering timer is timed out, the PDCP entity of the receiving end of the AM mode sequentially sets a first variable, submits PDCP SDUs and updates RX_DELIV, and sets a second variable and a third variable. The PDCP entity delivers the second variable and the third variable to an associated RLC entity. The associated RLC entity sets a fourth variable. If the second variable is equal to the fourth variable, the RLC entity performs the following operations in order: (1) the RLC entity performs RLC window sliding. (2) If RX_Hight_status < RX_Next, the RLC entity updates RX_Hight_status to RX_Next. The invention solves the problem of air interface resource waste caused by asynchronous sliding of the PDCP receiving window and the RLC receiving window when the reordering timer is overtime.
Description
Technical Field
The present invention relates to the field of mobile communication technologies, and in particular, to a method for updating an RLC (Radio link control ) receiving window in a 5G NR (new radio) technology.
Background
At the receiving end of the mobile communication system, the PDU (Protocol Data Unit ) represents data transferred from the lower layer to the own layer. The SDU (Service Data Unit ) represents data that is delivered to an upper layer after the processing of the PDU of the present layer. For example, the data transferred from the MAC (Media Access Control, medium access control) layer to the upper RLC layer is a MAC SDU, also called RLC PDU; the RLC layer delivers data to the upper PDCP (Packet Data Convergence Protocol ) layer, which is called RLC SDU, also called PDCP PDU; the data delivered to the upper layer by the PDCP layer is PDCP SDUs. RLC PDUs have RLC sequence numbers (RLC SNs). PDCP PDUs are divided into two types-PDCP data PDU (PDCP Data PDU) and PDCP control PDU (PDCP Control PDU). PDCP data PDUs have PDCP sequence numbers (PDCP SNs), and PDCP control PDUs have no PDCP sequence numbers.
In the 5G mobile communication system, the RLC layer provides 3 different transmission modes, namely, a Transparent Mode (TM), a Unacknowledged Mode (UM), and an Acknowledged Mode (AM). The confirmation mode refers to: after the sending end sends the data, the sending end needs to wait for the acknowledgement information of the receiving end. After receiving the data, the receiving end needs to send confirmation information to the sending end to inform whether the data is received correctly. After receiving the acknowledgement information, if the acknowledgement information records that the receiving end fails to correctly receive the data, the sending end needs to resend the data indicating the failure of receiving in the acknowledgement information.
In the 5G NR technology, in order to reduce the link delay, the RLC entity (entity) of the receiving end of the AM mode receives the complete RLC PDU and then directly delivers the received PDU to the PDCP entity of the upper layer for decryption operation, so that the RLC entity does not guarantee the sequence of PDCP sequence numbers of the delivered PDCP PDU.
After receiving the out-of-order RLC PDU, the RLC entity at the receiving end of the AM mode starts a Reassembly timer (t-Reassembly). The reassembly timer represents the maximum waiting time interval for the RLC entity of the receiving end (user terminal) in AM mode to wait for the MAC layer downlink packet loss for HARQ (Hybrid automatic repeat request ) retransmission. If the reassembly timer times out, the RLC entity of the receiving end of the AM mode will notify the RLC entity of the transmitting end (base station) of the non-acknowledged sequence number (NACK SN) carried in the status report: the RLC PDU corresponding to the unacknowledged sequence number is not received, and the RLC entity at the transmitting end is requested to perform ARQ (automatic repeat request, automatic retransmission request) retransmission of the RLC PDU. The unacknowledged sequence number may be understood as the RLC sequence number of an RLC PDU that is not received. The RLC entity of the receiving end in AM mode will not slide the RLC receiving window until it receives RLC PDU retransmission at the left boundary of the RLC receiving window. The RLC reception window represents a range of RLC sequence numbers of the RLC PDU that is currently receivable. The left boundary of the RLC receiving window is updated and moved with the reception of RLC PDUs corresponding to the RLC sequence number, which is called a sliding window. If the RLC sequence number of the received RLC PDU is not within the current RLC reception window, it is referred to as an out-window.
After receiving the PDCP PDU delivered by the RLC entity, the PDCP entity at the receiving end in AM mode starts a Reordering timer (t-Reordering) if it finds that the condition rx_deliv < rx_next is satisfied, indicating that a loss of PDCP PDU occurs. RX_DELIV refers to a COUNT value (COUNT) of the first PDCP SDU not delivered to the upper layer, which represents the left boundary of the PDCP reception window. Rx_next refers to the count value of the NEXT PDCP SDU expected to be received. The count value is composed of two parts, HFN (hyper frame number) and PDCP sequence number. The reordering timer is used for the PDCP entity of the receiving end (user terminal) in AM mode to process the scenario of downlink received out-of-order PDCP PDUs, indicating the maximum waiting time of the downlink reordered PDCP PDUs. If the reordering timer is timed out, the PDCP entity at the receiving end of the AM mode cannot wait for the missing PDCP PDU within a specified time, and the out-of-order PDCP SDU before the rx_reord and the sequential PDCP SDU after the out-of-order PDCP SDU are delivered to the upper layer together, and the rx_deliv is updated. Rx_reference refers to the next count value of the count value of PDCP PDUs that trigger the reordering timer. The PDCP receive window represents a range of PDCP sequence numbers for currently receivable PDCP PDUs. The left edge of the PDCP receive window moves with the receipt of PDCP PDUs corresponding to the PDCP sequence number, referred to as a sliding window. If the PDCP sequence number of the received PDCP PDU is not in the current PDCP receiving window, the window is called an out window.
The RLC receive window and PDCP receive window are basically identical in concept and function, but differ in when to slide the window. According to the protocol, when the reordering timer is overtime, the PDCP receive window will slide and the RLC receive window will not slide. Asynchronous sliding of the two receive windows results in unnecessary retransmission of RLC PDUs by the downlink. Specifically, after receiving the RLC PDU in the RLC receiving window, the RLC entity at the receiving end in the AM mode processes the RLC PDU to form a PDCP PDU, and sends the PDCP PDU to the PDCP entity, where the PDCP PDU is discarded because it is not determined as a window packet in the PDCP receiving window, which causes waste of air interface resources.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a method for updating an RLC receiving window in an AM mode based on a 5G NR technology when a reordering timer is overtime. The method can overcome the problems caused by asynchronous sliding of the PDCP receiving window and the RLC receiving window.
In order to solve the technical problems, the invention discloses a method for updating an NR RLC receiving window of an AM mode, wherein one PDCP entity at a receiving end of the AM mode is only associated with one RLC entity; comprises the following steps. Step S1: when the reordering timer is overtime, the PDCP entity at the receiving end of the AM mode sequentially performs the following operations: (1) Setting a first variable RX_DELIV_last to record the RX_DELIV value updated last time, wherein RX_DELIV refers to the count value of the first PDCP SDU which is not delivered to the upper layer; (2) Delivering out-of-order PDCP SDUs before rx_reord and sequential PDCP SDUs after rx_reord to an upper layer, and updating rx_deliv to be greater than or equal to the count value of the first PDCP SDU that failed to be delivered to the upper layer; RX_REORD refers to the next count value of the count value of PDCP PDU triggering a reordering timer; (3) The second variable pdcprcvwnwgap is set to record the length of the discontinuous segment in the PDCP receive window, and the third variable pushwwdiff is also set to record the length of the left boundary of the PDCP receive window that this update slips. Step S21: the PDCP entity at the receiving end of the AM mode delivers the second variable pdcprcvwnwgap and the third variable pushwnwwdiff to the associated RLC entity. Step S31: one RLC entity associated with the PDCP entity in the receiving end of the AM mode sets a fourth variable rllcrecvwnwgap for recording the length of the discontinuous segment in the RLC reception window. Step S41: if the second variable pdcprcvwnwgap is equal to the fourth variable rlcnvwnwgap, one RLC entity associated with the PDCP entity in the receiving end of the AM mode sequentially performs the following operations: (1) the RLC entity performs RLC window sliding; (2) If RX_Highest_Status < RX_Next, the RLC entity updates RX_Highest_Status to RX_Next, otherwise does not update RX_Highest_Status; RX_Highest_status represents the ACK_SN value in the RLC Status report; the ack_sn indicates the RLC sequence number of the RLC SDU that is not received next and is not indicated to be missing in the RLC status report; RX_Next represents the Next RLC sequence number of the last fully received RLC SDU received by the RLC entity. If the second variable pdcprcvwnwgap is not equal to the fourth variable rlcnvwnwgap, one RLC entity associated with the PDCP entity in the receiving end of the AM mode does not update the RLC receiving window, and waits for the MAC layer HARQ to retransmit the RLC PDU by the RLC entity, or waits for the reassembly timer to timeout, and notifies the RLC entity of the transmitting end of the RLC PDU ARQ retransmission by the status report. This is the first embodiment of the method disclosed in the present invention.
Further, one PDCP entity of the receiving end of the AM mode is changed to associate two RLC entities; the steps S21 to S41 are changed to the steps S22 to S42. Step S22: the PDCP entity at the receiving end of the AM mode delivers the PDCP sequence number part in the first variable rx_deliv and the second variable pdcprcvwnwgap to the associated two RLC entities. Step S32: the two RLC entities pRLC, RLC associated with the PDCP entity in the receiving end of the AM mode respectively set a fourth variable pRlcRecvWnwGap, sRlcRecvWnwGap for recording the length of the discontinuous segment in the respective RLC reception window. Step S42: if the second variable is equal to the sum of the two fourth variables, and one RLC entity does not have the condition of out-of-order delivery PDCP PDU and the other RLC entity has the condition of out-of-order delivery PDCP PDU, the RLC entity having the out-of-order delivery PDCP PDU sequentially performs the following operations: (1) The RLC entity without the disorder delivery PDCP PDU does not do RLC window sliding, and the RLC entity with the disorder delivery PDCP PDU does RLC window sliding; (2) RLC entities having out-of-order delivery PDCP PDUs update rx_highest_status to rx_next if rx_highest_status < rx_next, otherwise not. If the second variable is equal to the sum of the two fourth variables and the two RLC entities have the condition of submitting PDCP PDUs out of order, the two RLC entities respectively and sequentially perform the following operations: (1) the two RLC entities both do RLC window sliding; (2) The RLC entity updates rx_highest Status to rx_next if rx_highest_status < rx_next of any RLC entity, otherwise not. If the second variable is not equal to the sum of the two fourth variables, the two RLC entities do not update their own RLC receiving windows, and the two RLC entities wait for the MAC layer HARQ to retransmit the RLC PDU, or wait for the reassembly timer to timeout and then notify the RLC entity of the transmitting end of the RLC PDU ARQ retransmission through the status report. This is embodiment two of the method disclosed herein.
Further, in the step S1, the value of the first variable rx_deliv_last is rx_deliv before update; the second variable pdcprcvwnwgap has a value of rx_next-rx_deliv_last; RX_NEXT refers to the count value of the NEXT PDCP SDU expected to be received; the third variable PushWnwDiff takes the value of RX_DELIV-RX_DELIV_last after update.
Further, in the step S31 and the step S32, the value of the fourth variable is the difference between the RLC sequence number +1 of the RLC SDU which is one nearest complete received before the rlc_next_high and the RLC receiving window left boundary rx_next; RX_Next_Hight represents the Next RLC sequence number of the largest RLC sequence number of the RLC PDUs received in the current RLC reception window.
Further, in the step S41, the RLC entity performing RLC window sliding means: the RLC entity updates the RLC receive window left boundary by the offset sliding to the right by the third variable pushwnwwdiff and updates rx_next to rx_next+pushwnwwdiff.
Further, in the step S42, the RLC entity having the out-of-order delivery PDCP PDU performs RLC window sliding means: the RLC entity calculates the PDCP sequence number of the PDCP PDU corresponding to the RLC sequence number of each RLC PDU of the current RLC reception window, finds out the RLC SDU corresponding to the PDCP sequence number part-1 "of rx_deliv, and updates rx_next to the RLC sequence number corresponding to the RLC SDU following the found RLC SDU, i.e. to RLC sequence number +1 of the found RLC SDU.
Further, in the step S42, the performing RLC window sliding by the two RLC entities means: the two RLC entities respectively calculate PDCP sequence numbers of PDCP PDUs corresponding to RLC sequence numbers of each RLC PDU of the two RLC receiving windows, respectively find out the RLC SDU closest to PDCP sequence number part-1 "of" rx_deliv "in the two RLC receiving windows, and respectively update rx_next of the two RLC entities to RLC sequence numbers corresponding to the found two RLC SDUs.
The invention also discloses a device for updating the NR RLC receiving window of the AM mode, wherein one PDCP entity at the receiving end of the AM mode is only associated with one RLC entity; the device comprises a timeout processing unit, a first transfer unit, a first RLC calculation unit and a first synchronous sliding window unit. The timeout processing unit is configured to, when the reordering timer is timed out, cause the PDCP entity of the receiving end of the AM mode to sequentially perform the following operations: (1) Setting a first variable RX_DELIV_last to record the RX_DELIV value updated last time, wherein RX_DELIV refers to the count value of the first PDCP SDU which is not delivered to the upper layer; (2) Delivering the out-of-order PDCP SDUs before RX_REORD and the sequential PDCP SDUs after RX_REORD to an upper layer, and updating RX_DELIV to be equal to or more than the count value of the PDCP SDU which is not delivered to the upper layer by the first one of RX_REORD; RX_REORD refers to the next count value of the count value of PDCP PDU triggering a reordering timer; (3) The second variable pdcprcvwnwgap is set to record the length of the discontinuous segment in the PDCP receive window, and the third variable pushwwdiff is also set to record the length of the left boundary of the PDCP receive window that this update slips. The first delivery unit is configured to cause a PDCP entity at a receiving end of the AM mode to deliver a second variable pdcprcvwnwgap and a third variable pushwnwwdiff to an associated RLC entity. The first RLC computing unit is configured to enable one RLC entity associated with the PDCP entity in the receiving end of the AM mode to set a fourth variable rllcrecvwnwgap for recording a length of a discontinuous segment in an RLC receiving window. The first synchronous sliding window unit is configured to, when the second variable pdcprcvwnwgap is equal to the fourth variable rllcrecvwnwgap, cause one RLC entity associated with the PDCP entity in the receiving end of the AM mode to sequentially perform the following operations: (1) the RLC entity performs RLC window sliding; (2) If RX_Highest_Status < RX_Next, the RLC entity updates RX_Highest_Status to RX_Next, otherwise does not update RX_Highest_Status; RX_Highest_status represents the ACK_SN value in the RLC Status report, ACK_SN indicating the RLC sequence number of the RLC SDU that is not received next and that is not indicated to be lost in the RLC Status report; RX_Next represents the Next RLC sequence number of the last fully received RLC SDU received by the RLC entity. The first synchronization sliding window unit is further configured to, when the second variable pdcprcvwnwgap is not equal to the fourth variable rllcrecvwnwgap, make one RLC entity associated with the PDCP entity in the receiving end of the AM mode not update the RLC receiving window, wait for the MAC layer HARQ to retransmit the RLC PDU by the RLC entity, or wait for the reassembly timer to timeout and notify the RLC entity of the transmitting end of the RLC PDU through a status report. This is the first embodiment of the device disclosed in the present invention.
Further, one PDCP entity of the receiving end of the AM mode is changed to associate two RLC entities; the first transmission unit, the first RLC calculation unit and the first synchronous sliding window unit are respectively changed into a second transmission unit, a second RLC calculation unit and a second synchronous sliding window unit. The second transfer unit is configured to cause the PDCP entity at the receiving end of the AM mode to transfer the PDCP sequence number portion in the first variable rx_deliv and the second variable pdcprcvwnwgap to the associated two RLC entities. The second RLC calculating unit is configured to enable two RLC entities pRLC and RLC associated with the PDCP entity in the receiving end of the AM mode to set fourth variables pRlcRecvWnwGap, sRlcRecvWnwGap respectively for recording lengths of discontinuous segments in respective RLC receiving windows. The second synchronous sliding window unit is used for the situation that when the second variable is equal to the sum of the two fourth variables and one RLC entity does not have the out-of-order delivery PDCP PDU; when another RLC entity has the condition of submitting PDCP PDUs out of order, the RLC entity having PDCP PDUs submitted out of order sequentially performs the following operations: (1) The RLC entity without the disorder delivery PDCP PDU does not do RLC window sliding, and the RLC entity with the disorder delivery PDCP PDU does RLC window sliding; (2) RLC entities having out-of-order delivery PDCP PDUs update rx_highest_status to rx_next if rx_highest_status < rx_next, otherwise not. The second synchronous sliding window unit is further configured to, when the second variable is equal to a sum of two fourth variables and there is an out-of-order delivery of PDCP PDUs by two RLC entities associated with the PDCP entity in the receiving end of the AM mode, cause the two RLC entities to sequentially perform the following operations: (1) the two RLC entities both do RLC window sliding; (2) The RLC entity updates rx_highest Status to rx_next if rx_highest_status < rx_next of any RLC entity, otherwise not. The second synchronous sliding window unit is further configured to, when the second variable is not equal to the sum of the two fourth variables, make both RLC entities associated with the PDCP entity in the receiving end of the AM mode not update their respective RLC receiving windows, wait for the MAC layer HARQ to retransmit the RLC PDU by the two RLC entities, or notify the RLC entity of the transmitting end of the RLC PDU through a status report after the reassembly timer is timed out. This is the second embodiment of the device disclosed in the present invention.
The invention has the technical effects that: the problem of empty resource waste caused by asynchronous sliding of the PDCP receiving window and the RLC receiving window when the reordering timer is overtime is solved.
Drawings
Fig. 1 is a flowchart illustrating an embodiment one of a method for updating an AM mode NR RLC reception window according to the present invention.
Fig. 2 is a flowchart illustrating a second embodiment of a method for updating an AM mode NR RLC reception window according to the present invention.
Fig. 3 is a schematic structural diagram of an embodiment one of an apparatus for updating an AM mode NR RLC reception window according to the present invention.
Fig. 4 is a schematic structural diagram of a second embodiment of an apparatus for updating an AM mode NR RLC reception window according to the present invention.
The reference numerals in the drawings illustrate: 1 is a timeout processing unit, 21 is a first transfer unit, 22 is a second transfer unit, 31 is a first RLC computing unit, 32 is a second RLC computing unit, 41 is a first synchronous sliding window unit, and 42 is a second synchronous sliding window unit.
Detailed Description
Referring to fig. 1, a method for updating an AM mode NR RLC reception window according to the present invention is shown. An embodiment one is that one PDCP entity is associated with only one RLC entity, which is one scenario where 5G NR technology is most common at present. The association refers to a mapping corresponding relation between the PDCP entity and the RLC entity, and a data transmission channel is constructed. An embodiment one includes the following steps. Wherein, the receiving end refers to the user terminal, and the transmitting end refers to the base station. Or, the receiving end refers to a base station, and the transmitting end refers to a user terminal.
Step S1: when the reordering timer is timed out, the PDCP entity of the receiving end of the AM mode sequentially performs the following operations. (1) The PDCP entity at the receiving end of the AM mode sets a first variable rx_deliv_last for recording the last updated rx_deliv value, where the value of the first variable is the current rx_deliv. RX_DELIV refers to the count value of the first PDCP SDU not delivered to the upper layer. (2) The PDCP entity of the receiving end of the AM mode submits the out-of-order PDCP SDUs before the RX_REORD and the sequential PDCP SDUs after the RX_REORD to the upper layer according to the protocol requirement, and updates RX_DELIV to be greater than or equal to the count value of the PDCP SDU which is not submitted to the upper layer by the first one of the RX_REORDs. Rx_reference refers to the next count value of the count value of PDCP PDUs that trigger the reordering timer. (3) The PDCP entity at the receiving end of the AM mode sets a second variable pdcprcvwnwgap for recording the length of the discontinuous segment in the PDCP receiving window, where the second variable has a value of rx_next-rx_deliv_last. Rx_next refers to the count value of the NEXT PDCP SDU expected to be received. The PDCP entity sets a third variable PushWnwDiff for recording the length of the update slip of the left boundary of the PDCP receive window, where the third variable has a value of rx_deliv-rx_deliv_last. Wherein the first variable RX_DELIV_last, the second variable PdcpRecvWnwGap and the third variable PushWnwDiff are added in the invention. It is noted in particular that in part (2) operation, the RX_DELIV value is updated. Then the rx_deliv referred to in part (1) is the value before the update and the rx_deliv referred to in part (3) is the value after the update.
Step S21: the PDCP entity at the receiving end of the AM mode delivers the second variable pdcprcvwnwgap and the third variable pushwnwwdiff to the associated RLC entity.
Step S31: and setting a fourth variable RlcRecWnwGap for recording the length of a discontinuous section in an RLC receiving window by one RLC entity associated with the PDCP entity in the receiving end of the AM mode, wherein the value of the fourth variable is the difference value between the RLC sequence number +1 of the latest completely received RLC SDU before the RX_Next_Hight and the RLC receiving window left boundary RX_Next'. RX_Next_Hight represents the Next RLC sequence number of the largest RLC sequence number of the RLC PDUs received in the current RLC reception window. RX_Next represents the value of the Next RLC sequence number of the last fully received RLC SDU received by the RLC entity. It is to be noted in particular that rx_next (full uppercase) is a different variable with different meaning than rx_next (uppercase mix). Rx_next (full capital letter) is a variable of the PDCP layer defined by the international standard protocol. RX_Next (case-letter mixture) is a variable of the RLC layer defined by the International Standard protocol. The fourth variable, rlcRecWnwgap, is a novel addition of the present invention.
Step S41: if the second variable pdcprcvwnwgap is equal to the fourth variable rlcnvwnwgap, indicating that both PDCP PDUs received and PDCP PDUs not yet received in the current PDCP reception window are PDCP data PDUs, and the RLC sequence number of the RLC PDU in the current RLC reception window and the PDCP sequence number of the PDCP PDU in the current PDCP reception window are in one-to-one correspondence, one RLC entity associated with the PDCP entity in the receiving end of the AM mode sequentially performs the following operations. The RLC entity of the receiving end delivers the PDCP PDU obtained after processing the RLC PDU to the upper layer PDCP entity. The RLC PDU has an RLC sequence number. The PDCP PDU has a PDCP sequence number. Since the PDCP PDU can trace to find the corresponding RLC PDU, the corresponding relation exists between the PDCP sequence number of the PDCP PDU and the RLC sequence number of the corresponding RLC PDU. (1) the RLC entity performs RLC window sliding. Specifically, the RLC entity updates the RLC receive window left boundary by the offset sliding to the right by the third variable pushwnwwdiff and updates rx_next to rx_next+pushwndiff. (2) At this time, if RX_Hight_status < RX_Next, the RLC entity updates RX_Hight_status to RX_Next, otherwise, does not update RX_Hight_status. RX_Highest_status represents the ACK_SN value in the RLC Status report. The ack_sn indicates the RLC sequence number of the RLC SDU that is not received next and is not indicated to be missing in the RLC status report. The variable RX_Next_status_trigger and the reassembly timer operate according to the protocol. RX_Next_status_trigger represents the Next RLC sequence number of the RLC PDU that triggered the reassembly timer. It is noted that in part (1) operation, the value of RX_Next is updated. Then rx_next referred to in part (2) is the value after the update.
If the second variable pdcprcvwnwgap is not equal to the fourth variable rlcnvwnwgap, it indicates that the PDCP PDU obtained after the RLC entity processes in the current RLC receiving window may include a PDCP control PDU, or the PDCP PDU is discarded due to network congestion when the sender sends a PDCP data PDU, where one RLC entity associated with the PDCP entity in the receiving end in AM mode does not update the RLC receiving window, and the RLC entity waits for the MAC layer HARQ to retransmit the RLC PDU, or waits for a reassembly timer to timeout and notifies the RLC entity of the sender of ARQ retransmission of the RLC PDU through a status report.
Referring to fig. 2, a second embodiment of a method for updating an AM mode NR RLC reception window according to the present invention is shown. The second embodiment is that one PDCP entity associates two RLC entities, and the PDCP entity is configured as a split bearer (split bearer), for example, a DC (Dual-connectivity) scenario. The second embodiment is complex due to RLC reception window updates involving two RLC entities. For convenience of description, two RLC entities associated with the PDCP entity in the receiving end of the AM mode are referred to as pRLC and RLC, respectively, and both RLC entities randomly receive RLC PDUs in the present invention. The second embodiment comprises the following steps.
Step S1: the same as in step S1 of the first embodiment.
Step S22: the first variable RX_DELIV_last is used to record the last updated RX_DELIV value. RX_DELIV refers to the count value of the first PDCP SDU not delivered to the upper layer. The count value consists of two parts, namely HFN and PDCP serial numbers. The PDCP entity at the receiving end of the AM mode delivers the PDCP sequence number part in the first variable rx_deliv and the second variable pdcprcvwnwgap to the associated two RLC entities.
Step S32: the two RLC entities pRLC and RLC associated with the PDCP entity in the receiving end in AM mode respectively set a fourth variable pRlcRecvWnwGap, sRlcRecvWnwGap for recording the length of the discontinuous segment in each RLC receiving window, where the values are the difference between the RLC sequence number +1 of the RLC SDU that is one nearest complete received before the rx_next_high of the RLC entity and the left boundary rx_next of the RLC receiving window. RX_Next_Hight represents the Next RLC sequence number of the largest RLC sequence number of the RLC PDUs received in the current RLC reception window. The fourth variables pRlcRecvWnwGap and sRlcRecvWnwGap are novel.
Step S42: if the second variable is equal to the sum of two fourth variables, namely pdcprcvwnwgap=prlcrecvwnwgap+srlcrecvwnwgap, it indicates that both PDCP PDUs received and PDCP PDUs not received in the current PDCP receiving window are PDCP data PDUs, and the PDCP sequence number of the PDCP PDU in the current PDCP receiving window corresponds to the RLC sequence number of the RLC PDU after combining the two RLC receiving windows in a one-to-one correspondence. The RLC entity of the receiving end delivers the RLC PDU (also called RLC SDU) obtained after processing the RLC PDU to the upper layer PDCP entity. The RLC PDU has an RLC sequence number. The PDCP PDU has a PDCP sequence number. Since the PDCP PDU can trace to find the corresponding RLC PDU, the corresponding relation exists between the PDCP sequence number of the PDCP PDU and the RLC sequence number of the corresponding RLC PDU. This time division is divided into the following two cases.
Case one: if there is an RLC entity with rx_next_high=rx_next in two RLC entities associated with the PDCP entity in the receiving end of the AM mode, indicating that the RLC entity does not have a condition of submitting PDCP PDUs out of order; RX_Next_Highest. Noteq. RX_Next of another RLC entity, it indicates that there is an out-of-order delivery of PDCP PDUs by the RLC entity. Assuming that there is an out-of-order delivery PDCP PDU, the pRLC entity performs the following operations in order. (1) RLC window sliding is not required for the RLC entity, but only for the pRLC entity. Specifically, the pRLC entity calculates the PDCP sequence number of the PDCP PDU corresponding to the RLC sequence number of each RLC PDU of the current RLC reception window, finds the RLC SDU corresponding to the PDCP sequence number part-1 of rx_deliv, and updates rx_next to the RLC sequence number corresponding to the RLC SDU following the found RLC SDU (i.e., to RLC sequence number +1 of the found RLC SDU). (2) If RX_Highest_Status < RX_Next, then RX_Highest_Status is updated to RX_Next, otherwise, it is not updated. And the other variables RX_Next_status_trigger and the reassembly timer are operated according to the protocol. It is noted that in part (1) operation, the value of RX_Next is updated. Then rx_next referred to in part (2) is the value after the update.
And a second case: if two RLC entities associated with the PDCP entity in the receiving end of the AM mode both satisfy rx_next_high+.rx_next, it indicates that there is an out-of-order PDCP PDU condition for both RLC entities. At this time, two RLC entities associated with the PDCP entity in the receiving end of the AM mode sequentially perform the following operations, respectively. (1) RLC window sliding is performed by both RLC entities. Specifically, the two RLC entities respectively calculate PDCP sequence numbers of PDCP PDUs corresponding to RLC sequence numbers of each RLC PDU of the two RLC reception windows, respectively find out the RLC SDU closest to (including PDCP sequence number part-1 equal to) "rx_deliv" in the pRLC reception window and the RLC reception window, and respectively update rx_next of the two RLC entities to the found RLC sequence numbers corresponding to the two RLC SDUs. (2) The RLC entity updates rx_highest Status to rx_next if rx_highest_status < rx_next of any RLC entity, otherwise not. And the other variables RX_Next_status_trigger and the reassembly timer are operated according to the protocol. It is noted that in part (1) operation, the value of RX_Next is updated. Then rx_next referred to in part (2) is the value after the update.
If the second variable is not equal to the sum of the two fourth variables, namely, pdcprcvwwgap is not equal to prlcrecvwwgap+srlcrecvwwgap, it indicates that RLC PDUs in two RLC receiving windows associated with the PDCP entity in the receiving end of the current AM mode may include PDCP control PDUs when the PDCP entity processes the PDCP PDUs, or the sending end discards PDCP data PDUs due to network congestion or other reasons when sending the PDCP data PDUs, at this time, neither RLC entity updates its RLC receiving window, and the two RLC entities wait for MAC layer HARQ retransmission of RLC PDUs, or wait for a reassembly timer to timeout and notify the RLC entity of the sending end of ARQ retransmission of RLC PDUs through a status report.
The invention considers that under the situation that the air interface condition is poor, the RLC uplink state report and the downlink retransmission data packet may fail in the air interface transmission, so that the reordering timer of the PDCP layer is overtime and the PDCP receiving window is unilaterally slid. Compared with the prior art, the invention can synchronously slide the RLC receiving window according to the sliding condition of the PDCP receiving window when the reordering timer is overtime, which is the core technical innovation of the invention.
Referring to fig. 3, this is an embodiment one of an apparatus for updating an AM mode NR RLC reception window according to the present invention, which corresponds to the embodiment one of the method shown in fig. 1. An embodiment of the device comprises a timeout processing unit 1, a first transfer unit 21, a first RLC computing unit 31, a first synchronization window unit 41.
The timeout processing unit 1 is configured to, when the reordering timer is timed out, cause the PDCP entity of the receiving end of the AM mode to sequentially perform the following operations: (1) The first variable RX_DELIV_last is set to record the last updated RX_DELIV value, which refers to the count value of the first PDCP SDU not delivered to the upper layer. (2) The out-of-order PDCP SDUs before rx_reord and the sequential PDCP SDUs after rx_reord are delivered to the upper layer according to protocol requirements, and rx_deliv is updated to be greater than or equal to the count value of the PDCP SDU that the first one of rx_reord fails to deliver to the upper layer. Rx_reference refers to the next count value of the count value of PDCP PDUs that trigger the reordering timer. (3) The second variable pdcprcvwnwgap is set to record the length of the discontinuous segment in the PDCP receive window, and the third variable pushwwdiff is also set to record the length of the left boundary of the PDCP receive window that this update slips.
The first delivery unit 21 is configured to cause the PDCP entity at the receiving end of the AM mode to deliver the second variable pdcprcvwnwgap and the third variable pushwnwwdiff to the associated RLC entity.
The first RLC calculating unit 31 is configured to enable one RLC entity associated with the PDCP entity in the receiving end of the AM mode to set a fourth variable rllcrecvwnwgap for recording the length of the discontinuous segment in the RLC receiving window.
The first synchronization window unit 41 is configured to, when the second variable pdcprcvwnwgap is equal to the fourth variable rllcrecvwnwgap, cause one RLC entity associated with the PDCP entity in the receiving end of the AM mode to sequentially perform the following operations. (1) the RLC entity performs RLC window sliding. (2) At this time, if RX_Hight_status < RX_Next, the RLC entity updates RX_Hight_status to RX_Next, otherwise, does not update RX_Hight_status. RX_Highest_status represents the ACK_SN value in the RLC Status report. The ack_sn indicates the RLC sequence number of the RLC SDU that is not received next and is not indicated to be missing in the RLC status report.
The first synchronization window unit 41 is further configured to, when the second variable pdcprcvwnwgap is not equal to the fourth variable rllcrecvwnwgap, make one RLC entity associated with the PDCP entity in the receiving end of the AM mode not update the RLC receiving window, wait for the MAC layer HARQ to retransmit the RLC PDU by the RLC entity, or wait for the reassembly timer to timeout and notify the RLC entity of the transmitting end of the RLC PDU through the status report.
Referring to fig. 4, this is a second embodiment of the apparatus for updating an AM mode NR RLC reception window according to the present invention, which corresponds to the second embodiment of the method shown in fig. 2. The embodiment of the device comprises a timeout processing unit 1, a second transfer unit 22, a second RLC computing unit 32, a second synchronization window unit 42.
The timeout processing unit 1 is the same as the timeout processing unit 1 in the first embodiment.
The second delivery unit 22 is configured to cause the PDCP entity at the receiving end of the AM mode to deliver the PDCP sequence number part in the first variable rx_deliv and the second variable pdcprcvwnwgap to the associated two RLC entities.
The second RLC calculating unit 32 is configured to cause two RLC entities pRLC and RLC associated with the PDCP entity in the receiving end of the AM mode to set fourth variables pRlcRecvWnwGap, sRlcRecvWnwGap for recording lengths of discontinuous segments in respective RLC receiving windows, respectively.
The second synchronous sliding window unit 42 is configured to, when the second variable is equal to the sum of the two fourth variables and there is no out-of-order PDCP PDU submitted by one RLC entity among the two RLC entities associated with the PDCP entity in the receiving end of the AM mode; when another RLC entity has the condition of submitting PDCP PDUs out of order, the RLC entity having PDCP PDUs submitted out of order sequentially performs the following operations. (1) performing RLC window sliding for the RLC entity. (2) If RX_Hight_Status < RX_Next of the RLC entity, updating RX_Hight_Status to RX_Next, otherwise not updating.
The second synchronization sliding window unit 42 is further configured to, when the second variable is equal to the sum of the two fourth variables and there is an out-of-order delivery of PDCP PDUs by two RLC entities associated with the PDCP entity in the receiving end of the AM mode, cause the two RLC entities to perform the following operations in sequence, respectively. (1) RLC window sliding is performed by both RLC entities. (2) The RLC entity updates rx_highest Status to rx_next if rx_highest_status < rx_next of any RLC entity, otherwise not.
The second synchronization sliding window unit 42 is further configured to, when the second variable is not equal to the sum of the two fourth variables, make neither of the two RLC entities associated with the PDCP entity in the receiving end of the AM mode update their respective RLC receiving windows, wait for the MAC layer HARQ to retransmit the RLC PDU by the two RLC entities, or notify the RLC entity of the sending end of the RLC PDU ARQ retransmission by the status report after the reassembly timer expires.
Compared with the prior art, the method solves the problem of air interface resource waste caused by asynchronous sliding of the PDCP receiving window and the RLC receiving window when the reordering timer is overtime, shortens the service recovery time and improves the user experience.
The above are only preferred embodiments of the present invention, and are not intended to limit the present invention. Various modifications and variations of the present invention will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A method of updating an AM mode NR RLC reception window, wherein one PDCP entity at a receiving end of the AM mode is associated with only one RLC entity; comprises the following steps of;
Step S1: when the reordering timer is overtime, the PDCP entity at the receiving end of the AM mode sequentially performs the following operations: (1) Setting a first variable RX_DELIV_last to record the RX_DELIV value updated last time, wherein RX_DELIV refers to the count value of the first PDCP SDU which is not delivered to the upper layer; (2) Delivering out-of-order PDCP SDUs before rx_reord and sequential PDCP SDUs after rx_reord to an upper layer, and updating rx_deliv to be greater than or equal to the count value of the first PDCP SDU that failed to be delivered to the upper layer; RX_REORD refers to the next count value of the count value of PDCP PDU triggering a reordering timer; (3) Setting a second variable PdcpRecvWnwgap for recording the length of a discontinuous section in the PDCP receiving window, and setting a third variable PushWnwDiff for recording the length of the left boundary of the PDCP receiving window updated and slid at the time;
step S21: the PDCP entity of the receiving end of the AM mode transmits the second variable PdcpRecvWnwgap and the third variable PushWnwDiff to the associated RLC entity;
step S31: setting a fourth variable RlcRecvWnwgap by one RLC entity associated with the PDCP entity in the receiving end of the AM mode for recording the length of a discontinuous section in an RLC receiving window;
step S41: if the second variable pdcprcvwnwgap is equal to the fourth variable rlcnvwnwgap, one RLC entity associated with the PDCP entity in the receiving end of the AM mode sequentially performs the following operations: (1) the RLC entity performs RLC window sliding, namely: the RLC entity updates the left boundary of the RLC receiving window, the offset sliding to the right is a third variable PushWnwDiff, and RX_Next is updated to RX_Next+PushWnwDiff; (2) If RX_Highest_Status < RX_Next, the RLC entity updates RX_Highest_Status to RX_Next, otherwise does not update RX_Highest_Status; RX_Highest_status represents the ACK_SN value in the RLC Status report; the ack_sn indicates the RLC sequence number of the RLC SDU that is not received next and is not indicated to be missing in the RLC status report; RX_Next represents the Next RLC sequence number of the last completely received RLC SDU received by the RLC entity;
If the second variable pdcprcvwnwgap is not equal to the fourth variable rlcnvwnwgap, one RLC entity associated with the PDCP entity in the receiving end of the AM mode does not update the RLC receiving window, and waits for the MAC layer HARQ to retransmit the RLC PDU by the RLC entity, or waits for the reassembly timer to timeout, and notifies the RLC entity of the transmitting end of the RLC PDU ARQ retransmission by the status report.
2. The method for updating an AM mode NR RLC reception window according to claim 1, wherein one PDCP entity at the receiving end of the AM mode is changed to associate two RLC entities; the steps S21 to S41 are changed to the steps S22 to S42;
step S22: the PDCP entity of the receiving end of the AM mode transmits the PDCP sequence number part in the first variable RX_DELIV and the second variable PdcpRecvWnwgap to the two associated RLC entities;
step S32: the receiving end of the AM mode sets a fourth variable pRlcRecvWnwGap, sRlcRecvWnwGap for recording the length of discontinuous sections in each RLC receiving window respectively by two RLC entities pRLC and sRLC associated with the PDCP entity;
step S42: if the second variable is equal to the sum of the two fourth variables, and one RLC entity does not have the condition of out-of-order delivery PDCP PDU and the other RLC entity has the condition of out-of-order delivery PDCP PDU, the RLC entity having the out-of-order delivery PDCP PDU sequentially performs the following operations: (1) The RLC entity without the disorder delivery PDCP PDU does not do RLC window sliding, and the RLC entity with the disorder delivery PDCP PDU does RLC window sliding; (2) The RLC entity with the out-of-order delivery PDCP PDU updates RX_Hight_Status to RX_Next if RX_Hight_Status is less than RX_Next, otherwise, does not update;
If the second variable is equal to the sum of the two fourth variables and the two RLC entities have the condition of submitting PDCP PDUs out of order, the two RLC entities respectively and sequentially perform the following operations: (1) the two RLC entities both do RLC window sliding; (2) If RX_Hight_Status < RX_Next of any RLC entity, the RLC entity updates RX_Hight_Status to RX_Next, otherwise not;
if the second variable is not equal to the sum of the two fourth variables, the two RLC entities do not update their own RLC receiving windows, and the two RLC entities wait for the MAC layer HARQ to retransmit the RLC PDU, or wait for the reassembly timer to timeout and then notify the RLC entity of the transmitting end of the RLC PDU ARQ retransmission through the status report.
3. Method for updating an AM mode NR RLC reception window according to claim 1 or 2, wherein in step S1 the value of the first variable rx_deliv_last is rx_deliv before update; the second variable pdcprcvwnwgap has a value of rx_next-rx_deliv_last; RX_NEXT refers to the count value of the NEXT PDCP SDU expected to be received; the third variable PushWnwDiff takes the value of RX_DELIV-RX_DELIV_last after update.
4. The method for updating the NR RLC reception window of AM mode according to claim 1 or 2, wherein in step S31 and step S32, the value of the fourth variable is the difference between RLC sequence number +1 of the RLC SDU immediately preceding the rlc_next_high and the RLC reception window left boundary rx_next; RX_Next_Hight represents the Next RLC sequence number of the largest RLC sequence number of the RLC PDUs received in the current RLC reception window.
5. The method for updating the AM mode NR RLC reception window according to claim 2, wherein in step S42, the RLC entity having the out-of-order delivery PDCP PDU performs RLC window sliding: the RLC entity calculates the PDCP sequence number of the PDCP PDU corresponding to the RLC sequence number of each RLC PDU of the current RLC reception window, finds out the RLC SDU corresponding to the PDCP sequence number part-1 "of rx_deliv, and updates rx_next to the RLC sequence number corresponding to the RLC SDU following the found RLC SDU, i.e. to RLC sequence number +1 of the found RLC SDU.
6. The method for updating an AM mode NR RLC reception window according to claim 2, wherein in step S42, the RLC window sliding by both RLC entities means: the two RLC entities respectively calculate PDCP sequence numbers of PDCP PDUs corresponding to RLC sequence numbers of each RLC PDU of the two RLC receiving windows, respectively find out the RLC SDU closest to PDCP sequence number part-1 "of" rx_deliv "in the two RLC receiving windows, and respectively update rx_next of the two RLC entities to RLC sequence numbers corresponding to the found two RLC SDUs.
7. An apparatus for updating an NR RLC reception window of an AM mode, wherein one PDCP entity at a receiving end of the AM mode is associated with only one RLC entity; the device comprises a timeout processing unit, a first transfer unit, a first RLC calculation unit and a first synchronous sliding window unit;
The timeout processing unit is configured to, when the reordering timer is timed out, cause the PDCP entity of the receiving end of the AM mode to sequentially perform the following operations: (1) Setting a first variable RX_DELIV_last to record the RX_DELIV value updated last time, wherein RX_DELIV refers to the count value of the first PDCP SDU which is not delivered to the upper layer; (2) Delivering the out-of-order PDCP SDUs before RX_REORD and the sequential PDCP SDUs after RX_REORD to an upper layer, and updating RX_DELIV to be equal to or more than the count value of the PDCP SDU which is not delivered to the upper layer by the first one of RX_REORD; RX_REORD refers to the next count value of the count value of PDCP PDU triggering a reordering timer; (3) Setting a second variable PdcpRecvWnwgap for recording the length of a discontinuous section in the PDCP receiving window, and setting a third variable PushWnwDiff for recording the length of the left boundary of the PDCP receiving window updated and slid at the time;
the first transfer unit is configured to cause a PDCP entity at a receiving end of the AM mode to transfer a second variable pdcprcvwnwgap and a third variable pushwnwtiff to an associated RLC entity;
the first RLC computing unit is configured to enable one RLC entity associated with the PDCP entity in the receiving end of the AM mode to set a fourth variable rllcrecvwnwgap for recording a length of a discontinuous segment in an RLC receiving window;
The first synchronous sliding window unit is configured to, when the second variable pdcprcvwnwgap is equal to the fourth variable rllcrecvwnwgap, cause one RLC entity associated with the PDCP entity in the receiving end of the AM mode to sequentially perform the following operations: (1) the RLC entity performs RLC window sliding, namely: the RLC entity updates the left boundary of the RLC receiving window, the offset sliding to the right is a third variable PushWnwDiff, and RX_Next is updated to RX_Next+PushWnwDiff; (2) If RX_Highest_Status < RX_Next, the RLC entity updates RX_Highest_Status to RX_Next, otherwise does not update RX_Highest_Status; RX_Highest_status represents the ACK_SN value in the RLC Status report, ACK_SN indicating the RLC sequence number of the RLC SDU that is not received next and that is not indicated to be lost in the RLC Status report; RX_Next represents the Next RLC sequence number of the last completely received RLC SDU received by the RLC entity;
the first synchronization sliding window unit is further configured to, when the second variable pdcprcvwnwgap is not equal to the fourth variable rllcrecvwnwgap, make one RLC entity associated with the PDCP entity in the receiving end of the AM mode not update the RLC receiving window, wait for the MAC layer HARQ to retransmit the RLC PDU by the RLC entity, or wait for the reassembly timer to timeout and notify the RLC entity of the transmitting end of the RLC PDU through a status report.
8. The apparatus for updating an AM mode NR RLC reception window according to claim 7, wherein one PDCP entity at the receiving end of the AM mode is changed to associate two RLC entities; the first transmission unit, the first RLC calculation unit and the first synchronous sliding window unit are respectively changed into a second transmission unit, a second RLC calculation unit and a second synchronous sliding window unit;
the second transferring unit is configured to cause the PDCP entity at the receiving end of the AM mode to transfer the PDCP sequence number part in the first variable rx_deliv and the second variable pdcprcvwnwgap to the two associated RLC entities;
the second RLC calculating unit is configured to enable two RLC entities pRLC and RLC associated with the PDCP entity in the receiving end of the AM mode to set fourth variables pRlcRecvWnwGap, sRlcRecvWnwGap respectively for recording lengths of discontinuous segments in respective RLC receiving windows;
the second synchronous sliding window unit is used for the situation that when the second variable is equal to the sum of the two fourth variables and one RLC entity does not have the out-of-order delivery PDCP PDU; when another RLC entity has the condition of submitting PDCP PDUs out of order, the RLC entity having PDCP PDUs submitted out of order sequentially performs the following operations: (1) The RLC entity without the disorder delivery PDCP PDU does not do RLC window sliding, and the RLC entity with the disorder delivery PDCP PDU does RLC window sliding; (2) The RLC entity with the out-of-order delivery PDCP PDU updates RX_Hight_Status to RX_Next if RX_Hight_Status is less than RX_Next, otherwise, does not update;
The second synchronous sliding window unit is further configured to, when the second variable is equal to a sum of two fourth variables and there is an out-of-order delivery of PDCP PDUs by two RLC entities associated with the PDCP entity in the receiving end of the AM mode, cause the two RLC entities to sequentially perform the following operations: (1) the two RLC entities both do RLC window sliding; (2) If RX_Hight_Status < RX_Next of any RLC entity, the RLC entity updates RX_Hight_Status to RX_Next, otherwise not;
the second synchronous sliding window unit is further configured to, when the second variable is not equal to the sum of the two fourth variables, make both RLC entities associated with the PDCP entity in the receiving end of the AM mode not update their respective RLC receiving windows, wait for the MAC layer HARQ to retransmit the RLC PDU by the two RLC entities, or notify the RLC entity of the transmitting end of the RLC PDU through a status report after the reassembly timer is timed out.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211042700.8A CN115515180B (en) | 2022-08-29 | 2022-08-29 | Method and device for updating NR RLC receiving window of AM mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211042700.8A CN115515180B (en) | 2022-08-29 | 2022-08-29 | Method and device for updating NR RLC receiving window of AM mode |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115515180A CN115515180A (en) | 2022-12-23 |
| CN115515180B true CN115515180B (en) | 2023-09-15 |
Family
ID=84501727
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211042700.8A Active CN115515180B (en) | 2022-08-29 | 2022-08-29 | Method and device for updating NR RLC receiving window of AM mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115515180B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118118134A (en) * | 2022-11-30 | 2024-05-31 | 维沃移动通信有限公司 | Data receiving method and device, network side equipment and terminal equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104283656A (en) * | 2014-09-09 | 2015-01-14 | 南京纳凯永馨信息科技有限公司 | AM RLC receiving window maintenance and data receiving method |
| CN110731097A (en) * | 2017-06-16 | 2020-01-24 | 三星电子株式会社 | Method and apparatus for fast reporting frequency measurement result in next generation mobile communication system |
| CN111132225A (en) * | 2019-10-22 | 2020-05-08 | 翱捷智能科技(上海)有限公司 | Receiving side of RLC entity in AM mode and method for receiving data |
| CN112399468A (en) * | 2019-08-14 | 2021-02-23 | 大唐移动通信设备有限公司 | Data transmission method and receiving equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE60336813D1 (en) * | 2003-09-23 | 2011-06-01 | Panasonic Corp | Protocol Context Transmission in a Mobile Communication System |
| KR20180090658A (en) * | 2017-02-03 | 2018-08-13 | 삼성전자주식회사 | Method and apparatus for processing a security key in a handover using multiple connections in a mobile communication system |
-
2022
- 2022-08-29 CN CN202211042700.8A patent/CN115515180B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104283656A (en) * | 2014-09-09 | 2015-01-14 | 南京纳凯永馨信息科技有限公司 | AM RLC receiving window maintenance and data receiving method |
| CN110731097A (en) * | 2017-06-16 | 2020-01-24 | 三星电子株式会社 | Method and apparatus for fast reporting frequency measurement result in next generation mobile communication system |
| CN112399468A (en) * | 2019-08-14 | 2021-02-23 | 大唐移动通信设备有限公司 | Data transmission method and receiving equipment |
| CN111132225A (en) * | 2019-10-22 | 2020-05-08 | 翱捷智能科技(上海)有限公司 | Receiving side of RLC entity in AM mode and method for receiving data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115515180A (en) | 2022-12-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9860915B2 (en) | Apparatus and method for moving a receive window in a radio access network | |
| EP1993241B1 (en) | A method for reassembling data in wireless communication system and an apparatus thereof | |
| US8413002B2 (en) | Method of performing ARQ procedure for transmitting high rate data | |
| CN101483505B (en) | Service data unit discarding method | |
| EP2063579B1 (en) | Method for handling radio bearer messages during reset and reestablishment in a wireless system | |
| US8738984B2 (en) | Apparatus for processing retransmission failure in radio link control (RLC) layer | |
| EP1788751A1 (en) | A method of handling RLC SDUs during RLC reset and RLC re-establishment in a UMTS system | |
| US20070110101A1 (en) | Method of Handling RLC SDUs During RLC Reset and RLC Re-establishment in a UMTS System | |
| WO2007130325A2 (en) | Method and apparatus for facilitating lossless handover in 3gpp long term evolution systems | |
| CN115515180B (en) | Method and device for updating NR RLC receiving window of AM mode |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |