WO2024114536A1 - 数据接收方法、装置、网络侧设备及终端设备 - Google Patents

数据接收方法、装置、网络侧设备及终端设备 Download PDF

Info

Publication number
WO2024114536A1
WO2024114536A1 PCT/CN2023/134063 CN2023134063W WO2024114536A1 WO 2024114536 A1 WO2024114536 A1 WO 2024114536A1 CN 2023134063 W CN2023134063 W CN 2023134063W WO 2024114536 A1 WO2024114536 A1 WO 2024114536A1
Authority
WO
WIPO (PCT)
Prior art keywords
sequence number
rlc
pdcp
entity
data
Prior art date
Application number
PCT/CN2023/134063
Other languages
English (en)
French (fr)
Inventor
蔡佳楠
刘佳敏
Original Assignee
维沃移动通信有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2024114536A1 publication Critical patent/WO2024114536A1/zh

Links

Classifications

    • 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/1607—Details of the supervisory signal
    • 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

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a data receiving method, device, network side equipment and terminal equipment.
  • Radio Link Control (RLC) entity adopts the Acknowledged Mode (AM)
  • the lower boundary of the receive window is driven by the state variable RX_Next.
  • RRC Radio Resource Control
  • the receiving window will be moved when the timer times out. In this case, even if the RLC entity receives the retransmitted data packet, the PDCP entity will still discard it, thus causing a certain degree of waste of air interface resources.
  • COUNT discontinuous count values
  • the PDCP timer t-Reordering will not be started because the COUNT of PDCP data packets obtained from multiple RLC entities is continuous. However, if one or several of the RLC entities have discontinuous or incomplete reception at this time, these RLC entities will also request unnecessary ARQ retransmissions through status reports, which will also result in a waste of air interface resources.
  • the embodiments of the present application provide a data receiving method, apparatus, network side equipment and terminal equipment, which can reduce the waste of air interface resources.
  • a data receiving method comprising:
  • a radio link layer control protocol RLC entity receives a first indication sent by a packet data convergence protocol PDCP entity, where the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of a second receiving window of the PDCP entity;
  • the RLC entity updates a target state variable according to the first parameter
  • the RLC entity moves the first receiving window according to the updated target state variable
  • the value of the target state variable is the RLC sequence number of the last RLC service data unit received in sequence and completely by the RLC entity plus 1.
  • Another data receiving method comprising:
  • the packet data convergence protocol PDCP entity sends a first indication to the radio link layer control protocol RLC entity, where the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of the second receiving window of the PDCP entity;
  • the window moving condition of the second receiving window includes any one of the following:
  • the reordering timer of the PDCP entity times out
  • the count value of the data units received by the PDCP entity is equal to a reference state variable, and the value of the reference state variable is the count value of the first data unit waiting to be delivered in the PDCP entity.
  • a data receiving device which is applied to an RLC entity, including:
  • a first indication receiving module configured to receive a first indication sent by a Packet Data Convergence Protocol PDCP entity, wherein the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of a second receiving window of the PDCP entity;
  • a state variable updating module used for updating a target state variable according to the first parameter
  • a receiving window moving module used for moving the first receiving window according to the updated target state variable
  • the value of the target state variable is the RLC sequence number of the last RLC service data unit received in sequence and completely by the RLC entity plus 1.
  • another data receiving device is provided, which is applied to a PDCP entity, including:
  • a first indication sending module configured to send a first indication to a radio link layer control protocol RLC entity when the window of the second receiving window moves, wherein the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of the second receiving window of the PDCP entity;
  • the window moving condition of the second receiving window includes any one of the following:
  • the reordering timer of the PDCP entity times out
  • the count value of the data units received by the PDCP entity is equal to a reference state variable, and the value of the reference state variable is the count value of the first data unit waiting to be delivered in the PDCP entity.
  • a terminal device which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the data receiving method described in the first aspect and/or the second aspect are implemented.
  • a network side device including a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data receiving method described in the first aspect and/or the second aspect are implemented.
  • a data receiving system comprising: a network side device and a terminal device, wherein the network side device can be used to execute the steps of the data receiving method as described in the first aspect and/or the second aspect above, and the terminal device can be used to execute the steps of the data receiving method as described in the first aspect and/or the second aspect above.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the data receiving method described in the first aspect and/or the second aspect are implemented.
  • a chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instructions to implement the steps of the data receiving method described in the first aspect and/or the second aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the steps of the data receiving method as described in the first aspect and/or the second aspect.
  • a transmission device/equipment which includes the device/equipment (configured to) be used to execute steps to implement the data receiving method as described in the first aspect and/or the second aspect.
  • the PDCP entity when the window of the second receiving window moves, the PDCP entity sends a first indication to the RLC entity, and indicates the lower boundary of the second receiving window to the RLC entity through the first parameter carried in the first indication.
  • the RLC entity updates the target state variable RX_Next according to the first parameter, and then moves the first receiving window according to the target state variable RX_Next, so that the first receiving window can move with the movement of the second receiving window.
  • the data unit received in the previous first receiving window (the first receiving window before the movement) will no longer be received even if it is not completely received.
  • the RLC entity continues to receive the next data unit in the receiving window after the move, and there is no need to request the sender to retransmit the data unit whose RLC SN is less than RX_Next, thereby reducing the waste of air interface resources.
  • FIG1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG2 is a flow chart of a data receiving method in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of data reception when a PDCP entity corresponds to an RLC entity in an initial state according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of the lower boundaries of the first receiving window and the second receiving window after the reordering timer times out in the related art
  • FIG. 5 is a schematic diagram of the lower boundaries of the first receiving window and the second receiving window after the reordering timer times out in an embodiment of the present application;
  • FIG. 6 is a schematic diagram of data reception when a PDCP entity corresponds to two RLC entities in an initial state according to an embodiment of the present application
  • FIG. 7 is another schematic diagram of the lower boundaries of the first receiving window and the second receiving window after the reordering timer times out in the related art
  • FIG. 8 is another schematic diagram of the lower boundaries of the first receiving window and the second receiving window after the reordering timer times out in an embodiment of the present application;
  • FIG9 is a flow chart of another data receiving method in an embodiment of the present application.
  • FIG10 is a structural block diagram of a data receiving device in an embodiment of the present application.
  • FIG11 is a structural block diagram of another data receiving device in an embodiment of the present application.
  • FIG12 is a structural block diagram of a communication device in an embodiment of the present application.
  • FIG13 is a block diagram of a terminal device in an embodiment of the present application.
  • FIG14 is a structural block diagram of a network side device in an embodiment of the present application.
  • FIG15 is a structural block diagram of another network-side device in an embodiment of the present application.
  • first, second, etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by “first” and “second” are generally of the same type, and the number of objects is not limited.
  • the first object can be one or more.
  • “and/or” in the specification and claims represents at least one of the connected objects, and the character “/" generally represents that the objects associated with each other are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR new radio
  • FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system includes a terminal device 11 and a network side device 12.
  • the terminal device 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/virtual reality (virtual reality, VR) device, a robot, a wearable device (Wearable Device), a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (personal computer, PC), a teller machine or a self-service machine and other terminal side devices
  • the network side device 12 may include an access network device or a core network device, wherein the access network device 12 may also be referred to as a wireless access network device, a wireless access network (Radio Access Network, RAN), a wireless access network function or a wireless access network unit.
  • the access network device 12 may include a base station, a WLAN access point or a WiFi node, etc.
  • the base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home B node, a home evolved B node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary, it should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
  • the core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in
  • an embodiment of the present application provides a data receiving method.
  • FIG. 2 a flow chart of a data receiving method provided by an embodiment of the present application is shown. The method is applied to an RLC entity, as shown in FIG. 2 , and the method may specifically include:
  • Step 201 An RLC entity receives a first indication sent by a PDCP entity, where the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of a second receiving window of the PDCP entity.
  • Step 202 The RLC entity updates a target state variable according to the first parameter.
  • Step 203 The RLC entity moves the first receiving window according to the updated target state variable.
  • the value of the target state variable is the RLC sequence number of the last RLC service data unit received in sequence and completely by the RLC entity plus 1.
  • the RLC entity may be an RLC entity in a terminal device or an RLC entity in a network side device.
  • the terminal device may be the terminal device 11 in FIG. 1
  • the network side device may be the access network device in FIG. 1 .
  • the newly defined artificial intelligence processing node on the base station or access network side it can also be the core network equipment in Figure 1, such as the network data analysis function (Network Data Analytics Function, NWDAF), the location management function (Location Management Function, LMF), or the newly defined processing node on the core network side, or it can be a combination of the above multiple nodes.
  • NWDAF Network Data Analytics Function
  • LMF Location Management Function
  • the RLC entity has three modes: Transparent Mode (TM), Unacknowledged Mode (UM) and Acknowledged Mode (AM). Based on the data transmission mode, the RLC entity can be divided into TM RLC entity, UM RLC entity and AM RLC entity, where an AM RLC entity includes a transmitting end and a receiving end.
  • the RLC entity in the embodiment of the present application is an AM RLC entity.
  • the data receiving method provided in the embodiment of the present application is mainly used to improve the data receiving behavior in the receiving end of the AM RLC entity (hereinafter referred to as "RLC entity").
  • an RLC entity receives a first indication sent by a PDCP entity.
  • the first indication carries a first parameter, and the first parameter is used to indicate the lower boundary of the second receiving window of the PDCP.
  • the first parameter can be a set value, and there is a mapping relationship between the set value and the lower boundary of the second receiving window.
  • the mapping relationship can be specified by the protocol, or configured by the terminal device or network side device to which the RLC entity and the PDCP entity belong. According to the mapping relationship between the set value and the lower boundary of the second receiving window, the lower boundary of the second receiving window can be determined.
  • the first parameter can also be a state variable RX_DELIV maintained by the PDCP entity, and the value of the RX_DELIV is the count value (COUNT) of the next data unit that the PDCP entity expects to receive, that is, the lower boundary of the second receiving window.
  • the second receiving window is driven by the state variable RX_DELIV maintained in the PDCP entity.
  • the PDCP entity in the embodiment of the present application refers to the receiving entity of the PDCP.
  • the receiving entity of the PDCP (hereinafter referred to as the "PDCP entity") is used to process the data unit received from the lower layer (RLC layer) and submit it to the upper layer, and the upper layer includes any one of the application layer (application layer), service data adaptation protocol (Service Data Adaption Protocol, SDAP) layer, and radio resource control (Radio Resource Control, RRC) layer.
  • the PDCP entity needs to maintain the following state variables:
  • RX_DELIV This variable indicates the COUNT value of the first PDCP service data unit (SDU) that has not yet been submitted to the upper layer but is waiting to be submitted;
  • RX_NEXT This variable indicates the COUNT value of the next PDCP SDU expected to be received
  • RX_REORD This variable indicates the COUNT+1 of the PDCP protocol data unit (PDU) that triggers the t-reordering timer, that is, RX_NEXT at this time.
  • the PDCP entity When the PDCP entity receives the PDCP PDU delivered by the RLC entity, it calculates the RCVD_COUNT of the PDU and, after completing the corresponding decryption and security verification processing, performs the following operations:
  • RCVD_COUNT RX_DELIV
  • the PDCP SDUs that have been received and whose COUNT ⁇ RX_REORD and have completed downlink reception processing are delivered to the upper layer in ascending order.
  • PDCP SDUs that have been received and whose COUNT is greater than or equal to RX_REORD and have completed downlink reception processing are delivered to the upper layer in ascending order if COUNT is continuous;
  • the first indication is sent by the PDCP entity when the window of the second receiving window moves, wherein the window movement condition of the second receiving window includes any one of the following:
  • the reordering timer of the PDCP entity times out
  • the count value of the data units received by the PDCP entity is equal to a reference state variable, and the value of the reference state variable is the count value of the first data unit waiting to be delivered in the PDCP entity.
  • the reordering timer t-Reordering times out indicating that the data unit with a count value in the interval [RX_NEXT, RX_REORD] fails to be received.
  • the second receiving window corresponding to the PDCP entity moves, and if the data unit with a count value RCVD_COUNT ⁇ RX_REORD is not received, the PDCP entity will not receive and process these data units later. In this case, even if the RLC entity requests data retransmission from the transmitter and receives the retransmitted data packet, the PDCP entity will still discard the data unit with RCVD_COUNT less than the updated RX_DELIV, which will cause a certain degree of waste of air interface resources.
  • the reference state variable is RX_DELIV.
  • the count value RCVD_COUNT of the data unit received by the PDCP entity RX_DELIV, it is the movement of the second receiving window caused by the normal reception of the data unit.
  • the PDCP timer t-Reordering will not be started.
  • these RLC entities will also request the receiving end to retransmit data through status reports, which will also lead to waste of air interface resources.
  • the PDCP entity when the second receiving window moves due to C1 or C2, the PDCP entity sends a first indication to the RLC entity, and passes the lower boundary of the second receiving window to the RLC entity through the first parameter carried in the first indication.
  • the RLC entity After receiving the first indication, the RLC entity updates the target state variable according to the first parameter carried in the first indication.
  • the target state variable is the state variable RX_Next maintained by the RLC entity, and the value of RX_Next is the value of the RLC entity.
  • the RLC sequence number of the last RLC service data unit received in sequence and in its entirety is incremented by 1.
  • the RLC entity moves the first receiving window according to the updated target state variable.
  • the data unit requested to be retransmitted by the RLC entity to the sender may be discarded after being submitted to the PDCP entity because RCVD_COUNT is less than or equal to the updated RX_DELIV, resulting in a waste of air interface resources.
  • the PDCP entity when the window of the second receiving window moves, the PDCP entity sends a first indication to the RLC entity, and indicates the lower boundary of the second receiving window to the RLC entity through the first parameter carried in the first indication.
  • the RLC entity updates the target state variable RX_Next according to the first parameter, and then moves the first receiving window according to the target state variable RX_Next, so that the first receiving window can move with the movement of the second receiving window.
  • the data unit received in the previous first receiving window (the first receiving window before the movement) will no longer be received even if it is not completely received.
  • the RLC entity continues to receive the next data unit in the receiving window after the move, and there is no need to request the sender to retransmit the data unit whose RLC SN is less than RX_Next, thereby reducing the waste of air interface resources.
  • the RLC entity updates a target state variable according to the first parameter, including:
  • Step S11 the RLC entity determines the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window according to the first parameter, and determines the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window as the first reference sequence number;
  • Step S12 The RLC entity determines a target data unit whose PDCP sequence number is less than the first reference sequence number and greater than PDCP sequence numbers of other data units from each received data unit, and determines the RLC sequence number of the target data unit as the target sequence number;
  • Step S13 The RLC entity updates the target state variable according to the target sequence number.
  • the first parameter carried in the first indication may be a set value
  • the RLC entity may determine the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window of the PDCP entity according to the first parameter, that is, the PDCP SN.
  • the mapping relationship may be specified by the protocol, or may be configured by the RLC entity and the terminal device or network side device to which the PDCP entity belongs.
  • the RLC entity may determine the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window based on the mapping relationship between the set value and the lower boundary of the second receiving window.
  • the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window is used as the first reference sequence number.
  • the RLC entity determines a target data unit whose PDCP sequence number is less than the first reference sequence number and greater than the PDCP sequence numbers of other data units from the received data units, and determines the RLC sequence number of the target data unit as the target sequence number.
  • the RLC entity updates the target state variable according to the target sequence number.
  • the target sequence number of the data unit corresponding to the lower boundary of the second receiving window of the PDCP entity that is, the first reference sequence number
  • the RLC sequence number of the target data unit whose PDCP sequence number is less than PDCP SN(y) and greater than the PDCP sequence numbers of other data units is RLC SN(x)
  • the target state variable RX_Next RLC SN(x) + 1.
  • the RLC entity moves the first receiving window according to RX_Next.
  • the method further includes:
  • Step S21 the RLC entity discards the data unit whose RLC sequence number is less than or equal to the target sequence number
  • Step S22 The RLC entity updates other state variables and/or the running state of the reassembly timer according to the updated target state variable, and triggers a status report.
  • the RLC entity updates the target state variable according to the first indication and moves the first receiving window, it discards the data unit with RLC sequence number less than or equal to the target sequence number, and no longer delivers the data unit with RLC sequence number less than or equal to the target sequence number to the PDCP entity, thereby avoiding multiple deliveries of the same data unit by different RLC entities and improving the processing efficiency of data reception.
  • the RLC entity updates other state variables and/or the running state of the reassembly timer according to the updated target state variable RX_Next, and triggers a state report.
  • state variables that need to be maintained by the receiving end of the RLC entity include:
  • RX_Next The value of this variable is the RLC sequence number of the last RLC service data unit received in sequence and completely by the RLC entity plus 1.
  • RX_Next_Highest The value of this variable is the RLC SN+1 of the data unit with the maximum RLC SN among the data units received by the RLC entity.
  • RX_Next_Status_Trigger The value of this variable is the RLC SN+1 of the data unit that triggers the start of the reassembly timer t-Ressembly.
  • RX_Highest_Status The value of this variable is the highest possible RLC SN that the RLC entity can indicate through ACK_SN when constructing the STATUS PDU.
  • the RLC entity When the RLC entity receives a data unit, it performs the following operations based on the RLC SN of the data unit:
  • AM_Window_Size is the window size of the first receiving window.
  • RLC SN RX_Highest_Status
  • RX_Highest_Status update RX_Highest_Status to the RLC SN of the data unit with data larger than the current RX_Highest_Status but not yet received completely.
  • t-Reassembly can be stopped if any of the following conditions is met:
  • RX_Next_Status_Trigger falls outside the first receiving window, and RX_Next_Status_Trigger is not equal to RX_Next+AM_Window_Size.
  • the RLC entity updates the target state variable and moves the first receiving window according to the first indication, it discards the data units whose RLC sequence numbers are less than or equal to the target sequence number, and then needs to update other state variables and/or the operating status of the reorganization timer according to the above D3 to D5 and trigger a status report.
  • the RLC entity in step S12 determines, from each received data unit, a target data unit whose PDCP sequence number is less than the first reference sequence number and greater than the PDCP sequence numbers of other data units, and determines the RLC sequence number of the target data unit as the target sequence number, including:
  • Sub-step S121 the RLC entity searches for a second reference sequence number whose PDCP sequence number is less than the first reference sequence number and greater than other PDCP sequence numbers in a pre-established mapping relationship table; the mapping relationship table is used to record the PDCP sequence number and the RLC sequence number of each data unit that the RLC entity has received;
  • Sub-step S122 The RLC entity determines the RLC sequence number corresponding to the second reference sequence number in the mapping relationship table as the target sequence number.
  • the PDCP sequence number and the RLC sequence number of each data unit that the RLC entity has received can be recorded through a pre-established mapping relationship table.
  • the RLC entity After the RLC entity receives the first indication sent by the PDCP entity and determines the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window of the PDCP according to the first parameter, that is, the first reference sequence number, the RLC entity can search the mapping relationship table for a second reference sequence number whose PDCP sequence number is less than the first reference sequence number and greater than other PDCP sequence numbers, and then determine the RLC sequence number corresponding to the second reference sequence number as the target sequence number.
  • the method further comprises:
  • Step S31 The RLC entity saves the first reference sequence number
  • Step S32 When the RLC entity receives a data unit that falls within the first receiving window and whose PDCP sequence number is less than the first reference sequence number, it determines that the data unit has been completely received, updates the state variable and/or the operating status of the reassembly timer according to the RLC sequence number corresponding to the data unit, and discards the data unit.
  • the RLC entity can save the first reference sequence number, and when receiving a data unit that falls within the first receiving window and whose PDCP sequence number is less than the first reference sequence number, determine that the data unit has been completely received, update the state variable and/or the operating state of the reassembly timer according to the RLC sequence number corresponding to the data unit, and discard the data unit.
  • state variable here can include at least one of RX_Next, RX_Next_Highest, RX_Next_Status_Trigger and RX_Highest_Status, and the specific update process can refer to D1 to D5 above.
  • the method further includes: the RLC entity clearing the first reference sequence number when the RLC sequence number of the received data unit is equal to the updated target state variable and the PDCP sequence number of the data unit is greater than or equal to the first reference sequence number.
  • the RLC entity may clear the saved first reference sequence number when the RLC sequence number of the received data unit is equal to the updated target state variable RX_Next, and the PDCP SN of the data unit is greater than or equal to the first reference sequence number.
  • the method further includes: the RLC entity continuing to perform reception processing on the received data unit when a preset condition is met.
  • the preset condition includes any one of the following:
  • the RLC entity does not store the first reference sequence number
  • the PDCP sequence number of the data unit received by the RLC entity is greater than or equal to the first reference sequence number.
  • the RLC entity can continue to receive and process the received data unit according to the above operation flow from D1 to D5.
  • the first reference sequence number is not saved in the RLC entity, which may be that the RLC entity has not received the first indication, or the RLC entity has not recorded the first reference sequence number after receiving the first indication and determining the first reference sequence number according to the first parameter in the first indication; it may also be that the RLC entity clears the saved first reference sequence number when the RLC sequence number of the received data unit is equal to the updated target state variable RX_Next, and the PDCP SN of the data unit is greater than or equal to the first reference sequence number.
  • one PDCP entity may correspond to one RLC entity or may correspond to multiple RLC entities.
  • the following will illustrate the data receiving method provided in the embodiment of the present application by combining different corresponding relationships between the PDCP entity and the RLC entity.
  • one PDCP entity corresponds to one RLC entity.
  • FIG3 the data reception situation when the PDCP entity corresponds to one RLC entity in the initial state is shown.
  • Set RX_DELIV 5.
  • FIG. 4 a schematic diagram of the lower boundaries of the first receiving window and the second receiving window after the reordering timer in the related art is shown.
  • the PDCP entity moves the second receiving window when T-reorder times out, and sends a first indication to the RLC entity, which may be a PDCP reordering window updated indication.
  • the first indication carries a first parameter for indicating the lower boundary of the second receiving window of the PDCP entity.
  • the lower boundary RX_DELIV of the second receiving window of the PDCP entity indicated by the first parameter is 5.
  • the RLC entity may consider that the data units from [RX_Next, 4] have been received and submitted to the upper layer, and update the state variables and the running state of the reorganization timer according to the aforementioned processing flow from D3 to D5. Referring to FIG5 , a schematic diagram of the lower boundaries of the first receiving window and the second receiving window after the reordering timer times out in the embodiment of the present application is shown.
  • one PDCP entity corresponds to two RLC entities.
  • FIG. 6 the data reception situation when the PDCP entity corresponds to two RLC entities in the initial state is shown.
  • FIG. 7 a schematic diagram of the lower boundaries of the first receiving window and the second receiving window after the reordering timer in the related art times out is shown.
  • the PDCP entity moves the second receiving window when T-reorder times out, and sends a first indication to the RLC entity
  • the first indication may be a PDCP reordering window updated indication (PDCP reordering window updated indication).
  • the first indication carries a first parameter for indicating the lower boundary of the second receiving window of the PDCP entity.
  • FIG. 8 a schematic diagram of the lower boundary of the first receiving window and the second receiving window after the reordering timer times out in the embodiment of the present application is shown.
  • RLC1 triggers a status report to inform the sender of the current data reception situation.
  • RLC1 stores the first reference sequence number 5 for subsequent reception processing.
  • the PDCP SN corresponding to the AMD PDU subsequently received by RLC1 is 4, because it is less than the stored value 5, it is considered that the data unit is completely received and delivered, and the state variables are directly updated and the timer is controlled according to the processing flow from D1 to D5 mentioned above.
  • the updated RX_Next 5; when the PDCP SN corresponding to the AMD PDU received by RLC1 is 5, the state variables are updated and the timer is controlled according to the processing flow from D1 to D5 mentioned above, and then the stored value of the first reference sequence number is cleared.
  • RLC2 triggers a status report to inform the sender of the current data reception status. Further, RLC2 stores the first reference sequence number 5 for subsequent reception processing.
  • RLC2 updates each state variable and controls the timer according to the aforementioned processing flow from D1 to D5, and then clears the stored value of the first reference sequence number.
  • the embodiment of the present application provides a data receiving method, after receiving the first indication, the RLC entity updates the target state variable RX_Next according to the first parameter carried in the first indication, and then updates the target state variable RX_Next according to the target state variable RX_Next moves the first receiving window so that the first receiving window can move with the movement of the second receiving window.
  • the data unit received in the previous first receiving window (the first receiving window before the movement) will no longer be received even if it is not completely received.
  • the RLC entity will continue to receive the next data unit in the moved receiving window, and there is no need to request the sender to retransmit the data unit whose RLC SN is less than RX_Next, thereby reducing the waste of air interface resources.
  • an embodiment of the present application provides another data receiving method.
  • FIG. 9 a flow chart of another data receiving method provided by an embodiment of the present application is shown. The method is applied to an RLC entity, as shown in FIG. 9 , and the method may specifically include:
  • Step 301 When the window of the second receiving window moves, the PDCP entity sends a first indication to the RLC entity.
  • the first indication carries a first parameter, and the first parameter is used to indicate the lower boundary of the second receiving window of the PDCP entity.
  • the window moving condition of the second receiving window includes any one of the following:
  • the reordering timer of the PDCP entity times out
  • the count value of the data units received by the PDCP entity is equal to a reference state variable, and the value of the reference state variable is the count value of the first data unit waiting to be delivered in the PDCP entity.
  • the PDCP entity in the embodiment of the present application refers to the PDCP receiving entity.
  • the PDCP receiving entity (hereinafter referred to as "PDCP entity") is used to process the PDCP PDU (equivalent to RLC SDU) received from the lower layer (RLC layer) into PDCP SDU and then submit it to the upper layer, which includes any one of the application layer, SDAP layer, and RRC layer.
  • the PDCP entity needs to maintain the following state variables:
  • RX_DELIV This variable indicates the COUNT value of the first PDCP SDU that has not yet been submitted to the upper layer but is waiting to be submitted;
  • RX_NEXT This variable indicates the COUNT value of the next PDCP SDU expected to be received
  • RX_REORD This variable indicates the COUNT+1 of the PDCP data PDU that triggers the t-reordering timer, that is, RX_NEXT at this time.
  • the PDCP entity When the PDCP entity receives the PDCP PDU delivered by the RLC entity, it calculates the RCVD_COUNT of the PDU and, after completing the corresponding decryption and security verification processing, performs the following operations:
  • RCVD_COUNT RX_DELIV
  • the PDCP SDUs that have been received and whose COUNT ⁇ RX_REORD and have completed downlink reception processing are delivered to the upper layer in ascending order.
  • PDCP SDUs that have been received and whose COUNT is greater than or equal to RX_REORD and have completed downlink reception processing are delivered to the upper layer in ascending order if COUNT is continuous;
  • the first indication is sent by the PDCP entity when the window of the second receiving window moves, and the window movement conditions of the second receiving window include the above-mentioned C1 and C2.
  • the reordering timer t-Reordering times out indicating that the reception of the data packet with a count value in the interval [RX_NEXT, RX_REORD] fails.
  • the second receiving window corresponding to the PDCP entity moves, and if the data packet with a count value RCVD_COUNT ⁇ RX_REORD is not received, the PDCP entity will not receive and process these data packets later.
  • the PDCP entity will still discard the data unit with RCVD_COUNT less than the updated RX_DELIV, which will cause a certain degree of waste of air interface resources.
  • the reference state variable is RX_DELIV.
  • the count value RCVD_COUNT of the data unit received by the PDCP entity is equal to RX_DELIV, it is the movement of the second receiving window caused by the normal reception of the data packet.
  • the PDCP timer t-Reordering will not be started.
  • these RLC entities will also request the receiving end to retransmit data through status reports, which will also lead to waste of air interface resources.
  • the PDCP entity when the second receiving window moves due to C1 or C2, the PDCP entity sends a first indication to the RLC entity, and passes the lower boundary of the second receiving window to the RLC entity through the first parameter carried in the first indication.
  • the RLC entity updates the target state variable RX_Next according to the first parameter, and then moves the first receiving window according to the target state variable RX_Next, so that the first receiving window can move with the movement of the second receiving window.
  • the data unit received in the previous first receiving window (the first receiving window before the movement) will no longer be received even if it is not completely received.
  • the RLC entity continues to receive the next data unit in the receiving window after the move, and there is no need to request the sender to retransmit the data unit whose RLC SN is less than RX_Next, thereby reducing the waste of air interface resources.
  • the window movement condition of the second receiving window includes that a count value of data units received by the PDCP entity is equal to a reference state variable, and the sending timing of the first indication includes any one of the following:
  • the window moving step length of the second receiving window is greater than a preset threshold
  • the PDCP entity receives a second indication, where the second indication is used to indicate that one reception data processing is completed.
  • the PDCP entity may send a first indication to the RLC entity each time the window of the second receiving window moves, or may send the first indication when the window movement step of the second receiving window is greater than a preset threshold.
  • the preset threshold may be specified by a protocol, or may be configured by a terminal device or a network-side device to which the PDCP entity belongs.
  • the PDCP entity may also periodically send a first indication. Specifically, a preset timer may be set to send a first indication when the preset timer expires, thereby achieving periodic sending of the first indication.
  • the PDCP entity may also send a first indication when a second indication indicating that data processing is completed is received. The second indication may be sent by the media access control layer (MAC) to the PDCP entity when it is determined that data processing is completed.
  • MAC media access control layer
  • the present application provides a data receiving method, when the PDCP entity moves in the window of the second receiving window, it sends a first indication to the RLC entity, and indicates the lower boundary of the second receiving window to the RLC entity through the first parameter carried in the first indication.
  • the RLC entity updates the target state variable RX_Next according to the first parameter, and then moves the first receiving window according to the target state variable RX_Next, so that the first receiving window can move with the movement of the second receiving window.
  • the data unit received in the previous first receiving window (the first receiving window before the movement) will no longer be received even if it is not completely received.
  • the RLC entity continues to receive the next data unit in the receiving window after the move, and there is no need to request the sender to retransmit the data unit whose RLC SN is less than RX_Next, thereby reducing the waste of air interface resources.
  • the data receiving method provided in the embodiment of the present application can be executed by a data receiving device.
  • the data receiving device provided in the embodiment of the present application is described by taking the data receiving method executed by the data receiving device as an example.
  • an embodiment of the present application provides a data receiving device.
  • a structural block diagram of a data receiving device provided by an embodiment of the present application is shown, and the device can be applied to an RLC entity. As shown in FIG. 10 , the device can specifically include:
  • a first indication receiving module 401 is configured to receive a first indication sent by a Packet Data Convergence Protocol PDCP entity, wherein the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of a second receiving window of the PDCP entity;
  • a state variable updating module 402 configured to update a target state variable according to the first parameter
  • the receiving window moving module 403 is used to move the first receiving window according to the updated target state variable.
  • the value of the target state variable is the RLC sequence number of the last RLC service data unit received in sequence and completely by the RLC entity plus 1.
  • the state variable updating module includes:
  • a first determining submodule configured to determine the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window according to the first parameter, and to confirm the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window is designated as the first reference serial number;
  • a second determination submodule is used to determine, from each received data unit, a target data unit whose PDCP sequence number is less than the first reference sequence number and greater than the PDCP sequence numbers of other data units, and determine the RLC sequence number of the target data unit as the target sequence number;
  • the state variable updating submodule is used to update the target state variable according to the target sequence number.
  • the device further comprises:
  • a first data discarding module configured to discard data units whose RLC sequence numbers are less than or equal to the target sequence number
  • the status report triggering module is used to update other status variables and/or the running status of the reorganization timer according to the updated target status variable, and trigger the status report.
  • the second determining submodule includes:
  • a sequence number search unit configured to search a pre-established mapping relationship table for a second reference sequence number whose PDCP sequence number is less than the first reference sequence number and greater than other PDCP sequence numbers; the mapping relationship table is configured to record the PDCP sequence number and the RLC sequence number of each data unit that the RLC entity has received;
  • a sequence number determination unit is used to determine the RLC sequence number corresponding to the second reference sequence number in the mapping relationship table as the target sequence number.
  • the device further comprises:
  • a sequence number storage module configured for the RLC entity to store the first reference sequence number
  • the second data discarding module is used to determine that when a data unit falling within the first receiving window and with a PDCP sequence number less than the first reference sequence number is received, the data unit has been completely received, updates the state variable and/or the running state of the reassembly timer according to the RLC sequence number corresponding to the data unit, and discards the data unit.
  • the device further comprises:
  • a sequence number clearing module is used to clear the first reference sequence number when the RLC sequence number of the received data unit is equal to the updated target state variable and the PDCP sequence number of the data unit is greater than or equal to the first reference sequence number.
  • the device further comprises:
  • a receiving and processing module used to continue receiving and processing the received data unit when a preset condition is met
  • the preset condition includes any one of the following:
  • the RLC entity does not store the first reference sequence number
  • the PDCP sequence number of the data unit received by the RLC entity is greater than or equal to the first reference sequence number.
  • the data receiving device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment of the first aspect and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • an embodiment of the present application provides a data receiving device.
  • a structural block diagram of another data receiving device provided by an embodiment of the present application is shown, and the device can be applied to a PDCP entity.
  • the device can specifically include:
  • a first indication sending module 501 is used to send a first indication to a radio link layer control protocol RLC entity when the window of the second receiving window moves, wherein the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of the second receiving window of the PDCP entity;
  • the window moving condition of the second receiving window includes any one of the following:
  • the reordering timer of the PDCP entity times out
  • the count value of the data units received by the PDCP entity is equal to a reference state variable, and the value of the reference state variable is the count value of the first data unit waiting to be delivered in the PDCP entity.
  • the window movement condition of the second receiving window includes that a count value of data units received by the PDCP entity is equal to a reference state variable, and the sending timing of the first indication includes any one of the following:
  • the window moving step length of the second receiving window is greater than a preset threshold
  • the preset timer has timed out
  • the PDCP entity receives a second indication, where the second indication is used to indicate that one reception data processing is completed.
  • the data receiving device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment of the second aspect and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the data receiving device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a terminal device.
  • the terminal device can include but is not limited to the types of terminal devices 11 listed above.
  • an embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, wherein the memory 902 stores a program or instruction that can be run on the processor 901.
  • the communication device 900 is a network side device
  • the program or instruction is executed by the processor 901 to implement the various steps of the data receiving method embodiment described in the first aspect above, and can achieve the same technical effect.
  • the communication device 900 is a terminal device
  • the program or instruction is executed by the processor 901 to implement the various steps of the data receiving method embodiment described in the second aspect above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • FIG13 it is a schematic diagram of the hardware structure of a terminal device implementing an embodiment of the present application.
  • the terminal device 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009 and at least some of the components of the processor 1010.
  • the terminal device 1000 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1010 through a power management system, so as to implement functions such as charging, discharging, and power consumption management through the power management system.
  • a power supply such as a battery
  • the terminal device structure shown in FIG13 does not constitute a limitation on the terminal device, and the terminal device may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042.
  • the graphics processor 10041 is used in the video capture mode or The image data of the static picture or video obtained by the image capture device (such as a camera) in the image capture mode is processed.
  • the display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc.
  • the user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072.
  • the touch panel 10071 is also called a touch screen.
  • the touch panel 10071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the RF unit 1001 can transmit the data to the processor 1010 for processing; in addition, the RF unit 1001 can send uplink data to the network side device.
  • the RF unit 1001 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
  • the memory 1009 can be used to store software programs or instructions and various data.
  • the memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the memory 1009 may include a volatile memory or a non-volatile memory, or the memory 1009 may include both volatile and non-volatile memories.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM).
  • the memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
  • the processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.
  • the radio frequency unit 1001 is used to receive a first indication sent by a packet data convergence protocol PDCP entity, where the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of a second receiving window of the PDCP entity;
  • the processor 1010 is configured to update the target state variable according to the first parameter; and move the first receiving window according to the updated target state variable;
  • the value of the target state variable is the RLC sequence number of the last RLC service data unit received in sequence and completely by the RLC entity plus 1.
  • the processor 1010 is specifically configured to determine, according to the first parameter, a value corresponding to the lower boundary of the second receiving window.
  • the method comprises the following steps: determining the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window, and determining the PDCP sequence number of the data unit corresponding to the lower boundary of the second receiving window as the first reference sequence number; determining a target data unit whose PDCP sequence number is less than the first reference sequence number and greater than the PDCP sequence numbers of other data units from each received data unit, and determining the RLC sequence number of the target data unit as the target sequence number; and updating the target state variable according to the target sequence number.
  • processor 1010 is further configured to discard data units whose RLC sequence numbers are less than or equal to the target sequence number; update other state variables and/or the operating status of the reassembly timer according to the updated target state variables, and trigger a status report.
  • the processor 1010 is specifically used to search for a second reference sequence number in a pre-established mapping relationship table, whose PDCP sequence number is less than the first reference sequence number and greater than other PDCP sequence numbers; the mapping relationship table is used to record the PDCP sequence number and RLC sequence number of each data unit that the RLC entity has received; and the RLC sequence number corresponding to the second reference sequence number in the mapping relationship table is determined as the target sequence number.
  • processor 1010 is also used to save the first reference sequence number; when receiving a data unit that falls within the first receiving window and whose PDCP sequence number is less than the first reference sequence number, it is determined that the data unit has been completely received, and the state variable and/or the operating status of the reassembly timer are updated according to the RLC sequence number corresponding to the data unit, and the data unit is discarded.
  • the processor 1010 is further configured to clear the first reference sequence number when the RLC sequence number of the received data unit is equal to the updated target state variable and the PDCP sequence number of the data unit is greater than or equal to the first reference sequence number.
  • the processor 1010 is further configured to continue receiving and processing the received data unit if a preset condition is met;
  • the preset condition includes any one of the following:
  • the RLC entity does not store the first reference sequence number
  • the PDCP sequence number of the data unit received by the RLC entity is greater than or equal to the first reference sequence number.
  • the radio frequency unit 1001 is used to send a first indication to a radio link layer control protocol RLC entity when the window of the second receiving window moves, where the first indication carries a first parameter, and the first parameter is used to indicate a lower boundary of the second receiving window of the PDCP entity;
  • the window moving condition of the second receiving window includes any one of the following:
  • the reordering timer of the PDCP entity times out
  • the count value of the data units received by the PDCP entity is equal to a reference state variable, and the value of the reference state variable is the count value of the first data unit waiting to be delivered in the PDCP entity.
  • the window movement condition of the second receiving window includes that a count value of data units received by the PDCP entity is equal to a reference state variable, and the sending timing of the first indication includes any one of the following:
  • the window moving step length of the second receiving window is greater than a preset threshold
  • the preset timer has timed out
  • the PDCP entity receives a second indication, where the second indication is used to indicate that one reception data processing is completed.
  • the network side device 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114 and a memory 115.
  • the antenna 111 is connected to the radio frequency device 112.
  • the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing.
  • the baseband device 113 processes the information to be sent and sends it to the radio frequency device 112, and the radio frequency device 112 processes the received information and sends it out through the antenna 111.
  • the method executed by the network-side device in the above embodiment may be implemented in the baseband device 113, which includes a baseband processor.
  • the baseband device 113 may include, for example, at least one baseband board, on which a plurality of chips are arranged, as shown in FIG11 , wherein one of the chips is, for example, a baseband processor, which is connected to the memory 115 through a bus interface to call a program in the memory 115 and execute the network device operations shown in the above method embodiment.
  • the network side device may also include a network interface 116, which is, for example, a common public radio interface (CPRI).
  • a network interface 116 which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 1100 of the embodiment of the present invention also includes: instructions or programs stored in the memory 115 and executable on the processor 114.
  • the processor 114 calls the instructions or programs in the memory 115 to execute the methods executed by the modules shown in Figure 10 or Figure 11, and achieves the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a network side device.
  • the network side device 1200 includes: a processor 1201, a network interface 1202 and a memory 1203.
  • the network interface 1202 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 1200 of the embodiment of the present invention also includes: instructions or programs stored in the memory 1203 and executable on the processor 1201.
  • the processor 1201 calls the instructions or programs in the memory 1203 to execute the methods executed by the modules shown in Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • the various processes of the above-mentioned data receiving method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal device described in the above embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
  • An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data receiving method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the present application embodiment further provides a computer program/program product, wherein the computer program/program product is stored In the storage medium, the computer program/program product is executed by at least one processor to implement the various processes of the above-mentioned data receiving method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a data receiving system, including: a terminal device and a network side device, wherein the terminal can be used to execute the steps of the data receiving method described in the second aspect above, and the network side device can be used to execute the steps of the data receiving method described in the first aspect above.
  • the technical solution of the present application can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.
  • a storage medium such as ROM/RAM, a magnetic disk, or an optical disk
  • a terminal which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种数据接收方法、装置、网络侧设备及终端设备，属于通信技术领域，本申请实施例的数据接收方法包括：无线链路层控制协议RLC实体接收分组数据汇聚协议PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；所述RLC实体根据所述第一参数更新目标状态变量；所述RLC实体根据更新后的目标状态变量移动第一接收窗；其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。

