Nothing Special   »   [go: up one dir, main page]

WO2024168672A1 - 数据处理方法和装置 - Google Patents

数据处理方法和装置 Download PDF

Info

Publication number
WO2024168672A1
WO2024168672A1 PCT/CN2023/076416 CN2023076416W WO2024168672A1 WO 2024168672 A1 WO2024168672 A1 WO 2024168672A1 CN 2023076416 W CN2023076416 W CN 2023076416W WO 2024168672 A1 WO2024168672 A1 WO 2024168672A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
state variable
pdu
sdu
pdu set
Prior art date
Application number
PCT/CN2023/076416
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 富士通株式会社
Priority to PCT/CN2023/076416 priority Critical patent/WO2024168672A1/zh
Publication of WO2024168672A1 publication Critical patent/WO2024168672A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Definitions

  • the present application relates to the field of communications.
  • XR services refer to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. Its application areas include but are not limited to entertainment, medical care, education, etc.
  • XR services can include virtual reality (VR) services, augmented reality (AR) services, and mixed reality (MR) services.
  • VR virtual reality
  • AR augmented reality
  • MR mixed reality
  • Virtual reality is a rendered version of a published visual and audio scene, where the rendering is intended to simulate the visual and auditory sensory stimulation of the real world as naturally as possible when the observer or user moves within the limitations defined by the application.
  • Augmented reality refers to the provision of additional information or artificially generated items or content overlaid on the user's current environment.
  • Mixed reality is an advanced form of AR, in which some virtual elements are inserted into the physical scene with the aim of providing an illusion that these elements are part of the real scene.
  • a PDU Set consists of one or more PDUs (Protocol Data Units), which carry the payload of an information unit generated at the application layer (for example, frames or video slices for XR and media services).
  • PDUs Protocol Data Units
  • the application layer requires all PDUs in the PDU Set to use the corresponding information unit.
  • the application layer can still recover all or part of the information unit.
  • the PDU here is the application-level PDU, that is, the PDU in the PDU session layer, usually referring to an IP packet protecting an Ethernet frame.
  • each sublayer also has a corresponding PDU, such as PDCP PDU (Packet Data Convergence Protocol PDU), RLC PDU (Radio Link Control PDU), etc.
  • PDCP PDU Packet Data Convergence Protocol PDU
  • RLC PDU Radio Link Control PDU
  • an embodiment of the present application provides a data processing method and device.
  • a data processing apparatus which is configured in a terminal device, and the apparatus includes:
  • a processing unit which discards all PDCP SDUs and their corresponding PDCP data PDUs in a PDU Set, or considers that the discard timers of all PDCP SDUs belonging to the PDU Set have timed out when at least one of the following conditions associated with the PDU Set is satisfied;
  • a discard timer corresponding to a PDCP SDU expires, and the PDCP SDU belongs to the PDU Set;
  • a PDCP SDU belonging to the PDU Set is not confirmed as successfully delivered by a PDCP status report, and the PSII of the PDU Set is configured;
  • the PDCP layer of the terminal device receives an indication that a PDCP data PDU exceeds the maximum number of transmission times, and the SDU corresponding to the PDCP data PDU belongs to the PDU Set, and the PDU Set is configured with PSII.
  • a data processing apparatus configured in a sending device, and the sending device is a terminal device or a network device, and the apparatus includes:
  • a sending unit which sends the sequence number information of the PDCP SDUs associated with the PDCP sequence number to the receiving device after the sending device discards all the PDCP SDUs corresponding to a PDU Set.
  • a data processing apparatus which is configured in a receiving device, and the receiving device is a network device or a terminal device, and the apparatus includes:
  • a first processing unit which stores or records the sequence number information of the discarded PDCP SDU after the receiving device receives the sequence number information of the discarded PDCP SDU;
  • the second processing unit delivers the stored PDCP SDU to a higher layer according to the sequence number information of the discarded PDCP SDU.
  • One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, on the one hand, the problem of discarding data of PDU Set in the wireless access network is solved, which can be used to better support XR and media service applications.
  • the discard report is introduced, and the problem of sequence number gaps caused by data discard is solved by enhancing the sending and receiving ends, reducing the reordering delay, thereby improving the transmission performance of the XRM service. In this way, the processing of differentiated PDU Sets can be guaranteed and the integrated data processing requirements of PDU Sets can be met.
  • FIG1 is a schematic diagram of a data processing method according to an embodiment of the present application.
  • FIG2 is another schematic diagram of the data processing method according to an embodiment of the present application.
  • FIG3 is a schematic diagram of an example of a PDCP discard report format
  • FIG4 is another schematic diagram of the data processing method according to an embodiment of the present application.
  • 5 to 8 are schematic diagrams of several examples of magnitude relationships between the third state variable and the fourth state variable and the first state variable and the second state variable;
  • FIG9 is a schematic diagram of a data processing device according to an embodiment of the present application.
  • FIG10 is another schematic diagram of a data processing device according to an embodiment of the present application.
  • FIG11 is another schematic diagram of the data processing device according to an embodiment of the present application.
  • FIG12 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a network device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or time order of these elements, etc., and these elements should not be limited by these terms.
  • the term “and/or” includes any one and all combinations of one or more of the associated listed terms.
  • the terms “comprising”, “including”, “having”, etc. refer to the existence of the stated features, elements, components or components, but do not exclude the existence or addition of one or more other features, elements, components or components.
  • the term “communication network” or “wireless communication network” may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.
  • LTE Long Term Evolution
  • LTE-A enhanced Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • communication between devices in the communication system may be carried out according to communication protocols of any stage, such as but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G and future 5G
  • NR New Radio
  • the term "network device” refers to, for example, a device that connects a terminal device to a communication system.
  • the network equipment provides services for the terminal device.
  • Network equipment may include but is not limited to the following equipment: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.
  • Base stations may include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays, or low-power nodes (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • the term “base station” may include some or all of their functions, and each base station may provide communication coverage for a specific geographical area.
  • the term “cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment” (TE).
  • the terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, and the like.
  • Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, and IAB-MT, etc.
  • PDAs personal digital assistants
  • wireless modems wireless communication devices
  • handheld devices machine-type communication devices
  • laptop computers cordless phones
  • smart phones smart watches, digital cameras
  • IAB-MT IAB-MT
  • the terminal device can also be a machine or device for monitoring or measuring, such as but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device to device (D2D) terminal, machine to machine (M2M) terminal, and so on.
  • MTC machine type communication
  • D2D device to device
  • M2M machine to machine
  • HDRLL High Data Rate Low Latency
  • AR/VR/XR AR/VR/XR services
  • tactile/multimodal communication services The goals include:
  • Enhanced features to support multi-mode services including:
  • PDU Set granularity e.g. video/audio frame/tile, application data unit, control information
  • PDU Set granularity e.g. video/audio frame/tile, application data unit, control information
  • PDU Set has different QoS requirements, such as priority, importance, etc.
  • QoS requirements such as priority, importance, etc.
  • the existing QoS model based on QoS flow cannot support the different QoS requirements of PDU Set.
  • there are two major requirements for the processing of PDU Set integrated packet processing of PDU Set and differentiated processing of PDU Set.
  • QoS flow is the finest granularity of QoS differentiation in PDU session.
  • 5G QoS characteristics are determined by 5QI (5G QoS Identifier). This means that each packet in a QoS flow is processed according to the same QoS requirements.
  • a group of data packets is used to carry the payload of a PDU Set (e.g., frames, Video slice/tile).
  • a PDU Set e.g., frames, Video slice/tile.
  • the packets in such a PDU Set are decoded/processed as a whole.
  • a frame/video slice can be decoded only if all or a certain number of packets carrying the frame/video slice are successfully transmitted.
  • the client can decode a frame in a GOP (group of pictures) only if all frames on which the frame depends are successfully received. Therefore, the groups of packets in a PDU Set have inherent interdependencies in the media layer. If this dependency between packets in a PDU Set is not taken into account, the 5GS may perform scheduling inefficiently. For example, the 5GS may randomly drop one or more packets, but try to transmit other packets of the same PDU Set, which are useless to the client, thereby wasting radio resources.
  • PDU Set differentiated treatment XR/media services are characterized by high data rates and low latency.
  • 5GS QoS framework will be enhanced to support different QoS treatment of PDU Sets.
  • PDU Sets can carry different content, such as I/B/P frames, slices/tiles within I/B/P frames, etc. This key issue proposes to support differentiated QoS treatment, taking into account the different importance of PDU Sets, such as reducing resource waste by differentially treating data packets (i.e., PDUs) belonging to less important PDU Sets.
  • control plane enhancement includes defining the following PDU Set QoS parameters:
  • PDU Set Error Rate refers to the upper limit of the proportion of PDU Sets that have been processed by the transmitter of the link layer protocol (such as RLC in the RAN accessed by 3GPP) but have not been successfully delivered to the higher layer of the corresponding receiving end (such as PDCP in the RAN accessed by 3GPP);
  • PDU Set Delay Budget defines the upper limit of the delay that a PDU Set can experience in transmission between the UE and the N6 endpoint of the UPF (i.e. the time from the receipt of the first PDU to the successful delivery of the last arriving PDU in the PDU Set);
  • PDU Set Integrated Indication indicates whether the application layer requires all PDUs in order to use the PDU Set.
  • user plane enhancements include UPF identifying the following information related to PDU Set: PDU Set sequence number, last PDU mark of PDU Set, PDU sequence number within PDU Set, size of PDU Set, and importance of PDU Set.
  • the NAS (non-access stratum) layer of the UE can identify information related to the PDU Set. Similar to downlink traffic, these PDU Set related information may include the PDU Set identifier, the PDU sequence number in the PDU Set, the PDU Set Importance, and optionally, the start and/or end flags of the PDU Set, the size of the PDU Set, etc.
  • the PDU Set Importance indicates the importance of the PDU Set in the XRM (XR and multimedia) service flow, or the priority, such as high, medium, low, or 0 ⁇ Nmax digital expression, which is used for differentiated processing of the PDU Set in the RAN, such as priority processing, scheduling, data discarding, etc.
  • PDU Set Importance can be prepared for the UE according to the S-NSSAI/DNN (Single Network Slice Selection Assistance Information/Data Network Name) of the PDU session during PDU session establishment/modification.
  • the PDU Set Importance rules can be sent to the UE from the 5GC (5G Core Network) through the N1SM container defined in the session management process.
  • PDU Set Importance can be used by the UE to map the PDU Set to the appropriate MAC (medium access control) transmission buffer.
  • the UE classifies and marks the uplink user plane traffic according to the QoS rules, that is, the association of the uplink traffic of XRM with the QoS flows and/or sub-QoS flows.
  • This application considers discarding PDU Set and related operations at the PDCP (Packet Data Convergence Protocol) layer.
  • the PDCP layer needs to know the relevant information of the uplink data PDU Set. This information can be determined by the UE implementation, that is, the UE upper layer identifies the information related to the PDU Set and passes it to the PDCP layer through the internal interface; it can also be passed to the PDCP layer by the UE by adding the relevant information of the PDU Set in the uplink data header of the SDAP (Service Data Adaptation Protocol) layer.
  • SDAP Service Data Adaptation Protocol
  • PDU refers to the PDU in the PDU session.
  • the data discard function of the PDCP layer is for PDCP SDU (service data unit, service Service Data Unit).
  • the transmitting PDCP entity maintains a discard timer (discardTimer) for each PDCP SDU.
  • the discard timer is only configured for DRB (data radio bearer).
  • the duration of the timer (duration, that is, the initial value when the timer is started) is configured by the higher layer (RRC, radio resource control).
  • RRC radio resource control
  • the sending PDCP entity needs to discard the PDCP SDU and the corresponding PDCP data PDU.
  • a PDU Set has certain content criteria, which refers to the standard used to determine whether a PDU Set can be considered to be successfully delivered. For example, if a PDU Set is configured with PSII (which means that the PDU Set Integrity Indicator is true), then the PDU Set is only useful to the receiver if all bits are delivered correctly, that is, no errors can be tolerated. In this case, if a PDU Set is configured with PSII, when it is confirmed that a PDU has not been successfully delivered, the PDU Set to which the PDU belongs can be discarded.
  • PSII which means that the PDU Set Integrity Indicator is true
  • the PDU Set can be considered to be discarded as a whole; or when PSII is configured, the sender can discard the PDU Set that confirms that there are PDUs that have not been successfully delivered.
  • FIG1 is a schematic diagram of a data processing method of an embodiment of the present application. As shown in FIG1 , the method includes:
  • the terminal device discards all PDCP SDUs and their corresponding PDCP data PDUs in a PDU Set, or considers that the discard timers of all PDCP SDUs belonging to the PDU Set have timed out, if at least one of the following conditions associated with the PDU Set is met:
  • a discard timer corresponding to a PDCP SDU expires, and the PDCP SDU belongs to the PDU Set;
  • a PDCP SDU belonging to the PDU Set is not confirmed as successfully delivered by a PDCP status report, and the PSII of the PDU Set is configured;
  • the PDCP layer of the terminal device receives an indication that a PDCP data PDU exceeds the maximum number of transmission times, and the SDU corresponding to the PDCP data PDU belongs to the PDU Set, and the PDU Set is configured with PSII.
  • FIG1 above only schematically illustrates the embodiment of the present application, but the present application is not limited to the following embodiments. For example, some other operations may be added. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG. 1 above.
  • data is discarded based on content criteria, thereby ensuring the integrity of the PDU Set or the validity of the content and saving network resources.
  • the sending PDCP entity of the terminal device discards all PDCP SDUs and their corresponding PDCP data PDUs in the PDU Set.
  • each PDCP SDU still uses a separate discard timer.
  • the initial value, startup method, etc. of the discard timer can refer to the relevant technology and the description is omitted here.
  • TS 38.323 may be enhanced.
  • TS 38.323 may include the following description:
  • the discard timers of all PDCP SDUs in the PDU Set are considered to have timed out. That is, the terminal device considers that the discard timers of all PDCP SDUs in the PDU Set have timed out.
  • the sending PDCP entity of the terminal device discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the PDU Set.
  • PDUs i.e., PDCP SDUs belonging to the same PDU Set share the same discard timer. That is, the sending PDCP entity of the terminal device maintains a discard timer for each PDU Set.
  • the duration of the discard timer can be configured according to the PSDB or by the network device, and this application does not impose any restrictions on this.
  • the sending PDCP entity of the terminal device when the sending PDCP entity of the terminal device receives a PDCP SDU from the higher layer, if the PDCP SDU belongs to the PDU Set at the application level, that is, belongs to a PDU in the PDU Set, or is associated with a certain PDU Set, and the PDCP SDU is the first PDU in the PDU Set, for example, a PDU with the first PDU sequence number, and the PDU sequence number of the first PDU is, for example, 0, then the sending PDCP entity of the terminal device starts the discard timer associated with the PDU Set (if configured).
  • the sending PDCP entity discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the PDU Set.
  • TS 38.323 may be enhanced.
  • TS 38.323 may include the following description:
  • the transmission delay of the PDU Set is considered as a whole, thereby meeting the PSDB requirements of the PDU Set.
  • the terminal device may determine whether to discard the PDCP Set based on the PDCP status report.
  • the PDU Set has certain content criteria, that is, the criteria for determining whether the PDU Set can be considered to be successfully delivered.
  • a PDU Set is configured with PSII (which means that the PDU Set Integrity Indicator is true)
  • PSII which means that the PDU Set Integrity Indicator is true
  • the PDU Set is only useful to the receiver if all bits are delivered correctly, that is, no errors can be tolerated.
  • PSII when it is confirmed that a PDU has not been successfully delivered, the PDU Set to which the PDU belongs can be discarded.
  • a PDU Set can be configured with a PDU Set content ratio, which indicates that the PDU Set is useful to the receiver only when X% of the bits of the PDU Set are correctly delivered, where X is the content ratio of the PDU Set.
  • FEC Forward Error Correction
  • the sender can discard the PDU Set, that is, the remaining PDUs do not need to be sent, saving network resources.
  • the transmitting end can use the PDCP status report to know the transmission status of each PDCP SDU.
  • the PDCP status report is used for AM DRBs configured with statusReportRequired and is triggered by the receiving PDCP entity in cases of PDCP entity reestablishment, data recovery, or uplink data switching.
  • some trigger conditions can be added to allow the receiving end to send a PDCP status report, such as sending it at a scheduled time, or sending it in a congested situation, or sending it when the received data is erroneous (or there are many errors), or sending it when the sending end needs to discard data for other reasons, etc.
  • the sending PDCP entity may also add a request (poll) message to request the PDCP entity at the receiving end to send a PDCP status report.
  • the sending PDCP entity may determine whether the PDU Set is completely successfully delivered, the number and ratio of successfully delivered PDUs in the PDU Set, and other information based on the received PDCP status report.
  • the sending PDCP entity of the terminal device discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the PDU Set.
  • PSII is configured (or configured to be true) means that the PDU Set is configured with an integrity indication, indicating that the application layer requires all PDUs in order to use the PDU Set.
  • TS 38.323 may be enhanced.
  • TS 38.323 may include the following description:
  • the terminal device may enhance the SDU discarding function of the PDCP layer as follows:
  • the sending PDCP entity of the terminal device discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the PDU Set.
  • the terminal device may further enhance the SDU discarding function of the PDCP layer as follows:
  • the sending PDCP entity of the terminal device discards all PDCP SDUs belonging to the PDU Set and their corresponding PDCP data PDUs.
  • the first threshold and the second threshold may be predefined or configured by the network device, for example, the network device is configured through RRC signaling.
  • the network device is configured through RRC signaling.
  • data discard is performed based on the content criteria of the PDU Set, thereby ensuring the integrity or content validity of the PDU Set and saving network resources.
  • the terminal device may discard the PDU Set based on the RLC (Radio Link Control) layer's indication of exceeding the maximum number of transmissions.
  • RLC Radio Link Control
  • the terminal device can receive an indication at the PDCP layer that a certain PDCP data PDU exceeds the maximum number of transmission times (for example, all RLC entities submitted to the PDCP data PDU have received the indication), and the SDU corresponding to the PDCP data PDU belongs to a PDU Set, and the PDU Set is configured with PSII, then the sending PDCP entity discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the PDU Set.
  • the RLC layer of the terminal device can inform the higher layer (such as the PDCP layer, for example, indicating to the PDCP layer) that the RLC SDU has reached the maximum number of retransmissions.
  • the PDCP layer can determine that the transmission of the RLC SDU (corresponding to the PDCP PDU) has failed.
  • TS 38.323 may be enhanced.
  • TS 38.323 may include the following description:
  • the terminal device may enhance the SDU discarding function of the PDCP layer as follows:
  • the sending PDCP entity of the terminal device discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the PDU Set.
  • the third threshold may be predefined or configured by the network device, for example, the network device is configured through RRC signaling.
  • the network device is configured through RRC signaling.
  • the present application does not limit the specific configuration method, and reference may be made to the relevant technology.
  • the content criteria of the PDU Set are also considered for data discarding, thereby ensuring the integrity or content validity of the PDU Set and saving network resources.
  • the transmission delay of the PDU Set is considered as a whole, thereby meeting the PSDB requirements of the PDU Set; on the other hand, data is discarded based on the content criteria of the PDU Set, thereby ensuring the integrity of the PDU Set or the validity of the content and saving network resources.
  • SN gap sequence number gap
  • a series of consecutive PDCP SDUs are often discarded, resulting in a larger sequence number gap. How to avoid or minimize the sequence number gap needs to be solved.
  • an embodiment of the present application provides a data processing method, which is described from the side of a sending device.
  • the sending device can be a terminal device or a network device; correspondingly, the receiving device can be a network device or a terminal device.
  • FIG. 2 is a schematic diagram of a processing method according to an embodiment of the present application. Referring to FIG. 2 , the method includes:
  • the sending device After discarding all PDCP SDUs corresponding to a PDU Set, the sending device sends the sequence number information of the PDCP SDUs associated with the PDCP sequence number to the receiving device.
  • PDU Set often corresponds to a continuous series of PDCP SDU sequence numbers, so the sending device can send a discarded continuous section of SDU sequence number information to the receiving device.
  • FIG. 2 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto. For example, other operations may be added. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 2.
  • the method of discarding the PDU Set there is no restriction on the method of discarding the PDU Set.
  • the method of the embodiment of the first aspect may be used to discard the PDU Set, or other methods may be used to discard the PDU Set.
  • the transmitting end After discarding all PDCP SDUs corresponding to a certain PDU Set, the transmitting end The sequence number information of the SDUs to which the PDCP sequence number has been associated may be sent to the receiving end. In this way, the PDCP entity at the receiving end may know which sequence numbers have been discarded by the transmitting end, and thus will not wait to receive these data, thereby avoiding reordering delays.
  • the above sequence number information can be sent via a PDCP control PDU.
  • the sequence number information can be notified by adding a new PDCP control PDU at the PDCP layer.
  • the PDCP control PDU can be called a PDCP discard report.
  • the sending PDCP entity at the sending end can send a PDCP discard report to the PDCP entity at the other end (receiving end) after the PDU Set is discarded to notify the sequence number information of the discarded PDCP SDU.
  • the sequence number information includes a COUNT value (i.e., a PDCP sequence number of the PDCP SDU) of the first PDCP SDU in the discarded consecutive PDCP SDUs (e.g., the entire PDU Set), for example, called COUNT_start, and the number of the discarded consecutive PDCP SDUs, for example, called length.
  • COUNT_start a COUNT value of the first PDCP SDU and a COUNT value of the last PDCP SDU in the discarded consecutive PDCP SDUs
  • COUNT_end i.e., a COUNT value of the PDCP SDU
  • FIG3 is a schematic diagram of an example of the PDCP discard report format, showing a format of a PDCP control PDU as a PDCP discard report, taking COUNT_start and length as an example.
  • the PDCP control PDU can use 0 as the D/C bit in the PDCP header to indicate that it is a control PDU, and define a new PDU Type (for example, the binary bit is 100) to indicate that the PDU is a PDCP discard report.
  • COUNT_start is 32 bits, and length is 8 bits (it can also be 16 bits, etc.).
  • the report can contain multiple sets of COUNT_start and length, indicating that multiple consecutive SDU segments (such as multiple PDU Sets) have been discarded.
  • the problem of sequence number interval is solved, the reordering delay at the receiving end is reduced, and the service performance is improved.
  • the present application embodiment provides a data processing method, which is described from the side of a receiving device.
  • the receiving device may be a network device or a terminal device, which is a processing method of a receiving end corresponding to the embodiment of the second aspect.
  • the contents that are the same as those in the embodiment of the second aspect will not be described again.
  • FIG. 4 is a schematic diagram of a data processing method according to an embodiment of the present application. As shown in FIG. 4 , the method includes:
  • the receiving device After receiving the sequence number information of the discarded PDCP SDU, the receiving device saves or records the sequence number information of the discarded PDCP SDU;
  • the receiving device delivers the stored PDCP SDU to the upper layer according to the sequence number information of the discarded PDCP SDU.
  • FIG. 4 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order between the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced.
  • Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 4.
  • the sequence number information of the discarded PDCP SDU (such as PDCP discard report, as shown in FIG3)
  • the sequence number (such as COUNT value) information of the discarded PDCP SDU is saved or recorded, and then, according to the sequence number information of the discarded PDCP SDU, there is no need to wait for these discarded PDCP SDUs (also similar to assuming that these SDUs have been received), and the received (that is, stored) (COUNT value before COUNT_end) PDCP SDU is directly delivered to the upper layer.
  • the problem of sequence number interval is solved, the reordering delay of the receiving end is reduced, and the service performance is improved.
  • the above discard report is for downlink data and is issued by the network side (network device); correspondingly, if the receiving end is a network device, the above discard report is for uplink data and is issued by the UE.
  • the above-mentioned sequence number information includes the COUNT value of the first PDCP SDU among the discarded consecutive PDCP SDUs and the number of the discarded consecutive PDCP SDUs, that is, COUNT_start and length; or, the above-mentioned sequence number information includes the COUNT value of the first PDCP SDU among the discarded consecutive PDCP SDUs and the COUNT value of the last PDCP SDU, that is, COUNT_start and COUNT_end.
  • COUNT_end can be calculated through COUNT_start.
  • the above sequence number information may be sent via a PDCP control PDU.
  • a PDCP control PDU For details, please refer to the embodiment of the second aspect, which will not be described in detail here.
  • the receiving device maintains four state variables, namely, a first state variable RX_DELIV, a second state variable RX_NEXT, a third state variable RX_DISCOARD0, and a fourth state variable RX_DELIV.
  • RX_DISCARD1 a first state variable
  • RX_DISCARD1 a second state variable
  • RX_DISCARD0 a third state variable
  • RX_DISCARD0 a fourth state variable
  • the first state variable RX_DELIV indicates the COUNT value of the first PDCP SDU that has not been submitted to the upper layer but is still waiting to be received;
  • the second state variable RX_NEXT indicates the COUNT value of the next PDCP SDU expected to be received;
  • the third state variable RX_DISCARD0 corresponds to COUNT_start, indicating the COUNT value of the first discarded PDCP SDU of the sending device's sending PDCP entity;
  • the fourth state variable RX_DISCARD1 corresponds to COUNT_end (or COUNT_start+length-1, if the PDCP discard report uses length), indicating the COUNT value of the last discarded PDCP SDU of the sending device's sending PDCP entity.
  • the third state variable and the fourth state variable are variables maintained by the newly introduced receiving PDCP entity, and this application does not limit their names, and they can also be called other variable names.
  • the receiving device delivers the stored PDCP SDU to the upper layer, including: the receiving device delivers the PDCP SDUs whose COUNT values in the stored PDCP SDUs are less than or equal to the fourth state variable to the upper layer in sequence.
  • Figures 5 to 8 are schematic diagrams of several examples of the size relationship between the third state variable and the fourth state variable and the first state variable and the second state variable, showing the sequence numbers of the PDCP SDUs received and not received by the receiving end and the values of the corresponding state variables.
  • the receiving device upon receiving a PDCP discard report, performs the following operations:
  • the third state variable is updated to the COUNT value of the first PDCP SDU among the consecutive PDCP SDUs discarded in the discard report;
  • the fourth state variable is updated to the COUNT value of the first PDCP SDU among the discarded consecutive PDCP SDUs plus the value of the number of discarded consecutive PDCP SDUs minus 1.
  • the receiving device may further perform at least one of the following operations:
  • All stored PDCP SDUs are sorted in ascending order of associated COUNT values after performing header decompression Submit to the upper layer until the COUNT value is less than or equal to the fourth state variable;
  • the second state variable is updated to the maximum value between the first state variable and the second state variable before the update.
  • the receiving device may further maintain a fifth state variable RX_REORD, where the fifth state variable RX_REORD is used to indicate the next COUNT value of the COUNT value associated with the PDCP data PDU that triggers the reordering timer (t-Reordering).
  • the receiving device may further perform at least one of the following operations:
  • the fifth state variable is updated to the value of the second state variable and the reordering timer is started.
  • taking UE as a receiving device when the UE receives a PDCP discard report, it updates the state variable value of the receiving end. For example, after it compares the above state variables and confirms that it belongs to the scenario shown in Figure 5 or 6, it can perform the above operations to consider the discarded PDCP SDU and submit the PDCP SDU that can be delivered at present to the upper layer.
  • the receiving PDCP entity performs the following operations:
  • TS 38.323 may be enhanced.
  • TS 38.323 may include the following description:
  • the receiving device performs at least one of the following operations:
  • All stored PDCP SDUs are sorted in ascending order of associated COUNT values after performing header decompression. Submit to the upper layer until the COUNT value is less than or equal to the fourth state variable;
  • the second state variable is updated to the maximum value between the first state variable and the second state variable before the update.
  • the receiving device may perform the above operation when receiving a PDCP data PDU from a lower layer.
  • the receiving PDCP entity For example, if the received PDCP data PDU is not discarded (ie, a data PDU with the same COUNT has not been received before), the receiving PDCP entity:
  • TS 38.323 may be enhanced.
  • TS 38.323 may include the following description:
  • the PDCP entity of the receiving device is not configured with outOfOrderDelivery. That is, the above enhancement can be performed without configuring outOfOrderDelivery, that is, the PDCP entity needs to deliver the received PDCP SDU to the higher layer on demand.
  • the problem of sequence number interval is solved, the reordering delay at the receiving end is reduced, and the service performance is improved.
  • An embodiment of the present application provides a data processing device.
  • FIG9 is a schematic diagram of a data processing device according to an embodiment of the present application.
  • the device may be, for example, a terminal device, or may be one or more components or assemblies configured in the terminal device. Since the principle of solving the problem by the device is the same as that of the embodiment of the first aspect, its specific implementation may refer to the embodiment of the first aspect. The implementation of the method will not be repeated for the same contents.
  • the data processing device 900 includes:
  • a processing unit 901 which discards all PDCP SDUs and their corresponding PDCP data PDUs in a PDU Set, or considers that the discard timers of all PDCP SDUs in the PDU Set have timed out when at least one of the following conditions associated with the PDU Set is satisfied;
  • the discard timer corresponding to a PDCP SDU expires, and the PDCP SDU belongs to the above PDU Set;
  • a PDCP SDU belonging to the above PDU Set is not confirmed as successfully delivered by the PDCP status report, and the PSII of the above PDU Set is configured;
  • the PDCP layer of the terminal device receives an indication that a PDCP data PDU exceeds the maximum number of transmission times, and the SDU corresponding to the PDCP data PDU belongs to the above-mentioned PDU Set, and the above-mentioned PDU Set is configured with PSII.
  • the discard timer corresponding to the PDU Set times out including: the sending PDCP entity of the terminal device maintains a discard timer for the PDU Set, and the discard timer times out.
  • the sending PDCP entity of the terminal device when the sending PDCP entity of the terminal device receives a PDCP SDU from the higher layer, if the PDCP SDU belongs to the application-level PDU Set and is the first PDU in the above PDU Set, the sending PDCP entity of the terminal device starts the discard timer associated with the above PDU Set.
  • the processing unit 901 discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the above-mentioned PDU Set by sending a PDCP entity.
  • the first threshold may be predefined or configured by the network device through RRC signaling.
  • the processing unit 901 discards all PDCP SDUs and their corresponding PDCP data PDUs belonging to the above-mentioned PDU Set by sending a PDCP entity.
  • the second threshold may be predefined or configured by the network device through RRC signaling.
  • the PDCP layer of the terminal device receives an indication that a PDCP data PDU exceeds the maximum number of transmissions, including: when an RLC SDU exceeds the maximum number of retransmissions, the RLC layer of the terminal device indicates to the PDCP layer that the RLC SDU has reached the maximum number of retransmissions, and the RLC SDU corresponds to the aforementioned PDCP Data PDU.
  • Fig. 10 is another schematic diagram of a data processing device according to an embodiment of the present application
  • the device may be, for example, a sending device, or may be one or more components or assemblies configured in the sending device
  • the sending device may be a terminal device, or may be a network device. Since the principle of solving the problem by the device is the same as the method of the embodiment of the second aspect, its specific implementation may refer to the implementation of the method of the embodiment of the second aspect, and the same contents will not be repeated.
  • the data processing device 1000 includes:
  • the sending unit 1001 sends the sequence number information of the PDCP SDUs associated with the PDCP sequence number to the receiving device after the sending device discards all the PDCP SDUs corresponding to a PDU Set.
  • the sequence number information includes a COUNT value of the first PDCP SDU among the consecutive PDCP SDUs discarded and the number of consecutive PDCP SDUs discarded.
  • the sequence number information includes a COUNT value of a first PDCP SDU and a COUNT value of a last PDCP SDU in consecutive PDCP SDUs that are discarded.
  • the sequence number information may be sent via a PDCP control PDU.
  • FIG11 is another schematic diagram of a data processing device according to an embodiment of the present application, wherein the device may be, for example, a receiving device, or may be one or more components or assemblies configured in the receiving device, and the receiving device may be a network device or a terminal device. Since the principle of solving the problem by the device is the same as that of the method of the embodiment of the third aspect, its specific implementation may refer to the implementation of the method of the embodiment of the third aspect, and the same contents will not be repeated.
  • the data processing device 1100 includes:
  • a first processing unit 1101 which stores or records the sequence number information of the discarded PDCP SDU after the receiving device receives the sequence number information of the discarded PDCP SDU;
  • the second processing unit 1102 delivers the stored PDCP SDU to the upper layer according to the sequence number information of the discarded PDCP SDU.
  • the sequence number information includes the COUNT value of the first PDCP SDU among the discarded consecutive PDCP SDUs and the number of discarded consecutive PDCP SDUs; or, the sequence number information includes the COUNT value of the first PDCP SDU among the discarded consecutive PDCP SDUs and the COUNT value of the last PDCP SDU.
  • the sequence number information is sent via a PDCP control PDU.
  • the receiving device maintains the following four state variables:
  • the first state variable (RX_DELIV) indicates the COUNT value of the first PDCP SDU that has not been delivered to the upper layer but is still waiting to be received;
  • a third state variable (RX_DISCARD0), which indicates the COUNT value of the first discarded PDCP SDU of the transmitting PDCP entity of the transmitting device;
  • the fourth state variable (RX_DISCARD1) indicates the COUNT value of the last discarded PDCP SDU of the sending PDCP entity of the sending device.
  • the second processing unit 1102 delivers the stored PDCP SDU to a higher layer, including:
  • the second processing unit 1102 delivers the SDUs whose COUNT values in the stored PDCP SDUs are less than or equal to the fourth state variable to the higher layer in sequence.
  • the second processing unit 1102 further performs the following operations:
  • the fourth state variable is updated to the COUNT value of the first PDCP SDU among the discarded consecutive PDCP SDUs plus the value of the number of discarded consecutive PDCP SDUs minus 1.
  • the second processing unit 1102 may further perform at least one of the following operations:
  • the second state variable is updated to be the maximum value between the first state variable and the first state variable before the update.
  • the receiving device may also maintain a fifth state variable (RX_REORD).
  • the state variable indicates the next COUNT value of the COUNT value associated with the PDCP data PDU that triggered the reordering timer.
  • the second processing unit 1102 may further perform at least one of the following operations:
  • the fifth state variable is updated to the value of the second state variable and the reordering timer is started.
  • the second processing unit 1102 may further perform at least one of the following operations:
  • the second state variable is updated to the maximum value between the first state variable and the second state variable before the update.
  • the second processing unit 1102 may perform the above operation when the receiving device receives a PDCP data PDU from a lower layer.
  • the PDCP entity of the receiving device is not configured with outOfOrderDelivery. That is, the above apparatus 1100 can perform the above operation when the PDCP entity of the receiving device is not configured with outOfOrderDelivery.
  • the data processing devices 900, 1000, 1100 of the present application embodiments may also include other components or modules, and the specific contents of these components or modules may refer to the relevant technology.
  • FIG9 to FIG11 only exemplarily illustrate the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned various components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.
  • the problem of discarding PDU Set data in the wireless access network is solved, and it can be used to better support XR and media service applications.
  • a discard report is introduced, and by enhancing the sending and receiving ends, the problem of sequence number gaps caused by data discard is solved, and the reordering delay is reduced, thereby improving the transmission performance of the XRM service.
  • the processing of differentiated PDU Sets can be guaranteed and the integrated data processing requirements of PDU Sets can be met.
  • the embodiment of the present application provides a communication system, including a terminal device and a network device, wherein the terminal device is configured to execute the method described in any one of the first to third aspects, or the network device is configured to execute the method described in the second or third aspects.
  • the behaviors of the terminal device and the network device have been described in detail in the embodiments of the first to third aspects, and the contents are incorporated herein and will not be repeated here.
  • An embodiment of the present application further provides a terminal device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method described in any one of the first to third aspects.
  • FIG12 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1200 may include a processor 1201 and a memory 1202; the memory 1202 stores data and programs and is coupled to the processor 1201. It is worth noting that the figure is exemplary; other types of structures may also be used to supplement or replace the structure to implement telecommunication functions or other functions.
  • the processor 1201 may be configured to execute a program to implement the method described in the embodiments of any one of the first to third aspects.
  • the terminal device 1200 may further include: a communication module 1203, an input unit 1204, a display 1205, and a power supply 1206.
  • the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1200 does not necessarily include all the components shown in FIG12 , and the above components are not necessary; in addition, the terminal device 1200 may also include components not shown in FIG12 , and reference may be made to the prior art.
  • An embodiment of the present application further provides a network device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method described in the embodiment of the second aspect or the third aspect.
  • FIG13 is a schematic diagram of a network device according to an embodiment of the present application.
  • the network device 1300 may include: a central processing unit (CPU) 1301 and a memory 1302; the memory 1302 is coupled to the central processing unit 1301.
  • the memory 1302 may store various data; in addition, it may store information processing programs, and execute the programs under the control of the central processing unit 1301 to receive various information sent by the terminal device and send various information to the terminal device.
  • the processor 1301 may be configured to execute a program to implement the method described in the embodiments of the second aspect or the third aspect.
  • the network device 1300 may further include: a transceiver 1303 and an antenna 1304, etc.; wherein the functions of the above components are similar to those of the prior art and are not described in detail here. It is worth noting that the network device 1300 does not necessarily include all the components shown in FIG13 ; in addition, the network device 1300 may also include components not shown in FIG13 , which may refer to the prior art.
  • An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program enables a computer to execute the method described in the embodiment of any one of the first to third aspects in the terminal device.
  • An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in any one of the first to third aspects in a terminal device.
  • An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a network device, the program enables a computer to execute the method described in the embodiment of the second aspect or the third aspect in the network device.
  • An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in the embodiment of the second aspect or the third aspect in a network device.
  • the above devices and methods of the present application can be implemented by hardware, or by hardware combined with software.
  • the present application relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, or enables the logic component to implement the various methods or steps described above.
  • the logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • a software module executed by a processor or a combination of the two.
  • one or more of the functional block diagrams shown in the figure and/or one or more of the functional block diagrams The multiple combinations may correspond to various software modules of the computer program flow or to various hardware modules.
  • These software modules may correspond to various steps shown in the figure.
  • These hardware modules may be implemented by solidifying these software modules using, for example, a field programmable gate array (FPGA).
  • FPGA field programmable gate array
  • the software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • a storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor.
  • the processor and the storage medium may be located in an ASIC.
  • the software module may be stored in a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.
  • the functional blocks described in the drawings and/or one or more combinations of functional blocks it can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present application.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • it can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.
  • a data processing method applied to a terminal device, wherein the method comprises:
  • the terminal device discards all PDCP SDUs and their corresponding PDCP data PDUs in a PDU Set, or considers that the discard timers of all PDCP SDUs belonging to the PDU Set have timed out, if at least one of the following conditions associated with the PDU Set is met:
  • a discard timer corresponding to a PDCP SDU expires, and the PDCP SDU belongs to the PDU Set;
  • a PDCP SDU belonging to the PDU Set is not confirmed as successfully delivered by a PDCP status report, and the PSII of the PDU Set is configured;
  • the PDCP layer of the terminal device receives an indication that a PDCP data PDU exceeds the maximum number of transmission times, and the SDU corresponding to the PDCP data PDU belongs to the PDU Set, and the PDU Set is configured with PSII.
  • the discard timer corresponding to the PDU Set times out including: the sending PDCP entity of the terminal device maintains a discard timer for the PDU Set, and the discard timer times out.
  • the sending PDCP entity of the terminal device When the sending PDCP entity of the terminal device receives a PDCP SDU from the higher layer, if the PDCP SDU belongs to the application-level PDU Set and is the first PDU in the PDU Set, the sending PDCP entity of the terminal device starts the discard timer associated with the PDU Set.
  • the sending PDCP entity of the terminal device discards all PDCP SDUs belonging to the PDU Set and their corresponding PDCP data PDUs.
  • the sending PDCP entity of the terminal device discards all PDCP SDUs belonging to the PDU Set and their corresponding PDCP data PDUs.
  • the RLC layer of the terminal device When an RLC SDU exceeds the maximum number of retransmissions, the RLC layer of the terminal device indicates to the PDCP layer that the RLC SDU has reached the maximum number of retransmissions, and the RLC SDU corresponds to the PDCP data PDU.
  • the threshold is predefined or configured by the network device through RRC signaling.
  • a data processing method applied to a sending device, wherein the sending device is a terminal device or a network device, wherein the method comprises:
  • the sending device After discarding all PDCP SDUs corresponding to a PDU Set, the sending device sends the sequence number information of the PDCP SDUs associated with the PDCP sequence number to the receiving device.
  • the sequence number information includes the COUNT value of the first PDCP SDU in the discarded consecutive PDCP SDUs and the number of the discarded consecutive PDCP SDUs; or
  • the sequence number information includes the COUNT value of the first PDCP SDU and the COUNT value of the last PDCP SDU in the discarded consecutive PDCP SDUs.
  • the sequence number information is sent via the PDCP control PDU.
  • a data processing method applied to a receiving device, wherein the receiving device is a network device or a terminal device, wherein the method comprises:
  • the receiving device After receiving the sequence number information of the discarded PDCP SDU, the receiving device saves or records the sequence number information of the discarded PDCP SDU;
  • the receiving device delivers the stored PDCP SDU to the upper layer according to the sequence number information of the discarded PDCP SDU.
  • the sequence number information includes the COUNT value of the first PDCP SDU in the discarded consecutive PDCP SDUs and the number of the discarded consecutive PDCP SDUs; or
  • the sequence number information includes the COUNT value of the first PDCP SDU and the COUNT value of the last PDCP SDU in the discarded consecutive PDCP SDUs.
  • the sequence number information is sent via the PDCP control PDU.
  • the receiving device maintains the following four state variables:
  • the first state variable (RX_DELIV) indicates the COUNT value of the first PDCP SDU that has not been delivered to the upper layer but is still waiting to be received;
  • the third state variable (RX_DISCARD0) indicates the first state of the transmitting PDCP entity of the transmitting device. COUNT value of discarded PDCP SDUs;
  • the fourth state variable (RX_DISCARD1) indicates the COUNT value of the last discarded PDCP SDU of the sending PDCP entity of the sending device.
  • the receiving device delivers the SDUs whose COUNT values in the stored PDCP SDUs are less than or equal to the fourth state variable to the higher layer in sequence, and the fourth state variable indicates the COUNT value of the last discarded PDCP SDU of the sending PDCP entity of the sending device.
  • the receiving device performs the following operations:
  • the fourth state variable is updated to the COUNT value of the first PDCP SDU among the discarded consecutive PDCP SDUs plus the value of the number of the discarded consecutive PDCP SDUs minus 1.
  • the receiving device further performs at least one of the following operations:
  • the fourth state variable is less than the second state variable minus 1, submitting all stored associated PDCP SDUs having consecutive COUNT values starting from the fourth state variable+1 to a higher layer in ascending order of COUNT values;
  • the second state variable is updated to a maximum value between the first state variable and the first state variable before updating.
  • the receiving device further maintains a fifth state variable (RX_REORD), the fifth state variable indicating a next COUNT value of the COUNT value associated with the PDCP data PDU that triggers the reordering timer;
  • the receiving device further performs at least one of the following operations:
  • the fifth state variable is updated to the value of the second state variable, and the reordering timer is started.
  • the receiving device performs at least one of the following operations:
  • the fourth state variable is less than the second state variable minus 1, submitting all stored associated PDCP SDUs having consecutive COUNT values starting from the fourth state variable+1 to a higher layer in ascending order of COUNT values;
  • the second state variable is updated to a maximum value between the first state variable and the second state variable before updating.
  • the receiving device performs the operation when receiving a PDCP data PDU from a lower layer.
  • the PDCP entity of the receiving device is not configured with outOfOrderDelivery.
  • a terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 21.
  • a network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 8 to 21.
  • a communication system comprising a terminal device and a network device, wherein the terminal device is configured to execute the method described in any one of Notes 1 to 21, and/or the network device is configured to execute the method described in any one of Notes 8 to 21.

Landscapes

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

Abstract

本申请实施例提供了一种数据处理方法和装置，所述方法包括：终端设备在与一PDU Set关联的以下条件至少之一满足的情况下，丢弃该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU，或者认为属于该PDU Set中的所有PDCP SDU的丢弃定时器都超时；这些条件包括：一PDCP SDU对应的丢弃定时器到期，且该PDCP SDU属于上述PDU Set；该PDU Set对应的丢弃定时器超时；属于该PDU Set的一PDCP SDU没有被PDCP状态报告确认为成功送达，且该PDU Set的PSII被配置；终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，且该PDCP数据PDU对应的SDU属于上述PDU Set，且上述PDU Set被配置了PSII。根据本申请实施例的一方面，保证了PDU Set的完整性或是内容的有效性，节约了网络资源。

Description

数据处理方法和装置 技术领域
本申请涉及通信领域。
背景技术
3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)在Release 18(版本)中开始研究针对扩展现实(eXtended Reality，XR)业务的增强，XR业务指的是计算机技术和可穿戴设备产生的所有现实和虚拟组合的环境和人机交互。其应用领域包括但不限于娱乐、医疗、教育等。XR业务可以包括虚拟现实(Virtual reality，VR)业务、增强现实(Augmented reality，AR)业务和混合现实(Mixed reality，MR)业务。
虚拟现实是发布的视觉和音频场景的渲染版本，当观察者或用户在应用程序定义的限制内移动时，渲染旨在尽可能自然地模拟现实世界的视觉和听觉感官刺激。增强现实是指向用户提供附加信息或人工生成的项目或覆盖在其当前环境上的内容。混合现实是AR的一种高级形式，其中一些虚拟元素被插入到物理场景中，目的是提供一种错觉，让人感觉这些元素是真实场景一部分。
PDU集(PDU Set)由一个或多个PDU(Protocol Data Unit，协议数据单元)组成，这些PDU携带了在应用层生成的一个信息单元的有效载荷(例如，用于XR和媒体服务的帧或视频切片)。在一些实施方式中，应用层需要PDU Set中的所有PDU来使用相应的信息单元。在其他实施方式中，当某些PDU丢失时，应用层仍然可以恢复全部或部分信息单元。需要说明的是，这里的PDU是应用级别的PDU，也即PDU会话层中的PDU，通常是指IP包护着以太网帧。在AS(access stratum，接入层)的各协议栈中，每个子层也有相应的PDU，比如PDCP PDU(分组数据汇聚协议PDU)，RLC PDU(无线链路控制PDU)等。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，为了解决PDU Set的处理需求，目前对下行数据传输提出了控制面和用户面的增强。而在下行传输中，如何利用以上增强信息需要进行进一步标准化和技术实现。另外，对于上行传输，目前没有技术可以解决PDU Set的集成数据包处理和PDU Set的差异化处理，其中包括如何进行PDU Set数据丢弃。
针对上述问题至少之一或者其他类似问题，本申请实施例提供了一种数据处理方法和装置。
根据本申请实施例的一方面，提供一种数据处理装置，配置于终端设备，所述装置包括：
处理单元，其在与一PDU Set关联的以下条件至少之一满足的情况下，丢弃所述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU，或者认为属于所述PDU Set中的所有PDCP SDU的丢弃定时器都超时；
一PDCP SDU对应的丢弃定时器到期，且所述PDCP SDU属于所述PDU Set；
所述PDU Set对应的丢弃定时器超时；
属于所述PDU Set的一PDCP SDU没有被PDCP状态报告确认为成功送达，且所述PDU Set的PSII被配置；
所述终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，且所述PDCP数据PDU对应的SDU属于所述PDU Set，且所述PDU Set被配置了PSII。
根据本申请实施例的另一方面，提供一种数据处理装置，配置于发送设备，所述发送设备为终端设备或者网络设备，所述装置包括：
发送单元，其在发送设备丢弃了一PDU Set对应的所有PDCP SDU之后，将其中已经关联了PDCP序列号的PDCP SDU的序列号信息发送给接收设备。
根据本申请实施例的再一方面，提供一种数据处理装置，配置于接收设备，所述接收设备为网络设备或者终端设备，所述装置包括：
第一处理单元，其在所述接收到设备接收到丢弃的PDCP SDU的序列号信息后，保存或记录所述丢弃的PDCP SDU的序列号信息；
第二处理单元，其根据所述丢弃的PDCP SDU的序列号信息，将存储的PDCP SDU递交到高层。
本申请实施例的有益效果之一在于：根据本申请实施例，一方面，解决了将PDU Set在无线接入网的数据丢弃的问题，可以用于更好地支持XR和媒体业务应用。另一方面，引入了丢弃报告，通过对发送端和接收端进行增强，解决了由于数据丢弃导致的序列号间隙的问题，减少了重排序延迟，从而提高XRM业务的传输性能。由此，可以保障差异化的PDU Set的处理以及满足PDU Set的集成数据处理需求。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是本申请实施例的数据处理方法的一示意图；
图2是本申请实施例的数据处理方法的另一示意图；
图3是PDCP丢弃报告格式的一个示例的示意图；
图4是本申请实施例的数据处理方法的又一示意图；
图5至图8是第三状态变量和第四状态变量与第一状态变量和第二状态变量之间的大小关系的几个示例的示意图；
图9是本申请实施例的数据处理装置的一示意图；
图10是本申请实施例的数据处理装置的另一示意图；
图11是本申请实施例的数据处理装置的再一示意图；
图12是本申请实施例的终端设备的一示意图；
图13是本申请实施例的网络设备的一示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信 网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、收发节点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，还可以是IAB-MT，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
目前，5G技术正在研究支持先进媒体服务的关键问题、解决方案和结论，例如高数据速率低延迟(HDRLL，High Data Rate Low Latency)服务、AR/VR/XR服务和触觉/多模态通信服务。目标包括：
1.支持多模式服务的增强功能，包括：
-研究是否以及如何启用应用程序在类似时间向用户提供相关的触觉和多模式 数据(例如，与特定时间相关的音频、视频和触觉数据)，重点关注增强策略控制的需求(例如QoS策略协调)。
2.增强网络暴露以支持5GS(5G系统)与应用程序之间的交互，包括：
-研究是否以及如何在多个UE之间或每个UE的多个QoS流之间进行应用同步和QoS(Quality of Service，服务质量)策略协调，以及如何在AF和5GS之间进行交互。
-研究5GS QoS信息(例如QoS能力)和网络条件对应用程序的暴露，以实现快速编解码器/速率自适应，有助于提供所需的QoE(例如帮助缓解5GS拥塞)。
3.研究是否以及如何针对XR服务和媒体服务传输执行以下QoS和策略增强，包括：
-研究能够提高网络资源使用率和QoE(Quality of Experience，体验质量)的媒体服务的流量特性。
-增强QoS框架以支持PDU Set粒度(例如视频/音频帧/tile、应用数据单元、控制信息)，其中，PDU Set由具有相同QoS要求的PDU组成。
-考虑到PDU Set的不同重要性，支持差异化的QoS处理。例如，合法丢弃属于不太重要的PDU Set的数据包，以减少资源浪费。
-是否以及如何支持上行链路-下行链路传输协调以满足UE到UPF(User Plane Function，用户面功能)的N6终结点之间的RTT(Round Trip Time，往返时间)延迟要求。
-潜在的策略增强以最大限度地减少抖动，重点是来自AF(Application Function，应用功能)的需求供应、PCC(policy and charging control，策略和计费控制)规则的扩展。
发明人发现，PDU Set具有不同QoS需求，比如优先级、重要性等。现有基于QoS流的QoS模型不能支持PDU Set的不同QoS需求。具体来说，PDU Set的处理有两大需求：PDU Set的集成数据包处理和PDU Set的差异化处理。
对于PDU Set的集成数据包处理，在当前的5GS中，QoS流是PDU会话中QoS区分的最细粒度。5G QoS特性由5QI(5G QoS Identifier，5G QoS标识符)确定。这意味着QoS流中的每个数据包都根据相同的QoS要求进行处理。
其中，对于XR/媒体服务，一组数据包用于承载PDU Set的有效载荷(例如，帧、 视频切片/tile)。在媒体层，这样一个PDU Set中的数据包被作为一个整体进行解码/处理。例如，只有在承载帧/视频切片的所有或一定数量的数据包被成功传送的情况下，才可以对帧/视频切片进行解码。例如，只有在成功接收到该帧所依赖的所有帧的情况下，客户端才能解码GOP(group of pictures，图片组)中的帧。因此，PDU Set中的数据包组在媒体层中具有内在的相互依赖性。如果不考虑PDU Set中数据包之间的这种依赖关系，5GS可能会以低效率执行调度。例如，5GS可能会随机丢弃一个或多个数据包，但会尝试传送同一PDU Set的其他数据包，这些数据包对客户端无用，从而浪费无线电资源。
对于PDU Set差异化处理，XR/媒体服务的特点是高数据速率和低延迟。在Rel-18版本中，预计5GS QoS框架将得到增强，以支持PDU Set的不同QoS处理。PDU Set可以承载不同的内容，例如I/B/P帧、I/B/P帧内的切片/tile等。这个关键问题提出支持差异化的QoS处理，考虑到PDU Set的不同重要性，例如通过差异化地对待属于不太重要的PDU Set的数据包(即PDU)来减少资源浪费。
为了解决PDU Set的处理需求，目前对下行数据传输提出了控制面和用户面的增强。
其中，控制面增强包括定义以下PDU Set QoS参数：
PDU Set错误率(PSER，PDU Set Error Rate)，指链路层协议(比如3GPP接入的RAN中的RLC)的发送端已经处理的PDU Set但是没有成功递交(deliver)到对应收端的高层(比如3GPP接入的RAN中的PDCP)的比例的上限值；
PDU Set延迟预算(PSDB，PDU Set Delay Budget)，定义了一个PDU Set可以经历的在UE和UPF的N6终结点之间传输的延迟(也就是从收到第一个PDU到成功递交最后到达的PDU Set中的PDU之间的时间)的上限；
PDU Set完整性指示(PSII，PDU Set Integrated Indication)，指示应用层为了使用PDU Set是否需要所有的PDU。
此外，用户面增强包括UPF识别PDU Set相关的如下信息：PDU Set序列号、PDU Set的最后一个PDU标记、PDU Set内部的PDU序列号、PDU Set的大小、PDU Set重要性(Importance)。
发明人发现，在下行传输中，如何利用以上增强信息需要进行进一步标准化和技术实现。并且，对于上行传输，目前没有技术可以解决PDU Set的集成数据包处理和 PDU Set的差异化处理，其中包括如何进行PDU Set数据丢弃。
另外，对于上行流量，UE的NAS(non-access stratum，非接入层)层可以识别PDU Set相关的信息。和下行流量类似，这些PDU Set相关信息可以包括PDU Set标识、PDU Set内的PDU序列号、PDU Set Importance(重要性)，可选的，还可以包括PDU Set的开始和/或结束标志、PDU Set的大小等。其中，PDU Set Importance表明了PDU Set在XRM(XR以及多媒体)服务流中的重要性高低，或者是优先级，比如可以是高、中、低，或者是0～Nmax数字表达，用于在RAN对PDU Set进行差异化处理，比如优先级处理，调度，数据丢弃等。
此外，对于上游数据包的分类，可以在PDU会话建立/修改期间，根据PDU会话的S-NSSAI/DNN(Single Network Slice Selection Assistance Information/Data Network Name，单网络切片选择辅助信息/数据网络名称)为UE准备PDU Set Importance。PDU Set Importance规则可以从5GC(5G核心网)通过会话管理过程中定义的N1SM容器发送给UE。PDU Set Importance可以用于UE将PDU Set映射到合适的MAC(medium access control，媒体接入控制)传输缓存。如果PDU Set Importance用于QoS流或者是子QoS流的映射，UE根据QoS规则对上行用户平面流量进行分类和标记，即XRM的上行流量与QoS流和/或子QoS流的关联。
本申请考虑在PDCP(Packet Data Convergence Protocol，分组数据汇聚层协议)层进行PDU Set的丢弃和相关操作。对于上行传输，PDCP层需要知道上行数据PDU Set的相关信息。这些信息可以由UE实现决定，也就是UE上层识别PDU Set相关的信息之后通过内部接口传递给PDCP层；也可以由UE通过在SDAP(Service Data Adaptation Protocol，服务数据适配协议)层的上行数据报头中添加PDU Set的相关信息，从而传递给PDCP层。
下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。在下面的说明中，“如果…”、“在…的情况下”、“当…时”等说法含义相同，可以互换。此外，在下面的说明中，如无特别说明，PDU是指PDU会话中的PDU。
第一方面的实施例
现有技术中，PDCP层的数据丢弃功能是针对PDCP SDU(service data unit，服 务数据单元)。发送PDCP实体(transmitting PDCP entity)为每个PDCP SDU维护一个丢弃定时器(discardTimer)。该丢弃定时器只针对DRB(data radio bearer，数据无线承载)配置。定时器的时长(duration，也就是定时器启动时的初始值)由高层(RRC，radio resource control，无线资源控制)配置。在数据发送端，当PDCP层从上层收到一个SDU时，启动一个新的丢弃定时器。当某个PDCP SDU的丢弃定时器超时，或者某个PDCP SDU通过PDCP状态报告被确认成功送达(deliver)的时候，发送PDCP实体需要将该PDCP SDU以及对应的PDCP数据PDU进行丢弃。
一般情况下，PDU Set具有一定的内容准则，内容准则是指用于判断PDU Set是否可以认为是成功送达的标准。例如，如果某PDU Set被配置了PSII(指PDU Set完整性指示为真)，那么该PDU Set只有在全部比特都正确送达的情况下才对接收端有用，也就是不能容忍任何错误。这样的话，如果某PDU Set被配置了PSII，当确认一个PDU没有被成功送达，可以丢弃该PDU属于的PDU Set。
在本申请实施例中，由于PDU Set通常具有相同的到达时间要求，可以考虑将PDU Set作为一个整体进行丢弃；或者是在配置了PSII的情况下发送端可以丢弃确认了存在没有成功送达的PDU的PDU Set。
针对上述问题至少之一，本申请实施例提供一种数据处理方法，从终端设备的一侧进行说明。图1是本申请实施例的数据处理方法的一示意图。如图1所示，该方法包括：
101：终端设备在与一PDU Set关联的以下条件至少之一满足的情况下，丢弃所述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU，或者认为属于所述PDU Set中的所有PDCP SDU的丢弃定时器都超时，这些条件包括：
一PDCP SDU对应的丢弃定时器到期，且所述PDCP SDU属于所述PDU Set；
所述PDU Set对应的丢弃定时器超时；
属于所述PDU Set的一PDCP SDU没有被PDCP状态报告确认为成功送达，且所述PDU Set的PSII被配置；
所述终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，且所述PDCP数据PDU对应的SDU属于所述PDU Set，且所述PDU Set被配置了PSII。
值得注意的是，以上附图1仅示意性地对本申请实施例进行了说明，但本申请不 限于此。例如可以增加其他的一些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图1的记载。
根据上述实施例，考虑了内容准则进行数据丢弃，保证了PDU Set的完整性或者是内容的有效性，节约了网络资源。
在一些实施例中，当某个PDCP SDU对应的丢弃定时器超时，且该PDCP SDU属于(应用层的)PDU Set，则终端设备的发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，在终端设备进行上行传输时，每个PDCP SDU仍然使用单独的丢弃定时器，该丢弃定时器的初始值、启动方法等可以参考相关技术，此处省略说明。
根据上述实施例，可以对TS 38.323的描述进行增强，例如，TS 38.323可以包含如下描述：
在一些实施例中，当某个PDCP SDU对应的丢弃定时器超时，且该PDCP SDU属于(应用层的)PDU Set，则属于该PDU Set中的所有PDCP SDU的丢弃定时器都被认为超时。也即，终端设备认为属于该PDU Set中的所有PDCP SDU的丢弃定时器都超时。
在一些实施例中，当某个PDU Set对应的丢弃定时器超时，则终端设备的发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，属于同一PDU Set的PDU(也即PDCP SDU)共享同一个丢弃定时器。也即，终端设备的发送PDCP实体为每个PDU Set维护一个丢弃定时器。该丢弃定时器的时长可以根据PSDB进行配置，也可以由网络设备进行配置，本申请对此不做限制。
在上述实施例中，当终端设备的发送PDCP实体从高层收到一个PDCP SDU时，如果该PDCP SDU属于应用级别的PDU Set，也即，属于PDU Set中的一个PDU，或者是关联到某个PDU Set，并且，该PDCP SDU是该PDU Set中的第一个PDU，例如，具有第一个PDU序列号的PDU，该第一个PDU的PDU序列号例如为0，则终端设备的发送PDCP实体启动该PDU Set关联的丢弃定时器(如果配置了的话)。
由此，当某个PDU Set关联的或对应的丢弃定时器超时，发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
根据上述实施例，可以对TS 38.323的描述进行增强，例如，TS 38.323可以包含如下描述：
在前述各实施例中，将PDU Set的传输时延作为一个整体考虑，从而满足了PDU Set的PSDB需求。
在又一些实施例中，终端设备可以根据PDCP状态报告来确定是否进行PDCP Set的丢弃。
在上述实施例中，PDU Set具有一定的内容准则，也即，用于判断PDU Set是否可以认为是成功送达的标准。
例如，如果某PDU Set被配置了PSII(指PDU Set完整性指示为真)，那么该PDU Set只有在全部比特都正确送达的情况下才对接收端有用，也就是不能容忍任何错误。这样的话，如果某PDU Set被配置了PSII，当确认一个PDU没有被成功送达，可以丢弃该PDU属于的PDU Set。
再例如，PDU Set可以被配置一个PDU Set内容比率(content ratio)，用于指示当PDU Set的X％比特数被正确送达时，该PDU Set才对接收端有用，其中，X就是PDU Set的内容比率。这种情况针对的场景是应用层对PDU Set使用了FEC(Forward Error Correction)，可以容忍1-X％的错误率。这样的话，如果PDU Set配置了内容比率，当确认一个PDU Set中没有被成功送达(或者丢失)的数量超出某个阈值(称为第一阈值，例如，该第一阈值＝PDU Set中PDU的个数*(1-X％))，可以丢弃该PDU Set。
从另外一个角度，还可以根据已经成功送达的数量来进行判断，如果PDU Set配置了内容比率X，并且确认已经成功送达的PDU个数超出了某个阈值(称为第二阈值，例如，该第二阈值＝PDU Set中PDU的个数*X％)，那么发送端可以丢弃该PDU Set，也就是剩余的PDU可以不用发送，节约网络资源。
在上述实施例中，发送端可以利用PDCP状态报告来知道每个PDCP SDU的送 达状态。PDCP状态报告用于配置了statusReportRequired的AM DRB，在PDCP实体重建、数据恢复、或上行数据切换等情况由接收PDCP实体(receiving PDCP entity)触发。
在上述实施例中，可以增加一些触发条件来让接收端发送PDCP状态报告，比如定时发送，或者是在拥塞的情况下发送，或者是接收数据出错(或出错较多)的情况下发送，或者是其他原因需要发送端进行数据丢弃的情况下发送，等等。
在上述实施例中，发送PDCP实体还可以增加一个请求(poll)信息，用于请求接收端的PDCP实体发送一个PDCP状态报告。该发送PDCP实体可以根据收到的PDCP状态报告得出PDU Set是否完全成功送达、PDU Set中成功送达的PDU的个数、比例等信息。
在上述实施例中，当某个属于(应用层的)PDU Set的PDCP SDU没有被PDCP状态报告(该PDCP状态报告不是由切换引起的)确认为成功送达，且该PDU Set的PSII被配置(或配置为真)时，终端设备的发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，PSII被配置(或配置为真)是指，该PDU Set被配置了完整性指示，指示应用层为了使用该PDU Set需要所有的PDU。
根据上述实施例，可以对TS 38.323的描述进行增强，例如，TS 38.323可以包含如下描述：
在上述实施例中，以内容准则为内容比率为例，终端设备可以针对PDCP层的SDU丢弃功能进行如下增强：
当属于某个(应用层的)PDU Set的没有被PDCP状态报告(该状态报告不是由切换引起的)确认为成功送达的PDCP SDU个数超出了第一阈值时，终端设备的发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，仍以内容准则为内容比率为例，终端设备还可以针对PDCP层的SDU丢弃功能进行如下增强：
当属于某个(应用层的)PDU Set的被PDCP状态报告确认为成功送达的PDCP  SDU个数超出了第二阈值时，终端设备的发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，第一阈值和第二阈值可以是预定义的，也可以是网络设备配置的，例如网络设备通过RRC信令进行配置，本申请对具体的配置方式不做限制，可以参考相关技术。
在前述各实施例中，考虑了PDU Set的内容准则进行数据丢弃，保证了PDU Set的完整性或者是内容有效性，节约了网络资源。
在又一些实施例中，终端设备可以根据RLC(Radio Link Control，无线链路控制)层的超过最大传输次数指示进行PDU Set丢弃。
在上述实施例中，终端设备可以在PDCP层收到关于某个PDCP数据PDU超过最大传输次数的指示(例如，从该PDCP数据PDU提交到的所有RLC实体都收到了指示)，且该PDCP数据PDU对应的SDU属于某PDU Set，且该PDU Set被配置了PSII时，由发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，终端设备的RLC层在某个RLC SDU超过最大重传次数时，可以告知高层(例如PDCP层，例如向PDCP层指示)该RLC SDU达到了最大重传次数，由此，PDCP层可以判断该RLC SDU(对应了PDCP PDU)传输失败。
根据上述实施例，可以对TS 38.323的描述进行增强，例如，TS 38.323可以包含如下描述：
在上述实施例中，以内容准则为内容比率为例，终端设备可以针对PDCP层的SDU丢弃功能进行如下增强：
当属于某个(应用层的)PDU Set的PDCP数据PDU被RLC层的超过最大传输次数指示确认为送达失败的个数超出了第三阈值时，终端设备的发送PDCP实体丢弃属于该PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，第三阈值可以是预定义的，也可以是网络设备配置的，例如网络设备通过RRC信令进行配置，本申请对具体的配置方式不做限制，可以参考相关 技术。
在前述实施例中，同样考虑了PDU Set的内容准则进行数据丢弃，保证了PDU Set的完整性或者是内容有效性，节约了网络资源。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
根据本申请实施例的方法，一方面，将PDU Set的传输时延作为一个整体考虑，从而满足了PDU Set的PSDB需求；另一方面，考虑了PDU Set的内容准则进行数据丢弃，保证了PDU Set的完整性或者是内容有效性，节约了网络资源。
第二方面的实施例
发明人发现，丢弃已经关联了PDCP序列号的PDCP SDU会在发送了的PDCP数据PDU中造成序列号间隙(SN gap)，从而增加接收PDCP实体端的PDCP重排序延迟。此外，在进行PDU Set丢弃时，往往会丢弃连续的一系列PDCP SDU，从而导致较大的序列号间隙。如何避免或者最小化序列号间隙需要解决。
针对上述问题至少之一，本申请实施例提供一种数据处理方法，从发送设备的一侧进行说明，该发送设备可以是终端设备，也可以是网络设备；相应的，接收设备可以是网络设备，也可以是终端设备。
图2是本申请实施例的处理处理方法的一示意图，请参照图2，该方法包括：
201：发送设备在丢弃了一PDU Set对应的所有PDCP SDU之后，将其中已经关联了PDCP序列号的PDCP SDU的序列号信息发送给接收设备。
在上述实施例中，PDU Set往往对应了连续的一系列PDCP SDU序列号，所以发送设备可以将丢弃的连续的一段SDU序列号信息发送给接收设备。
值得注意的是，以上附图2仅示意性地对本申请实施例进行了说明，但本申请不限于此。例如可以增加其他的一些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图2的记载。
在上述实施例中，对PDU Set的丢弃方法不做限制，例如，可以采用第一方面的实施例的方法进行PDU Set的丢弃，也可以采用其他方法进行PDU Set丢弃。
根据上述实施例，在丢弃了某个PDU Set对应的所有PDCP SDU之后，发送端 可以将其中已经关联了PDCP序列号的SDU的序列号信息发送给接收端。这样，接收端的PDCP实体可以知道哪些序号是已经被发送端丢弃的，因此不会等待接收这些数据，从而避免了造成重排序延迟。
在一些实施例中，上述序列号信息可以通过PDCP控制PDU发送。例如，可以在PDCP层通过增加一个新的PDCP控制PDU来通知该序列号信息。该PDCP控制PDU可以称为PDCP丢弃报告(PDCP discard report)。发送端的发送PDCP实体可以在PDU Set丢弃之后，发送一个PDCP丢弃报告给对端(接收端)的PDCP实体，以通知丢弃的PDCP SDU的序列号信息。
在一些实施例中，该序列号信息包括丢弃的连续的PDCP SDU(例如整个PDU Set)中的第一个PDCP SDU的COUNT值(也即PDCP SDU的PDCP序列号)，例如称为COUNT_start，和丢弃的所述连续的PDCP SDU的个数，例如称为length。本申请不限于此，该序列号信息也可以包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT值和最后一个PDCP SDU的COUNT值，例如称为COUNT_end。
图3是PDCP丢弃报告格式的一个示例的示意图，示出了一种作为PDCP discard report的PDCP控制PDU的格式，以包含COUNT_start和length为例。该PDCP控制PDU可以在PDCP报头使用0作为D/C位，表明是控制PDU，定义一个新的PDU Type(比如二进制比特为100)表明该PDU是PDCP丢弃报告。COUNT_start为32比特，length为8比特(也可以为16比特等等)。为了可扩展性，该报告可以包含多组COUNT_start和length，表明对多个连续的SDU段(比如多个PDU Set)进行了丢弃。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
根据本申请实施例的方法，根据上述实施例，解决了序列号间隔的问题，减少了接收端的重排序延迟，提高了业务性能。
第三方面的实施例
本申请实施例提供一种数据处理方法，从接收设备的一侧进行说明，该接收设备可以是网络设备，也可以是终端设备，其是与第二方面的实施例对应的接收端的处理， 其中与第二方面的实施例相同的内容不再重复说明。
图4是本申请实施例的数据处理方法的一示意图，如图4所示，该方法包括：
401：接收设备在接收到丢弃的PDCP SDU的序列号信息后，保存或记录所述丢弃的PDCP SDU的序列号信息；
402：所述接收设备根据所述丢弃的PDCP SDU的序列号信息，将存储的PDCP SDU递交到高层。
值得注意的是，以上附图4仅示意性地对本申请实施例进行了说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图4的记载。
根据上述实施例，作为接收端，在收到丢弃的PDCP SDU的序列号信息(比如称为PDCP丢弃报告，如图3所示)之后，保存或记录丢弃的PDCP SDU的序列号(例如COUNT值)信息，进而，根据丢弃的PDCP SDU的序列号信息，不需要等待这些丢弃的PDCP SDU(也类似于假设这些SDU已经收到)，直接将已经收到的(也即存储的)(COUNT值在COUNT_end之前的)PDCP SDU递交到高层。由此，解决了序列号间隔的问题，减少了接收端的重排序延迟，提高了业务性能。
在上述实施例中，如果接收端是UE，则上述丢弃报告是针对下行数据，由网络侧(网络设备)发出；相应的，如果接收端是网络设备，则上述丢弃报告是针对上行数据，由UE发出。
在一些实施例中，上述序列号信息包括丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值和丢弃的所述连续的PDCP SDU的个数，也即，COUNT_start和length；或者，上述序列号信息包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT值和最后一个PDCP SDU的COUNT值，也即COUNT_start和COUNT_end。
在上述实施例中，如果收到的序列号信息是COUNT_start和length，可以通过COUNT_start计算出COUNT_end。
在一些实施例中，与第二方面的实施例对应的，上述序列号信息可以通过PDCP控制PDU发送。具体可以参考第二方面的实施例，此处不再赘述。
在一些实施例中，接收设备维护了四个状态变量，即第一状态变量RX_DELIV、第二状态变量RX_NEXT、第三状态变量RX_DISCOARD0、第四状态变量 RX_DISCARD1。
在上述实施例中，第一状态变量RX_DELIV指示第一个没有被递交到高层但是仍然在等待被接收的PDCP SDU的COUNT值；第二状态变量RX_NEXT指示下一个期待被接收的PDCP SDU的COUNT值；第三状态变量RX_DISCARD0对应COUNT_start，指示发送设备的发送PDCP实体的第一个丢弃的PDCP SDU的COUNT值；第四状态变量RX_DISCARD1对应COUNT_end(或者是COUNT_start+length-1，如果PDCP丢弃报告使用的是length)，指示发送设备的发送PDCP实体的最后一个丢弃的PDCP SDU的COUNT值。其中，第三状态变量和第四状态变量为新引入的接收PDCP实体维护的变量，本申请对其叫法不做限制，也可以叫其他变量名。
在一些实施例中，接收设备将存储的PDCP SDU递交到高层，包括：接收设备将存储的PDCP SDU中COUNT值小于等于第四状态变量的PDCP SDU按序递交到高层。
图5至图8是第三状态变量和第四状态变量与第一状态变量和第二状态变量之间的大小关系的几个示例的示意图，示出了接收端收到以及未收到的PDCP SDU的序列号的情况以及对应的状态变量的值。
在图5的示例中，RX_DISCARD0≤RX_DELIV，RX_DELIV≤RX_DISCARD1<RX_NEXT–1；在图6的示例中，RX_DISCARD0≤RX_DELIV,RX_DISCARD1≥RX_DELIV,RX_DISCARD1≥RX_NEXT–1；在图7的示例中，RX_DISCARD0＝＝RX_DELIV,RX_DISCARD1<RX_NEXT–1；在图8的示例中，RX_DISCARD0＝＝RX_DELIV,RX_DISCARD1≥RX_NEXT–1。
在一些实施例中，当收到PDCP丢弃报告时，接收设备执行以下操作：
将第三状态变量更新为丢弃报告中丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值；
将第四状态变量更新为丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值加上丢弃的连续的PDCP SDU的个数的值减1。
在上述实施例中，如果第三状态变量小于或等于第一状态变量，第一状态变量小于或等于第四状态变量，也即，在图5和图6的场景下，接收设备还可以执行以下操作至少之一：
将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序 递交到高层，直到COUNT值小于或等于第四状态变量为止；
如果第四状态变量小于第二状态变量减1，将所有存储的关联的COUNT值从第四状态变量+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
将第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中COUNT值大于第一状态变量；
将第二状态变量更新为第一状态变量和更新前的第二状态变量之间的最大值。
在上述实施例中，接收设备还可以维护第五状态变量RX_REORD，该第五状态变量RX_REORD用于指示触发重排序定时器(t-Reordering)的PDCP数据PDU关联的COUNT值的下一个COUNT值。
在上述实施例中，在图5和图6所示的场景下，接收设备还可以执行以下操作至少之一：
如果重排序定时器正在运行，且第一状态变量大于或等于第五状态变量，停止并重置重排序定时器；
如果重排序定时器没有在运行，且第一状态变量小于第二状态变量，则将第五状态变量更新为第二状态变量的值，并开启重排序定时器。
在上述各实施例中，以UE作为接收设备为例，当UE收到PDCP丢弃报告后，更新接收端的状态变量值，例如，其在通过上述状态变量之间的比较，确认属于图5或图6所示的场景后，可以执行以上操作，以考虑丢弃的PDCP SDU，将目前能递交的PDCP SDU递交到高层。
例如，对于AM DRB，当一个PDCP丢弃报告从下行收到之后，接收PDCP实体进行如下操作：
-将RX_DISCARD0更新为COUNT_start字段的值，将RX_DISCARD1更新为COUNT_start字段的值加上length字段的值减去1。
-如果RX_DISCARD0≤RX_DELIV且RX_DISCARD1≥RX_DELIV(图5所示的场景和图6所示的场景)：
-将所有存储的PDCP SDU在执行报头解压缩(如果还没有进行过解压缩的话)之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于等于RX_DISCARD1为止；
-如果RX_DISCARD1<RX_NEXT–1(图5所示的场景)：
-将所有存储的关联的COUNT值从RX_DISCARD+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
-将RX_DELIV更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中COUNT>RX_DELIV(也就是如果该COUNT值大于更新之前的RX_DELIV的话)；
-将RX_NEXT更新为RX_DELIV和原来的RX_NEXT之间的最大值(也就是如果RX_DELIV大于RX_NEXT，那么将RX_NEXT更新为RX_DELIV的值)。
-如果t-Reordering正在运行，且RX_DELIV≥RX_REORD：
-停止并重置重排序定时器；
-如果t-Reordering没有在运行，且RX_DELIV<RX_NEXT：
-将RX_REORD更新为RX_NEXT；
-开启重排序定时器。
根据上述实施例，可以对TS 38.323的描述进行增强，例如，TS 38.323可以包含如下描述：
在一些实施例中，如果第三状态变量等于第一状态变量，也即，在图7和图8的场景下，接收设备执行以下操作至少之一：
将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序递 交到高层，直到COUNT值小于等于第四状态变量为止；
如果第四状态变量小于第二状态变量减1，将所有存储的关联的COUNT值从第四状态变量+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
将第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中，COUNT值大于第一状态变量；
将第二状态变量更新为第一状态变量和更新前的第二状态变量之间的最大值。
在上述实施例中，接收设备可以在从低层收到PDCP数据PDU时进行上述操作。
在上述实施例中，以UE作为接收设备为例，当从低层收到PDCP数据PDU时，通过上述状态变量之间的比较，确认属于图7或图8所示的场景后，可以执行以上操作，以便当目前PDCP数据PDU接收处理完成之后，状态变量发生了变化的情况下，利用丢弃的SDU序列号信息，将目前能递交的SDU递交到高层。
例如，如果收到的PDCP数据PDU没有被丢弃(也即，以前没有收到过具有相同COUNT的数据PDU)，则接收PDCP实体：
-如果RX_DISCARD0＝＝RX_DELIV(图7和图8所示的场景)：
-将所有存储的PDCP SDU在执行报头解压缩(如果还没有进行过解压缩的话)之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于等于RX_DISCARD1为止；
-如果RX_DISCARD1<RX_NEXT–1(图7所示的场景)：
-将所有存储的关联的COUNT值从RX_DISCARD+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
-将RX_DELIV更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中COUNT>RX_DELIV(也就是如果该COUNT值大于更新之前的RX_DELIV的话)；
-将RX_NEXT更新为RX_DELIV和原来的RX_NEXT之间的最大值(也就是如果RX_DELIV大于RX_NEXT，那么将RX_NEXT更新为RX_DELIV的值)。
根据上述实施例，可以对TS 38.323的描述进行增强，例如，TS 38.323可以包含如下描述：

