WO2024093725A1 - 数据包的处理方法和通信装置 - Google Patents

数据包的处理方法和通信装置 Download PDF

Info

Publication number
WO2024093725A1
WO2024093725A1 PCT/CN2023/126166 CN2023126166W WO2024093725A1 WO 2024093725 A1 WO2024093725 A1 WO 2024093725A1 CN 2023126166 W CN2023126166 W CN 2023126166W WO 2024093725 A1 WO2024093725 A1 WO 2024093725A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
management entity
loss management
duration
packet
Prior art date
Application number
PCT/CN2023/126166
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 WO2024093725A1 publication Critical patent/WO2024093725A1/zh

Links

Classifications

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

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a method for processing a data packet and a communication device.
  • the PDCP layer During the transmission of a data packet, when the packet data convergence protocol (PDCP) layer at the sender receives a service data unit (SDU) from the upper layer, the PDCP layer starts a discard timer for the SDU. When the discard timer expires, the PDCP layer discards the PDCP SDU and PDCP protocol data unit (PDU) corresponding to the data packet. If the PDCP PDU corresponding to the data packet has been delivered to the lower layer, the PDCP layer can instruct the lower layer to discard the PDCP PDU.
  • SDU service data unit
  • the packet loss mechanism in which the discard timer maintained by the PDCP layer for each data packet has the same duration is not suitable for extended reality (XR) service features. For example, some data packets belonging to XR services are not discarded when they exceed the delay budget of XR services, which reduces the system capacity. For another example, jitter may occur when the data packets arrive at the PDCP layer, which may also cause some data packets belonging to XR services to not be discarded in time, reducing the system capacity.
  • XR extended reality
  • the embodiments of the present application provide a method for processing data packets and a communication device, which can enable a packet loss management entity to discard data packets at a reasonable time to improve system capacity.
  • a packet loss management method is provided, which is applied to a packet loss management entity.
  • the method includes: the packet loss management entity receives a first data packet; the packet loss management entity determines the duration of a first discard timer of the first data packet according to the duration of a discard timer of a second data packet and the time interval between the first data packet and the second data packet arriving at the packet loss management entity, the second data packet arrives at the packet loss management entity before the first data packet, and the first data packet and the second data packet belong to a first data packet set.
  • the first data packet and the second data packet are data packets belonging to the same data packet set, and the duration of the discard timer of the first data packet can be adjusted according to the time interval between the first data packet and the second data packet arriving at the packet loss management entity, so as to avoid the first data packet not being discarded in time when the delay budget of the data packet set is exceeded.
  • this scheme enables the packet loss management entity to discard the first data packet at a reasonable time to improve the system capacity.
  • the packet loss management entity determines the duration of the first discard timer according to the difference between the duration of the discard timer of the second data packet and the above time interval.
  • the discard timers of the first data packet and the second data packet can time out at the same time. Therefore, the first data packet and the second data packet can be managed as a whole for packet loss, which better matches the requirements of business integrity transmission and avoids some data packets from continuously occupying the storage resources of the packet loss management entity.
  • the packet loss management entity determines the duration of the first discard timer based on the duration of the discard timer of the second data packet, the above time interval and the duration of the extended timer.
  • the duration of the extended timer can be used to avoid premature discarding of the data packets that arrive at the packet loss management entity later, which affects the integrity transmission of the service corresponding to the data packet.
  • the packet loss management entity determines the duration of the first discard timer to be the first duration, where the first duration is determined based on the duration of the discard timer of the second data packet and the above-mentioned time interval; when the duration of the extended timer is greater than or equal to the first duration, the packet loss management entity determines the duration of the first discard timer to be the duration of the extended timer.
  • the larger value of the first duration and the duration of the extended timer is selected, so that the data packet has sufficient processing time to ensure the transmission performance of the service corresponding to the data packet.
  • the packet loss management entity is a terminal device or a packet data of the terminal device.
  • Convergence protocol PDCP layer the method also includes: the terminal device receives first indication information from the access network device, and the first indication information indicates that the terminal device determines the length of the first discard timer based on the length of the discard timer of the second data packet and the above-mentioned time interval.
  • the access network device can instruct the terminal device to use the method provided by the first aspect to determine the duration of the first discard timer, so that this scheme is compatible with the existing scheme.
  • the packet loss management entity is a terminal device or a packet data convergence protocol PDCP layer of the terminal device, and the method also includes: the terminal device receives second indication information from the access network device, and the second indication information indicates the duration of the extended timer.
  • the packet loss management entity is an access network device or a PDCP layer of the access network device.
  • the method further includes: when the first discard timer times out, the packet loss management entity discards the first data packet.
  • the duration of the extended timer is determined based on a delay budget of the first data packet.
  • the first data packet will not be discarded within the delay budget, and there can be sufficient processing time to ensure the transmission performance of the service corresponding to the first data packet.
  • the second data packet is the first data packet in the first data packet set that arrives at the packet loss management entity, and the duration of the discard timer of the second data packet is determined based on the delay budget of the first data packet set.
  • the second data packet that arrives first in the first data packet set will not be discarded within the delay budget of the first data packet set, thereby avoiding affecting the transmission performance of the service corresponding to the first data packet set.
  • a packet loss management method is provided, which is applied to a packet loss management entity.
  • the method includes: the packet loss management entity receives a first data packet, the first data packet belongs to a first data packet set; the packet loss management entity processes the first data packet according to a discard timer of the first data packet set.
  • the data packet set can be treated as a whole, and packet loss management can be performed on the data packets in the data packet set according to the discard timer of the data packet set to improve the system capacity.
  • the packet loss management entity when the duration of the discard timer of the first data packet set is less than the duration of the first discard timer of the first data packet, the packet loss management entity processes the first data packet according to the discard timer of the first data packet set.
  • the data packets in the data packet set are processed based on the discard timer of the data packet set.
  • the packet loss management entity when a discard timer of the first data packet set times out, discards the first data packet set.
  • the packet loss management entity processes the first data packet according to a discard timer of the first data packet set and a first discard timer of the first data packet.
  • the packet loss management entity when the discard timer of the first data packet set times out and the first discard timer times out, discards the first data packet.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device, and the method also includes: the terminal device receives indication information from the access network device, and the indication information is used to configure a discard timer for the first data packet set.
  • the packet loss management entity is an access network device or a PDCP layer of the access network device.
  • the duration of the discard timer of the first data packet set is determined based on the delay budget of the first data packet set.
  • the first data packet set or some data packets in the first data packet set can be discarded at a reasonable time on the basis of satisfying the delay budget of the service corresponding to the first data packet set, thereby improving the system capacity.
  • a packet loss management method is provided, which is applied to a packet loss management entity.
  • the method includes: the packet loss management entity receives a first data packet; the packet loss management entity determines the duration of a first discard timer of the first data packet according to a first jitter when the first data packet arrives at the packet loss management entity; or
  • the packet loss management entity determines the duration of the discard timer of the first data packet set according to the second jitter when the second data packet arrives at the packet loss management entity, the first data packet belongs to the first data packet set, and the second data packet is the first data packet in the first data packet set that arrives at the packet loss management entity.
  • jitter is taken into account when determining the duration of the discard timer for a data packet or a set of data packets, which is more in line with the actual transmission situation of the data packet or a set of data packets, so that the packet loss management entity can discard the data packet or a set of data packets at a more reasonable time, thereby improving the system capacity.
  • the first jitter is determined based on a time interval between an expected time instant and an actual time instant when the first data packet arrives at the packet loss management entity.
  • the duration of the first discard timer is determined based on the first jitter and a first duration, where the first duration is the duration of the discard timer of a preconfigured first data packet.
  • the duration of the first discard timer can be adjusted according to the jitter during the actual transmission of the first data packet, so as to avoid the first data packet being discarded prematurely when it arrives at the packet loss management entity earlier than the expected time, or to avoid the first data packet not being discarded in time when it arrives at the packet loss management entity later than the expected time.
  • the second jitter is determined based on a time interval between an expected time instant and an actual time instant when the second data packet arrives at the packet loss management entity.
  • the duration of the discard timer for the first data packet set is determined based on the second jitter and the second duration, where the second duration is the preconfigured duration of the discard timer for the first data packet set.
  • the duration of the discard timer of the first data packet set can be adjusted according to the actual transmission situation of the second data packet, so as to avoid the situation where the second data packet arrives at the packet loss management entity earlier than expected, and some data packets in the first data packet set that arrive at the packet loss management entity later are discarded prematurely, or to avoid the situation where the second data packet arrives at the packet loss management entity later than expected, and some data packets in the first data packet set that arrive at the packet loss management entity later cannot be discarded in time.
  • the expected time is determined based on a business cycle.
  • the packet loss management entity determines the length of a first discard timer for the first data packet based on a first jitter when the first data packet arrives at the packet loss management entity, including: the packet loss management entity determines the length of the first discard timer based on the expected transmission completion time of the first data packet and the actual time when the first data packet arrives at the packet loss management entity.
  • the duration of the first discard timer can be adjusted according to the actual arrival time of the first data packet, so that when the actual time when the first data packet arrives at the packet loss management entity is earlier than the expected time, the first data packet can be prevented from being discarded prematurely, affecting the service performance corresponding to the first data packet. Or when the actual time when the first data packet arrives at the packet loss management entity is later than the expected time, the first data packet can be prevented from not being discarded in time, reducing the system capacity.
  • the packet loss management entity determines the length of the discard timer for the first set of data packets based on the second jitter when the second data packet arrives at the packet loss management entity, including: the packet loss management entity determines the length of the discard timer for the first set of data packets based on the expected transmission completion time of the first set of data packets and the actual time when the second data packet arrives at the packet loss management entity.
  • the length of the discard timer of the data packet set can be adjusted according to the actual arrival time of the second data packet, so that when the actual time when the second data packet arrives at the packet loss management entity is earlier than the expected time, it can avoid that some data packets in the first data packet set are discarded prematurely, affecting the service performance corresponding to the first data packet set. Or when the actual time when the second data packet arrives at the packet loss management entity is later than the expected time, it can avoid that some data packets in the first data packet set cannot be discarded in time, reducing the system capacity.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device
  • the method also includes: the terminal device receives indication information from an access network device, the indication information instructing the terminal device to determine the length of a discard timer corresponding to a data packet based on the jitter when the data packet arrives at the packet loss management entity, or the indication information instructs the terminal device to determine the length of a discard timer corresponding to a data packet set based on the jitter when the data packet arrives at the packet loss management entity.
  • the packet loss management entity is an access network device or a PDCP layer of the access network device.
  • the first duration is determined based on a delay budget of the first data packet.
  • the second duration is determined based on a delay budget of the first data packet set.
  • a communication device configured to perform any possible implementation of the first aspect to the third aspect.
  • the device may include a unit and/or module, such as a processing unit and/or a transceiver unit, for executing the method in any possible implementation of the first aspect to the third aspect.
  • the device is a communication device (such as a terminal device, or an access network device) or a PDCP layer in the communication device.
  • the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the device is a chip, chip system or circuit for a communication device (such as a terminal device, or an access network device).
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit;
  • the processing unit may be at least one processor, processing circuit or logic circuit.
  • a communication device comprising: at least one processor, configured to execute a computer program or instruction stored in a memory, so as to execute the method in any possible implementation of the first to third aspects above.
  • the device further comprises a memory, configured to store a computer program or instruction.
  • the device further comprises a communication interface, and the processor reads the computer program or instruction stored in the memory through the communication interface.
  • the apparatus is a communication device (such as a terminal device or an access network device).
  • the apparatus is a PDCP layer of a communication device (such as a terminal device or an access network device).
  • a processor is provided for executing the method in any possible implementation of the first to third aspects above.
  • a computer-readable storage medium which stores a program code executed by a user device, wherein the program code includes a method for executing any possible implementation of the first to third aspects above.
  • a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first to third aspects.
  • FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an access layer and a non-access layer provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of a PSDB and a discard timer provided in an embodiment of the present application.
  • FIG4 is a flow chart of a packet loss management method provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of the discard timer of each data packet in Example #1 provided in an embodiment of the present application.
  • FIG6 is a schematic diagram of the discard timer of each data packet in Example #3 provided in an embodiment of the present application.
  • FIG. 7 is a flow chart of another packet loss management method provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of packet loss management for a data packet set provided in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a packet loss management method provided in an embodiment of the present application.
  • FIG. 10 is a flow chart of another packet loss management method provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a discard timer for a data packet when jitter is considered according to an embodiment of the present application.
  • FIG12 is a schematic diagram of a communication device provided in an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a communication device provided in an embodiment of the present application.
  • FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application.
  • the system 100 shown in FIG1 includes an access network device 10 and a terminal device 20, and the access network device 10 and the terminal device 20 can communicate through uplinks and downlinks.
  • the applicable system of the embodiment of the present application may also include multiple (2 or more) access network devices and multiple terminal devices, and two terminal devices can communicate through a side link.
  • FIG1 is only an example, and the present application does not limit this.
  • the terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • UE user equipment
  • some terminals are exemplified as: virtual reality (VR) devices, augmented reality (AR) devices, terminal devices in the fifth generation (5th generation, 5G) network, or terminal devices in the future evolved public land mobile network (public land mobile network, PLMN), etc., but the embodiments of the present application are not limited to this.
  • VR virtual reality
  • AR augmented reality
  • 5G fifth generation
  • PLMN public land mobile network
  • the terminal device may also be a wearable device.
  • Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
  • the device for realizing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to realize the function, such as a chip system or a chip, which can be installed in the terminal device.
  • the chip system can be composed of a chip, or it can include a chip and other discrete devices.
  • the access network device in the embodiment of the present application can be any communication device with wireless transceiver function for communicating with the terminal device, and can be an access network device deployed on a satellite or an access network device deployed on the ground.
  • the access network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., and can also be 5G, such as gNB in NR system, one or a group of (including multiple antenna panels) antenna panels of a base station in 5G system, or, it can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (
  • the gNB may include a centralized unit (CU) and a DU, where the gNB may or may not adopt a CU-DU split architecture.
  • the gNB may also include an active antenna unit (AAU).
  • AAU active antenna unit
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, for example: satellite communication systems, high altitude platform station (HAPS) communications, non-terrestrial network (NTN) systems such as drones, integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS) and ultra-dense low-orbit satellite communication systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS) and the like.
  • satellite communication systems for example: satellite communication systems, high altitude platform station (HAPS) communications, non-terrestrial network (NTN) systems such as drones, integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS) and ultra-dense low-orbit satellite communication systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS) and the like.
  • HAPS high
  • V2X vehicle-to-everything
  • V2X can include vehicle to network (V2N), vehicle to vehicle (V2V), vehicle to infrastructure (V2I), vehicle to pedestrian (V2P), etc., long-term evolution technology of vehicle communication (LTE-V), Internet of Vehicles, machine type communication (MTC), Internet of Things (IoT), long-term evolution technology of machine-to-machine communication (LTE-M), machine to machine (M2M), etc.
  • V2N vehicle to network
  • V2V vehicle to vehicle
  • V2I vehicle to infrastructure
  • V2P vehicle to pedestrian
  • LTE-V long-term evolution technology of vehicle communication
  • MTC machine type communication
  • IoT Internet of Things
  • LTE-M machine to machine
  • M2M machine to machine
  • the terminal device 20 can communicate with the access network device 10 through the network interface, and the terminal device 20 can also communicate with the core network device through the access network device 10.
  • the interface between the terminal device 20 and the network is divided into an access layer and a non-access layer.
  • FIG. 2 is a schematic diagram of an access layer and a non-access layer provided in an embodiment of the present application.
  • the access layer includes the physical layer (physical layer, PHY), the media access control layer (media access control, MAC), the radio link control layer (radio link control, RLC), the packet data convergence protocol layer (packet data convergence protocol, PDCP) and the radio resource control (radio resource control, RRC) layer.
  • the access layer also includes the service data adaptation protocol layer (service data adaptation protocol, SDAP) layer.
  • SDAP service data adaptation protocol
  • the access layer can be used to control the wireless link between the terminal device and the access network device.
  • the non-access layer can be used to control the signaling interaction between the terminal device and the core network device. For example, the non-access layer controls the signaling process between the terminal device and the access and mobility management function (AMF) network element.
  • AMF mobility management function
  • XR It refers to the combination of reality and virtuality through computers to create a virtual environment for human-computer interaction.
  • XR is a general term for multiple technologies such as virtual reality (VR), augmented reality (AR), and mixed reality (MR).
  • VR virtual reality
  • AR augmented reality
  • MR mixed reality
  • XR services can generate data frames periodically at a certain frame rate.
  • 3GPP 3rd Generation Partnership Project
  • the frame rate is 60 frames per second (fps), that is, 60 video frames are generated per second, and a data frame appears approximately every 16.66 milliseconds (ms).
  • the transmission rate of the data frame can be 20 megabits per second, or megabits per second (Mbps) or 45Mbps, etc.
  • the frame rate can also be 120fps, which is not limited in this application.
  • Jitter There is a certain delay in the encoding of data frames, which causes jitter in the time when the data frames arrive at the air interface. Jitter can be understood as the time interval between the expected time and the actual time when the data frames arrive at the air interface. Jitter can follow a truncated Gaussian distribution, and the truncation range is, for example, [-4, 4] ms.
  • c. Frame size fluctuation The size of a data frame is not fixed and can follow a truncated Gaussian distribution.
  • XR service data packet refers to the data packet belonging to the XR service.
  • XR services can generate data periodically.
  • uplink AR services periodically generate data frames.
  • Data frames can be transmitted by multiple data packets at the access layer.
  • PDU protocol data unit
  • the network has certain requirements for the transmission delay of each PDU set.
  • the transmission delay requirement for the PDU set is the PDU set delay budget (PSDB).
  • PSDB is only an example and this application does not limit it.
  • a PDU set can correspond to one or more data packets.
  • a PDU set contains data corresponding to an application layer information unit.
  • An application layer information unit is the minimum granularity of application layer encoding and decoding, such as a video frame or a video coding strip or a video coding block. If a PDU set corresponds to multiple data packets, the multiple data packets can be transmitted in sequence at the access layer with the data packet as the granularity.
  • a PDU set may consist of one or more PDUs, which are used to carry the payload of an information unit generated at the application level, such as a frame or video slice of an XR service.
  • the application layer requires all PDUs in the PDU set to use the corresponding information unit. In some implementations, when some PDUs are missing, the application layer can restore the corresponding information unit.
  • Service delay budget The upper limit of the transmission delay of a service data from the sender to the receiver.
  • the service delay budget includes the delay budget of the data packet and the delay budget of the data packet set.
  • the delay budget of a data packet takes the uplink transmission of a data packet as an example, and the delay budget of a data packet is the upper limit of the transmission delay of the data packet from the terminal device to the N6 interface of the user plane function (UPF).
  • the delay budget of a data packet set is, for example, the upper limit of the transmission delay of the data packet set from the sender to the receiver.
  • the data packet set is a group of data packets divided according to certain rules, including at least two data packets.
  • the data packet set is a group of data packets including the same upper layer sequence number (SN), or the data packet set is a PDU set, or the data packet set is a group of data packets generated by the application layer in a short period of time, or the data packets in the data packet set belong to the same multimedia data (for example, the same video frame, or the same audio and video).
  • SN upper layer sequence number
  • PDU PDU set
  • the data packet set is a group of data packets generated by the application layer in a short period of time, or the data packets in the data packet set belong to the same multimedia data (for example, the same video frame, or the same audio and video).
  • the PDCP entity on the terminal device side maintains a discard timer (discardTimer) of equal length for each data packet, that is, the survival time of all data packets after arriving at the PDCP layer is the same.
  • the discard timer can be configured by the access network device through the PDCP-Config element in the RRC signaling. If there is jitter when the data packet arrives at the PDCP layer, according to the discard timer maintained by the PDCP entity, if the data packet arrives at the PDCP layer earlier than the expected time, the data packet may be discarded prematurely, affecting the service transmission performance. If the data packet arrives at the PDCP layer later than the expected time, the data packet cannot be discarded in time, reducing the system capacity.
  • FIG3 is a schematic diagram of a PSDB and a discard timer provided in an embodiment of the present application.
  • XR services transmit a PDU set as a whole.
  • the PDU set includes 6 data packets.
  • the PDCP entity maintains a discard timer of equal duration for each data packet. Therefore, for the 6th data packet, the transmission of the PDU set has exceeded the PSDB, but the discard timer of the 6th data packet has not timed out, that is, the PDCP entity did not discard the 6th data packet in time, affecting the system capacity.
  • the data packets in the PDU set have jittered during the transmission process, resulting in the data packets that arrived at the PDCP layer earlier than expected being discarded prematurely, affecting the service transmission performance, and arriving at the PDCP layer later than expected. Data packets cannot be discarded in time, affecting system capacity.
  • an embodiment of the present application provides a method for processing data packets, which can discard data packets at a reasonable time to improve system capacity or performance.
  • FIG4 is a flow chart of a method for processing a data packet provided in an embodiment of the present application.
  • the method 400 shown in FIG4 is applied to a packet loss management entity, and includes the following steps:
  • the packet loss management entity receives data packet #1.
  • the packet loss management entity is an entity used for packet loss management at the access layer, and can discard data packets, such as a PDCP entity. This application does not limit the name of the entity used for packet loss management, and the packet loss management entity in the following text is understood in the same way.
  • the packet loss management entity may be a terminal device or a PDCP layer of the terminal device.
  • the packet loss management entity may be an access network device or a PDCP layer of the access network device.
  • the packet loss management entity determines the length of the discard timer for data packet #1 based on the length of the discard timer for data packet #2 and the time interval between data packet #1 and data packet #2 arriving at the packet loss management entity.
  • Data packet #2 arrives at the packet loss management entity before data packet #1.
  • Data packet #1 and data packet #2 belong to data packet set #1.
  • the packet loss management entity is a PDCP entity
  • the data packet #1 is an SDU from an upper layer (e.g., an SDAP layer or an application layer).
  • Data packet #1 may be the Nth data packet in data packet set #1 that arrives at the PDCP entity, where N is greater than 1.
  • Data packet #2 may be the N-1th data packet in data packet set #1 that arrives at the PDCP entity, and this application does not impose any restrictions on this.
  • the method 400 further includes:
  • the packet loss management entity discards the data packet #1.
  • the following text will refer to the discard timer of data packet #1 as discard timer #1, and the discard timer of data packet #2 as discard timer #2.
  • the packet loss management entity when data packet #1 arrives at the packet loss management entity, the packet loss management entity starts discard timer #1 for data packet #1. When the duration of discard timer #1 exceeds, that is, when discard timer #1 times out, the packet loss management entity discards data packet #1. If data packet #1 has been delivered to a lower layer, the packet loss management entity may instruct the lower layer to discard data packet #1 delivered to the lower layer.
  • the packet loss management entity is the PDCP entity
  • data packet #1 is a PDCP SDU from the upper layer.
  • the PDCP entity starts discard timer #1 for data packet #1.
  • the PDCP entity discards the PDCP SDU and PDCP PDU corresponding to data packet #1. If some PDCP PDUs have been delivered to the lower layer (such as the RLC layer), the PDCP entity instructs the lower layer to discard the PDCP PDU delivered to the lower layer.
  • a data packet is the form in which data is transmitted in a transmission network.
  • a data packet at the Internet protocol (IP) layer may be an IP packet consisting of an IP header and a payload
  • a data packet at the PDCP layer may be a PDCP SDU or a PDCP PDU consisting of a PDCP header and a PDCP SDU.
  • the IP layer delivers an IP packet to the SDAP layer, which becomes an SDAP SDU.
  • the SDAP layer adds a header to the received SDAP SDU and performs quality of service (QoS) mapping to generate an SDAP PDU.
  • QoS quality of service
  • the generated SDAP PDU is delivered to the PDCP layer, where it becomes a PDCP SDU.
  • the PDCP layer adds a PDCP header to the PDCP SDU, compresses the PDCP header and/or PDCP SDU, encrypts the PDCP SDU, and other operations to generate a PDCP PDU.
  • the PDCP PDU is delivered to the RLC layer to become an RLC SDU.
  • the RLC layer can segment the RLC SDU and add the corresponding RLC header to generate one or more RLC PDUs.
  • the RLC PDU is delivered to the MAC layer to become a MAC SDU.
  • the MAC layer can combine multiple MAC SDUs to form a MAC PDU, which is then delivered to the underlying layer, that is, the physical layer, for physical transmission.
  • the duration of discard timer #2 may be configured by the access network device or preset by the terminal device. For example, the terminal device may preset it based on the delay budget of data packet set #1. If the packet loss management entity is an access network device or the PDCP layer of an access network device, and data packet #2 is the first data packet in data packet set #1, then the duration of discard timer #2 may be preset by the access network device. For example, the access network device may preset it based on the delay budget of data packet set #1.
  • data packet set #1 is a PDU set
  • the duration of discard timer #1 may be PSDB.
  • the duration of a discard timer (discardTimer) configured by the access network device for the PDCP entity of the terminal device is equal to PSDB.
  • the duration of discard timer #1 can be determined by the duration of discard timer #2 of data packet #2 (the N-1th data packet in data packet set #1 that arrives at the packet loss management entity), and the time interval between data packet #1 and data packet #2 arriving at the packet loss management entity.
  • the packet loss management entity may determine the duration of discard timer #1 according to the difference between the duration of discard timer #2 and the time interval between data packet #1 and data packet #2 arriving at the packet loss management entity.
  • data packet set #1 includes 6 data packets, which are data packet #a1, data packet #a2, data packet #a3, data packet #a4, data packet #a5 and data packet #a6 in the order of arrival at the PDCP entity.
  • the durations of the discard timers started by the PDCP entity for data packets #a4, #a5 and #a6 when they arrive at the PDCP entity are no longer listed one by one.
  • data packet set #1 is a group of data packets with certain characteristics, or data packet set #1 is a group of data packets divided according to certain rules, including at least two data packets.
  • data packet set #1 is a group of data packets including the same upper layer sequence number (SN), or data packet set #1 is a PDU set, or data packet set #1 is a group of data packets generated by the application layer in a short period of time, or the data packets in data packet set #1 belong to the same multimedia data (for example, the same video frame, or the same audio and video).
  • SN upper layer sequence number
  • data packet set #1 is a PDU set
  • data packet set #1 is a group of data packets generated by the application layer in a short period of time, or the data packets in data packet set #1 belong to the same multimedia data (for example, the same video frame, or the same audio and video).
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device
  • the access network device sends a first indication message to the terminal device, where the first indication message is used to instruct the terminal device to determine the length of the discard timer #1 based on the length of the discard timer #2 of the data packet #2 and the time interval between data packets #1 and #2 arriving at the packet loss management entity.
  • the first indication information can be sent via RRC signaling, for example, the first indication information is a field/bit/enumeration value carried in a data radio bearer (DRB) or a configuration information element of PDCP, and this application does not impose any restrictions on this.
  • DRB data radio bearer
  • PDCP configuration information element
  • the first indication information is a PDUsetDiscard field. If this field is included in the configuration information element of the DRB or PDCP, the terminal device or the PDCP layer of the terminal device determines the length of the discard timer #1 based on the length of the discard timer #2 and the time interval between the arrival of data packet #1 and data packet #2 at the packet loss management entity. If this field is not included in the configuration information element of the DRB or PDCP, the terminal device or the PDCP layer of the terminal device may use a unified discard timer for the data packet.
  • the first indication information is 1-bit information
  • the terminal device or the PDCP layer of the terminal device can use a unified discard timer for the data packet.
  • the terminal device or the PDCP layer of the terminal device determines the length of the discard timer #1 according to the length of the discard timer #2 and the time interval between the arrival of the data packet #1 and the data packet #2 at the packet loss management entity.
  • the first indication information is the enumeration value support. If the enumeration value is included in the configuration information element of the DRB or PDCP, the terminal device or the PDCP layer of the terminal device determines the length of the discard timer #1 based on the length of the discard timer #2 and the time interval between data packet #1 and data packet #2 arriving at the packet loss management entity. If the enumeration value is not included in the configuration information element of the DRB or PDCP, the terminal device or the PDCP layer of the terminal device may use a unified discard timer for data packets.
  • the indication information is the first indication information in the embodiment of the present application.
  • This application does not limit the signaling, information element, and specific form of the first indication information.
  • the packet loss management entity is a terminal device or the PDCP layer of the terminal device, and the access network device sends a first indication message to the terminal device, and correspondingly, the terminal device receives the first indication message.
  • the first indication message is such as PDUsetDiscard, and the first indication message can be sent through RRC signaling, for example, the first indication message is carried in the configuration information element of DRB or PDCP.
  • the access network device can configure a discard timer with a duration of PSDB for the packet loss management entity, that is, the duration of the discard timer of the first data packet arriving at the packet loss management entity in data packet set #1 is configured as PSDB, and PSDB is a QoS parameter, which is the requirement of the QoS flow for the transmission delay.
  • Data packet set #1 can take a PDU set as an example, and the data packets in the PDU set carry the same PDU set SN, for example, the data packets in data packet set #1 all carry SN#m.
  • the terminal device receiving the first indication information may be a packet loss management entity, that is, the packet loss management entity itself is a terminal device.
  • the terminal device receiving the first indication information is a terminal device where the packet loss management entity is located, that is, the packet loss management entity is the PDCP layer of the terminal device.
  • the terminal device receiving the indication information that appears later is understood in the same way and will not be repeated in the following text.
  • FIG5 is a schematic diagram of the discard timer of each data packet in Example #1 provided in an embodiment of the present application.
  • the PDCP entity when the PDCP entity receives a data packet (data packet #a1) from an upper layer, and the data packet is the first data packet carrying SN#m, the PDCP entity starts a discard timer (discard timer #a1) with a duration of PSDB for the data packet; after t1 time, the PDCP entity receives a second data packet (data packet #a2) carrying SN#m, and starts a discard timer for it with a duration of (PSDB-t1).
  • the PDCP entity receives the third data packet carrying SN#m (data packet #a3), and starts a discard timer for it with a duration of (PSDB-t1-t2) (not shown in Figure 5); the same applies to the subsequent data packets carrying SN#m received by the PDCP entity.
  • the discard timer (discard timer #a6) of the sixth data packet carrying SN#m (data packet #a6) in the PDU set times out, the discard timers of all data packets in the PDU set will time out at the same time, that is, when the PSDB is exceeded (or when the PSDB is exhausted), all data packets in the PDU set will be discarded.
  • the method for determining the discard timer of each data packet in the example of Figure 5 is also applicable to the case where the packet loss management entity is an access network device or the PDCP layer of an access network device.
  • the packet loss management entity is an access network device or the PDCP layer of an access network device, and the access network device can preset the duration of the discard timer of the PDCP entity to PSDB, that is, the access network device can preset the duration of the discard timer of the first data packet in the data packet set that arrives at the packet loss management entity to be configured as PSDB.
  • the access network device presets the duration of the discard timer of the first data packet in data packet set #1 that arrives at the packet loss management entity to be the transmission delay budget of data packet set #1.
  • the duration of the discard timer #1 can also be determined based on the duration of the extended timer. That is, the packet loss management entity determines the duration of the discard timer of data packet #1 based on the duration of the discard timer of data packet #2, the time interval between data packet #1 and data packet #2 arriving at the packet loss management entity, and the duration of the extended timer.
  • the duration of the extended timer can be configured by the access network device or preset by the terminal device, for example, the terminal device presets the duration of the extended timer according to the delay budget of the data packet.
  • the duration of the extended timer can be preset by the access network device.
  • the access network device can preset the duration of the extended timer according to the delay budget of the data packet.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device
  • the access network device sends a second indication message to the terminal device.
  • the terminal device receives the second indication message, and the second indication message indicates the duration of the extended timer.
  • a possible implementation manner is that when the duration of the extended timer is less than duration #1, the duration of the discard timer #1 is duration #1; when the duration of the extended timer is greater than or equal to duration #1, the duration of the discard timer #1 is the duration of the extended timer, and duration #1 is determined based on the duration of the discard timer #2 and the time interval between data packets #1 and #2 arriving at the packet loss management entity.
  • duration #1 is determined based on the difference between the duration of discard timer #2 and the time interval between when data packet #1 and data packet #2 arrive at the packet loss management entity.
  • the duration of the discard timer of the Nth data packet that arrives at the packet loss management entity is MAX ⁇ the duration of the discard timer of the N-1th data packet that arrives at the packet loss management entity-the time interval between the Nth data packet and the N-1th data packet that arrive at the packet loss management entity, the duration of the extended timer ⁇ .
  • the method for determining the duration of the discard timer of the first data packet in data packet set #1 that arrives at the packet loss management entity can refer to the method for determining the duration of the discard timer #2 when data packet #2 is the first data packet in data packet set #1 that arrives at the packet loss management entity, and will not be repeated here.
  • Example #3 data packet set #1 is a PDU set, and the data packets in this PDU set carry SN#m.
  • the duration of the extended timer (discardTimerExtend) is equal to PDB, and the duration of the discard timer maintained by the PDCP entity is PSDB.
  • the discard timer maintained by the PDCP entity is the discard timer of the first data packet in data packet set #1 that arrives at the packet loss management entity.
  • FIG6 is a schematic diagram of the discard timer of each data packet in Example #3 provided in an embodiment of the present application.
  • some of the data packets that arrive first in the PDU set will be discarded when the PSDB is exhausted, while some of the data packets that arrive later (for example, the sixth data packet that arrives at the PDCP entity) can continue to survive after the PSDB is exhausted until their own PDB (i.e., the duration of the extended timer) is exhausted and then discarded.
  • the extended timer is considered when determining the duration of discard timer #1. While managing packet loss for packet set #1 as a whole, the arrival delay of some packets in packet set #1 is taken into account. The late arriving data packets are allowed to survive for a period of time after the transmission delay budget of data packet set #1 is exhausted, so that the network can schedule their transmission in time, avoiding the inability to transmit data packet set #1 completely, ensuring the integrity of XR services and improving system capacity and resource utilization efficiency.
  • the packet loss management entity can maintain a variable-length discard timer, that is, the length of the discard timer for each data packet can be adjusted according to the actual transmission situation. For example, for a data packet that arrives later in a data set, if the length of the discard timer of the data packet is not adjusted, the data packet is not discarded in time when the delay budget of the data set is exhausted, affecting the system capacity. Furthermore, for the data packets that arrive later, the length of the extended timer can be combined. Therefore, this solution ensures that the late-arriving data packets have sufficient transmission time while reasonably discarding the data packets, which can ensure the integrity transmission of similar XR services and improve the system capacity.
  • FIG7 is a flow chart of another method for processing a data packet provided in an embodiment of the present application.
  • the method 700 shown in FIG7 is applied to a packet loss management entity, and includes the following steps:
  • the packet loss management entity receives data packet #1, and data packet #1 belongs to data packet set #1.
  • the packet loss management entity may be a terminal device or a PDCP layer of the terminal device.
  • the packet loss management entity may be an access network device or a PDCP layer of the access network device.
  • S720 The packet loss management entity processes data packet #1 according to the discard timer of data packet set #1.
  • the packet loss management entity processes data packet #1 according to discard timer #A.
  • the packet loss management entity processes data packet #1 according to the discard timer #A, including: when the discard timer #A times out, it is considered that the discard timers of all data packets in data packet set #1 have timed out, and the packet loss management entity discards all data packets in data packet set #1.
  • the duration of discard timer #A and/or discard timer #1 can be configured by the access network device (for example, the access network device sends an indication message to the terminal device, and the indication message indicates the duration of discard timer #A and/or discard timer #1), or it can be preset by the terminal device.
  • the terminal device presets the duration of extended timer #1 according to the delay budget of the data packet, and the terminal device presets the duration of extended timer #A according to the delay budget of the data packet set.
  • the duration of discard timer #A and/or discard timer #1 can be preset by the access network device. For example, the access network device presets the duration of extended timer #1 according to the delay budget of the data packet, and the access network device presets the duration of extended timer #A according to the delay budget of the data packet set.
  • the access network device can configure the duration of the discard timer #A for the terminal device or the PDCP layer of the terminal device through RRC signaling.
  • the configuration information element of DRB or PDCP includes indication information A, and the indication information A can be PduSetDiscardTimer.
  • the terminal device or the PDCP layer of the terminal device obtains the indication information A, when the PDCP layer of the terminal device receives the first data packet in data packet set #1 (that is, the first data packet in data packet set #1 that arrives at the PDCP layer), the discard timer #A with a duration of the PduSetDiscardTimer configuration value is started for data packet set #1.
  • the access network device can configure the duration of discard timer #1 for the terminal device or the PDCP layer of the terminal device through RRC signaling.
  • the configuration information element of DRB or PDCP includes indication information B, and the indication information B can be DiscardTimer.
  • the terminal device or the PDCP layer of the terminal device obtains the indication information B, when the PDCP layer of the terminal device receives the Mth data packet in data packet set #1 (that is, the Mth data packet in data packet set #1 that arrives at the PDCP layer), M is greater than or equal to 1, and the discard timer #1 with a duration equal to the configured value of DiscardTimer is started for the Nth data packet.
  • the packet loss management entity when the packet loss management entity receives data packet #1 from the upper layer (such as the SDAP layer or the application layer), if data packet #1 is the first data packet of the received data packet set #1, the discard timer #A is started for the data packet set #1. At the same time, for each data packet received, the packet loss management entity starts a discard timer for the data packet with a duration equal to the duration of the discard timer #1, and the duration of the discard timer #A is less than or equal to the duration of the discard timer #1. When the discard timer #A times out, it is considered that the discard timers of all data packets in the data packet set #1 have timed out. The packet loss management entity discards all data packets in the data packet set #1. If some data packets have been delivered to the lower layer, the packet loss management entity can instruct the lower layer to discard the data packets delivered to the lower layer.
  • the packet loss management entity can instruct the lower layer to discard the data packets delivered to the lower layer.
  • data packet set #1 is PDU set #m
  • the packet loss management entity is the PDCP entity
  • the duration of discard timer #A is PSDB
  • the duration of discard timer #1 is infinity.
  • the PDCP entity receives a data packet from the upper layer, and the data packet is the first data packet carrying SN#m
  • the PDCP entity starts a discard timer #A with a duration of PSDB for the PDU set #m, and also starts a discard timer #1 with a duration of infinity for the data packet.
  • a discard timer with a duration of infinity is started for it.
  • the discard timers of all data packets in PDU set #m are considered to have timed out. As shown in Figure 8, when discard timer #A times out, all data packets in the PDU set are discarded. If some data packets have been delivered to the lower layer, The packet loss management entity may instruct the lower layer to discard the data packet delivered to the lower layer.
  • the packet loss management entity processes data packet #1 according to discard timer #A and discard timer #1.
  • the packet loss management entity processes the data packet #1 according to the discard timer #A and the discard timer #1, including: when the discard timer #A times out and the discard timer #1 times out, the packet loss management entity discards the data packet #1.
  • the packet loss management entity when the packet loss management entity receives data packet #1 from the upper layer, if data packet #1 is the first data packet of the received data packet set #1, the discard timer #A is started for the data packet set #1. At the same time, each time a data packet is received, the packet loss management entity starts a discard timer for the data packet with a duration equal to the duration of the discard timer #1. When the discard timer #A times out and the discard timer #1 also times out, the packet loss management entity discards the data packet #1. If the data packet #1 has been delivered to the lower layer, the packet loss management entity can instruct the lower layer to discard the data packet #1 delivered to the lower layer. It is understandable that when the discard timer #A times out but the discard timer #1 has not timed out, the packet loss management entity does not discard the data packet #1.
  • data packet set #1 is PDU set #m
  • the packet loss management entity is the PDCP entity.
  • the PDCP entity receives a data packet from the upper layer, and the data packet is the first data packet carrying SN#m
  • the PDCP entity starts discard timer #A for the PDU set #m, and simultaneously starts discard timer #1 for the data packet.
  • the duration of discard timer #A is PSDB
  • the duration of discard timer #1 is PDB.
  • a discard timer with a duration of PDB is started for them.
  • the possible arrival delay of the data packets in the data packet set is taken into account.
  • the late arriving data packets they are allowed to continue to survive for a period of time after the discard timer #A times out, so that the network can schedule their transmission in time, avoiding the inability to transmit the data packet set completely, ensuring the integrity of the service, and improving the system capacity and resource utilization efficiency.
  • the packet loss management entity can simultaneously maintain the discard timers of the data packets and the data packet set, so that through the coordination between the discard timer of the data packet and the discard timer of the data packet set, some of the data packets that arrive first in the data packet set can be discarded when the discard timer of the data packet set times out, thereby avoiding resource waste. Furthermore, for some of the data packets that arrive later, they can be discarded when their own discard timer times out in combination with the discard timer of the data packet itself, while reasonably discarding the data packets, ensuring that the data packets that arrive later have sufficient transmission time, ensuring the integrity of similar XR services, and also improving system capacity and resource utilization efficiency.
  • FIG10 is a flow chart of another method for processing a data packet provided in an embodiment of the present application.
  • the method 1000 shown in FIG10 is applied to a packet loss management entity, and includes the following steps:
  • the packet loss management entity receives data packet #1.
  • the packet loss management entity may be a terminal device or a PDCP layer of the terminal device.
  • the packet loss management entity may be an access network device or a PDCP layer of the access network device.
  • the packet loss management entity is a PDCP entity
  • the data packet #1 is a data packet from an upper layer (eg, an SDAP layer or an application layer).
  • the packet loss management entity determines the duration of the discard timer #1 of the data packet #1 according to the first jitter when the data packet #1 arrives at the packet loss management entity.
  • the method 1000 further includes:
  • the packet loss management entity processes data packet #1 according to the discard timer #1.
  • the packet loss management entity processes data packet #1 according to the discard timer #1, please refer to the description in method 400, which will not be repeated here.
  • the packet loss management entity determines the duration of the discard timer #1 according to the duration #A and the first jitter, where the duration #A is the preconfigured duration of the discard timer #1 of the data packet #1.
  • the duration of the discard timer #1 is the duration #A plus the first jitter.
  • the first jitter is determined based on the time interval between the expected time and the actual time when the data packet #1 arrives at the packet loss management entity. For example, the first jitter is the difference between the expected time and the actual time when the data packet #1 arrives at the packet loss management entity. A positive first jitter indicates that the data packet #1 arrives at the packet loss management entity earlier than the expected time, and a negative first jitter indicates that the data packet #1 arrives at the packet loss management entity later than the expected time.
  • the expected time when data packet #1 arrives at the packet loss management entity may be determined based on the service cycle. For example, data packet #1 corresponds to an XR service, and the cycle of the XR service may be notified to the packet loss management entity by the application layer.
  • the packet loss management entity may determine the expected time when data packet #1 arrives at the packet loss management entity based on the cycle and the specific time when data packets that arrive before data packet #1 arrive at the packet loss management entity.
  • the duration #A can be configured by the access network device, or can be determined by the terminal device itself according to the delay budget of the service corresponding to data packet #1.
  • the PDCP layer of the device then the duration #A can be determined by the access network device itself through the delay budget of the service corresponding to the data packet #1.
  • the duration #A can be understood as the duration of the discard timer of the data packet maintained by the packet loss management entity, that is, the discard timer that can be used when the data packet arrives at the packet loss management entity without jitter.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device, and the access network device sends indication information #1 to the terminal device.
  • the terminal device receives the indication information #1, and the indication information #1 is used to instruct the terminal device to determine the length of the discard timer corresponding to the data packet according to the jitter when the data packet arrives at the packet loss management entity.
  • the terminal device can determine the length of the discard timer #1 according to the first jitter of the data packet #1.
  • the indication information #1 is discardJitter.
  • duration #A is PDB
  • the expected time when data packet #1 arrives at the packet loss management entity is time T
  • the expected time when data packet #1 arrives at the packet loss management entity can be determined by the packet loss management entity according to the characteristics of the service corresponding to data packet #1. If the packet loss management entity is a terminal device or the PDCP layer of the terminal device, the expected time can also be indicated by the access network device.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device
  • data packet #1 corresponds to an XR service
  • the XR service has a specific frame rate, that is, data packets are generated periodically.
  • the period of generating data packets can be notified to the packet loss management entity by the application layer, and the packet loss management entity can determine the expected time when the data packet arrives at the packet loss management entity based on the period.
  • the access network device can indicate the period to the terminal device.
  • the access network device indicates to the terminal device the expected time when the data packet arrives at the packet loss management entity.
  • the expected time indicated by the access network device to the terminal device can be coordinated universal time (universal time coordinated, UTC), a frame number or a subframe number.
  • the packet loss management entity determines the duration of the discard timer #1 of the data packet #1 according to the first jitter when the data packet #1 arrives at the packet loss management entity, including:
  • the packet loss management entity determines the duration of discard timer #1 based on the expected transmission completion time of data packet #1 and the actual time when data packet #1 arrives at the packet loss management entity. It can be understood that, because there is a time interval between the actual time and the expected time when data packet #1 arrives at the packet loss management entity, that is, there is a first jitter, the packet loss management entity needs to determine the duration based on the expected transmission completion time of data packet #1 and the actual time when data packet #1 arrives at the packet loss management entity.
  • the packet loss management entity determines the duration of discard timer #1 based on the expected transmission completion time of data packet #1 and the actual time when data packet #1 arrives at the packet loss management entity, which can be understood as an example of the packet loss management entity determining the duration of discard timer #1 for data packet #1 based on the first jitter when data packet #1 arrives at the packet loss management entity.
  • the expected transmission completion time of data packet #1 can be determined according to the service corresponding to data packet #1.
  • the duration of discard timer #1 is the time difference between the expected transmission completion time of data packet #1 and the actual time when data packet #1 arrives at the packet loss management entity. Specifically, if data packet #1 is expected to complete transmission before time t2, and the actual time when data packet #1 arrives at the packet loss management entity is time t1, the duration of discard timer #1 is t2-t1.
  • the actual time when data packet #1 arrives at the packet loss management entity may be jittered, that is, there is a deviation from the expected time when data packet #1 arrives at the packet loss management entity. Therefore, by using this implementation to determine the duration of discard timer #1, it is possible to avoid data packet #1 from being discarded prematurely when it arrives at the packet loss management entity earlier than the expected time, or to avoid data packet #1 from not being discarded in time when it arrives at the packet loss management entity later than the expected time.
  • FIG11 is a schematic diagram of a discard timer for data packet #1 when jitter is considered according to an embodiment of the present application.
  • duration #a is the time interval between the expected time when data packet #1 arrives at the packet loss management entity and the expected time when data packet #1 is transmitted. If data packet #1 arrives earlier than the expected time T, that is, the time interval between the actual time when data packet #1 arrives at the packet loss management entity and the expected time is jitter #1, then the duration of discard timer #1 of data packet #1 is duration #a + jitter #1. If data packet #1 arrives later than the expected time, that is, the time interval between the actual time when data packet #1 arrives at the packet loss management entity and the expected time is jitter #2, then the duration of discard timer #1 is duration #a - jitter #2.
  • the expected transmission completion time of data packet #1 can be determined by the packet loss management entity according to the characteristics of the service corresponding to the data packet #1. If the packet loss management entity is a terminal device or the PDCP layer of the terminal device, the expected transmission completion time can be indicated by the access network device.
  • Transmission completion can be understood as the time when data packet #1 is sent from the access layer of the sending device until the receiving device receives data packet #1 from the access layer, that is, the expected transmission completion time can be the expected time when the receiving device receives data packet #1 from the access layer.
  • the packet loss management entity is a terminal device or the PDCP layer of the terminal device.
  • Data packet #1 corresponds to an XR service.
  • the XR service has a specific frame rate, that is, data packets are generated periodically and are expected to be transmitted within a delay budget.
  • the period and delay budget of generating data packets can be notified to the packet loss management entity by the application layer.
  • the packet loss management entity can determine the expected transmission completion time of data packet #1 based on the period and delay budget.
  • the access network device can indicate the period to the terminal device.
  • the packet loss management entity can determine the expected transmission completion time of data packet #1 based on the period and delay budget.
  • the expected time when data packet #1 arrives at the packet loss management entity is determined based on the specific time and period when the data packet #1 arrives at the packet loss management entity, and the expected transmission completion time of data packet #1 is determined in combination with the expected time and the delay budget.
  • the access network device may indicate the expected transmission completion time to the terminal device.
  • the expected transmission completion time indicated by the access network device to the terminal device may be universal time coordinated (UTC), a frame number or a subframe number.
  • method 400 and method 1000 can be used in combination, for example, data packet #1 is a data packet in data packet set #1, when the packet loss management entity receives data packet #1 from the upper layer, if data packet #1 is the first data packet in data packet set #1 to arrive at the packet loss management entity, data packet #1 generates a first jitter when arriving at the packet loss management entity, and data packet #1 arrives earlier than the expected time, then the duration of the discard timer #1 of data packet #1 is duration #A (see the above description) plus the first jitter, if data packet #1 arrives later than the expected time, then the duration of the discard timer #1 is duration #A minus the first jitter.
  • the duration of the discard timer of the subsequently arriving data packet can be determined based on the discard timer #1 and the time interval, for example, if the subsequently arriving data packet is data packet A, then the time interval is the time interval between data packet A and data packet #1 arriving at the packet loss management entity, how to determine the specific discard timer #1 and the time interval can refer to the description of the relevant content in method 400, and will not be repeated.
  • data packet #1 is a data packet in data packet set #1.
  • the packet loss management entity receives data packet #1 from the upper layer
  • data packet #1 if data packet #1 is the first data packet in data packet set #1 to arrive at the packet loss management entity, data packet #1 generates a first jitter when arriving at the packet loss management entity, and data packet #1 arrives earlier than the expected time, then the duration of the discard timer #1 of data packet #1 is duration #a (see the previous description) plus the first jitter.
  • the duration of the discard timer #1 is duration #a minus the first jitter.
  • the duration of the discard timer of the subsequently arriving data packet can be determined based on the discard timer #1 and the time interval.
  • the time interval refers to the description in method 400 and is not repeated here.
  • the duration of discard timer #1 is the time difference between the actual arrival time of data packet set #1 and the expected transmission completion time of data packet set #1.
  • the actual arrival time of data packet set #1 can be understood as the time when the first data packet in data packet set #1 that arrives at the packet loss management entity actually arrives at the packet loss management entity
  • the expected transmission completion time of data packet set #1 can be understood as the time when the last data packet in data packet set #1 is received from the access layer of the receiving device.
  • the duration of the discard timer for the subsequently arriving data packets can also take into account the duration of the extended timer when determining the duration. For specific considerations, please refer to the description in method 400, which will not be repeated here.
  • S1020 describes how the packet loss management entity processes packet #1 according to discard timer #1 when packet #1 is an independent packet. If packet #1 is not an independent packet but a packet in packet set #1, S1020 can be replaced by: the packet loss management entity determines the duration of discard timer #A of packet set #1 according to the second jitter when packet #0 arrives at the packet loss management entity, packet #1 belongs to packet set #1, and packet #0 is the first packet in packet set #1 that arrives at the packet loss management entity.
  • the packet loss management entity determines the duration of the discard timer #A according to the duration #B and the second jitter, and the duration #B is the duration of the discard timer #A of the preconfigured data packet set #1.
  • the duration of the discard timer #A is the duration #B plus the second jitter.
  • the second jitter is determined based on the time interval between the expected time and the actual time when the data packet #0 arrives at the packet loss management entity. For example, the second jitter is the difference between the expected time and the actual time when the data packet #0 arrives at the packet loss management entity. If the second jitter is a positive number, it means that the data packet #0 arrives at the packet loss management entity earlier than the expected time, and if the second jitter is a negative number, it means that the data packet #0 arrives at the packet loss management entity later than the expected time.
  • the expected time when data packet #0 arrives at the packet loss management entity may be determined according to the service cycle.
  • duration #B can be configured by the access network device, or it can be determined by the terminal device itself through the delay budget of the service corresponding to data packet set #1. If the packet loss management entity is an access network device or the PDCP layer of the access network device, duration #B can be determined by the access network device itself through the delay budget of the service corresponding to data packet set #1. Duration #B can be understood as the discard timer of data packet set #1 maintained by the packet loss management entity, that is, the discard timer of data packet set #1 used when data packet #0 arrives at the packet loss management entity without jitter.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device, and the access network device sends indication information #2 to the terminal device.
  • the terminal device receives the indication information #2, and the indication information #2 is used to instruct the terminal device to determine the duration of the discard timer corresponding to the data packet set according to the jitter when the data packets in the data packet set arrive at the packet loss management entity.
  • the terminal device After the terminal device receives the indication information #2, it can determine the duration of the discard timer #A according to the second jitter of the data packet #0.
  • the indication information #2 is discardJitter.
  • the duration #B is PSDB
  • the expected time when data packet #0 arrives at the packet loss management entity is time T
  • the expected time when packet #0 arrives at the packet loss management entity can be determined by the packet loss management entity according to the characteristics of the service corresponding to the packet set #1. If the packet loss management entity is a terminal device or a PDCP layer of the terminal device, the expected time can also be indicated by the access network device. For details, please refer to the method for determining the expected time when packet #1 arrives at the packet loss management entity in the previous text, which will not be repeated here.
  • the packet loss management entity determines the duration of the discard timer #A of the data packet set #1 according to the second jitter when the data packet #0 arrives at the packet loss management entity, including:
  • the packet loss management entity determines the duration of discard timer #A based on the expected transmission completion time of data packet set #1 and the actual time when data packet set #1 arrives at the packet loss management entity. It can be understood that, because there is a time interval between the actual time and the expected time when data packet #0 arrives at the packet loss management entity, that is, there is a second jitter, the packet loss management entity needs to determine the duration based on the expected transmission completion time of data packet set #1 and the actual time when data packet set #1 arrives at the packet loss management entity.
  • the packet loss management entity determines the duration of discard timer #A based on the expected transmission completion time of data packet set #1 and the actual time when data packet set #1 arrives at the packet loss management entity, which can be understood as an example of the packet loss management entity determining the duration of discard timer #A for data packet set #1 based on the second jitter when data packet #0 arrives at the packet loss management entity.
  • the actual moment when data packet set #1 arrives at the packet loss management entity can be understood as the actual moment when data packet #0 arrives at the packet loss management entity
  • the expected transmission completion moment of data packet set #1 can be understood as the moment when the last data packet in the expected data packet set #1 is received from the access layer of the receiving device.
  • the actual time when data packet #0 arrives at the packet loss management entity may be jittered, that is, there is a deviation from the expected time when data packet #0 arrives at the packet loss management entity. Therefore, this embodiment is used to determine the duration of discard timer #A. This can avoid that some data packets in data packet set #1 are discarded prematurely when data packet #0 arrives at the packet loss management entity earlier than the expected time, or avoid that some data packets in data packet set #1 cannot be discarded in time when data packet #0 arrives at the packet loss management entity later than the expected time.
  • the expected transmission completion time of data packet set #1 can be determined according to the service corresponding to data packet set #1.
  • the duration of discard timer #A is the time difference between the expected transmission completion time of data packet set #1 and the actual time when data packet set #1 arrives at the packet loss management entity. Specifically, if data packet set #1 is expected to complete transmission before time T2, and the actual time when data packet set #1 arrives at the packet loss management entity is time T1, the duration of discard timer #A can be determined to be T2-T1.
  • the expected transmission completion time of data packet set #1 can be determined by the packet loss management entity according to the characteristics of the service corresponding to the data packet set #1. If the packet loss management entity is a terminal device or a PDCP layer of the terminal device, the expected transmission completion time can be indicated by the access network device. For details, please refer to the method for determining the expected transmission completion time of data packet #1 in the previous text, which will not be repeated here.
  • the method 1000 further includes:
  • the packet loss management entity processes packet #1 according to the discard timer #A.
  • the packet loss management entity may instruct the lower layer to discard the data packets delivered to the lower layer.
  • the packet loss management entity discards data packet #1. If data packet #1 has been delivered to the lower layer, the packet loss management entity may instruct the lower layer to discard data packet #1 delivered to the lower layer.
  • the discard timer #A when the discard timer #A times out, it is also necessary to determine whether the discard timer of data packet #1 has timed out. If the discard timer of data packet #1 has not timed out, data packet #1 will not be discarded. If the discard timer of data packet #1 has timed out, data packet #1 will be discarded.
  • the packet loss management entity can adjust the length of the discard timer corresponding to the data packet or data packet set according to the actual jitter, or the length of the discard timer corresponding to the data packet or data packet set can be determined based on the transmission time (such as the actual arrival time or the expected transmission completion time) to avoid the data packet being discarded prematurely or not discarded in time, that is, the data packet is discarded at a reasonable time to improve system capacity and resource utilization efficiency.
  • the transmission time such as the actual arrival time or the expected transmission completion time
  • indication can be indicated explicitly and/or implicitly.
  • implicit indication can be based on the location and/or resources used for transmission; explicit indication can be based on one or more parameters, and/or one or more indexes, and/or one or more bit patterns it represents.
  • the methods and operations implemented by the packet loss management entity can also be implemented by components (such as a chip, a chip system, a processor or a circuit) of the packet loss management entity (such as a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device).
  • components such as a chip, a chip system, a processor or a circuit
  • the packet loss management entity such as a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device.
  • At least one item refers to one item or multiple items
  • at least two items and “multiple items” refer to two items or more.
  • At least one of the following items” or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • at least one of a, b, or c can be represented by: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple. If not otherwise specified, the multiple in the present application means 2 or more.
  • each network element such as a transmitting end device or a receiving end device, includes a hardware structure and/or software module corresponding to the execution of each function in order to realize the above functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.
  • the embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.
  • the device 1200 includes a transceiver unit 1210.
  • the transceiver unit 1210 can be used to implement corresponding communication functions.
  • the transceiver unit 1210 can also be called a communication interface or a communication unit.
  • the device 1200 further includes a processing unit 1220.
  • the processing unit 1220 may be used to perform data processing.
  • the device 1200 also includes a storage unit, which can be used to store instructions and/or data.
  • the processing unit 1220 can read the instructions and/or data in the storage unit so that the device implements the actions of the packet loss management entity in the aforementioned method embodiments.
  • the device 1200 may be the packet loss management entity in the aforementioned embodiment (e.g., a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device), or may be a component of the packet loss management entity (e.g., a chip).
  • the device 1200 may implement steps or processes corresponding to those performed by the packet loss management entity in the above method embodiment, wherein the transceiver unit 1210 may be used to perform operations related to transceiving of the packet loss management entity in the above method embodiment, and the processing unit 1220 may be used to perform operations related to processing of the packet loss management entity in the above method embodiment.
  • the device 1200 can implement the steps or processes executed by the packet loss management entity in the method embodiment according to the embodiment of the present application.
  • the device 1200 may include a unit for executing the method executed by the packet loss management entity in the embodiment shown in Figure 4, Figure 7 or Figure 10.
  • the transceiver unit 1210 is used to receive data packet #1; the processing unit 1220 is used to determine the duration of the discard timer #1 of data packet #1 based on the duration of the discard timer of data packet #2 and the time interval between data packet #1 and data packet #2 arriving at the packet loss management entity, data packet #2 arrives at the packet loss management entity before data packet #1, and data packet #1 and data packet #2 belong to data packet set #1.
  • the processing unit 1220 is specifically configured to determine the duration of the discard timer #1 according to the difference between the duration of the discard timer of the data packet #2 and the above time interval.
  • the processing unit 1220 is specifically configured to determine the duration of the discard timer #1 according to the duration of the discard timer of the data packet #2, the above time interval and the duration of the extended timer.
  • the processing unit 1220 determines the duration of the discard timer #1 to be duration #1, where duration #1 is determined based on the duration of the discard timer of data packet #2 and the above-mentioned time interval; when the duration of the extended timer is greater than or equal to duration #1, the processing unit 1220 determines the duration of the discard timer #1 to be the duration of the extended timer.
  • the packet loss management entity is a terminal device or a packet data convergence protocol PDCP layer of the terminal device
  • the transceiver unit 1220 is also used to receive a first indication message from an access network device, wherein the first indication message indicates that the terminal device determines the length of the discard timer #1 based on the length of the discard timer of data packet #2 and the above-mentioned time interval.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device
  • the transceiver unit 1220 is further used to receive second indication information from the access network device, where the second indication information indicates the duration of the extended timer.
  • the packet loss management entity is an access network device or a PDCP layer of the access network device.
  • the packet loss management entity discards the data packet #1.
  • the duration of the extended timer is determined based on a delay budget of data packet #1.
  • data packet #2 is the first data packet in data packet set #1 that arrives at the packet loss management entity, and the duration of the discard timer of data packet #2 is determined based on the delay budget of data packet set #1.
  • the transceiver unit 1210 is used to receive data packet #1, which belongs to data packet set #1; and the processing unit 1220 is used to process data packet #1 according to the discard timer of data packet set #1.
  • the processing unit 1220 is specifically configured to process data packet #1 according to the discard timer of data packet set #1.
  • the processing unit 1220 is configured to discard data packet set #1.
  • the processing unit 1220 is specifically configured to process data packet #1 according to the discard timer of data packet set #1 and the discard timer #1 of data packet #1.
  • the processing unit 1220 is configured to discard data packet #1.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device, and the transceiver unit 1220 is further used to receive indication information from an access network device, where the indication information is used to configure a discard timer for data packet set #1.
  • the packet loss management entity is an access network device or a PDCP layer of the access network device.
  • the duration of the discard timer of data packet set #1 is determined based on the delay budget of data packet set #1.
  • the transceiver unit 1210 is configured to receive data packet #1; the processing unit 1220 is configured to determine the duration of the discard timer #1 of data packet #1 according to the first jitter when data packet #1 arrives at the packet loss management entity. Or the processing unit 1220 is configured to determine the duration of the discard timer of data packet set #1 according to the second jitter when data packet #0 arrives at the packet loss management entity, data packet #1 belongs to data packet set #1, and data packet #0 is the first data packet in data packet set #1 to arrive at the packet loss management entity.
  • the first jitter is determined based on a time interval between an expected time instant and an actual time instant when the data packet #1 arrives at the packet loss management entity.
  • the duration of the discard timer #1 is determined based on the first jitter and the duration #A, where the duration #A is the duration of the discard timer of the preconfigured data packet #1.
  • the second jitter is determined based on a time interval between an expected time point and an actual time point when data packet #0 arrives at the packet loss management entity.
  • the duration of the discard timer of the data packet set #1 is determined based on the second jitter and duration #B, where duration #B is the duration of the preconfigured discard timer of the data packet set #0.
  • the expected time is determined based on a business cycle.
  • the processing unit 1220 is specifically configured to determine the duration of the discard timer #1 according to the expected transmission completion time of the data packet #1 and the actual time when the data packet #1 arrives at the packet loss management entity.
  • the processing unit 1220 is specifically configured to determine the length of the discard timer of the data packet set #1 according to the expected transmission completion time of the data packet set #1 and the actual time when the data packet #0 arrives at the packet loss management entity.
  • the packet loss management entity is a terminal device or a PDCP layer of the terminal device
  • the transceiver unit 1220 is also used to receive indication information from an access network device, wherein the indication information instructs the terminal device to determine the length of a discard timer corresponding to a data packet based on the jitter when the data packet arrives at the packet loss management entity, or the indication information instructs the terminal device to determine the length of a discard timer corresponding to a data packet set based on the jitter when the data packet arrives at the packet loss management entity.
  • the packet loss management entity is an access network device or a PDCP layer of the access network device.
  • duration #A is determined based on a delay budget of data packet #1.
  • duration #B is determined based on the delay budget of data packet set #1.
  • the device 1300 includes a processor 13120, the processor 13120 is coupled to a memory 1320, the memory 1320 is used to store computer programs or instructions and/or data, and the processor 13120 is used to execute the computer programs or instructions stored in the memory 1320, or read the data stored in the memory 1320, so as to execute the methods in the above method embodiments.
  • processor 13120 is one or more.
  • memory 1320 is one or more.
  • the memory 1320 is integrated with the processor 13120 or is separately configured.
  • the device 1300 further includes a transceiver 1330, and the transceiver 1330 is used for receiving and/or sending signals.
  • the processor 13120 is used to control the transceiver 1330 to receive and/or send signals.
  • the device 1300 is used to implement the operations performed by the packet loss management entity (eg, a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device) in the above method embodiments.
  • the packet loss management entity eg, a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device
  • processors mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processors
  • ASIC application-specific integrated circuits
  • FPGA field programmable gate arrays
  • a general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM).
  • a RAM may be used as an external cache.
  • RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous link DRAM
  • DR RAM direct rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.
  • memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
  • An embodiment of the present application also provides a computer-readable storage medium, on which computer instructions are stored for implementing the methods performed by a packet loss management entity (e.g., a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device) in the above-mentioned method embodiments.
  • a packet loss management entity e.g., a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device
  • An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by a packet loss management entity (e.g., a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device) in the above-mentioned method embodiments.
  • a packet loss management entity e.g., a terminal device, a PDCP layer of a terminal device, an access network device, or a PDCP layer of an access network device
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer can be a personal computer, a server, or a network device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from a website, a computer, a server or a data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless
  • the computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more available media.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)).
  • SSD solid state disk
  • the aforementioned available medium includes, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
  • program codes such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供了一种丢包管理方法和通信装置。该方法用于丢包管理实体，包括：丢包管理实体接收数据包#1；根据先于数据包#1到达丢包管理实体的数据包#2的丢弃计时器的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定数据包#1的丢弃计时器的时长。本申请提供的丢包管理方法能够使得丢包管理实体在合理的时间丢弃数据包，以提升系统容量。