Description

数据接收方法、装置、网络侧设备及终端设备
相关申请的交叉引用
本申请要求在2022年11月30日提交中国专利局、申请号为202211535285.X、名称为“数据接收方法、装置、网络侧设备及终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请属于通信技术领域，具体涉及一种数据接收方法、装置、网络侧设备及终端设备。
背景技术
无线链路层控制协议(Radio Link Control，RLC)实体采用确认模式(Acknowledged Mode，AM)时，接收窗的下边界靠状态变量RX_Next推动。相关技术中，只有在SN＝RX_Next的数据包接收完全时，才会更新RX_Next，进而移动接收窗。没有收到的SN＝RX_Next的数据包会通过状态报告请求对端进行RLC的自动重传请求(Automatic Repeat-reQuest，ARQ)重传直至接收完整，或当最大重传次数超过时，终端设备触发无线资源控制(Radio Resource Control，RRC)重建立过程，或者基站侧释放与该终端设备的连接。
如果分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)实体的接收端由于接收的数据包的计数值(COUNT)不连续启动了定时器t-Reordering，当定时器超时时移动接收窗，这种情况下即使RLC实体接收到了重传数据包，PDCP实体也还是会丢弃，因此造成一定程度的空口资源浪费。
如果一个PDCP实体对应多个RLC实体，由于从多个RLC实体获得的PDCP数据包COUNT连续，所以PDCP的定时器t-Reordering不会启动，但如果此时其中的某个或某几个RLC实体存在接收不连续或不完整的情况，那么这些RLC实体也会通过状态报告请求不必要的ARQ重传，同样会产生空口资源浪费的情况。
发明内容
本申请实施例提供一种数据接收方法、装置、网络侧设备及终端设备，能够降低空口资源的浪费。
第一方面，提供了一种数据接收方法，包括：
无线链路层控制协议RLC实体接收分组数据汇聚协议PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
所述RLC实体根据所述第一参数更新目标状态变量；
所述RLC实体根据更新后的目标状态变量移动第一接收窗；
其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
第二方面，提供了另一种数据接收方法，包括：
分组数据汇聚协议PDCP实体在第二接收窗的窗口移动的情况下，向无线链路层控制协议RLC实体发送第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
其中，所述第二接收窗的窗口移动条件包括以下任一项：
所述PDCP实体的重排序定时器超时；
所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
第三方面，提供了一种数据接收装置，应用于RLC实体，包括：
第一指示接收模块，用于接收分组数据汇聚协议PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
状态变量更新模块，用于根据所述第一参数更新目标状态变量；
接收窗移动模块，用于根据更新后的目标状态变量移动第一接收窗；
其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
第四方面，提供了另一种数据接收装置，应用于PDCP实体，包括：
第一指示发送模块，用于在第二接收窗的窗口移动的情况下，向无线链路层控制协议RLC实体发送第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
其中，所述第二接收窗的窗口移动条件包括以下任一项：
所述PDCP实体的重排序定时器超时；
所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
第五方面，提供了一种终端设备，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面和/或第二方面所述的数据接收方法的步骤。
第六方面，提供了一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面和/或第二方面所述的数据接收方法的步骤。
第七方面，提供了一种数据接收系统，包括：网络侧设备和终端设备，所述网络侧设备可用于执行如上述第一方面和/或第二方面所述的数据接收方法的步骤，所述终端设备可用于执行如上述第一方面和/或第二方面所述的数据接收方法的步骤。
第八方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面和/或第二方面所述的数据接收方法的步骤。
第九方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面和/或第二方面所述的数据接收方法的步骤。
第十方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面和/或第二方面所述的数据接收方法的步骤。
第十一方面，提供了一种传输装置/设备，其中，包括所述装置/设备(被配置成)用于执行以实现如第一方面和/或第二方面所述的数据接收方法的步骤。
在本申请实施例中，PDCP实体在第二接收窗的窗口移动时，就向RLC实体发送第一指示，通过第一指示中携带的第一参数向RLC实体指示第二接收窗的下边界。RLC实体接收到第一指示之后，根据第一参数更新目标状态变量RX_Next，进而根据目标状态变量RX_Next移动第一接收窗，使得第一接收窗能够随着第二接收窗的移动而移动。第一接收窗移动之后，上一个第一接收窗(移动之前的第一接收窗)内接收的数据单元即使没有接收完全也不再继续接收，RLC实体在移动后的接收窗内继续接收下一个数据单元，无需再向发送端请求重传RLC SN小于RX_Next的数据单元，从而减少了空口资源的浪费。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例中的一种数据接收方法的流程图；
图3是本申请实施例中初始状态下PDCP实体对应一个RLC实体时的数据接收情况示意图；
图4是相关技术中重排序定时器超时后第一接收窗和第二接收窗的下边界的一种示意图；
图5是本申请实施例中重排序定时器超时后第一接收窗和第二接收窗的下边界的一种示意图；
图6是本申请实施例中初始状态下PDCP实体对应两个RLC实体时的数据接收情况示意图；
图7是相关技术中重排序定时器超时后第一接收窗和第二接收窗的下边界的另一种示意图；
图8是本申请实施例中重排序定时器超时后第一接收窗和第二接收窗的下边界的另一种示意图；
图9是本申请实施例中的另一种数据接收方法的流程图；
图10是本申请实施例中的一种数据接收装置的结构框图；
图11是本申请实施例中的另一种数据接收装置的结构框图；
图12是本申请实施例中的一种通信设备的结构框图；
图13是本申请实施例中的一种终端设备的结构框图；
图14是本申请实施例中的一种网络侧设备的结构框图；
图15是本申请实施例中另一种网络侧设备的结构框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端设备11和网络侧设备12。其中，终端设备11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(VUE)、行人终端(PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链 等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端设备11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备12也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备12可以包括基站、WLAN接入点或WiFi节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)，统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)，网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的数据接收方法进行详细地说明。
第一方面，本申请实施例提供了一种数据接收方法。参照图2，示出了本申请实施例提供的一种数据接收方法的流程图。该方法应用于RLC实体，如图2所示，该方法具体可以包括：
步骤201、RLC实体接收PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界。
步骤202、所述RLC实体根据所述第一参数更新目标状态变量。
步骤203、所述RLC实体根据更新后的目标状态变量移动第一接收窗。
其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
所述RLC实体可以是终端设备中的RLC实体，也可以是网络侧设备中的RLC实体。所述终端设备可以是图1中的终端设备11，所述网络侧设备可以是图1中的接入网设备， 如基站或接入网侧新定义的人工智能处理节点，还可以是图1中的核心网设备，如网络数据分析功能(Network Data Analytics Function，NWDAF)、定位管理功能(Location Management Function，LMF)、或者核心网侧新定义的处理节点，还可以是上述多个节点的组合。
需要说明的是，RLC实体有三种模式：透明模式(Transparent Mode，TM)、非确认模式(Unacknowledged Mode，UM)和确认模式(Acknowledged Mode，AM)。基于数据传输模式，RLC实体可以分为TM RLC实体、UM RLC实体和AM RLC实体，其中，一个AM RLC实体包括发送端和接收端。本申请实施例中的RLC实体为AM RLC实体。本申请实施例提供的数据接收方法，主要用于对AM RLC实体(以下简称“RLC实体”)的接收端中的数据接收行为进行改进。
在本申请实施例中，RLC实体接收PDCP实体发送的第一指示。该第一指示中携带第一参数，该第一参数用于指示PDCP的第二接收窗的下边界。作为一种示例，该第一参数可以为一个设定值，该设定值与第二接收窗的下边界之间存在映射关系，该映射关系可以由协议规定，也可以由RLC实体与PDCP实体所属的终端设备或网络侧设备配置。根据设定值与第二接收窗的下边界之间的映射关系，可以确定出第二接收窗的下边界。作为另一种示例，第一参数也可以是PDCP实体维护的状态变量RX_DELIV，该RX_DELIV的值为PDCP实体下一个期望接收的数据单元的计数值(COUNT)，也即第二接收窗的下边界，第二接收窗靠PDCP实体中维护的状态变量RX_DELIV推动。
可以理解的是，本申请实施例中的PDCP实体指的是PDCP的接收实体。PDCP的接收实体(以下简称“PDCP实体”)用于将从下层(RLC层)接收到的数据单元处理后递交上层，所述上层包括应用层(application layer)、服务数据适配协议(Service Data Adaption Protocol，SDAP)层、无线资源控制(Radio Resource Control，RRC)层中的任一项。PDCP实体需要维护以下状态变量：
RX_DELIV：该变量指示的是还没有递交上层但是等待递交的第一个PDCP服务数据单元(Service Data Unit，SDU)的COUNT值；
RX_NEXT：该变量指示的是下一个期望接收的PDCP SDU的COUNT值；
RX_REORD：该变量指示的是触发t-reordering定时器的PDCP协议数据单元(Protocol Data Unit，PDU)的COUNT+1，即此时的RX_NEXT。
当PDCP实体接收到RLC实体递交的PDCP PDU时，会计算出该PDU的RCVD_COUNT，在完成相应的解密和完保校验处理后，执行以下操作：
A1、如果RCVD_COUNT<RX_DELIV，或COUNT＝RCVD_COUNT的PDCP PDU已经被接收过，则丢弃该PDCP PDU，如果没有被丢弃则继续进行下列接收处理；
A2、如果RCVD_COUNT>＝RX_NEXT，更新RX_NEXT＝RCVD_COUNT+1；
A3、如果RCVD_COUNT＝RX_DELIV，按照COUNT升序的顺序向高层递交处理好的PDCP SDU，更新RX_DELIV使其指向还没有递交到上层的第一个PDCP SDU；
A4、如果重排序定时器t-Reordering正在运行且RX_DELIV>＝RX_REORD，则停止t-Reordering；
A5、如果重排序定时器t-Reordering没有运行且RX_DELIV<RX_NEXT，则更新RX_REORD＝RX_NEXT，启动t-Reordering。
如果t-Reordering超时，则认为计数值位于区间[RX_NEXT,RX_REORD]的数据包接收失败，PDCP实体执行以下操作：
B1、已经接收的COUNT<RX_REORD且完成下行接收处理的PDCP SDU按升序递交给高层；
B2、已经接收的COUNT>＝RX_REORD且完成下行接收处理的PDCP SDU如果COUNT可连续则按升序递交给高层；
B3、更新RX_DELIV使其指向还没有递交到上层的第一个PDCP SDU；
B4、如果RX_DELIV<RX_NEXT，则更新RX_REORD＝RX_NEXT，启动t-Reordering。
在本申请实施例中，第一指示是PDCP实体在第二接收窗的窗口移动的情况下发送的，其中，第二接收窗的窗口移动条件包括以下任一项：
C1、所述PDCP实体的重排序定时器超时；
C2、所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
对于C1项，重排序定时器t-Reordering超时，说明计数值位于区间[RX_NEXT,RX_REORD]的数据单元接收失败，此时PDCP实体对应的第二接收窗移动，且计数值RCVD_COUNT＜RX_REORD的数据单元如果没有接收到，PDCP实体后续也不会对这些数据单元再进行接收处理。这种情况下，即使RLC实体向发送端请求了数据重传，并接收到了重传数据包，PDCP实体也还是会将RCVD_COUNT小于更新后的RX_DELIV的数据单元丢弃，这样就会造成一定程度的空口资源浪费。
对于C2项，所述参考状态变量为RX_DELIV，当PDCP实体接收到的数据单元的计数值RCVD_COUNT＝RX_DELIV时，属于数据单元正常接收引起的第二接收窗的移动。在这种情况下，如果一个PDCP实体对应多个RLC实体，由于PDCP实体从多个RLC实体获得的PDCP数据单元COUNT连续，所以PDCP的定时器t-Reordering不会启动，但如果此时其中的某个或某几个RLC实体存在接收不连续或不完整的情况，那么这些RLC实体也会通过状态报告请求接收端进行数据重传，同样会导致空口资源浪费。
为了避免空口资源浪费，在本申请实施例中，PDCP实体在第二接收窗因C1或C2发生窗口移动的情况下，向RLC实体发送第一指示，通过第一指示中携带的第一参数将第二接收窗的下边界传递给RLC实体。
RLC实体接收到第一指示之后，根据第一指示中携带的第一参数更新目标状态变量。其中，目标状态变量为RLC实体维护的状态变量RX_Next，RX_Next的值为RLC实体 按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
最后，RLC实体根据更新后的目标状态变量移动第一接收窗。
在相关技术中，RLC实体仅在RLC序列号，也即RLC SN＝RX_Next的数据单元接收完全时才更新RX_Next；如果RLC SN＝RX_Next的数据单元没有接收完全，RLC实体通过状态报告请求发送端对数据单元进行重传直至接收完全，或者当最大重传次数超过预设阈值时，终端设备会触发RRC重建立过程，或者网络侧设备释放RLC实体所属的终端设备。结合前述C1项和C2项的相关描述可知，RLC实体向发送端请求重传的数据单元在递交给PDCP实体之后，也可能会因为RCVD_COUNT小于或等于更新后的RX_DELIV而被丢弃，造成空口资源的浪费。
而在本申请实施例中，PDCP实体在第二接收窗的窗口移动时，就向RLC实体发送第一指示，通过第一指示中携带的第一参数向RLC实体指示第二接收窗的下边界。RLC实体接收到第一指示之后，根据第一参数更新目标状态变量RX_Next，进而根据目标状态变量RX_Next移动第一接收窗，使得第一接收窗能够随着第二接收窗的移动而移动。第一接收窗移动之后，上一个第一接收窗(移动之前的第一接收窗)内接收的数据单元即使没有接收完全也不再继续接收，RLC实体在移动后的接收窗内继续接收下一个数据单元，无需再向发送端请求重传RLC SN小于RX_Next的数据单元，从而减少了空口资源的浪费。
可选地，步骤202所述RLC实体根据所述第一参数更新目标状态变量，包括：
步骤S11、所述RLC实体根据所述第一参数确定所述第二接收窗的下边界对应的数据单元的PDCP序列号，并将所述第二接收窗的下边界对应的数据单元的PDCP序列号确定为第一参考序列号；
步骤S12、所述RLC实体从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将所述目标数据单元的RLC序列号确定为目标序列号；
步骤S13、所述RLC实体根据所述目标序列号更新所述目标状态变量。
在本申请实施例中，第一指示中携带的第一参数可以为一个设定值，RLC实体可以根据第一参数确定PDCP实体的第二接收窗的下边界对应的数据单元的PDCP序列号，也即PDCP SN。示例性地，第一参数与第二接收窗的下边界对应的数据单元的PDCP序列号之间存在映射关系，该映射关系可以由协议规定，也可以由RLC实体与PDCP实体所属的终端设备或网络侧设备配置。RLC实体根据设定值与第二接收窗的下边界之间的映射关系，可以确定出第二接收窗的下边界对应的数据单元的PDCP序列号。在本申请中，将第二接收窗的下边界对应的数据单元的PDCP序列号作为第一参考序列号。
接下来，RLC实体从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将该目标数据单元的RLC序列号确定为目标序列号。
RLC实体根据目标序列号更新目标状态变量。作为一种示例，假设PDCP实体的第二接收窗的下边界对应的数据单元的PDCP序列号，也即第一参考序列号为PDCP SN(y)，在RLC实体已经接收到的数据单元中，PDCP序列号小于PDCP SN(y)且大于其他数据单元的PDCP序列号的目标数据单元的RLC序列号为RLC SN(x)，那么目标状态变量RX_Next＝RLC SN(x)+1。RLC实体根据RX_Next移动第一接收窗。
在本申请的一种可选实施例中，所述方法还包括：
步骤S21、所述RLC实体丢弃RLC序列号小于或等于所述目标序列号的数据单元；
步骤S22、所述RLC实体根据更新后的目标状态变量更新其他状态变量和/或重组定时器的运行状态，并触发状态报告。
在本申请实施例中，认为RLC序列号小于或等于目标序列号RLC SN(x)的数据单元已经接收完全并已完成向高层的递交，因此，在本申请实施例中，RLC实体在根据第一指示更新目标状态变量并移动第一接收窗之后，丢弃RLC序列号小于或等于目标序列号的数据单元，不再将RLC序列号小于或等于目标序列号的数据单元递交给PDCP实体，避免了不同RLC实体对同一数据单元的多次递交，提高了数据接收的处理效率。。
并且，RLC实体根据更新后的目标状态变量RX_Next更新其他状态变量和/或重组定时器的运行状态，并触发状态报告。
需要说明的是，RLC实体的接收端需要维护的状态变量包括：
RX_Next：该变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
RX_Next_Highest：该变量的值为RLC实体接收到的数据单元中具有最大RLC SN的数据单元的RLC SN+1。
RX_Next_Status_Trigger：该变量的值为触发重组定时器t-Ressembly启动的数据单元的RLC SN+1。
RX_Highest_Status：该变量的值为RLC实体在构建STATUS PDU时可以通过ACK_SN指示的最高的可能的RLC SN。
当RLC实体接收到数据单元时，会根据数据单元的RLC SN执行以下操作：
D1、当数据单元的RLC SN满足RX_Next<＝RLC SN<RX_Next+AM_Window_Size时才能对该数据单元进行后续接收处理，否则直接丢弃该数据单元。其中，AM_Window_Size为第一接收窗的窗口大小。
D2、当数据单元的RLC SN>＝RX_Next_Highest时，更新RX_Next_Highest＝RLC SN+1。
D3、如果该数据单元对应的SDU的所有数据接收完全，重组RLC SDU并递交给高层，并更新状态变量。具体地，如果RLC SN＝RX_Highest_Status，更新RX_Highest_Status为比当前RX_Highest_Status大的数据还没有接收完全的数据单元的RLC SN。如果RLC SN＝RX_Next，更新RX_Next为比当前RX_Next大的数据还没有接收完全的数据单元的 RLC SN。
D4、如果重组定时器t-Reassembly在运行中，满足以下任意条件即可停止t-Reassembly：
a)RX_Next_Status_Trigger＝RX_Next；
b)RX_Next_Status_Trigger＝RX_Next+1，且RLC SN＝RX_Next的数据单元只有最后一个分段没有接收；
c)RX_Next_Status_Trigger落在第一接收窗外，且RX_Next_Status_Trigger不等于RX_Next+AM_Window_Size。
D5、如果重组定时器t-Reassembly没有运行，满足以下任意条件时，需启动t-Reassembly并设定RX_Next_Status_Trigger＝RX_Next_Highest：
a)RX_Next_Highest>RX_Next+1；
b)RX_Next_Highest＝RX_Next+1且RLC SN＝RX_Next的数据单元除了最后一个分段外还有分段没有被接收。
可以理解的是，RLC实体在根据第一指示更新目标状态变量并移动第一接收窗之后，丢弃RLC序列号小于或等于目标序列号的数据单元，然后需要按照上述D3至D5更新其他状态变量和/或重组定时器的运行状态并触发状态报告。
在本申请的一种可选实施例中，步骤S12所述RLC实体从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将所述目标数据单元的RLC序列号确定为目标序列号，包括：
子步骤S121、所述RLC实体在预先建立的映射关系表中查找PDCP序列号小于所述第一参考序列号且大于其他PDCP序列号的第二参考序列号；所述映射关系表用于记录所述RLC实体已经接收到的各个数据单元的PDCP序列号和RLC序列号；
子步骤S122、所述RLC实体将所述映射关系表中所述第二参考序列号对应的RLC序列号确定为目标序列号。
在本申请实施例中，可以通过预先建立的映射关系表记录RLC实体已经接收到的各个数据单元的PDCP序列号和RLC序列号。RLC实体在接收到PDCP实体发送的第一指示并根据第一参数确定出PDCP的第二接收窗的下边界对应的数据单元的PDCP序列号也即第一参考序列号之后，可以在该映射关系表中查找PDCP序列号小于第一参考序列号且大于其他PDCP序列号的第二参考序列号，然后将该第二参考序列号对应的RLC序列号确定为目标序列号。
可选地，所述方法还包括：
步骤S31、所述RLC实体保存所述第一参考序列号；
步骤S32、所述RLC实体在接收到落在所述第一接收窗内且PDCP序列号小于所述第一参考序列号的数据单元时，确定所述数据单元已接收完全，按照所述数据单元对应的RLC序列号更新状态变量和/或所述重组定时器的运行状态，并丢弃所述数据单元。
在本申请实施例中，RLC实体在确定出PDCP的第二接收窗的下边界对应的第一参考序列号之后，可以保存该第一参考序列号，并在接收到落在第一接收窗内且PDCP序列号小于第一参考序列号的数据单元时，确定该数据单元已接收完全，按照该数据单元对应的RLC序列号更新状态变量和/或所述重组定时器的运行状态，并丢弃所述数据单元。可以理解的是，这里的状态变量可以包括RX_Next、RX_Next_Highest、RX_Next_Status_Trigger和RX_Highest_Status中的至少一项，具体更新过程可以参照上述D1至D5。
可选地，所述方法还包括：所述RLC实体在接收到的数据单元的RLC序列号等于更新后的目标状态变量，且所述数据单元的PDCP序列号大于或等于所述第一参考序列号的情况下，清除所述第一参考序列号。
在本申请实施例中，RLC实体可以在接收到的数据单元的RLC序列号等于更新后的目标状态变量RX_Next，且数据单元的PDCP SN大于或等于第一参考序列号时，清除保存的第一参考序列号。
可选地，所述方法还包括：所述RLC实体在满足预设条件的情况下，对接收的数据单元继续进行接收处理。
其中，所述预设条件包括以下任一项：
E1、所述RLC实体中未保存所述第一参考序列号；
E2、所述RLC实体接收的数据单元的PDCP序列号大于或等于所述第一参考序列号。
在本申请实施例中，如果满足上述E1和E2中的任一项，RLC实体可以按照上述D1至D5的操作流程对接收的数据单元继续进行接收处理。其中，对于E1项，RLC实体中未保存第一参考序列号，可能是RLC实体并未接收到第一指示，或者是RLC实体在接收到第一指示并根据第一指示中的第一参数确定出第一参考序列号之后，未记录第一参考序列号；也可能是RLC实体在接收到的数据单元的RLC序列号等于更新后的目标状态变量RX_Next，且数据单元的PDCP SN大于或等于第一参考序列号时，清除了保存的第一参考序列号。
可以理解的是，一个PDCP实体可以对应一个RLC实体，也可以对应多个RLC实体。下面将结合PDCP实体与RLC实体之间不同的对应关系，对本申请实施例提供的数据接收方法进行举例说明。
在本申请的一种可能的应用场景中，一个PDCP实体对应一个RLC实体。参照图3，示出了初始状态下PDCP实体对应一个RLC实体时的数据接收情况。如图3所示，假设初始状态时，RLC实体已经成功接收了RLC SN＝1、3、4的确认模式数据(AM Data，AMD)PDU并递交给了PDCP实体，因为RLC SN＝2的数据包没有接收到或只有部分数据被接收，所以RLC实体的第一接收窗的下边界RX_Next＝2，PDCP实体的第二接收窗的下边界RX_DELIV＝2，同时PDCP实体启动了重排序定时器T-reorder。当T-reorder超时且RLC SN＝2的AMD PDU仍没有接收时，PDCP实体移动了第二接收窗的下边界 使RX_DELIV＝5。
参照图4，示出了相关技术中重排序定时器超时后第一接收窗和第二接收窗的下边界示意图。如图4所示，如果按照相关技术，RLC实体的第一接收窗与PDCP实体的第二接收窗相互独立，所以RLC实体的第一接收窗的下边界仍为RX_Next＝2，RLC实体通过状态报告请求发送端对RLC SN＝2的数据单元进行ARQ重传。由于PDCP实体的第二接收窗已经发生了移动，这种情况下即使RLC实体接收到了发送端重传的RLC SN＝2的数据单元，PDCP实体也还是会丢弃该数据单元，因此造成了空口资源的浪费。
在本申请实施例提供的数据接收方法中，PDCP实体在T-reorder超时的情况下移动第二接收窗，并向RLC实体发送第一指示，该第一指示可以是PDCP重排序窗口更新指示(PDCP reordering window updated indication)。第一指示中携带第一参数，用于指示所述PDCP实体的第二接收窗的下边界。在图4所示的场景下，第一参数指示的PDCP实体的第二接收窗的下边界RX_DELIV＝5。RLC实体接收到第一指示后，查询映射关系表，得到映射关系表中小于5的最大PDCP SN＝4，也即第二参考序列号为4，PDCP SN＝4对应的RLC SN＝4，也即目标序列号为4。RLC实体可以认为从[RX_Next,4]的数据单元都完成了接收并已经递交给高层，按前述D3至D5的处理流程更新状态变量和重组定时器的运行状态。参照图5，示出了本申请实施例中重排序定时器超时后第一接收窗和第二接收窗的下边界示意图。如图5所示，更新后的RX_Next＝5，第一接收窗同步完成了移动。之后，RLC实体触发状态报告，使发送端获悉当前的数据接收情况。进一步地，RLC实体存储第一参考序列号5，用于后续的接收处理。
结合图5可知，在本申请实施例中，RLC实体无需再请求发送端重传RLC SN＝2的数据单元，从而节省了空口资源。
在本申请的另一种可能的应用场景中，一个PDCP实体对应两个RLC实体。参照图6，示出了初始状态下PDCP实体对应两个RLC实体时的数据接收情况。如图6所示，假设初始状态时，RLC1已经成功接收了RLC SN＝1、3的AMD PDU并递交给了PDCP实体。因为RLC SN＝2的数据单元没有接收到或只有部分数据被接收，所以RLC1的第一接收窗的下边界RX_Next＝2。RLC2已经成功接收了SN＝1、3、4的AMD PDU并递交给了PDCP实体，RLC2的第一接收窗下边界RX_Next＝2。PDCP实体的第二接收窗的下边界RX_DELIV＝2，同时PDCP实体启动了重排序定时器T-reorder。当T-reorder超时且RLC SN＝2的数据包仍没有被接收完全时，PDCP实体移动了第二接收窗的下边界使RX_DELIV＝5。
参照图7，示出了相关技术中重排序定时器超时后第一接收窗和第二接收窗的下边界示意图。如图7所示，如果按照相关技术，RLC实体的第一接收窗与PDCP实体的第二接收窗相互独立，所以RLC1和RLC2的第一接收窗的下边界仍为RX_Next＝2。RLC1和RLC2通过状态报告请求对端对RLC SN＝2进行ARQ重传。由于PDCP实体的第二接收窗已经发生了移动，这种情况下即使RLC1和RLC2接收到了发送端重传的RLC SN＝2 的数据单元，PDCP实体也还是会丢弃该数据单元，因此造成了空口资源的浪费。
在本申请实施例提供的数据接收方法中，PDCP实体在T-reorder超时的情况下移动第二接收窗，并向RLC实体发送第一指示，该第一指示可以是PDCP重排序窗口更新指示(PDCP reordering window updated indication)。第一指示中携带第一参数，用于指示所述PDCP实体的第二接收窗的下边界。在图7所示的场景下，第一参数指示的PDCP实体的第二接收窗的下边界RX_DELIV＝5。
RLC1收到第一指示后，查询RLC1维护的映射关系表，得到映射关系表中小于5的最大PDCP SN＝3，也即第二参考序列号为3，PDCP SN＝3对应的RLC SN＝3，也即目标序列号为3。需要说明的是，在本申请实施例中，每个RLC实体独立维护一个映射关系表。RLC1可以认为从[RX_Next,3]的数据单元都完成了接收并已经递交给高层，按前述D3至D5的处理流程更新状态变量和重组定时器的运行状态。参照图8，示出了本申请实施例中重排序定时器超时后第一接收窗和第二接收窗的下边界示意图。如图8所示，对于RLC1，更新后的RX_Next＝4，RLC1的第一接收窗同步完成了移动。之后，RLC1触发状态报告，使发送端获悉当前的数据接收情况。进一步地，RLC1存储第一参考序列号5，用于后续的接收处理。当RLC1后续接收到的AMD PDU对应的PDCP SN为4时，因为小于存储值5，认为该数据单元完全接收且已递交，直接按前述D1至D5的处理流程更新各状态变量并控制定时器，更新后的RX_Next＝5；当RLC1接收到的AMD PDU对应的PDCP SN为5时，按前述D1至D5的处理流程更新各状态变量并控制定时器，之后清空存储的第一参考序列号的值。
RLC2收到第一指示后，查询RLC2维护的映射关系表，得到映射关系表中小于5的最大PDCP SN＝4，也即第二参考序列号为4，PDCP SN＝4对应的RLC SN＝4，也即目标序列号为4。RLC2可以认为从[RX_Next,4]的数据单元都完成了接收并已经递交给高层，按前述D1至D5的处理流程更新状态变量和重组定时器的运行状态。如图8所示，对于RLC2，更新后的RX_Next＝5，RLC2的第一接收窗同步完成了移动。之后，RLC2触发状态报告，使发送端获悉当前的数据接收情况。进一步地，RLC2存储第一参考序列号5，用于后续的接收处理。当RLC2接收到RLC SN＝5即等于RX_Next的AMD PDU时，正常情况下该数据单元对应的PDCP SN应该大于或等于5，此时RLC2按照前述D1至D5的处理流程更新各状态变量并控制定时器，之后清空存储的第一参考序列号的值。
结合图8可知，在本申请实施例中，RLC1和RLC2均无需再请求发送端重传RLC SN＝2的数据单元，节省了空口资源；并且，RLC1在接收到PDCP SN＝4的数据单元时，由于该数据单元的PDCP SN小于存储的第一参考序列号5，无需再向PDCP实体递交该数据单元，避免了不同RLC实体对同一数据单元的多次递交，提高了数据接收的处理效率。
综上，本申请实施例提供了一种数据接收方法，RLC实体在接收到第一指示之后，根据第一指示中携带的第一参数更新目标状态变量RX_Next，进而根据目标状态变量 RX_Next移动第一接收窗，使得第一接收窗能够随着第二接收窗的移动而移动。第一接收窗移动之后，上一个第一接收窗(移动之前的第一接收窗)内接收的数据单元即使没有接收完全也不再继续接收，RLC实体在移动后的接收窗内继续接收下一个数据单元，无需再向发送端请求重传RLC SN小于RX_Next的数据单元，从而减少了空口资源的浪费。
第二方面，本申请实施例提供了另一种数据接收方法。参照图9，示出了本申请实施例提供的另一种数据接收方法的流程图。该方法应用于RLC实体，如图9所示，该方法具体可以包括：
步骤301、PDCP实体在第二接收窗的窗口移动的情况下，向RLC实体发送第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界。
其中，所述第二接收窗的窗口移动条件包括以下任一项：
C1、所述PDCP实体的重排序定时器超时；
C2、所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
可以理解的是，本申请实施例中的PDCP实体指的是PDCP的接收实体。PDCP的接收实体(以下简称“PDCP实体”)用于将从下层(RLC层)接收到的PDCP PDU(等价于RLC SDU)处理呈PDCP SDU后递交上层，所述上层包括应用层、SDAP层、RRC层中的任一项。
PDCP实体需要维护以下状态变量：
RX_DELIV：该变量指示的是还没有递交上层但是等待递交的第一个PDCP SDU的COUNT值；
RX_NEXT：该变量指示的是下一个期望接收的PDCP SDU的COUNT值；
RX_REORD：该变量指示的是触发t-reordering定时器的PDCP data PDU的COUNT+1，即此时的RX_NEXT。
当PDCP实体接收到RLC实体递交的PDCP PDU时，会计算出该PDU的RCVD_COUNT，在完成相应的解密和完保校验处理后，执行以下操作：
A1、如果RCVD_COUNT<RX_DELIV，或COUNT＝RCVD_COUNT的PDCP PDU已经被接收过，则丢弃该PDCP PDU，如果没有被丢弃则继续进行下列接收处理；
A2、如果RCVD_COUNT>＝RX_NEXT，更新RX_NEXT＝RCVD_COUNT+1；
A3、如果RCVD_COUNT＝RX_DELIV，按照COUNT升序的顺序向高层递交处理好的PDCP SDU，更新RX_DELIV使其指向还没有递交到上层的第一个PDCP SDU；
A4、如果重排序定时器t-Reordering正在运行且RX_DELIV>＝RX_REORD，则停止t-Reordering；
A5、如果重排序定时器t-Reordering没有运行且RX_DELIV<RX_NEXT，则更新 RX_REORD＝RX_NEXT，启动t-Reordering。
如果t-Reordering超时，则认为计数值位于区间[RX_NEXT,RX_REORD]的数据包接收失败，PDCP实体执行以下操作：
B1、已经接收的COUNT<RX_REORD且完成下行接收处理的PDCP SDU按升序递交给高层；
B2、已经接收的COUNT>＝RX_REORD且完成下行接收处理的PDCP SDU如果COUNT可连续则按升序递交给高层；
B3、更新RX_DELIV使其指向还没有递交到上层的第一个PDCP SDU；
B4、如果RX_DELIV<RX_NEXT，则更新RX_REORD＝RX_NEXT，启动t-Reordering。
在本申请实施例中，第一指示是PDCP实体在第二接收窗的窗口移动的情况下发送的，第二接收窗的窗口移动条件包括上述C1和C2。
对于C1项，重排序定时器t-Reordering超时，说明计数值位于区间[RX_NEXT,RX_REORD]的数据包接收失败，此时PDCP实体对应的第二接收窗移动，且计数值RCVD_COUNT＜RX_REORD的数据包如果没有接收到，PDCP实体后续也不会对这些数据包再进行接收处理。这种情况下，即使RLC实体向发送端请求了数据重传，并接收到了重传数据包，PDCP实体也还是会将RCVD_COUNT小于更新后的RX_DELIV的数据单元丢弃，这样就会造成一定程度的空口资源浪费。
对于C2项，所述参考状态变量为RX_DELIV，当PDCP实体接收到的数据单元的计数值RCVD_COUNT＝RX_DELIV时，属于数据包正常接收引起的第二接收窗的移动。在这种情况下，如果一个PDCP实体对应多个RLC实体，由于PDCP实体从多个RLC实体获得的PDCP数据包COUNT连续，所以PDCP的定时器t-Reordering不会启动，但如果此时其中的某个或某几个RLC实体存在接收不连续或不完整的情况，那么这些RLC实体也会通过状态报告请求接收端进行数据重传，同样会导致空口资源浪费。
为了避免空口资源浪费，在本申请实施例中，PDCP实体在第二接收窗因C1或C2发生窗口移动的情况下，向RLC实体发送第一指示，通过第一指示中携带的第一参数将第二接收窗的下边界传递给RLC实体。RLC实体接收到第一指示之后，根据第一参数更新目标状态变量RX_Next，进而根据目标状态变量RX_Next移动第一接收窗，使得第一接收窗能够随着第二接收窗的移动而移动。第一接收窗移动之后，上一个第一接收窗(移动之前的第一接收窗)内接收的数据单元即使没有接收完全也不再继续接收，RLC实体在移动后的接收窗内继续接收下一个数据单元，无需再向发送端请求重传RLC SN小于RX_Next的数据单元，从而减少了空口资源的浪费。
可选地，所述第二接收窗的窗口移动条件包括所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述第一指示的发送时机包括以下任一项：
F1、所述第二接收窗的窗口移动；
F2、所述第二接收窗的窗口移动步长大于预设门限；
F3、预设定时器超时；
F4、所述PDCP实体接收到第二指示，所述第二指示用于指示一次接收数据处理完毕。
在本申请实施例中，PDCP实体可以在第二接收窗的窗口每次发生移动时向RLC实体发送第一指示，也可以在第二接收窗的窗口移动步长大于预设门限的时候发送第一指示。其中，预设门限可以由协议规定，也可以由PDCP实体所属的终端设备或网络侧设备配置。PDCP实体还可以周期性发送第一指示，具体地，可以通过设置一个预设定时器，在预设定时器超时的情况下发送第一指示，从而实现第一指示的周期性发送。此外，PDCP实体还可以在接收到用于指示一次数据处理完毕的第二指示的情况下发送第一指示。该第二指示可以是介质访问控制层(Media Access Control，MAC)在确定一次数据处理完毕的情况下发送给PDCP实体的。
综上，本申请提供了一种数据接收方法，PDCP实体在第二接收窗的窗口移动时，就向RLC实体发送第一指示，通过第一指示中携带的第一参数向RLC实体指示第二接收窗的下边界。RLC实体接收到第一指示之后，根据第一参数更新目标状态变量RX_Next，进而根据目标状态变量RX_Next移动第一接收窗，使得第一接收窗能够随着第二接收窗的移动而移动。第一接收窗移动之后，上一个第一接收窗(移动之前的第一接收窗)内接收的数据单元即使没有接收完全也不再继续接收，RLC实体在移动后的接收窗内继续接收下一个数据单元，无需再向发送端请求重传RLC SN小于RX_Next的数据单元，从而减少了空口资源的浪费。
本申请实施例提供的数据接收方法，执行主体可以为数据接收装置。本申请实施例中以数据接收装置执行数据接收方法为例，说明本申请实施例提供的数据接收装置。
第三方面，本申请实施例提供了一种数据接收装置。参照图10，示出了本申请实施例提供的一种数据接收装置的结构框图，该庄主可以应用于RLC实体。如图10所示，该装置具体可以包括：
第一指示接收模块401，用于接收分组数据汇聚协议PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
状态变量更新模块402，用于根据所述第一参数更新目标状态变量；
接收窗移动模块403，用于根据更新后的目标状态变量移动第一接收窗。
其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
可选地，所述状态变量更新模块，包括：
第一确定子模块，用于根据所述第一参数确定所述第二接收窗的下边界对应的数据单元的PDCP序列号，并将所述第二接收窗的下边界对应的数据单元的PDCP序列号确 定为第一参考序列号；
第二确定子模块，用于从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将所述目标数据单元的RLC序列号确定为目标序列号；
状态变量更新子模块，用于根据所述目标序列号更新所述目标状态变量。
可选地，所述装置还包括：
第一数据丢弃模块，用于丢弃RLC序列号小于或等于所述目标序列号的数据单元；
状态报告触发模块，用于根据更新后的目标状态变量更新其他状态变量和/或重组定时器的运行状态，并触发状态报告。
可选地，所述第二确定子模块，包括：
序列号查找单元，用于在预先建立的映射关系表中查找PDCP序列号小于所述第一参考序列号且大于其他PDCP序列号的第二参考序列号；所述映射关系表用于记录所述RLC实体已经接收到的各个数据单元的PDCP序列号和RLC序列号；
序列号确定单元，用于将所述映射关系表中所述第二参考序列号对应的RLC序列号确定为目标序列号。
可选地，所述装置还包括：
序列号保存模块，用于所述RLC实体保存所述第一参考序列号；
第二数据丢弃模块，用于在接收到落在所述第一接收窗内且PDCP序列号小于所述第一参考序列号的数据单元时，确定所述数据单元已接收完全，按照所述数据单元对应的RLC序列号更新状态变量和/或所述重组定时器的运行状态，并丢弃所述数据单元。
可选地，所述装置还包括：
序列号清除模块，用于在接收到的数据单元的RLC序列号等于更新后的目标状态变量，且所述数据单元的PDCP序列号大于或等于所述第一参考序列号的情况下，清除所述第一参考序列号。
可选地，所述装置还包括：
接收处理模块，用于在满足预设条件的情况下，对接收的数据单元继续进行接收处理；
其中，所述预设条件包括以下任一项：
所述RLC实体中未保存所述第一参考序列号；
所述RLC实体接收的数据单元的PDCP序列号大于或等于所述第一参考序列号。
本申请实施例提供的数据接收装置能够实现第一方面的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
第四方面，本申请实施例提供了一种数据接收装置。参照图11，示出了本申请实施例提供的另一种数据接收装置的结构框图，该装置可以应用于PDCP实体。如图11所示，该装置具体可以包括：
第一指示发送模块501，用于在第二接收窗的窗口移动的情况下，向无线链路层控制协议RLC实体发送第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
其中，所述第二接收窗的窗口移动条件包括以下任一项：
所述PDCP实体的重排序定时器超时；
所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
可选地，所述第二接收窗的窗口移动条件包括所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述第一指示的发送时机包括以下任一项：
所述第二接收窗的窗口移动；
所述第二接收窗的窗口移动步长大于预设门限；
预设定时器超时；
所述PDCP实体接收到第二指示，所述第二指示用于指示一次接收数据处理完毕。
本申请实施例提供的数据接收装置能够实现第二方面的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例中的数据接收装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端设备。示例性的，终端设备可以包括但不限于上述所列举的终端设备11的类型。
可选的，如图12所示，本申请实施例还提供一种通信设备900，包括处理器901和存储器902，存储器902上存储有可在所述处理器901上运行的程序或指令，例如，该通信设备900为网络侧设备时，该程序或指令被处理器901执行时实现上述第一方面所述的数据接收方法实施例的各个步骤，且能达到相同的技术效果。该通信设备900为终端设备时，该程序或指令被处理器901执行时实现上述第二方面所述的数据接收方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
如图13所示，为实现本申请实施例的一种终端设备的硬件结构示意图。
该终端设备1000包括但不限于：射频单元1001、网络模块1002、音频输出单元1003、输入单元1004、传感器1005、显示单元1006、用户输入单元1007、接口单元1008、存储器1009以及处理器1010等中的至少部分部件。
本领域技术人员可以理解，终端设备1000还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1010逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图13中示出的终端设备结构并不构成对终端设备的限定，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1004可以包括图形处理单元(Graphics Processing Unit，GPU)10041和麦克风10042，图形处理器10041对在视频捕获模式或 图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1006可包括显示面板10061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板10061。用户输入单元1007包括触控面板10071以及其他输入设备10072中的至少一种。触控面板10071，也称为触摸屏。触控面板10071可包括触摸检测装置和触摸控制器两个部分。其他输入设备10072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1001接收来自网络侧设备的下行数据后，可以传输给处理器1010进行处理；另外，射频单元1001可以向网络侧设备发送上行数据。通常，射频单元1001包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1009可用于存储软件程序或指令以及各种数据。存储器1009可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1009可以包括易失性存储器或非易失性存储器，或者，存储器1009可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1009包括但不限于这些和任意其它适合类型的存储器。
处理器1010可包括一个或多个处理单元；可选的，处理器1010集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1010中。
在本申请的一种实施例中，射频单元1001用于接收分组数据汇聚协议PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
处理器1010用于根据所述第一参数更新目标状态变量；根据更新后的目标状态变量移动第一接收窗；
其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
可选地，处理器1010具体用于根据所述第一参数确定所述第二接收窗的下边界对应 的数据单元的PDCP序列号，并将所述第二接收窗的下边界对应的数据单元的PDCP序列号确定为第一参考序列号；从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将所述目标数据单元的RLC序列号确定为目标序列号；根据所述目标序列号更新所述目标状态变量。
可选地，处理器1010还用于丢弃RLC序列号小于或等于所述目标序列号的数据单元；根据更新后的目标状态变量更新其他状态变量和/或重组定时器的运行状态，并触发状态报告。
可选地，处理器1010具体用于在预先建立的映射关系表中查找PDCP序列号小于所述第一参考序列号且大于其他PDCP序列号的第二参考序列号；所述映射关系表用于记录所述RLC实体已经接收到的各个数据单元的PDCP序列号和RLC序列号；将所述映射关系表中所述第二参考序列号对应的RLC序列号确定为目标序列号。
可选地，处理器1010还用于保存所述第一参考序列号；在接收到落在所述第一接收窗内且PDCP序列号小于所述第一参考序列号的数据单元时，确定所述数据单元已接收完全，按照所述数据单元对应的RLC序列号更新状态变量和/或所述重组定时器的运行状态，并丢弃所述数据单元。
可选地，处理器1010还用于在接收到的数据单元的RLC序列号等于更新后的目标状态变量，且所述数据单元的PDCP序列号大于或等于所述第一参考序列号的情况下，清除所述第一参考序列号。
可选地，处理器1010还用于在满足预设条件的情况下，对接收的数据单元继续进行接收处理；
其中，所述预设条件包括以下任一项：
所述RLC实体中未保存所述第一参考序列号；
所述RLC实体接收的数据单元的PDCP序列号大于或等于所述第一参考序列号。
在本申请的另一种实施例中，射频单元1001用于在第二接收窗的窗口移动的情况下，向无线链路层控制协议RLC实体发送第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
其中，所述第二接收窗的窗口移动条件包括以下任一项：
所述PDCP实体的重排序定时器超时；
所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
可选地，所述第二接收窗的窗口移动条件包括所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述第一指示的发送时机包括以下任一项：
所述第二接收窗的窗口移动；
所述第二接收窗的窗口移动步长大于预设门限；
预设定时器超时；
所述PDCP实体接收到第二指示，所述第二指示用于指示一次接收数据处理完毕。
本申请实施例还提供一种网络侧设备，如图14所示，该网络侧设备1100包括：天线111、射频装置112、基带装置113、处理器114和存储器115。天线111与射频装置112连接。在上行方向上，射频装置112通过天线111接收信息，将接收的信息发送给基带装置113进行处理。在下行方向上，基带装置113对要发送的信息进行处理，并发送给射频装置112，射频装置112对收到的信息进行处理后经过天线111发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置113中实现，该基带装置113包括基带处理器。
基带装置113例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图11所示，其中一个芯片例如为基带处理器，通过总线接口与存储器115连接，以调用存储器115中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口116，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备1100还包括：存储在存储器115上并可在处理器114上运行的指令或程序，处理器114调用存储器115中的指令或程序执行图10或图11所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供了一种网络侧设备。如图15所示，该网络侧设备1200包括：处理器1201、网络接口1202和存储器1203。其中，网络接口1202例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备1200还包括：存储在存储器1203上并可在处理器1201上运行的指令或程序，处理器1201调用存储器1203中的指令或程序执行图4所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述数据接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述数据接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储 在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述数据接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种数据接收系统，包括：终端设备及网络侧设备，所述终端可用于执行如上第二方面所述的数据接收方法的步骤，所述网络侧设备可用于执行如上第一方面所述的数据接收方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (20)

  1. 一种数据接收方法，所述方法包括：
    无线链路层控制协议RLC实体接收分组数据汇聚协议PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
    所述RLC实体根据所述第一参数更新目标状态变量；
    所述RLC实体根据更新后的目标状态变量移动第一接收窗；
    其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
  2. 根据权利要求1所述的方法，其中，所述RLC实体根据所述第一参数更新目标状态变量，包括：
    所述RLC实体根据所述第一参数确定所述第二接收窗的下边界对应的数据单元的PDCP序列号，并将所述第二接收窗的下边界对应的数据单元的PDCP序列号确定为第一参考序列号；
    所述RLC实体从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将所述目标数据单元的RLC序列号确定为目标序列号；
    所述RLC实体根据所述目标序列号更新所述目标状态变量。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    所述RLC实体丢弃RLC序列号小于或等于所述目标序列号的数据单元；
    所述RLC实体根据更新后的目标状态变量更新其他状态变量和/或重组定时器的运行状态，并触发状态报告。
  4. 根据权利要求2所述的方法，其中，所述RLC实体从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将所述目标数据单元的RLC序列号确定为目标序列号，包括：
    所述RLC实体在预先建立的映射关系表中查找PDCP序列号小于所述第一参考序列号且大于其他PDCP序列号的第二参考序列号；所述映射关系表用于记录所述RLC实体已经接收到的各个数据单元的PDCP序列号和RLC序列号；
    所述RLC实体将所述映射关系表中所述第二参考序列号对应的RLC序列号确定为目标序列号。
  5. 根据权利要求2所述的方法，其中，所述方法还包括：
    所述RLC实体保存所述第一参考序列号；
    所述RLC实体在接收到落在所述第一接收窗内且PDCP序列号小于所述第一参考序列号的数据单元时，确定所述数据单元已接收完全，按照所述数据单元对应的RLC序列号更新状态变量和/或所述重组定时器的运行状态，并丢弃所述数据单元。
  6. 根据权利要求5所述的方法，其中，所述方法还包括：
    所述RLC实体在接收到的数据单元的RLC序列号等于更新后的目标状态变量，且所述数据单元的PDCP序列号大于或等于所述第一参考序列号的情况下，清除所述第一参考序列号。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    所述RLC实体在满足预设条件的情况下，对接收的数据单元继续进行接收处理；
    其中，所述预设条件包括以下任一项：
    所述RLC实体中未保存所述第一参考序列号；
    所述RLC实体接收的数据单元的PDCP序列号大于或等于所述第一参考序列号。
  8. 一种数据接收方法，其中，所述方法包括：
    分组数据汇聚协议PDCP实体在第二接收窗的窗口移动的情况下，向无线链路层控制协议RLC实体发送第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
    其中，所述第二接收窗的窗口移动条件包括以下任一项：
    所述PDCP实体的重排序定时器超时；
    所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
  9. 根据权利要求8所述的方法，其中，所述第二接收窗的窗口移动条件包括所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述第一指示的发送时机包括以下任一项：
    所述第二接收窗的窗口移动；
    所述第二接收窗的窗口移动步长大于预设门限；
    预设定时器超时；
    所述PDCP实体接收到第二指示，所述第二指示用于指示一次接收数据处理完毕。
  10. 一种数据接收装置，其中，包括：
    第一指示接收模块，用于接收分组数据汇聚协议PDCP实体发送的第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
    状态变量更新模块，用于根据所述第一参数更新目标状态变量；
    接收窗移动模块，用于根据更新后的目标状态变量移动第一接收窗；
    其中，所述目标状态变量的值为所述RLC实体按序接收且接收完整的最后一个RLC服务数据单元的RLC序列号加1。
  11. 根据权利要求10所述的装置，其中，所述状态变量更新模块，包括：
    第一确定子模块，用于根据所述第一参数确定所述第二接收窗的下边界对应的数据单元的PDCP序列号，并将所述第二接收窗的下边界对应的数据单元的PDCP序列号确定为第一参考序列号；
    第二确定子模块，用于从已经接收到的各个数据单元中确定出PDCP序列号小于所述第一参考序列号且大于其他数据单元的PDCP序列号的目标数据单元，并将所述目标数据单元的RLC序列号确定为目标序列号；
    状态变量更新子模块，用于根据所述目标序列号更新所述目标状态变量。
  12. 根据权利要求11所述的装置，其中，所述装置还包括：
    第一数据丢弃模块，用于丢弃RLC序列号小于或等于所述目标序列号的数据单元；
    状态报告触发模块，用于根据更新后的目标状态变量更新其他状态变量和/或重组定时器的运行状态，并触发状态报告。
  13. 一种数据接收装置，其中，包括：
    第一指示发送模块，用于在第二接收窗的窗口移动的情况下，向无线链路层控制协议RLC实体发送第一指示，所述第一指示中携带第一参数，所述第一参数用于指示所述PDCP实体的第二接收窗的下边界；
    其中，所述第二接收窗的窗口移动条件包括以下任一项：
    所述PDCP实体的重排序定时器超时；
    所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述参考状态变量的值为所述PDCP实体中等待递交的第一个数据单元的计数值。
  14. 根据权利要求13所述的装置，其中，所述第二接收窗的窗口移动条件包括所述PDCP实体接收到的数据单元的计数值等于参考状态变量，所述第一指示的发送时机包括以下任一项：
    所述第二接收窗的窗口移动；
    所述第二接收窗的窗口移动步长大于预设门限；
    预设定时器超时；
    所述PDCP实体接收到第二指示，所述第二指示用于指示一次接收数据处理完毕。
  15. 一种网络侧设备，其中，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至9任一项所述的数据接收方法的步骤。
  16. 一种终端设备，其中，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至9任一项所述的数据接收方法的步骤。
  17. 一种可读存储介质，其中，所述可读存储介质上存储程序或指令，所述程序或 指令被处理器执行时实现如权利要求1至9任一项所述的数据接收方法的步骤。
  18. 一种芯片，其中，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至9任一项所述的数据接收方法。
  19. 一种计算机程序产品，其中，所述计算机程序产品被至少一个处理器执行以实现如权利要求1至9任一项所述的数据接收方法。
  20. 一种传输装置/设备，其中，包括所述装置/设备被配置成用于执行如权利要求1至9任一项所述的数据接收方法。