在上述实施例中，接收设备的PDCP实体没有被配置outOfOrderDelivery。也即，以上增强可以在没有配置outOfOrderDelivery的情况下进行，也就是说，PDCP实体需要将收到的PDCP SDU进行向高层按需递交。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
根据本申请实施例的方法，解决了序列号间隔的问题，减少了接收端的重排序延迟，提高业务性能。
第四方面的实施例
本申请实施例提供一种数据处理装置。
图9是本申请实施例的数据处理装置的一示意图，该装置例如可以是终端设备，也可以是配置于该终端设备中的某个或某些部件或者组件。由于该装置解决问题的原理与第一方面的实施例的方法相同，因此其具体的实施可以参照第一方面的实施例的 方法的实施，内容相同之处不再重复说明。
如图9所示，该数据处理装置900包括：
处理单元901，其在与一PDU Set关联的以下条件至少之一满足的情况下，丢弃上述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU，或者认为属于上述PDU Set中的所有PDCP SDU的丢弃定时器都超时；
一PDCP SDU对应的丢弃定时器到期，且该PDCP SDU属于上述PDU Set；
上述PDU Set对应的丢弃定时器超时；
属于上述PDU Set的一PDCP SDU没有被PDCP状态报告确认为成功送达，且上述PDU Set的PSII被配置；
终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，且该PDCP数据PDU对应的SDU属于上述PDU Set，且上述PDU Set被配置了PSII。
在一些实施例中，PDU Set对应的丢弃定时器超时，包括：终端设备的发送PDCP实体为PDU Set维护一个丢弃定时器，该丢弃定时器超时。
在上述实施例中，当终端设备的发送PDCP实体从高层收到一个PDCP SDU时，如果该PDCP SDU属于应用级别的PDU Set，且为上述PDU Set中的第一个PDU，则终端设备的发送PDCP实体启动上述PDU Set关联的丢弃定时器。
在一些实施例中，当属于上述PDU Set的没有被PDCP状态报告确认为成功送达的PDCP SDU个数超出第一阈值时，处理单元901通过发送PDCP实体丢弃属于上述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，第一阈值可以是预定义的，也可以是网络设备通过RRC信令配置的。
在一些实施例中，当属于上述PDU Set的被PDCP状态报告确认为成功送达的PDCP SDU个数超出第二阈值时，处理单元901通过发送PDCP实体丢弃属于上述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
在上述实施例中，第二阈值可以是预定义的，也可以是网络设备通过RRC信令配置的。
在一些实施例中，终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，包括：终端设备的RLC层在一RLC SDU超过最大重传次数时，向PDCP层指示(indicate)该RLC SDU达到最大重传次数，该RLC SDU对应前述PDCP 数据PDU。
图10是本申请实施例的数据处理装置的另一示意图，该装置例如可以是发送设备，也可以是配置于该发送设备中的某个或某些部件或者组件，该发送设备可以是终端设备，也可以是网络设备。由于该装置解决问题的原理与第二方面的实施例的方法相同，因此其具体的实施可以参照第二方面的实施例的方法的实施，内容相同之处不再重复说明。
如图10所示，该数据处理装置1000包括：
发送单元1001，其在发送设备丢弃了一PDU Set对应的所有PDCP SDU之后，将其中已经关联了PDCP序列号的PDCP SDU的序列号信息发送给接收设备。
在一些实施例中，序列号信息包括丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值和丢弃的连续的PDCP SDU的个数。
在一些实施例中，序列号信息包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT值和最后一个PDCP SDU的COUNT值。
在上述各实施例中，序列号信息可以通过PDCP控制PDU发送。
图11是本申请实施例的数据处理装置的另一示意图，该装置例如可以是接收设备，也可以是配置于该接收设备中的某个或某些部件或者组件，该接收设备可以是网络设备，也可以是终端设备。由于该装置解决问题的原理与第三方面的实施例的方法相同，因此其具体的实施可以参照第三方面的实施例的方法的实施，内容相同之处不再重复说明。
如图11所示，该数据处理装置1100包括：
第一处理单元1101，其在接收设备接收到丢弃的PDCP SDU的序列号信息后，保存或记录上述丢弃的PDCP SDU的序列号信息；
第二处理单元1102，其根据上述丢弃的PDCP SDU的序列号信息，将存储的PDCP SDU递交到高层。
在一些实施例中，序列号信息包括丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值和丢弃的连续的PDCP SDU的个数；或者，序列号信息包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT值和最后一个PDCP SDU的COUNT值。
在一些实施例中，序列号信息通过PDCP控制PDU发送。
在一些实施例中，接收设备维护了以下四个状态变量：
第一状态变量(RX_DELIV)，其指示第一个没有被递交到高层但是仍然在等待被接收的PDCP SDU的COUNT值；
第二状态变量(RX_NEXT)，其指示下一个期待被接收的PDCP SDU的COUNT值；
第三状态变量(RX_DISCARD0)，其指示发送设备的发送PDCP实体的第一个丢弃的PDCP SDU的COUNT值；
第四状态变量(RX_DISCARD1)，其指示发送设备的发送PDCP实体的最后一个丢弃的PDCP SDU的COUNT值。
在一些实施例中，第二处理单元1102将存储的PDCP SDU递交到高层，包括：
第二处理单元1102将存储的PDCP SDU中COUNT值小于等于第四状态变量的SDU按序递交到高层。
在一些实施例中，第二处理单元1102还执行以下操作：
将第三状态变量更新为丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值；
将第四状态变量更新为丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值加上丢弃的所述连续的PDCP SDU的个数的值减1。
在上述实施例中，如果所述第三状态变量小于或等于所述第一状态变量，所述第一状态变量小于或等于第四状态变量，也即在图5和图6所示的场景下，第二处理单元1102还可以执行以下操作至少之一：
将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于或等于第四状态变量为止；
如果第四状态变量小于第二状态变量减1，将所有存储的关联的COUNT值从第四状态变量+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
将第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中该COUNT值大于第一状态变量；
将第二状态变量更新为第一状态变量和更新前的第一状态变量之间的最大值。
在上述实施例中，接收设备还可以维护第五状态变量(RX_REORD)，该第五状 态变量指示触发重排序定时器的PDCP数据PDU关联的COUNT值的下一个COUNT值。
在上述实施例中，第二处理单元1102还可以执行以下操作至少之一：
如果重排序定时器正在运行，且第一状态变量大于或等于第五状态变量，停止并重置重排序定时器；
如果重排序定时器没有在运行，且第一状态变量小于第二状态变量，则将第五状态变量更新为第二状态变量的值，并开启重排序定时器。
在一些实施例中，如果第三状态变量等于第一状态变量，也即在图7和图8所示的场景下，第二处理单元1102还可以执行以下操作至少之一：
将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于等于所述第四状态变量为止；
如果第四状态变量小于所述第二状态变量减1，将所有存储的关联的COUNT值从第四状态变量+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
将第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中，该COUNT值大于第一状态变量；
将所二状态变量更新为第一状态变量和更新前的第二状态变量之间的最大值。
在上述实施例中，第二处理单元1102可以在接收设备从低层收到PDCP数据PDU时进行上述操作。
在本申请实施例中，接收设备的PDCP实体没有被配置outOfOrderDelivery。也即，上述装置1100可以在接收设备的PDCP实体没有被配置outOfOrderDelivery的情况下进行上述操作。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的数据处理装置900、1000、1100还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图9至图11中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
根据本申请实施例的装置，解决了将PDU Set在无线接入网的数据丢弃的问题，可以用于更好地支持XR和媒体业务应用。此外，还引入了丢弃报告，通过对发送端和接收端进行增强，解决了由于数据丢弃导致的序列号间隙的问题，减少了重排序延迟，从而提高XRM业务的传输性能。通过本申请实施例的装置，可以保障差异化的PDU Set的处理以及满足PDU Set的集成数据处理需求。
第五方面的实施例
本申请实施例提供一种通信系统，包括终端设备和网络设备，该终端设备被配置为执行第一方面至第三方面任一方面的实施例所述的方法，或者，该网络设备被配置为执行第二方面或第三方面的实施例所述的方法。关于该终端设备和该网络设备的行为已经在第一方面至第三方面的实施例中做了详细说明，其内容被合并于此，此处不再赘述。
本申请实施例还提供一种终端设备，该终端设备包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如第一方面至第三方面中任一方面的实施例所述的方法。
图12是本申请实施例的终端设备的一示意图。如图12所示，该终端设备1200可以包括处理器1201和存储器1202；存储器1202存储有数据和程序，并耦合到处理器1201。值得注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
例如，处理器1201可以被配置为执行程序而实现如第一方面至第三方面中任一方面的实施例所述的方法。
如图12所示，该终端设备1200还可以包括：通信模块1203、输入单元1204、显示器1205、电源1206。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1200也并不是必须要包括图12中所示的所有部件，上述部件并不是必需的；此外，终端设备1200还可以包括图12中没有示出的部件，可以参考现有技术。
本申请实施例还提供了一种网络设备，该网络设备包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如第二方面或第三方面的实施例所述的方法。
图13是本申请实施例的网络设备的一示意图。如图13所示，网络设备1300可以包括：中央处理器(CPU)1301和存储器1302；存储器1302耦合到中央处理器1301。其中该存储器1302可存储各种数据；此外还存储信息处理的程序，并且在中央处理器1301的控制下执行该程序，以接收终端设备发送的各种信息、并且向终端设备发送各种信息。
例如，处理器1301可以被配置为执行程序而实现如第二方面或第三方面的实施例所述的方法。
此外，如图13所示，网络设备1300还可以包括：收发机1303和天线1304等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1300也并不是必须要包括图13中所示的所有部件；此外，网络设备1300还可以包括图13中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在终端设备中执行所述程序时，所述程序使得计算机在所终端设备中执行第一方面至第三方面中任一方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在终端设备中执行第一方面至第三方面中任一方面的实施例所述的方法。
本申请实施例还提供一种计算机可读程序，其中当在网络设备中执行所述程序时，所述程序使得计算机在所述网络设备中执行第二方面或第三方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在网络设备中执行第二方面或第三方面的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或 多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种数据处理方法，应用于终端设备，其中，所述方法包括：
终端设备在与一PDU Set关联的以下条件至少之一满足的情况下，丢弃所述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU，或者认为属于所述PDU Set中的所有PDCP SDU的丢弃定时器都超时：
一PDCP SDU对应的丢弃定时器到期，且所述PDCP SDU属于所述PDU Set；
所述PDU Set对应的丢弃定时器超时；
属于所述PDU Set的一PDCP SDU没有被PDCP状态报告确认为成功送达，且所述PDU Set的PSII被配置；
所述终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，且所述PDCP数据PDU对应的SDU属于所述PDU Set，且所述PDU Set被配置了PSII。
2.根据附记1所述的方法，其中，
所述PDU Set对应的丢弃定时器超时，包括：所述终端设备的发送PDCP实体为所述PDU Set维护一个丢弃定时器，所述丢弃定时器超时。
3.根据附记2所述的方法，其中，
当所述终端设备的发送PDCP实体从高层收到一个PDCP SDU时，如果所述PDCP SDU属于应用级别的PDU Set，且为所述PDU Set中的第一个PDU，则所述终端设备的发送PDCP实体启动所述PDU Set关联的丢弃定时器。
4.根据附记1所述的方法，其中，所述方法还包括：
当属于所述PDU Set的没有被PDCP状态报告确认为成功送达的PDCP SDU个数超出第一阈值时，所述终端设备的发送PDCP实体丢弃属于所述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
5.根据附记1所述的方法，其中，所述方法还包括：
当属于所述PDU Set的被PDCP状态报告确认为成功送达的PDCP SDU个数超出第二阈值时，所述终端设备的发送PDCP实体丢弃属于所述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
6.根据附记1所述的方法，其中，所述终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，包括：
所述终端设备的RLC层在一RLC SDU超过最大重传次数时，向所述PDCP层指示(indicate)所述RLC SDU达到最大重传次数，所述RLC SDU对应所述PDCP数据PDU。
7.根据附记4或5所述的方法，其中，
所述阈值是预定义的，或者是网络设备通过RRC信令配置的。
8.一种数据处理方法，应用于发送设备，所述发送设备为终端设备或网络设备，其中，所述方法包括：
发送设备在丢弃了一PDU Set对应的所有PDCP SDU之后，将其中已经关联了PDCP序列号的PDCP SDU的序列号信息发送给接收设备。
9.根据附记8所述的方法，其中，
所述序列号信息包括丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值和丢弃的所述连续的PDCP SDU的个数；或者
所述序列号信息包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT值和最后一个PDCP SDU的COUNT值。
10.根据附记8或9所述的方法，其中，
所述序列号信息通过PDCP控制PDU发送。
11.一种数据处理方法，应用于接收设备，所述接收设备为网络设备或终端设备，其中，所述方法包括：
接收设备在接收到丢弃的PDCP SDU的序列号信息后，保存或记录所述丢弃的PDCP SDU的序列号信息；
所述接收设备根据所述丢弃的PDCP SDU的序列号信息，将存储的PDCP SDU递交到高层。
12.根据附记11所述的方法，其中，
所述序列号信息包括丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值和丢弃的所述连续的PDCP SDU的个数；或者
所述序列号信息包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT值和最后一个PDCP SDU的COUNT值。
13.根据附记11或12所述的方法，其中，
所述序列号信息通过PDCP控制PDU发送。
14.根据附记11-13任一项所述的方法，其中，
所述接收设备维护了以下四个状态变量：
第一状态变量(RX_DELIV)，其指示第一个没有被递交到高层但是仍然在等待被接收的PDCP SDU的COUNT值；
第二状态变量(RX_NEXT)，其指示下一个期待被接收的PDCP SDU的COUNT值；
第三状态变量(RX_DISCARD0)，其指示发送设备的发送PDCP实体的第一个 丢弃的PDCP SDU的COUNT值；
第四状态变量(RX_DISCARD1)，其指示发送设备的发送PDCP实体的最后一个丢弃的PDCP SDU的COUNT值。
15.根据附记11-14任一项所述的方法，其中，所述接收设备将存储的PDCP SDU递交到高层，包括：
所述接收设备将存储的PDCP SDU中COUNT值小于等于第四状态变量的SDU按序递交到高层，所述第四状态变量指示发送设备的发送PDCP实体的最后一个丢弃的PDCP SDU的COUNT值。
16.根据附记14或15所述的方法，其中，所述方法还包括：
所述接收设备执行以下操作：
将所述第三状态变量更新为所述丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值；
将所述第四状态变量更新为所述丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值加上所述丢弃的所述连续的PDCP SDU的个数的值减1。
17.根据附记16所述的方法，其中，
如果所述第三状态变量小于或等于所述第一状态变量，所述第一状态变量小于或等于所述第四状态变量，则所述接收设备还执行以下操作至少之一：
将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于或等于所述第四状态变量为止；
如果所述第四状态变量小于所述第二状态变量减1，将所有存储的关联的COUNT值从所述第四状态变量+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
将所述第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中所述COUNT值大于所述第一状态变量；
将所述第二状态变量更新为所述第一状态变量和更新前的所述第一状态变量之间的最大值。
18.根据附记17所述的方法，其中，
所述接收设备还维护第五状态变量(RX_REORD)，所述第五状态变量指示触发重排序定时器的PDCP数据PDU关联的COUNT值的下一个COUNT值；
所述接收设备还执行以下操作至少之一：
如果所述重排序定时器正在运行，且所述第一状态变量大于或等于所述第五状态变量，停止并重置所述重排序定时器；
如果所述重排序定时器没有在运行，且所述第一状态变量小于所述第二状态变量，则将所述第五状态变量更新为所述第二状态变量的值，并开启所述重排序定时器。
19.根据附记15所述的方法，其中，
如果所述第三状态变量等于所述第一状态变量，则所述接收设备执行以下操作至少之一：
将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于等于所述第四状态变量为止；
如果所述第四状态变量小于所述第二状态变量减1，将所有存储的关联的COUNT值从所述第四状态变量+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
将所述第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中，所述COUNT值大于所述第一状态变量；
将所述第二状态变量更新为所述第一状态变量和更新前的所述第二状态变量之间的最大值。
20.根据附记19所述的方法，其中，
所述接收设备在从低层收到PDCP数据PDU时进行所述操作。
21.根据附记11-20任一项所述的方法，其中，
所述接收设备的PDCP实体没有被配置outOfOrderDelivery。
22.一种终端设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记1至21任一项所述的方法。
23.一种网络设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记8至21任一项所述的方法。
24.一种通信系统，包括终端设备和网络设备，所述终端设备被配置为执行附记1至21任一项所述的方法，和/或，所述网络设备被配置为执行附记8至21任一项所述的方法。

