WO2024120328A1 - 数据包处理方法及装置 - Google Patents

数据包处理方法及装置 Download PDF

Info

Publication number
WO2024120328A1
WO2024120328A1 PCT/CN2023/136057 CN2023136057W WO2024120328A1 WO 2024120328 A1 WO2024120328 A1 WO 2024120328A1 CN 2023136057 W CN2023136057 W CN 2023136057W WO 2024120328 A1 WO2024120328 A1 WO 2024120328A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
protocol entity
indication information
target data
entity
Prior art date
Application number
PCT/CN2023/136057
Other languages
English (en)
French (fr)
Inventor
陈力
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2024120328A1 publication Critical patent/WO2024120328A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a data packet processing method and device.
  • the packet data aggregation protocol layer determines whether a data packet is discarded based on a discard timer.
  • the scheduling of the media intervention control layer may not be able to schedule all data packets for transmission in time, resulting in low resource utilization.
  • the embodiments of the present application provide a data packet processing method and device, which can optimize the processing of target data packets and improve resource utilization.
  • a method for processing a data packet comprising:
  • the first protocol entity discards the target data packet
  • the first condition includes at least one of the following:
  • the first protocol entity receives first indication information of the second protocol entity
  • the first protocol entity does not receive second indication information of the second protocol entity
  • the first protocol entity receives first indication information from the second protocol entity within a preset time period
  • the first protocol entity does not receive second indication information from the second protocol entity within a preset time period
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is an underlying protocol entity of the first protocol entity.
  • a data collection device which is included in a first protocol entity, and the device includes:
  • a first processing module configured to discard a target data packet when a first condition is met
  • the first condition includes at least one of the following:
  • the first protocol entity receives first indication information of the second protocol entity
  • the first protocol entity does not receive second indication information of the second protocol entity
  • the first protocol entity receives first indication information from the second protocol entity within a preset time period
  • the first protocol entity does not receive second indication information from the second protocol entity within a preset time period
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is an underlying protocol entity of the first protocol entity.
  • a third aspect provides a data packet processing method, including:
  • the second protocol entity sends first indication information or second indication information to the first protocol entity, wherein the first indication information is used to instruct the first protocol entity to discard the target data packet, and the second indication information is used to instruct the first protocol entity to retain or not discard the target data packet;
  • the fourth condition includes at least one of the following:
  • the preset sending cycle is reached
  • the remaining data packet delay budget PDB or the remaining data packet set delay budget PSDB times out
  • the data in the cache exceeds the channel capacity
  • the demand for the target data packet exceeds the processing capacity of the second protocol entity
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is an underlying protocol entity of the first protocol entity.
  • a data collection device which is included in a second protocol entity, and the device includes:
  • a second processing module configured to send first indication information or second indication information to the first protocol entity when the fourth condition is met, wherein the first indication information is used to instruct the first protocol entity to discard the target data packet, and the second indication information is used to instruct the first protocol entity to retain or not discard the target data packet;
  • the fourth condition includes at least one of the following:
  • the preset sending cycle is reached
  • the remaining data packet delay budget PDB or the remaining data packet set delay budget PSDB times out
  • the data in the cache exceeds the channel capacity
  • the demand for the target data packet exceeds the processing capacity of the second protocol entity
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is an underlying protocol entity of the first protocol entity.
  • a data packet processing device comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the data packet processing method described in the first aspect or the steps of the data packet processing method described in the third aspect are implemented.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the third aspect are implemented.
  • a chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the third aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the data packet processing method as described in the first aspect, or to implement the steps of the data packet processing method as described in the third aspect.
  • the first protocol entity discards the target data packet according to the first indication information or the second indication information of the second protocol entity, which can optimize the processing of the target data packet, improve resource utilization, and thereby increase the capacity of the communication system and save terminal power consumption.
  • FIG1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG. 2 is a schematic diagram of a flow chart of a method for processing a data packet on a first protocol entity side according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a flow chart of a method for processing data packets on the second protocol entity side according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of the structure of a first protocol entity side data packet collection device according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of the structure of a second protocol entity side data packet collection device according to an embodiment of the present application.
  • FIG6 is a schematic diagram of the structure of a communication device according to an embodiment of the present application.
  • first, second, etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by “first” and “second” are generally of the same type, and the number of objects is not limited.
  • the first object can be one or more.
  • “and/or” in the specification and claims represents at least one of the connected objects, and the character “/" generally represents that the objects associated with each other are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR new radio
  • FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/virtual reality (virtual reality, VR) device , robots, wearable devices (Wearable Device), vehicle user equipment (VUE), pedestrian user equipment (PUE), smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), game consoles, personal computers (personal computers, PCs), teller machines or self-service machines and other terminal side devices, wearable devices include: smart watches, smart bracelets, smart headphones,
  • the network side device 12 may include access network equipment or core network equipment, wherein the access network equipment may also be called wireless access network equipment, wireless access network (Radio Access Network, RAN), wireless access network function or wireless access network unit.
  • the access network equipment may include a base station, a wireless local area network (WLAN) access point or a WiFi node, etc.
  • WLAN wireless local area network
  • the base station may be called a node B, an evolved node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home node B, a home evolved node B, a transmitting and receiving point (TRP) or some other suitable term in the field.
  • eNB evolved node B
  • BTS base transceiver station
  • ESS extended service set
  • TRP transmitting and receiving point
  • the base station is not limited to specific technical vocabulary. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.
  • the uplink is mainly based on the transmission of relatively dense small data packets, which can carry information such as gestures and controls, and serve as input and reference for downlink presentation data;
  • the downlink is mainly based on the transmission of multimedia data such as video and audio, and the timely reception and presentation of these multimedia data provide users with an immersive experience.
  • data packets arrive periodically or quasi-periodically, the data rate can reach tens or even hundreds of Mbps, the frame rate (Frame per Second, FPS) is typically 60 or 120, and the interval between adjacent data packets is roughly 1/FPS second.
  • FPS Frame per Second
  • These data generally need to be successfully transmitted within 10ms on the air interface, and the transmission success rate is required to be no less than 99% or even 99.9%.
  • uplink may also transmit multimedia data such as video and audio. Its service characteristics are similar to those of downlink. Usually the data rate is relatively low, for example, at most tens of Mbps, and the time limit for air interface transmission can also be relaxed. For example, it generally needs to be successfully transmitted within 60ms.
  • the downlink data transmission characteristics are basically consistent with VR services.
  • Degree of Freedom describes the number of independent parameters used to define the movement of the viewport in 3D space.
  • XR Extended Reality
  • users can obtain information about new angles of view by turning their heads in the virtual reality experience.
  • the XR user's head turning action can be notified to the base station by sending an uplink signal.
  • the base station After receiving the uplink signal, the base station will schedule the required downlink data for the XR user to use.
  • XR services mainly include video data, audio data, and some control signaling and special data with control functions.
  • XR service transmission mainly involves uplink and downlink video/audio data transmission and interaction between user equipment (UE, also known as terminal) and wireless new networks (such as LTE/NR, etc.).
  • UE user equipment
  • wireless new networks such as LTE/NR, etc.
  • the UE needs to transmit some control signaling and special data with control functions through the wireless network uplink, which is used to control the generation, processing and downlink wireless transmission of video and audio service data in the XR service sent by the control network to the UE.
  • control information and special data with control functions include some service control data generated by the UE XR application encoder and control data information contained in the service transmission protocol, such as:
  • IDR Instantaneous Decoding Refresh
  • non-FOV Field of view
  • User behavior data collected by sensors such as pose/control data
  • the network can receive this data to determine user behavior, such as the user turning his head, and then adjust the content of the video data to be sent;
  • TCP transmission control protocol
  • ACK positive confirmation
  • TCP feedback transmission control protocol feedback
  • Real-time Transport Control Protocol (RTCP) ACK signaling is used to control the real-time transmission of data and confirm the real-time requirements and time synchronization of business data transmission.
  • RTCP Real-time Transport Control Protocol
  • the network usually needs to receive these control signaling and special data with control functions from the UE in a timely and reliable manner to obtain the transmission status of the current service and related necessary control information; the application server needs to further generate the video and audio service data required for subsequent transmission based on this information, and pass it to the wireless network for processing and transmission, and finally send these service data downlink to the UE.
  • XR services are quasi-periodic services, which means that service packets arrive at equal intervals, and the intervals are small floating-point numbers (non-positive integers) (for example, 30FPS (FPS refers to the number of frames per second) ⁇ 33.33ms, 60FPS ⁇ 16.67ms, 120FPS ⁇ 8.33ms).
  • XR services have very high latency requirements, and the air interface transmission delay budget requirement (PDB) is about 10ms.
  • the time of each service packet has a certain range of deviations. This deviation is called jitter.
  • the jitter deviation follows a truncated Gaussian distribution, and the range is ⁇ 4ms before and after the time position of the quasi-periodic service packet.
  • the time it takes for a packet to arrive at the base station is n (unit: ms). Due to the influence of jitter, the actual arrival time of the packet is n+j, where j is the size of the jitter. For example, if the jitter is -1ms, it means that the packet that should have arrived at time n actually arrives at n-1ms.
  • BSR Buffer Status Report
  • NR logical channel group
  • LCG logical channel group
  • NR supports the simultaneous configuration of up to 8 logical channel groups for a single UE.
  • BSR is triggered based on the following events:
  • the number of padding bits in the new TB is greater than or equal to the number of bits occupied by (a single BSR medium access control (MAC) control element (CE) + its corresponding subheader) (i.e., the padding bits in the new TB can also accommodate the bits corresponding to a single BSR MAC CE), then the Padding BSR will be triggered;
  • MAC medium access control
  • CE control element
  • the retxBSR-Timer timer times out and at least one logical channel has uplink data to be transmitted, which triggers the Regular BSR.
  • SR Scheduling Request
  • the UE When the Periodic BSR is triggered, the UE includes a BSR MAC CE in the constructed uplink TB only when there are new uplink transmission resources, but does not actively request new uplink transmission resources from the network by triggering the SR.
  • the UE When the Padding BSR is triggered, the UE directly includes a BSR MAC CE in the new uplink TB.
  • This embodiment involves the uplink data processing and sending process of the wireless communication AS (Access Statum) of the UE.
  • AS Access Statum
  • the following is a description of the prior art of the main protocol layers and related functions involved.
  • Packet Data Convergence Protocol (PDCP) layer and radio bearer (1) Packet Data Convergence Protocol (PDCP) layer and radio bearer:
  • the service data generated by the UE's application layer (Application, APP) will be classified into different service data flows according to their corresponding quality of service (Quality-of-service, QoS) requirements, and each service data flow corresponds to the same or similar QoS requirements.
  • QoS quality of service
  • the service data flow corresponds to a QoS flow
  • the service data flow corresponds to an Evolved Packet System (Evolved Packet System, EPS) bearer.
  • EPS Evolved Packet System
  • Service data is delivered to the AS layer in the form of packets, and is further mapped to a radio bearer at the AS layer according to its corresponding QoS flow (NR) or EPS bearer (LTE).
  • a radio bearer consists of a PDCP entity (PDCP protocol layer processing entity), an RLC entity (PDCP protocol layer processing entity) and the corresponding logical channel (located at the MAC protocol layer).
  • PDCP service data unit SDU
  • the PDCP entity will generate a corresponding PDCP protocol data unit (PDU) for each PDCP SDU that arrives, and set a PDCP sequence number (SN) to indicate the transmission order of each PDCP SDU and its corresponding PDCP PDU in the PDCP entity; wherein the value of the PDCP SN is set according to the order in which the PDCP SDU is delivered to the PDCP entity, and the transmission order of the PDCP SDU that arrives first is first, and the order of the PDCP SDU that arrives later is later.
  • PDU PDCP protocol data unit
  • SN PDCP sequence number
  • the PDCP entity will maintain an internal variable, TX_NEXT, which indicates the total number of PDCP PDUs transmitted by the PDCP entity, and is used to set the value of the PDCP SN; it is initialized to 0 when the PDCP entity is established.
  • TX_NEXT an internal variable
  • the PDCP entity will set the SN of the PDCP PDU corresponding to the PDCP SDU to TX_NEXT, and increase TX NEXT by 1.
  • the PDCP entity will add a header file to each PDCP SDU and generate the corresponding PDCP PDU, which contains the SN value set for the PDCP PDU.
  • the PDCP Entity usually passes the PDCP PDU to the lower protocol layer (RLC) in order for subsequent processing and transmission according to the order of the SN contained in the PDCP PDU.
  • RLC protocol layer
  • SN is an ordinal number, indicating the number of each PDCP SDU transmitted.
  • the general principle is that the earlier the PDCP SDU arrives at the PDCP entity, the smaller the SN value, and the earlier it is transmitted.
  • the PDCP PDUs transmitted from the PDCP entity to the corresponding RLC entity will be cached in the UE buffer as RLC SDUs to be transmitted and further processed by the RLC entity. Specifically, when a logical channel corresponding to a certain RLC entity is allocated certain transmission resources, the RLC entity will determine which RLC SDUs can be multiplexed into the allocated transmission resources for transmission based on the amount of data that the allocated transmission resources can accommodate and the amount of data of the RLC SDUs to be transmitted in the buffer.
  • the RLC entity For one or more RLC SDUs determined by the RLC entity that can be fully multiplexed into the allocated transmission resources, the RLC entity will add corresponding RLC header files to these RLC SDUs, generate corresponding RLC PDUs, and pass them to the lower protocol layer (MAC) for subsequent processing and transmission.
  • MAC protocol layer
  • the RLC entity After multiplexing the above complete RLC PDUs, if there are still some resources remaining but not enough to reuse another complete RLC SDU (that is, the amount of data that the resources can support is less than the amount of data required to multiplex the next RLC SDU), the RLC entity will perform segmentation processing, that is, add a header file to part of the data of the next RLC SDU to be transmitted, generate an RLC PDU and pass it to the lower protocol layer for subsequent processing and transmission.
  • the remaining part will still be retained in the UE buffer and wait for the arrival of the next uplink transmission resource before transmission.
  • Each RLC entity corresponding to a radio bearer further corresponds to a logical channel in the MAC layer.
  • the UE's MAC entity will further allocate the uplink transmission resources among multiple logical channels.
  • each logical channel corresponds to a logical channel priority.
  • the UE's MAC entity allocates resources for each logical channel in descending order of logical channel priority based on the resource allocation mechanism of logical channel prioritization (LCP).
  • LCP resource allocation mechanism of logical channel prioritization
  • the corresponding RLC entity will pass one or more RLC PDUs to the corresponding logical channel of the MAC layer.
  • the MAC layer will use these RLC PDUs obtained from the RLC entity for each logical channel as MAC SDUs to be transmitted, add the MAC header file corresponding to the corresponding logical channel, form the MAC subPDU of the corresponding logical channel, and multiplex it into the entire transmission resource as the data sent by this logical channel for this uplink transmission.
  • the MAC subPDUs of multiple logical channels will be combined together to form a MAC PDU, which will be transmitted to the network through wireless signals as the data packet sent in this uplink.
  • the UE since the RLC entity will segment the RLC SDU (as mentioned above), for each uplink transmission resource obtained by the UE, the UE needs to first multiplex the remaining part of the RLC SDU that was segmented in the previous transmission and has not yet been transmitted into the resource for transmission, and then transmit the data packets corresponding to other subsequent RLC SDUs.
  • the UE In general, in the existing LTE and NR networks, the UE usually adopts the principle of "first arrive, first transmit" to implement the above-mentioned uplink data processing and transmission process for the data of each radio bearer. Specifically, for each radio bearer, the UE will process the data packets in the order in which the data packets (SDU) are delivered to the corresponding entity of this layer at each of the above-mentioned protocol layers, and pass the processed data packets (PDU) to the next protocol layer in sequence.
  • SDU data packets
  • PDU processed data packets
  • the corresponding PDCP entity will set a forward PDCP SN value for it, so that it can be processed by the above-mentioned protocol layers first, and be multiplexed into the uplink resources for transmission first; and the data packets that arrive later will be assigned a later PDCP SN value, and will usually be processed, multiplexed and transmitted by the above-mentioned protocol layers after the data packets that arrive first.
  • the UE ultimately executes a sequential transmission mechanism according to the order in which the data packets arrive at the AS.
  • the main reason for adopting this principle is based on transmission delay considerations: in existing wireless networks, the transmission delay requirements for data in each wireless bearer are basically the same, and existing wireless networks do not allow the UE AS layer to obtain the specific content of each data packet and cannot perform differentiated processing for each data packet; therefore, performing uplink processing, scheduling, and transmission of data packets in the order in which they arrive is a more reasonable approach in the existing technology from the perspective of ensuring delay as much as possible.
  • the discard timer of the PDCP layer only the data bearer (DRB) has a discard timer.
  • the sending side will start a new timer for each SDU from the upper layer, and discard the SDU after the timeout to prevent sending buffer congestion.
  • the specific duration of this timer is configured by the upper layer RRC. Specifically, when a PDCP SDU delivered by the upper layer is received, the PDCP entity on the sending side starts a discard timer associated with this PDCP SDU.
  • the PDCP entity on the sending side needs to discard this PDCP SDU and the corresponding PDCP data PDU. If this PDCP data PDU has been passed to the lower layer, it is necessary to instruct the lower layer to discard it.
  • SRB signaling bearer
  • the existing technologies all use the PDCP layer to determine whether to discard a data packet based on the configured PDCP layer discard timer.
  • the MAC layer may not be able to schedule all data packets for transmission in time, and the PDCP layer may not know the resource status of the MAC layer. Therefore, the specific packet discard processing requires collaboration between the MAC layer and the PDCP layer.
  • the present application embodiment provides a data packet processing method, as shown in FIG2, including:
  • Step 101 When a first condition is met, the first protocol entity discards the target data packet
  • the first condition includes at least one of the following:
  • the first protocol entity receives first indication information of the second protocol entity
  • the first protocol entity does not receive second indication information of the second protocol entity
  • the first protocol entity receives first indication information from the second protocol entity within a preset time period
  • the first protocol entity does not receive second indication information from the second protocol entity within a preset time period
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is an underlying protocol entity of the first protocol entity, the first protocol entity includes at least one of the following: application layer entity, non-access stratum (NAS) entity, PDCP entity, RLC entity, MAC entity, the second protocol entity includes at least one of the following: RLC entity, MAC entity, physical (Physics, PHY) entity.
  • the first protocol entity discards the target data packet according to the first indication information or the second indication information of the second protocol entity, which can optimize the processing of the target data packet, improve resource utilization, and thereby increase the capacity of the communication system and save terminal power consumption.
  • the first condition further includes:
  • the first protocol entity receives the first indication information of the second protocol entity and satisfies a second condition, where the second condition includes at least one of the following:
  • the first timer times out
  • the first data unit associated with the target data packet is a data unit within a first target class packet or the first data unit is a first target class packet;
  • the first data unit belongs to a first target class data packet or the first data unit belongs to a group where the first target class data packet belongs;
  • the priority of the first data unit, or the priority of its corresponding PDU, or the priority of its corresponding SDU is lower than a preset first threshold, such as when the priority identifier of the data packet, or the PDU, or the SDU is lower than a threshold value, wherein data packets of different priorities may be transmitted in a QoS flow, or the same QoS flow, but some data packets are more important, such as: IDR frames;
  • the first data unit is successfully transmitted
  • first target information that the first data unit needs to be discarded, where the first target information is used to indicate at least one of the following:
  • the terminal Whether the terminal supports carrier aggregation (CA) or dual connectivity (DC). For example, the terminal does not support carrier aggregation (CA) or dual connectivity (DC).
  • CA carrier aggregation
  • DC dual connectivity
  • carrier aggregation CA or dual connectivity DC is configured for the terminal, for example, the network side device does not configure carrier aggregation CA or dual connectivity DC for the terminal;
  • the terminal has activated carrier aggregation CA or dual connectivity DC, for example, the terminal has not activated carrier aggregation CA or dual connectivity DC;
  • resources configured by the network side device for the terminal or resources used to transmit the first data unit, such as insufficient resources, the resources configured by the network side device for the terminal are less than or equal to a preset threshold, or the resources used to transmit the first data unit are less than or equal to a preset threshold;
  • the memory or cache space of the terminal for example, the memory or cache space of the terminal is insufficient, and the layer 1, layer 2, layer 3, and radio resource control cache size are less than a preset threshold;
  • the capabilities of the terminal such as insufficient capabilities of the terminal, one or more capabilities being lower than a preset value;
  • RSRP Reference Signal Receiving Power
  • RSRQ Reference Signal Receiving Quality
  • SINR Signal to Interference plus Noise Ratio
  • the size of the first data unit, or the size of its corresponding PDU, or the size of its corresponding SDU, or the size of its corresponding buffer status report BSR, or the size of its corresponding status report SR, such as any one of the above items is greater than or equal to a preset threshold;
  • the queue of the first data unit, or the queue of data to be transmitted by the terminal such as the number of data packets in the first target data queue of the terminal is greater than or equal to a preset threshold;
  • the first target data queue includes: the queue of the first data unit, or the queue of data to be transmitted;
  • the size of the queue of the first data unit, or the queue of data to be transmitted by the terminal is greater than or equal to a preset threshold;
  • the first target data queue includes: the queue of the first data unit, or the queue of data to be transmitted;
  • the packet error rate of the first data unit, or the packet error rate of its corresponding PDU, or the packet error rate of its corresponding SDU, such as the packet error rate of the data packet, or the PDU, or the SDU is greater than or equal to a preset threshold.
  • This situation requires a certain feedback mechanism, which may not be limited to the UE side, for example, sidelink and other scenarios can be considered;
  • the delay of the target data packet, or the delay of its corresponding PDU, or the delay of its corresponding SDU, for example, any one of the above items is greater than or equal to a preset threshold, or the delay difference of the associated data unit is greater than or equal to a preset threshold.
  • the method further comprises:
  • the first protocol entity retains or does not discard the target data packet
  • the third condition includes at least one of the following:
  • the first protocol entity does not receive the first indication information of the second protocol entity
  • the first protocol entity receives second indication information of the second protocol entity
  • the first protocol entity does not receive first indication information from the second protocol entity within a preset time period
  • the first protocol entity receives second indication information from the second protocol entity within a preset time period
  • the first protocol entity reserves the target data packet according to the first indication information or the second indication information of the second protocol entity, which can optimize the processing of the target data packet, improve resource utilization, and thereby increase the capacity of the communication system and save terminal power consumption.
  • the target data packet is the data packet corresponding to the first indication information or the second indication information, or the target data packet is the data packet indicated by the first indication information or the second indication information.
  • the data packet identifier of the target data packet can be carried in the first indication information or the second indication information so that the first protocol entity determines the target data packet.
  • the first indication information indicates at least one of the following:
  • the target data packet can be discarded, so that the first protocol entity can discard the target data packet according to the first indication information, thereby ensuring transmission validity and saving system resources;
  • the target data packet is discarded, that is, the second protocol entity has discarded the target data packet, so the first protocol entity does not need to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the second protocol entity schedules a new transmission, so that the first protocol entity does not need to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the delay of the target data packet exceeds the preset delay, so that the first protocol entity no longer needs to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the scheduling or transmission of the target data packet exceeds the preset delay, so that the first protocol entity no longer needs to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the target data packet cannot be transmitted within the preset delay, indicating that the delay of the target data packet cannot be guaranteed, and the first protocol entity may discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the target data packet is successfully transmitted, which means that the target data packet is successfully transmitted at the transmitting end, so that the first protocol entity does not need to retain the target data packet and can discard the target data packet according to the first indication information to save system resources;
  • the feedback information corresponding to the target data packet includes an ACK or NACK, which is used to feedback whether the target data packet is correctly transmitted to the target node.
  • the feedback information corresponding to the target data packet is ACK
  • the first protocol entity does not need to retain the target data packet any more, and can discard the target data packet according to the first indication information to save system resources.
  • the second indication information indicates at least one of the following:
  • the target data packet cannot be discarded, for example, even if the target data packet exceeds a preset time, the target data packet cannot be discarded, so that the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet is not discarded, for example, the target data packet is not discarded after exceeding a preset time, so that the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet will be retransmitted or is being retransmitted, for example, the target data packet exceeds a preset time and is retransmitted or is being retransmitted, and the first protocol entity still needs to retain the target data packet to ensure the reliability of data packet transmission;
  • the delay of the target data packet does not exceed the preset delay, the first protocol entity still needs to retain the target data packet, and the first protocol entity may retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the scheduling or transmission of the target data packet does not exceed the preset delay, which means that the preset delay will not be exceeded, including the current transmission scheduling and the future transmission scheduling.
  • the first protocol entity may retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet can be transmitted within the preset delay, which means that the current scheduled transmission does not exceed the preset delay, and the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet is not successfully transmitted, and the first protocol entity still needs to retain the target data packet.
  • the first protocol entity may retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the feedback information corresponding to the target data packet includes ACK or NACK, which is used to feedback whether the target data packet is correctly transmitted to the target node.
  • the feedback information corresponding to the target data packet is NACK
  • the first protocol entity still needs to retain the target data packet, and the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission.
  • the preset delay includes at least one of the following:
  • PDB Packet delay budget
  • PSDB PDU set delay budget
  • Residual PDB or Residual PSDB are Residual PDB or Residual PSDB.
  • the remaining PDB or the remaining PSDB is the difference between a first parameter and a second parameter, wherein the first parameter includes any one of the following:
  • Access network PDB or PSDB that is, the PDB or PSDB corresponding to the data packet on the access network side;
  • the second parameter includes at least one of the following:
  • PDB or PSDB is the delay requirement of the terminal or the delay requirement of the terminal in a preset node, such as PDB or PSDB of the wireless access network, or PDB or PSDB of the core network.
  • the target data packet includes at least one of the following:
  • RLC carries the corresponding data packets, including: protocol data unit (PDU), protocol data unit set (PDU set), frame (Frame), burst set (Burst), slice (Slice), picture (Picture), group of picture (Group of picture, GOP), group of PDU set (group of PDU set), group of PDU, etc.
  • Data packets corresponding to MAC SDU including: PDU, PDU set, Burst, Frame, Slice, Picture, Group of picture (GOP), group of PDU set, group of PDU, etc.
  • the data packets corresponding to MAC PDU include: PDU, PDU set, Burst, Frame, Slice, Picture, Group of picture (GOP), group of PDU set, group of PDU, etc.
  • the first indication information or the second indication information may be included in an inter-layer primitive sent by the second protocol entity to the first protocol entity, so as to ensure the transmission reliability of the first indication information and the second indication information.
  • Inter-layer primitives refer to primitive communications between protocol entities at different layers, including but not limited to: request, response, confirmation, indication and other primitives.
  • the present application embodiment provides a data packet processing method, as shown in FIG3, including:
  • Step 201 When the fourth condition is met, the second protocol entity sends first indication information or second indication information to the first protocol entity, wherein the first indication information is used to instruct the first protocol entity to discard a target data packet, and the second indication information is used to instruct the first protocol entity to retain or not discard the target data packet;
  • the fourth condition includes at least one of the following:
  • the second protocol entity may send the first indication information or the second indication information to the first protocol entity according to the preset sending cycle, where the preset sending cycle is agreed upon in the protocol or configured by the network side device;
  • the second protocol entity may send first indication information or second indication information to the first protocol entity, indicating to discard or retain the target data packet;
  • the second protocol entity may send first indication information or second indication information to the first protocol entity, indicating to discard or retain the target data packet;
  • the second protocol entity may send first indication information or second indication information to the first protocol entity, indicating to discard or retain the target data packet;
  • the demand for the target data packet exceeds the processing capacity (low layer processing capacity) of the second protocol entity, and the second protocol entity may send first indication information or second indication information to the first protocol entity, instructing to discard or retain the target data packet;
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is the underlying protocol entity of the first protocol entity, the first protocol entity includes at least one of the following: application layer entity, NAS entity, PDCP entity, RLC entity, MAC entity, the second protocol entity includes at least one of the following: RLC entity, MAC entity, PHY entity.
  • the first protocol entity discards the target data packet according to the first indication information or the second indication information of the second protocol entity, which can optimize the processing of the target data packet, improve resource utilization, and thereby increase the capacity of the communication system and save terminal power consumption.
  • the target data packet is the data packet corresponding to the first indication information or the second indication information, or the target data packet is the data packet indicated by the first indication information or the second indication information.
  • the data packet identifier of the target data packet can be carried in the first indication information or the second indication information so that the first protocol entity determines the target data packet.
  • the first indication information indicates at least one of the following:
  • the target data packet can be discarded, so that the first protocol entity can discard the target data packet according to the first indication information, thereby ensuring transmission validity and saving system resources;
  • the target data packet is discarded, that is, the second protocol entity has discarded the target data packet, so the first protocol entity does not need to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the second protocol entity schedules a new transmission, so that the first protocol entity does not need to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the delay of the target data packet exceeds the preset delay, so that the first protocol entity no longer needs to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the scheduling or transmission of the target data packet exceeds the preset delay, so that the first protocol entity no longer needs to retain the target data packet and can discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the target data packet cannot be transmitted within the preset delay, indicating that the delay of the target data packet cannot be guaranteed, and the first protocol entity may discard the target data packet according to the first indication information to ensure transmission validity and save system resources;
  • the target data packet is successfully transmitted, which means that the target data packet is successfully transmitted at the transmitting end, so that the first protocol entity does not need to retain the target data packet and can discard the target data packet according to the first indication information to save system resources;
  • the feedback information corresponding to the target data packet includes an acknowledgment message (ACK) or a negative acknowledgement message (NACK), which is used to feedback whether the target data packet is correctly transmitted to the target node.
  • ACK acknowledgment message
  • NACK negative acknowledgement message
  • the first protocol entity does not need to retain the target data packet any more, and can discard the target data packet according to the first indication information to save system resources.
  • the second indication information indicates at least one of the following:
  • the target data packet cannot be discarded, for example, even if the target data packet exceeds a preset time, the target data packet cannot be discarded, so that the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet is not discarded, for example, the target data packet is not discarded after exceeding a preset time, so that the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet will be retransmitted or is being retransmitted, for example, the target data packet exceeds a preset time and is retransmitted or is being retransmitted, and the first protocol entity still needs to retain the target data packet to ensure the reliability of data packet transmission;
  • the delay of the target data packet does not exceed the preset delay, the first protocol entity still needs to retain the target data packet, and the first protocol entity may retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the scheduling or transmission of the target data packet does not exceed the preset delay, which means that the preset delay will not be exceeded, including the current transmission scheduling and the future transmission scheduling.
  • the first protocol entity may retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet can be transmitted within the preset delay, which means that the current scheduled transmission does not exceed the preset delay, and the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the target data packet is not successfully transmitted, and the first protocol entity still needs to retain the target data packet.
  • the first protocol entity may retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission;
  • the feedback information corresponding to the target data packet includes an acknowledgment message (ACK) or a negative acknowledgement message (NACK), which is used to feedback whether the target data packet is correctly transmitted to the target node.
  • ACK acknowledgment message
  • NACK negative acknowledgement message
  • the first protocol entity still needs to retain the target data packet, and the first protocol entity can retain or not discard the target data packet according to the second indication information to ensure the reliability of data packet transmission.
  • the preset delay includes at least one of the following:
  • Residual PDB or Residual PSDB are Residual PDB or Residual PSDB.
  • the remaining PDB or the remaining PSDB is the difference between a first parameter and a second parameter, wherein the first parameter includes any one of the following:
  • the second parameter includes at least one of the following:
  • PDB or PSDB is the delay requirement of the terminal or the delay requirement of the terminal in a preset node, such as the PDB or PSDB of the wireless access network, or the PDB or PSDB of the core network.
  • the target data packet includes at least one of the following:
  • RLC carries the corresponding data packets, including: protocol data unit (PDU), protocol data unit set (PDU set), frame (Frame), burst set (Burst), slice (Slice), picture (Picture), group of picture (Group of picture, GOP), group of PDU set (group of PDU set), group of PDU, etc.
  • Data packets corresponding to MAC SDU including: PDU, PDU set, Burst, Frame, Slice, Picture, Group of picture (GOP), group of PDU set, group of PDU, etc.
  • the data packets corresponding to MAC PDU include: PDU, PDU set, Burst, Frame, Slice, Picture, Group of picture (GOP), group of PDU set, group of PDU, etc.
  • the first indication information or the second indication information may be included in an inter-layer primitive sent by the second protocol entity to the first protocol entity, so as to ensure the transmission reliability of the first indication information and the second indication information.
  • Inter-layer primitives refer to primitive communications between protocol entities at different layers, including but not limited to: request, response, confirmation, indication and other primitives.
  • the data packet processing method provided in the embodiment of the present application can be executed by a data acquisition device.
  • the data acquisition device provided in the embodiment of the present application is described by taking the data acquisition device executing the data packet processing method as an example.
  • the embodiment of the present application provides a data collection device, as shown in FIG4 , which is applied to a first protocol entity 300 and includes:
  • a first processing module 310 configured to discard a target data packet when a first condition is met
  • the first condition includes at least one of the following:
  • the first protocol entity receives first indication information of the second protocol entity
  • the first protocol entity does not receive second indication information of the second protocol entity
  • the first protocol entity receives first indication information from the second protocol entity within a preset time period
  • the first protocol entity does not receive second indication information from the second protocol entity within a preset time period
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is the underlying protocol entity of the first protocol entity, the first protocol entity includes at least one of the following: application layer entity, NAS entity, PDCP entity, RLC entity, MAC entity, the second protocol entity includes at least one of the following: RLC entity, MAC entity, PHY entity.
  • the first protocol entity discards the target data packet according to the first indication information or the second indication information of the second protocol entity, which can optimize the processing of the target data packet, improve resource utilization, and thereby increase the capacity of the communication system and save terminal power consumption.
  • the first condition further includes:
  • the first protocol entity receives the first indication information of the second protocol entity and satisfies a second condition, where the second condition includes at least one of the following:
  • the first timer times out
  • the first data unit associated with the target data packet is a data unit within a first target class packet or the first data unit is a first target class packet;
  • the first data unit belongs to a first target class data packet or the first data unit belongs to a group where the first target class data packet belongs;
  • the priority of the first data unit, or the priority of its corresponding PDU, or the priority of its corresponding SDU is lower than a preset first threshold, such as when the priority identifier of the data packet, or the PDU, or the SDU is lower than a threshold value, wherein data packets of different priorities may be transmitted in one QoS flow, or the same QoS flow, but some data packets are more important, such as: IDR (Instant Decoding Refresh) frame;
  • the first data unit is successfully transmitted
  • first target information that the first data unit needs to be discarded, where the first target information is used to indicate at least one of the following:
  • the terminal Whether the terminal supports carrier aggregation CA or dual connectivity DC, for example, the terminal does not support carrier aggregation CA or dual connectivity DC;
  • carrier aggregation CA or dual connectivity DC is configured for the terminal, for example, the network side device does not configure carrier aggregation CA or dual connectivity DC for the terminal;
  • the terminal has activated carrier aggregation CA or dual connectivity DC, for example, the terminal has not activated carrier aggregation CA or dual connectivity DC;
  • resources configured by the network side device for the terminal or resources used to transmit the first data unit, such as insufficient resources, the resources configured by the network side device for the terminal are less than or equal to a preset threshold, or the resources used to transmit the first data unit are less than or equal to a preset threshold;
  • the memory or cache space of the terminal for example, the memory or cache space of the terminal is insufficient, and the layer 1, layer 2, layer 3, and radio resource control cache size are less than a preset threshold;
  • the capabilities of the terminal such as insufficient capabilities of the terminal, one or more capabilities being lower than a preset value;
  • the size of the first data unit, or the size of its corresponding PDU, or the size of its corresponding SDU, or the size of its corresponding BSR, or the size of its corresponding SR, such as any one of the above items is greater than or equal to a preset threshold;
  • the queue of the first data unit, or the queue of data to be transmitted by the terminal such as the number of data packets in the first target data queue of the terminal is greater than or equal to a preset threshold;
  • the first target data queue includes: the queue of the first data unit, or the queue of data to be transmitted;
  • the queue of the first data unit, or the size of the data queue to be transmitted by the terminal such as the total size of the data packets in the first target data queue of the terminal is greater than or equal to a preset threshold;
  • the first target data queue includes: the queue of the first data unit, or the queue of data to be transmitted;
  • the latency requirement of the terminal or the first data unit; or the PDB requirement of the terminal or the first data unit, such as the latency or PDB or waiting time of the terminal or the data packet reaches a preset threshold or a preset timer;
  • the packet error rate of the first data unit, or the packet error rate of its corresponding PDU, or the packet error rate of its corresponding SDU, such as the packet error rate of the data packet, or the PDU, or the SDU is greater than or equal to a preset threshold.
  • This situation requires a certain feedback mechanism, which may not be limited to the UE side, for example, Sidelink and other scenarios can be considered;
  • the delay of the target data packet, or the delay of its corresponding PDU, or the delay of its corresponding SDU, for example, any one of the above items is greater than or equal to a preset threshold, or the delay difference of the associated data unit is greater than or equal to a preset threshold.
  • the first processing module 310 is further configured to retain or not discard the target data packet if a third condition is met;
  • the third condition includes at least one of the following:
  • the first protocol entity does not receive the first indication information of the second protocol entity
  • the first protocol entity receives second indication information of the second protocol entity
  • the first protocol entity does not receive first indication information from the second protocol entity within a preset time period
  • the first protocol entity receives second indication information from the second protocol entity within a preset time period
  • the first indication information indicates at least one of the following:
  • the target data packet can be discarded
  • the target data packet is discarded
  • the second protocol entity schedules a new transmission
  • the delay of the target data packet exceeds the preset delay
  • the scheduling or transmission of the target data packet exceeds a preset delay
  • the target data packet cannot be transmitted within the preset delay
  • the target data packet is successfully transmitted
  • the feedback information corresponding to the target data packet is the feedback information corresponding to the target data packet.
  • the second indication information indicates at least one of the following:
  • the target data packet cannot be discarded
  • the target data packet is not discarded
  • the target data packet will be retransmitted or is being retransmitted;
  • the delay of the target data packet does not exceed the preset delay
  • the scheduling or transmission of the target data packet does not exceed a preset delay
  • the target data packet can be transmitted within a preset delay
  • the target data packet is not successfully transmitted
  • the feedback information corresponding to the target data packet is the feedback information corresponding to the target data packet.
  • the preset delay includes at least one of the following:
  • Residual PDB or Residual PSDB are Residual PDB or Residual PSDB.
  • the remaining PDB or the remaining PSDB is the difference between a first parameter and a second parameter, wherein the first parameter includes any one of the following:
  • the second parameter includes at least one of the following:
  • the target data packet includes at least one of the following:
  • RLC carries the corresponding data packets
  • the first indication information or the second indication information is included in an inter-layer primitive sent by the second protocol entity to the first protocol entity.
  • the embodiment of the present application provides a data packet processing device, as shown in FIG5 , which is applied to a second protocol entity 400, including:
  • the second processing module 410 is used to send first indication information or second indication information to the first protocol entity when the fourth condition is met, wherein the first indication information is used to instruct the first protocol entity to discard the target data packet, and the second indication information is used to instruct the first protocol entity to retain or not discard the target data packet;
  • the fourth condition includes at least one of the following:
  • the preset sending cycle is reached
  • the remaining data packet delay budget PDB or the remaining data packet set delay budget PSDB times out
  • the data in the cache exceeds the channel capacity
  • the demand for the target data packet exceeds the processing capacity of the second protocol entity
  • the target data packet is a data packet corresponding to the first indication information or the second indication information
  • the second protocol entity is the underlying protocol entity of the first protocol entity, the first protocol entity includes at least one of the following: application layer entity, NAS entity, PDCP entity, RLC entity, MAC entity, the second protocol entity includes at least one of the following: RLC entity, MAC entity, PHY entity.
  • the first protocol entity discards the target data packet according to the first indication information or the second indication information of the second protocol entity, which can optimize the processing of the target data packet, improve resource utilization, and thereby increase the capacity of the communication system and save terminal power consumption.
  • the first indication information indicates at least one of the following:
  • the target data packet can be discarded
  • the target data packet is discarded
  • the second protocol entity schedules a new transmission
  • the delay of the target data packet exceeds the preset delay
  • the scheduling or transmission of the target data packet exceeds a preset delay
  • the target data packet cannot be transmitted within the preset delay
  • the target data packet is successfully transmitted
  • the feedback information corresponding to the target data packet is the feedback information corresponding to the target data packet.
  • the second indication information indicates at least one of the following:
  • the target data packet cannot be discarded
  • the target data packet is not discarded
  • the target data packet will be retransmitted or is being retransmitted;
  • the delay of the target data packet does not exceed the preset delay
  • the scheduling or transmission of the target data packet does not exceed a preset delay
  • the target data packet can be transmitted within a preset delay
  • the target data packet is not successfully transmitted
  • the feedback information corresponding to the target data packet is the feedback information corresponding to the target data packet.
  • the preset delay includes at least one of the following:
  • Residual PDB or Residual PSDB are Residual PDB or Residual PSDB.
  • the remaining PDB or the remaining PSDB is the difference between a first parameter and a second parameter, wherein the first parameter includes any one of the following:
  • the second parameter includes at least one of the following:
  • the target data packet includes at least one of the following:
  • RLC carries the corresponding data packets
  • the first indication information or the second indication information is included in an inter-layer primitive sent by the second protocol entity to the first protocol entity.
  • the data acquisition device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device may be a terminal, or may be other devices other than a terminal.
  • the terminal may include but is not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (NAS), etc.
  • NAS network attached storage
  • the data packet processing device provided in the embodiment of the present application can implement the various processes implemented by the method embodiments of Figures 2 to 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, wherein the memory 602 stores a program or instruction that can be run on the processor 601.
  • the communication device 600 is a network side device
  • the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned data packet processing method embodiment, and can achieve the same technical effect.
  • the communication device 600 is a terminal
  • the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned data packet processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • each process of the above-mentioned data packet processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
  • An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data packet processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the embodiment of the present application further provides a computer program/program product, which is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the various processes of the above-mentioned data packet processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the disclosed part may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present application.
  • a storage medium such as ROM/RAM, magnetic disk, optical disk

