WO2019047912A1 - 处理数据的方法和设备 - Google Patents

处理数据的方法和设备 Download PDF

Info

Publication number
WO2019047912A1
WO2019047912A1 PCT/CN2018/104549 CN2018104549W WO2019047912A1 WO 2019047912 A1 WO2019047912 A1 WO 2019047912A1 CN 2018104549 W CN2018104549 W CN 2018104549W WO 2019047912 A1 WO2019047912 A1 WO 2019047912A1
Authority
WO
WIPO (PCT)
Prior art keywords
data unit
count value
wireless device
value
protocol
Prior art date
Application number
PCT/CN2018/104549
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
Priority claimed from CN201710940143.4A external-priority patent/CN109474651B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18854517.2A priority Critical patent/EP3618405A4/en
Priority to US16/633,398 priority patent/US11025555B2/en
Publication of WO2019047912A1 publication Critical patent/WO2019047912A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present application relates to the field of communications and, more particularly, to a method and apparatus for processing data.
  • the fifth generation (5th Generation, 5G) mobile communication technology is an extension of the 4th generation (4G) mobile communication technology.
  • the existing Evolved Universal Terrestrial Radio Access Network (E-UTRAN) standard supports Dual Connectivity (DC), that is, a UE configured with multiple Rx/Tx in the RRC_CONNECTED connection state.
  • DC Dual Connectivity
  • the radio resources scheduled by the two base station eNBs may be utilized, wherein the two eNBs are connected by a non-ideal backhaul on the X2 interface.
  • One of the two eNBs is a master eNB (MeNB) and one is a secondary eNB (Secondary eNB, SeNB).
  • the receiving device after receiving the data, the receiving device performs data processing in the Packet Data Convergence Protocol (PDCP) layer, including decryption, integrity check, reordering, and the like.
  • PDCP Packet Data Convergence Protocol
  • a Data Radio Bearer corresponds to one PDCP entity (or PDCP layer), and the PDCP layer performs the received PDCP Protocol Data Unit (PDCP PDU). After reordering, it is delivered to the upper layer protocol stack.
  • This transport mechanism is called In-Order Delivery (or in-order delivery).
  • the PDCP layer can reorder the received PDCP PDUs and directly deliver the data to the upper layer protocol stack, that is, the out-of-order transmission mechanism (Out-of- Order Delivery, or a non-sequential delivery.
  • the prior art does not address a solution for both a PDCP PDU that is delivered in sequence (or within a PDCP entity) and a PDCP PDU that is not delivered in order.
  • the present application provides a method and apparatus for processing data to provide a PDCP PDU that is delivered in sequence within a data radio bearer (or within a PDCP entity) and a non-sequential PDCP PDU. s solution.
  • a method of processing data is provided, the method being applied to a wireless device, the method comprising:
  • the first value set includes the wireless device receiving and storing Receiving a count value of the service data unit corresponding to the sequentially delivered protocol data unit in the cache, the third value set including the non-sequential delivery received by the wireless device and submitted by the wireless device to the upper layer protocol stack a count value of the service data unit corresponding to the protocol data unit, wherein the fifth value set formed by the second value set and the fourth value set is a continuous count value area counted from the first count value segment.
  • the wireless device performs any of the foregoing possible implementations by using a packet data convergence protocol PDCP layer of the wireless device; the first protocol data unit is a PDCP packet data unit PDU.
  • PDCP packet data convergence protocol
  • the foregoing method may be a process performed by a wireless device, such as a UE or a network device, at its PDCP layer.
  • the second count value is a count value of a service data unit corresponding to a protocol data unit that is delivered by the wireless device to the last sequential delivery protocol stack, and a non-deletion of the wireless device. The larger of the maximum values of the service data unit corresponding to the protocol data unit submitted in order,
  • the first count value is matched with the second count value maintained by the wireless device, specifically:
  • the first count value is equal to the second count value plus one.
  • the second count value is a count value of a service data unit corresponding to a protocol data unit that is delivered by the wireless device to a last sequential delivery protocol stack, or the second count value is the wireless value.
  • the COUNT value of the received PDCP PDU is the state variable RX_DELIV+1 maintained by the wireless device
  • the PDCP SDU corresponding to the PDCP PDU of the In-Order Delivery that is stored in the upper layer protocol stack is initiated (the structure of one PDCP PDU includes Head Header Part and PDCP SDU) and the operation of deleting the COUNT value of the recorded PD-PDU of Out-of-Order Delivery.
  • acquiring the first count value of the first protocol data unit includes:
  • the first count value is determined according to the sequence number SN of the first protocol data unit and the superframe number HFN of the first protocol data unit.
  • the COUNT value of the PDCP PDU is determined by the above process.
  • the method further includes :
  • the method further includes:
  • the service data unit corresponding to the first protocol data unit is stored in a receiving buffer
  • the service data unit corresponding to the first protocol data unit is delivered to an upper protocol stack, and the first count value is recorded.
  • the wireless device can determine different operations for the PDCP PDU of the In-Order Delivery and the PDCP PDU of the Out-of-Order Delivery, respectively.
  • a method of processing data is provided, the method being applied to a wireless device, the method comprising:
  • the first timer is turned on by the wireless device after receiving the protocol data unit whose count value is the first count value, and then performing the following steps:
  • the first value set includes the wireless device receiving and storing Receiving a count value of the service data unit corresponding to the sequentially delivered protocol data unit in the cache, the third value set including the non-sequential delivery received by the wireless device and submitted by the wireless device to the upper layer protocol stack a count value of the service data unit corresponding to the protocol data unit, wherein the fifth value set formed by the second value set and the fourth value set is a continuous count value area counted from the first count value segment.
  • the first timer is a timer t-Reordering.
  • the above procedure defines the operation of the timer t-Reordering when the Expiration is exceeded.
  • a PDCP PDU of Out-of-Order Delivery is delivered in an orderly manner
  • the COUNT values of the two PDCP PDUs are considered, and the DRB reception operation (Receive Operation) and the PD-based PDU with only In-Order Delivery are guaranteed.
  • the uniformity of DRB's Receive Operation enhances the compatibility of wireless devices with data processing.
  • the method further includes :
  • the second calculated value is a count value of a service data unit corresponding to a protocol data unit that is delivered by the wireless device to a last sequential delivery protocol stack, or the second count value is the wireless value.
  • the wireless device performs any of the above possible implementations by using a PDCP layer of the wireless device; the protocol data unit is a PDCP packet data unit PDU.
  • the foregoing method may be a process performed by a wireless device, such as a UE or a network device, at its PDCP layer.
  • a wireless device for performing the method of any of the first aspect or the first aspect of the first aspect.
  • the wireless device comprises means for performing the method of any of the first aspect or the first aspect of the first aspect described above, as follows:
  • a wireless device comprising:
  • a receiving module configured to receive a first protocol data unit
  • a processing module configured to acquire a first count value of the first protocol data unit
  • the processing module is further configured to: if the first count value matches the second count value maintained by the wireless device, deliver the service data unit corresponding to the second value set in the first value set to the upper layer protocol stack, Deleting a fourth set of values in the third set of values, the first set of values comprising a count value of service data units corresponding to the sequentially delivered protocol data units received by the wireless device and stored in the receive buffer,
  • the third set of values includes a count value of the service data unit corresponding to the unsorted protocol data unit received by the wireless device and submitted to the upper layer protocol stack by the wireless device, wherein the second set of values is
  • the fifth set of values consisting of the fourth set of values is a continuous count value segment counted from the first count value.
  • the second count value is a count value of a service data unit corresponding to a protocol data unit that is delivered by the wireless device to the last sequential delivery protocol stack. a larger of the maximum values of the service data unit corresponding to the non-scheduled protocol data unit deleted by the wireless device,
  • the first count value matches the second count value maintained by the wireless device, including:
  • the first count value is equal to the second count value plus one.
  • the wireless device according to the embodiment 10 or 11, wherein the processing module is specifically configured to:
  • the first count value is determined according to the sequence number SN of the first protocol data unit and the superframe number HFN of the first protocol data unit.
  • the processing module is further configured to:
  • the processing module is further configured to:
  • the service data unit corresponding to the first protocol data unit is stored in a receiving buffer
  • the service data unit corresponding to the first protocol data unit is delivered to an upper protocol stack, and the first count value is recorded.
  • the wireless device according to any one of embodiments 10 to 14, wherein the wireless device performs any one of the embodiments 10 to 14 by a packet data convergence protocol PDCP layer of the wireless device.
  • the step of: the first protocol data unit is a PDCP packet data unit PDU.
  • a wireless device for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.
  • the wireless device includes means for performing the method in any of the possible implementations of the second aspect or the second aspect described above, as follows:
  • a wireless device comprising:
  • a processing module if the first timer expires, the first timer is turned on by the wireless device after receiving the protocol data unit whose count value is the first count value, for performing the following steps;
  • the first value set includes the wireless device receiving and storing Receiving a count value of the service data unit corresponding to the sequentially delivered protocol data unit in the cache, the third value set including the non-sequential delivery received by the wireless device and submitted by the wireless device to the upper layer protocol stack a count value of the service data unit corresponding to the protocol data unit, wherein the fifth value set formed by the second value set and the fourth value set is a continuous count value area counted from the first count value segment
  • the data unit is a PDCP Packet Data Unit PDU.
  • a wireless device comprising a processor, a memory, and a transceiver.
  • the processor is coupled to the memory and the transceiver.
  • the memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a wireless device comprising a processor, a memory, and a transceiver.
  • the processor is coupled to the memory and the transceiver.
  • the memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.
  • a computer readable storage medium storing a program causing a wireless device to perform the first aspect described above, and processing data in any of the various implementations thereof Methods.
  • a computer readable storage medium storing a program causing a wireless device to perform the second aspect described above, and processing the data in any of the various implementations thereof Methods.
  • a chip comprising: a processing module and a communication interface, the processing module being configured to perform the method of processing data according to any of the above first aspects, and various implementation manners thereof.
  • the chip further includes a storage module, where the storage module is configured to store an instruction, the processing module is configured to invoke an instruction stored by the storage module, and execute an instruction stored in the storage module.
  • the invocation of the processing module causes the processing module to perform the method of processing data in any of the first aspects described above, and various implementations thereof.
  • a chip comprising: a processing module and a communication interface, wherein the processing module is configured to perform the method of processing data according to any of the above second aspects, and various implementation manners thereof.
  • the chip further includes a storage module, where the storage module is configured to store an instruction, the processing module is configured to invoke an instruction stored by the storage module, and execute an instruction stored in the storage module.
  • the invocation of the processing module causes the processing module to perform the method of processing data in any of the second aspects described above, and various implementations thereof.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the method of the first or second aspect or any possible implementation thereof.
  • FIG. 1 is a schematic diagram of a scenario in which an embodiment of the present application is applied.
  • FIG. 2 is a schematic diagram of the architecture of a dual connectivity wireless protocol stack.
  • Figure 3 is a diagram of a wireless protocol architecture for dual connectivity.
  • Figure 4 is a diagram of another wireless protocol architecture for dual connectivity.
  • FIG. 5 is a schematic flowchart of a method of processing data according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a protocol stack in accordance with an embodiment of the present application.
  • Figure 7 is a schematic illustration of an example in accordance with an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method of processing data according to another embodiment of the present application.
  • FIG. 9 is a schematic diagram of an example in accordance with another embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a wireless device in accordance with an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a wireless device in accordance with another embodiment of the present application.
  • FIG. 12 is a structural block diagram of a wireless device according to an embodiment of the present application.
  • the technical solution of the embodiment of the present application can be applied to a wireless communication system, for example, a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, and an LTE time division duplex (Time Division Duplex).
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • Time Division Duplex Time Division Duplex
  • TDD Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiMAX Worldwide Interoperability for Microwave Access
  • 5G future 5th Generation
  • New Radio, NR New Radio
  • LTE next-generation scenarios Wireless Local Area Network (WLAN) scenarios
  • Bluetooth communications and communication systems defined by the 3rd Generation Partnership Project (3GPP) are medium-sized.
  • 3GPP 3rd Generation Partnership Project
  • FIG. 1 is a schematic diagram of a scenario in which an embodiment of the present application is applied.
  • the core network can be included in the new air interface scenario, such as NGC/5GC or EPC, and the access network of the new air interface.
  • the embodiments of the present application are collectively referred to as a core network and an access network.
  • the functional entities in the new air interface scenario are mainly network devices, and user devices connected to network devices in the new air interface access network, such as user equipment 1 shown in FIG.
  • a relay device, and a user device connected to the relay such as the user device 2 shown in FIG. 1, may also be included.
  • the relay device and the network device establish a connection through the link 2, so the relay device can also be regarded as a user device with respect to the network device; the relay device and the user device 2 establish a connection through the link 3, and thus User equipment, relay equipment can also be regarded as a network equipment. Therefore, those skilled in the art may understand that the network device in the embodiment of the present application may also include a relay device, and the user equipment in the embodiment of the present application may also include a relay device.
  • the network device may specifically be a gNB, a new radio eNB, a Transmission And Reception Point (TRP), a macro base station, a micro base station, a high frequency base station, and a cloud radio access network (Cloud Radio Access Network, CRAN)
  • the wireless controller in the scenario, or the network device can be a relay station, an access point, an in-vehicle device, a wearable device, a network device in a future 5G network, a network device in a future evolved PLMN network, an LTE macro or micro Any one or a combination of the eNB, the customer-premises equipment (CPE), the WLAN access point (AP), the WLAN group owner (GO), and the like, for example,
  • the network device may be a gNB, and the function of the network device in the embodiment of the present application is completed by the gNB, or the network device is a combination of the gNB and the TRP, and the resource configuration function of the network device in the embodiment of the present application is completed by the
  • the user equipment UE in the embodiment of the present application may be a mobile phone, a tablet, a smart car, a sensing device, an IOT device, a CPE, a relay base station, a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, Remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication devices, user agents or user devices.
  • the user equipment can also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the 5G communication system is called “super 4G network” or “post-long-term evolution LTE system” or “new air interface NR”.
  • a bearer is further established, such as a Signaling Radio Bearer (SRB) or a Data Radio Bearer. , DRB).
  • RRC Radio Resource Control
  • the DRB may be any one of a primary cell group (MCG) Bearer, a secondary cell group (SCG) Bearer, an MCG split bearer (segmented bearer), and an SCG split bearer.
  • FIG. 2 shows a schematic diagram of the architecture of a dual connectivity DC wireless protocol stack.
  • the protocol stack includes at least a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • the PDCP layer of the primary network node (MN) and the RLC layer of the secondary network node (SN) are connected through the X2 port.
  • a Service Data Adaptation Protocol (SDAP) layer may also be included.
  • SDAP Service Data Adaptation Protocol
  • the functional entity corresponding to the PDCP layer is a PDCP entity, and so on.
  • the PDCP layer processes radio resource control RRC messages on the control plane and Internet Protocol (IP) on the user plane.
  • IP Internet Protocol
  • the PDCP layer can perform header compression and encryption on the IP data packet PDCP Service Data Unit (SDU), and then add a PDCP header to form a PDCP. Protocol Data Unit (PDU), and then deliver the PDCP PDU to the RLC layer.
  • SDU IP Data Unit
  • PDU Protocol Data Unit
  • the PDCP layer also provides sequential submission and repeated packet detection to the upper layer. To this end, there is a Sequence Number (SN) in the PDCP header in each PDCP PDU.
  • SN Sequence Number
  • the number of functional entities included in the protocol stack is different.
  • a dual connectivity (DC) scenario two RLC entities and two MACs are established on each DRB on the UE side. entity.
  • a specific bearer in a DC scenario can be established into three different bearer types: MCG bearer, SCG bearer, and split bearer.
  • Multi-RAT Dual Connectivity defines different multi-connection types, such as E-UTRA-NR Dual Connectivity (EN-UTRA-NR Dual Connectivity, EN- DC), NGEN-DC Dual Connectivity (NG-DC), NE-DC (NE-DC), and defines four Bearer types: MCG bearer, SCG bearer, MCG split bearer and SCG split bearer.
  • a DRB can be configured as one of these four types.
  • Figure 3 shows the wireless protocol architecture of the four bearers in the EN-DC scenario.
  • the corresponding bearer types in the MN include: MCG bearer, MCG split bearer; the corresponding bearer types in the SN include: SCG bearer, SCG split bearer.
  • the MN includes: an LTE/NR PDCP layer, an NR PDCP layer, an LTE RLC layer, and an LTE MAC layer.
  • the SN includes: an NR PDCP layer, an NR RLC layer, and an NR MAC layer.
  • the NR PDCP layer of the MN and the NR RLC layer of the SN are connected through the X2 port.
  • the LTE RLC layer of the MN and the NR PDCP layer of the SN are connected through the X2 port.
  • Figure 4 shows the wireless protocol architecture of the four bearers in the NGEN-DC scenario and the NE-DC scenario.
  • the corresponding bearer types in the MN include: MCG bearer, MCG split bearer; the corresponding bearer types in the SN include: SCG bearer, SCG split bearer.
  • the MN includes: an SDAP layer, an LTE/NR PDCP layer, an NR PDCP layer, a MN RLC layer, and a MN MAC layer.
  • the SN includes: an SDAP layer, an NR PDCP layer, an LTE/NR PDCP layer, an SN RLC layer, and an SN MAC layer.
  • the NR PDCP layer of the MN and the SN RLC layer of the SN are connected through the Xn port.
  • the MN RLC layer of the MN and the NR PDCP layer of the SN are connected through the X2 port.
  • the receiving device after receiving data, performs data processing such as decryption, integrity check, reordering, and the like at the PDCP layer.
  • the PDCP layer is reordered and then delivered to the upper layer stack of the upper layer protocol.
  • the PDCP PDU delivery mechanism is called in-order delivery of In-Order Delivery.
  • the PDCP layer may not be reordered.
  • This PDCP PDU delivery mechanism is called out-of-order delivery.
  • a Quality of Service (QoS) flow that is applied to web browsing may include a Transmission Control Protocol (TCP) stream, a User Datagram Protocol (UDP) packet, and a real-time.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • RTP Real-time Transport Protocol
  • RTP Real-time Transport Protocol
  • the TCP stream and the RTP data packet occupy a large proportion, so the QoS flow can be configured in an In-Order Delivery DRB.
  • some UDP packets (such as DNS requests) or RTP control packets need to be transmitted to the corresponding processing unit of the peer end with a low delay. If these packets also need to be cached in the PDCP layer and follow the reordering delivery rules, it will result in some Some lost TCP packets or RTP packets affect the user, resulting in a large reordering delay, which in turn affects the user experience.
  • the solution provided by the embodiments of the present application does not specifically limit a radio bearer. It can be applied not only to the data radio bearer DRB but also to the signal radio bearer SRB. Specifically, when there are both an In-Order Delivery PDCP PDU and an Out-of-Order Delivery PDCP PDU in an SRB, the receiving operation can also be referred to.
  • the solution provided by the embodiments of the present application does not specifically limit a radio bearer. It can be applied not only to the data radio bearer DRB but also to the signal radio bearer SRB.
  • the embodiment of the present application provides a processing mechanism for a DRB of a PDCP PDU that has both In-Order Delivery and an Out-of-Order Delivery PDCP PDU.
  • FIG. 5 shows a schematic flow diagram of a method 500 of processing data in accordance with an embodiment of the present application.
  • the method 500 can be performed by a wireless device, which can be a user equipment UE or a network device as described above.
  • the wireless device may be a receiving device in a new air interface scenario.
  • the method 500 includes:
  • the first protocol data unit may be a PDCP PDU.
  • a wireless device is a UE as an example.
  • a corresponding PDCP entity is established within the UE.
  • the RLC entity and the MAC entity have different configurations.
  • the RLC entity and the MAC entity are respectively configured for the MN and the SN; the PDCP duplication transmission is applied to the CA scenario, and the corresponding RLC entities are established for different CCs, and the RLC entities are connected to the same MAC entity.
  • FIG. 6 shows a schematic diagram of a protocol stack in accordance with an embodiment of the present application. As shown in FIG.
  • the protocol stack is sequentially: an upper layer protocol stack, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. It should be understood that the protocol stack in FIG. 6 is applicable to the data receiving process of the UE or network device.
  • an RLC entity and a MAC entity are taken as an example, but the embodiments of the present application are not limited.
  • the PHY layer performs corresponding processing, and then delivers the data packet to the MAC layer, performs corresponding processing at the MAC layer, and then submits the data to the RLC layer for corresponding processing at the RLC layer. Then submit it to the PDCP layer to get a PDCP PDU.
  • the first protocol data unit received by the network device may be received by the receiver, or may be forwarded by the receiver on the device other than the wireless device. Forwarding to the wireless device in a wired or wireless manner, for example, the wireless device is a CU, and the received PDCP PDU is forwarded by the DU and then forwarded through the F1 interface.
  • the UE after receiving the PDCP PDU, the UE first determines at the PDCP layer whether the PDCP PDU is an In-Order Delivery PDU or an Out-of-Order transmitted PDU.
  • the UE may determine by using indication information of a header header portion of the PDCP PDU. For example, it is determined by the value of the corresponding field of the Header part.
  • I/O In-Order or Out-of-Order
  • the UE may further determine, by using the indication information in the SDU corresponding to the PDCP PDU, for example, by using indication information in the SDAP Header of the SDU, for example, by using a QoS Flow ID in the SDAP Header of the SDU or The Session ID or a domain (such as an I/O domain) dedicated to In-Order Delivery or Out-of-Order Delivery is determined.
  • the UE may also determine by receiving an indication message of the sender device. For example, when the sender device wants to send the PDCP PDU of the Out-of-Order Delivery, it first indicates to the UE by using a specific RRC message or MAC CE or DCI. After receiving the UE, the UE may determine that the subsequent PDCP PDU is an Out-of-Delivery PDCP PDU. Further, after the sender device completes the transmission of the Out-of-Delivery PDCP PDU, the device may send a specific RRC message or a MAC CE or a DCI to indicate to the UE that the PD-CP PDU has been sent out of the Out-of-Delivery. The transmitted PDCP PDU is a PDCP PDU of In-Order Delivery.
  • the SN number of the PDCP PDU is also indicated in the PDCP PDU.
  • the UE may determine the COUNT value of the PDCP PDU according to the SN number of the PDCP and the current Hyper Frame Number (HFN) number.
  • COUNT SN
  • the first count value may be a COUNT value of a PDCP PDU.
  • the first count value may be directly obtained, or may be obtained by calculation, which is not limited thereto.
  • S520 includes:
  • the first count value is determined according to the sequence number SN of the first protocol data unit and the superframe number HFN of the first protocol data unit.
  • the method may further include:
  • the service data unit corresponding to the first protocol data unit is stored in a receiving buffer
  • the service data unit corresponding to the first protocol data unit is delivered to an upper protocol stack, and the first count value is recorded.
  • the PDCP PDU is a PDU of the In-Order Delivery
  • the PDCP SDU obtained by processing the PDCP PDU is stored in the receiving buffer.
  • the receiving buffer may specifically be a receiving buffer of a PDCP layer. If the PDCP PDU is a UR-of-Order-delivered PDU, the PDCP SDU obtained by processing the PDCP PDU is transmitted to an upper layer (upper layer), and the COUNT value of the PDCP PDU is recorded.
  • the upper layer protocol stack upper layer described in the embodiment of the present application is a protocol stack of the upper layer of the PDCP layer, such as the SDAP layer or the IP layer or the RRC layer, and the like.
  • the service data unit corresponding to the second value set in the first value set is delivered to the upper layer protocol stack, and the third value set is Deleting a fourth set of values, the first set of values comprising a count value of a service data unit corresponding to the sequentially delivered protocol data unit received by the wireless device and stored in a receive buffer, the third set of values comprising Determining, by the wireless device, a count value of a service data unit corresponding to the unsorted protocol data unit received by the wireless device and having been delivered to the upper layer protocol stack, wherein the second value set and the fourth value set
  • the fifth set of values formed is a continuous count value segment counted from the first count value.
  • the second count value is a count value of the service data unit corresponding to the last sequential delivery protocol data unit that the wireless device submits to the upper layer protocol stack, and the non-sequence of the wireless device deletion The larger of the maximum values in the count values of the service data units corresponding to the submitted protocol data unit,
  • the first count value is matched with the second count value maintained by the wireless device, specifically:
  • the first count value is equal to the second count value plus one.
  • the second count value may be a count value of a service data unit corresponding to a protocol data unit that is delivered by the wireless device to the last sequential protocol stack, or the second count value may also be The maximum value of the count value of the service data unit corresponding to the non-sequentially delivered protocol data unit deleted by the wireless device.
  • RX_NEXT may also be named by other names.
  • the embodiment of the present application is only described by taking RX_NEXT as an example, and is not limited.
  • the UE maintains a state variable RX_DELIV at the PDCP layer, and the RX_DELIV is a count value, that is, the second count value indicates that the PDCP PDU of the Out-of-Order Delivery that has been deleted to the upper layer protocol stack has been deleted.
  • the COUNT value associated with the PDCP SDU is the highest of the COUNT values associated with the PDCP SDU corresponding to the PDCP PDU that has been submitted to the In-Order Delivery of the upper protocol stack.
  • the cached PDCP SDU corresponding to the COUNT value is delivered to the upper protocol stack, and all of them are The recorded COUNT value that has been submitted to the upper layer protocol stack PDCP SDU is deleted.
  • RX_DELIV may also be named by other names.
  • the embodiment of the present application is only described by taking RX_DELIV as an example, and is not limited thereto.
  • the method 500 further includes:
  • the UE updates the RX_DELIV value to the COUNT value associated with the PDCP SDU that is submitted to the upper layer protocol stack and the maximum value of the COUNT value that is deleted this time.
  • the wireless device receives the first protocol data unit and determines the first count value of the first protocol data unit, when the first count value matches the second count value maintained by the wireless device. And the service data unit corresponding to the second set of values in the first set of values is delivered to the upper layer stack, and the fourth set of values in the third set of values is deleted, the first set of values including the wireless device receiving and storing a count value of the service data unit corresponding to the sequentially delivered protocol data unit in the receive buffer, the third set of values including the non-sequence of the wireless device record received by the wireless device and submitted to the upper layer protocol stack a count value of the service data unit corresponding to the submitted protocol data unit, wherein the fifth value set formed by the second value set and the fourth value set is a continuous count value counted from the first count value
  • the segment realizes the receiving operation of the protocol data unit that exists in both the protocol data unit and the non-sequential delivery. Enhance the user experience.
  • the UE receives the PDCP PDU for In-Order Delivery with COUNT values of 31, 33, and 38 and the PDCP PDU for Out-of-Order Delivery with COUNT values of 32 and 34.
  • the UE stores the SDU corresponding to the In-Order Delivery PDCP PDU in the receiving buffer, and delivers the SDU corresponding to the PDCP PDU of the Out-of-Order Delivery to the upper layer protocol stack, and records the corresponding COUNT values, that is, 32 and 34.
  • the UE When the UE receives a PDCP PDU with a COUNT value of 30, it satisfies the condition that the COUNT value is RX_DELIV+1. Thus, whether it is a PDCP PDU for In-Order Delivery or a PDCP PDU for Out-of-Order Delivery, an operation is triggered.
  • the PDCP PDU is an In-Order PDCP PDU as an example.
  • the UE stores the SDU corresponding to the PDCP PDU in the receiving buffer.
  • the foregoing operation process is specifically: the COUNT values 30, 31, and 33 corresponding to the PDCP PDUs of the stored In-Order Delivery from the RX_DELIV+1, that is, the corresponding second value set, and the recorded Out-of-Order Delivery
  • the PDCP PDU corresponds to the COUNT values 32 and 34, that is, the fourth set of values, consisting of consecutive COUNT value segments.
  • the COUNT value segment of 30 to 34 starting from 30 shown in FIG. 7 corresponds to the fifth set of values.
  • the SDU corresponding to the PDCP PDU of the In-Order Delivery stored therein that is, the PDCP SDU corresponding to the COUNT values 30, 31, and 33 shown in FIG.
  • the UE submits it to the upper protocol stack; for the Out-record recorded therein
  • the COUNT value corresponding to the PDCP PDU of the-Order, that is, 32 and 34 shown in FIG. 7, is deleted.
  • the value of RX_DELIV is updated, and its value is updated to be equal to the maximum value of the COUNT value segment of the current process, that is, 34, that is, the second count value is updated to the maximum value of the fifth value set. .
  • the method for processing data in the embodiment of the present application considers the COUNT value of the PDCP PDU of the In-Order Delivery and the PDCP PDU of the Out-of-Order Delivery, so that the PDCP layer pair of the receiver device has both In-Order
  • the PDCP PDU of the delivery has the receiving operation of the PDCP PDU of the Out-of-Order Delivery.
  • FIG. 8 shows a schematic flowchart of a method 800 for processing data according to another embodiment of the present application. As shown in FIG. 8, the method 800 includes:
  • the first timer is started by the wireless device after receiving the protocol data unit whose count value is the first count value, and then performing the following steps:
  • the value of the first timer may be configured by a network side, such as a network device configuration or a core network configuration, or may be determined by the UE.
  • the UE can maintain a timer, such as a timer t-Reordering.
  • a timer t-Reordering When the timer t-Reordering is not running, once at least one PDCP SDU corresponding to the PDCP PDU of the In-Order Delivery stored in the receiving buffer or any recorded Out-of-Order Delivery that has been submitted to the upper protocol stack occurs.
  • the COUNT value associated with the PDCP SDU corresponding to the PDCP PDU starts the timer t-Reordering, and records the COUNT value that triggers the timer t-Reordering as RX_REORD, that is, the first count value.
  • the timing is stopped and reset.
  • the service data unit corresponding to the sequentially delivered protocol data unit whose stored count value is smaller than the first count value is delivered to the upper layer protocol stack.
  • the service data unit corresponding to the second value set in the first value set is delivered to the upper layer protocol stack, and the fourth value set in the third value set is deleted, where the first value set includes the wireless device receiving a count value of the service data unit corresponding to the sequentially delivered protocol data unit stored in the receive buffer, the third set of values including the non-press received by the wireless device and received by the wireless device and submitted to the upper layer protocol stack a count value of the service data unit corresponding to the protocol data unit that is delivered, wherein the fifth value set formed by the second value set and the fourth value set is a continuous count counted from the first count value Value section.
  • the method further includes:
  • the second calculated value may be a count value of a service data unit corresponding to a protocol data unit that is delivered by the wireless device to the last sequential protocol stack, or the second count value may also be The maximum value of the count value of the service data unit corresponding to the non-sequentially delivered protocol data unit deleted by the wireless device.
  • the UE submits all PDCP SDUs corresponding to the PDCP PDUs of the In-Order Delivery whose COUNT value is smaller than RX_REORD to the upper protocol stack, and all the records are delivered to the upper protocol stack.
  • the COUNT value of the COUNT value associated with the PDCP SDU corresponding to the PDCP PDU of the Out-of-Order Delivery is less than the COUNT value of the RX_REORD.
  • the COUNT value associated with the PDCP SDU corresponding to the PDCP PDU of the In-Order Delivery stored in the current receive buffer starting from RX_REORD, that is, the second set of values, and the recorded Out-of-submitted to the upper protocol stack The COUNT value associated with the PDCP SDU corresponding to the PDCP PDU of the Order Delivery, that is, the fourth set of values, the consecutive COUNT value segments, that is, the fifth set of values, the storage of all the COUNT values corresponding thereto
  • the PDCP SDU corresponding to the PDCP PDU of the In-Order Delivery is delivered to the upper layer protocol stack, and the COUNT value associated with the PDCP SDU corresponding to the PDCP PDU of the Out-of-Order Delivery of all the records that have been submitted to the upper protocol stack is deleted. Further, the UE may update the RX_DELIV value to the COUNT value associated with the PDCP SDU that is submitted to the upper layer protocol stack and the maximum value of the COUNT value
  • the wireless device when determining that the first counter expires, the wireless device submits the service data unit corresponding to the sequentially delivered protocol data unit whose stored count value is smaller than the first count value to the upper layer protocol stack; Deleting the count value of the service data unit corresponding to the unsorted protocol data unit that has been submitted to the upper layer protocol stack that is smaller than the first count value; and the service corresponding to the second value set in the first value set
  • the data unit is submitted to the upper layer protocol stack, and the fourth value set in the third value set is deleted, and when the timer expires, the receiving of the protocol data unit that exists in the orderly delivery of the protocol data unit and the non-sequential delivery is realized. Operation helps to improve the user experience.
  • the COUNT value of the trigger timer t-Reordering is 38, that is, RX_REORD (corresponding to the first count value) is 38.
  • RX_REORD corresponding to the first count value
  • the UE still does not receive the COUNT value.
  • the UE initiates a receiving operation, where RX_DELIV is 34, corresponding to the second count value.
  • the SDU corresponding to the In-Order Delivery PDCP PDU stored therein is delivered to the upper layer protocol stack, and the COUNT value corresponding to the recorded PD-PDU of the Out-of-Order Delivery is deleted.
  • the UE does not have an SDU corresponding to the stored In-Order Delivery PDCP PDU, the UE does not perform the corresponding operation, and the UE deletes the COUNT value 36.
  • the COUNT value corresponding to the COUNT value (corresponding to the second value set) corresponding to the stored In-Order Delivery PDCP PDU from the RX_REORD and the Recorded Out-of-Order Delivery PDCP PDU (corresponding to The fourth set of values comprises a continuous COUNT value segment (corresponding to the fifth set of values), that is, a COUNT value segment of 38 to 40 starting from 38 as shown in FIG.
  • the method for processing data in the embodiment of the present application considers the COUNT value of the PDCP PDU of the In-Order Delivery and the PDCP PDU of the Out-of-Order Delivery when the timer t-Reordering expires, thereby implementing the receiver device.
  • the PDCP layer performs a receiving operation on the DRB of both the In-Order Delivery PDCP PDU and the Out-of-Order Delivery PDCP PDU.
  • the count value is illustrated by taking the COUNT value as an example.
  • the foregoing counting value may also use other counting values, such as SN, or HFN, etc., which is not limited in this embodiment of the present application.
  • FIG. 10 shows a schematic block diagram of a wireless device 1000 in accordance with an embodiment of the present application.
  • the wireless device 1000 is configured to perform the steps of the aforementioned method 500 or related examples.
  • each module in the wireless device 1000 may be implemented by software.
  • the wireless device 1000 can be installed in a general purpose computer device. As shown in FIG. 10, the wireless device 1000 includes:
  • the receiving module 1010 is configured to receive the first protocol data unit.
  • the processing module 1020 is configured to acquire a first count value of the first protocol data unit.
  • the processing module 1020 is further configured to: if the first count value matches a second count value maintained by the wireless device,
  • the first value set includes the wireless device receiving and storing Receiving a count value of the service data unit corresponding to the sequentially delivered protocol data unit in the cache, the third value set including the non-sequential delivery received by the wireless device and submitted by the wireless device to the upper layer protocol stack a count value of the service data unit corresponding to the protocol data unit, wherein the fifth value set formed by the second value set and the fourth value set is a continuous count value area counted from the first count value segment.
  • the second count value is a count value of a service data unit corresponding to a protocol data unit that is delivered by the wireless device to the last sequential delivery protocol stack, and a non-sequential delivery of the wireless device deletion The larger of the maximum values of the service data unit corresponding to the protocol data unit,
  • the first count value is matched with the second count value maintained by the wireless device, specifically:
  • the first count value is equal to the second count value plus one.
  • processing module 1020 is specifically configured to:
  • the first count value is determined according to the sequence number SN of the first protocol data unit and the superframe number HFN of the first protocol data unit.
  • the processing module 1020 further uses to:
  • the wireless device performs the steps in the foregoing method by using a packet data convergence protocol PDCP layer of the wireless device; the first protocol data unit is a PDCP packet data unit PDU.
  • the processing module 1020 is further configured to:
  • the service data unit corresponding to the first protocol data unit is stored in a receiving buffer
  • the service data unit corresponding to the first protocol data unit is delivered to an upper protocol stack, and the first count value is recorded.
  • processing module in the embodiment of the present application may be implemented by a processor, and the receiving module may be implemented by a receiver.
  • FIG. 11 shows a schematic block diagram of a wireless device 1100 in accordance with an embodiment of the present application.
  • the wireless device 1100 is configured to perform the steps of the aforementioned method 800 or related examples.
  • each module in the wireless device 1100 may be implemented by software.
  • the wireless device 1100 can be installed in a general purpose computer device. As shown in FIG. 11, the wireless device 1100 includes:
  • the processing module 1110 if the first timer expires, the first timer is turned on by the wireless device after receiving the protocol data unit whose count value is the first count value, for performing the following steps:
  • the first value set includes the wireless device receiving and storing Receiving a count value of the service data unit corresponding to the sequentially delivered protocol data unit in the cache, the third value set including the non-sequential delivery received by the wireless device and submitted by the wireless device to the upper layer protocol stack a count value of the service data unit corresponding to the protocol data unit, wherein the fifth value set formed by the second value set and the fourth value set is a continuous count value area counted from the first count value segment.
  • the processing module 1110 further uses to:
  • the wireless device performs the steps in the foregoing method by using a PDCP layer of the wireless device; the protocol data unit is a PDCP packet data unit PDU.
  • processing module in the embodiment of the present application may be implemented by a processor.
  • FIG. 12 shows a schematic structural diagram of a wireless device according to an embodiment of the present application.
  • the illustrated wireless device includes a processor 1201, a memory 1202, for storing corresponding programs and data for the processor 1201 to invoke to implement the corresponding functions.
  • the processor 1201 can invoke the programs and data stored in the memory to implement the functions performed by the wireless device in the method embodiments of the present application.
  • the wireless device may further include a transmitter 1203 and a receiver 1204 for transmitting and receiving data.
  • the first protocol data unit received by the wireless device may be received by a receiver 1204 on the wireless device.
  • the first protocol data unit received by the wireless device may be forwarded by a receiver on another device outside the wireless device (can be forwarded by wire or wirelessly)
  • the wireless device is a CU, and the received PDCP PDU is forwarded through the DU and then forwarded through the F1 interface.
  • the wireless device is capable of performing any of the methods performed by the wireless device in embodiments of the present application.
  • the method disclosed in the foregoing embodiment of the present application may be applied to a processor or implemented by a processor.
  • the processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or the like.
  • Programming logic device discrete gate or transistor logic device, discrete hardware component, system chip (SoC), central processor unit (CPU), or network processor (Network) Processor, NP
  • SoC system chip
  • CPU central processor unit
  • N Network processor
  • DSP digital signal processing circuit
  • MCU Micro Controller Unit
  • PLD Programmable Logic Device
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read only memory or an electrically erasable programmable memory, a register, etc.
  • RAM random access memory
  • ROM read-only memory
  • programmable read only memory or an electrically erasable programmable memory
  • register etc.
  • the storage medium is located in the memory, and the processor reads the instructions in the memory and combines the hardware to complete the steps of the above method.
  • the memory referred to in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read only memory ROM, a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), an electrically erasable programmable read only memory. (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory can be a random access memory RAM that acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • Synchronous DRAM synchronous dynamic random access memory
  • SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM direct memory bus random access memory
  • memories described herein are intended to comprise, without being limited to, these and any other suitable types of memory.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application.
  • the implementation of the examples constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk, and the like, which can store program codes.

Landscapes

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

Abstract

本申请提供了一种处理数据的方法和设备，该方法包括：获取第一协议数据单元的第一计数值；若第一计数值与第二计数值匹配，将第一数值集合中第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，第一数值集合包括无线设备接收缓存中按序递交的协议数据单元对应的计数值，第三数值集合包括无线设备已递交到上层协议栈的非按序递交的协议数据单元对应的计数值，其中，第二数值集合与第四数值集合组成的第五数值集合是从第一计数值开始连续计数的计数值区段。本申请实施例的处理数据的方法和设备，实现了对既存在按序递交的协议数据单元又存在非按序递交的协议数据单元的接收操作，有助于提升用户体验。

Description

处理数据的方法和设备
本申请要求于2017年9月30日提交中国专利局、申请号为201710940143.4、申请名称为“处理数据的方法和设备”的中国专利申请的优先权，以及于2017年9月8日提交中国专利局、申请号为201710803613.2、申请名称为“处理按序递交和非按序递交的PDCP PDU的方法和设备”的中国专利申请的优先权，它们的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种处理数据的方法和设备。
背景技术
第五代(5th Generation，5G)移动通信技术(mobile communication technology)是对第四代(the 4 Generation，4G)移动通讯技术的延伸。现有的演进的通用陆面无线接入网络(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)标准支持双连接(Dual Connectivity，DC)，即一个配置有多Rx/Tx的UE，在RRC_CONNECTED连接状态时，可以利用2个基站eNB调度的无线资源，其中，所述两个eNB通过X2接口上的非理想回程(non-ideal backhaul)相连接。这2个eNB一个作为主eNB(Master eNB，MeNB)，一个作为辅eNB(Secondary eNB，SeNB)。在DC中，接收方设备在接收数据后，会在分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层进行数据的处理，包括解密、完整性校验、重排序等操作。
在原有的LTE标准中，一个数据无线承载(Data Radio Bearer，DRB)对应一个PDCP实体(或称PDCP层)，PDCP层会对接收到的PDCP协议数据单元(PDCP Protocol Data Unit，PDCP PDU)进行重排序后再递交到较上层协议栈，这种传输机制称为按序传输(In-Order Delivery,或称为按序递交)。在3GPP针对NR的讨论中，已经确定了某些情况下PDCP层可以对接收到的PDCP PDU不进行重排序，直接将数据递交到较上层协议栈，即非按序传输机制(Out-of-Order Delivery)，或称为非按序递交。现有技术没有针对一个数据无线承载内(或者说一个PDCP实体内)既有按序递交的PDCP PDU，又有非按序递交的PDCP PDU的情况的解决方案。
发明内容
本申请提供一种处理数据的方法和设备，以提供一种针对一个数据无线承载内(或者说一个PDCP实体内)既有按序递交的PDCP PDU，又有非按序递交的PDCP PDU的情况的解决方案。
第一方面，提供了一种处理数据的方法，所述方法应用于无线设备，所述方法包括：
接收第一协议数据单元；
获取所述第一协议数据单元的第一计数值；
若所述第一计数值与所述无线设备维持的第二计数值匹配，
将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
在一些可能的实现方式中，所述无线设备通过所述无线设备的分组数据汇聚协议PDCP层执行上述任一可能的实现方式；所述第一协议数据单元为PDCP分组数据单元PDU。
前述的方法可以为无线设备，如UE或者网络设备，在其PDCP层执行的过程。
上述过程中针对一个数据无线承载(Data Radio Bearer，DRB)内既有按序递交In-Order Delivery的PDCP PDU，又有非按序递交Out-of-Order Delivery的PDCP PDU的情况时，在进行数据包接收和PDCP层向上层协议栈递交处理时，考虑了这两种PDCP PDU的COUNT值，保证了这种DRB的接收操作(Receive Operation)与只存在In-Order Delivery的PDCP PDU的DRB的Receive Operation的统一性，提升了无线设备对数据处理的兼容性。
在一些可能的实现方式中，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值，
其中，所述第一计数值与所述无线设备维持的第二计数值匹配，具体为：
所述第一计数值等于所述第二计数值加1。
具体地，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值，或者，所述第二计数值为所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值。
通过上述过程，当接收的PDCP PDU的COUNT值为无线设备维持的状态变量RX_DELIV+1时，启动向上层协议栈递交存储的In-Order Delivery的PDCP PDU对应的PDCP SDU(一个PDCP PDU的结构包括头Header部分和PDCP SDU)及删除记录的Out-of-Order Delivery的PDCP PDU的COUNT值的操作。
在一些可能的实现方式中，获取所述第一协议数据单元的第一计数值，包括：
根据所述第一协议数据单元的序列号SN和所述第一协议数据单元的超帧号HFN，确定所述第一计数值。
通过上述过程确定了PDCP PDU的COUNT值。
在一些可能的实现方式中，在将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述方法还包括：
将所述第二计数值更新为所述第五数值集合的最大值。
通过上述过程，实现了状态变量RX_DELIV的更新。
在一些可能的实现方式中，在所述接收所述第一协议数据单元之后，所述方法还包括：
若所述第一协议数据单元为按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元存储于接收缓存中；
若所述第一协议数据单元为按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元递交到上层协议栈，并记录所述第一计数值。
通过上述过程，无线设备可以确定对In-Order Delivery的PDCP PDU和Out-of-Order Delivery的PDCP PDU分别进行不同的操作过程。
第二方面，提供了一种处理数据的方法，所述方法应用于无线设备，所述方法包括：
如果第一计时器超期，所述第一计时器由所述无线设备在接收到计数值为第一计数值的协议数据单元后开启，则执行如下步骤：
将存储的计数值小于所述第一计数值的按序递交的协议数据单元对应的服务数据单元递交到上层协议栈(upper layer)；
将记录的小于所述第一计数值的已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值删除；
将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
可选地，所述第一定时器是定时器t-Reordering。
上述过程定义了定时器t-Reordering超期Expiration时的操作。在该过程中，针对一个数据无线承载(Data Radio Bearer，DRB)内既有按序递交In-Order Delivery的PDCP PDU，又有非按序递交Out-of-Order Delivery的PDCP PDU的情况时，在进行数据包接收和PDCP层向上层协议栈递交处理时，考虑了这两种PDCP PDU的COUNT值，保证了这种DRB的接收操作(Receive Operation)与只存在In-Order Delivery的PDCP PDU的DRB的Receive Operation的统一性，提升了无线设备对数据处理的兼容性。
在一些可能的实现方式中，在将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述方法还包括：
将所述无线设备上维持的第二计数值更新为所述第五数值集合的最大值，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值。
具体地，所述第二计算值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值，或者，所述第二计数值为所述无线设 备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值。
通过上述过程，实现了状态变量RX_DELIV的更新。
在一些可能的实现方式中，所述无线设备通过所述无线设备的PDCP层执行上述任一可能的实现方式；所述协议数据单元为PDCP分组数据单元PDU。
前述的方法可以为无线设备，如UE或者网络设备，在其PDCP层执行的过程。
第三方面，提供了一种无线设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该无线设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的模块，具体如下所示：
10、一种无线设备，其特征在于，包括：
接收模块，用于接收第一协议数据单元；
处理模块，用于获取所述第一协议数据单元的第一计数值；
所述处理模块，还用于若所述第一计数值与所述无线设备维持的第二计数值匹配，将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
11、根据实施例10所述的无线设备，其特征在于，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值，
其中，所述第一计数值与所述无线设备维持的第二计数值匹配，包括：
所述第一计数值等于所述第二计数值加1。
12、根据实施例10或11所述的无线设备，其特征在于，所述处理模块具体用于：
根据所述第一协议数据单元的序列号SN和所述第一协议数据单元的超帧号HFN，确定所述第一计数值。
13、根据实施例10至12中任一项所述的无线设备，其特征在于，在所述将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述处理模块还用于：
将所述第二计数值更新为所述第五数值集合的最大值。
14、根据实施例10至13中任一项所述的无线设备，其特征在于，在所述接收所述第一协议数据单元之后，所述处理模块还用于：
若所述第一协议数据单元为按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元存储于接收缓存中；
若所述第一协议数据单元为非按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元递交到上层协议栈，并记录所述第一计数值。
15、根据实施例10至14中任一项所述的无线设备，其特征在于，所述无线设备通过所述无线设备的分组数据汇聚协议PDCP层执行所述实施例10至14中任一项所述的步骤；所述第一协议数据单元为PDCP分组数据单元PDU。
第四方面，提供了一种无线设备，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该无线设备包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的模块，具体如下所示：
16、一种无线设备，其特征在于，包括：
处理模块，如果第一计时器超期，所述第一计时器由所述无线设备在接收到计数值为第一计数值的协议数据单元后开启，用于执行如下步骤；
将存储的计数值小于所述第一计数值的按序递交的协议数据单元对应的服务数据单元递交到上层协议栈；
将记录的小于所述第一计数值的已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值删除；
将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段
17、根据实施例16所述的无线设备，其特征在于，在将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述处理模块还用于：
将所述无线设备上维持的第二计数值更新为所述第五数值集合的最大值，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值。
18、根据实施例16或17所述的无线设备，其特征在于，所述无线设备通过所述无线设备的分组数据汇聚协议PDCP层执行所述实施例16或17所述的步骤；所述协议数据单元为PDCP分组数据单元PDU。
第五方面，提供了一种无线设备，所述无线设备包括处理器、存储器和收发器。处理器与存储器和收发器连接。存储器用于存储指令，处理器用于执行该指令，收发器用于在处理器的控制下与其他网元进行通信。所述处理器执行该存储器存储的指令时，该执行使得所述处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种无线设备，所述无线设备包括处理器、存储器和收发器。处理器与存储器和收发器连接。存储器用于存储指令，处理器用于执行该指令，收发器用于在处理器的控制下与其他网元进行通信。所述处理器执行所述存储器存储的指令时，该执行使得所述处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有程序，所述程序使得无线设备执行上述第一方面，及其各种实现方式中的任一种处理数据的方法。
第八方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有程 序，所述程序使得无线设备执行上述第二方面，及其各种实现方式中的任一种处理数据的方法。
第九方面，提供了一种芯片，包括：处理模块与通信接口，所述处理模块用于执行上述第一方面，及其各种实现方式中的任一种处理数据的方法。
在一些可能的实现方式中，所述芯片还包括存储模块，所述存储模块用于存储指令，所述处理模块用于调用所述存储模块存储的指令，并且对所述存储模块中存储的指令的调用使得所述处理模块执行上述第一方面，及其各种实现方式中的任一种处理数据的方法。
第十方面，提供了一种芯片，包括：处理模块与通信接口，所述处理模块用于执行上述第二方面，及其各种实现方式中的任一种处理数据的方法。
在一些可能的实现方式中，所述芯片还包括存储模块，所述存储模块用于存储指令，所述处理模块用于调用所述存储模块存储的指令，并且对所述存储模块中存储的指令的调用使得所述处理模块执行上述第二方面，及其各种实现方式中的任一种处理数据的方法。
第十一方面，提供了一种包含指令的计算机程序产品，其在计算机上运行时，使得计算机执行上述第一方面或第二方面或其任意可能的实现方式中的方法。
应理解，前述提供的各实施例的编号与后文的各实施例的编号并无明确的对应关系，仅为了此部分在表述上的方便。
附图说明
图1是应用本申请实施例的一个场景示意图。
图2是双连接的无线协议栈的架构的示意图。
图3是双连接的一个无线协议架构图。
图4是双连接的另一个无线协议架构图。
图5是根据本申请实施例的处理数据的方法的示意性流程图。
图6是根据本申请实施例的一个协议栈的示意图。
图7是根据本申请实施例的一个例子的示意图。
图8是根据本申请另一实施例的处理数据的方法的示意性流程图。
图9是根据本申请另一实施例的一个例子的示意图。
图10是根据本申请实施例的无线设备的示意性框图。
图11是根据本申请另一实施例的无线设备的示意性框图。
图12是根据本申请实施例的无线设备的结构框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于无线通信系统中，例如：长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、未来的第五代(5th Generation，5G)系统 或新空口(New Radio，NR)、LTE下一代场景、无线局域网(Wireless Local Area Network，WLAN)场景、蓝牙通信、第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)定义的通信系统等场景中等。为了描述方便，本申请实施例中以新空口场景为例进行说明。图1示出了应用本申请实施例的一个场景示意图。如图1所示，在新空口场景中可以包括核心网，比如NGC/5GC或者EPC，新空口的接入网。为了描述方便，本申请实施例统一称为核心网、接入网。新空口场景中的功能实体主要为网络设备，以及连接新空口接入网中的网络设备的用户设备，如图1所示的用户设备1。可选地，还可以包括中继设备，以及与中继连接的用户设备，如图1所示的用户设备2。其中，中继设备与网络设备通过链路2建立连接，因此相对于网络设备，中继设备也可以视为一种用户设备；中继设备与用户设备2通过链路3建立连接，因此相对于用户设备，中继设备也可以视为一种网络设备。因此，本领域的技术人员可以理解，本申请实施例所述的网络设备也可以包含中继设备，本申请实施例所述的用户设备也可以包含中继设备。其中，网络设备具体可以为gNB、新型无线电基站(New radio eNB)、传输点(Transmission And Reception Point，TRP)、宏基站、微基站、高频基站、云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备、未来5G网络中的网络设备、未来演进的PLMN网络中的网络设备、LTE宏或微eNB、用户驻地设备(Customer-premises equipment，CPE)、WLAN接入点(Access Point，AP)、WLAN组所有者(Group owner，GO)等中的任一种或者某几种的组合，例如，网络设备可以为一个gNB，由该gNB完成本申请实施例中网络设备所涉及的功能，或者，网络设备为gNB与TRP的组合，如由gNB完成本申请实施例中网络设备的资源配置功能，由TRP完成本申请实施例中网络设备的发送接收功能，本申请实施例并不以此为限。
本申请实施例中的用户设备UE可以为手机、平板、智能汽车、传感设备、IOT设备、CPE、中继基站、终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。用户设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。
5G通信系统被称为“超4G网络”或“后长期演进LTE系统”或者“新空口NR”。在LTE或者NR中，UE与基站建立无线资源控制(Radio Resource Control，RRC)连接之后，会进一步建立承载(bearer)，如信号无线承载(Signaling Radio Bearer，SRB)或者数据无线承载(Data Radio Bearer，DRB)。应用于双连接结构中时，DRB可以为主小区群(Master Cell Group，MCG)Bearer、辅小区群(Secondary Cell Group，SCG)Bearer、MCG Split bearer(分割承载)、SCG Split bearer中的任意一种。
对于单连接场景，UE与基站内部会针对每个DRB建立相应的协议栈。图2示出了双连接DC无线协议栈的架构的示意图。如图2所示，该协议栈至少包含分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制(Radio Link  Control，RLC)层、介质访问控制(Medium Access Control，MAC)层。主网络节点(Master Node，MN)的PDCP层与次网络节点(Secondary Node，SN)的RLC层通过X2口连接。在NR中，还可以包含服务数据适应协议(Service Data Adaptation Protocol，SDAP)层。该协议栈中的各个层对应有相应的功能实体，如PDCP层对应的功能实体为PDCP实体，依次类推。PDCP层处理控制平面上的无线资源控制RRC消息以及用户平面上的因特网协议包(Internet Protocol，IP)等。在用户平面上，PDCP层得到来自上层的IP数据分组后，可以对IP数据分组包PDCP服务数据单元(Service Data Unit，SDU)进行头压缩和加密，然后增加一个PDCP头(header)，形成PDCP协议数据单元(Protocol Data Unit，PDU)，然后把PDCP PDU递交到RLC层。PDCP层还向上层提供按序提交和重复分组检测功能，为此，在每一个PDCP PDU中PDCP head中都有一个序列号(Sequence Number，SN)。在不同的连接场景下，该协议栈中包含的各功能实体的数量不同，例如，在双连接(Dual Connectivity，DC)场景下，在UE侧每个DRB会建立2个RLC实体和2个MAC实体。在LTE中，DC场景中一个特定的承载(bearer)可以建立为3种不同的bearer类型：MCG bearer，SCG bearer和split bearer(分割承载)。
在NR中，多无线接入技术双连接(Multi-RAT Dual Connectivity，MR-DC)中定义了不同的多连接类型，如E-UTRA-NR双连接(E-UTRA-NR Dual Connectivity，EN-DC)，NGEN-DC双连接(NG-RAN E-UTRA-NR Dual Connectivity，NGEN-DC)，NE双连接(NR-E-UTRA Dual Connectivity，NE-DC)，并定义了4种Bearer类型：MCG bearer，SCG bearer，MCG split bearer和SCG split bearer。一个DRB可以被配置为这4种类型中的一种。
如图3所示为EN-DC场景下的4种bearer的无线协议架构。MN中对应的承载类型包括：MCG bearer，MCG split bearer；SN中对应的承载类型包括：SCG bearer，SCG split bearer。MN中包括：LTE/NR PDCP层，NR PDCP层，LTE RLC层，LTE MAC层。SN中包括：NR PDCP层，NR RLC层，NR MAC层。MN的NR PDCP层和SN的NR RLC层通过X2口连接。MN的LTE RLC层和SN的NR PDCP层通过X2口连接。
如图4所示为NGEN-DC场景和NE-DC场景下的4种bearer的无线协议架构。MN中对应的承载类型包括：MCG bearer，MCG split bearer；SN中对应的承载类型包括：SCG bearer，SCG split bearer。MN中包括：SDAP层，LTE/NR PDCP层，NR PDCP层，MN RLC层，MN MAC层。SN中包括：SDAP层，NR PDCP层，LTE/NR PDCP层，SN RLC层，SN MAC层。MN的NR PDCP层和SN的SN RLC层通过Xn口连接。MN的MN RLC层和SN的NR PDCP层通过X2口连接。
在各种DRB中，接收方设备在接收数据后，会在PDCP层进行数据的处理，如解密、完整性校验、重排序等。在原有的LTE标准中，PDCP层会进行重排序后再递交到上层协议栈upper layer，这种PDCP PDU的递交机制称为按序递交In-Order Delivery。在3GPP针对NR的讨论中，已经确定了某些情况下PDCP层可以不进行重排序，当数据到达后，不再在PDCP层的缓存存储，而是直接递交到上层协议栈进行处理，从而减小数据链路的时延。这种PDCP PDU的递交机制称为非按序递交Out-of-Order Delivery。
现有的Out-of-Order Delivery的粒度为每DRB，即整个DRB中的PDCP PDU的递交都是Out-of-Order Delivery。然而，在某些情况下，一个DRB内可能既存在In-Order Delivery的PDCP PDU又存在Out-of-Order Delivery的PDCP PDU。例如，在某个应用于网页浏览的服务质量(Quality of Service，QoS)流flow中可能包含传输控制协议(Transmission Control Protocol，TCP)流、用户数据报协议(User Datagram Protocol，UDP)包和实时传输协议(Real-time Transport Protocol，RTP)流，其中RTP流中还包含有RTP数据包和RTP控制包。其中，TCP流和RTP数据包占较大比例，因此可以将该QoS flow配置于一个In-Order Delivery的DRB中。但是，某些UDP包(如DNS请求)或者RTP控制包需要以较低的延迟传输到对端的相应处理单元，如果这些包也需要在PDCP层缓存并遵照重排序的递交规则，会导致被某些丢失的TCP数据包或者RTP数据包影响，造成较大的重排序时延，进而影响用户体验。
需要说明的是，本申请各实施例所提供的方案对无线承载(bearer)不作具体限定。不仅可以适用于数据无线承载DRB，也可以适用于信号无线承载SRB，具体即当一个SRB内既存在In-Order Delivery PDCP PDU又存在Out-of-Order Delivery PDCP PDU时，其接收操作也可以参考本申请各实施例所提供的方案。
针对上述问题，本申请实施例提供了一种针对既有In-Order Delivery的PDCP PDU又有Out-of-Order Delivery的PDCP PDU的DRB的处理机制。
图5示出了根据本申请实施例的处理数据的方法500的示意性流程图。所述方法500可以由无线设备执行，所述无线设备可以是前文所述的用户设备UE或网络设备。可选地，所述无线设备可以是新空口场景中的接收设备。如图5所示，所述方法500包括：
S510，接收第一协议数据单元。
可选地，所述第一协议数据单元可以为PDCP PDU。为了便于描述，这里以无线设备是UE为例进行描述。针对每一个DRB，在UE内部会建立对应的PDCP实体。对于不同的连接结构，RLC实体和MAC实体有不同的配置。例如，应用于DC场景，UE针对MN和SN分别建立RLC实体和MAC实体；应用于CA场景的PDCP duplication传输，针对不同的CC建立相应的RLC实体，这些RLC实体连接到同一个MAC实体。图6示出了根据本申请实施例的一个协议栈的示意图。如图6所示，该协议栈从依次是：上层协议栈，PDCP层，RLC层，MAC层，PHY层。应理解，图6中的协议栈适用于UE或网络设备的数据接收过程。在图6中，以一个RLC实体和一个MAC实体为例进行说明，但并不对本申请实施例构成限定。
具体而言，当UE从PHY层接收到无线消息后，在PHY层进行相应处理后将其中的数据包递交给MAC层，在MAC层进行相应处理后递交到RLC层，在RLC层进行相应处理后再递交到PDCP层，得到一个PDCP PDU。
需要说明的是，如果上述执行主体是网络设备，网络设备接收的第一协议数据单元可以通过接收器接收，还可以是通过所述无线设备外的其他设备上的接收器接收后转发(可以通过有线或无线的方式转发)给所述无线设备的，例如所述无线设备为CU，其接收到的PDCP PDU是通过DU接收后经过F1接口转发的。
进一步地，在接收到上述PDCP PDU后，UE在PDCP层首先确定该PDCP PDU是一个In-Order Delivery传输的PDU还是一个Out-of-Order传输的PDU。
可选地，UE可以通过该PDCP PDU的头Header部分的指示信息来确定。例如，通过Header部分的相应域的值来确定。比如，该PDU在Header部分设置有1比特bit的I/O(In-Order或Out-of-Order)域来指示，当I/O＝1时，表示该PDU为一个In-Order Delivery传输的包，当I/O＝0时，表示该PDU为一个Out-of-Order Delivery传输的包。应理解，这里只是示例性地描述指示信息对应的比特取值，并不对本申请实施例的保护范围构成限定。
可选地，UE还可以通过该PDCP PDU对应的SDU中的指示信息来确定，例如，通过该SDU的SDAP Header中的指示信息来确定，例如，通过该SDU的SDAP Header中的QoS Flow ID或者Session ID或者专门用来指示In-Order Delivery或者Out-of-Order Delivery的域(如I/O域)来确定。
可选地，UE还可以通过接收发送方设备的指示消息来确定。例如，当发送方设备要发送Out-of-Order Delivery的PDCP PDU时，先通过特定的RRC消息或者MAC CE或者DCI等方式向UE进行指示。UE接收后可以确定后续的PDCP PDU为Out-of-Delivery的PDCP PDU。进一步地，发送方设备完成Out-of-Delivery的PDCP PDU的发送后，可以再发送特定的RRC消息或者MAC CE或者DCI等方式向UE进行指示已完成发送Out-of-Delivery的PDCP PDU，后续发送的PDCP PDU为In-Order Delivery的PDCP PDU。
可选地，该PDCP PDU中还指示了PDCP PDU的SN号。UE可以根据该PDCP的SN号及当前的超帧号(Hyper Frame Number，HFN)号确定该PDCP PDU的COUNT值，一种可能的计算方式为COUNT＝SN||HFN，其中，本领域技术人员可知“||”表示拼接运算。
S520，获取所述第一协议数据单元的第一计数值。
可选地，所述第一计数值可以是PDCP PDU的COUNT值。
其中，第一计数值可以是直接获取的，也可以是通过计算得到的，对此不作限定。
可选地，S520包括：
根据所述第一协议数据单元的序列号SN和所述第一协议数据单元的超帧号HFN，确定所述第一计数值。
例如，当UE的PDCP层从较低层协议栈(如RLC层)接收到一个PDCP PDU后，UE确定该PDCP PDU对应的COUNT值。具体地，UE根据该PDCP PDU header中指示的SN号及当前的HFN号确定该PDCP PDU的COUNT值，一种可能的计算方式为COUNT＝SN||HFN。
可选地，在S510之后，所述方法还可以包括：
若所述第一协议数据单元为按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元存储于接收缓存中；
若所述第一协议数据单元为按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元递交到上层协议栈，并记录所述第一计数值。
具体而言，如果该PDCP PDU为In-Order Delivery的PDU，则将该PDCP PDU处理后得到的PDCP SDU存储在接收缓存中。该接收缓存具体可以为一个PDCP层的接收缓存。如果该PDCP PDU为Our-of-Order Delivery的PDU，则将该PDCP PDU处理后得到的PDCP SDU传输至上层协议栈(upper layer),并将该PDCP PDU的COUNT 值记录下来。
应理解，本申请实施例中所描述的上层协议栈upper layer为相对PDCP层的较上层的协议栈，如SDAP层或者IP层或者RRC层等，对此不作限定。
S530，若所述第一计数值与所述无线设备维持的第二计数值匹配，将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
可选地，或者，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值，
其中，所述第一计数值与所述无线设备维持的第二计数值匹配，具体为：
所述第一计数值等于所述第二计数值加1。
具体地，所述第二计数值可以是所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值，或者，所述第二计数值也可以是所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值。
具体而言，UE在PDCP层维持一个状态变量RX_NEXT，该RX_NEXT用于指示后续期待接收到下一个PDCP SDU关联的COUNT值，RX_NEXT＝当前接收到的最大COUNT值+1。当COUNT>＝RX_NEXT时，将RX_NEXT更新为COUNT+1。
应理解，在实际的应用过程中，上述状态变量RX_NEXT也可以用其他名称命名，本申请实施例仅以RX_NEXT为例进行说明，并不构成限定。
具体而言，UE在PDCP层维持一个状态变量RX_DELIV，该RX_DELIV为一个计数值，即所述第二计数值，表示已经删除的已递交到上层协议栈的Out-of-Order Delivery的PDCP PDU对应的PDCP SDU关联的COUNT值和已经递交到上层协议栈的In-Order Delivery的PDCP PDU对应的PDCP SDU所关联的COUNT值中的最大值。如果UE接收到一个COUNT值满足COUNT＝RX_DELIV+1的PDCP PDU，即所述第一计数值与所述无线设备维持的第二计数值匹配，则对于从RX_DELIV+1开始的由当前接收缓存中存储的In-Order Delivery的PDCP PDU对应的PDCP SDU关联的COUNT值，即所述第二数值集合，以及记录的被递交到上层协议栈的Out-of-Order Delivery对应的PDCP SDU所关联的COUNT值，即所述第四数值集合，组成的连续的COUNT值区段，即所述第五数值集合，将其中的COUNT值对应的缓存的PDCP SDU递交到上层协议栈，以及，将其中所有的记录的已递交到上层协议栈PDCP SDU关联的COUNT值删除。
应理解，在实际的应用过程中，上述状态变量RX_DELIV也可以用其他名称命名，本申请实施例仅以RX_DELIV为例进行说明，并不构成限定。
可选地，在S530之后，所述方法500还包括：
将所述第二计数值更新为所述第五数值集合的最大值。
进一步地，UE将RX_DELIV值更新为此次递交到上层协议栈的PDCP SDU关联的COUNT值及此次删除的COUNT值中的最大值。
因此，在本申请实施例中，无线设备通过接收第一协议数据单元，并确定第一协议数据单元的第一计数值，在第一计数值与所述无线设备维持的第二计数值匹配时，将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段，实现了对既存在按序递交的协议数据单元又存在非按序递交的协议数据单元的接收操作，有助于提升用户体验。
为了便于本领域的技术人员理解本申请实施例的技术方案，下面结合图7中的例子进行描述。应理解，图7中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图7的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
如图7所示，UE维持的状态变量RX_DELIV＝29，即对应所述第二计数值。随后UE接收到COUNT值为31、33和38的In-Order Delivery的PDCP PDU和COUNT值为32和34的Out-of-Order Delivery的PDCP PDU。UE将In-Order Delivery PDCP PDU对应的SDU存储在接收缓存中，将Out-of-Order Delivery的PDCP PDU对应的SDU递交到上层协议栈，并记录其对应的COUNT值，即32和34。当UE接收到一个COUNT值为30的PDCP PDU时，因为其满足COUNT值为RX_DELIV+1这个条件。因而，无论其为In-Order Delivery的PDCP PDU还是Out-of-Order Delivery的PDCP PDU，均触发一次操作过程。为了描述方便，以该PDCP PDU为一个In-Order的PDCP PDU为例进行说明。根据前述的方法，UE将该PDCP PDU对应的SDU存储在接收缓存中。前述的操作过程具体为，UE对于从RX_DELIV+1开始的存储的In-Order Delivery的PDCP PDU对应的COUNT值30、31和33，即对应第二数值集合，及记录的Out-of-Order Delivery的PDCP PDU对应的COUNT值32和34，即第四数值集合，组成的连续COUNT值区段。图7所示的从30开始的30至34这一COUNT值区段，即对应所述第五数值集合。对于其中存储的In-Order Delivery的PDCP PDU对应的SDU，即图7中所示的COUNT值为30、31和33对应的PDCP SDU，UE将其递交到上层协议栈；对于其中记录的Out-of-Order的PDCP PDU对应的COUNT值，即图7中所示的32和34，将其删除。最后，将RX_DELIV的值进行更新，将其值更新为等于本次处理的COUNT值区段的最大值，即34，即：将所述第二计数值更新为所述第五数值集合的最大值。
因此，本申请实施例的处理数据的方法，考虑了In-Order Delivery的PDCP PDU和Out-of-Order Delivery的PDCP PDU的COUNT值，从而实现了接收方设备的PDCP层对既存在In-Order Delivery的PDCP PDU又存在Out-of-Order Delivery的PDCP PDU的接收操作。
本申请还提供了另一实施例，图8示出了根据本申请另一实施例的处理数据的方法800的示意性流程图。如图8所示，所述方法800包括：
S810，如果第一计时器超期，所述第一计时器由所述无线设备在接收到计数值为第一计数值的协议数据单元后开启，则执行如下步骤：
可选地，所述第一计时器的数值可以由网络侧配置，比如网络设备配置或者核心网配置，也可以由UE自行确定。
以UE为例，UE可以维持一个计时器，比如定时器t-Reordering。当定时器t-Reordering未运行时，一旦出现至少一个存储在接收缓存中的In-Order Delivery的PDCP PDU对应的PDCP SDU或者任何被记录的已递交到上层协议栈的Out-of-Order Delivery的PDCP PDU对应的PDCP SDU所关联的COUNT值，就开启该定时器t-Reordering，并且将触发该定时器t-Reordering的COUNT值记录为RX_REORD，即所述第一计数值。在该定时器t-Reordering运行期间，如果关联的COUNT值为RX_REORD-1的PDCP SDU被递交到上层协议栈，或者记录的值为RX_REORD-1的COUNT值被删除，则停止并重置该定时器t-Reordering。比如，在前文所述的图7中，当第一计数值区段(即CONUT值从30至34的区段)处理后，还存在一个COUNT值为38的PDCP SDU被存储于接收缓存中，因而，UE开启定时器t-Reordering，并记录RX_REORD＝38。
S820，将存储的计数值小于所述第一计数值的按序递交的协议数据单元对应的服务数据单元递交到上层协议栈。
S830，将记录的小于所述第一计数值的已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值删除。
S840，将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
可选地，在S840之后，所述方法还包括：
将所述无线设备上维持的第二计数值更新为所述第五数值集合的最大值，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值。
具体地，所述第二计算值可以是所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值，或者，所述第二计数值也可以是所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值。
具体而言，如果定时器t-Reordering超期，UE将所有存储的COUNT值小于RX_REORD的In-Order Delivery的PDCP PDU对应的PDCP SDU递交到上层协议栈，将所有记录的被递交到上层协议栈的Out-of-Order Delivery的PDCP PDU对应的 PDCP SDU所关联的COUNT值中小于RX_REORD的COUNT值删除。对于从RX_REORD开始的由当前接收缓存中存储的In-Order Delivery的PDCP PDU对应的PDCP SDU关联的COUNT值，即所述第二数值集合，以及记录的被递交到上层协议栈的Out-of-Order Delivery的PDCP PDU对应的PDCP SDU所关联的COUNT值，即所述第四数值集合，组成的连续的COUNT值区段，即所述第五数值集合，将其中所有的COUNT值对应的存储的In-Order Delivery的PDCP PDU对应的PDCP SDU递交到上层协议栈，将其中所有的记录的已递交到上层协议栈的Out-of-Order Delivery的PDCP PDU对应的PDCP SDU关联的COUNT值删除。进一步地，UE可以将RX_DELIV值更新为此次递交到上层协议栈的PDCP SDU关联的COUNT值及此次删除的COUNT值中的最大值。
因此，在本申请实施例中，无线设备在确定第一计数器超期时，将存储的计数值小于所述第一计数值的按序递交的协议数据单元对应的服务数据单元递交到上层协议栈；将记录的小于所述第一计数值的已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值删除；将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，在计时器超期时实现了对既存在按序递交的协议数据单元又存在非按序递交的协议数据单元的接收操作，有助于提升用户体验。
应理解，上述方法800可以与上述方法500组合执行，也可以单独实施，本申请实施例对此不作限定。
为了便于本领域的技术人员理解本申请实施例的技术方案，下面结合图9中的例子进行描述。应理解，图9中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图9的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
如图9所示，触发定时器t-Reordering的COUNT值为38，即RX_REORD(对应所述第一计数值)为38，当定时器t-Reordering的时长到达后，UE仍未接收到COUNT值为RX_DELIV+1的PDCP PDU，则UE启动一次接收操作，其中，RX_DELIV为34，对应所述第二计数值。具体为，对于COUNT值小于RX_REORD的区段，将其中存储的In-Order Delivery PDCP PDU对应的SDU递交到上层协议栈，将记录的Out-of-Order Delivery的PDCP PDU对应的COUNT值删除，如图9所示，UE没有存储的In-Order Delivery PDCP PDU对应的SDU，则不进行相应操作，UE将COUNT值36删除。进一步地，UE对于从RX_REORD开始的由存储的In-Order Delivery的PDCP PDU对应的COUNT值(对应所述第二数值集合)及记录的Out-of-Order Delivery的PDCP PDU对应的COUNT值(对应所述第四数值集合)组成的连续COUNT值区段(对应所述第五数值集合)，即图9所示的从38开始的38至40这一COUNT值区段，对于其中存储的In-Order Delivery的PDCP PDU对应的SDU，即图9中所示的COUNT值为38和40对应的PDCP SDU，UE将其递交到上层协议栈，对于其中记录的Out-of-Order的PDCP PDU对应的COUNT值，即图9中所示的39，将其删除。最后，将RX_DELIV的值进行更新，将其值更新为等于本次处理的COUNT值区段的最大值，即40。
因此，本申请实施例的处理数据的方法，在定时器t-Reordering超期时，考虑了In-Order Delivery的PDCP PDU和Out-of-Order Delivery的PDCP PDU的COUNT值，从而实现了接收方设备的PDCP层对既存在In-Order Delivery的PDCP PDU又存在Out-of-Order Delivery的PDCP PDU的DRB的接收操作。
应理解，在本申请实施例中，计数值是以COUNT值为例进行说明的。在实际实施过程中，上述计数值也可以使用其他计数值，比如SN，或HFN等，本申请实施例对此不作限定。
上文结合图1至图9，详细描述了根据本申请实施例的处理数据的方法，下面将结合图10至图12，描述根据本申请实施例的无线设备。
图10示出了根据本申请实施例的无线设备1000的示意性框图。所述无线设备1000用于执行前述方法500或相关例子中的步骤。可选地，所述无线设备1000中各个模块可以是通过软件来实现的。所述无线设备1000可以安装在通用计算机设备中。如图10所示，所述无线设备1000包括：
接收模块1010，用于接收第一协议数据单元；
处理模块1020，用于获取所述第一协议数据单元的第一计数值；
所述处理模块1020，还用于若所述第一计数值与所述无线设备维持的第二计数值匹配，
将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
可选地，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值，
可选地，所述第一计数值与所述无线设备维持的第二计数值匹配，具体为：
所述第一计数值等于所述第二计数值加1。
可选地，所述处理模块1020具体用于：
根据所述第一协议数据单元的序列号SN和所述第一协议数据单元的超帧号HFN，确定所述第一计数值。
可选地，在所述将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述处理模块1020还用于：
将所述第二计数值更新为所述第五数值集合的最大值。
可选地，所述无线设备通过所述无线设备的分组数据汇聚协议PDCP层执行上述方法中的步骤；所述第一协议数据单元为PDCP分组数据单元PDU。
可选地，在所述接收所述第一协议数据单元之后，所述处理模块1020还用于：
若所述第一协议数据单元为按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元存储于接收缓存中；
若所述第一协议数据单元为非按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元递交到上层协议栈，并记录所述第一计数值。
应理解，根据本申请实施例的无线设备1000中的各个模块的上述和其它管理操作和/或功能分别为了实现前述方法500的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，在此不再赘述。
还应理解，本申请实施例中的处理模块可以由处理器实现，接收模块可以由接收器实现。
图11示出了根据本申请实施例的无线设备1100的示意性框图。所述无线设备1100用于执行前述方法800或相关例子中的步骤。可选地，所述无线设备1100中各个模块可以是通过软件来实现的。所述无线设备1100可以安装在通用计算机设备中。如图11所示，所述无线设备1100包括：
处理模块1110，如果第一计时器超期，所述第一计时器由所述无线设备在接收到计数值为第一计数值的协议数据单元后开启，用于执行如下步骤：
将存储的计数值小于所述第一计数值的按序递交的协议数据单元对应的服务数据单元递交到上层协议栈；
将记录的小于所述第一计数值的已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值删除；
将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
可选地，在所述将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述处理模块1110还用于：
将所述无线设备上维持的第二计数值更新为所述第五数值集合的最大值，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值。
可选地，所述无线设备通过所述无线设备的PDCP层执行上述方法中的步骤；所述协议数据单元为PDCP分组数据单元PDU。
应理解，根据本申请实施例的无线设备1100中的各个模块的上述和其它管理操作和/或功能分别为了实现前述方法800的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，在此不再赘述。
还应理解，本申请实施例中的处理模块可以由处理器实现。
图12示出了根据本申请实施例的无线设备的结构示意图。如图12所示，所示无线设备包括处理器1201，存储器1202，所述存储器1202，用于存储相应的程序和数据，以供所述处理器1201调用来实现相应的功能。所述处理器1201可以调用所述存储器中存储的程序和数据，来实现本申请各方法实施例中所述无线设备所执行的功能。
进一步地，所述无线设备还可以包括发射器1203和接收器1204，用于发送和接收数据。在一种实施例中，所述无线设备接收到的所述第一协议数据单元可以是通过所述无线设备上的接收器1204接收的。在另一种实施例中，所述无线设备接收到的所述第一协议数据单元可以是通过所述无线设备外的其他设备上的接收器接收后转发(可以通过有线或无线的方式转发)给所述无线设备的，例如所述无线设备为CU，其接收到的PDCP PDU是通过DU接收后通过F1接口转发的。
所述无线设备能够执行本申请实施例中由无线设备执行的任一方法。
上述本申请实施例揭示的方法可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application Specific Integrated Circuit，ASIC)，现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件，分立门或者晶体管逻辑器件，分立硬件组件，还可以是系统芯片(System On Chip，SoC)，还可以是中央处理器(Central Processor Unit，CPU)，还可以是网络处理器(Network Processor，NP)，还可以是数字信号处理电路(Digital Signal Processor，DSP)，还可以是微控制器(Micro Controller Unit，MCU)，还可以是可编程控制器(Programmable Logic Device，PLD)或其他集成芯片。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的指令，结合其硬件完成上述方法的步骤。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器ROM、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器RAM，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
还应理解，本文中涉及的第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以 存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (17)

  1. 一种处理数据的方法，其特征在于，所述方法应用于无线设备，所述方法包括：
    接收第一协议数据单元；
    获取所述第一协议数据单元的第一计数值；
    若所述第一计数值与所述无线设备维持的第二计数值匹配，
    将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
  2. 根据权利要求1所述的方法，其特征在于，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值，
    其中，所述第一计数值与所述无线设备维持的第二计数值匹配，包括：
    所述第一计数值等于所述第二计数值加1。
  3. 根据权利要求1或2所述的方法，其特征在于，所述获取所述第一协议数据单元的第一计数值，包括：
    根据所述第一协议数据单元的序列号SN和所述第一协议数据单元的超帧号HFN，确定所述第一计数值。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，在所述将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述方法还包括：
    将所述第二计数值更新为所述第五数值集合的最大值。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，在所述接收所述第一协议数据单元之后，所述方法还包括：
    若所述第一协议数据单元为按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元存储于接收缓存中；
    若所述第一协议数据单元为非按序递交的协议数据单元，将所述第一协议数据单元对应的服务数据单元递交到上层协议栈，并记录所述第一计数值。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述无线设备通过所述无线设备的分组数据汇聚协议PDCP层执行所述权利要求1至5中任一项所述的方法；所述第一协议数据单元为PDCP分组数据单元PDU。
  7. 一种处理数据的方法，其特征在于，所述方法应用于无线设备，所述方法包括：
    如果第一计时器超期，所述第一计时器由所述无线设备在接收到计数值为第一计 数值的协议数据单元后开启，则执行以下步骤：
    将存储的计数值小于所述第一计数值的按序递交的协议数据单元对应的服务数据单元递交到上层协议栈；
    将记录的小于所述第一计数值的已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值删除；
    将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
  8. 根据权利要求7所述的方法，其特征在于，在所述将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除之后，所述方法还包括：
    将所述无线设备上维持的第二计数值更新为所述第五数值集合的最大值，所述第二计数值为所述无线设备递交到上层协议栈的最后一个按序递交的协议数据单元对应的服务数据单元的计数值和所述无线设备删除的非按序递交的协议数据单元对应的服务数据单元的计数值中的最大值中的较大值。
  9. 根据权利要求7或8所述的方法，其特征在于，所述无线设备通过所述无线设备的分组数据汇聚协议PDCP层执行所述权利要求7或8所述的方法；所述协议数据单元为PDCP分组数据单元PDU。
  10. 一种无线设备，其特征在于，包括：
    接收模块，用于接收第一协议数据单元；
    处理模块，用于获取所述第一协议数据单元的第一计数值；
    所述处理模块，还用于若所述第一计数值与所述无线设备维持的第二计数值匹配，则将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段。
  11. 一种无线设备，其特征在于，包括：
    处理模块，如果第一计时器超期，所述第一计时器由所述无线设备在接收到计数值为第一计数值的协议数据单元后开启，用于执行如下步骤：
    将存储的计数值小于所述第一计数值的按序递交的协议数据单元对应的服务数据单元递交到上层协议栈；
    将记录的小于所述第一计数值的已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值删除；
    将第一数值集合中的第二数值集合对应的服务数据单元递交至上层协议栈，将第 三数值集合中的第四数值集合删除，所述第一数值集合包括所述无线设备接收并存储于接收缓存中的按序递交的协议数据单元对应的服务数据单元的计数值，所述第三数值集合包括所述无线设备记录的所述无线设备接收并已递交到上层协议栈的非按序递交的协议数据单元对应的服务数据单元的计数值，其中，所述第二数值集合与所述第四数值集合组成的第五数值集合是从所述第一计数值开始计数的连续的计数值区段
  12. 一种无线设备，其特征在于，包括：处理器，存储器和收发器；
    所述收发器，用于接收和发送数据；
    所述存储器用于存储指令；
    所述处理器用于调用所述存储器中的所述指令，执行如权利要求1至9中任一项所述的方法。
  13. 一种计算机程序产品，包括计算机程序，其特征在于，该计算机程序在某一计算机上执行时，将会使所述计算机实现如权利要求1至9中任一项所述的方法。
  14. 一种计算机程序，其特征在于，该计算机程序在某一计算机上执行时，将会使所述计算机实现如权利要求1至9中任一项所述的方法。
  15. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该计算机程序在某一计算机上执行时，将会使所述计算机实现如权利要求1至9中任一项所述的方法。
  16. 一种芯片，其特征在于，包括：处理模块与通信接口，所述处理模块用于执行如权利要求1至9任一项所述的方法。
  17. 根据权利要求16所述的芯片，其特征在于，所述芯片还包括存储模块，所述存储模块用于存储指令，所述处理模块用于调用所述存储模块存储的指令，并且对所述存储模块中存储的指令的调用使得所述处理模块执行如权利要求1至9中任一项所述的方法。