Description

数据包的处理方法和通信装置
本申请要求于2022年11月04日提交中国国家知识产权局、申请号为202211379116.1、申请名称为“数据包的处理方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且，更具体地，涉及数据包的处理方法和通信装置。
背景技术
数据包在传输过程中，发送端的分组数据汇聚协议(packet data convergence protocol，PDCP)层接收到来自上层的业务数据单元(service data unit，SDU)时，PDCP层会为该SDU启动丢弃计时器。超过丢弃计时器的时长，PDCP层丢弃数据包对应的PDCP SDU和PDCP协议数据单元(protocol data unit，PDU)。如果该数据包对应的PDCP PDU已经被递交给下层，则PDCP层可以指示下层丢弃该PDCP PDU。
PDCP层为每个数据包维护的丢弃计时器的时长相等的这种丢包机制不适用于扩展现实(extended reality，XR)业务特征，例如属于XR业务的部分数据包在超出XR业务的时延预算时没有被丢弃，降低了系统容量。再例如数据包到达PDCP层可能会出现抖动，也可能导致属于XR业务的部分数据包不能及时被丢弃，降低了系统容量。
发明内容
本申请实施例提供一种数据包的处理方法和通信装置，能够使得丢包管理实体在合理的时间丢弃数据包，以提升系统容量。
第一方面，提供了一种丢包管理方法，应用于丢包管理实体。该方法包括：丢包管理实体接收第一数据包；丢包管理实体根据第二数据包的丢弃计时器的时长，以及第一数据包和第二数据包到达丢包管理实体的时间间隔确定第一数据包的第一丢弃计时器的时长，第二数据包先于第一数据包到达丢包管理实体，第一数据包和第二数据包属于第一数据包集合。
基于上述方案，第一数据包和第二数据包是属于同一数据包集合的数据包，第一数据包的丢弃计时器的时长可以根据第一数据包和第二数据包到达丢包管理实体的时间间隔做调整，避免在超出数据包集合的时延预算时第一数据包没有被及时丢弃。相对于对数据包维护相同时长的丢弃计时器的方案，本方案能够使得丢包管理实体在合理的时间丢弃第一数据包，以提升系统容量。
结合第一方面，在第一方面的某些实现方式中，丢包管理实体根据第二数据包的丢弃计时器的时长与上述时间间隔的差值确定第一丢弃计时器的时长。
基于上述方案，第一数据包和第二数据包的丢弃计时器可以同时超时，因此对于第一数据包和第二数据包可以作为一个整体作丢包管理，更好的匹配业务完整性传输的要求，避免部分数据包持续占用丢包管理实体的存储资源。
结合第一方面，在第一方面的某些实现方式中，丢包管理实体根据第二数据包的丢弃计时器的时长，上述时间间隔以及扩展计时器的时长确定第一丢弃计时器的时长。
基于上述方案，对于数据集合中部分较晚到达丢包管理实体的数据包可以采用扩展计时器的时长，避免较晚到达丢包管理实体的数据包过早丢弃，影响该数据包对应业务的完整性传输。
结合第一方面，在第一方面的某些实现方式中，在扩展计时器的时长小于第一时长的情况下，丢包管理实体确定第一丢弃计时器的时长为第一时长，第一时长基于第二数据包的丢弃计时器的时长，以及上述时间间隔确定；在扩展计时器的时长大于或等于第一时长的情况下，丢包管理实体确定第一丢弃计时器的时长为扩展计时器的时长。
基于上述方案，对于数据包集合中部分较晚到达丢包管理实体的数据包选择第一时长和扩展计时器的时长中的较大值，以期该数据包有足够的处理时间，保障该数据包对应业务的传输性能。
结合第一方面，在第一方面的某些实现方式中，该丢包管理实体为终端设备或终端设备的分组数据 汇聚协议PDCP层，方法还包括：终端设备接收来自接入网设备的第一指示信息，该第一指示信息指示终端设备根据第二数据包的丢弃计时器的时长，以及上述时间间隔确定第一丢弃计时器的时长。
基于上述方案，在丢包管理实体为终端设备或终端设备的PDCP层时，接入网设备可以指示终端设备使用第一方面提供的方法确定第一丢弃计时器的时长，使得本方案与现有方案可以兼容。
结合第一方面，在第一方面的某些实现方式中，该丢包管理实体为终端设备或终端设备的分组数据汇聚协议PDCP层，方法还包括：终端设备接收来自接入网设备的第二指示信息，第二指示信息指示扩展计时器的时长。
结合第一方面，在第一方面的某些实现方式中，该丢包管理实体为接入网设备或接入网设备的PDCP层。
结合第一方面，在第一方面的某些实现方式中，方法还包括：在第一丢弃计时器超时的情况下，丢包管理实体丢弃第一数据包。
结合第一方面，在第一方面的某些实现方式中，扩展计时器的时长基于第一数据包的时延预算确定。
基于上述方案，第一数据包在时延预算内不会被丢弃，可以有足够的处理时间，保障第一数据包对应业务的传输性能。
结合第一方面，在第一方面的某些实现方式中，第二数据包为第一数据包集合中到达丢包管理实体的第一个数据包，第二数据包的丢弃计时器的时长基于第一数据包集合的时延预算确定。
基于上述方案，可以使得第一数据包集合中第一个到达的第二数据包在第一数据包集合的时延预算内不会被丢弃，避免影响第一数据包集合对应业务的传输性能。
第二方面，提供了一种丢包管理方法，应用于丢包管理实体。该方法包括：丢包管理实体接收第一数据包，第一数据包属于第一数据包集合；丢包管理实体根据第一数据包集合的丢弃计时器处理第一数据包。
基于上述方案，可以将数据包集合作为一个整体，根据数据包集合的丢弃计时器对数据包集合内数据包做丢包管理，以提升系统容量。
结合第二方面，在第二方面的某些实现方式中，在第一数据包集合的丢弃计时器的时长小于第一数据包的第一丢弃计时器的时长的情况下，丢包管理实体根据第一数据包集合的丢弃计时器处理第一数据包。
基于上述方案，在数据包集合的丢弃计时器的时长比第一丢弃计时器的时长小的情况下，以数据包集合的丢弃计时器为基准，处理数据包集合中的数据包。
结合第二方面，在第二方面的某些实现方式中，在第一数据包集合的丢弃计时器超时的情况下，丢包管理实体丢弃第一数据包集合。
基于上述方案，以数据包集合的丢弃计时器为基准，在数据包集合的丢弃计时器超时时，可以将数据包集合作为一个整体丢弃，以提升系统容量。
结合第二方面，在第二方面的某些实现方式中，丢包管理实体根据第一数据包集合的丢弃计时器和第一数据包的第一丢弃计时器处理第一数据包。
基于上述方案，对于部分较晚到达丢包管理实体的数据包除了考虑数据包集合的丢弃计时器之外，还需考虑自身的丢弃计时器，从而使得这些较晚到达的数据包有一定的处理和传输时间，保障该部分数据包对应业务的完整性传输。
结合第二方面，在第二方面的某些实现方式中，在第一数据包集合的丢弃计时器超时且第一丢弃计时器超时的情况下，丢包管理实体丢弃第一数据包。
结合第二方面，在第二方面的某些实现方式中，丢包管理实体为终端设备或终端设备的PDCP层，方法还包括：终端设备接收来自接入网设备的指示信息，该指示信息用于配置所述第一数据包集合的丢弃计时器。
结合第二方面，在第二方面的某些实现方式中，丢包管理实体为接入网设备或接入网设备的PDCP层。
结合第二方面，在第二方面的某些实现方式中，第一数据包集合的丢弃计时器的时长基于第一数据包集合的时延预算确定。
基于上述方案，可以在满足第一数据包集合对应业务的时延预算的基础上，在合理的时间丢弃第一数据包集合或者第一数据包集合中的部分数据包，提高系统容量。
第三方面，提供了一种丢包管理方法，应用于丢包管理实体。该方法包括：丢包管理实体接收第一数据包；丢包管理实体根据第一数据包到达丢包管理实体时的第一抖动确定第一数据包的第一丢弃计时器的时长；或
丢包管理实体根据第二数据包到达丢包管理实体时的第二抖动确定第一数据包集合的丢弃计时器的时长，第一数据包属于第一数据包集合，第二数据包为第一数据包集合中到达丢包管理实体的第一个数据包。
基于上述方案，在确定数据包或数据包集合的丢弃计时器的时长时考虑了抖动，更符合数据包或数据包集合的实际传输情况，使得丢包管理实体能够在更合理的时间丢弃数据包或数据包集合，提升系统容量。
结合第三方面，在第三方面的某些实现方式中，第一抖动基于第一数据包到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。
结合第三方面，在第三方面的某些实现方式中，第一丢弃计时器的时长基于第一抖动和第一时长确定，该第一时长为预配置的第一数据包的丢弃计时器的时长。
基于上述方案，第一丢弃计时器的时长可以根据第一数据包的实际传输时的抖动调整，以期避免第一数据包早于预期时刻到达丢包管理实体的情况下被过早丢弃，或者避免第一数据包晚于预期时刻到达丢包管理实体的情况下不能被及时丢弃。
结合第三方面，在第三方面的某些实现方式中，第二抖动基于第二数据包到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。
结合第三方面，在第三方面的某些实现方式中，第一数据包集合的丢弃计时器的时长基于第二抖动和第二时长确定，该第二时长为预配置的第一数据包集合的丢弃计时器的时长。
基于上述方案，第一数据包集合的丢弃计时器的时长可以根据第二数据包的实际传输情况调整，以期避免第二数据包早于预期时刻到达丢包管理实体的情况下，第一数据包集合中部分较晚到达丢包管理实体的数据包被过早丢弃，或者避免第二数据包晚于预期时刻到达丢包管理实体的情况下，第一数据包集合中部分较晚到达丢包管理实体的数据包不能被及时丢弃。
结合第三方面，在第三方面的某些实现方式中，上述预期时刻基于业务周期确定。
结合第三方面，在第三方面的某些实现方式中，丢包管理实体根据第一数据包到达丢包管理实体时的第一抖动确定第一数据包的第一丢弃计时器的时长，包括：丢包管理实体根据第一数据包的预期传输完成时刻和第一数据包到达丢包管理实体的实际时刻确定第一丢弃计时器的时长。
基于上述方案，第一丢弃计时器的时长可以根据第一数据包实际到达时刻调整，使得第一数据包到达丢包管理实体的实际时刻早于预期时刻时可以避免第一数据包被过早丢弃，影响第一数据包对应的业务性能。或者使得第一数据包到达丢包管理实体的实际时刻晚于预期时刻时可以避免第一数据包不能被及时丢弃，降低系统容量。
结合第三方面，在第三方面的某些实现方式中，丢包管理实体根据第二数据包到达丢包管理实体时的第二抖动确定第一数据包集合的丢弃计时器的时长，包括：丢包管理实体根据第一数据包集合的预期传输完成时刻和第二数据包到达丢包管理实体的实际时刻确定第一数据包集合的丢弃计时器的时长。
基于上述方案，数据包集合的丢弃计时器的时长可以根据第二数据包实际到达时刻调整，使得第二数据包到达丢包管理实体的实际时刻早于预期时刻时可以避免第一数据包集合中的部分数据包被过早丢弃，影响第一数据包集合对应的业务性能。或者使得第二数据包到达丢包管理实体的实际时刻晚于预期时刻时可以避免第一数据包集合中的部分数据包不能被及时丢弃，降低系统容量。
结合第三方面，在第三方面的某些实现方式中，丢包管理实体为终端设备或终端设备的PDCP层，方法还包括：终端设备接收来自接入网设备的指示信息，该指示信息指示终端设备根据数据包到达丢包管理实体时的抖动确定数据包对应丢弃计时器的时长，或者所述指示信息指示终端设备根据数据包集合中数据包到达丢包管理实体时的抖动确定数据包集合对应丢弃计时器的时长。
结合第三方面，在第三方面的某些实现方式中，丢包管理实体为接入网设备或接入网设备的PDCP层。
结合第三方面，在第三方面的某些实现方式中，第一时长基于第一数据包的时延预算确定。
结合第三方面，在第三方面的某些实现方式中，第二时长基于第一数据包集合的时延预算确定。
第四方面，提供一种通信装置，该装置用于执行上述第一方面至第三方面任一种可能实现方式中的 方法。具体地，该装置可以包括用于执行第一方面至第三方面任一种可能实现方式中的方法的单元和/或模块，如处理单元和/或收发单元。
在一种实现方式中，该装置为通信设备(如终端设备，又如接入网设备)或通信设备中的PDCP层。当该装置为通信设备或通信设备中的PDCP层时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于通信设备(如终端设备，又如接入网设备)的芯片、芯片系统或电路。当该装置为用于通信设备的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第五方面，提供一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面至第三方面任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为通信设备(如终端设备，又如接入网设备)。
在另一种实现方式中，该装置为通信设备(如终端设备，又如接入网设备)的PDCP层。
第六方面，提供一种处理器，用于执行上述第一方面至第三方面任一种可能实现方式中的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第七方面，提供一种计算机可读存储介质，该计算机可读介质存储用户设备执行的程序代码，该程序代码包括用于执行上述第一方面至第三方面任一种可能实现方式中的方法。
第八方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第三方面任一种可能实现方式中的方法。
附图说明
图1是本申请实施例提供的一种网络架构的示意图。
图2是本申请实施例提供的接入层和非接入层的示意图。
图3是本申请实施例提供的PSDB和丢弃计时器的示意图。
图4是本申请实施例提供的一种丢包管理方法的流程示意图。
图5是本申请实施例提供的示例#1中各数据包的丢弃计时器的示意图。
图6是本申请实施例提供的示例#3中各数据包的丢弃计时器的示意图。
图7是本申请实施例提供的另一种丢包管理方法的流程示意图。
图8是本申请实施例提供的一种针对数据包集合丢包管理的示意图。
图9是本申请实施例提供的一种针对数据包丢包管理的示意图。
图10是本申请实施例提供的又一种丢包管理方法的流程示意图。
图11是本申请实施例提供的考虑抖动时数据包的丢弃计时器的示意图。
图12是本申请实施例提供的一种通信装置的示意图。
图13是本申请实施例提供的一种通信装置的示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
图1是本申请实施例提供的一种网络架构的示意图。
图1示出的系统100包括接入网设备10和终端设备20，接入网设备10和终端设备20之间可以通过上下行链路通信。当然，本申请实施例适用系统还可包括多个(2个及2个以上)接入网设备以及多个终端设备，两个终端设备之间可以通过侧行链路进行通信，图1仅为示例，本申请对此不做限制。
本申请实施例中的终端设备也可以称为用户设备(user equipment，UE)、接入终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
作为示例，一些终端的举例为：虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备，第五代(5th generation，5G)网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
本申请实施例中的接入网设备可以是用于与终端设备通信的任意一种具有无线收发功能的通信设备，可以是部署在卫星上的接入网设备，也可以是部署在地面上的接入网设备。该接入网设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseband unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如NR系统中的gNB，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU，其中gNB可以采用CU-DU分离架构，也可以不采用CU-DU分离架构。gNB还可以包括有源天线单元(active antenna unit，AAU)。
本申请实施例的技术方案可以应用于各种通信系统，例如：卫星通信系统、高空平台(high altitude platform station,HAPS)通信、无人机等非地面网络(non-terrestrial network,NTN)系统，通信、导航一体化(integrated communication and navigation,ICAN)系统、全球导航卫星系统(global navigation satellite system,GNSS)和超密低轨卫星通信系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、5G系统或5G之后演进的通信系统，车辆外联(vehicle-to-everything，V2X)，其中V2X可以包括车到互联网(vehicle to network，V2N)、车到车(vehicle to vehicle，V2V)、车到基础设施(vehicle to infrastructure，V2I)、车到行人(vehicle to pedestrian，V2P)等、车间通信长期演进技术(long term evolution-vehicle，LTE-V)、车联网、机器类通信(machine type communication，MTC)、物联网(Internet of things，IoT)、机器间通信长期演进技术(long term evolution-machine，LTE-M)，机器到机器(machine to machine，M2M)等。
终端设备20可以通过网络接口与接入网设备10通信，终端设备20也可以通过接入网设备10与核心网设备通信。终端设备20与网络之间的接口分为接入层和非接入层。
图2是本申请实施例提供的接入层和非接入层的示意图。
例如，图2所示的LTE系统中，接入层包括物理层(physical layer，PHY)、媒体接入控制层(media access control，MAC)、无线链路控制层(radio link control，RLC)、分组数据汇聚协议层(packet data convergence protocol，PDCP)和无线资源控制(radio resource control，RRC)层，图2所示的5G系统中，接入层除了上述层之外，还包括业务数据适配协议层(service data adaptation protocol，SDAP)层。接入层可用于控制终端设备与接入网设备之间的无线链路。非接入层可用于控制终端设备和核心网设备之间的信令交互，例如非接入层控制终端设备与接入和移动性管理(access and mobility management function，AMF)网元之间的信令流程。
为便于理解本申请实施例，对本申请中涉及到的术语做简单说明。
1、XR：是指通过计算机将真实与虚拟相结合，打造一个人机交互的虚拟环境。XR是虚拟现实(virtual reality，VR)、增强现实(augmented reality，AR)、混合显示(mixed reality，MR)等多种技术的统称。通过将上述多种技术相融合，可以为体验者带来虚拟世界与现实世界之间无缝转换的“沉浸感”。
第三代合作伙伴项目(the 3rd generation partnership project，3GPP)Rel-17对XR的业务特征进行了建模分析，XR业务可以按照一定的帧率周期性生成数据帧。例如对于上行AR业务，包括如下业务特征：
a、帧率：例如帧率为60帧每秒(frames per second，fps)，即每秒生成60帧视频图像，约每16.66毫秒(millisecond，ms)出现一个数据帧，数据帧的传输速率可以为20兆比特每秒，或兆位每秒(megabits per second，Mbps)或45Mbps等。帧率也可以是120fps，本申请对此不做限制。
b、抖动(jitter)：数据帧的编码存在一定的时延，导致数据帧到达空口侧的时间出现抖动，抖动可以理解为数据帧到达空口侧的预期时刻和实际时刻之间的时间间隔。抖动可以服从截断高斯分布，截断的范围例如为[-4，4]ms。
c、帧大小波动：数据帧的大小并非是固定不变的，可以服从截断高斯分布。数据帧的大小的均值可以表示为mean＝R×1e6/F/8，其中F为帧率，R为数据流的速率；以F＝60fps，R＝20Mbps为例，mean＝41.67KBytes；通常数据帧的大小在0.5*mean到1.5*mean之间。
2、XR业务数据包：指属于XR业务的数据包。XR业务可以周期性生成数据，例如上行AR业务周期性的生成数据帧，数据帧在接入层可以由多个数据包进行传输，这些数据包可以组成一个或多个协议数据单元(protocol data unit，PDU)集合(set)。通常网络会对每个PDU集合的传输时延有一定要求，例如对PDU集合的传输时延要求为PDU集合时延预算(PDU set delay budget，PSDB)，PSDB仅为举例，本申请对此不做限制。
可以理解，一个PDU集合可以对应一个或多个数据包。一个PDU集合包含了一个应用层信息单元对应的数据，一个应用层信息单元是应用层编解码的最小粒度，例如一个视频帧或一个视频编码条带或一个视频编码区块。若一个PDU集合对应多个数据包时，该多个数据包可以按顺序以数据包为粒度在接入层进行传输。
示例地，PDU集合可以由一个或多个PDU组成，该一个或多个PDU用于承载在应用程序级别生成的一个信息单元的有效载荷，应用程序级别的信息单元例如XR业务的帧或者视频切片。一些实现方式中，应用层需要PDU集合中的所有PDU才能使用对应的信息单元。一些实现方式中，当缺少部分PDU时，应用层可以恢复对应的信息单元。
3、业务的时延预算：某业务的数据从发送端到接收端的传输时延的上限。业务的时延预算包括数据包的时延预算和数据包集合的时延预算。
示例地，数据包的时延预算以数据包的上行传输为例，数据包的时延预算为数据包从终端设备到达用户平面功能(user plane function，UPF)的N6接口的传输时延的上限。数据包集合的时延预算例如数据包集合从发送端到接收端的传输时延的上限。
其中，数据包集合为按照一定规则划分的一组数据包，包括至少两个数据包。例如，数据包集合为包括相同的上层序列号(sequence number，SN)的一组数据包，或者数据包集合为一个PDU集合，或者数据包集合为应用层在短时间内产生的一组数据包，或者数据包集合中的数据包属于同一段多媒体数据(例如同属于一个视频帧，或同属于一段音视频)。
以终端设备的上行传输为例，终端设备侧的PDCP实体为每个数据包维护相等时长的丢弃计时器(discardTimer)，即所有数据包到达PDCP层后的存活时间都是一样的。该丢弃计时器可以由接入网设备通过RRC信令中的PDCP-Config信元配置。如果数据包到达PDCP层时有抖动，则按照PDCP实体维护的丢弃计时器，数据包早于预期时刻到达PDCP层，则可能过早丢弃该数据包，影响业务传输性能，数据包晚于预期时刻到达PDCP层，则不能及时丢弃该数据包，降低了系统容量。
图3是本申请实施例提供的PSDB和丢弃计时器的示意图。
以终端设备对XR业务的上行传输为例，XR业务将一个PDU集合作为整体进行传输，如图3所示，PDU集合包括6个数据包，PDCP实体为每个数据包维护相等时长的丢弃计时器，因此对于第6个数据包而言，PDU集合的传输已经超出PSDB的情况下，第6个数据包的丢弃计时器还没有超时，即PDCP实体没有及时丢弃第6个数据包，影响系统容量。或者PDU集合中的数据包在传输的过程中产生了抖动，导致早于预期时刻到达PDCP层的数据包过早被丢弃，影响业务传输性能，晚于预期时刻到达PDCP层 的数据包不能及时被丢弃，影响系统容量。
鉴于此，本申请实施例提供一种数据包的处理方法，能够在合理的时间丢弃数据包，以提升系统容量或性能。
图4是本申请实施例提供的一种数据包的处理方法的流程示意图。图4所示的方法400应用于丢包管理实体，包括以下步骤：
S410，丢包管理实体接收数据包#1。
丢包管理实体是接入层用于丢包管理的实体，可以丢弃数据包。例如PDCP实体，本申请对用于丢包管理的实体的名称不做限制，后文的丢包管理实体同此理解。
在上行传输中，丢包管理实体可以为终端设备或终端设备的PDCP层，在下行传输中，丢包管理实体可以为接入网设备或接入网设备的PDCP层。
S420，丢包管理实体根据数据包#2的丢弃计时器的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定数据包#1的丢弃计时器的时长，数据包#2先于数据包#1到达丢包管理实体，数据包#1和数据包#2属于数据包集合#1。
示例地，丢包管理实体为PDCP实体，该数据包#1为来自上层(例如SDAP层或应用层)的SDU，数据包#1可以是数据包集合#1中到达PDCP实体的第N个数据包，N大于1，数据包#2可以是数据包集合#1中到达PDCP实体的第N-1个数据包，本申请对此不做限制。
可选地，方法400还包括：
在数据包#1的丢弃计时器超时的情况下，丢包管理实体丢弃该数据包#1。
后文为简洁，将数据包#1的丢弃计时器记为丢弃计时器#1，将数据包#2的丢弃计时器记为丢弃计时器#2。
一种可能的实施方式，数据包#1到达丢包管理实体时，丢包管理实体为数据包#1开启丢弃计时器#1，当超过丢弃计时器#1的时长，也就是说丢弃计时器#1超时时，丢包管理实体将数据包#1丢弃，如果数据包#1已经被递交到下层，则丢包管理实体可以指示下层，将被递交到下层的数据包#1丢弃。
示例地，丢包管理实体为PDCP实体，数据包#1为来自上层的PDCP SDU，数据包#1到达PDCP实体时，PDCP实体为数据包#1开启丢弃计时器#1，当丢弃计时器#1超时时，PDCP实体将数据包#1对应的PDCP SDU和PDCP PDU丢弃，如果有部分PDCP PDU已经被递交到下层(例如RLC层)，则PDCP实体指示下层，将被递交到下层的PDCP PDU丢弃。
可以理解的是，数据包是数据在传输网络中传递的形式。例如数据包在国际互连协议(internet protocol，IP)层可以是由IP头和有效载荷构成的IP包，数据包在PDCP层可以是PDCP SDU或者由PDCP头和PDCP SDU构成的PDCP PDU。
下面以5G系统为例描述一个数据包从上至下的传递过程。IP层将一个IP包递交给SDAP层，即成为SDAP SDU，SDAP层对收到的SDAP SDU加头并进行服务质量(quality of service，QoS)映射后产生SDAP PDU，将产生的SDAP PDU递交给PDCP层，在PDCP层成为PDCP SDU。PDCP层为PDCP SDU增加PDCP头，并对PDCP头和/或PDCP SDU进行压缩，对PDCP SDU进行加密等操作后产生PDCP PDU，PDCP PDU被递交至RLC层成为RLC SDU，RLC层可以对RLC SDU进行分段，并添加相应的RLC头，从而产生一个或多个RLC PDU。RLC PDU递交到MAC层后成为MAC SDU，MAC层可以将多个MAC SDU组合起来，形成一个MAC PDU，从而交给底层也就是物理层进行物理传输。
一种可能的实施方式，如果丢包管理实体是终端设备或终端设备的PDCP层，数据包#2是数据包集合#1中到达丢包管理实体的第一个数据包，则丢弃计时器#2的时长可以由接入网设备配置，也可以由终端设备预设。例如，终端设备可以根据数据包集合#1的时延预算预设。如果丢包管理实体是接入网设备或接入网设备的PDCP层，数据包#2是数据包集合#1中的第一个数据包，则丢弃计时器#2的时长可以由接入网设备预设。例如，接入网设备根据数据包集合#1的时延预算预设。
示例地，数据包集合#1为PDU集合，丢弃计时器#1的时长可以是PSDB。例如，接入网设备为终端设备的PDCP实体配置的丢弃计时器(discardTimer)的时长等于PSDB。
一种可能的实施方式，无论丢包管理实体是终端设备或终端设备的PDCP层，还是接入网设备或接入网设备的PDCP层，数据包#1是数据包集合#1中到达丢包管理实体的第N个数据包，则丢弃计时器#1的时长可以由数据包#2(数据包集合#1中到达丢包管理实体的第N-1个数据包)的丢弃计时器#2的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定。
示例地，丢包管理实体可以根据丢弃计时器#2的时长与数据包#1和数据包#2到达丢包管理实体的时间间隔的差值确定丢弃计时器#1的时长。
例如，数据包集合#1包括6个数据包，按照到达PDCP实体的先后顺序依次是数据包#a1、数据包#a2、数据包#a3、数据包#a4、数据包#a5和数据包#a6，PDCP实体接收到数据包#a1时，为数据包#a1启动时长为30ms(毫秒)的丢弃计时器#a1，5ms后，PDCP实体接收到数据包#a2时，为数据包#a2启动时长为30ms-5ms＝25ms的丢弃计时器#a2，再5ms后，PDCP实体接收到数据包#a3时，为数据包#a3启动时长为25ms-5ms＝20ms的丢弃计时器#a3，以此类推，为简洁，对数据包#a4、数据包#a5和数据包#a6到达PDCP实体时，PDCP实体为其开启的丢弃计时器的时长不再一一列举。
可以理解，数据包集合#1为具备一定特征的一组数据包，或者数据包集合#1为按照一定规则划分的一组数据包，包括至少两个数据包。例如，数据包集合#1为包括相同的上层序列号(sequence number，SN)的一组数据包，或者数据包集合#1为一个PDU集合，或者数据包集合#1为应用层在短时间内产生的一组数据包，或者数据包集合#1中的数据包属于同一段多媒体数据(例如同属于一个视频帧，或同属于一段音视频)。
可选地，丢包管理实体为终端设备或终端设备的PDCP层，接入网设备向终端设备发送第一指示信息，该第一指示信息用于指示终端设备根据数据包#2的丢弃计时器#2的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定丢弃计时器#1的时长。
示例地，第一指示信息可以通过RRC信令发送，例如第一指示信息是承载于数据无线承载(data radio bearer，DRB)或者PDCP的配置信元中的字段/比特/枚举值，本申请对此不做限制。
例如，第一指示信息为PDUsetDiscard字段，若DRB或者PDCP的配置信元中有该字段，则终端设备或终端设备的PDCP层根据丢弃计时器#2的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定丢弃计时器#1的时长。若DRB或者PDCP的配置信元中没有该字段，则终端设备或终端设备的PDCP层针对数据包可以采用统一丢弃定时器。
再例如，第一指示信息为1比特信息，该1比特取值为0时，终端设备或终端设备的PDCP层针对数据包可以采用统一丢弃定时器。该1比特取值为1时，终端设备或终端设备的PDCP层根据丢弃计时器#2的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定丢弃计时器#1的时长。
又例如，第一指示信息为枚举值support(支持)。若DRB或者PDCP的配置信元中有该枚举值，则终端设备或终端设备的PDCP层根据丢弃计时器#2的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定丢弃计时器#1的时长。若DRB或者PDCP的配置信元中没有该枚举值，则终端设备或终端设备的PDCP层针对数据包可以采用统一丢弃定时器。
可以理解的是，只要是终端设备接收一个指示信息，从而终端设备获知根据丢弃计时器#2的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定丢弃计时器#1的时长，则该指示信息为本申请实施例中的第一指示信息。
本申请对承载第一指示信息的信令、信元，以及第一指示信息的具体体现形式不做限制。
示例#1，丢包管理实体为终端设备或终端设备的PDCP层，接入网设备向终端设备发送第一指示信息，对应的，终端设备接收该第一指示信息。第一指示信息如PDUsetDiscard，该第一指示信息可以通过RRC信令发送，例如第一指示信息承载于DRB或者PDCP的配置信元中。接入网设备可以为丢包管理实体配置时长为PSDB的丢弃计时器，即数据包集合#1中到达丢包管理实体的第一个数据包的丢弃计时器的时长被配置为PSDB，PSDB是QoS参数，是QoS流对传输时延的要求。例如，核心网会将QoS参数告诉接入网设备以便接入网设备通过合适的调度行为使得QoS参数得到满足。数据包集合#1可以以PDU集合为例，该PDU集合中的数据包携带相同的PDU集合SN，例如数据包集合#1中的数据包都携带SN#m。
示例#1中接收该第一指示信息的终端设备可以是丢包管理实体，即丢包管理实体本身为终端设备。或者接收该第一指示信息的终端设备为丢包管理实体所在的终端设备，即丢包管理实体为终端设备的PDCP层。后文出现的接收指示信息的终端设备同此理解，后文出现不再赘述。
图5是本申请实施例提供的示例#1中各数据包的丢弃计时器的示意图。
如图5所示，当PDCP实体接收到来自上层的数据包(数据包#a1)，且该数据包是第一个携带了SN#m的数据包时，PDCP实体为该数据包启动时长为PSDB的丢弃计时器(丢弃计时器#a1)；t1时间后，PDCP实体接收到第二个携带SN#m的数据包(数据包#a2)，则为其启动时长为(PSDB-t1)的丢弃计时器 (丢弃计时器#a2)；再过t2时间后，PDCP实体接收到第三个携带SN#m的数据包(数据包#a3)，则为其启动时长为(PSDB-t1-t2)的丢弃计时器(图5未示出)；后续PDCP实体接收到的携带SN#m的数据包依此类推。最终，PDU集合中第6个携带SN#m的数据包(数据包#a6)的丢弃计时器(丢弃计时器#a6)超时时，该PDU集合中的所有数据包的丢弃计时器会同时超时，即超出PSDB时(或者说PSDB耗尽时)，该PDU集合中的所有数据包都会被丢弃。
可以理解的是，图5示例的各数据包的丢弃计时器的确定方法也适用于丢包管理实体为接入网设备或接入网设备的PDCP层的情况。示例#2，丢包管理实体为接入网设备或接入网设备的PDCP层，接入网设备可以预设PDCP实体的丢弃计时器的时长为PSDB，即接入网设备可以预设数据包集合中到达丢包管理实体的第一个数据包的丢弃计时器的时长被配置为PSDB。例如接入网设备预设数据包集合#1中第一个到达丢包管理实体的数据包的丢弃计时器的时长为数据包集合#1的传输时延预算。
进一步地，丢弃计时器#1的时长还可以基于扩展计时器的时长确定。即丢包管理实体根据数据包#2的丢弃计时器的时长，数据包#1和数据包#2到达丢包管理实体的时间间隔以及扩展计时器的时长确定数据包#1的丢弃计时器的时长。
可以理解，若丢包管理实体为终端设备或终端设备的PDCP层，扩展计时器的时长可以由接入网设备配置，也可以由终端设备预设，例如终端设备根据数据包的时延预算预设扩展计时器的时长。若丢包管理实体为接入网设备或接入网设备的PDCP层，扩展计时器的时长可以由接入网设备预设。例如，接入网设备可以根据数据包的时延预算预设扩展计时器的时长。
示例地，丢包管理实体为终端设备或终端设备的PDCP层，接入网设备向终端设备发送第二指示信息，对应的，终端设备接收该第二指示信息，第二指示信息指示扩展计时器的时长。
一种可能的实施方式，在扩展计时器的时长小于时长#1的情况下，丢弃计时器#1的时长为时长#1；在扩展计时器的时长大于或等于时长#1的情况下，丢弃计时器#1的时长为扩展计时器的时长，时长#1基于丢弃计时器#2的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定。
示例地，时长#1基于丢弃计时器#2的时长与数据包#1和数据包#2到达丢包管理实体的时间间隔的差值确定。
也就是说，除数据包集合#1中第一个到达丢包管理实体的数据包之外，第N个到达丢包管理实体的数据包的丢弃计时器的时长为MAX{第N-1个到达丢包管理实体的数据包的丢弃计时器的时长-第N个数据包和第N-1数据包到达丢包管理实体的时间间隔，扩展计时器的时长}。数据包集合#1中第一个到达丢包管理实体的数据包的丢弃计时器的时长的确定方法，可以参考上文数据包#2为数据包集合#1中第一个到达丢包管理实体的数据包时，丢弃计时器#2的时长的确定方法，不再赘述。
示例#3，数据包集合#1为PDU集合，该PDU集合中的数据包携带SN#m。扩展计时器(discardTimerExtend)的时长等于PDB，并且PDCP实体维护的丢弃计时器的时长为PSDB，PDCP实体维护的丢弃计时器为数据包集合#1中第一个到达丢包管理实体的数据包的丢弃计时器。若PSDB＝15ms，PDB＝8ms，当PDCP实体接收到来自上层的数据包，且该数据包是第一个携带了SN#m的数据包时，PDCP实体为该数据包启动时长为15ms的丢弃计时器；5ms后，PDCP实体接收到第二个携带SN#m的数据包，该数据包的丢弃计时器的时长为MAX{第1个到达PDCP实体的数据包的丢弃计时器的时长-第2个数据包和第1个数据包到达PDCP实体的时间间隔，8ms}，即MAX{15ms-5ms＝10ms，8ms}，因此为其启动时长为10ms的丢弃计时器；又5ms后，PDCP实体接收到第三个携带SN#m的数据包，该数据包的丢弃计时器的时长为MAX{第2个到达PDCP实体的数据包的丢弃计时器的时长-第3个数据包和第2个数据包到达PDCP实体的时间间隔，8ms}，即MAX{10ms-5ms＝5ms，8ms}，因此为其启动时长为8ms的丢弃计时器，后续PDCP实体接收到的携带SN#m的数据包的丢弃计时器的时长与第三个携带SN#m的数据包的丢弃计时器的时长的计算方式类似，不再一一列举。
图6是本申请实施例提供的示例#3中各数据包的丢弃计时器的示意图。
如图6所示，该PDU集合中先到达的部分数据包(例如第1个和第2个到达PDCP实体的数据包)会在PSDB耗尽时被丢弃，而后到达的部分数据包(例如第6个到达PDCP实体的数据包)则可以在PSDB耗尽后继续存活至自身PDB(即扩展计时器的时长)耗尽被丢弃。
可以理解，本申请实施例中的名称扩展计时器仅为示例，对本申请的保护范围不构成限制。
对于类似XR业务的相关业务，确定丢弃计时器#1的时长时考虑扩展计时器的这种方式，在将数据包集合#1作为整体进行丢包管理的同时，考虑到了数据包集合#1内部分数据包存在到达时延。因此对于 后到达的数据包，允许其在数据包集合#1的传输时延预算耗尽后可以继续存活一段时间，使网络能够来得及对其进行调度传输，避免数据包集合#1不能被完整传输，可以保障XR业务的完整性，提升系统容量和资源利用效率。
基于方法400，对于每一个数据包而言，丢包管理实体可维护时长可变丢弃计时器，即可以根据实际传输情况调整每个数据包的丢弃计时器的时长。例如数据集合中后到达的数据包，如不调整该数据包的丢弃计时器的时长，则该数据包在数据集合的时延预算耗尽的情况下没有被及时丢弃，影响系统容量。进一步的，对于后到达的数据包，可以结合扩展计时器的时长，因此本方案在合理丢弃数据包的同时保障后到达数据包有足够的传输时间，可以保障类似XR业务的完整性传输，也可以提升系统容量。
图7是本申请实施例提供的另一种数据包的处理方法的流程示意图。图7所示的方法700应用于丢包管理实体，包括以下步骤：
S710，丢包管理实体接收数据包#1，数据包#1属于数据包集合#1。
在上行传输中，丢包管理实体可以为终端设备或终端设备的PDCP层，在下行传输中，丢包管理实体可以为接入网设备或接入网设备的PDCP层。
S720，丢包管理实体根据数据包集合#1的丢弃计时器处理数据包#1。
后文为简洁，将数据包集合#1的丢弃计时器记为丢弃计时器#A。
一种可能的实施方式，在丢弃计时器#A的时长小于数据包#1的丢弃计时器#1的时长的情况下，丢包管理实体根据丢弃计时器#A处理数据包#1。
在该实施方式中，丢包管理实体根据丢弃计时器#A处理数据包#1包括：在丢弃计时器#A超时的情况下，认为数据包集合#1中的所有数据包的丢弃计时器超时，丢包管理实体丢弃数据包集合#1中的所有数据包。
如果丢包管理实体是终端设备或终端设备的PDCP层，丢弃计时器#A和/或丢弃计时器#1(丢弃计时器#1可以是针对数据包集合#1中所有数据包的丢弃计时器)的时长可以由接入网设备配置(例如，接入网设备向终端设备发送指示信息，该指示信息指示丢弃计时器#A和/或丢弃计时器#1的时长)，也可以由终端设备预设。例如终端设备根据数据包的时延预算预设扩展计时器#1的时长，终端设备根据数据包集合的时延预算预设扩展计时器#A的时长。如果丢包管理实体是接入网设备或接入网设备的PDCP层，丢弃计时器#A和/或丢弃计时器#1的时长可以由接入网设备预设。例如接入网设备根据数据包的时延预算预设扩展计时器#1的时长，接入网设备根据数据包集合的时延预算预设扩展计时器#A的时长。
示例地，接入网设备可以通过RRC信令为终端设备或终端设备PDCP层配置丢弃计时器#A的时长，例如DRB或者PDCP的配置信元中包括指示信息A，该指示信息A可以是PduSetDiscardTimer，终端设备或终端设备PDCP层获取指示信息A后，当终端设备的PDCP层接收到数据包集合#1中的第一个数据包(即数据包集合#1中到达PDCP层的第1个数据包)时，为数据包集合#1启动时长为PduSetDiscardTimer配置值的丢弃计时器#A。接入网设备可以通过RRC信令为终端设备或终端设备PDCP层配置丢弃计时器#1的时长，例如DRB或者PDCP的配置信元中包括指示信息B，该指示信息B可以是DiscardTimer，终端设备或终端设备PDCP层获取指示信息B后，当终端设备的PDCP层接收到数据包集合#1中的第M个数据包(即数据包集合#1中到达PDCP层的第M个数据包)时，M大于或等于1，为第N个数据包开启时长为DiscardTimer配置值的丢弃计时器#1。
示例地，当丢包管理实体接收到来自上层(例如SDAP层或应用层)的数据包#1时，如果数据包#1是接收到的数据包集合#1的第一个数据包，则为数据包集合#1启动丢弃计时器#A。同时，每收到一个数据包，丢包管理实体为数据包启动时长为丢弃计时器#1的时长的丢弃计时器，丢弃计时器#A的时长小于或等于丢弃计时器#1的时长。当丢弃计时器#A超时时，认为数据包集合#1中所有数据包的丢弃计时器超时。丢包管理实体将数据包集合#1中的所有数据包丢弃，如果部分数据包已经被递交至下层，则丢包管理实体可以指示下层，将被递交到下层的数据包丢弃。
具体地，例如，数据包集合#1为PDU集合#m，丢包管理实体为PDCP实体，丢弃计时器#A的时长为PSDB，丢弃计时器#1的时长为infinity(无限)。当该PDCP实体接收到来自上层的数据包，且该数据包是第一个携带SN#m的数据包时，PDCP实体为该PDU集合#m启动时长为PSDB的丢弃计时器#A，同时为该数据包启动时长为infinity的丢弃计时器#1。后续每收到一个携带SN#m的数据包，都为其启动时长为infinity的丢弃计时器。丢弃计时器#A超时时，PDU集合#m的所有数据包的丢弃计时器都会被认为超时，如图8所示，丢弃计时器#A超时时PDU集合中的所有数据包被丢弃，如果部分数据包已经被递交至下层， 则丢包管理实体可以指示下层，将被递交到下层的数据包丢弃。
另一种可能的实施方式，丢包管理实体根据丢弃计时器#A和丢弃计时器#1处理数据包#1。
在该实施方式中，丢包管理实体根据丢弃计时器#A和丢弃计时器#1处理数据包#1包括：在丢弃计时器#A超时且丢弃计时器#1超时的情况下，丢包管理实体丢弃数据包#1。
示例地，当丢包管理实体接收到来自上层的数据包#1时，如果数据包#1是接收到的数据包集合#1的第一个数据包，则为数据包集合#1启动丢弃计时器#A。同时，每收到一个数据包，丢包管理实体为数据包启动时长为丢弃计时器#1的时长的丢弃计时器。当丢弃计时器#A超时且丢弃计时器#1也超时时，丢包管理实体将数据包#1丢弃，如果数据包#1已经被递交至下层，则丢包管理实体可以指示下层，将被递交到下层的数据包#1丢弃。可以理解的是，当丢弃计时器#A超时但丢弃计时器#1没有超时时，丢包管理实体不丢弃数据包#1。
例如，数据包集合#1为PDU集合#m，丢包管理实体为PDCP实体。当该PDCP实体收到来自上层的数据包，且该数据包是第一个携带了SN#m的数据包时，PDCP实体为该PDU集合#m启动丢弃计时器#A，同时为该数据包启动丢弃计时器#1，丢弃计时器#A的时长为PSDB，丢弃计时器#1的时长为PDB。后续接收到的携带SN#m的数据包，都为其启动时长为PDB的丢弃计时器。因此如图9所示，PDU集合#m中先到达的部分数据包(例如数据包#a1、数据包#a2、数据包#a3、数据包#a4)会在丢弃计时器#A超时时被丢弃，而后到达的数据包(例如数据包#a5、数据包#a6)可以在丢弃计时器#A超时后继续存活至自身丢弃计时器超时为止。
对于类似XR业务的相关业务，在该实施方式中，将数据包集合作为整体进行丢包管理的同时，考虑到了数据包集合内数据包可能的到达时延，对于后到达的数据包，允许其在丢弃计时器#A超时后继续存活一段时间，使网络能够来得及对其进行调度传输，避免数据包集合不能完整传输，保障了业务的完整性，可以提升系统容量和资源利用效率。
基于方法700，丢包管理实体可以同时维护数据包和数据包集合的丢弃计时器，从而通过数据包的丢弃计时器和数据包集合的丢弃计时器之间的配合，可以使数据包集合内的先到达的部分数据包在数据包集合的丢弃计时器超时时被丢弃，避免资源浪费。进一步的，对于后到达的部分数据包，可以结合该数据包自身的丢弃计时器，在自身丢弃计时器超时时被丢弃，在合理丢弃数据包的同时保障后到达的数据包有足够的传输时间，保障类似XR业务的完整性，也可以提升系统容量和资源利用效率。
图10是本申请实施例提供的又一种数据包的处理方法的流程示意图。图10所示的方法1000应用于丢包管理实体，包括以下步骤：
S1010，丢包管理实体接收数据包#1。
在上行传输中，丢包管理实体可以为终端设备或终端设备的PDCP层，在下行传输中，丢包管理实体可以为接入网设备或接入网设备的PDCP层。
示例地，丢包管理实体为PDCP实体，该数据包#1为来自上层(例如SDAP层或应用层)的数据包。
S1020，丢包管理实体根据数据包#1到达丢包管理实体时的第一抖动确定数据包#1的丢弃计时器#1的时长。
可选地，方法1000还包括：
丢包管理实体根据丢弃计时器#1处理数据包#1。
丢包管理实体根据丢弃计时器#1如何处理数据包#1，可以参考方法400中的描述，在此不再赘述。
一种可能的实施方式，丢包管理实体根据时长#A和第一抖动确定丢弃计时器#1的时长，时长#A为预配置的数据包#1的丢弃计时器#1的时长。
示例地，丢弃计时器#1的时长为时长#A加第一抖动。
示例地，第一抖动基于数据包#1到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。例如，第一抖动为数据包#1到达丢包管理实体的预期时刻和实际时刻的差值。第一抖动为正数表示数据包#1早于预期时刻到达丢包管理实体，第一抖动为负数表示数据包#1晚于预期时刻到达丢包管理实体。
其中，数据包#1到达丢包管理实体的预期时刻可以根据业务周期确定。例如，数据包#1对应XR业务，XR业务的周期可以由应用层告知丢包管理实体，丢包管理实体可以根据周期和先于数据包#1到达的数据包到达丢包管理实体的具体时刻确定数据包#1到达丢包管理实体的预期时刻。
示例地，若丢包管理实体为终端设备或终端设备的PDCP层，则时长#A可以由接入网设备配置，也可以由终端设备通过数据包#1对应的业务的时延预算自行确定。若丢包管理实体为接入网设备或接入网 设备的PDCP层，则时长#A可以由接入网设备通过数据包#1对应的业务的时延预算自行确定。时长#A可以理解为丢包管理实体维护的数据包的丢弃计时器的时长，即数据包到达丢包管理实体没有抖动时可以采用的丢弃计时器。
可选地，丢包管理实体为终端设备或终端设备的PDCP层，接入网设备向终端设备发送指示信息#1，对应的，终端设备接收该指示信息#1，该指示信息#1用于指示终端设备根据数据包到达丢包管理实体时的抖动确定数据包对应丢弃计时器的时长。终端设备接收到指示信息#1后，可以根据数据包#1的第一抖动确定丢弃计时器#1的时长。例如，指示信息#1为discardJitter。
示例地，时长#A为PDB，数据包#1到达丢包管理实体的预期时刻为T时刻，第一抖动基于数据包#1到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。若数据包#1到达丢包管理实体的实际时刻为T-t1时刻，第一抖动为T-(T-t1)＝t1，则丢弃计时器#1的时长为PDB+t1，若数据包#1到达丢包管理实体的实际时刻为T+t1时刻，第一抖动为T-(T+t1)＝-t1，则丢弃计时器#1的时长为PDB-t1。数据包#1到达丢包管理实体的预期时刻可以由丢包管理实体根据该数据包#1对应业务的特征自行确定，如果丢包管理实体是终端设备或终端设备的PDCP层，该预期时刻还可以由接入网设备指示。
示例地，丢包管理实体是终端设备或终端设备的PDCP层，数据包#1对应XR业务，XR业务有特定帧率，即周期性产生数据包，产生数据包的周期可以由应用层告知丢包管理实体，丢包管理实体可以根据该周期确定数据包到达丢包管理实体的预期时刻。或者，接入网设备可以向终端设备指示该周期。或者，接入网设备向终端设备指示数据包到达丢包管理实体的预期时刻，例如，接入网设备向终端设备指示的预期时刻可以是协调世界时(universal time coordinated，UTC)，帧号或子帧号。
另一种可能的实施方式，丢包管理实体根据数据包#1到达丢包管理实体时的第一抖动确定数据包#1的丢弃计时器#1的时长，包括：
丢包管理实体根据数据包#1的预期传输完成时刻和数据包#1到达丢包管理实体的实际时刻确定丢弃计时器#1的时长。可以理解的是，正因为数据包#1到达丢包管理实体的实际时刻和预期时刻存在时间间隔，即存在第一抖动，丢包管理实体才需根据数据包#1的预期传输完成时刻和数据包#1到达丢包管理实体的实际时刻确定。因此，丢包管理实体根据数据包#1的预期传输完成时刻和数据包#1到达丢包管理实体的实际时刻确定丢弃计时器#1的时长可以理解为丢包管理实体根据数据包#1到达丢包管理实体时的第一抖动确定数据包#1的丢弃计时器#1的时长的一种示例。
数据包#1的预期传输完成时刻可以根据数据包#1对应的业务确定，例如丢弃计时器#1的时长为数据包#1的预期传输完成时刻和数据包#1到达丢包管理实体的实际时刻的时间差。具体地，若数据包#1预期要在t2时刻前完成传输，数据包#1到达丢包管理实体的实际时刻为t1时刻，则丢弃计时器#1的时长为t2-t1。
在该实施方式中，数据包#1到达丢包管理实体的实际时刻可能会发生抖动，即与数据包#1到达丢包管理实体的预期时刻有偏差，因此采用该实施方式确定丢弃计时器#1的时长，可以避免数据包#1早于预期时刻到达丢包管理实体的情况下被过早丢弃，或者避免数据包#1晚于预期时刻到达丢包管理实体的情况下不能被及时丢弃。
图11是本申请实施例提供的考虑抖动时数据包#1的丢弃计时器的示意图。
如图11所示，时长#a为数据包#1到达丢包管理实体的预期时刻和数据包#1的预期传输完成时刻的时间间隔，若数据包#1早于预期时刻T到达，即数据包#1到达丢包管理实体的实际时刻与预期时刻的时间间隔为抖动#1，则数据包#1的丢弃计时器#1的时长为时长#a+抖动#1。若数据包#1晚于预期时刻到达，即数据包#1到达丢包管理实体的实际时刻与预期时刻的时间间隔为抖动#2，则丢弃计时器#1的时长为时长#a-抖动#2。
数据包#1的预期传输完成时刻可以由丢包管理实体根据该数据包#1对应业务的特征自行确定，如果丢包管理实体是终端设备或终端设备的PDCP层，该预期传输完成时刻可以由接入网设备指示。
传输完成可以理解为数据包#1从发送设备的接入层发出直到接收设备从接入层接收到数据包#1，即预期传输完成时刻可以是接收设备从接入层接收到数据包#1的预期时刻。
示例地，丢包管理实体是终端设备或终端设备的PDCP层，数据包#1对应XR业务，XR业务有特定帧率，即周期性产生数据包，并且期望在时延预算(delay budget)内完成传输，产生数据包的周期和时延预算可以由应用层告知丢包管理实体，丢包管理实体可以根据该周期和时延预算确定数据包#1的预期传输完成时刻。或者，接入网设备可以向终端设备指示该周期。例如，丢包管理实体可以根据周期和先 于数据包#1到达的数据包到达丢包管理实体的具体时刻和周期确定数据包#1到达丢包管理实体的预期时刻，结合预期时刻和时延预算确定数据包#1的预期传输完成时刻。或者，接入网设备可以向终端设备指示该预期传输完成时刻。例如，接入网设备向终端设备指示的预期传输完成时刻可以是协调世界时(universal time coordinated，UTC)，帧号或子帧号。
可以理解，本申请实施例中的不同方法可以结合使用，或者本申请实施例中不同方法的实施方式也可以结合使用。
例如，方法400和方法1000可以结合使用，例如数据包#1为数据包集合#1中的数据包，当丢包管理实体接收到来自上层的数据包#1时，如果数据包#1是数据包集合#1到达丢包管理实体的第一个数据包，数据包#1到达丢包管理实体产生了第一抖动，且数据包#1早于预期时刻到达，则数据包#1的丢弃计时器#1的时长为时长#A(参见前文描述)加第一抖动，若数据包#1晚于预期时刻到达，则丢弃计时器#1的时长为时长#A减第一抖动。后续到达的数据包的丢弃计时器的时长可以基于丢弃计时器#1和时间间隔确定，例如后续到达的数据包为数据包A，则该时间间隔为数据包A和数据包#1到达丢包管理实体的时间间隔，具体根据丢弃计时器#1和时间间隔如何确定可参考方法400中相关内容的描述，不再赘述。
或者数据包#1为数据包集合#1中的数据包，当丢包管理实体接收到来自上层的数据包#1时，如果数据包#1是数据包集合#1到达丢包管理实体的第一个数据包，数据包#1到达丢包管理实体产生了第一抖动，且数据包#1早于预期时刻到达，则数据包#1的丢弃计时器#1的时长为时长#a(参见前文描述)加第一抖动，若数据包#1晚于预期时刻到达，则丢弃计时器#1的时长为时长#a减第一抖动。后续到达的数据包的丢弃计时器的时长可以基于丢弃计时器#1和时间间隔确定。时间间隔参考方法400中的描述，不再赘述。
或者丢弃计时器#1的时长为数据包集合#1的实际到达时刻与数据包集合#1的预期传输完成时刻的时间差。数据包集合#1的实际到达时刻可以理解为数据包集合#1中到达丢包管理实体的第一个数据包实际到达丢包管理实体的时刻，数据包集合#1的预期传输完成时刻可以理解为数据包集合#1中最后一个数据包从接收设备接入层接收到的时刻。除数据包集合#1中第一个到达丢包管理实体数据包之外，后续到达的数据包的丢弃计时器的时长在确定的时候还可以考虑扩展计时器的时长，具体如何考虑可参见方法400中的描述，此处不再赘述。
上述S1020描述的是数据包#1作为独立数据包，丢包管理实体如何根据丢弃计时器#1处理数据包#1。如果数据包#1不是独立数据包，而是属于数据包集合#1中的一个数据包，则S1020可替换为：丢包管理实体根据数据包#0到达丢包管理实体时的第二抖动确定数据包集合#1的丢弃计时器#A的时长，数据包#1属于数据包集合#1，数据包#0为数据包集合#1中到达丢包管理实体的第一个数据包。
一种可能的实施方式，丢包管理实体根据时长#B和第二抖动确定丢弃计时器#A的时长，时长#B为预配置的数据包集合#1的丢弃计时器#A的时长。
示例地，丢弃计时器#A的时长为时长#B加第二抖动。
示例地，第二抖动基于数据包#0到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。例如，第二抖动为数据包#0到达丢包管理实体的预期时刻和实际时刻的差值。第二抖动为正数，表示数据包#0早于预期时刻到达丢包管理实体，第二抖动为负数，表示数据包#0晚于预期时刻到达丢包管理实体。
其中，数据包#0到达丢包管理实体的预期时刻可以根据业务周期确定。
示例地，若丢包管理实体为终端设备或终端设备的PDCP层，则时长#B可以由接入网设备配置，也可以由终端设备通过数据包集合#1对应的业务的时延预算自行确定。若丢包管理实体为接入网设备或接入网设备的PDCP层，则时长#B可以由接入网设备通过数据包集合#1对应的业务的时延预算自行确定。时长#B可以理解为丢包管理实体维护的数据包集合#1的丢弃计时器，即数据包#0到达丢包管理实体没有抖动时采用的数据包集合#1的丢弃计时器。
可选地，丢包管理实体为终端设备或终端设备的PDCP层，接入网设备向终端设备发送指示信息#2，对应的，终端设备接收该指示信息#2，该指示信息#2用于指示终端设备根据数据包集合中数据包到达丢包管理实体时的抖动确定数据包集合对应丢弃计时器的时长。终端设备接收到指示信息#2后，可以根据数据包#0的第二抖动确定丢弃计时器#A的时长。例如，指示信息#2为discardJitter。
示例地，时长#B为PSDB，数据包#0到达丢包管理实体的预期时刻为T时刻，第二抖动基于数据包#0到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。若数据包#0到达丢包管理实体的实际时刻为T-t1时刻，第二抖动为T-(T-t1)＝t1，则丢弃计时器#A的时长为PSDB+t1，若数据包#0到达丢包管理实体的实际时刻为T+t1时刻，第二抖动为T-(T+t1)＝-t1，则丢弃计时器#A的时长为PSDB-t1。数据 包#0到达丢包管理实体的预期时刻可以由丢包管理实体根据该数据包集合#1对应业务的特征自行确定，如果丢包管理实体是终端设备或终端设备的PDCP层，该预期时刻还可以由接入网设备指示。具体参见前文数据包#1到达丢包管理实体的预期时刻的确定方法，此处不再赘述。
另一种可能的实施方式，丢包管理实体根据数据包#0到达丢包管理实体时的第二抖动确定数据包集合#1的丢弃计时器#A的时长，包括：
丢包管理实体根据数据包集合#1的预期传输完成时刻和数据包集合#1到达丢包管理实体的实际时刻确定丢弃计时器#A的时长。可以理解的是，正因为数据包#0到达丢包管理实体的实际时刻和预期时刻存在时间间隔，即存在第二抖动，丢包管理实体才需根据数据包集合#1的预期传输完成时刻和数据包集合#1到达丢包管理实体的实际时刻确定。因此，丢包管理实体根据数据包集合#1的预期传输完成时刻和数据包集合#1到达丢包管理实体的实际时刻确定丢弃计时器#A的时长可以理解为丢包管理实体根据数据包#0到达丢包管理实体时的第二抖动确定数据包集合#1的丢弃计时器#A的时长的一种示例。
其中，数据包集合#1到达丢包管理实体的实际时刻可以理解为数据包#0到达丢包管理实体的实际时刻，数据包集合#1的预期传输完成时刻可以理解为预期数据包集合#1中最后一个数据包从接收设备接入层接收到的时刻。
在该实施方式中，数据包#0到达丢包管理实体的实际时刻可能会发生抖动，即与数据包#0到达丢包管理实体的预期时刻有偏差，因此采用该实施方式确定丢弃计时器#A的时长，可以避免数据包#0早于预期时刻到达丢包管理实体的情况下数据包集合#1中的部分数据包被过早丢弃，或者避免数据包#0晚于预期时刻到达丢包管理实体的情况下数据包集合#1中的部分数据包不能被及时丢弃。
数据包集合#1的预期传输完成时刻可以根据数据包集合#1对应的业务确定，例如丢弃计时器#A的时长为数据包集合#1的预期传输完成时刻和数据包集合#1的到达丢包管理实体实际时刻的时间差。具体地，若数据包集合#1预期要在T2时刻前完成传输，数据包集合#1到达丢包管理实体的实际时刻为T1时刻，则可以确定丢弃计时器#A的时长为T2-T1。
数据包集合#1的预期传输完成时刻可以由丢包管理实体根据该数据包集合#1对应业务的特征自行确定，如果丢包管理实体是终端设备或终端设备的PDCP层，该预期传输完成时刻可以由接入网设备指示。具体可以参考前文数据包#1的预期传输完成时刻的确定方法，此处不再赘述。
可选地，方法1000还包括：
丢包管理实体根据丢弃计时器#A处理数据包#1。
示例地，当丢弃计时器#A超时时，认为数据包集合#1中的所有数据包的丢弃计时器超时，丢包管理实体将数据包集合#1中的所有数据包丢弃，如果部分数据包已经被递交至下层，则丢包管理实体可以指示下层，将被递交到下层的数据包丢弃。
可以理解为在该示例中，当丢弃计时器#A超时时，即使数据包集合#1中的部分数据包的丢弃计时器还没有超时，也会被认为这部分数据包的丢弃计时器超时，即丢弃计时器#A超时时，无论数据包集合#1中是否存在数据包的丢弃计时器没有超时，数据包集合#1中的所有数据包都会被丢弃。
或者，当丢弃计时器#A超时，数据包#1的丢弃计时器#1也超时时，丢包管理实体将数据包#1丢弃，如果数据包#1已经被递交至下层，则丢包管理实体可以指示下层，将被递交到下层的数据包#1丢弃。
可以理解为在该示例中，当丢弃计时器#A超时时，还需确定数据包#1的丢弃计时器是否超时，如果数据包#1的丢弃计时器没有超时，则不丢弃该数据包#1，如果数据包#1的丢弃计时器超时，则丢弃该数据包#1。
基于方法1000，丢包管理实体可以根据实际发生的抖动调整数据包或数据包集合对应的丢弃计时器的时长，或者数据包或数据集合对应的丢弃计时器的时长可以基于传输时间(例如实际到达时间或预期传输完成时间)确定，避免数据包被过早丢弃或未及时丢弃，即使得数据包在合理的时间被丢弃，以提升系统容量和资源利用效率。
上述流程图中各步骤的先后顺序依照方法的内在逻辑确定，上述流程图中所示的序号仅为示例，不对本申请步骤的先后顺序造成限制。
在本申请中，“指示”可以显式地和/或隐式地指示。示例性地，隐式指示可以基于用于传输的位置和/或资源；显式指示可以基于一个或多个参数，和/或一个或多个索引，和/或一个或多个它所表示的位模式。
可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可 以在某些场景下，与其他特征进行结合，不作限定。
本申请的各实施例中的方案可以进行合理的组合使用，并且实施例中出现的各个术语的解释或说明、相似操作、或步骤可以在各个实施例中互相参考或解释，对此不作限定。
还可以理解，上述各个方法实施例中，由丢包管理实体(例如终端设备，终端设备的PDCP层，接入网设备，或接入网设备的PDCP层)实现的方法和操作，也可以由丢包管理实体(例如终端设备，终端设备的PDCP层，接入网设备，或接入网设备的PDCP层)的组成部件(例如芯片、芯片系统、处理器或者电路)来实现。
应理解，本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系，但也可能表示的是一种“和/或”的关系，具体可参考前后文进行理解。
本申请中，“至少一项(个)“是指一项(个)或者多项(个)，“至少两项(个)“以及“多项(个)”是指两项(个)或两项(个)以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。如果没有特别说明，本申请中的多个为2个以及2个以上。
上文结合附图描述了本申请实施例的方法实施例，下面描述本申请实施例的装置实施例。可以理解，方法实施例的描述与装置实施例的描述可以相互对应，因此，未描述的部分可以参见前面方法实施例。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如发射端设备或者接收端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图12是本申请实施例提供的通信装置1200的示意图。该装置1200包括收发单元1210。收发单元1210可以用于实现相应的通信功能。收发单元1210还可以称为通信接口或通信单元。
可选地，该装置1200还包括处理单元1220。处理单元1220可以用于进行数据处理。
可选地，该装置1200还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1220可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中丢包管理实体的动作。
在一种设计中，该装置1200可以是前述实施例中的丢包管理实体(例如终端设备，终端设备的PDCP层，接入网设备，或接入网设备的PDCP层)，也可以是丢包管理实体的组成部件(如芯片)。该装置1200可实现对应于上文方法实施例中的丢包管理实体执行的步骤或者流程，其中，收发单元1210可用于执行上文方法实施例中丢包管理实体的收发相关的操作，处理单元1220可用于执行上文方法实施例中丢包管理实体的处理相关的操作。
该装置1200可实现对应于根据本申请实施例的方法实施例中的丢包管理实体执行的步骤或者流程，该装置1200可以包括用于执行图4、图7或图10所示实施例中的丢包管理实体执行的方法的单元。
一种可能的实施方式，收发单元1210，用于接收数据包#1；处理单元1220，用于根据数据包#2的丢弃计时器的时长，以及数据包#1和数据包#2到达丢包管理实体的时间间隔确定数据包#1的丢弃计时器#1的时长，数据包#2先于数据包#1到达丢包管理实体，数据包#1和数据包#2属于数据包集合#1。
可选地，处理单元1220具体用于根据数据包#2的丢弃计时器的时长与上述时间间隔的差值确定丢弃计时器#1的时长。
可选地，处理单元1220具体用于根据数据包#2的丢弃计时器的时长，上述时间间隔以及扩展计时器的时长确定丢弃计时器#1的时长。
可选地，在扩展计时器的时长小于时长#1的情况下，处理单元1220确定丢弃计时器#1的时长为时长#1，时长#1基于数据包#2的丢弃计时器的时长，以及上述时间间隔确定；在扩展计时器的时长大于或等于时长#1的情况下，处理单元1220确定丢弃计时器#1的时长为扩展计时器的时长。
可选地，该丢包管理实体为终端设备或终端设备的分组数据汇聚协议PDCP层，收发单元1220还用于接收来自接入网设备的第一指示信息，该第一指示信息指示终端设备根据数据包#2的丢弃计时器的时长，以及上述时间间隔确定丢弃计时器#1的时长。
可选地，该丢包管理实体为终端设备或终端设备的PDCP层，收发单元1220还用于接收来自接入网设备的第二指示信息，第二指示信息指示扩展计时器的时长。
可选地，该丢包管理实体为接入网设备或接入网设备的PDCP层。
可选地，在丢弃计时器#1超时的情况下，丢包管理实体丢弃数据包#1。
可选地，扩展计时器的时长基于数据包#1的时延预算确定。
可选地，数据包#2为数据包集合#1中到达丢包管理实体的第一个数据包，数据包#2的丢弃计时器的时长基于数据包集合#1的时延预算确定。
另一种可能的实施方式，收发单元1210，用于接收数据包#1，数据包#1属于数据包集合#1；处理单元1220，用于根据数据包集合#1的丢弃计时器处理数据包#1。
可选地，在数据包集合#1的丢弃计时器的时长小于数据包#1的丢弃计时器#1的时长的情况下，处理单元1220，具体用于根据数据包集合#1的丢弃计时器处理数据包#1。
可选地，在数据包集合#1的丢弃计时器超时的情况下，处理单元1220用于丢弃数据包集合#1。
可选地，处理单元1220具体用于根据数据包集合#1的丢弃计时器和数据包#1的丢弃计时器#1处理数据包#1。
可选地，在数据包集合#1的丢弃计时器超时且丢弃计时器#1超时的情况下，处理单元1220用于丢弃数据包#1。
可选地，丢包管理实体为终端设备或终端设备的PDCP层，收发单元1220还用于接收来自接入网设备的指示信息，该指示信息用于配置数据包集合#1的丢弃计时器。
可选地，丢包管理实体为接入网设备或接入网设备的PDCP层。
可选地，数据包集合#1的丢弃计时器的时长基于数据包集合#1的时延预算确定。
又一种可能的实施方式，收发单元1210，用于接收数据包#1；处理单元1220，用于根据数据包#1到达丢包管理实体时的第一抖动确定数据包#1的丢弃计时器#1的时长。或处理单元1220，用于根据数据包#0到达丢包管理实体时的第二抖动确定数据包集合#1的丢弃计时器的时长，数据包#1属于数据包集合#1，数据包#0为数据包集合#1中到达丢包管理实体的第一个数据包。
可选地，第一抖动基于数据包#1到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。
可选地，丢弃计时器#1的时长基于第一抖动和时长#A确定，该时长#A为预配置的数据包#1的丢弃计时器的时长。
可选地，第二抖动基于数据包#0到达丢包管理实体的预期时刻和实际时刻的时间间隔确定。
可选地，数据包集合#1的丢弃计时器的时长基于第二抖动和时长#B确定，该时长#B为预配置的数据包集合#0的丢弃计时器的时长。
可选地，上述预期时刻基于业务周期确定。
可选地，处理单元1220，具体用于根据数据包#1的预期传输完成时刻和数据包#1到达丢包管理实体的实际时刻确定丢弃计时器#1的时长。
可选地，处理单元1220，具体用于根据数据包集合#1的预期传输完成时刻和数据包#0到达丢包管理实体的实际时刻确定数据包集合#1的丢弃计时器的时长。
可选地，丢包管理实体为终端设备或终端设备的PDCP层，收发单元1220还用于接收来自接入网设备的指示信息，该指示信息指示终端设备根据数据包到达丢包管理实体时的抖动确定该数据包对应丢弃计时器的时长，或者所述指示信息指示终端设备根据数据包集合中数据包到达丢包管理实体时的抖动确定该数据包集合对应丢弃计时器的时长。
可选地，丢包管理实体为接入网设备或接入网设备的PDCP层。
可选地，时长#A基于数据包#1的时延预算确定。
可选地，时长#B基于数据包集合#1的时延预算确定。
图13是本申请实施例提供的通信装置1300的示意图。该装置1300包括处理器13120，处理器13120与存储器1320耦合，存储器1320用于存储计算机程序或指令和/或数据，处理器13120用于执行存储器1320存储的计算机程序或指令，或读取存储器1320存储的数据，以执行上文各方法实施例中的方法。
在一些实施例中，处理器13120为一个或多个。
在一些实施例中，存储器1320为一个或多个。
在一些实施例中，该存储器1320与该处理器13120集成在一起，或者分离设置。
在一些实施例中，如图13所示，该装置1300还包括收发器1330，收发器1330用于信号的接收和/或发送。例如，处理器13120用于控制收发器1330进行信号的接收和/或发送。
作为一种方案，该装置1300用于实现上文各个方法实施例中由丢包管理实体(例如终端设备，终端设备的PDCP层，接入网设备，或接入网设备的PDCP层)执行的操作。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由丢包管理实体(例如终端设备，终端设备的PDCP层，接入网设备，或接入网设备的PDCP层)执行的方法的计算机指令。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由丢包管理实体(例如终端设备，终端设备的PDCP层，接入网设备，或接入网设备的PDCP层)执行的方法。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线 (例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (35)

  1. 一种丢包管理方法，其特征在于，所述方法应用于丢包管理实体，包括：
    所述丢包管理实体接收第一数据包；
    所述丢包管理实体根据第二数据包的丢弃计时器的时长，以及所述第一数据包和所述第二数据包到达所述丢包管理实体的时间间隔确定所述第一数据包的第一丢弃计时器的时长，所述第二数据包先于所述第一数据包到达所述丢包管理实体，所述第一数据包和所述第二数据包属于第一数据包集合。
  2. 根据权利要求1所述的方法，其特征在于，所述丢包管理实体根据第二数据包的丢弃计时器的时长，以及所述第一数据包和所述第二数据包到达所述丢包管理实体的时间间隔确定所述第一数据包的第一丢弃计时器的时长，包括：
    所述丢包管理实体根据所述第二数据包的丢弃计时器的时长与所述时间间隔的差值确定所述第一丢弃计时器的时长。
  3. 根据权利要求1或2所述的方法，其特征在于，所述丢包管理实体根据第二数据包的丢弃计时器的时长，以及所述第一数据包和所述第二数据包到达所述丢包管理实体的时间间隔确定所述第一数据包的第一丢弃计时器的时长，包括：
    所述丢包管理实体根据所述第二数据包的丢弃计时器的时长，所述时间间隔以及扩展计时器的时长确定所述第一丢弃计时器的时长。
  4. 根据权利要求3所述的方法，其特征在于，所述丢包管理实体根据所述第二数据包的丢弃计时器的时长，所述时间间隔以及扩展计时器的时长确定所述第一丢弃计时器的时长，包括：
    在所述扩展计时器的时长小于第一时长的情况下，所述丢包管理实体确定所述第一丢弃计时器的时长为所述第一时长，所述第一时长基于所述第二数据包的丢弃计时器的时长，以及所述时间间隔确定；
    在所述扩展计时器的时长大于或等于所述第一时长的情况下，所述丢包管理实体确定所述第一丢弃计时器的时长为所述扩展计时器的时长。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述丢包管理实体为终端设备或终端设备的分组数据汇聚协议PDCP层，所述方法还包括：
    所述终端设备接收来自接入网设备的第一指示信息，所述第一指示信息指示所述终端设备根据所述第二数据包的丢弃计时器的时长，以及所述时间间隔确定所述第一丢弃计时器的时长。
  6. 根据权利要求3至5中任一项所述的方法，其特征在于，所述丢包管理实体为终端设备或终端设备的分组数据汇聚协议PDCP层，所述方法还包括：
    所述终端设备接收来自接入网设备的第二指示信息，所述第二指示信息指示所述扩展计时器的时长。
  7. 根据权利要求1至4中任一项所述的方法，其特征在于，所述丢包管理实体为接入网设备或接入网设备的PDCP层。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    在所述第一丢弃计时器超时的情况下，所述丢包管理实体丢弃所述第一数据包。
  9. 根据权利要求3至8中任一项所述的方法，其特征在于，所述扩展计时器的时长基于所述第一数据包的时延预算确定。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述第二数据包为所述第一数据包集合中到达所述丢包管理实体的第一个数据包，所述第二数据包的丢弃计时器的时长基于所述第一数据包集合的时延预算确定。
  11. 一种丢包管理方法，其特征在于，所述方法应用于丢包管理实体，包括：
    所述丢包管理实体接收第一数据包，所述第一数据包属于第一数据包集合；
    所述丢包管理实体根据所述第一数据包集合的丢弃计时器处理所述第一数据包。
  12. 根据权利要求11所述的方法，其特征在于，所述丢包管理实体根据所述第一数据包集合的丢弃计时器处理所述第一数据包，包括：
    在所述第一数据包集合的丢弃计时器的时长小于所述第一数据包的第一丢弃计时器的时长的情况下，所述丢包管理实体根据所述第一数据包集合的丢弃计时器处理所述第一数据包。
  13. 根据权利要求11或12所述的方法，其特征在于，所述丢包管理实体根据所述第一数据包集合的 丢弃计时器处理所述第一数据包，包括：
    在所述第一数据包集合的丢弃计时器超时的情况下，所述丢包管理实体丢弃所述第一数据包集合。
  14. 根据权利要求11所述的方法，其特征在于，所述丢包管理实体根据所述第一数据包集合的丢弃计时器处理所述第一数据包，包括：
    所述丢包管理实体根据所述第一数据包集合的丢弃计时器和所述第一数据包的第一丢弃计时器处理所述第一数据包。
  15. 根据权利要求14所述的方法，其特征在于，所述丢包管理实体根据所述第一数据包集合的丢弃计时器和所述第一数据包的第一丢弃计时器处理所述第一数据包，包括：
    在所述第一数据包集合的丢弃计时器超时且所述第一丢弃计时器超时的情况下，所述丢包管理实体丢弃所述第一数据包。
  16. 根据权利要求11至15中任一项所述的方法，其特征在于，所述丢包管理实体为终端设备或终端设备的PDCP层，所述方法还包括：
    所述终端设备接收来自接入网设备的指示信息，所述指示信息用于配置所述第一数据包集合的丢弃计时器。
  17. 根据权利要求11至16中任一项所述的方法，其特征在于，所述丢包管理实体为接入网设备或接入网设备的PDCP层。
  18. 根据权利要求11至17中任一项所述的方法，其特征在于，所述第一数据包集合的丢弃计时器的时长基于所述第一数据包集合的时延预算确定。
  19. 一种丢包管理方法，其特征在于，所述方法应用于丢包管理实体，包括：
    所述丢包管理实体接收第一数据包；
    所述丢包管理实体根据所述第一数据包到达所述丢包管理实体时的第一抖动确定所述第一数据包的第一丢弃计时器的时长；或
    所述丢包管理实体根据第二数据包到达所述丢包管理实体时的第二抖动确定第一数据包集合的丢弃计时器的时长，所述第一数据包属于所述第一数据包集合，所述第二数据包为所述第一数据包集合中到达所述丢包管理实体的第一个数据包。
  20. 根据权利要求19所述的方法，其特征在于，所述第一抖动基于所述第一数据包到达所述丢包管理实体的预期时刻和实际时刻的时间间隔确定。
  21. 根据权利要求19或20所述的方法，其特征在于，所述第一丢弃计时器的时长基于所述第一抖动和第一时长确定，所述第一时长为预配置的所述第一数据包的丢弃计时器的时长。
  22. 根据权利要求19所述的方法，其特征在于，所述第二抖动基于所述第二数据包到达所述丢包管理实体的预期时刻和实际时刻的时间间隔确定。
  23. 根据权利要求19或22所述的方法，其特征在于，所述第一数据包集合的丢弃计时器的时长基于所述第二抖动和第二时长确定，所述第二时长为预配置的所述第一数据包集合的丢弃计时器的时长。
  24. 根据权利要求20或22所述的方法，其特征在于，所述预期时刻基于业务周期确定。
  25. 根据权利要求19所述的方法，其特征在于，所述丢包管理实体根据所述第一数据包到达所述丢包管理实体时的第一抖动确定所述第一数据包的第一丢弃计时器的时长，包括：
    所述丢包管理实体根据所述第一数据包的预期传输完成时刻和所述第一数据包到达所述丢包管理实体的实际时刻确定所述第一丢弃计时器的时长。
  26. 根据权利要求19所述的方法，其特征在于，所述丢包管理实体根据第二数据包到达所述丢包管理实体时的第二抖动确定第一数据包集合的丢弃计时器的时长，包括：
    所述丢包管理实体根据所述第一数据包集合的预期传输完成时刻和所述第二数据包到达所述丢包管理实体的实际时刻确定所述第一数据包集合的丢弃计时器的时长。
  27. 根据权利要求19至26中任一项所述的方法，其特征在于，所述丢包管理实体为终端设备或终端设备的PDCP层，所述方法还包括：
    所述终端设备接收来自接入网设备的指示信息，所述指示信息指示所述终端设备根据数据包到达所述丢包管理实体时的抖动确定数据包对应丢弃计时器的时长，或者所述指示信息指示所述终端设备根据数据包集合中数据包到达所述丢包管理实体时的抖动确定数据包集合对应丢弃计时器的时长。
  28. 根据权利要求19至26中任一项所述的方法，其特征在于，所述丢包管理实体为接入网设备或 接入网设备的PDCP层。
  29. 根据权利要求21所述的方法，其特征在于，所述第一时长基于所述第一数据包的时延预算确定。
  30. 根据权利要求23所述的方法，其特征在于，所述第二时长基于所述第一数据包集合的时延预算确定。
  31. 一种通信装置，其特征在于，包括执行如权利要求1至10中任一项所述方法的单元或模块，或执行如权利要求11至18中任一项所述方法的单元或模块，或执行如权利要求19至30中任一项所述方法的单元或模块。
  32. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行以下任一项：
    如权利要求1至10中任一项所述的方法，如权利要求11至18中任一项所述的方法，如权利要求19至30中任一项所述的方法。
  33. 根据权利要求32所述的装置，其特征在于，所述装置还包括所述存储器和/或通信接口，所述通信接口与所述处理器耦合，
    所述通信接口，用于输入和/或输出信息。
  34. 一种计算机可读存储介质，其特征在于，包括计算机程序，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至10中任一项所述的方法；或者，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求11至18中任一项所述的方法；或者
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求19至30中任一项所述的方法。
  35. 一种计算机程序产品，其特征在于，所述计算机程序产品中包括计算机程序代码，其特征在于：
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求1至10中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求11至18中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求19至30中任一项所述的方法。
PCT/CN2023/126166 2022-11-04 2023-10-24 数据包的处理方法和通信装置 WO2024093725A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211379116.1A CN117998461A (zh) 2022-11-04 2022-11-04 数据包的处理方法和通信装置
CN202211379116.1 2022-11-04

Publications (1)

Publication Number Publication Date
WO2024093725A1 true WO2024093725A1 (zh) 2024-05-10

Family

ID=90898010

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/126166 WO2024093725A1 (zh) 2022-11-04 2023-10-24 数据包的处理方法和通信装置

Country Status (2)

Country Link
CN (1) CN117998461A (zh)
WO (1) WO2024093725A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111385221A (zh) * 2018-12-29 2020-07-07 华为技术有限公司 一种数据处理方法和通信设备
CN111865820A (zh) * 2020-07-10 2020-10-30 锐迪科微电子科技（上海）有限公司 数据发送方法、装置、接收端、通信系统、设备及介质
WO2021031019A1 (zh) * 2019-08-16 2021-02-25 Oppo广东移动通信有限公司 数据包的删除方法、设备及存储介质
CN113923713A (zh) * 2020-07-09 2022-01-11 维沃移动通信有限公司 数据处理的方法及装置
WO2022036341A1 (en) * 2020-08-11 2022-02-17 Qualcomm Incorporated Techniques for timer adjustment for packet loss

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111385221A (zh) * 2018-12-29 2020-07-07 华为技术有限公司 一种数据处理方法和通信设备
WO2021031019A1 (zh) * 2019-08-16 2021-02-25 Oppo广东移动通信有限公司 数据包的删除方法、设备及存储介质
CN113923713A (zh) * 2020-07-09 2022-01-11 维沃移动通信有限公司 数据处理的方法及装置
CN111865820A (zh) * 2020-07-10 2020-10-30 锐迪科微电子科技（上海）有限公司 数据发送方法、装置、接收端、通信系统、设备及介质
WO2022036341A1 (en) * 2020-08-11 2022-02-17 Qualcomm Incorporated Techniques for timer adjustment for packet loss

Also Published As

Publication number Publication date
CN117998461A (zh) 2024-05-07

Similar Documents

Publication Publication Date Title
WO2019196810A1 (zh) 一种数据传输的方法、相关设备及通信系统
CN113766567A (zh) 一种通信方法及装置
US20220159100A1 (en) Communication Method And Apparatus
US20240056889A1 (en) Communication processing method for data transmission and related device
WO2023207846A1 (zh) 通信方法和装置
CN116114254A (zh) 一种通信方法及装置
WO2024093725A1 (zh) 数据包的处理方法和通信装置
WO2021249218A1 (zh) 数据传输方法和装置
WO2021027854A1 (zh) 一种通信方法及设备
WO2021087923A1 (zh) 一种传输信息的方法和装置
WO2024104101A1 (zh) 数据处理方法、装置、通信设备及可读存储介质
WO2024067106A1 (zh) 通信方法、装置及计算机可读存储介质
WO2023241452A1 (zh) 数据处理方法、装置及通信设备
WO2023216986A1 (zh) 缓存状态报告bsr指示方法和装置
WO2023070392A1 (zh) 数据传输方法、设备及存储介质
WO2022056863A1 (zh) 一种切换方法及装置
WO2024099159A1 (zh) 确定丢包的方法、装置、通信设备及可读存储介质
WO2023207850A1 (zh) 通信方法及通信装置
WO2024131590A1 (zh) 信息传输方法、装置及通信设备
WO2024131591A1 (zh) 信息传输方法、装置及通信设备
WO2024093908A1 (zh) 一种通信方法及相关设备
WO2024067365A1 (zh) 数据传输方法及装置
WO2024088260A1 (zh) 一种被用于无线通信的通信节点中的方法和装置
WO2023040586A1 (zh) 定时器处理方法、装置及存储介质
WO2023109743A1 (zh) 传输数据的方法和通信装置

Legal Events

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

Ref document number: 23884657

Country of ref document: EP

Kind code of ref document: A1