Landscapes

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

Abstract

本申请公开了一种数据包处理方法及装置，属于通信技术领域，本申请实施例的数据包处理方法，包括：在满足第一条件的情况下，第一协议实体丢弃目标数据包；第一条件包括以下至少一项：第一协议实体接收到第二协议实体的第一指示信息；第一协议实体未接收到第二协议实体的第二指示信息；第一协议实体在预设时间段内接收到第二协议实体的第一指示信息；第一协议实体在预设时间段内未接收到第二协议实体的第二指示信息；其中，目标数据包为第一指示信息或第二指示信息对应的数据包；第二协议实体为第一协议实体的底层协议实体。

Description

数据包处理方法及装置
相关申请的交叉引用
本申请主张在2022年12月09日在中国提交的中国专利申请No.202211585926.2的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种数据包处理方法及装置。
背景技术
在相关技术中的包丢弃(Packet discard/drop)机制中，分组数据汇聚协议层根据丢弃定时器来确定数据包是否丢弃，但是媒体介入控制层的调度可能并不能及时将所有的数据包都调度传输，导致资源利用率较低。
发明内容
本申请实施例提供一种数据包处理方法及装置，能够优化目标数据包的处理，提高资源利用率。
第一方面，提供了一种数据包处理方法，包括：
在满足第一条件的情况下，第一协议实体丢弃目标数据包；
所述第一条件包括以下至少一项：
所述第一协议实体接收到所述第二协议实体的第一指示信息；
所述第一协议实体未接收到所述第二协议实体的第二指示信息；
所述第一协议实体在预设时间段内接收到所述第二协议实体的第一指示信息；
所述第一协议实体在预设时间段内未接收到所述第二协议实体的第二指示信息；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体。
第二方面，提供了一种数据采集装置，包含于第一协议实体，该装置包括：
第一处理模块，用于在满足第一条件的情况下，丢弃目标数据包；
所述第一条件包括以下至少一项：
第一协议实体接收到所述第二协议实体的第一指示信息；
所述第一协议实体未接收到所述第二协议实体的第二指示信息；
所述第一协议实体在预设时间段内接收到所述第二协议实体的第一指示信息；
所述第一协议实体在预设时间段内未接收到所述第二协议实体的第二指示信息；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体。
第三方面，提供了一种数据包处理方法，包括：
在满足第四条件的情况下，第二协议实体向第一协议实体发送第一指示信息或第二指示信息，所述第一指示信息用以指示所述第一协议实体丢弃目标数据包，所述第二指示信息用以指示所述第一协议实体保留或不丢弃所述目标数据包；
所述第四条件包括以下至少一项：
到达预设的发送周期；
信道冲突；
剩余数据包延时预算PDB或剩余数据包集合延时预算PSDB超时；
缓存中的数据超出信道容量；
所述目标数据包的需求超出所述第二协议实体的处理容量；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体。
第四方面，提供了一种数据采集装置，包含于第二协议实体，该装置包括：
第二处理模块，用于在满足第四条件的情况下，向第一协议实体发送第一指示信息或第二指示信息，所述第一指示信息用以指示所述第一协议实体丢弃目标数据包，所述第二指示信息用以指示所述第一协议实体保留或不丢弃所述目标数据包；
所述第四条件包括以下至少一项：
到达预设的发送周期；
信道冲突；
剩余数据包延时预算PDB或剩余数据包集合延时预算PSDB超时；
缓存中的数据超出信道容量；
所述目标数据包的需求超出所述第二协议实体的处理容量；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体。
第五方面，提供了一种数据包处理装置，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的数据包处理方法的步骤或第三方面所述的数据包处理方法的步骤。
第六方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第七方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第三方面所述的方法。
第八方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的数据包处理方法，或实现如第三方面所述的数据包处理方法的步骤。
在本申请实施例中，第一协议实体根据第二协议实体的第一指示信息或第二指示信息来进行目标数据包的丢弃，能够优化目标数据包的处理，提高资源利用率，进而提高通信系统容量及节省终端功耗。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例第一协议实体侧数据包处理方法的流程示意图；
图3是本申请实施例第二协议实体侧数据包处理方法的流程示意图；
图4是本申请实施例第一协议实体侧数据包采集装置的结构示意图；
图5是本申请实施例第二协议实体侧数据包采集装置的结构示意图；
图6是本申请实施例通信设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network，RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点或WiFi节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
对于VR业务，上行以较为密集的小数据包传输为主，这些小数据包可承载手势、控制等信息，作为下行呈现数据的输入和参考；下行以视频和音频等多媒体数据传输为主，通过这些多媒体数据的及时接收以及呈现，向用户提供沉浸式的感受。以下行视频数据为例，数据包周期或准周期性到达，数据速率可达几十甚至上百Mbps，帧率(Frame per Second，FPS)的典型值为60或120，相邻数据包之间的间隔大致为1/FPS秒，这些数据在空口一般需要在10ms内成功传输，并且传输成功率要求不低于99％甚至99.9％。
对于AR业务，上行除了上述密集小数据包传输之外，也可能传输视频和音频等多媒体数据，其业务特性和下行类似，通常数据速率相对较低，例如最多几十Mbps，空口传输的时间限也可以放宽，例如一般需要在60ms内成功传输；下行数据传输特性基本与VR业务一致。
用户希望在扩展现实中进行交互和操作，动作和互动包括动作、手势和身体反应。自由度(Degree of Freedom，DoF)描述了用于定义3D空间中视口移动的独立参数的数量。
在扩展现实(Extended Reality，XR)的应用场景中，用户在虚拟现实体验中可以通过转头等动作来获取新视野角度的信息。这时XR用户的转头动作可以通过发送一个上行信号告知基站，基站在接收到上行信号后，会为该XR用户调度所需的下行数据以供使用。
XR业务主要包括视频数据、音频数据以及一些具有控制功能的控制信令和特殊数据。在无线网络中，XR业务传输主要涉及用户设备(User Equipement，UE，也称之为终端)与无线通过新网络(例如LTE/NR等)之间的上行和下行视频/音频数据传输和交互。其中，UE在传输视频、音频数据本身的同时，需要通过无线网络上行传输一些具有控制功能的控制信令和特殊数据，用以对控制网络为UE发送的XR业务中视频和音频业务数据的生成、处理及下行无线传输。
这些具有控制功能的控制信息和特殊数据包括UE XR应用编码器生成的一些业务控制数据及业务传输协议包含的控制数据信息，例如：
从应用层面，可以包括(但不限于)：
视频编码器生成的I帧或即时解码刷新(Instantaneous Decoding Refresh，IDR)帧或non-FOV(Field of view，视场角)帧；
传感器采集的用户行为数据，如pose/control数据等；网络可以通过这些数据的接收，判断用户行为，例如上述的用户转头等动作，进而调整发送的视频数据内容；
从传输协议层面，可以包括：
针对下行音频/视频业务传输的传输控制协议(Transmission Control Protocol，TCP)肯定确认(Acknowledgement，ACK)信令(TCP反馈)，网络需要根据相应视频/音频帧是否已被UE确认，决定是否可以继续发送后续帧；
实时传输控制协议(Real-time Transport Control Protocol，RTCP)ACK信令，用于控制数据实时传输的控制信令，确认业务数据传输的实时性要求及时间同步。
网络通常需要及时、可靠地接收到来自UE的这些具有控制功能的控制信令和特殊数据，用以获取当前业务的传输状态以及相关必要控制信息；应用服务器需要基于这些信息、进一步生成后续所需传输的视频、音频业务数据，并传递给无线网络进行处理和传输，最终将这些业务数据下行发送给UE。
根据XR标准项目的讨论，XR业务属于准周期业务也就是说业务包等间隔到达，且间隔为较小的浮点型数(非正整数)(例如，30FPS(FPS指的是每秒多少帧)→33.33ms，60FPS→16.67ms，120FPS→8.33ms)。此外，XR业务对时延要求很高，空口传输时延预算要求(PDB)在10ms左右。
但由于从服务器短发送至基站端的业务需要存在传输的时延等原因，XR业务包存在一些达到基站侧的时间上的抖动，也就是说在准周期的基础上，每个业务来包时间存在一定范围内的前后偏移，该偏移称作抖动jitter。Jitter的偏移服从截断的高斯分布，范围是在准周期业务包达到的时间位置上前后偏移±4ms。
例如，包准周期达到基站端的时间为n(单位例如ms)，由于存在jitter的影响，包的实际到达时间为n+j，其中j为jitter的大小，例如jitter为-1ms，则表示本应在时间n到达的包的实际到达时间为n-1ms。
为了便于网络侧基于上行待传数据执行上行调度，从LTE开始，引入了缓冲区状态报 告(Buffer Status Report，BSR)上报机制，由UE向基站上报各逻辑信道组对应的上行待传数据量，NR中基本沿用了此机制。
BSR上报的粒度为逻辑信道组(Logical Channel Group，LCG)，每个建立的逻辑信道可以为其配置一个归属的逻辑信道组，NR中支持为单个UE同时配置最多8个逻辑信道组。
BSR基于下列事件来触发：
(1)某个逻辑信道组的某个逻辑信道有新的上行待传数据到来，并且，此逻辑信道的优先级比之前有上行待传数据的逻辑信道的优先级更高，或者，此新数据到达之前所有逻辑信道都没有上行待传数据，此时将触发规律(Regular)BSR；
(2)在组织某个上行新传传输块(Transport Block，TB)时，此新传TB中的Padding比特数大于等于(单个BSR媒介访问控制协议(Medium Access Control，MAC)控制要素(Control Element，CE)+其对应的Subheader)占用的比特数(即此新传TB中的Padding比特还可以容纳单个BSR MAC CE对应的比特)，此时将触发Padding BSR；
(3)retxBSR-Timer定时器超时，并且至少一个逻辑信道存在上行待传数据，此时将触发Regular BSR；
(4)periodicBSR-Timer定时器超时，此时将触发周期Periodic BSR。
当触发了Regular BSR，并且没有用于新传的上行资源时，UE将触发调度请求(Scheduling Request，SR)，通过物理上行控制信道(Physical uplink control channel，PUCCH)传输或随机接入向网络请求上行新传资源。
当触发了Periodic BSR时，UE仅在有上行新传资源时，在构造的上行TB中包含一个BSR MAC CE，但并不会通过触发SR来主动向网络请求上行新传资源。
当触发了Padding BSR时，UE直接在上行新传TB中包含一个BSR MAC CE。
本实施例涉及UE的无线通信AS(Access Statum，接入层)上行数据处理及发送流程。下面对所涉及的主要协议层及相关功能的现有技术描述如下。
(1)分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层和无线承载(radio bearer)：
UE的应用层(Application，APP)生成的业务数据，会按照其对应的服务质量(Quality-of-service，QoS)要求，被归类为不同业务数据流，每个业务数据流对应于同样或相似的的QoS需求。在NR系统中，所述业务数据流对应于一个QoS流(flow)，而在LTE系统中，所述的业务数据流对应于一个演进分组系统(Evolved Packet System，EPS)承载。
业务数据会以数据包(Packet)的形式，传递到AS层，并在AS层根据其所对应的QoS flow(NR)或者EPS承载(LTE)，被进一步映射到一个无线承载(Radio Bearer)中。一个无线承载包括一个PDCP实体(PDCP协议层处理实体)，一个RLC实体(PDCP协议层处理实体)以及相应的逻辑信道(位于MAC协议层)。
当一个传递到接入层(Access-stratum，AS)层的数据包被映射到一个无线承载后，会 以PDCP业务数据单元(service Data Unit，SDU)的形式，传递到相应的PDCP实体进行处理。PDCP实体会为每个到达的PDCP SDU生成一个对应的PDCP协议数据单元(Protocol Data Unit，PDU)，并设置一个PDCP序列号(sequence number，SN)，用于表示PDCP实体中每个PDCP SDU及其相应PDCP PDU对应的传输次序；其中，PDCP SN的取值按照PDCP SDU传递到PDCP实体的顺序设置，先到达的PDCP SDU传输次序在先、后传递的次序在后。具体地，PDCP实体会维护一个内部变量，TX_NEXT，表示PDCP实体传输的PDCP PDU的总数，用于设置PDCP SN的值；PDCP实体建立时将其初始化为0，每次一个PDCP SDU从上层(Upper layers)传递到相应PDCP实体后，PDCP实体会将该PDCP SDU对应的PDCP PDU的SN设置为TX_NEXT，并将TX NEXT加1。之后，PDCP实体会为每个PDCP SDU添加头文件，生成相应的PDCP PDU，其中包含为该PDCP PDU设置的SN值。PDCP Entity通常会按照PDCP PDU所包含的SN的顺序，将PDCP PDU按序传递给下层协议层(RLC)进行后续处理和传输。其中，SN是一个序数，表示每个PDCP SDU是第几个传输的，总体原则就是PDCP SDU到达PDCP实体越早，SN值越小，传输的越早
(2)无线链路层控制协议(Radio Link Control，RLC)层
从PDCP实体传递到相应RLC实体的PDCP PDU，会被当作待传的RLC SDU缓存在UE的缓冲区内，并由RLC实体进行进一步处理。具体地，当某个RLC实体对应的逻辑信道被分配一定的传输资源时，RLC实体将根据所分配传输资源所能容纳的数据量，以及缓冲区内待传输的RLC SDU的数据量，确定哪些RLC SDU可以复用到所分配的传输资源中进行传输。
对于RLC实体确定的、可以完整复用到所分配传输资源的一个或多个RLC SDU，RLC entity会为这些RLC SDU分别添加对应的RLC头文件，并生成对应的RLC PDU，传递给下层协议层(MAC)进行后续的处理和传输。而在复用了上述完整的RLC PDU后，如果仍有一定资源剩余、但不足以再复用一个完整的RLC SDU(即，资源能支持的数据量小于复用下一个RLC SDU所需的数据量)，则RLC实体会进行分段处理，即为下一个待传输的RLC SDU的一部分数据添加头文件，生成RLC PDU并传递给下层协议层进行后续处理和传输。
对于这种被分段的RLC SDU，剩余部分将会仍然被保留在UE的缓冲区，等待下次上行传输资源的到来，再行传输。
(3)媒体介入控制(Medium Access Control，MAC)层和逻辑信道
每个无线承载对应的RLC实体，在MAC层进一步对应于一个逻辑信道(logical channel)。当UE被分配了一个上行传输资源的授权后(Uplink grant)，UE的MAC实体会进一步将本次上行传输的资源，在多个逻辑信道间进行分配。具体地，每个逻辑信道对应于一个逻辑信道优先级，UE的MAC实体基于逻辑信道优先处理(Logical channel prioritization，LCP)的资源分配机制，按照逻辑信道优先级由高到低的顺序为每个逻辑信 道分配本次上行传输可用的传输资源，其对应于每个逻辑信道可以传输的数据量。
如上所述，基于每个逻辑信道所分配到到的传输资源，对应的RLC实体将会将一个或者多个RLC PDU传递给MAC层相应的逻辑信道。MAC层会将每个逻辑信道从RLC实体获得的这些RLC PDU作为待传输的MAC SDU，添加相应逻辑信道对应的MAC头文件，形成对应逻辑信道的MAC subPDU，并将其复用到整个传输资源中，作为这个逻辑信道本次上行传输所发送的数据。多个逻辑信道的MAC subPDU会被组合在一起，最终组成一个MAC PDU，作为本次上行发送的数据包，通过无线信号向网络进行传输。
需要指出的是，由于RLC实体会对RLC SDU进行分段处理(如上所述)，对于每个UE获得的上行传输资源，UE需要首先将在之前传输中被分段、且尚未传输完毕的RLC SDU的剩余部分复用到资源中进行传输，之后才能传输后续的其他RLC SDU对应的数据包。
总的来说，现有LTE和NR网络中，UE针对每个无线承载的数据，通常采用“先到达、先传输”的原则实现上述上行数据处理和传输过程。具体地，针对每个无线承载，UE在上述每个协议层会按照数据包(SDU)传递到本层对应实体的先后顺序处理数据包，并且将处理后的数据包(PDU)按序传递给下一协议层。也就是说，对于先传递到AS层的数据包，相应PDCP实体将会为其设置靠前的PDCP SN值，使其率先获得个上述各协议层的处理，并率先复用到上行资源中进行传输；而后到达的数据包，则会被分配靠后的PDCP SN取值，通常会在在先到达数据包之后被各上述协议层处理、复用及传输。这也意味着，对于映射到每个无线承载上的数据包，UE最终执行的是按照数据包到达AS先后顺序的按序传输机制。
采用这种原则的主要是基于传输时延考虑：由于现有无线网络中，每个无线承载中数据的传输时延要求基本相同，而现有无线网络中不允许UE AS层获取每个数据包具体内容、无法执行针对每个数据包的区分处理；因此，按照数据包到达的顺序来进行数据包的上行处理、调度和传输，从尽量保证时延的角度，是现有技术中较为合理的方式。
对于PDCP层的丢弃定时器，只有数据承载(Data Radio Bearer，DRB)才有丢弃定时器，发送侧对每一个从上层来的SDU都会启动一个新的定时器，超时后丢弃该SDU，用于防止发送缓冲拥塞。此定时器的具体时长是由上层RRC配置。具体地，当接收到上层递送的PDCP SDU时，则发送侧PDCP实体启动与此PDCP SDU相关联的一个丢弃定时器。当此PDCP SDU相关联的丢弃定时器超时，或者此PDCP SDU成功传输时(即由PDCP状态报告确认成功传输)，则发送侧PDCP实体需要丢弃此PDCP SDU以及对应的PDCP数据PDU。如果此PDCP数据PDU已经传递到下层，则需要指示下层丢弃。对于信令承载(Signaling Radio Bearer，SRB)，当上层请求丢弃一个PDCP SDU，则PDCP实体需要丢弃所有存储的PDCP SDU和PDCP PDU。当然：丢弃一个已经与PDCP SN相关联的PDCP SDU，会在传输的PDCP数据PDU中带来一个SN空隙(gap)，这会在接收PDCP实体增加对应的PDCP乱序(re-ordering)延时，这时会基于UE实现来保证在SDU丢弃后如何 最小化SN gap。
在包丢弃(Packet discard/drop)机制中，现有的技术都是PDCP层根据配置的PDCP层的丢弃定时器(DiscardTimer)来确定数据包是否丢弃。但是MAC层的调度可能并不能及时将所有的数据包都调度传输，同时PDCP层可能并不知道MAC层的资源状态，所以在具体的包丢弃处理时，需要MAC层与PDCP层之间的协作。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的数据包处理方法进行详细地说明。
本申请实施例提供一种数据包处理方法，如图2所示，包括：
步骤101：在满足第一条件的情况下，第一协议实体丢弃目标数据包；
所述第一条件包括以下至少一项：
所述第一协议实体接收到所述第二协议实体的第一指示信息；
所述第一协议实体未接收到所述第二协议实体的第二指示信息；
所述第一协议实体在预设时间段内接收到所述第二协议实体的第一指示信息；
所述第一协议实体在预设时间段内未接收到所述第二协议实体的第二指示信息；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体，所述第一协议实体包括以下至少一项：应用层实体，非接入层(Non-access stratum，NAS)实体，PDCP实体，RLC实体，MAC实体，所述第二协议实体包括以下至少一项：RLC实体，MAC实体，物理(Physics，PHY)实体。
在本申请实施例中，第一协议实体根据第二协议实体的第一指示信息或第二指示信息来进行目标数据包的丢弃，能够优化目标数据包的处理，提高资源利用率，进而提高通信系统容量及节省终端功耗。
一些实施例中，所述第一条件还包括：
所述第一协议实体接收到所述第二协议实体的第一指示信息，且满足第二条件，所述第二条件包括以下至少一项：
第一定时器超时；
与所述目标数据包关联的第一数据单元为第一目标类分组内的数据单元或所述第一数据单元为第一目标类分组；
所述第一数据单元属于第一目标类数据包或所述第一数据单元属于第一目标类数据包所在分组；
所述第一数据单元的优先级，或其对应的PDU的优先级，或其对应的SDU的优先级，低于预设第一阈值，比如当数据包，或PDU，或SDU的优先级标识低于一个门限值，其中，不同优先级的数据包可能在一个QoS流中传输，或相同QoS流，但某些数据包比较重要，如：IDR帧；
所述第一数据单元传输成功；
基于第一目标信息确定需要丢弃所述第一数据单元，所述第一目标信息用于指示以下至少一项：
终端是否支持载波聚合(Carrier Aggregation，CA)或双连接(Dual Connectivity，DC)，比如终端不支持载波聚合CA或双连接DC；
为所述终端是否配置了载波聚合CA或双连接DC，比如网络侧设备未为所述终端配置载波聚合CA或双连接DC；
为所述终端是否激活了载波聚合CA或双连接DC，比如所述终端未激活载波聚合CA或双连接DC；
网络侧设备为所述终端配置的资源，或用于传输所述第一数据单元的资源，比如资源不足，网络侧设备为所述终端配置的资源小于等于一个预设门限，或者，用于传输所述第一数据单元的资源小于等于一个预设门限；
所述终端的内存或缓存空间，比如终端的内存或缓存空间不足，层1、层2、层3、无线资源控制缓存大小小于一个预设门限；
所述终端的能力，比如终端的能力不足，一个或多个能力低于预设值；
所述终端的信道质量，或用于传输所述第一数据单元的信道质量，比如信道质量不够好，信道测量性能低于等于一个预设门限，其中的测量性能包括：参考信号接收功率(Reference Singal Receiving Power，RSRP),参考信号接收质量(Reference Signal Receiving Quality，RSRQ),信噪比(Signal to Interference plus Noise Ratio，SINR)等；
所述第一数据单元的大小，或其对应的PDU的大小，或其对应的SDU的大小，或其对应的缓冲区状态报告BSR的大小，或其对应的状态报告SR的大小，比如上述几项中的任一项大于等于一个预设门限；
所述第一数据单元的队列，或所述终端待传输的数据队列，比如所述终端第一目标数据队列的数据包数量大于或等于一个预设门限；所述第一目标数据队列包括：第一数据单元的队列，或待传输的数据队列；
所述第一数据单元的队列，或所述终端待传输的数据队列的大小，比如所述终端第一目标数据队列的数据包总大小大于或等于一个预设门限；所述第一目标数据队列包括：第一数据单元的队列，或待传输的数据队列；
所述终端或所述第一数据单元的延时Latency需求；或所述终端或所述第一数据单元的时延预算要求PDB需求，比如终端或数据包的Latency或PDB或等待时间达到一个预设门限或预设定时器；
第一数据单元的误包率，或其对应的PDU的误包率，或其对应的SDU的误包率，比如数据包，或PDU，或SDU的误包率大于等于一个预设门限，这种情况需要一定反馈机制，可能不仅限于UE侧，比如可以考虑到边链路(Sidelink)等场景；
目标数据包的延时，或其对应的PDU的延时，或其对应的SDU的延时，比如上述几项中的任一项大于等于一个预设门限，或者关联数据单元的时延差大于等于一个预设门限。
一些实施例中，所述方法还包括：
在满足第三条件的情况下，所述第一协议实体保留或不丢弃所述目标数据包；
所述第三条件包括以下至少一项：
所述第一协议实体未接收到所述第二协议实体的第一指示信息；
所述第一协议实体接收到所述第二协议实体的第二指示信息；
所述第一协议实体在预设时间段内未接收到所述第二协议实体的第一指示信息；
所述第一协议实体在预设时间段内接收到所述第二协议实体的第二指示信息；
在本申请实施例中，第一协议实体根据第二协议实体的第一指示信息或第二指示信息来进行目标数据包的保留，能够优化目标数据包的处理，提高资源利用率，进而提高通信系统容量及节省终端功耗。
本实施例中，目标数据包为所述第一指示信息或所述第二指示信息对应的数据包，或者，目标数据包为所述第一指示信息或所述第二指示信息指示的数据包，可以在第一指示信息或第二指示信息中携带目标数据包的数据包标识，以使得第一协议实体确定目标数据包。
一些实施例中，所述第一指示信息指示以下至少一项：
所述目标数据包能够被丢弃，这样第一协议实体可以根据第一指示信息丢弃目标数据包，能够保证传输有效性以及节省系统资源；
所述目标数据包被丢弃，即第二协议实体已经丢弃目标数据包，这样第一协议实体无需保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
在所述目标数据包未成功传输的情况下，所述第二协议实体调度新传，这样第一协议实体无需保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包的延时超出预设延时，这样第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包的调度或传输超出预设延时，这样第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包不能在预设延时内完成传输，表明无法保证目标数据包的延时，第一协议实体可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包成功传输，这里是指目标数据包在发端被成功传输，这样第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以节省系统资源；
所述目标数据包对应的反馈信息，来自对端的反馈信息，包括肯定确认(ACK)或否认确认(Negative Acknowledgement，NACK)，用于反馈目标数据包是否正确传输到目标节点。在目标数据包对应的反馈信息为ACK时，第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以节省系统资源。
一些实施例中，所述第二指示信息指示以下至少一项：
所述目标数据包不能被丢弃，比如即使目标数据包超出预设时间也不能丢弃，这样第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包未被丢弃，比如目标数据包超出预设时间后未被丢弃，这样第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包将被重传或在重传，比如目标数据包超出预设时间，被重传或正在重传，第一协议实体仍需要保留目标数据包，以保证数据包传输的可靠性；
所述目标数据包的延时未超出预设延时，第一协议实体仍需要保留目标数据包，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包的调度或传输未超出预设延时，指不会超出预设延时，包括当前传输调度和未来传输调度，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包能够在预设延时内完成传输，指当前调度传输未超出预设延时，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包未成功传输，第一协议实体仍需要保留目标数据包，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包对应的反馈信息，来自对端的反馈信息，包括ACK或NACK，用于反馈目标数据包是否正确传输到目标节点。在目标数据包对应的反馈信息为NACK时，第一协议实体仍需要保留目标数据包，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性。
一些实施例中，所述预设延时包括以下至少一项：
数据包延时预算(Packet delay budget，PDB)或者数据包集合延时预算(PDU set delay budget，PSDB)；
剩余PDB或剩余PSDB。
一些实施例中，所述剩余PDB或剩余PSDB为第一参数与第二参数之差，所述第一参数包括以下任意一项：
接入网侧数据包延时需求；
接入网PDB或PSDB，即数据包在接入网侧对应的PDB或PSDB；
PDB或PSDB；
数据包延时需求；
所述第二参数包括以下至少一项：
数据包在上层协议实体的缓存的延时；
上层协议实体的PDB或PSDB需求。
其中，PDB或PSDB为终端的延时需求或者终端在预设节点内的延时需求，比如无线接入网PDB或PSDB，或者核心网PDB或PSDB。
一些实施例中，所述目标数据包包括以下至少一项：
PDCP服务数据单元SDU；
PDCP协议数据单元PDU；
PDCP缓存中的数据；
RLC承载对应的数据包，包括：协议数据单元(PDU)、协议数据单元集合(PDU set)、帧(Frame)、突发集(Burst)、切片(Slice)、图片(Picture)、图片组(Group of picture，GOP)、协议数据单元集合组(group of PDU set)、协议数据单元组(group of PDU)等；
MAC SDU对应的数据包，包括：PDU，PDU set，Burst，Frame，Slice，Picture，Group of picture(GOP)，group of PDU set，group of PDU等；
MAC PDU对应的数据包，包括：PDU，PDU set，Burst，Frame，Slice，Picture，Group of picture(GOP)，group of PDU set，group of PDU等。
一些实施例中，所述第一指示信息或所述第二指示信息可以包含在所述第二协议实体向所述第一协议实体发送的层间原语中，这样能够保证第一指示信息和第二指示信息的传输可靠性，层间原语指不同层协议实体之间采用原语通信，包括但不限于：请求(Request)、响应(Response)、确认(Confirm)、指示(Indication)等原语。
本申请实施例提供一种数据包处理方法，如图3所示，包括：
步骤201：在满足第四条件的情况下，第二协议实体向第一协议实体发送第一指示信息或第二指示信息，所述第一指示信息用以指示所述第一协议实体丢弃目标数据包，所述第二指示信息用以指示所述第一协议实体保留或不丢弃所述目标数据包；
所述第四条件包括以下至少一项：
到达预设的发送周期，第二协议实体可以按照预设的发送周期向第一协议实体发送第一指示信息或第二指示信息，预设的发送周期为协议约定或网络侧设备配置的；
信道冲突，第二协议实体可以向第一协议实体发送第一指示信息或第二指示信息，指示丢弃或保留目标数据包；
剩余数据包延时预算PDB或剩余数据包集合延时预算PSDB超时，第二协议实体可以向第一协议实体发送第一指示信息或第二指示信息，指示丢弃或保留目标数据包；
缓存中的数据超出信道容量，第二协议实体可以向第一协议实体发送第一指示信息或第二指示信息，指示丢弃或保留目标数据包；
所述目标数据包的需求超出所述第二协议实体的处理容量(low layer processing capacity)，第二协议实体可以向第一协议实体发送第一指示信息或第二指示信息，指示丢弃或保留目标数据包；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体，所述第一协议实体包括以下至少一项：应用层实体，NAS实体，PDCP实体，RLC实体，MAC实体，所述第二协议实体包括以下至少一项：RLC实体，MAC实体，PHY实体。
在本申请实施例中，第一协议实体根据第二协议实体的第一指示信息或第二指示信息来进行目标数据包的丢弃，能够优化目标数据包的处理，提高资源利用率，进而提高通信系统容量及节省终端功耗。
本实施例中，目标数据包为所述第一指示信息或所述第二指示信息对应的数据包，或者，目标数据包为所述第一指示信息或所述第二指示信息指示的数据包，可以在第一指示信息或第二指示信息中携带目标数据包的数据包标识，以使得第一协议实体确定目标数据包。
一些实施例中，所述第一指示信息指示以下至少一项：
所述目标数据包能够被丢弃，这样第一协议实体可以根据第一指示信息丢弃目标数据包，能够保证传输有效性以及节省系统资源；
所述目标数据包被丢弃，即第二协议实体已经丢弃目标数据包，这样第一协议实体无需保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
在所述目标数据包未成功传输的情况下，所述第二协议实体调度新传，这样第一协议实体无需保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包的延时超出预设延时，这样第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包的调度或传输超出预设延时，这样第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包不能在预设延时内完成传输，表明无法保证目标数据包的延时，第一协议实体可以根据第一指示信息丢弃目标数据包，以保证传输有效性以及节省系统资源；
所述目标数据包成功传输，这里是指目标数据包在发端被成功传输，这样第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以节省系统资源；
所述目标数据包对应的反馈信息，来自对端的反馈信息，包括确认消息(ACK)或否认消息(NACK)，用于反馈目标数据包是否正确传输到目标节点。在目标数据包对应的反馈信息为ACK时，第一协议实体无需再保留目标数据包，可以根据第一指示信息丢弃目标数据包，以节省系统资源。
一些实施例中，所述第二指示信息指示以下至少一项：
所述目标数据包不能被丢弃，比如即使目标数据包超出预设时间也不能丢弃，这样第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包未被丢弃，比如目标数据包超出预设时间后未被丢弃，这样第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包将被重传或在重传，比如目标数据包超出预设时间，被重传或正在重传，第一协议实体仍需要保留目标数据包，以保证数据包传输的可靠性；
所述目标数据包的延时未超出预设延时，第一协议实体仍需要保留目标数据包，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包的调度或传输未超出预设延时，指不会超出预设延时，包括当前传输调度和未来传输调度，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包能够在预设延时内完成传输，指当前调度传输未超出预设延时，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包未成功传输，第一协议实体仍需要保留目标数据包，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性；
所述目标数据包对应的反馈信息，来自对端的反馈信息，包括确认消息(ACK)或否认消息(NACK)，用于反馈目标数据包是否正确传输到目标节点。在目标数据包对应的反馈信息为NACK时，第一协议实体仍需要保留目标数据包，第一协议实体可以根据第二指示信息保留或不丢弃目标数据包，以保证数据包传输的可靠性。
一些实施例中，所述预设延时包括以下至少一项：
数据包延时预算PDB或者数据包集合延时预算PSDB；
剩余PDB或剩余PSDB。
一些实施例中，所述剩余PDB或剩余PSDB为第一参数与第二参数之差，所述第一参数包括以下任意一项：
接入网侧数据包延时需求；
接入网PDB或PSDB；
PDB或PSDB；
数据包延时需求；
所述第二参数包括以下至少一项：
数据包在上层协议实体的缓存的延时；
上层协议实体的PDB或PSDB需求。
其中，PDB或PSDB为终端的延时需求或者终端在预设节点内的延时需求，比如无线接入网PDB或PSDB，或者核心网PDB或PSDB。
一些实施例中，所述目标数据包包括以下至少一项：
PDCP服务数据单元SDU；
PDCP协议数据单元PDU；
PDCP缓存中的数据；
RLC承载对应的数据包，包括：协议数据单元(PDU)、协议数据单元集合(PDU set)、帧(Frame)、突发集(Burst)、切片(Slice)、图片(Picture)、图片组(Group of picture，GOP)、协议数据单元集合组(group of PDU set)、协议数据单元组(group of PDU)等；
MAC SDU对应的数据包，包括：PDU，PDU set，Burst，Frame，Slice，Picture， Group of picture(GOP)，group of PDU set，group of PDU等；
MAC PDU对应的数据包，包括：PDU，PDU set，Burst，Frame，Slice，Picture，Group of picture(GOP)，group of PDU set，group of PDU等。
一些实施例中，所述第一指示信息或所述第二指示信息可以包含在所述第二协议实体向所述第一协议实体发送的层间原语中，这样能够保证第一指示信息和第二指示信息的传输可靠性，层间原语指不同层协议实体之间采用原语通信，包括但不限于：请求(Request)、响应(Response)、确认(Confirm)、指示(Indication)等原语。
本申请实施例提供的数据包处理方法，执行主体可以为数据采集装置。本申请实施例中以数据采集装置执行数据包处理方法为例，说明本申请实施例提供的数据采集装置。
本申请实施例提供一种数据采集装置，如图4所示，应用于第一协议实体300，包括：
第一处理模块310，用于在满足第一条件的情况下，丢弃目标数据包；
所述第一条件包括以下至少一项：
第一协议实体接收到所述第二协议实体的第一指示信息；
所述第一协议实体未接收到所述第二协议实体的第二指示信息；
所述第一协议实体在预设时间段内接收到所述第二协议实体的第一指示信息；
所述第一协议实体在预设时间段内未接收到所述第二协议实体的第二指示信息；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体，所述第一协议实体包括以下至少一项：应用层实体，NAS实体，PDCP实体，RLC实体，MAC实体，所述第二协议实体包括以下至少一项：RLC实体，MAC实体，PHY实体。
在本申请实施例中，第一协议实体根据第二协议实体的第一指示信息或第二指示信息来进行目标数据包的丢弃，能够优化目标数据包的处理，提高资源利用率，进而提高通信系统容量及节省终端功耗。
一些实施例中，所述第一条件还包括：
所述第一协议实体接收到所述第二协议实体的第一指示信息，且满足第二条件，所述第二条件包括以下至少一项：
第一定时器超时；
与所述目标数据包关联的第一数据单元为第一目标类分组内的数据单元或所述第一数据单元为第一目标类分组；
所述第一数据单元属于第一目标类数据包或所述第一数据单元属于第一目标类数据包所在分组；
所述第一数据单元的优先级，或其对应的PDU的优先级，或其对应的SDU的优先级，低于预设第一阈值，比如当数据包，或PDU，或SDU的优先级标识低于一个门限值，其中，不同优先级的数据包可能在一个QoS流中传输，或相同QoS流，但某些数据包比较重要，如：IDR(即时解码刷新)帧；
所述第一数据单元传输成功；
基于第一目标信息确定需要丢弃所述第一数据单元，所述第一目标信息用于指示以下至少一项：
终端是否支持载波聚合CA或双连接DC，比如终端不支持载波聚合CA或双连接DC；
为所述终端是否配置了载波聚合CA或双连接DC，比如网络侧设备未为所述终端配置载波聚合CA或双连接DC；
为所述终端是否激活了载波聚合CA或双连接DC，比如所述终端未激活载波聚合CA或双连接DC；
网络侧设备为所述终端配置的资源，或用于传输所述第一数据单元的资源，比如资源不足，网络侧设备为所述终端配置的资源小于等于一个预设门限，或者，用于传输所述第一数据单元的资源小于等于一个预设门限；
所述终端的内存或缓存空间，比如终端的内存或缓存空间不足，层1、层2、层3、无线资源控制缓存大小小于一个预设门限；
所述终端的能力，比如终端的能力不足，一个或多个能力低于预设值；
所述终端的信道质量，或用于传输所述第一数据单元的信道质量，比如信道质量不够好，信道测量性能低于等于一个预设门限，其中的测量性能包括：RSRP,RSRQ,SINR等；
所述第一数据单元的大小，或其对应的PDU的大小，或其对应的SDU的大小，或其对应的BSR的大小，或其对应的SR的大小，比如上述几项中的任一项大于等于一个预设门限；
所述第一数据单元的队列，或所述终端待传输的数据队列，比如所述终端第一目标数据队列的数据包数量大于或等于一个预设门限；所述第一目标数据队列包括：第一数据单元的队列，或待传输的数据队列；
所述第一数据单元的队列，或所述终端待传输的数据队列的大小，比如所述终端第一目标数据队列的数据包总大小大于或等于一个预设门限；所述第一目标数据队列包括：第一数据单元的队列，或待传输的数据队列；
所述终端或所述第一数据单元的延时Latency需求；或所述终端或所述第一数据单元的PDB需求，比如终端或数据包的Latency或PDB或等待时间达到一个预设门限或预设定时器；
第一数据单元的误包率，或其对应的PDU的误包率，或其对应的SDU的误包率，比如数据包，或PDU，或SDU的误包率大于等于一个预设门限，这种情况需要一定反馈机制，可能不仅限于UE侧，比如可以考虑到Sidelink等场景；
目标数据包的延时，或其对应的PDU的延时，或其对应的SDU的延时，比如上述几项中的任一项大于等于一个预设门限，或者关联数据单元的时延差大于等于一个预设门限。
一些实施例中，第一处理模块310还用于在满足第三条件的情况下，保留或不丢弃所述目标数据包；
所述第三条件包括以下至少一项：
所述第一协议实体未接收到所述第二协议实体的第一指示信息；
所述第一协议实体接收到所述第二协议实体的第二指示信息；
所述第一协议实体在预设时间段内未接收到所述第二协议实体的第一指示信息；
所述第一协议实体在预设时间段内接收到所述第二协议实体的第二指示信息；
一些实施例中，所述第一指示信息指示以下至少一项：
所述目标数据包能够被丢弃；
所述目标数据包被丢弃；
在所述目标数据包未成功传输的情况下，所述第二协议实体调度新传；
所述目标数据包的延时超出预设延时；
所述目标数据包的调度或传输超出预设延时；
所述目标数据包不能在预设延时内完成传输；
所述目标数据包成功传输；
所述目标数据包对应的反馈信息。
一些实施例中，所述第二指示信息指示以下至少一项：
所述目标数据包不能被丢弃；
所述目标数据包未被丢弃；
所述目标数据包将被重传或在重传；
所述目标数据包的延时未超出预设延时；
所述目标数据包的调度或传输未超出预设延时；
所述目标数据包能够在预设延时内完成传输；
所述目标数据包未成功传输；
所述目标数据包对应的反馈信息。
一些实施例中，所述预设延时包括以下至少一项：
数据包延时预算PDB或者数据包集合延时预算PSDB；
剩余PDB或剩余PSDB。
一些实施例中，所述剩余PDB或剩余PSDB为第一参数与第二参数之差，所述第一参数包括以下任意一项：
接入网侧数据包延时需求；
接入网PDB或PSDB；
PDB或PSDB；
数据包延时需求；
所述第二参数包括以下至少一项：
数据包在上层协议实体的缓存的延时；
上层协议实体的PDB或PSDB需求。
一些实施例中，所述目标数据包包括以下至少一项：
PDCP服务数据单元SDU；
PDCP协议数据单元PDU；
PDCP缓存中的数据；
RLC承载对应的数据包；
MAC SDU对应的数据包；
MAC PDU对应的数据包。
一些实施例中，所述第一指示信息或所述第二指示信息包含在所述第二协议实体向所述第一协议实体发送的层间原语中。
本申请实施例提供一种数据包处理装置，如图5所示，应用于第二协议实体400，包括：
第二处理模块410，用于在满足第四条件的情况下，向第一协议实体发送第一指示信息或第二指示信息，所述第一指示信息用以指示所述第一协议实体丢弃目标数据包，所述第二指示信息用以指示所述第一协议实体保留或不丢弃所述目标数据包；
所述第四条件包括以下至少一项：
到达预设的发送周期；
信道冲突；
剩余数据包延时预算PDB或剩余数据包集合延时预算PSDB超时；
缓存中的数据超出信道容量；
所述目标数据包的需求超出所述第二协议实体的处理容量；
其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
所述第二协议实体为所述第一协议实体的底层协议实体，所述第一协议实体包括以下至少一项：应用层实体，NAS实体，PDCP实体，RLC实体，MAC实体，所述第二协议实体包括以下至少一项：RLC实体，MAC实体，PHY实体。
在本申请实施例中，第一协议实体根据第二协议实体的第一指示信息或第二指示信息来进行目标数据包的丢弃，能够优化目标数据包的处理，提高资源利用率，进而提高通信系统容量及节省终端功耗。
一些实施例中，所述第一指示信息指示以下至少一项：
所述目标数据包能够被丢弃；
所述目标数据包被丢弃；
在所述目标数据包未成功传输的情况下，所述第二协议实体调度新传；
所述目标数据包的延时超出预设延时；
所述目标数据包的调度或传输超出预设延时；
所述目标数据包不能在预设延时内完成传输；
所述目标数据包成功传输；
所述目标数据包对应的反馈信息。
一些实施例中，所述第二指示信息指示以下至少一项：
所述目标数据包不能被丢弃；
所述目标数据包未被丢弃；
所述目标数据包将被重传或在重传；
所述目标数据包的延时未超出预设延时；
所述目标数据包的调度或传输未超出预设延时；
所述目标数据包能够在预设延时内完成传输；
所述目标数据包未成功传输；
所述目标数据包对应的反馈信息。
一些实施例中，所述预设延时包括以下至少一项：
数据包延时预算PDB或者数据包集合延时预算PSDB；
剩余PDB或剩余PSDB。
一些实施例中，所述剩余PDB或剩余PSDB为第一参数与第二参数之差，所述第一参数包括以下任意一项：
接入网侧数据包延时需求；
接入网PDB或PSDB；
PDB或PSDB；
数据包延时需求；
所述第二参数包括以下至少一项：
数据包在上层协议实体的缓存的延时；
上层协议实体的PDB或PSDB需求。
一些实施例中，所述目标数据包包括以下至少一项：
PDCP服务数据单元SDU；
PDCP协议数据单元PDU；
PDCP缓存中的数据；
RLC承载对应的数据包；
MAC SDU对应的数据包；
MAC PDU对应的数据包。
一些实施例中，所述第一指示信息或所述第二指示信息包含在所述第二协议实体向所述第一协议实体发送的层间原语中。
本申请实施例中的数据采集装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例 不作具体限定。
本申请实施例提供的数据包处理装置能够实现图2至图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图6所示，本申请实施例还提供一种通信设备600，包括处理器601和存储器602，存储器602上存储有可在所述处理器601上运行的程序或指令，例如，该通信设备600为网络侧设备时，该程序或指令被处理器601执行时实现上述数据包处理方法实施例的各个步骤，且能达到相同的技术效果。该通信设备600为终端时，该程序或指令被处理器601执行时实现上述数据包处理方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述数据包处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述数据包处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述数据包处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡 献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (23)

  1. 一种数据包处理方法，包括：
    在满足第一条件的情况下，第一协议实体丢弃目标数据包；
    所述第一条件包括以下至少一项：
    所述第一协议实体接收到第二协议实体的第一指示信息；
    所述第一协议实体未接收到所述第二协议实体的第二指示信息；
    所述第一协议实体在预设时间段内接收到所述第二协议实体的第一指示信息；
    所述第一协议实体在预设时间段内未接收到所述第二协议实体的第二指示信息；
    其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
    所述第二协议实体为所述第一协议实体的底层协议实体。
  2. 根据权利要求1所述的数据包处理方法，其中，所述第一协议实体包括以下至少一项：应用层实体，非接入层NAS实体，分组数据汇聚协议PDCP实体，无线链路控制RLC实体，媒体介入控制MAC实体，所述第二协议实体包括以下至少一项：RLC实体，MAC实体，物理层PHY实体。
  3. 根据权利要求1所述的数据包处理方法，其中，所述第一条件还包括：
    所述第一协议实体接收到所述第二协议实体的第一指示信息，且满足第二条件，所述第二条件包括以下至少一项：
    第一定时器超时；
    与所述目标数据包关联的第一数据单元为第一目标类分组内的数据单元或所述第一数据单元为第一目标类分组；
    所述第一数据单元属于第一目标类数据包或所述第一数据单元属于第一目标类数据包所在分组；
    所述第一数据单元的优先级，或其对应的PDCP协议数据单元PDU的优先级，或其对应的PDCP服务数据单元SDU的优先级，低于第一阈值；
    所述第一数据单元传输成功；
    基于第一目标信息确定需要丢弃所述第一数据单元。
  4. 根据权利要求3所述的数据包处理方法，其中，所述第一目标信息用于指示以下至少一项：
    终端是否支持载波聚合CA或双连接DC；
    为所述终端是否配置了载波聚合CA或双连接DC；
    为所述终端是否激活了载波聚合CA或双连接DC；
    网络侧设备为所述终端配置的资源，或用于传输所述第一数据单元的资源；
    所述终端的内存或缓存空间；
    所述终端的能力；
    所述终端的信道质量，或用于传输所述第一数据单元的信道质量；
    所述第一数据单元的大小，或其对应的PDU的大小，或其对应的SDU的大小，或其对应的缓冲区状态报告BSR的大小，或其对应的状态报告SR的大小；
    所述第一数据单元的队列，或所述终端待传输的数据队列；
    所述第一数据单元的队列，或所述终端待传输的数据队列的大小；
    所述终端或所述第一数据单元的延时Latency需求；或所述终端或所述第一数据单元的时延预算要求PDB需求；
    第一数据单元的误包率，或其对应的PDU的误包率，或其对应的SDU的误包率；
    目标数据包的延时，或其对应的PDU的延时，或其对应的SDU的延时。
  5. 根据权利要求1所述的数据包处理方法，所述方法还包括：
    在满足第三条件的情况下，所述第一协议实体保留或不丢弃所述目标数据包；
    所述第三条件包括以下至少一项：
    所述第一协议实体未接收到所述第二协议实体的第一指示信息；
    所述第一协议实体接收到所述第二协议实体的第二指示信息；
    所述第一协议实体在预设时间段内未接收到所述第二协议实体的第一指示信息；
    所述第一协议实体在预设时间段内接收到所述第二协议实体的第二指示信息。
  6. 根据权利要求1或5所述的数据包处理方法，其中，所述第一指示信息指示以下至少一项：
    所述目标数据包能够被丢弃；
    所述目标数据包被丢弃；
    在所述目标数据包未成功传输的情况下，所述第二协议实体调度新传；
    所述目标数据包的延时超出预设延时；
    所述目标数据包的调度或传输超出预设延时；
    所述目标数据包不能在预设延时内完成传输；
    所述目标数据包成功传输；
    所述目标数据包对应的反馈信息。
  7. 根据权利要求1或5所述的数据包处理方法，其中，所述第二指示信息指示以下至少一项：
    所述目标数据包不能被丢弃；
    所述目标数据包未被丢弃；
    所述目标数据包将被重传或在重传；
    所述目标数据包的延时未超出预设延时；
    所述目标数据包的调度或传输未超出预设延时；
    所述目标数据包能够在预设延时内完成传输；
    所述目标数据包未成功传输；
    所述目标数据包对应的反馈信息。
  8. 根据权利要求6或7所述的数据包处理方法，其中，所述预设延时包括以下至少一项：
    数据包延时预算PDB或者数据包集合延时预算PSDB；
    剩余PDB或剩余PSDB。
  9. 根据权利要求8所述的数据包处理方法，其中，所述剩余PDB或剩余PSDB为第一参数与第二参数之差，所述第一参数包括以下任意一项：
    接入网侧数据包延时需求；
    接入网PDB或PSDB；
    PDB或PSDB；
    数据包延时需求；
    所述第二参数包括以下至少一项：
    数据包在上层协议实体的缓存的延时；
    上层协议实体的PDB或PSDB需求。
  10. 根据权利要求1-9任一项所述的数据包处理方法，其中，所述目标数据包包括以下至少一项：
    SDU；
    PDU；
    PDCP缓存中的数据；
    RLC承载对应的数据包；
    MAC SDU对应的数据包；
    MAC PDU对应的数据包。
  11. 根据权利要求1所述的数据包处理方法，其中，所述第一指示信息或所述第二指示信息包含在所述第二协议实体向所述第一协议实体发送的层间原语中。
  12. 一种数据包处理方法，包括：
    在满足第四条件的情况下，第二协议实体向第一协议实体发送第一指示信息或第二指示信息，所述第一指示信息用以指示所述第一协议实体丢弃目标数据包，所述第二指示信息用以指示所述第一协议实体保留或不丢弃所述目标数据包；
    所述第四条件包括以下至少一项：
    到达预设的发送周期；
    发生信道冲突；
    剩余数据包延时预算PDB或剩余数据包集合延时预算PSDB超时；
    缓存中的数据超出信道容量；
    所述目标数据包的需求超出所述第二协议实体的处理容量；
    其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
    所述第二协议实体为所述第一协议实体的底层协议实体。
  13. 根据权利要求12所述的数据包处理方法，其中，所述第一协议实体包括以下至少一项：应用层实体，非接入层NAS实体，分组数据汇聚协议PDCP实体，无线链路控制RLC实体，媒体介入控制MAC实体，所述第二协议实体包括以下至少一项：RLC实体，MAC实体，物理层PHY实体。
  14. 根据权利要求12所述的数据包处理方法，其中，所述第一指示信息指示以下至少一项：
    所述目标数据包能够被丢弃；
    所述目标数据包被丢弃；
    在所述目标数据包未成功传输的情况下，所述第二协议实体调度新传；
    所述目标数据包的延时超出预设延时；
    所述目标数据包的调度或传输超出预设延时；
    所述目标数据包不能在预设延时内完成传输；
    所述目标数据包成功传输；
    所述目标数据包对应的反馈信息。
  15. 根据权利要求12所述的数据包处理方法，其中，所述第二指示信息指示以下至少一项：
    所述目标数据包不能被丢弃；
    所述目标数据包未被丢弃；
    所述目标数据包将被重传或在重传；
    所述目标数据包的延时未超出预设延时；
    所述目标数据包的调度或传输未超出预设延时；
    所述目标数据包能够在预设延时内完成传输；
    所述目标数据包未成功传输；
    所述目标数据包对应的反馈信息。
  16. 根据权利要求14或15所述的数据包处理方法，其中，所述预设延时包括以下至少一项：
    数据包延时预算PDB或者数据包集合延时预算PSDB；
    剩余PDB或剩余PSDB。
  17. 根据权利要求16所述的数据包处理方法，其中，所述剩余PDB或剩余PSDB为第一参数与第二参数之差，所述第一参数包括以下任意一项：
    接入网侧数据包延时需求；
    接入网PDB或PSDB；
    PDB或PSDB；
    数据包延时需求；
    所述第二参数包括以下至少一项：
    数据包在上层协议实体的缓存的延时；
    上层协议实体的PDB或PSDB需求。
  18. 根据权利要求12所述的数据包处理方法，其中，所述目标数据包包括以下至少一项：
    PDCP服务数据单元SDU；
    PDCP协议数据单元PDU；
    PDCP缓存中的数据；
    RLC承载对应的数据包；
    MAC SDU对应的数据包；
    MAC PDU对应的数据包。
  19. 根据权利要求12所述的数据包处理方法，其中，所述第一指示信息或所述第二指示信息包含在所述第二协议实体向所述第一协议实体发送的层间原语中。
  20. 一种数据包处理装置，应用于第一协议实体，所述装置包括：
    第一处理模块，用于在满足第一条件的情况下，丢弃目标数据包；
    所述第一条件包括以下至少一项：
    第一协议实体接收到第二协议实体的第一指示信息；
    所述第一协议实体未接收到所述第二协议实体的第二指示信息；
    所述第一协议实体在预设时间段内接收到所述第二协议实体的第一指示信息；
    所述第一协议实体在预设时间段内未接收到所述第二协议实体的第二指示信息；
    其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
    所述第二协议实体为所述第一协议实体的底层协议实体。
  21. 一种数据包处理装置，应用于第二协议实体，所述装置包括：
    第二处理模块，用于在满足第四条件的情况下，向第一协议实体发送第一指示信息或第二指示信息，所述第一指示信息用以指示所述第一协议实体丢弃目标数据包，所述第二指示信息用以指示所述第一协议实体保留或不丢弃所述目标数据包；
    所述第四条件包括以下至少一项：
    到达预设的发送周期；
    信道冲突；
    剩余数据包延时预算PDB或剩余数据包集合延时预算PSDB超时；
    缓存中的数据超出信道容量；
    所述目标数据包的需求超出所述第二协议实体的处理容量；
    其中，所述目标数据包为所述第一指示信息或所述第二指示信息对应的数据包；
    所述第二协议实体为所述第一协议实体的底层协议实体。
  22. 一种数据包处理装置，包括处理器和存储器，所述存储器存储可在所述处理器上运 行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至11任一项所述的数据包处理方法的步骤，或实现如权利要求12至19任一项所述的数据包处理方法的步骤。
  23. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至11任一项所述的数据包处理方法的步骤，或实现如权利要求12至19任一项所述的数据包处理方法的步骤。