PCT/CN2023/134063 2022-11-30 2023-11-24 数据接收方法、装置、网络侧设备及终端设备 WO2024114536A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211535285.X 2022-11-30
CN202211535285.XA CN118118134A (zh) 2022-11-30 2022-11-30 数据接收方法、装置、网络侧设备及终端设备

Publications (1)

Publication Number Publication Date
WO2024114536A1 true WO2024114536A1 (zh) 2024-06-06

Family

ID=91210979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/134063 WO2024114536A1 (zh) 2022-11-30 2023-11-24 数据接收方法、装置、网络侧设备及终端设备

Country Status (2)

Country Link
CN (1) CN118118134A (zh)
WO (1) WO2024114536A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190319893A1 (en) * 2017-08-07 2019-10-17 Lg Electronics Inc. Method for handling state variables of a pdcp entity in wireless communication system and a device therefor
CN111132225A (zh) * 2019-10-22 2020-05-08 翱捷智能科技(上海)有限公司 一种am模式下的rlc实体的接收侧及其接收数据的方法
CN112399468A (zh) * 2019-08-14 2021-02-23 大唐移动通信设备有限公司 一种数据传输方法及接收设备
CN115515180A (zh) * 2022-08-29 2022-12-23 翱捷科技股份有限公司 一种更新am模式的nr rlc接收窗口的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190319893A1 (en) * 2017-08-07 2019-10-17 Lg Electronics Inc. Method for handling state variables of a pdcp entity in wireless communication system and a device therefor
CN112399468A (zh) * 2019-08-14 2021-02-23 大唐移动通信设备有限公司 一种数据传输方法及接收设备
CN111132225A (zh) * 2019-10-22 2020-05-08 翱捷智能科技(上海)有限公司 一种am模式下的rlc实体的接收侧及其接收数据的方法
CN115515180A (zh) * 2022-08-29 2022-12-23 翱捷科技股份有限公司 一种更新am模式的nr rlc接收窗口的方法及装置