PCT/CN2018/104549 2017-09-08 2018-09-07 处理数据的方法和设备 WO2019047912A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18854517.2A EP3618405A4 (en) 2017-09-08 2018-09-07 METHOD AND DEVICE FOR PROCESSING DATA
US16/633,398 US11025555B2 (en) 2017-09-08 2018-09-07 Method for processing data and device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710803613.2 2017-09-08
CN201710803613 2017-09-08
CN201710940143.4 2017-09-30
CN201710940143.4A CN109474651B (zh) 2017-09-08 2017-09-30 处理数据的方法和设备

Publications (1)

Publication Number Publication Date
WO2019047912A1 true WO2019047912A1 (zh) 2019-03-14

Family

ID=65633905

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104549 WO2019047912A1 (zh) 2017-09-08 2018-09-07 处理数据的方法和设备

Country Status (1)

Country Link
WO (1) WO2019047912A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024117952A1 (en) * 2022-12-02 2024-06-06 Telefonaktiebolaget Lm Ericsson (Publ) Method performed by a communication device comprising a protocol stack, receiving an indication from an upper layer to clear data in a buffer which data have not been yet submitted to one or more layers below the layer

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104426638A (zh) * 2013-08-20 2015-03-18 联芯科技有限公司 一种数据递交方法和装置
CN104519524A (zh) * 2013-09-26 2015-04-15 中兴通讯股份有限公司 一种基于多流传输的数据排序方法及接收装置
CN104935413A (zh) * 2014-03-19 2015-09-23 夏普株式会社 分组数据汇聚协议pdcp实体及其执行的方法
US20150326456A1 (en) * 2014-05-09 2015-11-12 Telefonaktiebolaget L M Ericsson (Publ) Pdcp and flow control for split bearer

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104426638A (zh) * 2013-08-20 2015-03-18 联芯科技有限公司 一种数据递交方法和装置
CN104519524A (zh) * 2013-09-26 2015-04-15 中兴通讯股份有限公司 一种基于多流传输的数据排序方法及接收装置
CN104935413A (zh) * 2014-03-19 2015-09-23 夏普株式会社 分组数据汇聚协议pdcp实体及其执行的方法
US20150326456A1 (en) * 2014-05-09 2015-11-12 Telefonaktiebolaget L M Ericsson (Publ) Pdcp and flow control for split bearer

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024117952A1 (en) * 2022-12-02 2024-06-06 Telefonaktiebolaget Lm Ericsson (Publ) Method performed by a communication device comprising a protocol stack, receiving an indication from an upper layer to clear data in a buffer which data have not been yet submitted to one or more layers below the layer