PCT/CN2023/136057 2022-12-09 2023-12-04 数据包处理方法及装置 WO2024120328A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211585926.2 2022-12-09
CN202211585926.2A CN118175582A (zh) 2022-12-09 2022-12-09 数据包处理方法及装置

Publications (1)

Publication Number Publication Date
WO2024120328A1 true WO2024120328A1 (zh) 2024-06-13

Family

ID=91349385

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/136057 WO2024120328A1 (zh) 2022-12-09 2023-12-04 数据包处理方法及装置

Country Status (2)

Country Link
CN (1) CN118175582A (zh)
WO (1) WO2024120328A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103167553A (zh) * 2011-12-13 2013-06-19 华为技术有限公司 用于无线通信的方法和装置以及基站
US20150334037A1 (en) * 2013-01-28 2015-11-19 Huawei Technologies Co., Ltd. Method and apparatus for buffering data
WO2018204266A1 (en) * 2017-05-02 2018-11-08 Intel IP Corporation Methods, systems, and apparatus to aggregate retransmissions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103167553A (zh) * 2011-12-13 2013-06-19 华为技术有限公司 用于无线通信的方法和装置以及基站
US20150334037A1 (en) * 2013-01-28 2015-11-19 Huawei Technologies Co., Ltd. Method and apparatus for buffering data
WO2018204266A1 (en) * 2017-05-02 2018-11-08 Intel IP Corporation Methods, systems, and apparatus to aggregate retransmissions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "Issues on packet duplication", 3GPP DRAFT; R2-1801233_ISSUES ON PDCP DUPLICATIONV2, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Vancouver, Canada; 20180122 - 20180126, 12 January 2018 (2018-01-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051386662 *

Also Published As

Publication number Publication date
CN118175582A (zh) 2024-06-11

Similar Documents

Publication Publication Date Title
WO2022213923A1 (zh) 传输处理方法、装置及通信设备
US20240284255A1 (en) Data transmission method and apparatus, and terminal
CN113923712A (zh) 数据处理的方法及装置
WO2023046196A1 (zh) 辅助信息上报方法、业务配置方法、终端及网络侧设备
WO2014198023A1 (zh) 一种调度方法及基站
US20240314626A1 (en) Information reporting method, configuration method, apparatuses, terminal and network side device
WO2023066107A1 (zh) 数据传输方法、装置及终端
WO2024120328A1 (zh) 数据包处理方法及装置
WO2024120322A1 (zh) 数据包处理方法及装置
WO2024131590A1 (zh) 信息传输方法、装置及通信设备
WO2023066108A1 (zh) 数据传输方法、装置及终端
WO2024131591A1 (zh) 信息传输方法、装置及通信设备
WO2024099159A1 (zh) 确定丢包的方法、装置、通信设备及可读存储介质
WO2024099086A1 (zh) 辅助信息发送、接收方法、设备及可读存储介质
CN115550888B (zh) 传输方法、装置、设备及介质
WO2024169550A1 (zh) 一种缓存状态报告确定方法、通信方法及装置
WO2023217009A1 (zh) 数据传输方法、装置及通信设备
WO2023016402A1 (zh) 数据传输方法、装置及终端、网络侧设备
WO2024066419A1 (zh) 业务传输方法及装置
WO2023045838A1 (zh) 信息接收、信息上报方法、装置、设备及计算机存储介质
CN116997018A (zh) 通信方法、终端及网络侧设备
WO2024093725A1 (zh) 数据包的处理方法和通信装置
WO2024007039A2 (en) Methods and apparatus for prioritizing data for transmission
WO2024168212A1 (en) Configured grant enhancement for extended reality and cloud gaming services
WO2024097252A1 (en) Uplink enhancement for extended reality and cloud gaming services

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: 23899906

Country of ref document: EP

Kind code of ref document: A1