Claims (20)

  1. 一种数据处理装置，配置于终端设备，其中，所述装置包括：
    处理单元，其在与一协议数据单元集(PDU Set)关联的以下条件至少之一满足的情况下，丢弃所述PDU Set中的所有分组数据汇聚层协议服务数据单元(PDCP SDU)和其对应的PDCP数据PDU，或者认为属于所述PDU Set中的所有PDCP SDU的丢弃定时器都超时：
    一PDCP SDU对应的丢弃定时器到期，且所述PDCP SDU属于所述PDU Set；
    所述PDU Set对应的丢弃定时器超时；
    属于所述PDU Set的一PDCP SDU没有被PDCP状态报告确认为成功送达，且所述PDU Set的PSII被配置；
    所述终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，且所述PDCP数据PDU对应的SDU属于所述PDU Set，且所述PDU Set被配置了PSII。
  2. 根据权利要求1所述的装置，其中，
    所述PDU Set对应的丢弃定时器超时，包括：所述终端设备的发送PDCP实体为所述PDU Set维护一个丢弃定时器，所述丢弃定时器超时。
  3. 根据权利要求2所述的装置，其中，
    当所述终端设备的发送PDCP实体从高层收到一个PDCP SDU时，如果所述PDCP SDU属于应用级别的PDU Set，且为所述PDU Set中的第一个PDU，则所述处理单元通过发送PDCP实体启动所述PDU Set关联的丢弃定时器。
  4. 根据权利要求1所述的装置，其中，所述装置还包括：
    当属于所述PDU Set的没有被PDCP状态报告确认为成功送达的PDCP SDU个数超出第一阈值时，所述处理单元通过发送PDCP实体丢弃属于所述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
  5. 根据权利要求1所述的装置，其中，所述装置还包括：
    当属于所述PDU Set的被PDCP状态报告确认为成功送达的PDCP SDU个数超出第二阈值时，所述处理单元通过发送PDCP实体丢弃属于所述PDU Set中的所有PDCP SDU和其对应的PDCP数据PDU。
  6. 根据权利要求1所述的装置，其中，所述终端设备的PDCP层收到关于一PDCP数据PDU超过最大传输次数的指示，包括：
    所述终端设备的无线链路控制(RLC)层在一无线链路控制服务数据单元(RLC SDU)超过最大重传次数时，向所述PDCP层指示(indicate)所述RLC SDU达到最大重传次数，所述RLC SDU对应所述PDCP数据PDU。
  7. 根据权利要求4所述的装置，其中，
    所述第一阈值是预定义的，或者是网络设备通过无线资源控制(RRC)信令配置的。
  8. 一种数据处理装置，配置于发送设备，所述发送设备为终端设备或网络设备，其中，所述装置包括：
    发送单元，其在所述发送设备丢弃了一PDU Set对应的所有PDCP SDU之后，将其中已经关联了PDCP序列号的PDCP SDU的序列号信息发送给接收设备。
  9. 根据权利要求8所述的装置，其中，
    所述序列号信息包括丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值和丢弃的所述连续的PDCP SDU的个数；或者
    所述序列号信息包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT值和最后一个PDCP SDU的COUNT值。
  10. 根据权利要求8所述的装置，其中，
    所述序列号信息通过PDCP控制PDU发送。
  11. 一种数据处理装置，配置于接收设备，所述接收设备为网络设备或终端设备，其中，所述装置包括：
    第一处理单元，其在所述接收设备接收到丢弃的PDCP SDU的序列号信息后，保存或记录所述丢弃的PDCP SDU的序列号信息；
    第二处理单元，其根据所述丢弃的PDCP SDU的序列号信息，将存储的PDCP SDU递交到高层。
  12. 根据权利要求11所述的装置，其中，
    所述序列号信息包括丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值和丢弃的所述连续的PDCP SDU的个数；或者
    所述序列号信息包括丢弃的连续的PDCP SDU中第一个PDCP SDU的COUNT 值和最后一个PDCP SDU的COUNT值。
  13. 根据权利要求11所述的装置，其中，
    所述序列号信息通过PDCP控制PDU发送。
  14. 根据权利要求11所述的装置，其中，
    所述接收设备维护了以下四个状态变量：
    第一状态变量，其指示第一个没有被递交到高层但是仍然在等待被接收的PDCP SDU的COUNT值；
    第二状态变量，其指示下一个期待被接收的PDCP SDU的COUNT值；
    第三状态变量，其指示发送设备的发送PDCP实体的第一个丢弃的PDCP SDU的COUNT值；
    第四状态变量，其指示发送设备的发送PDCP实体的最后一个丢弃的PDCP SDU的COUNT值。
  15. 根据权利要求11所述的装置，其中，所述第二处理单元将存储的PDCP SDU递交到高层，包括：
    所述第二处理单元将存储的PDCP SDU中COUNT值小于等于第四状态变量的SDU按序递交到高层，所述第四状态变量指示发送设备的发送PDCP实体的最后一个丢弃的PDCP SDU的COUNT值。
  16. 根据权利要求14所述的装置，其中，所述第二处理单元还执行以下操作：
    将所述第三状态变量更新为所述丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值；
    将所述第四状态变量更新为所述丢弃的连续的PDCP SDU中的第一个PDCP SDU的COUNT值加上所述丢弃的所述连续的PDCP SDU的个数的值减1。
  17. 根据权利要求16所述的装置，其中，
    如果所述第三状态变量小于或等于所述第一状态变量，所述第一状态变量小于或等于所述第四状态变量，则所述第二处理单元还执行以下操作至少之一：
    将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于或等于所述第四状态变量为止；
    如果所述第四状态变量小于所述第二状态变量减1，将所有存储的关联的COUNT值从所述第四状态变量+1开始具有连续COUNT值的PDCP SDU按照 COUNT值升序递交到高层；
    将所述第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中所述COUNT值大于所述第一状态变量；
    将所述第二状态变量更新为所述第一状态变量和更新前的所述第一状态变量之间的最大值。
  18. 根据权利要求17所述的装置，其中，
    所述接收设备还维护第五状态变量，所述第五状态变量指示触发重排序定时器的PDCP数据PDU关联的COUNT值的下一个COUNT值；
    所述第二处理单元还执行以下操作至少之一：
    如果所述重排序定时器正在运行，且所述第一状态变量大于或等于所述第五状态变量，停止并重置所述重排序定时器；
    如果所述重排序定时器没有在运行，且所述第一状态变量小于所述第二状态变量，则将所述第五状态变量更新为所述第二状态变量的值，并开启所述重排序定时器。
  19. 根据权利要求15所述的装置，其中，
    如果所述第三状态变量等于所述第一状态变量，则所述第二处理单元执行以下操作至少之一：
    将所有存储的PDCP SDU在执行报头解压缩之后按照关联的COUNT值的升序递交到高层，直到COUNT值小于等于所述第四状态变量为止；
    如果所述第四状态变量小于所述第二状态变量减1，将所有存储的关联的COUNT值从所述第四状态变量+1开始具有连续COUNT值的PDCP SDU按照COUNT值升序递交到高层；
    将所述第一状态变量更新为第一个没有递交到高层的PDCP SDU的COUNT值，其中，所述COUNT值大于所述第一状态变量；
    将所述第二状态变量更新为所述第一状态变量和更新前的所述第二状态变量之间的最大值。
  20. 根据权利要求19所述的装置，其中，
    所述第二处理单元在从低层收到PDCP数据PDU时进行所述操作。