Similar Documents

Publication Publication Date Title
CN109474651B (zh) 处理数据的方法和设备
WO2018202190A1 (zh) 一种数据传输的处理方法和装置
CN108366369B (zh) 一种数据安全传输的方法及接入网、终端、核心网设备
WO2015139557A1 (zh) 分组数据汇聚协议pdcp实体及其执行的方法
TWI734010B (zh) 傳輸數據的方法和設備
US20220070748A1 (en) Data transmission method and related device
TWI677255B (zh) 處理用於無線承載的承載型態改變的裝置及方法
TWI670954B (zh) 處理承載型態改變的裝置
WO2022078517A1 (zh) 数据传输方法、设备和存储介质
WO2020224631A1 (zh) 处理数据包的方法和装置
WO2018107925A1 (zh) 一种数据流的处理方法及装置、计算机存储介质
WO2021027853A1 (zh) 一种通信方法及装置
US11627190B2 (en) Timer control method, data packet processing method, and device
WO2020233190A1 (zh) 多链路系统的mpdu发送、接收方法及装置、存储介质、发送端、接收端
WO2020029445A1 (zh) 无线通信方法、通信设备、芯片和通信系统
WO2019047912A1 (zh) 处理数据的方法和设备
US20230224253A1 (en) Communication method and apparatus
CN108200605B (zh) 一种基站的数据传输方法和装置
WO2020107220A1 (zh) 无线通信方法、终端设备和网络设备
WO2022134958A1 (zh) 数据传输方法、装置、设备和存储介质
CN111654360B (zh) 一种非激活态的切换处理方法及通信设备
WO2021087729A1 (zh) 一种指示解压缩对象的方法及装置、通信设备
WO2024169671A1 (zh) 通信的方法和装置
WO2023207555A1 (zh) 一种通信方法及装置
WO2019014918A1 (zh) 传输数据的方法和设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18854517

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018854517

Country of ref document: EP

Effective date: 20191129

NENP Non-entry into the national phase

Ref country code: DE