Also Published As

Publication number Publication date
CN118118134A (zh) 2024-05-31

Similar Documents

Publication Publication Date Title
JP4318707B2 (ja) 無線通信システムにおける送信側の再確立時にタイマーを処理する方法及び装置
EP1993226B1 (en) Method and related apparatus for handling re-establishment of radio link control entity in a wireless communications system
US20100105334A1 (en) Radio link control status reporting and polling
TWI734010B (zh) 傳輸數據的方法和設備
US20030202501A1 (en) Method and system for polling PDU of radio link control layer
CN111818630B (zh) 状态变量维护方法、装置及用户设备
WO2018214081A1 (zh) 无线链路控制传输方法及相关产品
CN110234124B (zh) 信息传输方法及终端设备
CN113923713A (zh) 数据处理的方法及装置
WO2020048256A1 (zh) 确定方法、终端设备及网络设备
WO2019095975A1 (zh) 数据包处理的方法和设备
EP3926916A1 (en) Timer control method, data packet processing method, and device
WO2018228193A1 (zh) 一种业务数据单元分段处理方法和数据接收端
US20070183328A1 (en) Method of resetting radio link control entity in a mobile communications system and related apparatus
WO2022078517A1 (zh) 数据传输方法、设备和存储介质
CN101068372B (zh) 处理无线链接控制重置流程的变量的方法及其装置
CN109644083B (zh) 数据传输方法及相关产品
WO2019134168A1 (en) Radio link control (rlc) acknowledged mode (am) data reception
WO2024114536A1 (zh) 数据接收方法、装置、网络侧设备及终端设备
US20220201564A1 (en) Data transmission method, terminal, and network node
WO2022121876A1 (zh) 多播业务的确认模式传输方法、装置、设备及存储介质
CN112671515B (zh) 一种无线链路控制层有限重传数据传输方法
EP3723409A1 (en) Wireless communication method and apparatus
CN113939026A (zh) 用户设备、网络侧设备及无线通信方法
WO2023041016A1 (zh) 多播业务的状态变量指示方法和设备