PCT/CN2023/076416 2023-02-16 2023-02-16 数据处理方法和装置 WO2024168672A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076416 WO2024168672A1 (zh) 2023-02-16 2023-02-16 数据处理方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076416 WO2024168672A1 (zh) 2023-02-16 2023-02-16 数据处理方法和装置

Publications (1)

Publication Number Publication Date
WO2024168672A1 true WO2024168672A1 (zh) 2024-08-22

Family

ID=92422015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/076416 WO2024168672A1 (zh) 2023-02-16 2023-02-16 数据处理方法和装置

Country Status (1)

Country Link
WO (1) WO2024168672A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110299681A1 (en) * 2010-06-03 2011-12-08 Nokia Corporation Ciphering in a packet-switched telecommunications system
US20150043435A1 (en) * 2013-08-09 2015-02-12 Blackberry Limited Method and system for protocol layer enhancements in data offload over small cells
WO2022016541A1 (en) * 2020-07-24 2022-01-27 Qualcomm Incorporated Retransmission procedures at a packet data convergence protocol layer
WO2022075912A1 (en) * 2020-10-08 2022-04-14 Telefonaktiebolaget Lm Ericsson (Publ) Group pdcp discard timer for low-latency services

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110299681A1 (en) * 2010-06-03 2011-12-08 Nokia Corporation Ciphering in a packet-switched telecommunications system
US20150043435A1 (en) * 2013-08-09 2015-02-12 Blackberry Limited Method and system for protocol layer enhancements in data offload over small cells
WO2022016541A1 (en) * 2020-07-24 2022-01-27 Qualcomm Incorporated Retransmission procedures at a packet data convergence protocol layer
WO2022075912A1 (en) * 2020-10-08 2022-04-14 Telefonaktiebolaget Lm Ericsson (Publ) Group pdcp discard timer for low-latency services

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LI CHEN, CATT: "PDU Discard of XR services", 3GPP DRAFT; R2-2211439; TYPE DISCUSSION; FS_NR_XR_ENH, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Toulouse, FR; 20221114 - 20221118, 4 November 2022 (2022-11-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052215548 *

Similar Documents

Publication Publication Date Title
CN108809542B (zh) 一种数据传输的处理方法和装置
CN108337633B (zh) 数据分流配置方法、基站系统和用户终端
WO2019101054A1 (zh) 聚合速率控制方法、设备以及系统
CN109714134B (zh) 接收窗口滑动方法及装置
WO2023207846A1 (zh) 通信方法和装置
US11647419B2 (en) Adjusting window size based on quality of experience
WO2022052102A1 (zh) 一种通信方法及装置
WO2024065516A1 (zh) 数据传输、数据指示装置以及方法
WO2023087145A1 (en) Methods and apparatuses for pdcp reordering management
WO2024168672A1 (zh) 数据处理方法和装置
WO2023184479A1 (en) Method and apparatus of supporting mobility
WO2024168688A1 (zh) 数据处理方法和装置
WO2024065524A1 (zh) 分组数据汇聚协议实体建立、分组数据汇聚协议实体建立指示装置以及方法
WO2024092725A1 (zh) 数据映射装置以及方法
WO2024098267A1 (zh) 数据传输装置、数据发送装置以及方法
WO2023184545A1 (zh) 一种数据传输方法及装置、通信设备
WO2023201607A1 (zh) 一种数据传输方法及装置、通信设备
WO2023184552A1 (zh) 一种数据传输方法及装置、通信设备
WO2024104101A1 (zh) 数据处理方法、装置、通信设备及可读存储介质
WO2023184537A1 (zh) 一种数据传输方法及装置、通信设备
WO2023108413A1 (en) Method and apparatus of reporting buffer status
WO2024055871A1 (zh) 一种通信系统中传输数据的方法和通信装置
US20240031861A1 (en) Communication method and device
WO2024174902A1 (zh) 通信方法和通信装置
WO2024164312A1 (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: 23921830

Country of ref document: EP

Kind code of ref document: A1